From: Jeff King <peff@peff.net>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Git in Outreachy Dec-Mar?
Date: Sat, 1 Sep 2018 04:43:22 -0400 [thread overview]
Message-ID: <20180901084321.GC25852@sigill.intra.peff.net> (raw)
In-Reply-To: <CAP8UFD0SYECLk--7JsZkxBdQeJPuG1Ut5GMLsCJHqM+jG7C0jQ@mail.gmail.com>
On Fri, Aug 31, 2018 at 10:16:49AM +0200, Christian Couder wrote:
> > 2. To get our landing page and list of projects in order (and also
> > micro-projects for applicants). This can probably build on the
> > previous round at:
> >
> > https://git.github.io/Outreachy-15/
> >
> > and on the project/microprojects lists for GSoC (which will need
> > some updating and culling).
>
> Ok to take a look at that.
Thanks. I think sooner is better for this (for you or anybody else who's
interested in mentoring). The application period opens on September
10th, but I think the (still growing) list of projects is already being
looked at by potential candidates.
> > 3. To figure out funding (unlike GSoC, the intern stipend comes from
> > the projects). I can look into getting outside funds (which is what
> > we did last year). Worst case, we do have enough project money to
> > cover an intern. Last year[1] opinions were that this was a
> > reasonable use of project money, but of course new opinions are
> > welcome.
>
> I can also look at getting outside funds.
>
> My opinion though is that it is probably better if the Git project can
> use its own fund for this, as it makes it easier for possible mentors
> if they don't need to look at getting outside funds.
I disagree. An internship costs more than we generally take in over the
course of a year. So we would eventually run out of money doing this.
I also think it doesn't need to be the mentor's responsibility to find
the funding. That can be up to an "org admin", and I don't think it
should be too big a deal (I had no trouble getting funding from GitHub
last year, and I don't expect any this year; I just didn't want to start
that process until I knew we were serious about participating).
So if you (or anybody else) wants to mentor, please focus on the project
list and application materials.
-Peff
next prev parent reply other threads:[~2018-09-01 8:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 15:14 Git in Outreachy Dec-Mar? Jeff King
2018-08-29 13:12 ` Ævar Arnfjörð Bjarmason
2018-08-30 3:16 ` Jeff King
2018-08-30 11:46 ` Johannes Schindelin
2018-08-30 19:24 ` Jeff King
2018-08-31 8:54 ` Christian Couder
2018-08-31 10:30 ` Оля Тележная
2018-09-01 7:11 ` Christian Couder
2018-09-01 8:34 ` Jeff King
2018-08-30 12:18 ` Ævar Arnfjörð Bjarmason
2018-08-30 19:42 ` Jeff King
2018-09-05 13:23 ` Ævar Arnfjörð Bjarmason
2018-08-31 8:16 ` Christian Couder
2018-09-01 8:43 ` Jeff King [this message]
2018-09-02 7:37 ` Christian Couder
2018-09-02 8:43 ` Jeff King
2018-09-03 4:36 ` Christian Couder
2018-09-05 7:20 ` Christian Couder
2018-09-06 1:14 ` Jeff King
2018-09-06 9:58 ` Christian Couder
2018-09-06 19:34 ` Jeff King
2018-09-08 8:59 ` Christian Couder
2018-09-06 1:21 ` Jeff King
2018-09-06 9:51 ` Christian Couder
2018-09-06 19:31 ` Jeff King
2018-09-08 8:57 ` Christian Couder
2018-09-08 15:40 ` Jeff King
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=20180901084321.GC25852@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
/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).