Recommendations to publish Product updates
Open, LowPublic


At T124288: Communication channels between communities and teams involved in the product development process we have discussed where to post calls for feedback at the main checkpoints of the life of a software product. That process is too heavy for posting more regular updates looking for awareness and more casual feedback.

Currently different WMF Product teams organize these updates in different ways. It would be useful to have a default recommendation that teams could adapt to the specific characteristics of their projects.

Questions that this guideline would answer:

  • When is it worth to post updates? (vs regular activity in Phabricator and their notifications)
  • When i18n and translations need to be taken into account? (when "always" is probably met with translators fatigue)
  • What is the preferred format for updates in the project page?
  • When to use also an additional wiki page (in another wiki), a specialized mailing list, wikitech-l, Tech News, the Wikimedia Blog...?

There are existing pages related to this topic -- see

Qgil created this task.Jun 6 2016, 8:00 AM
Restricted Application added subscribers: Zppix, Aklapper. · View Herald TranscriptJun 6 2016, 8:00 AM
debt added a subscriber: debt.Jun 6 2016, 4:06 PM
Qgil updated the task description. (Show Details)Jun 7 2016, 1:32 PM
Qgil added a comment.EditedSep 28 2016, 7:49 AM
This comment has been deleted.
Qgil added a subscriber: Keegan.Oct 4 2016, 1:24 PM

@Keegan you are the natural owner for this task. Do you want to take it?

Keegan added a comment.Oct 4 2016, 5:22 PM

@Keegan you are the natural owner for this task. Do you want to take it?

Sure. I think it might be interesting to see if some of these points are resolved in the review of the Technical Collaboration Guideline and clarifying current information instead of writing a more detailed section.

Keegan claimed this task.Oct 4 2016, 5:22 PM