THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Hi Apache Software Foundation Community,
This document outlines the selected process to launch the Community Survey 2020.
Selected Distribution Process
The 2020 ASF Community Survey is intended to be completed by committers, contributors, and users of any Apache Software Foundation project. We decided to distribute it using the following criteria:
- Committers - We'll submit a personalized email to each apache.org email address with a unique link to take the survey. The responses will be 100% anonymized, unless the individual specifically shares their contact information and gives permission to further contacts to continue the research.
- Contributors and Users - We'll ask PMCs to directly invite their contributors and users to take the survey by sending notes to their mailing lists. The invite will have a universal link everyone could use to take the survey. All records will be anonymized.
Below is a description of the software selected for the survey, as well as the Privacy Policy followed.
Technology Selected
We selected LimeSurvey as the platform to execute the 2020 ASF Community Survey. LimeSurvey is "the worldwide leading open source survey software" (Licensed: GPL v2 or later). We further selected LimeSurvey GmbH as the SaaS provider. Due to the provider being German, the data protection Terms of Service are excellent and follow BDSG, TKG, and GDPR. (See https://www.limesurvey.org/policies/terms-conditions, Section 10: Data Protection). As is typical of the strong German data protection laws, the privacy policy is excellent as well: https://www.limesurvey.org/policies/privacy-policy
LimeSurvey is an open source project which is over 15 years old (though admittedly there was a complete re-write in 2012). Here is their bug tracker: https://www.limesurvey.org/community/bug-tracker LimeSurvey currently has 1.3k stars on github: https://github.com/LimeSurvey/LimeSurvey. There are no currently published security advisories on the project. The list of security vulnerabilities can be found here: https://www.cvedetails.com/vulnerability-list/vendor_id-6900/Limesurvey.html The known vulnerabilities are apparently all addressed in the most recent release of the software.
(Myrle Krantz's contribution)
Launch Schedule
- Blogpost on survey published (Target date: December 4, 2019)
- Survey Launch to Committers (Target date: December 4, 2019)
- Send an ask to pmcs@apache.org to promote in their comms channels (Target date: December 4, 2019)
- Publish social media messages (Target date: December 4, 2019)
- Send reminders to individuals (Target date: December 11, 2019 AND December 27, 2019)
Privacy Policy
For this survey, we followed the ASF privacy policy.
In order to be GDPR compliant, we will only contact apache.org email addresses, which implies that their users have given ASF permission to use it for contacting them on topics related to ASF. Further, we will announce that this survey will take place in a blog post and participation is opt-in only.
FAQs
Will there be a message to committer@ explaining that they will receive a subsequent message?
Yes, we will add a sentence in the first email saying that we will send one reminder to take the survey if they haven't two weeks after the first invite.
What is the content of the message to developers soliciting their participation in the survey?
See full comms plan here (1)
Initial invite
Hi {FIRSTNAME},
The ASF is contacting you because we need your participation in the 2020 ASF Community Survey. This is important because it will provide us with scientific information about our community, and shed light on how we can collaborate better and become more diverse. Please take 15 minutes to fill out the 2020 ASF Community Survey.
{SURVEYURL}
This is your unique link [1], please don’t share it with anyone. All responses will be aggregated and anonymized. You can find information about privacy on the survey’s Confluence page [2] and read more about it in its blogpost [3].
The last survey of this kind was implemented in 2016, which means that our existing data about Apache communities is outdated. The 2020 ASF Community Survey is looking to gather scientific data that allows us to understand our community better, both in its demographic composition, and also in collaboration styles and preferences. We want to find areas where we can continue to do great work, and others where we need to provide more support so that our projects can keep growing healthy and diverse.
The deadline to complete the survey is January 4th, 2020. We will send 2 more reminders before the date.
Kindly,
Griselda Cuevas
V.P. of Diversity and Inclusion
The Apache Software Foundation
[1] {SURVEYURL}
[2] https://cwiki.apache.org/confluence/display/EDI/The+2020+ASF+Community+Survey+-+Launch+Plan
[3] [Link to blog]
PS: We will send another email to remind people to take the survey in two weeks, only people who haven’t taken the survey will receive it. If you do not want to participate in this survey and don't want to receive any more reminders please click the following link:
{OPTOUTURL}
Launch Blogpost (Published in the apache.org blogpost and the D&I newly created blog)
Blog --TITLE: Launch of the 2020 ASF Community Survey
This week, we are excited to launch the 2020 ASF Community Survey, with which we will gather scientific data that allows us to understand our community better, both in its demographic composition, and also in collaboration styles and preferences. We want to find areas where we can continue to do great work and others where we need to provide more support so that our projects can keep growing healthy and diverse. This joint effort was long overdue: our last survey of this kind was implemented in 2016 [1], which means that all the information we currently have about our communities is outdated.
For this new version of the survey, we have hired Bitergia to design it, a company expert in analysing open source communities and other types of software development teams. They have experience in this type of surveys and research in open source communities. Among other studies, their previous work includes an analysis in gender diversity in technical contributions for OpenStack [2]. The 2020 ASF Community Survey is the first part of a two-stage research. The second part consists of interviews with people who have contributed to the ASF, in order to assess their experience. We’ll share more on this second part of the project soon.
This survey and research are part of the ASF efforts to build a more equitable, inclusive and diverse community. They are run by the Vice Presidency of Diversity and Inclusion, a team formed last May. We’ll share a broader update about this group in January.
If you have an apache.org email address you will receive an email by Wednesday, Dec 4 at noon PST, with a link to the survey. Please take 15 minutes to complete it. If you didn’t receive the email or you do not have an apache.org email address, please use this link to complete the survey:
https://communitysurvey.limequery.org/454363
We are looking to hear from everyone in our community: from users and contributors, to committers and PMCs. Everyone’s voice matters.
Find more information about the 2020 ASF Community Survey on its page on Confluence, including the privacy policy governing this initiative. If you are part of our community, either as a user, contributor, or both, your participation is paramount to the success of this project! Please consider filling out the survey, and share this blog on social media, send it to your fellow Apache contributors. As individuals form the Apache community, your opinion matters: we need to hear your voice.
Links
[1] https://cwiki.apache.org/confluence/display/COMDEV/ASF+Committer+Diversity+Survey+-+2016
[2] https://blog.bitergia.com/tag/openstack/
Who will be the from: address on the message?
Griselda Cuevas <gris@apache.org>
Lime Survey will be configured to send emails via Apache's SMTP server.
Will there be a personalized link to the survey?
Yes, each individual receiving the invite directly from Lime Survey will have a unique link that could be used only once. This doesn't compromise anonymity when taking the survey, since we are not correlating answers to unique links.
Having a unique link helps provide opt-outs from reminders.
How will non-Apache-id holders be able to request a survey?
We will reach non-committers via three channels: Blogposts in the official apache.org blog and the D&I blog, social media snippets and email shared to PMCs and PPMCs to share through their user and dev lists. These messages will contain a universal link to the survey and anyone who has that link could fill it.
See comms plan for full messaging (1)
What will be done with the results?
The results will be analyzed by Bitergia, and will be used to inform the design of the contributor experience interviews. We'll publish a plan for these interviews two weeks after the survey launches.
Bitergia will also produce a report with aggregated results, similar to what we posted about the 2016 Survey ran by ComDev (2)
Does this process conform to GDPR requirements?
Yes. In order to be GDPR compliant, we will only contact apache.org email addresses, which implies that their users have given ASF permission to use it for contacting them on topics related to ASF. Further, we will announce that this survey will take place in a blog post and participation is opt-in only.