Tracking task for work on recommendations on what information to include in project proposals and updates.
A starting point:
All projects have a wiki page with an overview and a standard infobox containing their basic information: Phabricator links, contact details, subscription, and checkpoints passed / pending. Users can follow the checkpoint links to understand quickly the development status of a project.
Technical Collaboration Guideline/Vision#Project information
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Keegan | T138339 Create a systematic approach to community engagement for product development teams | |||
| Resolved | Qgil | T131915 Technical Collaboration quarterly goals for July - September 2016 | |||
| Resolved | Keegan | T138240 Technical Collaboration Guideline - project information | |||
| Resolved | Keegan | T137826 Recommendations for announcing new project proposals | |||
| Resolved | Keegan | T137825 Recommendations for publishing project updates | |||
| Resolved | Keegan | T120070 Recommendation for projects requesting prioritization or resources | |||
| Resolved | • Elitre | T126952 Integrate Risker's checklist for content-creation extensions to the WMF product development process | |||
| Resolved | • Moushira | T121648 Do a mini research on best practices for product decision making in like-minded movements or platforms |
Update: I've met with some folks from product, will schedule more, and I'm meeting with the community liaisons as well. These discussions are casual for now and notes are not publicly available so to free up people to express themselves.
We're going to need to work through the process of completing the information feedback loop. Currently the loop is unclosed and information feels as though it's being sent into space, hoping to hear something back. This is frustrating for all parties involved.
Another identified issue, and one without a ready solution, is self-imposed limitations for gathering feedback - mailing lists and wikis. The use of this technology is quite practical, but also quite limiting and self-selected.
More to come, my internet is not working well for meetings these few days, but will resume that aspect of the work at the end of the week. Next week I plan on getting some writing down.
@mcruzWMF owns a goal about publishing the Wikimedia Resource Center and that project fully relates to the team and projects information of Product teams. Therefore, I am adding Maria to this task, and @Keegan please coordinate with her to make sure that both projects are in sync.
During our last Technical Collaboration team meeting, the topic of project information spontaneously came was briefly discussed. A summary of opinions:
Looks DONE to me. Marking this task resolved, since it is a quarterly goal and Keegan is on vacation. Thank you!