Hello,
I'd like to clarify the structure of the code repository by moving our
plugins to a dedicated place, instead of the sandbox:
/plugins
/0.10
/WebAdmin
/0.11
/mercurial-plugin
/spam-filter
/0.12
/spam-filter
/multirepos
/mercurial-plugin
The sandbox would then only contain active branches, inactive or dormant
ones could stay in the /sandbox/Attic.
This is by no means an attempt to "take over" the role of trac-hacks, we
don't have the infrastructure nor the will to do so, trac-hacks fulfills
its role perfectly fine, thanks to the constant care of Michael.
The new structure will make it easier to visualize which plugins fits
with which branch, like on t-h. Even if the multirepos branch is nearly
done, I'll start by moving the mercurial plugin below the
/plugins/multirepos folder, as an example of how things should be.
The point of having some plugins here is a matter of commodity. We could
host plugins elsewhere (and I indeed have some in trac-hacks), but
having a few key plugins on t.e.o makes it more practical for a couple
of situations: when there's a change in the interface in trunk or in an
experimental branch that should immediately be reflected in the plugins,
or conversely when changes in the plugin need to be preceded by a change
in the interfaces. The primary example is the mercurial plugin, which
helped the evolution of our versioncontrol API to be more DVCS friendly,
and will continue do so in the future (merge, branch-y log, etc.).
We could also use this as an alternative migration path if a small
plugin from sample-plugins grows, so that it can either become part of
tracopt (when it's an optional feature that just needs to be activated)
or a full-fledge plugins (e.g. if it needs more dependencies).
In the end, we'll have a picture which goes like this:
0.X/trac/*
0.X/trac/<module>/*
0.X/tracopt/<module>/*
...
/plugins/0.X/<plugin>/tracext/*
0.X/sample-plugins/<single-file-plugin>.py
...
3rd party plugins
With some flexibility to move things up and down, as seen fit.
-- Christian
--
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.
