all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christian Grothoff <grothoff@in.tum.de>
To: Sree Harsha Totakura <totakura@in.tum.de>
Cc: Bart Polot <bart@net.in.tum.de>,
	Matthias Wachs <wachs@net.in.tum.de>,
	bug-guix@gnu.org, gnunet-developers@gnu.org
Subject: Re: [GNUnet-developers] Using GNUnet for binary package distribution
Date: Mon, 25 Mar 2013 11:51:06 +0100	[thread overview]
Message-ID: <51502C1A.6050504@in.tum.de> (raw)
In-Reply-To: <51502B22.2010703@in.tum.de>

Just to clarify, the point is to for now list the project under both 
mentoring organizations, and then sort out details later.  Having
mentoring from both Guix and GNUnet would make sense anyway, and I
believe having Harsha do it will make a lot of sense and avoid any
possible conflict in terms of the direction of the development.

So for now, what we ask you (Ludo) to do is to make sure the Guix/GNUnet
integration is listed on the GNU ideas page with you (or some other
Guix hacker) listed as a mentor.

Thanks!

Happy hacking!

-Christian

On 03/25/2013 11:46 AM, Sree Harsha Totakura wrote:
> On 03/23/2013 09:51 PM, Sree Harsha Totakura wrote:
>>> So how do we proceed?  On the GNU side, the submission as to be mailed
>>>> by Monday [0].
>>>>
>>>> Since you’re already working on gnunet-update, perhaps it would make
>>>> more sense for one of you to be the official mentor.
>>>>
>>>> Then I or anyone else on bug-guix can of course help for all things Guix.
>>>>
>>>> WDYT?
>> I prefer to register as a student for GSoC.  Once gnunet-update's gets
>> into good shape, I can then start hacking Guix to use gnunet.
>
> Hi Ludo,
>
> I just discussed with Christian.  We are thinking to represent the idea
> as follows since we see Guix and GNUnet as interdependent on delivering
> updates.
>
> * Under the GNU project, may be you can post the idea as "fetching
> updates using a peer-to-peer network (gnunet)"
> * Under the GNUnet project, it will be represented as "using Guix for
> delivering updates to GNUnet"
>
> Matthias and Bart shall be the mentors from GNUnet.
>
> Shall we agree on this?
>
> --
> Harsha
>

  reply	other threads:[~2013-03-25 10:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 13:02 Using GNUnet for binary package distribution Ludovic Courtès
2013-03-21 17:03 ` Andreas Enge
2013-03-21 18:01 ` Christian Grothoff
2013-03-21 18:14   ` Sree Harsha Totakura
2013-03-22 12:25     ` [GNUnet-developers] " Ludovic Courtès
2013-03-22 12:57       ` Christian Grothoff
2013-03-22 13:56         ` Ludovic Courtès
2013-03-22 12:29   ` [GNUnet-developers] " Ludovic Courtès
     [not found]     ` <514C6DF0.5000800@in.tum.de>
2013-03-22 14:52       ` Ludovic Courtès
2013-03-23 20:51         ` Sree Harsha Totakura
2013-03-25 10:46           ` Sree Harsha Totakura
2013-03-25 10:51             ` Christian Grothoff [this message]
2013-03-25 12:58               ` 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

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

  git send-email \
    --in-reply-to=51502C1A.6050504@in.tum.de \
    --to=grothoff@in.tum.de \
    --cc=bart@net.in.tum.de \
    --cc=bug-guix@gnu.org \
    --cc=gnunet-developers@gnu.org \
    --cc=totakura@in.tum.de \
    --cc=wachs@net.in.tum.de \
    /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.