The following discussion is archived. Please do not modify it. Subsequent comments should be made in a new section.A summary of the conclusions reached follows.
No objections to avoid bureaucratic overhead where it's not required (or similar). –Be..anyone (talk) 02:16, 2 January 2015 (UTC)
An editor had requested comment from other editors for this discussion.
The discussion is now closed, please do not modify it.
New software features — these are often MediaWiki extensions — are installed or enabled at Wikimedia Commons regularly. In the past, the Wikimedia Foundation has enabled extensions on Commons without any request from the Commons community. Examples inlcude Scribunto (aka. Lua), VisualEditor, UploadWizard, Media Viewer, TemplateData and Hovercards. Some of them are well-accepted, others caused slightly more agitation.
On the other hand, members of the Commons community have also requested that extensions be installed for Wikimedia Commons. One example is the translate extension.
What we are striving for with this RfC?
This RfC is aimed to determine how to match the "community consensus" requirement in future for configuration changes. We are curious about your ideas concerning translation and internationalization of our discussions.
Please sign (~~~~) below the subject(s), you support and specify what you like using a few words in up to 5 sentences. Feel invited adding new alternatives if you believe more people would prefer that new option.
Extensions imposing edit restrictions on users
We have separated this option. We believe that before a change that is restricting one user's edit rights is installed, we should discuss how to implement that. Although it usually affects only a small number of users who is willing to run maintenance tasks in these areas, we would like to know your opinion here.