= Site Maintenance Procedure

This page documents site maintenance procedures. It is a work in progress.

== Plugin pages

* Plugins hosted outside of trac-hacks.org should have the [tagged:external] tag.
* Many externally hosted plugins have a //Recent Changes// section that can be removed from the page.
* Sporadically a page has a license notice and can in applicable cases be found at the bottom. This needs to be removed and the license should be added as a tag (if not already).
* Authors of plugins hosted on GitHub should be invited to join the [github:trac-hacks] organization.
* A stub page should be created for a plugin hosted on GitHub, if the stub page doesn't already exist. 
* The `[[Maintainer]]` macro can be used on project wiki pages (e.g. TagsPlugin@78).
* It isn't necessary to specify the owner in the //new ticket// query string. It makes maintenance easier if the owner is removed (e.g. TagsPlugin@79).
* Deprecated plugins should have a notice at the top of the page using the `box` WikiProcessor (e.g. TracTagsXmlrpcPlugin@6). The deprecated tag should be added to the page.
* Plugins without a license should be tagged with [tagged:nolicense]. A ticket should be created to request that the author adds a license. The ticket should refer to DevGuide#Licensing for best practices of adding a license.
* Plugins should be tagged with one of the licenses listed on the [/tags?q=realm%3Awiki+license&wiki=on license] page. New licenses can be added to the list by creating a page and tagging it with //license//.
* Each [/tags?q=realm%3Awiki+license&wiki=on license] page should contain a link to the license text on the corresponding [http://opensource.org/ OSI] page.
* Source code attached to unmaintained plugins would preferably be checked into the repository.
* Pages for externally hosted plugin that are no longer reachable should be removed after attempting to contact the author and waiting for 30 days.
* TODO: Determine process for removing deprecated and unmaintained plugins and their associated tickets.
* TODO: Should plugins be tagged with 'plugin' to distinguish them from users? Should macros similarly be tagged as 'macro' or 'plugin' or both? Same for themes?