Changes between Version 4 and Version 5 of TracHacks/SiteMaintenance

Timestamp:

Aug 25, 2015, 11:47:01 AM (9 years ago)

Author:

figaro

Comment:

Added link to BugReporting. Added rule on nosource.

TracHacks/SiteMaintenance

@@ -2 +2 @@
 
 This page documents site maintenance procedures. It is a work in progress.
+
+See also: BugReporting
 
 == Plugin pages
@@ -7 +9 @@
 * 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).
+* Pages for externally hosted plugin that are no longer reachable should be removed after attempting to contact the author and waiting for 30 days.
 * 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. 
@@ -16 +18 @@
 * 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.
+* 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).
 * 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.
+* Plugins without source code should be tagged with [tagged:nosource]. A ticket should be created to request that the author adds the source code.
 * 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?