Changes between Version 63 and Version 64 of SiteUpgradeProposal
- Timestamp:
- Aug 8, 2015, 12:20:03 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SiteUpgradeProposal
v63 v64 19 19 20 20 * ~~Upgrade Trac to version 1.0.~~ 21 * ~~Re-enable XmlRpcPlugin.~~ 21 22 * Upgrade plugins to work with Trac 1.0. This work is being tracked in #10193 and #11949. 22 * ~~Re-enable XmlRpcPlugin.~~23 23 24 24 == Milestone 3 … … 30 30 * Upgrade trac-hacks.org to Trac 1.1.x or 1.2 (#12171). 31 31 32 33 32 == Milestone 5 34 33 35 * TODO: define some enhancements for this milestone (e.g. BookmarkPlugin, TracPastePlugin, IrcLogsPlugin, etc ...).34 * TODO: Define some enhancements for this milestone (e.g. BookmarkPlugin, TracPastePlugin, IrcLogsPlugin, etc.). 36 35 37 36 == Open Issues 38 37 39 There are a number of [/query?status=new&status=assigned&status=reopened&component=TracHacks&order=priority open defects and enhancements] that we may want to address during the upgrade . Here are some specific ones that we may want to give higher priority:38 There are a number of [/query?status=new&status=assigned&status=reopened&component=TracHacks&order=priority open defects and enhancements] that we may want to address during the upgrade: 40 39 41 * Many plugins don't have a license. An idea outlined in #9805 is to force the user to either specify a license or accept a default license when creating a NewHack.40 * Many [https://trac-hacks.org/tags/nolicense?wiki=on plugins don't have a license]. An idea outlined in #9805 is to force the user to either specify a license or accept a default license when creating a NewHack. 42 41 * Spam continues to be a problem. Upgrading to the t:SpamFilter might improve the issue, but the captcha from the latest th:SpamFilter plugin as observed on t.e.o can be frustrating experience and we don't want to risk driving away users. 43 42 * A related issue is that many tickets are created by ''anonymous'' and ''anonymous'' often does not follow-up when more information or feedback is requested. We could require users to create an account before they can create a ticket, which might cut down on newticket spam as well as these abandoned tickets. … … 54 53 * !LicensingPolicies page that describes the proper way to document the license for a plugin. 55 54 * 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 standards55 * User registration, especially [wiki:SiteUpgradeProposal/UserClearance#Validusernames valid usernames] and how to deal with existing accounts, that to not comply to the upcoming standards. 57 56 * Peer review the BugReporting page and add a link to BugReporting on each NewHack template. 58 57 … … 74 73 * Support for translated wiki pages 75 74 * `TICKET_EDIT_COMMENT` should be set for correcting typos, at least for own comments (t:#10909 proposes adding a `TICKET_EDIT_OWN_COMMENT` permission). 76 * BookmarkPlugin 75 * BookmarkPlugin: ability to bookmark each page. 76 * WikiGoodiesPlugin: additional wiki formatting and macros. 77 * BadLinksPlugin: for cleaning out dead links to externally hosted plugins. 78 * BackLinksMacro: list the wiki pages referring to the current page, which helps in keeping t.h. page referrals consistent. 77 79 * Autowikify all tags: #10197. 78 * WikiGoodiesPlugin79 80 * !HacksManagement 80 81 * The TracHacksPlugin provides the NewHack page. More extensive hack management features could be added, such as the following: 81 82 * Delete a hack (particularly useful for cleaning up spam): remove project from SVN, remove wiki page, remove component (#7511). 82 83 * Track unmaintained plugins by contacting authors if there is no activity after a set amount of time. 83 * BadLinksPlugin - for cleaning out dead links to externally hosted plugins.84 84 * Support for development space for t-h.o plugins. (sandinak) 85 85 - 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. … … 87 87 * Allow authors to edit their own log messages. 88 88 * The NewHack template '''Recent Changes''' heading should link to the revision log (e.g. ContextMenuPlugin#RecentChanges). 89 * ~~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''.~~ This is implemented in the latest workflow.89 * ~~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. 90 90 * 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. 91 91 * 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 93 * Authentication through external providers such as GitHub and BitBucket. 94 94 95 == Tickets for TracHacks 95 96 96 == Tickets for TracHacks97 97 [[TicketQuery(component=TracHacks,status!=closed,format=table)]] 98 98 99 99 == Tickets for TracHacksPlugin 100 100 101 [[TicketQuery(component=TracHacksPlugin,status!=closed,format=table)]]