Page MenuHomeMiraheze

Configurations for Picturepedia
Closed, DeclinedPublic

Description

Hello,

I have a lot of configuration requests for my wiki here. Sorry that the list is so long!


  • Extensions:

  • Userrights configuration changes:
    • Please create a brand-new user group called "owner"
        • Please revoke the following permissions from whatever groups they are assigned to by default and grant them only to the "owner" group:
          • abusefilter-modify
          • abusefilter-modify-restricted
          • abusefilter-revert
          • approverevisions
          • protectsite
          • delete
          • undelete
          • deletelogentry
          • deleterevision
          • block
          • unblock
          • unblockself
          • blockemail
          • globalblock-whitelist
          • protect
          • unprotect
          • editprotected
          • rollback
      • Please revoke the following permissions from their default groups and assign them to bureaucrats only:
        • nuke
        • markbotedits
        • mergehistory
        • tboverride
        • override-antispoof

  • Miscellaneous configuration:
    • Please completely delete the "rollbacker" user group
    • Please completely delete the "autopatrolled" user group and assign the autopatrol userright to everyone - I don't want to deal with patrolling pages
    • Please make it so that only the "owner" group can access Special:UserRights


Again, I apologize for the extremely long list.

Thank you for your time,
Trevor

Event Timeline

Trevor created this object in space S1 Public.
Trevor created this object with edit policy "Trevor (Trevor Davis)".
Trevor updated the task description. (Show Details)
Trevor added a subscriber: labster.

I'm currently handling the userrights configuration.

I have only completely transferred the abusefilter related rights and protectsite to the owner group, the rest of the rights are still assigned to the sysop group (to which the ordinarily belong) as well as to the owner group. This is because having only owner able to delete, but the bureaucrat group having nuke, doesn't quite work out (this is only one example however). Simply put, transferring all of these rights to owner only leaves a few inconsistencies. If there are rights/actions you need only assigned to owner, let me know, and I can work out exactly how to do it.
I have not assigned approvedrevisions anywhere, because it is not used by anything currently (we can override that when the related extension is installed).

Void mentioned this in Unknown Object (Diffusion Commit).Feb 13 2017, 21:04
This comment was removed by Trevor.

Scratch that.

Instead, please configure userrights so that all actions related to protection, editing protected pages and blocking are restricted only to owner. However, all actions related to deletion can be assigned to bureaucrats. Please revoke any rights related to deletion from sysop and assign all of them to bureaucrat.

Oh, I forgot something. Please also create a new protection level that only allows the "owner" group to edit a page protected with that level.

Would you also like editusercss, edituserjs, and editinterface assigned to owner as well?
Answered on IRC

NDKilla mentioned this in Unknown Object (Diffusion Commit).Feb 13 2017, 22:21

Almost.

  • I need a steward and/or sysadmin to add me to the "owner" group
  • globalblock-whitelist needs to be revoked from sysops
  • I didn't want the deletion rights being assigned to both owner and bureaucrat - just crats
  • browsearchive needs to be added to bureaucrats (but not owner)
  • If possible, I would like to merge the userrights of the "check user" and "oversight" groups into the "steward" group. I know that I don't have access to any of these three groups, but I only want one user group with restricted rights, not three.
Void mentioned this in Unknown Object (Diffusion Commit).Feb 13 2017, 22:50

Handled the userrights except for editing the checkuser and oversight groups.

@Void Is merging the checkuser and oversight permissions into the steward group, and then deleting the two groups possible technically?

Certainly. I'm just not doing it without approval from the sysadmins.

Reception123 mentioned this in Unknown Object (Diffusion Commit).Feb 14 2017, 08:00

@Reception123 @NDKilla @John am I approved to merge the userrights of the "checkuser" and "oversight" groups into the "steward" group and then delete the other two groups?

Void claimed this task.

I think we're done here.