Hi,
On Sun, Mar 12, 2017 at 10:24 AM, Rogol Domedonfors domedonfors@gmail.com wrote:
If there's not going to be anything to implement, how do you see this as having an effect on anything?
Documenting and promoting best practices tends to be useful for the awareness, adoption and refinement of those best practices.
Pine's answer about guidance/policies in Wikimedia is useful, thank you.
What will be done differently or better?
The goal is to have more consistent and predictable communication and decision processes across software projects and communities, allowing for an increase in awareness and involvement by a wider variety of volunteers, and the detection of requests and problems in the early stages of development.
Why should anyone be doing any work on it?
Because the current communication, discussion, and decision processes are not as systematic as we wish, this reduces the quantity and diversity of volunteers engaged, and therefore the quality and efficacy of the collaboration between product development teams and communities.
How will we know whether or not it has been a success, and whther or not the time effort and effort was well-spent?
Good question. I think we can consider the TCG as a useful tool when
* a healthy number of wiki projects want to be early adopters of new features * a healthy number of wiki projects have volunteers facilitating communication as tech ambassadors or translators * product development teams without a community liaison can successfully organize their community engagement activities following best practices * satisfaction levels about community engagement in product development are high * there are no clashes between product development teams and communities
There are other ideas about targets and metrics being discussed at https://phabricator.wikimedia.org/T132499