That is include 'root' group not sysadmin group
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jun 14 2018
May 19 2018
May 18 2018
sometime, I want to edit LS, but I can't save the edit, nah, maybe have a wrong chmod or something else.
LoL, I think this is just for admin, I usually push to the server, :) and I always be there.
May 17 2018
Two questions: Why is this task protected? And why not do it through github?
May 16 2018
Apr 2 2018
Mar 19 2018
Mar 18 2018
Mar 16 2018
Feb 16 2018
Feb 10 2018
@MacFan4000 @Void Fixed on upstream, requires system update and task handling here
Feb 6 2018
Seems like an upstream issue. I've attempted debugging and testing with another version, but it failed there too.
Jan 13 2018
Void resolved it
Jan 12 2018
abusefilter-private gives rights to view the IP of whatever user triggered that filter when viewing an abuse log entry. The intended right may have been abusefilter-view-private (provides ability to view private abuse filters) or abusefilter-log-private (provides ability to view AbuseLog entries of filters marked as private). Either way, anyone with abusefilter-modify (given to sysops) has the ability to view (and modify) all filters (including private).
As such, I've merged the PR; the right does not belong with the oversight toolset.
OS is used by Stewards and we never use it as CheckUser. It find to be able to change private filters. Also that link is not releated.
I added a github PR here.
Jan 7 2018
Jan 6 2018
Jan 4 2018
Dec 25 2017
I have one as well.
Dec 24 2017
I err recently acquired a wikimedia cloak in case you guys need a wikimedia cloaked user for something
Dec 13 2017
Nov 17 2017
All sysadmins get dB access now that we’re on a VPs.