From: Christian Couder <email@example.com>
To: Heba Waly <firstname.lastname@example.org>
Cc: Jeff King <email@example.com>, git <firstname.lastname@example.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Emily Shaffer <email@example.com>,
Jonathan Tan <firstname.lastname@example.org>
Subject: Re: GSoC and Outreachy Summer 2020?
Date: Fri, 21 Feb 2020 17:03:47 +0100 [thread overview]
Message-ID: <CAP8UFD1QbOK9g2oAhfTm2npoNF9Ay_HiAfFai9rJwZzc73cBbw@mail.gmail.com> (raw)
On Fri, Feb 21, 2020 at 2:44 PM Heba Waly <email@example.com> wrote:
> On Sun, Feb 16, 2020 at 11:39 PM Christian Couder
> <firstname.lastname@example.org> wrote:
> > For some time I have been thinking about trying to get more former
> > GSoC students and Outreachy interns helping us with mentoring.
> Hi Christian,
> I'd be happy to co-mentor an Outreachy intern with an experienced
> mentor, hope I'm not too late.
Thank you for your interest in co-mentoring! It's very much appreciated!
I don't think you are late. It seems that February 25 at 4pm UTC is
the deadline for project submission.
> If so, please guide me on the steps required to get involved.
Earlier in this thread Dscho (Johannes Schindelin) said he would be ok
to mentor someone for Outreachy, so I think, if he is still
interested, he would be the best person to guide you on the steps
required to get involved, and perhaps he could co-mentor with you.
I am planning to mentor a GSoC student this Summer, not an Outreachy
intern, and I think it would simplify things for me if I am not
involved in both programs. But let's see what Dscho says.
next prev parent reply other threads:[~2020-02-21 16:04 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
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 [this message]
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
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:
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 \
* 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
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).