Talk:Strategy/Wikimedia movement/2018-20/Working Groups/Product & Technology/Recommendations/2

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

So you're doubling down on Flow Structured Discussions?[edit]

What part of "no" do you not understand? MER-C (talk) 15:58, 11 August 2019 (UTC)

And that too amidst an ongoing t/p consultation .... *Sigh* Winged Blades of Godric (talk) 16:04, 11 August 2019 (UTC)
The recommendation is agnostic about how (or where) the discussion platform(s) get implemented. --Tgr (talk) 11:10, 15 August 2019 (UTC)

On Q 3-2 Who specifically will be influenced by this recommendation?[edit]

I'd recommend not using "or maybe some other large chapter" but something more generic, to indicate that any other (fit) entity might have to take this on. Siebrand (talk) 21:16, 11 August 2019 (UTC)

Fair point, thanks. --Tgr (talk) 11:10, 15 August 2019 (UTC)

Community approaches[edit]

I think this recommendation would be improved by starting with community decision making norms (addressed in other recommendations) which can be supported by new and existing tools rather than starting with the tools. I think the issue here is more of a community/social than technical -- there's no magic tool that's going to take the place of collaboration and mutual trust building between Foundation and the communities.

Happily, on the implementation side, the resources for this recommendation probably exist inside the Foundation already in some combination of the product and community engagement departments. I do feel like the Foundation has recently (last couple of years) invested a lot of time and energy using existing channels like mediawiki.org for discussions about specific features as well as outreach on mailing lists and village pumps and have been able to find consensus and make decisions in a distributed and community oriented way. We’ve also looked at a few different platforms over the years (https://www.allourideas.org/, https://www.kialo.com) but neither has gotten a lot of traction on the internet in general.

Another concern about an overly technical focus here. The Foundation’s talk page consultation *strongly* advised the Foundation to make incremental changes and not make wholesale changes to the software itself so any development here should have a strong stakeholder component. Tgr has pointed out that this discussion is independent of implementation and my point is that we've been able to make progress on community decision making without wholesale tool changes. TNegrin (WMF) (talk) 23:10, 2 September 2019 (UTC)

Thanks Toby, good points! We changed the language a bit to be more about the social features we want and less the technical tools commonly used to achieve them. Wrt the risk of disruption, the recommendation had a note on "developing the new platform in parallel to current key discussion spaces so that people can fall back to those in case of problems"; changed that to say work in parallel or incrementally, so it doesn't presuppose whether to use a new or existing space.
Re: the past, I agree the WMF (and especially Product and CE) made great strides in the last few years in managing software consultations, but also I think that an open process for prioritizing between a diverse set of projects with different target audiences, and shaping product strategy, is a far harder problem than getting feedback on already fairly well-formed product plans. This recommendation is not so much a reflection on problems with current product-related community discussions (although I think even there's some room to grow) as an expected dependency of the recommendations on open product governance. --Tgr (talk) 07:27, 6 September 2019 (UTC)
I think we are in agreement :) If you went even further and changed this to "investigate software to support new community decision making structures", it might be a more accurate description of what you are trying to achieve. --TNegrin (WMF) (talk) 14:08, 11 September 2019 (UTC)

From Catalan Salon[edit]

We are worried that every WG asks for dedicated teams for things that doesn't need so much people (...)