All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Heba Waly <heba.waly@gmail.com>
Cc: Jeff King <peff@peff.net>, 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: Fri, 21 Feb 2020 17:03:47 +0100	[thread overview]
Message-ID: <CAP8UFD1QbOK9g2oAhfTm2npoNF9Ay_HiAfFai9rJwZzc73cBbw@mail.gmail.com> (raw)
In-Reply-To: <CACg5j25_098i=rU++OB=YSbAFjCQdgUX7gP6D-9yo6F_A_yn0w@mail.gmail.com>

Hi Heba,

On Fri, Feb 21, 2020 at 2:44 PM Heba Waly <heba.waly@gmail.com> wrote:
>
> On Sun, Feb 16, 2020 at 11:39 PM Christian Couder
> <christian.couder@gmail.com> 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.

Best,
Christian.

  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

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=CAP8UFD1QbOK9g2oAhfTm2npoNF9Ay_HiAfFai9rJwZzc73cBbw@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=heba.waly@gmail.com \
    --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. 
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.