Changes between Version 66 and Version 67 of SiteUpgradeProposal
- Timestamp:
- Jan 28, 2016, 6:25:07 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SiteUpgradeProposal
v66 v67 1 1 = Site Upgrade Proposal 2 2 3 {{{#!box info 3 4 Implementation of this proposal is **in progress**. … … 11 12 12 13 == Milestone 1 (completed) 14 13 15 * DONE Upgrade server to Debian Squeeze. 14 16 * 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. 53 55 54 * !LicensingPolicies page that describes the proper way to document the license for a plugin .56 * !LicensingPolicies page that describes the proper way to document the license for a plugin, such as DevGuide#Licensing and License/MandatorySignOff. 55 57 * Page that describes proper promotion and what types of external links are allowed, similar to t:TracUsers#guidelines. 56 * User registration, especially [wiki:SiteUpgradeProposal/UserClearance#Validusernames valid usernames] and how to deal with existing accounts, that to not comply to the upcoming standards.58 * User registration, especially [wiki:SiteUpgradeProposal/UserClearance#Validusernames valid usernames] and how to deal with existing accounts, that do not comply to the upcoming standards. 57 59 * Peer review the BugReporting page and add a link to BugReporting on each NewHack template. 58 60 … … 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). 88 90 * Allow authors to edit their own log messages. 89 * The NewHack template '''Recent Changes''' heading should link to the revision log (e.g. ContextMenuPlugin#RecentChanges). 90 * ~~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. 91 * The NewHack template '''Recent Changes''' heading should link to the revision log, for example ContextMenuPlugin#RecentChanges. 91 92 * 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. 92 93 * 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. 93 * Move all users wiki pages to `wiki/users/` or `wiki/TracUsers`, in orderto keep the TitleIndex more organized and hierarchical.94 * Move all users wiki pages to `wiki/users/` or `wiki/TracUsers`, to keep the TitleIndex more organized and hierarchical. 94 95 * Authentication through external providers such as GitHub and BitBucket. 96 * Improve search functionality: the search functionality is currently rudimentary and requires an update to allow for more granular search, such as within attachments. 97 * ~~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. 95 98 96 99 == Tickets for TracHacks