diversity-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Griselda Cuevas <g...@apache.org>
Subject Re: Survey Diversity and Inclusion
Date Fri, 01 Nov 2019 23:43:15 GMT
Hi folks - I'm adding Maria, who will help us draft a comprehensive comms
plan to outline what we have communicated in this thread.


The plan so far is the following:

1. Send direct emails to all apache.org addresses OR to committers@
inviting them to fill the survey
2. Send a note to pmcs@ asking them to share the survey in their users@ and
dev@ lists
3. Social media promotion (in partnership w/ Sally)

Can you help us note this in the comms plan? Once you have it, you can
share w/ this list in a new thread to facilitate discussion on a single


On Fri, 1 Nov 2019 at 11:00, Griselda Cuevas <gris@apache.org> wrote:

> Thanks for the feedback everyone, we're evaluating the best alternative to
> reach the most committers and contributors.
> Kevin is helping us determine if we can do a direct upload of apache.org
> email addresses to the survey software directly. If we determine this is a
> safe procedure, we'll do that instead of the email to committers@
> We will still send a note to pmcs@ asking them to share a link to the
> survey with their mailing lists. The message will be different, so I
> wouldn't worry about duplication or spam.
> I will also work with Sally to write any comms.
> G
> On Fri, 1 Nov 2019 at 08:04, William A Rowe Jr <wrowe@rowe-clan.net>
> wrote:
>> On Mon, Oct 28, 2019 at 6:10 PM Patricia Shanahan <pats@acm.org> wrote:
>> > One danger that I don't know how to solve: In trying to reach as many
>> > people as possible you will bombard many of us with multiple e-mails.
>> Undoubtedly, but like many here, I'll end up seeing only one message.
>> > I am subscribed to dev@diversity.a.o, members@, committers@, two PMC
>> > private lists, and the corresponding dev@lists. I'm going to get about
>> 7
>> > copies, and some people are subscribed to a lot more than 2 projects.
>> >
>> As a suggestion, committers@ are direct emails, which should entirely
>> overlap
>> the subset of everyone subscribed to members@ and private@ (therefore
>> including the pmcs@ superset), and those members@ and private@ lists
>> do not add value if the entire committers@ base will be solicited. So
>> let's
>> please not duplicate.
>> Worried someone is filtering their committers@ traffic? Do we want to
>> include other /active/ contributors who are not yet committers? Then
>> it seems the dev@ lists are the most effective way to add people. But
>> it might improve the situation if the initial committers@ appeal does
>> include some text like the following;
>> > This survey seeks the input of any Apache "contributor", even those
>> > who are not committers. We seek your help to extend this invitation
>> > with those who have contributed in some way to the projects you
>> > participate in, or perhaps share with your communities' dev@ or
>> > users@ list.
>> For the message to come from a respected member of the project
>> means that even though people will see multiple copies, these direct
>> appeals will probably encourage more participation, especially by
>> external contributors, but also perhaps by committers.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message