Am 07.02.2006 um 13:59 schrieb Christian Boos:
Thomas Tressieres wrote:
My only wish is to have the version control plugin ASAP in the
next official release.
This is something I'm not sure about. TracMercurial has some
obvious licensing
issues that prevents it to be shipped in the next official release,
but besides of
that, I don't think this would have been the case either, as the
other developers
seem to favor a minimalistic approach (only concentrate on the core).
Definitely minimalist here. I don't particularly care about where
plugins are hosted (p.e.c, trac-hacks, separate site), but they
should be in a separate source directory, preferably with a separate
issue tracker etc.
BTW, a good read around this topic is a recent weblog entry by Ben
Goodger on bloat in Firefox:
<http://weblogs.mozillazine.org/ben/archives/009620.html>
Adding more and more bloat to the core product seriously affects
maintainability. Plus, I'd argue it may decrease the chances that
more developers get involved because it gets harder to digest the
code base. Another advantage to keeping subsystems out of the core
product is that it forces (or at least encourages) you to design good
external APIs. When you're putting a feature in the core, you don't
need to care as much about loose coupling.
This approach has some interests, but also some drawbacks:
when we do some refactoring, this will instantly break all the plugins
(that already happened for the 0.9.3 release).
You know that 0.9.3 was an unfortunate exception to the rule, not the
norm. There should -- in general -- be no backwards-incompatible
changes in dot releases. And as soon as we reach 1.x, there should
not even be backwards-incompatible changes in minor releases (1.1, 1.2).
Just putting some "important" plugins in the same repository does not
lessen the burden of maintaining API compatibility. It's a PITA, but
it needs to be done if we really want to encourage the development of
extensions.
Cheers,
Chris
--
Christopher Lenz
cmlenz at gmx.de
http://www.cmlenz.net/
_______________________________________________
Trac-dev mailing list
Trac-dev@lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac-dev
