COMMUNITY DATA: Include Community Feedback #35
Conversation
Included comments from Daniel Katz to improve text.
| CONTRIBUTORS: People who contribute to an OS project. Contributions can be code, non code, or both. Contributors can also be users but for the purposes of this survey we’re asking them to evaluate their experience as Contributors. | ||
| - Code contributor - a person who opens a pull request | ||
| - Non-code contributor | ||
| - Organizers of events, meetings, conferences | ||
| - Organizers/speakers for events, meetings, conferences | ||
| - Writing, editing and updating documentation | ||
| - UI or UX Design | ||
| - Operations activities that move forward the goals of a project, such as but not limited to: social media administration, communications administration, fundraising, governance | ||
| - Testing | ||
| - Operations activities that move forward the goals of a project, such as but not limited to: project management, social media administration, communications administration, fundraising, governance |
There was a problem hiding this comment.
I get kind of a duality feeling from reading this which I don't think should be there. At least to me (someone who is known to be a bit too "cuadriculado"), I perceive a first level/split: code vs non-code, then the non-code half has further subdivisions. This leaves me with the impression that code and non-code are equiparable, thus, all non-code contributions together can be compared/comparable to code contributions. I also get the "contributions aren't only code" message and "all contributions are valuable" which imo deserve more emphasis.
An idea to try and emphasize more these last two messages could be to remove mentions to code/non-code and to have a single level bullet point list. The content would be basically the same:
CONTRIBUTORS: People who contribute to an OS project. CONTRIBUTIONS ARE NOT LIMITED TO CODE. Contributors can also be users but for the purposes of this survey we’re asking them to evaluate their experience as Contributors.
- Code contributor - a person who opens a pull request
- Organizers/speakers for events, meetings, conferences
- Writing, editing and updating documentation
- UI or UX Design
- Testing
- Operations activities that move forward the goals of a project, such as but not limited to: project management, social media administration, communications administration, fundraising, governance
There was a problem hiding this comment.
Your suggestion makes sense, thank you for sharing it!
There was a problem hiding this comment.
Oriol - saludos, I hope all is well with you! I was away from Jupyter for a few months, apologies for the delay here. I think this is a great suggestion and feedback. Anavelyz and I worked on this today and have made some changes based on your comments. If you have time to take a look we have requested your review.
| @@ -45,16 +45,17 @@ What can be done with results? | |||
| - Compare year over the year NPS, create dashboard (pending - can we create a dashboard) | |||
|
|
|||
| #### Community: Targeted Respondents | |||
| CONTRIBUTORS: People who contribute to an OS project, this can be code, documentation or both. Contributors can also be users but for the purposes of this survey we’re asking them to evaluate their experience as Contributors. | |||
| CONTRIBUTORS: People who contribute to an OS project. Contributions can be code, non code, or both. Contributors can also be users but for the purposes of this survey we’re asking them to evaluate their experience as Contributors. | |||
There was a problem hiding this comment.
| CONTRIBUTORS: People who contribute to an OS project. Contributions can be code, non code, or both. Contributors can also be users but for the purposes of this survey we’re asking them to evaluate their experience as Contributors. | |
| CONTRIBUTORS: People who contribute to an OS project. CONTRIBUTIONS ARE NOT LIMITED TO CODE. Contributors can also be users but for the purposes of this survey we’re asking them to evaluate their experience as Contributors. |
Updated text to improve the definition of the targeted respondents for this survey. Suggestions incorporated from feedback from Oriol. Deleted duplication of definitions and decided to incorporate them into the section describing who the NPS survey targeted audience is.
Quick update to Include comments from @danielskatz to improve text. Many thanks for your feedback and feel free to add further comments now that a big chunk of time has passed. Also, a shout out to @Anavelyz for helping me to submit this PR.
Closes #34