Topic on Talk:Technical Collaboration Guidance/Milestone communication

Action items for communities and result evaluation

3
Strainu (talkcontribs)

When a certain change, no matter how minor, requires further actions from the communities (for instance changes in Common.js/Common.css), that change should be communicated on wiki, along with clear expectations of the changes to be made and, if possible, an example.

It would also help if such changes could be evaluated after a while: how many communities did make the change? For the communities that did not make it, what was the blocker? Did they start a discussion following the announcement? Did they work around the new feature to disable it? Are they dependent on a single person who was not available/willing to make the change? On the long run, this should lead to upgrades to this guideline.

AKlapper (WMF) (talkcontribs)

https://meta.wikimedia.org/wiki/Tech/News is on-wiki and might be sufficient? Or do you have recent examples of changes that require further actions from the communities that were not included in Tech News?

Strainu (talkcontribs)

For communities that subscribe to it with the Village Pump, it most likely is. For the rest, I'm not sure, the workflow probably differs from wiki to wiki. Sending a one-time invite for communities to subscribe their village pump would help mitigate this and make the news more relevant.

Reply to "Action items for communities and result evaluation"