unofficial mirror of guix-devel@gnu.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: Mon, 10 Mar 2014 22:09:32 +0100	[thread overview]
Message-ID: <87a9cxkbg3.fsf@gnu.org> (raw)
In-Reply-To: <531E0776.3090705@rigelk.eu> (Pierre-Antoine Rault's message of "Mon, 10 Mar 2014 19:41:58 +0100")

Hi!

Thanks for your proposal!

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

> Having worked with libtorrent and kademila, i am quite familiar with dht
> and P2P, and I think GNUnet shouldn't be much difficult to adapt to. I
> am thus reading info about GNUnet, but I already have some features in
> mind (not sure if redondant with other messages posted before):

Please do get in touch with the GNUnet folks as well.  I’ve Cc’d them so
you can say hi.  ;-)

> * As said by Andreas Enge, users should all be able to share packages
> themselves, provided they can cryptographically sign their binaries.
> They would deploy a node (a personnal node) using a local deamon (could
> be by passing a command to guix-daemon which would handle the task). The
> local daemon would contact a list of known nodes (contained in a
> mirrorlist) and send them hashes with their corresponding signature.

What exactly do is meant by “node” and “mirrorlist” here?

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, and HTTP server.

[0] http://lists.gnu.org/archive/html/bug-guix/2013-03/msg00085.html

> * Users should be able to trust a node. That would not mean trusting all
> providers for all hashes recursively, but rather trust those trusted by
> the node in cascade. Thus a distinction beetween trusted pairs and
> trusted node pairs should be done.

Please read the “Invoking guix archive” section of the manual (from
Git), to get a feel of the current approach.  See also Mark’s message at
<https://lists.gnu.org/archive/html/guix-devel/2014-02/msg00297.html>
for ideas of what we’d like.

> * 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.

> My Scheme level isn't high, but I'm learning Geiser/Paredit at the
> moment and reading the docs thoroughly.

Depending on the approach taken, it could be an issue if you have little
experience with Scheme.

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.

Thanks,
Ludo’.

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

  reply	other threads:[~2014-03-10 21:09 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 [this message]
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

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87a9cxkbg3.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).