Superprotect [1] 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 updated Product Development Process [2] that will guide the work of the WMF Engineering and Product teams.[3] 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 the Q&A for details.[4]
[1] https://meta.wikimedia.org/wiki/Superprotect [2] https://www.mediawiki.org/wiki/WMF_Product_Development_Process [3] https://www.mediawiki.org/wiki/Wikimedia_Engineering [4] https://www.mediawiki.org/wiki/WMF_Product_Development_Process/2015-11-05#Q....
Excellent, many thanks Quim!! On Nov 5, 2015 18:35, "Quim Gil" qgil@wikimedia.org wrote:
Superprotect [1] 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 updated Product Development Process [2] that will guide the work of the WMF Engineering and Product teams.[3] 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 the Q&A for details.[4]
[1] https://meta.wikimedia.org/wiki/Superprotect [2] https://www.mediawiki.org/wiki/WMF_Product_Development_Process [3] https://www.mediawiki.org/wiki/Wikimedia_Engineering [4]
https://www.mediawiki.org/wiki/WMF_Product_Development_Process/2015-11-05#Q....
-- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
I want to thank everyone who has made this possible. Developing software products for a big and unique movement like Wikimedia is a complex task (but no more complex than building free encyclopedias, dictionaries, etc.) I believe that shipping better features faster is one of the most important problems we have to solve as a movement in order to keep Wikimedia relevant in this fast-changing World. I'm looking forward to learning to solve this problem together as community, convinced that the tech-savvy and tech-curious volunteers will play a key role :)
~~~~ Lila
On Thu, Nov 5, 2015 at 9:34 AM, Quim Gil qgil@wikimedia.org wrote:
Superprotect [1] 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 updated Product Development Process [2] that will guide the work of the WMF Engineering and Product teams.[3] 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 the Q&A for details.[4]
[1] https://meta.wikimedia.org/wiki/Superprotect [2] https://www.mediawiki.org/wiki/WMF_Product_Development_Process [3] https://www.mediawiki.org/wiki/Wikimedia_Engineering [4]
https://www.mediawiki.org/wiki/WMF_Product_Development_Process/2015-11-05#Q....
-- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
2015-11-05 18:34 GMT+01:00 Quim Gil qgil@wikimedia.org:
today we are removing Superprotect from Wikimedia servers.
This is great news, thanks!
wikitech-l@lists.wikimedia.org