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: Thu, 30 Aug 2018 14:18:19 +0200	[thread overview]
Message-ID: <87sh2wcak4.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20180830031607.GB665@sigill.intra.peff.net>


On Thu, Aug 30 2018, Jeff King wrote:

> On Wed, Aug 29, 2018 at 03:12:37PM +0200, Ævar Arnfjörð Bjarmason 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).
>> [...]
>> 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) :)
>
> Yes, if nobody steps up to do 2, then it won't happen. :)
>
> For myself, I don't think I have time to commit to mentoring this round.
> And IMHO the people signing up to mentor should be the ones contributing
> to the project list (since they will ultimately be on the hook for
> working on those projects with the intern).
>
>> 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?

Thanks!

> It doesn't need to be. As far as I know, the main reasons (from the
> perspective of a project) to do it through Outreachy are:
>
>  - being part of a larger program generates attention and gets the
>    interest of intern candidates (free advertising, if you will)

I was wondering if we couldn't do it through Outreachy *and* also do our
own advertisements / possibly recruit candidates outside of the
Outreachy pool. In that case we'd still get the attention/outreach
benefits, in addition to our own...

>  - Outreachy handles payment, invoicing for external funds, and any
>    legal stuff
>
>  - it's possibly easier to external funding if it's earmarked for a
>    program like Outreachy, since that program provides a framework with
>    particular goals, conditions, oversight, etc.

... but not both of these at least if we selected any a non-Outreachy
candidates. Nice to get a good summary of the pros there.

> I think there's some general value in having a group, too. Because
> there are many interns all participating at the same time, they can
> offer each other support or advice, show off their work to each other
> via blog posts, etc.  And it may be easier for them to communicate
> about their accomplishments and status for future work, since it's
> part of an established program that can easily be explained.

Yup, but just as a clarifying point here wouldn't the participants also
get all the same benefits of this in the case of Outreachy+OurOwnProgram
if we ran OurOwnProgram concurrently to Outreachy?

I.e. I was assuming that once candidates are "handed off" to a project
they're communicating within that project (possibly with other
candidates), and Outreachy is no longer very involved (except maybe for
progress reports / final report, but wouldn't we also do that for a
OurOwnProgram?).

I may have that completely wrong though, which is why I'm asking, which
b.t.w. I'm doing mostly just to get an idea of how what Outreachy's role
is in this exactly, not to strongly advocate for a OurOwnProgram.

> As for reasons _not_ to do it, I don't think the requirements are particularly
> onerous. Mostly it's:
>
>   - it has to happen at a specific time, which might not be convenient
>     for mentors or interns (last year I found it hard to get focused
>     starting in December, with all of the holidays)

Yup.

>   - it naturally limits the candidate pool to under-represented groups
>     (which is the whole point of the program, but if you don't
>     actually care about that, then it's just a complication)

I'm fine with doing selection discrimination of under-represented groups
through such a program. Particularly if, as you mention, there's
earmarked funding for it which otherwise might not be available, so it's
not zero-sum when it comes to a hypothetical alternative of casting a
wider net of our own (and as you mention, that would be more work).

I do think it's unfortunate that the selection criteria for the program
privileges U.S. citizens and U.S. residents above other people,
particularly since they're also accepting worldwide candidates (and
we've had at least one non-American participant that I know about), so
it's not e.g. for U.S. administrative or tax reasons as one might expect
if they only accepted Americans.

I don't think that's some big deal, just something that puts the Git
project as an international cooperation (and one that solicits funds
from donors worldwide) into a slightly odd position, so something we
should keep in mind going forward.

> So IMHO it's easily worth the trouble.
>
>> 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.
>
> I think that the autonomy and level of responsibility for the
> mentors/project is about the same between GSoC and Outreachy. The main
> difference is just the funding model (but again, I suspect we would not
> have too much trouble securing external funding).

Thanks.

  parent reply	other threads:[~2018-08-30 12:18 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 [this message]
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=87sh2wcak4.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).