all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [OUTREACHY] Proposal: substitutes over IPFS
Date: Thu, 17 Sep 2020 02:36:31 +0200	[thread overview]
Message-ID: <CAE4v=pjsB_zQ933-nO7=4wNv5XFCtgYck2xeYV4mztR0ZvT5zw@mail.gmail.com> (raw)
In-Reply-To: <m1a6xpzth8.fsf@khs-macbook.home>

Hello Konrad,

Konrad Hinsen <konrad.hinsen@fastmail.net> ezt írta (időpont: 2020.
szept. 16., Sze, 16:28):
>
> Hi Ludo,
>
> > I prefer not to volunteer to mentor it, but I’m happy to contribute to
> > discussions and code review.
> >
> > Who’d be willing to mentor it?
>
> I don't know what exactly that implies, so all I say for now is that I'd
> be happy to participate in this project. I know the IPFS side rather
> well, but have only a user-level knowledge of how Guix handles
> substitutes.
>
> Does Outreachy call for a single mentor, or can it be a team?

I believe it is better if  it's a team. How it worked in the past was
that we usually designated one person to be the primary mentor,
and have others help out when they were unavailable. Also we usually
had one hour weekly where there was live discussion,
where all the mentors were participating. Outreachy asks for a 5 hour
per week commitment from the team per intern.
Usually there are peeks when this can be more, but there are periods
when this is just too much. It all boils down to good communication
though.
I would be happy to co-mentor this, although I do not have too much
hands on knowledge about substitute handling code either.

>
> Konrad.

Best regards,
g_bor

-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21


  parent reply	other threads:[~2020-09-17  0:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 18:54 [OUTREACHY] Call for mentors Gábor Boskovits
2020-09-12 14:00 ` [OUTREACHY] toward a proposal? zimoun
2020-09-12 15:18   ` Gábor Boskovits
2020-09-16 14:01     ` zimoun
2020-09-16 15:24       ` Ricardo Wurmus
2020-09-16 15:45         ` zimoun
2020-09-16 17:22           ` Ricardo Wurmus
2020-09-16 18:27             ` zimoun
2020-09-16 18:46               ` Ricardo Wurmus
2020-09-17  8:12                 ` Gábor Boskovits
2020-09-17 10:01                   ` zimoun
2020-09-17 11:15                     ` Gábor Boskovits
2020-09-17 11:26                       ` zimoun
2020-09-17 12:01                         ` Gábor Boskovits
2020-09-16 13:22 ` [OUTREACHY] Proposal: substitutes over IPFS Ludovic Courtès
2020-09-16 14:05   ` Pierre Neidhardt
2020-09-16 14:28   ` Konrad Hinsen
2020-09-16 15:21     ` Ricardo Wurmus
2020-09-17  0:36     ` Gábor Boskovits [this message]
2020-09-17 20:33       ` 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='CAE4v=pjsB_zQ933-nO7=4wNv5XFCtgYck2xeYV4mztR0ZvT5zw@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    /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.