Changes between Version 86 and Version 87 of SiteUpgradeProposal

Timestamp:

Oct 12, 2017, 9:57:27 AM (7 years ago)

Author:

figaro

Comment:

Further cosmetic changes

SiteUpgradeProposal

@@ -13 +13 @@
   * 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.
-
+  
 == Policies and Guidelines
 
@@ -22 +22 @@
  * User registration, especially [wiki:SiteUpgradeProposal/UserClearance#Validusernames valid usernames] and how to deal with existing accounts, that do not comply to the upcoming standards.
  * Peer review the BugReporting page and add a link to BugReporting on each NewHack template.
+ * More clarification on what constitutes actual support on the functionality of a plugin and an installation issue.
 
 == Enhancements Waiting on Trac Features
@@ -53 +54 @@
  * BadLinksPlugin: for cleaning out dead links to externally hosted plugins.
  * BackLinksMacro: list the wiki pages referring to the current page, which helps in keeping t.h. page referrals consistent.
- * !HacksManagement
-  * The TracHacksPlugin provides the NewHack page. More extensive hack management features could be added, such as the following:
-   * Track unmaintained plugins by contacting authors if there is no activity after a set amount of time.
+ * 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.
  * Support for development space for t-h.o plugins. (sandinak)
-    -  We shouldn't do the work inside our 'deliverable' space ( svn/{plugin}/ } .. be nice to have say /svn/devel/{plugin} .. and we can merge across to our production environments.
- * Mechanism for users to subscribe to notifications of new plugin releases, and for plugin authors to control when new release notifications are sent out (#6476 is related).
+    -  We shouldn't do the work inside our 'deliverable' space (svn/{plugin}/) .. be nice to have say /svn/devel/{plugin} .. and we can merge across to our production environments.
+ * Mechanism for users to subscribe to notifications of new plugin releases, and for authors to control when new release notifications are sent out (#6476 is related).
  * Allow authors to edit their own log messages.
  * RepoSearchPlugin was previously enabled, as described on the TracHacks@43 page, and is a feature we'll want to keep in mind for the future.
- * PyPI Integration: make it easier for authors to publish from the trac-hacks repository to PyPI, allow a PyPI location to be registered via the !NewHack form, promote and encourage links from hack pages to PyPI, documentation for plugin authors/maintainers on how to publish to PyPI.
+ * PyPI Integration: make it easier for authors to publish from the trac-hacks repository to PyPI, allow a PyPI location to be registered via the !NewHack form, promote and encourage links from plugin pages to PyPI, documentation for plugin authors/maintainers on how to publish to PyPI.
  * Automate registering and publishing projects to Transifex.
  * Move all users wiki pages to `wiki/users/` or `wiki/TracUsers`, to keep the TitleIndex more organized and hierarchical.
  * 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 hacks.
+ * Store more information about plugins.
   * Created timestamp
   * Deleted timestamp
   * List of maintainers and contributors
-   * Create a notification subscriber for "hacks that I maintain"
+   * Create a notification subscriber for "plugins that I maintain"
    * This could be used to automatically generate the SVN authz permission policy configuration file.
  * Timeline filter for //Plugins created//
- * Allow users to subscribe to hacks that they use. Add an `IUseThis` macro for listing those hacks on a user page.
+ * Allow users to subscribe to plugins that they use. Add an `IUseThis` macro for listing those plugins on a user page.
  * Create a trac-hacks group on BitBucket, like we've done on [https://github.com/trac-hacks GitHub].
  * GitHub integration