From: Jeff King <peff@peff.net>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>,
"Jonathan Tan" <jonathantanmy@google.com>,
"Emily Shaffer" <emilyshaffer@google.com>,
"Оля Тележная" <olyatelezhnaya@gmail.com>,
"Matheus Tavares Bernardino" <matheus.bernardino@usp.br>,
"Elijah Newren" <newren@gmail.com>,
"Thomas Gummerer" <t.gummerer@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: Re: Number of Outreachy interns and co-mentors
Date: Fri, 27 Sep 2019 00:43:04 -0400 [thread overview]
Message-ID: <20190927044304.GA24011@sigill.intra.peff.net> (raw)
In-Reply-To: <CAP8UFD0gQU4JKneKc6HLxT6NutzZrxDVqWKDSeOx1ZYDfMkWRw@mail.gmail.com>
On Thu, Sep 26, 2019 at 03:12:15PM +0200, Christian Couder wrote:
> On https://www.outreachy.org/apply/project-selection/#git it looks
> like we will only have 1 intern as the title of our section is "Git -
> 1 intern". I wonder if it's because only funding for 1 intern has been
> secured or if there is another reason.
Right, it's because of the funding promise.
> Also I am not sure how people can register that they are ok to
> co-mentor one of the project, but it looks like the person who
> registered a project can invite co-mentors. So I think it would be
> nice if people, who would be ok to co-mentor, could tell which
> projects they would be ok to co-mentor, so that we all know and that
> they can be invited to co-mentor on the site.
>
> It would be great if we could have 2 (co-)mentors per project and it
> would likely help getting funding for all the interns.
Yeah, I agree it would be nice to have that in the system if there's
going to be co-mentoring. I don't know how the interface for it works,
though (and I think the mentors see different screens than I do).
-Peff
prev parent reply other threads:[~2019-09-27 4:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 13:12 Number of Outreachy interns and co-mentors Christian Couder
2019-09-27 4:43 ` Jeff King [this message]
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=20190927044304.GA24011@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=matheus.bernardino@usp.br \
--cc=newren@gmail.com \
--cc=olyatelezhnaya@gmail.com \
--cc=t.gummerer@gmail.com \
/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 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 NNTP newsgroup(s).