Katia Rojas wrote on 2019-10-23 3:22PM GMT+2: ...snip... > Where should we send the survey that we've been working on? > > So far there is a strong opinion on sending it only to the > [email protected] <[email protected]> > > The main purpose of this survey is to gather feedback from all existing ASF > contributors about the current level of diversity and inclusion, including > education, age, socio-economic status, and gender. ...snip... "All existing ASF contributors" is tens of thousands of people, many of whom we may not have any effective way to contact (i.e. drive-by contributors to various Apache projects in the past). So defining "contributor" is important; it's also important to decide what *effective* group of people we can contact with hopes of responses.
dev@diversity will only get a very small number of highly self-selected individuals, so is no where near what we need. It seems to me (and I'm not on the survey team), the best thing to do is mirror the existing 2016 survey and send a single, well-written email to [email protected] asking all Apache committers to respond. While that won't catch non-committers who have contributed, it's a very important metric to start with, and is much easier than trying to contact all-dev@ lists or use the giant announce@ list. I understand the goal; but the effort and effectiveness for reaching *all* contributors is much higher. It feels like getting a really solid set of committer data first might be best. Does that make sense? Note also that there are specific technical rules for successfully emailing committers@ or other wide lists, so be sure to work with infra or someone to get help before physically sending the mail. -- - Shane Director & Member The Apache Software Foundation
