We need to conduct survey for diversity statistics in Fedora.
Here is the rough draft from @tatica ::
*** Survey : I might like to start kicking a small survey to know how diverse our community is, it's important to me to understand the reach of our contributors, their experiences, needs and culture prior to start any project. Since we might have some people answering it just for fun instead of the right reasons, it could be a good idea to make it only-FAS for now; if at least 30% of the Fedora environment answer it, it would be a success. Here is a list of the things I would like to know, some might go off some might be included:
I'm interested into people knowing that Fedora has an insane cultural background and maybe in a near future, this will open the eyes of those who think that everything in Fedora is plan blue!
We may add one more question as any blockers and motivational factors, if you face/observe any in Fedora.
I've gathered the questions into a wiki page for easier contributions. Please refer to https://fedoraproject.org/wiki/Diversity/Survey
This two pages are our motivational goals:
So, somewhat recently, I stumbled across this giant survey of open source contributors (seems like roughly 2000 people). You can find the questionnaire they used along with the anonymized, raw dataset from responses (for importing into either R or a LimeSurvey instance).
Might be useful for us to refer to later on. :smile:
I expanded on the survey topic and tried to offer justification for it in the FAD page. Proof me and make sure I got the vision right when you have a moment. :grinning:
This has long been one of the founding goals of the Diversity Team, but it's helpful to have some background context. This item has been filed as tickets in the Fedora Council Trac for over two years. See both tickets here.
Discussed during the first ever Fedora Diversity FAD.
To say that this was heavily discussed would be an understatement! As a note, it would be impossible for me to cover the level of detail that we took when discussing elements of the survey during the FAD. But for the benefit of anyone who was not in attendance, I am confidently able to assure that the strategies, questions, and level of thought that have gone into these are significant and have been given great consideration. Here goes!
As a way for us to reference how we did this in the past, the process for how we created the questions is as follows:
This is a very, very short breakdown of what was two days of discussion, debate, and critical thinking / analysis.
The final questions we have along with answer choices will be posted towards the end of the FAD once we finalize the list. I invite @amsharma, @bex, bee2502, @jonatoni, @rhea, @marinaz, and @tatica to add anything else to this ticket comment that I may have overlooked or missed, as far as details for strategy, planning, or other misc. details go.
Discussed during Diversity FAD and 2017-02-07 meeting.
This comment is the "big one" to summarize and pull in everything we discussed in person in Brno. I'll revisit our objectives and goals we wanted to have for the questions as well as post a non-final list of the questions converted from the Etherpad.
The primary objectives we identified for the demographic survey were…
Other questions, comments, and ideas from our raw notes…
We also wanted to identify how the data will be used and clearly communicate how the data will be used (ideally, this outline or information being available for participants in the survey to review).
Below are the "mk. 1" version of the survey questions. Our last plan for these was to submit them to Fedora Legal for feedback, which I believe @bex and @marinaz were going to work on. These questions will also be updated in the Survey wiki page.
Should we use headers / categories for questions, we will want something easier to read for a "production" version of this section.
The following questions can be presented as a table, with the same set of answer options. Questions about diverse perspectives, comfort with contributing ideas, valuing best ideas, and feeling respected were adapted from Red Hat Associate Survey.
Please do not put any identifying information about yourself or others in either text box.
@bex / @marinaz Whenever either of you have a chance to submit these questions to Fedora Legal, it would be great if you could leave an update in the ticket. :smiley: I'm not sure how long it will take for Legal to review these, but it would be helpful to know when they've been submitted for our own planning purposes.
@bex Can you update this ticket about the current situation and also, some timeline till when we can hear back from Legal team? It would help us greatly in planning our tasks for the upcoming year.
Metadata Update from bee2502:
- Issue priority set to: happening now (was: urgent (1-2 weeks))
- Issue tagged with: blocked, needs feedback
Meaningwhile by the time @bex revert on this, can we decide on how we are going to ship this survey to the end users and how we are going to socialize about it. Also testing is something we would like to do before shipping,
AFAIR Bex gonna help us to review the questions, not the platform we are going to use.
Do we know which platform we are planning to use? Can we test that with few questions before we hear back from Bex?
I don't think we are blocked here, we still have actions to do?
For platform, does hosting it on limesurvey or surveymonkey seem appropriate? Limesurvey is open source but Surveymonkey is easier to use and gives some auto generated statistics too.
Personally, I am +1 for Surveymonkey and 0 for Limesurvey.
About promoting the survey, I can think CommBlog and social media channels but this is something I want to leave out for later as the more important part here is identifying the timeline of these posts which we cannot work on till we have updates.
re: testing, What points will we test the survey for? As far as I know, the testing was mainly for not making the survey too long but I think we addressed it well in FAD. If we are testing the platform i.e. surveymonkey vs limesurvey for UX, Diversity team members can look at sample surveys on surveymonkey. The FLOSS 2013 survey was on limesurvey. Surveymonkey definitely doesnt have any platform related bugs and possibly, limesurvey too since both are quite famous worldwide.
I'm +1 for Limesurvey because it's open source. Sorry but I would like avoiding platforms that are not open source, even that it's easier to use them.
to comment on this ticket.
Copyright © 2014-2017 Red Hat
3.3 — Documentation