Superprotect was introduced by the Wikimedia Foundation to resolve a product development disagreement. We have not used it for resolving a dispute since. Consequently,today we are removing Superprotect from Wikimedia servers.
Without Superprotect, a symbolic point of tension is resolved. However, we still have the underlying problem of disagreement and consequent delays at the product deployment phase. We need to become better software partners, work together towards better products, and ship better features faster. The collaboration between the WMF and the communities depends on mutual trust and constructive criticism. We need to improve Wikimedia mechanisms to build consensus, include more voices, and resolve disputes.
There is a first draft of an updatedProduct Development Process that will guide the work of theWMF Engineering and Product teams. It stresses the need for community feedback throughout the process, but particularly in the early phases of development. More feedback earlier on will allow us to incorporate community-driven improvements and address potential controversy while plans and software are most flexible.
We welcome the feedback of technical and non-technical contributors. Check theQ&A for details.
Quim Gil, Engineering Community Manager @ Wikimedia Foundation
Superprotect was a user right available to Wikimedia wikis and granted to aglobal group of WMF staff members, deployed to stop changes to an executable code. Its main target was administrative pages likeMediaWiki:Common.js, which can be used to modify the user experience of a wiki. At the time of this announcement, Superprotect was not enforced anywhere.
Superprotect wasannounced andenabled in Wikimedia servers on August 10, 2014. It has been used on two occasions:
It is a series of actions that define how software projects should be created in a team or organization. The work of developing software is organized in different stages, and quality criteria are defined to move from stage to the the next. There aremany ways to organize software development.
TheTeam Practices Group is drafting a proposal for aframework for helping us manage our day-to-day work and will operationalize aspects of theProduct Development Process, derived from team organization and agile methodologies in collaboration with stakeholders involved in the product development process. The intended audience of these efforts are the product development teams executing the work.
TheCommunity Liaisons are working onDesign and Development principles to act as an overall guide for WMF Engineering teams. Professional software developers, designers, product managers, etc, are increasingly familiar with the principles of free open source development, but the Wikimedia movement additionally has its own culture of openness, collaboration, and expectations.
The newsoftware product development process in the drafts should make Superprotect unnecessary. Collaboration with Wikimedia communities starting with the early planning stages will give contributors opportunities to shape product direction early. Community feedback and reviews should start well before the deployment phase, in order to identify blockers and other release criteria. Product launch decisions should be based on quality of code and features. Disagreements should be discussed openly and if irregular edits would happen, they should be dealt by the wiki's own administrators using their regular processes, not by a tool controlled exclusively by the WMF, alien to the community processes and administrators.
The Product department has published a new draft product development process for discussion with communities and contributors. The intention of this new process is to provide a clear and accessible expectation of how the Foundation will develop software and how it will partner with users collaboratively in order to do so; removing Superprotect upfront was a logical step.
There is no alternative to Superprotect as a tool controlled by the WMF to protect specific wiki pages, and the WMF is not seeking to build or use a similar tool. Wikimedia projects have processes to protect pages and to revoke administrator's permissions, which are under the control of their own administrators, bureaucrats and the Wikimedia stewards.
The WMF is responsible for providing a consistent user experience across Wikimedia projects, following a public development process that includes community feedback and reviews. Volunteers are responsible for providing feedback and shaping features early in the process, and helping to define success criteria. When a community review is negative, specific and actionable blockers should be identified (open bugs, design flaws, performance criteria) so theproduct owners at the WMF can discuss how to address the issues. Potential moves forward include the acceptance of new release blockers,A/B tests to analyze the impact of the new features, satisfaction surveys to users in order to increase the diversity of feedback, and a commitment to revert the deployment quickly if unexpected problems arise.
#Superprotect is gone was announced in these channels on 2015-11-05:
Since then, the news have spread to other channels:
(Discuss)
--WikiAnika (talk)07:51, 6 November 2015 (UTC)[reply]