Last modified: 2014-06-27 22:15:07 UTC
Original bug title: Remove GWToolset extension from Commons as no community consensus has been provided to install it As far as I remember there was no community consensus to install and enable this extension. If I should be wrong, please correct me, I wasn't around the whole time. The issue is it's too bureaucratic to get pages edited for admins. (i.e. it imposes new user rights and restrictions) See Bug 67209.
I hereby decree that this will never happen.
(In reply to Tomasz W. Kozlowski from comment #1) Why. Prove!
> Remove GWToolset extension from Commons as no community consensus has > been provided to install it What are the actual *material* issues with this extension's deploy? Or is community consensus the one and only argument for this request?
Just supplying links... Here's a list of communication/outreach the GWToolset team did over the years: https://commons.wikimedia.org/wiki/Commons:GLAMwiki_Toolset_Project/Outreach_schedule There aren't many citation links from that page, but it looks like a lot of communication happened in Dec of 2013. And the announcement on the VP when it was enabled: https://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2013/12#GLAMwiki_Toolset
(In reply to Andre Klapper from comment #3) > is community consensus the one and only argument for this request The issue is that I used to be able to edit all pages as admin before and the extension imposed restrictions on that that were not passed by community consensus. I have been elected to help on Commons but I am no longer able to do that in this regard. Of course don't take this bug seriously as GWToolset provides a lot of benefit and removing it would be really worse. But in future things like user rights should be sorted before an extension is installed - meaning that an RfC is due at minimum.
(In reply to Rainer Rillke @commons.wikimedia from comment #5) > Of course don't take this bug seriously as GWToolset provides a lot of > benefit and removing it would be really worse. > But in future things like user rights should be sorted before an extension > is installed - meaning that an RfC is due at minimum. I see this last paragraph as an invitation to help move things forward, can I assume so? :) I'd love to see this solved through a (probably quick/easy) collaboration between the GWToolset devs and the Commons community over what changes wrt user rights are needed. I guess the right place is on Commons and then letting bug 67209 know what the outcome is. Reasonable?
I agree with Rillke, The issue is that I used to be able to edit all pages as admin before and the extension imposed restrictions on that that were not passed by community consensus. I have been elected to help on Commons but I am no longer able to do that in this regard. (defacto i am able to edit because i am a gwt member, but other admins can't fulfill DR's related to GWT namespace)
(In reply to Greg Grossmeier from comment #6) > Reasonable? Yeah, I'm down. (american sense :) However, I am more concerned about future recurrences. How can we enforce RfCs (multilingual preferred) for extensions that are about to change the user rights structure?
(In reply to Rainer Rillke @commons.wikimedia from comment #8) > (In reply to Greg Grossmeier from comment #6) > > Reasonable? > > Yeah, I'm down. (american sense :) However, I am more concerned about future > recurrences. How can we enforce RfCs (multilingual preferred) for extensions > that are about to change the user rights structure? Good question. What do you suggest? I'm all ears and willing to help however I can. We can take this off-bugzilla somewhere if easier (probably).
I suggest that extensions affecting user rights and protection structures must be somehow passed by the community’s formal procedure to gather community consensus. It could be also beneficial (not only for the WMF-"deployer") having a table at, e.g. Meta, listing what the community’s formal procedure actually is and where it is described. Existing resources are https://meta.wikimedia.org/wiki/Requesting_wiki_configuration_changes and https://www.mediawiki.org/wiki/Review_queue
