| 1 | = Site Maintenance Procedure |
| 2 | |
| 3 | This page documents site maintenance procedures. It is a work in progress. |
| 4 | |
| 5 | |
| 6 | == Plugin pages |
| 7 | * Plugins hosted outside of trac-hacks.org should have the [tagged:external] tag. |
| 8 | * Many externally hosted plugins have a //Recent Changes// section that can be removed from the page. |
| 9 | * Authors of plugins hosted on GitHub should be invited to join the [github:trac-hacks] organization. |
| 10 | * A stub page should be created for a plugin hosted on GitHub, if the stub page doesn't already exist. |
| 11 | * The `[[Maintainer]]` macro can be used on project wiki pages (e.g. TagsPlugin@78). |
| 12 | * It isn't necessary to specify the owner in the //new ticket// query string. It make maintenance easier if the owner is removed (e.g. TagsPlugin@79). |
| 13 | * Deprecated plugins should have a notice at the top of the page using the `box` WikiProcessor (e.g. TracTagsXmlrpcPlugin@6) |
| 14 | * 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#License for best practices of adding a license. |
| 15 | * 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//. |
| 16 | * 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. |
| 17 | * Source code attached to unmaintained plugins would preferably be checked into the repository. |
| 18 | * Pages for externally hosted plugin that are no longer reachable should be removed after attempting to contact the author and waiting for 30 days. |
| 19 | * TODO: Determine process for removing deprecated and unmaintained plugins. |