Gerrit/Inactive projects

Background
This page is about marking code repositories with no recent activity.

'''See T102920 for underlying discussion. Please keep discussion centralized in that task.'''

Definitions
(Possibly) Inactive code repositories are defined by:
 * Premise: no patches have been merged to the repository in at least 180 days (localization updates don't count).
 * POSSIBLY INACTIVE: If there are open changesets submitted without any review or stuck with 0/+1 after 90 days, the repository is labelled POSSIBLY INACTIVE. Ideally, a notification would be sent to the identified maintainers and other contributors to the project.
 * INACTIVE: If there are open changesets submitted without any review or stuck with 0/+1 after 180 days, the repository is labelled INACTIVE.

Actions to mark a repository as (possibly) inactive
Note: Some of these steps might require special permissions. Please file a task in Phabricator if you cannot perform all actions.


 * For POSSIBLY INACTIVE code repositories, try to contact the authors / maintainers (e.g. check the latest changes or a project homepage if existing) and ask about the status of the project (and whether potentially proposed patches in Gerrit will receive a review). Assuming that you receive no answer:
 * For POSSIBLY INACTIVE code repositories, either write a patch to update the CI/Zuul configuration to automatically add an explanatory comment in Gerrit about the repository's status. Or create a Phabricator task in the project #Continuous-Integration-Config to let someone else do it.
 * For INACTIVE code repositories, set "Projects > General > Project Options > State" to "Read Only" in Gerrit. Remove the project from the CI/Zuul configuration. Additionally update the project description and prefix it with "[INACTIVE]".
 * Update the extension/project wiki page of INACTIVE projects to reflect the inactive status of the codebase by applying the mw:Template:Unmaintained extension and adding mw:Category:Unmaintained extensions.
 * Update the Phabricator description of INACTIVE projects to reflect the inactive status of the codebase.
 * For INACTIVE projects, mw:Developers/Maintainers would be updated by removing inactive maintainers.
 * To filter out INACTIVE projects from Wikimedia code review metrics on http://korma.wmflabs.org/, update the file gerrit_trackers_blacklist.conf.
 * Still to be defined if wanted or not (please discuss in T102920): For POSSIBLY INACTIVE and INACTIVE code repositories, it may be appropriate to disable the repository on translatewiki.net. Submit a patch commenting the repository in the file groups/MediaWiki/mediawiki-extensions.txt in the translatewiki Git repository and mention that the repository is not maintained anymore, whether it has i18n issues, how many wikis/users are using it. Or create a Phabricator task in the project #translatewiki.net to let someone else do it.
 * Still to be defined if wanted or not (see discussion in T102920): How is "archived" defined as in mw:Category:Archived extensions?

Actions to mark a repository as active again
Once a request for ownership has been received, the steps above need to be reverted.