The following resources contain information and ideas about how to coordinate doc tasks and enable contributions across the community. They also contain a TON of other info. To keep this project in scope, do not get distracted by all the content in these resources that is about what our docs lack, or what developers want from the docs themselves. Focus on these questions:
- What strategies or tools have people tried, considered or suggested to enable contributors to find and navigate doc tasks?
- What strategies or tools have people tried, considered or suggested to coordinate and prioritize doc tasks?
- What are the barriers to contributing doc improvements?
- What tools or strategies reduce those barriers?
To review:
- Wikimedia technical conference 2019 docs session notes and summary: T234634
- Google doc summarizing WMF and WMDE staff feedback in initial investigations preceding dev portal project
- Developer satisfaction survey 2020
- Developer satisfaction survey 2021
- Friends of the Docs and Doc Working Group meeting notes
- Analysis of our docs from a past Outreachy project:
- https://etherpad.wikimedia.org/p/Developers_and_MediaWiki session notes 2017
- Toolforge 2 annual surveys 2015
- review the questions ppl asked at Docs Q&A at 2021 hackathon
- Developer wishlist 2017 item around Documentation special interest group: T156301
- https://www.mediawiki.org/wiki/User:Xephyr826/Recruiting_Technical_Writers
- https://www.mediawiki.org/wiki/User:Waldyrious/Docs (only review the content on this page, any links that are still relevant are included as items in the following list)
- currently-abandoned process for using phabricator for doc tasks and prioritization: https://www.mediawiki.org/wiki/Documentation/Technical_documentation_prioritization
- a thread with many good ideas to consider and extract, i.e. T149372#2834421
- answers about documentation under "Questions for Newcomers" from 2017 hackathon: https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2017/Lessons_Learned#Questions_for_Newcomers
- Another previous iteration of a "how can we do tech docs" project
- https://www.mediawiki.org/wiki/Technical_Documentation_Tasks_for_Hack-a-thons
- https://www.mediawiki.org/wiki/MediaWiki_Documentation_Day_2017
- https://www.mediawiki.org/wiki/Write_the_Docs_San_Francisco_Meetup_May_2017
- Cloud services annual surveys(restricted link) (Note that these surveys are usually more representative of staff developer opinions than community developers; their response rates are historically higher in the Toolforge surveys. So, just skim these.)
- Hackathon 2022 doc discussion notes: https://www.mediawiki.org/wiki/Documentation/Technical_documentation_community_and_outreach_programs/Hackathon_2022_docs_discussions
- KR1 strategy: "collections" (restricted Google doc)
- KR1 review process and template for accuracy criteria https://www.mediawiki.org/wiki/Documentation/Review_template
- Outputs from my review of the Localisation / Localization collection. I can't say I would recommend this as a task-generation process, but there could be good elements in it for collection assessment. But also, I was pretty new to this role when I did this so just keep that in mind ;-)