Product teams could use guidance on what information is helpful for communities to include in project updates. These milestones that need communicated offer opportunities for collaboration with communities in review of the work accomplished, and the work ahead.
The outputs for this task will be a set of recommendations for content to include in product or project updates. These recommendations will be included in the Technical Collaboration Guidelines.
| 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 | Trizek-WMF | T112864 Create a newsletter about Collaboration team products | |||
| Resolved | Trizek-WMF | T123538 Rethink the way we communicate with communities concerning Collaboration team work | |||
| Resolved | • Elitre | T139305 Future of the visual editor newsletter | |||
| Resolved | Keegan | T137825 Recommendations for publishing project updates |
First draft of recommendations: https://www.mediawiki.org/wiki/Technical_Collaboration_Guideline/Milestone_communication#Updates