Changes between Version 66 and Version 67 of SiteUpgradeProposal

Timestamp:

Jan 28, 2016, 6:25:07 AM (8 years ago)

Author:

figaro

Comment:

Cosmetic changes

SiteUpgradeProposal

@@ -1 +1 @@
 = Site Upgrade Proposal
+
 {{{#!box info
 Implementation of this proposal is **in progress**.
@@ -11 +12 @@
 
 == Milestone 1 (completed)
+
  * DONE Upgrade server to Debian Squeeze.
  * DONE Subversion: 1.5.1 -> 1.6.18.
@@ -52 +54 @@
 On several occasions questions have come up about proper use of the site and how it should be administered. This suggests we need more site policies, and the philosophy of trac-hacks suggests that these policies be formed by the community.
 
- * !LicensingPolicies page that describes the proper way to document the license for a plugin.
+ * !LicensingPolicies page that describes the proper way to document the license for a plugin, such as DevGuide#Licensing and License/MandatorySignOff.
  * Page that describes proper promotion and what types of external links are allowed, similar to t:TracUsers#guidelines.
- * User registration, especially [wiki:SiteUpgradeProposal/UserClearance#Validusernames valid usernames] and how to deal with existing accounts, that to not comply to the upcoming standards.
+ * 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.
 
@@ -87 +89 @@
  * 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).
  * Allow authors to edit their own log messages.
- * The NewHack template '''Recent Changes''' heading should link to the revision log (e.g. ContextMenuPlugin#RecentChanges).
- * ~~Don't allow ''anonymous'' users to change the state of tickets. Users often accept tickets forgetting they are not logged in, resulting in a ticket being assigned to ''anonymous''.~~ Fixed in the latest workflow.
+ * The NewHack template '''Recent Changes''' heading should link to the revision log, for example ContextMenuPlugin#RecentChanges.
  * 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.
- * Move all users wiki pages to `wiki/users/` or `wiki/TracUsers`, in order to keep the TitleIndex more organized and hierarchical.
+ * 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.
+ * ~~Don't allow ''anonymous'' users to change the state of tickets. Users often accept tickets forgetting they are not logged in, resulting in a ticket being assigned to ''anonymous''.~~ Fixed in the latest workflow.
 
 == Tickets for TracHacks