From: Christian Couder <christian.couder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Emily Shaffer <emilyshaffer@google.com>,
Jonathan Tan <jonathantanmy@google.com>
Subject: Re: GSoC and Outreachy Summer 2020?
Date: Tue, 4 Feb 2020 17:11:20 +0100 [thread overview]
Message-ID: <CAP8UFD2_qmB1q9vhz=BJo3XG4jnLWDPhCVVb4gAh_pfKoGnZJQ@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD1-cswU0gSX3a2KqiExhYgY_qMZ6Sz7FHdxs7mrb_hh-w@mail.gmail.com>
On Tue, Feb 4, 2020 at 12:55 PM Christian Couder
<christian.couder@gmail.com> wrote:
>
> On Wed, Jan 22, 2020 at 6:34 AM Jeff King <peff@peff.net> wrote:
> >
> > I notice deadlines are approaching for Git to apply for GSoC (Feb 5th)
> > and for Outreachy (Feb 18th), though we still have some time. Do mentors
> > have sufficient bandwidth for us to participate?
>
> I am willing to mentor or co-mentor someone for GSoC.
>
> (Sorry about replying only to Peff previously.)
>
> I also just added the following file, made from SoC-2019-Ideas.md:
>
> https://github.com/git/git.github.io/blob/master/General-Application-Information.md
>
> As with https://github.com/git/git.github.io/blob/master/General-Microproject-Information.md
> the idea is to not have separate documents for each year and each
> program (GSoC or Outreachy), but rather point people to the same
> document that we should update regularly.
While at it, I just applied on behalf of Git to the GSoC 2020 and I
sent invite to possible Organization Administrators. I am one of the
admins already but we need another person to accept the invite before
tomorrow as they require at least 2 admins. This is the only thing
left we need to apply.
The information I used to apply is in:
https://git.github.io/SoC-2020-Org-Application/
Thanks,
Christian.
next prev parent reply other threads:[~2020-02-04 16:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 5:34 GSoC and Outreachy Summer 2020? Jeff King
2020-01-22 14:15 ` Johannes Schindelin
2020-02-04 11:55 ` Christian Couder
2020-02-04 16:11 ` Christian Couder [this message]
2020-02-04 16:13 ` Christian Couder
2020-02-04 16:37 ` Jeff King
2020-02-16 10:38 ` Christian Couder
2020-02-21 13:44 ` Heba Waly
2020-02-21 16:03 ` Christian Couder
2020-02-21 18:30 ` Jeff King
2020-02-22 7:20 ` Heba Waly
2020-02-23 21:44 ` Jeff King
2020-02-24 15:48 ` Johannes Schindelin
2020-02-25 20:20 ` Jeff King
2020-02-26 0:55 ` Heba Waly
2020-02-26 1:42 ` Jeff King
2020-02-26 10:17 ` Heba Waly
2020-02-26 18:38 ` Jeff King
2020-02-24 7:30 ` Christian Couder
2020-02-21 10:27 ` Christian Couder
2020-02-26 6:17 ` Christian Couder
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD2_qmB1q9vhz=BJo3XG4jnLWDPhCVVb4gAh_pfKoGnZJQ@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=peff@peff.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://80x24.org/mirrors/git.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).