> -----Original Message----- > My preferred route for functionality like this (and MasterTicket / > Dynamic Report Variables / etc) would be to bless some plugins with > auto inclusion into the trac install (disabled by default). I greatly > value that trac is simple to use. I recently helped teach a Software > Engineering class that made use of trac. I feel that it could not > have been used if it was more toward the bugzilla side of issue > tracking (way too complex for a first go at software management). > That said, part of the project was to estimate and track time (which > is convenient since I wrote the plugin). I am sure that others will > want to have only ticket dependancies and not time tracking, or only > custom reports with a variable filling form. All of these are > essential for the group of users that need them and the system cannot > be complete without them. By blessing and including these plugins > with trac we can keep the simplicity, while easily enabling plugins > that fill out the functionality we need.
I agree with this approach. Keep the Trac codebase small, and just bundle snapshots of some plugins (perhaps determined by community voting once t-h gets moved to 0.11) along with a set of release media. If people want new versions of those plugins, they can upgrade, but this is enough of a stopgap until ... > One thought I have been kicking around is a package management plugin > for trac that would be able download and install a plugin and update > trac from the web admin screen. But this would really need to be > included in Trac (or as a blessed / pre-included plugin) to alleviate > the same frustrations that users are expressing in this thread. With > a package manager and "blessed" plugins, I think that the > disagreements over what functionality should be included by default > can be mitigated to some extent. ... we really fix the problem with a 1-click plugin installer. I have been working on this for quite a while now, and have hit a large number of brick walls. The short version is that we need to fork PyPI (TracPI or something) because I can't get the catalog-sig to acknowledge any patches I send them. This would be a part of the long-fabled trac-hacks++ Alec and I have been discussing over the last year or so. I think this installer will solve the _real_ problem people are having. Its not that lots of plugins are a bad idea, they are just annoying to get working. Put this installer in Trac core, and you get the experience I think everyone wants. --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
