On 4/13/2019 11:02 AM, Joan Touzet wrote:
On 2019-04-13 2:37 a.m., Dinesh Joshi wrote:
Rich, Myrle – both of you made great points. I especially think non-code
contributions are critical and generally go unrecognized. They are
equally as important.
Regarding gathering data about individuals being nominated, perhaps
sending a survey to the PMC Chairs to gather the stats, would that be
reasonable? I am just trying brainstorm an effective way to gather data
around who is being left out and associated reasons.
Hi Dinesh,
I like the idea, but the devil is in the details.
PMCs tend to be overloaded with responsibilities already. Unless we
provide them something well-packaged and easy to run, we won't get any
data this way.
You'll also end up with serious selection bias; we'll hear back from the
PMCs who are motivated to tell us about specific people, or who are
idle, or who have smaller communities (because it's easy to get your
hands around who all there is).
I'm not saying this isn't doable, but I am having a hard time thinking
of a way that we can get a good sample this way.
-Joan
Is the intent to have the PMC supply the information, or to ask the
nominee to complete a survey?
If the former, there may not be much information. I know and care about
a nominee's contributions, but do not typically know their gender or
ethnicity. I may be able to guess whether they identify as male or
female from their name, but that is limited by my limited knowledge of
non-English naming practices, and many English names are ambiguous.
If the latter, we would get into a situation in which people would know
they were being discussed because of getting a survey invitation.
How about sending survey requests to randomly selected people who are
active on project mailing lists?
Dinesh
On Apr 12, 2019, at 6:22 AM, Myrle Krantz <my...@apache.org> wrote:
On Thu, Apr 11, 2019 at 3:32 PM Rich Bowen <rbo...@rcbowen.com> wrote:
Your suggestion of surveying non-committer Github contributors
certainly
has merit, but, having tried to gather that kind of data in the past
(ie, actual contact info for contributors to an open source project,
based on Github names), it's not particularly easy, as even the people
that list their email address on Github (which is not everyone, by a
long shot) consider it pretty spammy to receive surveys.
Also, focusing on github contributions would leave out people who
provide
customer support. And documentation and graphics might not compare
appropriately in size with code contributions either. But non-code
contributors is one of our biggest problem-areas IMHO.
Best,
Myrle
---------------------------------------------------------------------
To unsubscribe, e-mail: diversity-unsubscr...@apache.org
For additional commands, e-mail: diversity-h...@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: diversity-unsubscr...@apache.org
For additional commands, e-mail: diversity-h...@apache.org
---
This email has been checked for viruses by AVG.
https://www.avg.com
---------------------------------------------------------------------
To unsubscribe, e-mail: diversity-unsubscr...@apache.org
For additional commands, e-mail: diversity-h...@apache.org
