Please refrain from opening pointless tasks, this phabricator instance is not for testing.

done.

I am fully willing to do this myself. I just am creating this item for the record.

Incompatible with our setup

Default skin set to timeless, to keep mobile friendliness

@MacFan4000 any objections?

If there was a consistent issue where there was abuse being stopped by the abuse filters that needed CU information to look into, I'd do it, but there just hasn't been precedent.

I would like to suggest reconsideration of the abusefilter-private right. Abusefilter now logs private data access. This must be enabled with the $wgAbuseFilterPrivateLog setting and the abusefilter-private-log right is required to view it. I suggest this config option be enabled and both rights be added to the checkuser group.

I support a change of default skin to "Vector", I believe that "Refreshed" is difficult to use due to the absence of some sidebar links such as "Special pages".

Done

I made a mistake in my last PR. Please merge this one quick: https://github.com/Test-Wiki/mediawiki/pull/6

Void resolved it

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.

I have one as well.

I err recently acquired a wikimedia cloak in case you guys need a wikimedia cloaked user for something

All sysadmins get dB access now that we’re on a VPs.

Done

DB access has not been granted

I had to re-fork the repo as well. I forgot that I had put it there. Anyway current one will work fine. Probobly better to use an on-wiki version anyway.

Any idea what happened to the usual logo though? It was originally located at /var/www/html/resources/assets/logo.png

I fixed it. Avatars key need to be reuploaded though. I had to reclone the git repo because of conflicts. When I moved the images folder back to the document root, I forgot to delete the already existent images folder resulting in the images being in /var/www/html/images/images

Functionality now added, you can use either of $log comments or $sal comments, and whatever comments is will be added to the page. (This will take a minute even after the bot responds in the IRC channel.)

Ugh, I was just in the process of launching Void-bot with the added functionality when this issue came up again. I'll have to bypass the need for login, or something.

All I have to do is work the script into the bot and then deploy it. This will take a bit of fiddling, since the file structure where I host the bot is significantly different from where I've been testing it. (And I also need to make sure I can install Pywikibot there properly).

I've gotten far enough that I can do this using a custom pywikibot script. I now just need to make the java bot call the pwb script, modify a text file, and then call another pwb script. Shouldn't take too long now.

There's no real need for adding additional rights. Requesting existing rights should be done on wiki.

The Steward and Checkuser groups grant a user access to highly sensitive data such as IP info. Also it is possible for a user to easily set up these groups himself on a wiki he runs if he is determined enough. Checkuser grants access to a user IP and a log of who got IPs for whoever. This right is restricted on english wikipedia (see: https://en.wikipedia.org/wiki/Wikipedia:CheckUser for more info) but a concession has been made for you to run checkuser on your own IP/username. I suggest that if you want to test checkuser you use that facility. All other rights are simply redundant and the entire wikipedia/test wiki user right structure can be replicated on a wiki you can freely host (I personally run http://testwiki.epizy.com/index.php/Special:ListGroupRights where I have a semi wikipedia style user right structure on a free webhost (I refer to my wiki by way of reference only). It is really easy to replicate any wiki if you put enough time and dedication in it. I also get the feeling that we presently have enough Stewards in comparison to the size of the community. All the stewards have been experienced wikimedians both on wikipedia, this test wiki and a variety of others (Void holds the 2nd highest rank on another test wiki, macfan contributes code patches to mediawiki, mbrt was one of the first users to join and has experience on other test wikis while alvaromolina is a sysop on multiple wikimedia wikis, a steward on a beta network that is essentially a wikipedia replica and actively blocks bad IPs via the use of checkuser). Personally, at this moment we have enough stewards for the community and they have all spent a lot of time on this wiki and in management positions on others. Right now you have spent less time on this wiki and have not shown (much) management experience. I therefore (for now) personally don't think you are experienced enough to make such a big proposal at this time and suggest you wait a while and accumulate management experience before re-proposing.

I've got free time today to do testing. I needed to figure a way to get the python scripts to interact with the java framework, and I believe I have a solution.

@Void What is the status of the switch to pywikibot

You should make a request on the community portal than.

Well, I had requested my self for Steward and Checkuser it would be really nice if u granted me at least one of those. Thanks.

I don’t know that we really need these. Most of those rights, sysops have.

I can't do them myself so any sys admin can please discuss and reach a consensus.

We restricted that do to abuse from a long term vandal.

Sorry but I meant stuff like 'View abuse filters marked as private (abusefilter-view-private)'
which is granted to wikipedia admins. Couldn't we give that to crats at least or is that too powerful?

Those permissions are already included with sysop I belive.

I'm having trouble getting the script to accept the site's cert. It keeps throwing unable to find valid certification path to requested target

@Void Whats the status on this?

Yes that worked and I added Mbrt as an admin as well. :)

Done, and added MacFan4000 as admin (I think)

I'll handle it when in around four hours.

Sound good

I've encountered an unexpected error while attempting to test. I might have the fix done soon, but I can no longer give a good estimate on how long it will take to finish.

I'll get to work on it tomorrow. Should be up and running by the weekend.

sound good :) UTC :)

okay it no problem :)

We have plenty of free space.