Changes between Version 87 and Version 88 of SiteUpgradeProposal

Timestamp:

May 14, 2020, 6:51:53 PM (4 years ago)

Author:

figaro

Comment:

Cosmetic changes

SiteUpgradeProposal

@@ -7 +7 @@
 There are a number of [/query?status=new&status=assigned&status=reopened&component=TracHacks&order=priority open defects and enhancements]:
 
- * Many [/tags/nolicense?wiki=on plugins don't have a license]. An idea outlined in #11660 is to force the user to either specify a license or accept a default license when creating a NewHack.
- * Deleting and marking spam is tedious. After deleting the spam ticket, comment or edit; we have to navigate to the Monitoring panel on the Admin page and then manually locate the entry in the logs. It would be much easier if the `delete` button also flagged the entry as spam, and there was a delete checkbox on the logs page so that this is a one-step operation.
- * There are a number projects that are no longer maintained, have been supplanted by another project and are just taking up space at this point.
+ * Many [/tags/nolicense?wiki=on plugins don't have a license]. An idea outlined in #11660 is to force the user to either specify a license or accept a default license when creating a [NewHack new plugin].
+ * Deleting and marking spam is tedious. After deleting the spam ticket, comment or edit, administrators have to navigate to the Monitoring panel on the Admin page and then manually locate the entry in the logs. It would be much easier if the `delete` button also flagged the entry as spam, and there was a delete checkbox on the logs page so that this is a one-step operation.
+ * There are a number projects that are no longer maintained, have been supplanted by another project and are just taking up space.
   * We should have a process for removing old projects. Perhaps we should have a policy of reviewing and voting on them, a notification should be placed on the page and then a prescribed waiting period elapsed before eventually deleting them. Obsolete plugins with no license would have even more reason to be deleted (see also #9805).
   * Projects that have no source, often because the links to an external site are dead, are being tagged with [/tags/nosource tag:nosource]. Tickets are being opened to notify authors of pending project deletion, and are being tagged with [/tags/"pending-deletion" tag:pending-deletion].
-  * The Apache Software Foundation moves a project to the Attic when it is no longer maintained. For us, the Attic could be a wiki page prefix and path prefix in the repository (or perhaps the path should be deleted and links to the repository pegged). Ideally the pages in the Attic would be filtered from search results unless explicitly requested. Changing the prefix of the page and repository path wouldn't be required if we just used tags.
+  * The Apache Software Foundation moves a project to the Attic when it is no longer maintained. For us, the Attic could be a wiki page prefix and path prefix in the repository, or perhaps the path should be deleted and links to the repository pegged. Ideally the pages in the Attic would be filtered from search results, unless explicitly requested. Changing the prefix of the page and repository path wouldn't be required if we just used tags.
   
 == Policies and Guidelines
@@ -44 +44 @@
      * Is there a way to show a download/svn-update/checkout statistics counter for each plugin? This would also be something like a "judge".
  * Add site analytics.
- * Tools to facilitate code reviews, such as the CodeReviewerPlugin.
+ * Tools to facilitate code reviews, such as the CodeReviewerPlugin or PeerReviewPlugin.
  * Support for Git and Hg (#9831) in addition to SVN. Is it practical to have live mirrors, do we settle on a single DVCS or do we just give the user a choice of which to work with?
   * Trac supports multiple repositories since Trac 0.12, so we no longer need to have a single repository for all of trac-hacks.org (though having a single repository can be an easy way to checkout all of the plugins at one time).
   * Sync to BitBucket and GitHub when plugins are hosted externally: GitHubSyncPlugin, BitbucketSyncPlugin.
   * Show !ChangeLogs on trac-hacks wiki pages for plugins hosted externally (#7650).
- * Support for translated wiki pages
+ * Support for translated wiki pages.
  * BookmarkPlugin: ability to bookmark each page.
  * WikiGoodiesPlugin: additional wiki formatting and macros.
- * BadLinksPlugin: for cleaning out dead links to externally hosted plugins.
+ * BadLinksPlugin or WantedPagesMacro: for cleaning out dead links to externally hosted plugins.
+ * AllAttachmentsMacro: list all attachments for housekeeping purposes. 
  * BackLinksMacro: list the wiki pages referring to the current page, which helps in keeping t.h. page referrals consistent.
  * The TracHacksPlugin provides the NewHack page. More management features could be added, such as contacting authors of unmaintained plugins when there is no activity after a set amount of time.
@@ -65 +66 @@
  * Authentication through external providers such as GitHub and BitBucket.
  * Improve search functionality: the search functionality is currently rudimentary and requires an update to allow for more granular search, such as within attachments.
- * Store more information about plugins.
+ * Store more information about plugins, such as:
   * Created timestamp
   * Deleted timestamp