git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	git@vger.kernel.org,
	"Christian Couder" <christian.couder@gmail.com>
Subject: Re: Git in Outreachy Dec-Mar?
Date: Thu, 30 Aug 2018 15:24:53 -0400	[thread overview]
Message-ID: <20180830192453.GC19685@sigill.intra.peff.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1808301340280.71@tvgsbejvaqbjf.bet>

On Thu, Aug 30, 2018 at 01:46:00PM +0200, Johannes Schindelin wrote:

> On Wed, 29 Aug 2018, Jeff King wrote:
> 
> >   - 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)
> > 
> > So IMHO it's easily worth the trouble.
> 
> I am willing to mentor, and the only reason that kept me from already
> stepping forward and trying to brush up the landing page is this concern:
> traditionally, we (as in: the core Git contributors) have been less than
> successful in attracting and retaining contributors from under-represented
> groups. I don't think any regular reader of this mailing list can deny
> that.
> 
> And while I find it very important to reach out (there are just *so* many
> benefits to having a more diverse team), I have to ask *why* we are so
> unsuccessful. As long as we do not even know the answer to that, is it
> even worth pursuing Outreachy?
> 
> I mean, if we make serious mistakes here, without even realizing, that
> directly lead to being stuck in our old bubble, then we are prone to
> simply repeat those mistakes over and over and over again. And that would
> just be a waste of our time, *and* a big de-motivator for the Outreachy
> students.
> 
> What's your take on this?

My feeling is that our lack of diversity has less to do with driving out
diverse candidates, and more that they do not join in the first place.
Which isn't to say we _wouldn't_ drive out diversity, but that I'm not
sure we have very good data on what happens in that second stage. If we
can use the program to overcome "step 1", that helps us get that data
(and hopefully react to it in time to be useful, and not just use the
candidate as a guinea pig; I agree there is the possibility of doing
more harm than good to a student who becomes de-motivated).

That leaves aside the question of whether things we are doing prevent
people from participating in the first place. I'm certainly open to that
idea, but I think it's a separate discussion.

-Peff

  reply	other threads:[~2018-08-30 19:24 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 [this message]
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

  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=20180830192453.GC19685@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --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.
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).