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. I am subscribed to [email protected], 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.

On 10/28/2019 3:49 PM, Griselda Cuevas wrote:
Hi folks,

I'm back from my leave and ramping up on this project.

First of all, I want to say THANK YOU Katia for stepping in and helping
move the project forward with very little friction. To be a new contributor
to our community you have helped us achieve tremendous progress. Also thank
you Justin for supporting Katia and providing her with advice.

I want to also thank everyone who has contributed with feedback, advice,
revisions and support.

I caught up with Katia and we decided on the following path forward:
1) Draft emails as per Sally's suggestions in this thread
2) Partner with Sally to send final message with survey to members@ &
committers@
3) Promote survey in social media and other channels to capture
non-committer participation (draft from ideas shared in this thread)
4) Run survey for 1 month after initial publication

I will also be following up with the working group and Bitergia to catch up
with the rest of the project.

Cheers,
G

On Mon, 28 Oct 2019 at 14:47, Kenneth Knowles <[email protected]> wrote:

Not sure if there was followup that makes this email obsolete. If so,
apologies.

Both Justin & Shane have proposed ways for the survey to reach a wider
audience than committers@. I think both of their ideas avoid any
unsolicited email. I think expanded reach is very important. For the
survey* results I presented at ApacheCon NA, inclusion of non-committers
was key to many insights.

What do you think of their ideas? Any other ideas?

Kenn

*survey of people at Google who self-identified as using or contributing to
ASF projects



--
This email has been checked for viruses by AVG.
https://www.avg.com

Reply via email to