Recommendations to publish Product updates
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Qgil
	Jun 6 2016, 8:00 AM

Description

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 https://www.mediawiki.org/wiki/Technical_Collaboration_Guideline/Milestone_communication#See_also

Related Objects
Search...

Status	Assigned	Task
Resolved	Keegan	T138339 Create a systematic approach to community engagement for product development teams
Declined	• Elitre	T144625 First review of the Technical Collaboration Guidance by Foundation Product teams and most active technical volunteers
Resolved	• Elitre	T137088 Recommendations to publish Product updates

Event Timeline

Qgil created this task.Jun 6 2016, 8:00 AM

Restricted Application added subscribers: Zppix, Aklapper. · View Herald TranscriptJun 6 2016, 8:00 AM

Qgil mentioned this in T124288: Communication channels between communities and teams involved in the product development process.Jun 6 2016, 8:01 AM

CKoerner_WMF subscribed.Jun 6 2016, 2:20 PM

debt subscribed.Jun 6 2016, 4:06 PM

Qgil added a project: Community-Relations-Support.Jun 7 2016, 1:07 PM

Qgil updated the task description. (Show Details)Jun 7 2016, 1:32 PM

Qgil mentioned this in T137226: Improve discoverability of product updates.Jun 8 2016, 12:21 PM

Keegan moved this task from Backlog to Current on the Technical-Collaboration-Guidance board.Aug 5 2016, 6:21 PM

Keegan mentioned this in T138339: Create a systematic approach to community engagement for product development teams.Aug 5 2016, 6:37 PM

Qgil triaged this task as Low priority.Sep 28 2016, 7:45 AM

Qgil added a subtask: T144625: First review of the Technical Collaboration Guidance by Foundation Product teams and most active technical volunteers.

This comment has been deleted.

Qgil removed a subtask: T144625: First review of the Technical Collaboration Guidance by Foundation Product teams and most active technical volunteers.Sep 28 2016, 7:50 AM

Qgil added a parent task: T144625: First review of the Technical Collaboration Guidance by Foundation Product teams and most active technical volunteers.

https://www.mediawiki.org/wiki/Technical_Collaboration_Guideline/Milestone_communication#Updates exists. We need to check whether the ideas in this task are or should be reflected there, as part of T144625: First review of the Technical Collaboration Guidance by Foundation Product teams and most active technical volunteers.

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

In T137088#2688418, @Qgil wrote:

@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

Qgil moved this task from Backlog to Ready to Go on the Community-Relations-Support (Oct-Dec-2016) board.Oct 4 2016, 7:15 PM

BethNaught subscribed.Dec 4 2016, 5:29 PM