Requests for comment/Indic Sysop
The following request for comments is closed. This proposal failed to gain enough support or interest to be enacted, and has been inactive for several years. Snowolf How can I help? 20:07, 17 June 2013 (UTC)[reply]
This is a proposal for a new global sysop group called Indic Sysop and I would like to hear from others on the subject. Kindly spend a few minutes and provide your thoughts and vote on the talk page.
Contents
What is an Indic Sysop?
editA sysop group similar to Global Sysops, but limited to Indic language Wikimedia projects. This should have an opt-in wikiset where Indic wikis can opt in or out. This should give willing Indic language sysops to help smaller and Inactive Indic language wikis of other languages that they can read/write. This should also have its own mailing lists and policies. We can model this on Global Sysops. Meta-Wiki should act as the central command for this as well. Like a steward bit, this should not be a permanent bit that stays on. It should be reviewed every year and reconfirmed to stay as an Indic Sysop
Why do we need them?
editWe have 40 odd languages and 60+ wikimedia projects in the Indic language space with another 20 in incubator as per the first community newsletter. Some of the Indian wikis are moderately active, some are almost inactive and some are locked due to inactivity. Unlike in other parts of the world, many Indic language sysops are multilingual within the indic language group. If they are willing to help other Indic projects and they would like to see the other projects progressing, they can opt to become the Indic Sysop. Currently, GS folks does not really put their hand much in Indic wikis - may be due to the non-latin script and language barriers. There has been some requests in the recent past across Indic wikipedias to help implementing typing tools and such, which really needs an active local admin to help. Unfortunately, it is not easy to find a local admin in many Indic wikis. It may be a good idea to create a pool of sysops to deal across Indic languages only and this may help in re-activating many inactive projects.
Who can become an Indic Sysop?
editAn existing Indic wiki admin with at least six months of admin experience on an Indic language wikimedia project and who passes the voting on meta with atleast 25 votes and 75% votes in favor can become an Indic Sysop. Candidate should preferably be able to read/write multiple languages in the Indic language group. Technical Specialists and counter vandalism folks can live without being much of multi-lingual. One should be a currently active editor and admin on his or her home wiki and should show atleast some crosswiki activism in Indic language wikis. They should have atleast some admin actions and atleast 100 edits in the past 30 days on their home wiki or across Indic language wikis.
Removal of access
editThe bit should be reviewed and re-voted once a year and inactive members and members without enough support should be removed from the group. A user with 10 or less admin actions across Indic wiki set (excluding their home wik)i and less than 100 edits across Indic wikis shall be considered as Inactive. Any misuse of the bit can be reported to Stewards and stewards can remove the bit on validation of the claim.
Permissions
editHere is the list of permissions from Global Sysops:
- Block
- Block or unblock a user from sending email (blockemail)
- Block or unblock other users from editing (block)
- Bypass IP blocks, auto-blocks and range blocks (ipblock-exempt)
- ⧼Right-proxyunbannable/{{{1}}}⧽ (proxyunbannable)
- Delete
- Delete pages (delete)
- Mass delete pages (nuke)
- Not create redirects from source pages when moving pages (suppressredirect)
- Search deleted pages (browsearchive)
- Undelete a page (undelete)
- View deleted history entries, without their associated text (deletedhistory)
- Delete and undelete specific revisions of pages (deleterevision)
- Protect/Edit
- Change protection settings and edit cascade-protected pages (protect)
- ⧼Right-editusercssjs/{{{1}}}⧽ (editusercssjs)
- Not be affected by IP-based rate limits (autoconfirmed)
- Edit the user interface (editinterface)
- Create or modify abuse filters (abusefilter-modify)
- View detailed abuse log entries (abusefilter-log-detail)
- Miscellaneous
- Have one's own edits automatically marked as patrolled (autopatrol)
- Not be affected by rate limits (noratelimit)
- Import pages from other wikis (import)
- Mark others' edits as patrolled (patrol)
- Mark rolled-back edits as bot edits (markbotedits)
- Move files (movefile)
- Move pages (move)
- Move pages with their subpages (move-subpages)
- Move root user pages (move-rootuserpages)
- Override files on the shared media repository locally (reupload-shared)
- Override the spoofing checks (override-antispoof)
- Override the disallowed titles or usernames list (tboverride)
- Overwrite existing files (reupload)
- Perform CAPTCHA-triggering actions without having to go through the CAPTCHA (skipcaptcha)
- Quickly rollback the edits of the last user who edited a particular page (rollback)
- Upload files (upload)
- Use higher limits in API queries (apihighlimits)
- View a list of unwatched pages (unwatchedpages)