On 1/31/08, Jani Tiainen <[EMAIL PROTECTED]> wrote: > > Alec Thomas kirjoitti: > > On 29/01/2008, John M Camara <[EMAIL PROTECTED]> wrote: > >> Agreed. Although there could be 2 distributions. One that would be > >> bare bones and another that comes with a number of popular plugins > >> that are maintained with the core. > > > > I think you've hit on the key word here: "maintained". The current > > system allows us to distribute maintenance of extra features out to > > plugin authors, which IMO is a good thing. To bring these into core and > > up to the same level of quality as the rest of Trac, some of the plugins > > would need not-insignificant work (and I speak as an author of several > > such plugins). And then there's the additional ongoing maintenance that > > this would bring. More features, more bugs, more work. All for features > > that may or may not be used by the majority of users. > > > > One option is to have a distribution of Trac maintained by the community > > that includes a bunch of frequently used plugins like AccountManager, > > XmlRpc, etc. That way users can choose to download the featureful > > distribution if they want to go the easy path, or build up their own > > features manually as they do now. This could be a "blessed" distribution > > on t.e.o or maintained on trac-hacks, or whatever. > > > > Question is, who's going to organise and maintain it? > > Very good question... > > I think one problem is that Trac core even it now provides lot of things > is not mature and complete enough to take steps further to direction > proposed here. > > Trac indeed is going to direction like Eclipse IDE - just providing core > platform for project management that can be extended by plugins - since > more or less all parts of Trac are plugins. > > It could be done so that plugin that reaches certain point of popularity > is considered to be taken into core distribution. > > I like way the Apache or PHP is delivered. You get almost all > functionaly you can think of OOTB, most of them are modules that you > need to load (enable) but still it's provided with package. No need to > extra downloads and you can be sure that it works with version you're > playing with.
But the key there is that the Apache core is just as well maintained as the plugins delivered OOTB (there *are* lots of other plugins!). I think the main energy of the Trac project should direct at getting the core stable so that plugin developers actually have a stable core to develop on. If you want distributions with lots of plugins, one of the (obvious) requirements to delivering the same plugins in every release of the 'full blown' version is that all software (not only the core) is available in a timely manner. I think with the current dynamics in the core, plugin authors won't really be able to provide guarantees/promises to that extent. > Like "AccountManager" is one of the plugins I would see like packaged > plugin but not necessarily enabled. > > Maybe someday, maybe... Right. Bye, Erik. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
