On Oct 31, 2006, at 1:10 PM, Sid Wiesner wrote:
> > Matt Good wrote: >> I don't see a reason to "bundle" plugins in the Trac release. Once >> we're using setuptools we can just "require" packages that are >> essential to a base Trac install, but for some reason packaged >> separately. The same bundling ideas have been raised with Genshi, >> though it will be much easier to rely on setuptool's "requires" to >> make >> sure it's installed with Trac. > > Drupal uses a similar architecture as Trac where there is a core and a > set of plugins (they called them modules). One really useful thing > they do is have a base install bundle. There are only a few required > modules in that core (and I believe many of the nonessential ones are > disabled by default), but having the bundled package adds a really > nice feature set right from the start. And it is very easy to enable > the module and get the right mix of desired functionality. > > It would be nice to see a similar thing happen with Trac. Yes, there > are a lot of plugins available, but there are definitely some that are > widely useful and requested. These could be included in the install > package, and possibly disabled by default, but easy to enable and add > functionality. Personally I would rather see the base install come with a plugin manager than a static set of "common" plugins. I started work on this with the HackInstall plugin, but my initial mechanism was too unreliable in too many cases. At some point I would like to see that project restarted, probably using PyPI as a data source. --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 -~----------~----~----~----~------~----~------~--~---
