From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Christian Couder <christian.couder@gmail.com>
Subject: Re: Git in Outreachy Dec-Mar?
Date: Thu, 30 Aug 2018 15:42:24 -0400 [thread overview]
Message-ID: <20180830194223.GD19685@sigill.intra.peff.net> (raw)
In-Reply-To: <87sh2wcak4.fsf@evledraar.gmail.com>
On Thu, Aug 30, 2018 at 02:18:19PM +0200, Ævar Arnfjörð Bjarmason wrote:
> > 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...
True. I'd worry about spreading our mentor resources too thinly (which I
think are probably a bigger bottleneck than actual money). But I guess
you're proposing to issue a larger call for candidates, and then we pick
from the result (so in the end we'd end up with the same number of
actual interns, just from a bigger pool).
> 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.
I think there _is_ some contact and group resources between Outreachy
and the interns. But I'm actually not sure of the extent. I know they
encouraged interns to blog (and read each other's blogs). I don't know
if there's an intern mailing list, irc, etc. I had the impression that
there is, but I don't actually know the details.
> > - 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).
Yeah, just for reference, my "you" there was a hypothetical "one might
or might not care about...", not responding to your particular email.
> 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 assume you mean this bit from the eligibility rules:
You must meet one of the following criteria:
- You live any where in the world and you identify as a woman (cis
or trans), trans man, or genderqueer person (including genderfluid
or genderfree).
- You live in the United States or you are a U.S. national or
permanent resident living abroad, AND you are a person of any
gender who is Black/African American, Hispanic/Latin@, Native
American/American Indian, Alaska Native, Native Hawaiian, or
Pacific Islander
So there are more categories for the US, but I think that is largely
because under-representation is somewhat regional. Being black in the US
is different than being black in Africa. Certainly one could argue that
Africa as a whole is under-represented in the tech world, but I think
you'd probably need to draw different boundaries in different places if
you want to extend opportunities to those who are least likely to
already have them.
I don't know what those groupings would look like in, say, Europe. If
you're suggesting that the program would be better off having
region-specific rules for more regions, I'd certainly agree with that. I
don't know if it's something the Outreachy folks have considered or
discussed; it might be worth bringing it up.
-Peff
next prev parent reply other threads:[~2018-08-30 19:42 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 [this message]
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=20180830194223.GD19685@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--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.
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).