There has not been consensus regarding this recommendation but we would like to discuss it with the rest of the WGs
Make governance of the software used in Wikimedia projects more inclusive, participatory and predictable by setting up a “Deployment Council” for setting the requirements for deploying new functionality to the wikis, in the form of a co-decision-making process between the organization building the feature and the editor community.
This recommendation aims at unifying the view of what are required and acceptable features between the product and engineering people in various movement bodies with some of the stakeholders such as content contributors. We hope that establishing a trusted council with a mandate would help the cause of a unified view.
Becoming the essential infrastructure of free knowledge will no doubt mean significant changes to the software the wiki communities interact with, and currently deploying major changes is often controversial and stressful, as there is no formal system for editors to set requirements, so they are left to oppose changes they disagree with by informal means; and with no dedicated process, they default to processes used on wikis (like requests for comment) which tend to be poorly suited for the task. While the situation is not completely unmanageable, it does limit the pace of deployment.
To fix this situation, and a new group with a community-given mandate is needed to provide the continuity (product owner organizations need to be secure that basic planning choices won’t be rehashed after millions of donor dollars have already been invested) and high quality of decisions.
The late stage of the product development process will become smoother (being based on the consensus of more stakeholders).
Movement entities doing major product development work (such as the WMF and WMDE; if the recommendation on Decentralization is followed, significantly more in the future), wiki editor communities who are most affected by new products.
Yes, If implemented wrongly, will lead to more frustration from the communities than today, or low-quality decisions.
If a good process isn’t determined the deployment council could potentially slow down deployment by slower decision making. An overly risk-averse council might hold back new features due to small problems within them even though the existing problems they solve might be far bigger.
Involve the communities in the change process; ensure participants are well-informed.
Determining a good process for the council will be crucial for mitigating this risk. A focus on creating and acting on policies with a clear mandate will be important for mitigation.
It adds a new structure around product decision making.
It is complemented by the Open Product Proposal Process recommendation which deals with the other half of the development process.
Good decision making requires constructive and respectful but frank discussions with well-informed participants, thus this recommendation relies on Support Community Decisionmaking and Disseminate Product Knowledge.
It answers the scoping question “Which are the structures and processes to assure the required level of inclusion in decision making and planning of the community at large in their full diversity?”
It suggests changing movement-wide decision-making processes, which is also in the territory of Roles and Responsibilities.