Tech:Inactivity policy

This page is a draft

Sysadmins are responsible for making sure that things run smoothly, that there are no issues with servers, and that different requests from users are completed (see System administrators and Tech:Access for details). Activity is important for a sysadmin, whether they are operations or mediawiki-admins and inactivity can provoke security concerns.

Below is a proposed inactivity policy

Main
Ops are responsible for checking who is active and who is not. If a sysadmin knows that they will be inactive for a long period of time (i.e. more than a week) it is recommended that they send an email to staff@undefinedmiraheze.org to notify the other sysadmins of their absence. As long as the user has notified Ops of their inactivity, there is no reason for a removal.

Criteria
If a user has not notified Ops of their leave/inactivity, their activity will be evaluated based on the following criteria.


 * Server access - Have they been regularly accessing servers to perform different tasks, run commands, check logs?


 * Git Hub commits - Have they been actively commiting to any Miraheze GitHub repository?


 * Phabricator - Have they actively been taking part in discussions on Phabricator, leaving comments?


 * IRC - Have they been actively communicating on IRC? (any #miraheze namespace channel)

The criteria is evaluated based on exactly one month from the date it is being made (i.e. if someone evaluates a user on the 1st of Feburary, activity from 1 January to 1 February is taken into account)

The person evaluating the user will make a conclusion based on the factors above, whether the user can be considered "active" or "inactive". Usually (but this is not always the case) two categories in which the user is "inactive" concludes that they are overall inactive.

Removal
After an evaluation is made and the conclusion is that the user is "inactive", a Phabricator task should be created presenting the evaluation. All sysadmins are invited to comment on the task, whether they think the user's sysadmin permissions should be removed or not. If sysadmins express their support, the sysadmin may be removed.

Re-gaining sysadmin permissions
If the user wishes to return a sysadmin, after their period of inactivity, they must open a new access request, and assure Ops that they will be active in the future. Unlike usual access requests, sysadmins who have been removed for inactivity do not require all Ops to comment and express their support, but if one of the Ops members feels like they should not be part of the sysadmin team again, then they may not be re-added.