Changes between Initial Version and Version 1 of Ticket #12398, comment 6
- Timestamp:
- Apr 23, 2016, 11:26:00 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12398, comment 6
initial v1 8 8 I'm aiming to get away from the special maintenance status since I can't see the benefit. It's more difficult for users to discover !SpamFilter, and it's one more thing to install. Wouldn't TracMercurial be included in `tracopt` were it not for the license incompatibility? 9 9 10 One of the big negatives I hear from users about Trac is that the installation is difficult to maintain with so many plugins. Of course we can tackle the issues of plugin discoverability and site maintenance in other ways as well. Take for instance Jenkins, which has a really nice built-in page for installing and upgrading plugins with the push of a button. I'm also imagining being able to push-button clonebare installation and be up and running with Trac on Google App Engine, Heroku, !PythonAnywhere; along the lines of what Bitnami provides, but hitting more of the popular application platforms. Now I'm getting off topic.10 One of the big negatives I hear from users about Trac is that the installation is difficult to maintain with so many plugins. We can tackle the issues of plugin discoverability and site maintenance in other ways as well. Take for instance Jenkins, which has a really nice built-in page for installing and upgrading plugins with the push of a button. I'm also imagining being able to push-button clone a bare installation and be up and running with Trac on Google App Engine, Heroku, !PythonAnywhere; along the lines of what Bitnami provides, but hitting more of the popular application platforms. Now I'm getting off topic. 11 11 12 12 One of my goals in the long run, if I manage to find time, is to pull in some of the commonly-used plugins, like the core of !AccountManager. !SpamFilter fits the pattern I have in my mind about the set of plugins that are common to a large number of Trac installations.