From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: [OUTREACHY] toward a proposal?
Date: Wed, 16 Sep 2020 17:45:15 +0200 [thread overview]
Message-ID: <CAJ3okZ2_55pVfS3LBrOu6QcKPNr=D9exTHgb=x7=d8KDLZu=Tw@mail.gmail.com> (raw)
In-Reply-To: <87zh5pvj64.fsf@elephly.net>
Thank you for explaining.
On Wed, 16 Sep 2020 at 17:23, Ricardo Wurmus <rekado@elephly.net> wrote:
> >> > The proposal is to implement the same result hiding all the plumbing
> >> > details, i.e.,
> >> >
> >> > guix git log --oneline | grep msmtp
> On the Outreachy website you need to get an account in order to request
> to become a (co-)mentor. The “community managers” (I think this
> includes me) then approve that.
Do you think the proposal is a good one for an Outreachy project?
> At this point you can write the proposal on the Outreachy website. This
> will again need to be approved in the end. We need to have a written
> proposal in the Outreachy system before the next round begins.
> Outreachy is a bit stricter in that regard than GSoC where it’s
> sufficient to have a vague project idea on some website. This is
> generally a good thing, because it facilitates more successful projects
> with fewer sub-projects that nobody ever thought through (which is a bad
> thing to discover one third into the internship).
Is this again approvement done by the "community managers" or by another board?
Cheers,
simon
next prev parent reply other threads:[~2020-09-16 15:48 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 [this message]
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
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
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='CAJ3okZ2_55pVfS3LBrOu6QcKPNr=D9exTHgb=x7=d8KDLZu=Tw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.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 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).