Last modified: 2014-08-13 21:04:11 UTC
At this time, it appears that even if a user may have these two rights locally, he/she nevertheless requires these in at least one of his/her global groups in order to manage global permissions. This is needless, especially as with Wikimedia the rights changes are all done on Meta.
Thanks for filing the bug. (In reply to comment #0) > with > Wikimedia the rights changes are all done on Meta. To clarify, one would probably want to be able to add configurations that *enforce* this.
(In reply to comment #1) > Thanks for filing the bug. > > (In reply to comment #0) > > with > > Wikimedia the rights changes are all done on Meta. > > To clarify, one would probably want to be able to add configurations that > *enforce* this. As not all rights global group permissions are done on meta, you do not want configurations to enforce something that shouldn't be enforced. While I am automatically cc on these things, I think we would appreciate some notification when you want to change the way the stewards and staff operate. As the premise of this bug is mistaken, I am closing this as invalid.
I'm sorry but that's not the premise of the bug, it's only a possibility which would require a configuration change. The bug is valid, even if Wikimedia decided not to use it.
Note that this was already filed in 2008 as bug 17308 and has only been waiting for a technical implementation. Making the log global seems harder than expected per last comment there, while this seems a rather easy and clean solution.
I don't think it is an issue of logging, per se (that can stay local if needed), but it's an issue about this rather artificial requirement.
Why was this requirement even added? I don't see why it should matter whether it is a local or global right.
Dupe of bug 29435?
(In reply to Kunal Mehta (Legoktm) from comment #7) > Dupe of bug 29435? Actually, yes indeed. *** This bug has been marked as a duplicate of bug 29435 ***
