Changes between Version 55 and Version 56 of SiteUpgradeProposal


Ignore:
Timestamp:
Aug 24, 2014 5:02:19 AM (6 weeks ago)
Author:
rjollos
Comment:

More ideas.

Legend:

Unmodified
Added
Removed
Modified
  • SiteUpgradeProposal

    v55 v56  
    5656  * Several tickets should be addressed before this plugin will be ready for production use: #5773, #6140, #6144, #6160, #6348. 
    5757 * 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.  
    58    * Would be cool if the Top50 of the plugin charts are somehow installed (automatically with their latest (stable?) version) on a demo-site for seeing how they look like and for playing and testing with it. That would give the user a chance to see what it actually is and can do before he spend the time with installing. 
     58   * 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". 
     60 * Add site analytics. 
    6061 * Tools to facilitate code reviews, such as the CodeReviewerPlugin. 
    6162 * 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? 
     63  * 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). 
    6264  * Sync to BitBucket and GitHub when plugins are hosted externally: GitHubSyncPlugin, BitbucketSyncPlugin. 
    6365  * Show !ChangeLogs on trac-hacks wiki pages for plugins hosted externally (#7650). 
     
    6668 * BookmarkPlugin 
    6769 * Autowikify all tags: #10197. 
    68  * WikiExtrasPlugin 
     70 * WikiGoodiesPlugin 
    6971 * !HacksManagement 
    70   * Plugins are currently created using the NewHackMacro. This could be transformed into a plugin that allows more extensive hack management features, such as the following: 
     72  * The TracHacksPlugin provides the NewHack page. More extensive hack management features could be added, such as the following: 
    7173   * Delete a hack (particularly useful for cleaning up spam): remove project from SVN, remove wiki page, remove component. 
    7274   * Track unmaintained plugins by contacting authors if there is no activity after a set amount of time. 
     
    7779 * Allow authors to edit their own log messages. 
    7880 * The NewHack template '''Recent Changes''' heading should link to the revision log (e.g. ContextMenuPlugin#RecentChanges). 
    79  * 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''. 
    80  * RepoSearchPlugin was previously enabled, as described on the TracHacks page, and is a feature we'll want to keep in mind for the future. 
     81 * ~~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. 
     82 * 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. 
    8183 * 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. 
    8284 * Move all users wiki pages to `wiki/users/` or `wiki/TracUsers`, in order to keep the TitleIndex more organized and hierarchical. 
     85 
     86[[TicketQuery(component=TracHacks,status!=closed,format=table)]]