We have a case where all options have pros and cons. We are also discussing the possible scenarios for two different sets of participants: committers and non-committers.
To Patricia's earlier points. The only way to avoid spamming people is to email directly to apache.org accounts. This is the solution I feel the most comfortable with, since those email addresses belong to the apache.org domain and the survey could fall under the program notification category in the Can-Spam act. I am actually investigating this. This approach also provides a unique token that would prevent people from filling a survey multiple times. For non-committers, the solution I feel most comfortable with is the open universal token. I think the risk of having people filling multiple surveys is low, and I am willing to take on the cons there. >From all the options, the risks of the current proposal is the less costly and less risky. I also haven't hear from legal-discuss on the gift card side, so it looks like we won't have an incentive program for the survey. If this is combines with a general email to committers@, we are basically setting ourselves up for lower and lower response rate. Craig, could you outline your questions or aspects you would like the doc to clarify? On Thu, Nov 21, 2019, 8:05 PM Patricia Shanahan <[email protected]> wrote: > > > On 11/21/2019 7:39 PM, Craig Russell wrote: > > Hi Georg, > > > >> On Nov 21, 2019, at 7:33 PM, Georg Link <[email protected]> wrote: > >> > >>> 3. We should disallow multiple responses from the same individual to > the survey. This might involve assigning an immutable ID to each person who > receives or requests a survey. > >> > >> Tricky. If we share one link on social media, then everyone using that > same link expects to take the survey. We cannot prevent anyone from taking > the survey again. I do not like to add a separate step of requesting to > participate and then us manually sending out personalized invites. > > > > I thought that this would be the trickiest part. > > > > I thought that it might be possible to send an individual invitation to > each person that we either know of (email address from our committer base) > or who requests a survey for their specific email address (non-committer > contributor) and we could then send an immutable survey ID. > > I have several e-mail addresses, and could create a lot more if I wanted > to. A human might get suspicious of a lot of survey requests from domain > patriciashanahan.com, but would your scripts? > > > Is there any other way to discourage if not eliminate multiple responses? > > Just ask people to only respond once. >
