git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Christian Couder <christian.couder@gmail.com>
Subject: Re: Git in Outreachy Dec-Mar?
Date: Wed, 29 Aug 2018 15:12:37 +0200	[thread overview]
Message-ID: <8736uxe2pm.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20180828151419.GA17467@sigill.intra.peff.net>


On Tue, Aug 28 2018, Jeff King wrote:

> The Outreachy application period is set to begin on September 10th for
> interns participating in the December-March program. Do we want to
> participate?
>
> Details on the program are here:
>
>   https://www.outreachy.org/communities/cfp/
>
> If we want to, then we need:
>
>   1. Volunteers to mentor. This is similar in scope to being a GSoC
>      mentor.
>
>   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).
>
>   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.
>
> If the answer is "yes, we should participate", it will hopefully be
> accompanied with "yes, I will mentor", and "yes, and I will start
> getting the land#ing page ready." :)

I just have a "yes" to the first one of those. Which tells you how much
skin I have in the game (and how much you should(n't) listen to me) :)

Just a question: It seems to me that #1 and #2 is not tied up to the
Outreachy process. I agree that finding a qualified intern to work on
Git would be a good use of project funds.

What's not clear to me is if/how tied up this needs to be to a specific
external program such as Outreachy. I.e. do we as a project need to go
through that organization, or can that be just one of the ways in which
we send out a call for interns?

With GSoC we don't have a choice in the matter, since Google's paying
the bills and runs the show, but it sounds like in this case we at least
partially do.

Or maybe Outreachy is doing some heavy lifting with screening or has
partial subsidies which would still make it prohibitive to e.g. send out
a general call of our own for candidates on the mailing list & in other
venues.

  reply	other threads:[~2018-08-29 13:12 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8736uxe2pm.fsf@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --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 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).