all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Pierre-Antoine Rault <par@rigelk.eu>
Cc: guix-devel@gnu.org, gnunet-developers@gnu.org
Subject: Re: [GSoC] GNUnet binary distribution system
Date: Tue, 11 Mar 2014 14:06:38 +0100	[thread overview]
Message-ID: <87ob1ckhpd.fsf@gnu.org> (raw)
In-Reply-To: <531E4894.7080103@rigelk.eu> (Pierre-Antoine Rault's message of "Tue, 11 Mar 2014 00:19:48 +0100")

Pierre-Antoine Rault <par@rigelk.eu> skribis:

> On 10/03/2014 22:09, Ludovic Courtès wrote:

[...]

>> The initial discussion [0] left open the question of where
>> binaries themselves should be stored.  A possibility would be to
>> use GNUnet’s DHT simply as a discovery mechanism, and then to
>> establish a connection directly to the user’s machine, which would
>> run, say, an HTTP server.
>
> That's what I had in mind. Now, considered the post [2] by Christian
> Grothoff, we might consider using either an HTTP server for
> performance or GNUnet's MESH for anonymity (and security). We should
> balance needs and ease of implementation.
>
> [2] http://lists.gnu.org/archive/html/guix-devel/2014-03/msg00113.html

Yes.

Could you experiment with the MESH interface, and sketch how files would
be served concretely?  You could use the ‘gnunet-mesh’ command-line tool
for quick experimentation, although I haven’t found its documentation.

[...]

>>> * I think we should focus on ease of use, since it could become a
>>> good alternative to setting up a full fledged server to share
>>> officially supported packages and unofficial ones (like the AUR
>>> for Archlinux).
>>
>> That’s been discussed before (see
>> <http://lists.gnu.org/archive/html/guix-devel/2013-08/msg00127.html>),
>>
>>
> but it’s orthogonal.
>
> Then we have to extend the guix tools to cover user modules (overlays,
> that is).

Yes, but as I said, this is unrelated to the project at hand.

>> This proposal needs discussion with both Guix and GNUnet people
>> (and notably Sree Harsha, who is at the intersection of both
>> projects :-)), to work towards a concrete road map of things to
>> hack on.
>
> Sure ; It's the only way to have a clear and shared view of what parts
> of Guix are involved in the project. I'm working on a roadmap draft
> for now.

Great.  We can’t start this as a GSoC project unless we have a
reasonably clear view of what needs to be implemented.  We must not end
up re-discussing the general design once the coding period has started.
There are still a number of open issues, so it’s important to refine
that.

Thanks,
Ludo’.

_______________________________________________
GNUnet-developers mailing list
GNUnet-developers@gnu.org
https://lists.gnu.org/mailman/listinfo/gnunet-developers

      parent reply	other threads:[~2014-03-11 13:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 18:41 [GSoC] GNUnet binary distribution system Pierre-Antoine Rault
2014-03-10 21:09 ` Ludovic Courtès
2014-03-10 22:03   ` Christian Grothoff
2014-03-10 22:26     ` Ludovic Courtès
2014-03-10 23:19   ` Pierre-Antoine Rault
2014-03-11  3:35     ` Mark H Weaver
2014-03-11  6:59       ` Pierre-Antoine Rault
2014-03-11 18:29         ` Mark H Weaver
2014-03-11  8:42     ` Christian Grothoff
2014-03-11 13:06     ` Ludovic Courtès [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ob1ckhpd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=gnunet-developers@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=par@rigelk.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.