Would it make sense to add a question about the form of a participant's contribution? (ie, code, marketing, QA, UX, tech docs, logo, organizational, and I know I'm forgetting something important please forgive me) I'd be interested in seeing in numbers how good we are at recognizing non-code contributions with committership.
Best Regards, Myrle On Tue, Oct 2, 2018 at 9:26 PM Christopher <ctubb...@apache.org> wrote: > > Agreed. It should not be significantly longer. Even without being > longer or differently scoped, it occurs to me that an "Annual > Community Survey" may just be better branding and may elicit more > responses. > > I'd be happy to try to help with reviewing and providing feedback on > question wording and survey length. > On Tue, Oct 2, 2018 at 3:09 PM Joan Touzet <woh...@apache.org> wrote: > > > > One problem with such an approach is that by lengthening the survey, you > > end up with more "drop-outs," i.e., people who don't finish the complete > > survey. This means that you have a reduced sample set. I believe the 2016 > > survey didn't count any partial responses, which is typically good > > practice from a quantitative standpoint. > > > > I'm not opposed to a couple of questions, but we shouldn't take what was > > an 8-ish question survey and turn it into a 20-ish question survey. The > > 13% response rate we had would likely be halved, if not worse. > > > > -Joan > > > > ----- Original Message ----- > > > From: "Christopher" <ctubb...@apache.org> > > > To: "ComDev" <dev@community.apache.org> > > > Sent: Tuesday, October 2, 2018 1:52:44 PM > > > Subject: Re: [DISCUSSION] Running another ASF Committer Diversity Survey > > > > > > Would it be possible to widen the survey's scope to a broader > > > "Community Survey", while still retaining the diversity questions as > > > one component, but also including other non-diversity questions > > > pertaining to the ASF community at large? > > > > > > This suggestion comes from some conversations in Montreal, where some > > > of us discussed the desire to have some additional feedback from our > > > community. For example, one question I remember being discussed in > > > particular was something like "If the ASF had more money, what should > > > it do with it?" (possible answers: marketing materials provided to > > > PMCs, hire more INFRA, provide EC2 credits to PMCs or INFRA for CI, > > > publish educational/outreach materials for distribution, other). I'm > > > sure we could come up with additional questions for the non-diversity > > > component to the survey as well. > > > > > > Does broadening the scope of this survey to include diversity and > > > non-diversity components make sense? > > > On Mon, Oct 1, 2018 at 5:30 AM Sharan Foga <sha...@apache.org> wrote: > > > > > > > > Hi All > > > > > > > > It’s been nearly 2 years since we ran our ASF Committer Diversity > > > > Survey so I think it's about time that we looked at running it > > > > again to see if things are changing. For those of you who haven't > > > > seen the details or the results from our 2016 ASF Committer > > > > Diversity Survey then you can find them at the link below: > > > > > > > > https://s.apache.org/lV9h > > > > > > > > Our original 2016 survey was run to: > > > > > > > > - help us get a picture of our existing diversity as all our > > > > committers are linked to all ASF projects, and also; > > > > - to create a baseline measure so we can see if we see if we are > > > > improving or not in our diversity efforts. > > > > > > > > So I think that it would also be good to discuss and review the > > > > survey questions to see if we can improve them or the phrasing to > > > > better capture the data. Also if anyone is interested in helping > > > > out then please let me know. > > > > > > > > Thanks > > > > Sharan > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
