I agree with Ryan, Essential plugins i.e. repository back ends, database back ends etc etc should remain with the trac core, you don't want to download trac then go "oh great...I have to download a bunch of plugins to get it working on my particular setup"
Everything else that isn't really anything to do with the initial setup can be put on t.h.o. So +1 move to /plugins top level -1 move to t.h.o ~Rowan On Dec 28, 8:00 pm, Ryan J Ollos <[email protected]> wrote: > Noah Kantrowitz-3 wrote: > > > Does anyone have a good reason to not transfer development of these > > plugins > > to trac-hacks? That seems far more consistent and I see no reason not to > > other than historical stuffs. > > In an ideal world (or sometime in the future), Trac would work with any > repository back-end ... or at least the most popular ones. I think it would > be ideal to have all of the repository plugins that are of sufficiently high > quality included with the Trac distribution. That way, someone could > download just the Trac distribution and immediately get it working with > their repository back-end. Most everything beyond a repository plugin would > seem better suited to t.h.o. > > Just my opinion though ... > > -- > View this message in > context:http://old.nabble.com/-RFC---plugins-toplevel-on-t.e.o-tp26740666p269... > Sent from the Trac Dev mailing list archive at Nabble.com. -- 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.
