T44105 Restore normal bureaucrat permissions where changed without consensus (original) (raw)
Restore normal bureaucrat permissions where changed without consensus
- Edit Task
- Edit Related Tasks...
- Create Subtask
- Edit Parent Tasks
- Edit Subtasks
- Merge Duplicates In
- Close As Duplicate
- Edit Related Objects...
- Edit Commits
- Edit Mocks
- Mute Notifications
- Protect as security issue
See URL: on some wikis the permissions given to bureaucrat group have been changed against consensus (by mistake, without it being requested) or no request (with associated consensus) has been found with all due diligence by several users who dug the archives.
On those wikis the default configuration should be restored.
Version: unspecified
Severity: normal
URL: https://meta.wikimedia.org/w/index.php?title=Bureaucrat&oldid=4550727#Removing_access
Related Changes in Gerrit:
Event Timeline
Configuration changes, especially important ones, should be left to the communities pursuant to their policies and global policies. These changes indeed were not made with community agreement and hence should be reverted as Nemo asked.
(In reply to comment #3)
Have the communities (enwiktionary, fiwiki, nowikibooks, ruwikisource,
sewikimedia) been asked whether or not they actually want the bureaucrats to
keep these permission? They at least need to be notified about this first.
Notifications are good (thanks Dereckson). Please open separate bugs for each request to keep the non-default configuration, to reduce mess.
Sewikimedia is completely out of the question here, based on bug 14665.
I re-read the bug entirely and I don't see any request to change bureaucrat config. As it's a chapter wiki, anyway, it will be trivial for the board or president to confirm the need for it with another bug of course.
Also, the shell user considering this request should take into account the bug
creator's ideas
????
(In reply to comment #5)
(In reply to comment #3)
Sewikimedia is completely out of the question here, based on bug 14665.
I re-read the bug entirely and I don't see any request to change bureaucrat
config. As it's a chapter wiki, anyway, it will be trivial for the board or
president to confirm the need for it with another bug of course.
Okay you're probably right, let's treat it like the others.
Also, the shell user considering this request should take into account the bug
creator's ideas????
Basically I think that because you disagree with any bureaucrats being able to remove sysop/bureaucrat (not just on wikis which don't have consensus for it), this should be taken into consideration before deploying the change.
That's not to say it shouldn't be done, because it probably should (once the communities have been notified and the relevant bugs - bug 13853, bug 14568, bug 14665 commented on).
(In reply to comment #6)
That's not to say it shouldn't be done, because it probably should [...]
(In reply to comment #7)
[ -shell +shellpolicy following en.wiktionary objection ]
Dereckson, please open separate bugs for each wiki if they are able to link proper consensus on the matter.
(In reply to comment #7)
[ -shell +shellpolicy following en.wiktionary objection ]
Dereckson, please open separate bugs for each wiki if they are able to link
proper consensus on the matter.
I beg to differ. Grandfathering should apply here. The correct configuration request workflow didn't impose especially a bug in the past. This is the current best practice, not the older one.
As noted by others, this bug is correct; I split each wiki to its bug as of course we need local consensus URL for such rights to be assigned to user groups.
-shellpolicy +dependencies
(In reply to comment #10)
I split each wiki to its bug as of course we need local consensus URL
I don't see how the latter requires the first. :)
(In reply to comment #11)
(In reply to comment #10)
I split each wiki to its bug as of course we need local consensus URL
I don't see how the latter requires the first. :)
Because we have only one URL field. ;-)
It's way clearer to track this way and how shell requests are usually handled, that's it.
See bug 42459 - someone on the Swedish Wikimedia chapter board says that they want to keep the ability for bureaucrats to remove admins. They didn't mention bureaucrats removing bureaucrats though...
Update: fi.wiki and se.wikimedia told us our will but en.wikt is still waiting for a link; no.books didn't react/bother (they'll have to request it afterwards if they change their mind); ru.source is being notified now because they don't like people talking to them ;) (village pump semiprotected etc.).
No objections from ru.source and no.books, en.wikt held a vote: patch updated.
(In reply to comment #18)
No objections from ru.source and no.books, en.wikt held a vote: patch
updated.
Please raise again the issue on ru.source (especially there: their village pump is active), maybe directly in Russian (we have a lot of Russians users involved in Wikipedia) and no.books.
Or let the situation as it's currently for these two wikis.
And finally, ask se.wikimedia if they want or not to be able to debureaucrat.
[ Bug assigned to change submitter. +shellpolicy ]
(In reply to comment #19)
Please raise again the issue on ru.source (especially there: their village
pump is active), maybe directly in Russian (we have a lot of Russians
users involved in Wikipedia) and no.books.Or let the situation as it's currently for these two wikis.
And finally, ask se.wikimedia if they want or not to be able to debureaucrat.
Has anybody had the time to do this?
[Removed the 'patch-in-gerrit' keyword since the patch was abandoned, changed status from 'ASSIGNED' to 'NEW' due to the lack of an assignee.]
(In reply to comment #19)
Please raise again the issue on ru.source (especially there: their village
pump
is active), maybe directly in Russian (we have a lot of Russians users
involved
in Wikipedia) and no.books.Or let the situation as it's currently for these two wikis.
And finally, ask se.wikimedia if they want or not to be able to debureaucrat.
Has this been done yet?
Also what's going to happen about nowikibooks? Doesn't look like there was any reply...
(In reply to comment #23)
Also what's going to happen about nowikibooks? Doesn't look like there was
any
reply...
There is very little activity on nowikibooks. Dereckson's post of November 2012 is still where he left it, with no replies, and no other human has posted on the community portal since.
Personally, I would just remove the right from nowikibooks. It's clear that they are not going to be needing it for the foreseeable future anyway: the only bureaucrat has not edited since 2007.
Is there a link to the changeset that changed these rights to begin with?
No there isn't. The rights were set up this way when the config files were first checked into Git. That's why we're here...
All dependent bugs have been resolved; is there anything else left to do here?
(In reply to TeleComNasSprVen from comment #27)
All dependent bugs have been resolved; is there anything else left to do
here?
Yes, see comment 24 (rights to be removed from nowikibooks).
Not sure what happened with ruwikisource. Bureaucrats there still have the right to de-bureaucrat others.
I'm inclined to leave sewikimedia alone. They're an active chapter who probably like the ability to add and remove bureaucrat rights on their own wiki without needing to trouble the stewards. I've added Jan Ainali to confirm or deny this.
Thanks for the notice, and yes you are right, we would like to have that ability.
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits