Changes between Version 57 and Version 58 of SiteUpgradeProposal


Ignore:
Timestamp:
Aug 24, 2014, 8:42:55 AM (3 months ago)
Author:
rjollos
Comment:

Indicate some related tickets.

Legend:

Unmodified
Added
Removed
Modified
  • SiteUpgradeProposal

    v57 v58  
    5555 * Hosting a pastebin using the TracPastePlugin ([https://groups.google.com/forum/?fromgroups#!topic/trac-dev/cOn7IjJSd7o mailing list discussion]).
    5656  * Several tickets should be addressed before this plugin will be ready for production use: #5773, #6140, #6144, #6160, #6348.
    57  * Expanded support for creating polls and voting on projects and tickets (#6471). t.e.o uses the VotePlugin, so it is probably pretty stable. FiveStarVotePlugin is another that we could consider using. The PollMacro is currently installed on t.h.o, and EasyPollMacro appears to build on it and add more functionality.
     57 * Expanded support for creating polls and voting on projects and tickets (#6471). t.e.o uses the VotePlugin (#8717), so it is probably pretty stable. FiveStarVotePlugin is another that we could consider using. The PollMacro is currently installed on t.h.o, and EasyPollMacro appears to build on it and add more functionality.
    5858   * It would be cool if the Top 50 plugins are somehow installed (automatically with their latest [stable?] version) on a demo-site for seeing how they look like and for playing with and testing. That would give the user a chance to evaluate the functionality before spending the time with installing.
    5959     * Is there a way to show a download/svn-update/checkout statistics counter for each plugin? This would also be something like a "judge".
    6060 * Add site analytics.
    6161 * Tools to facilitate code reviews, such as the CodeReviewerPlugin.
    62  * Support for Git and Hg 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?
     62 * 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?
    6363  * 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).
    6464  * Sync to BitBucket and GitHub when plugins are hosted externally: GitHubSyncPlugin, BitbucketSyncPlugin.
     
    7171 * !HacksManagement
    7272  * The TracHacksPlugin provides the NewHack page. More extensive hack management features could be added, such as the following:
    73    * Delete a hack (particularly useful for cleaning up spam): remove project from SVN, remove wiki page, remove component.
     73   * Delete a hack (particularly useful for cleaning up spam): remove project from SVN, remove wiki page, remove component (#7511).
    7474   * Track unmaintained plugins by contacting authors if there is no activity after a set amount of time.
    7575 * BadLinksPlugin - for cleaning out dead links to externally hosted plugins.
    7676 * Support for development space for t-h.o plugins. (sandinak)
    7777    -  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.
    78  * Mechanism for users to subscribe to notifications of new plugin releases, and for plugin authors to control when new release notifications are sent out.
     78 * 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).
    7979 * Allow authors to edit their own log messages.
    8080 * The NewHack template '''Recent Changes''' heading should link to the revision log (e.g. ContextMenuPlugin#RecentChanges).