Am 07.02.2006 um 13:18 schrieb Christian Boos:
So this is the general long-term direction, and adding features
that conflict with that direction should obviously be avoided.
The scope for Trac 1.0 is (and has always been) clearly limited to
single-project support. InterWiki/InterTrac links can help
managing multiple projects, however we should not try to bolt on
more comprehensive features such as retrieving and displaying
information from another environment.
I think that at this point (pre 1.0), it's still undecided how we
want to handle
multiple projects, no?
The plan to have multiple-projects-per-environment has existed pretty
much since I've joined the Trac team. Although it arguably has been
poorly communicated (mostly over IRC).
There are many options.
Not really. There are many open questions in general, but the two
basic approaches at this level are multi-project/single-env or multi-
project/multi-env (or single-project/single-env).
One seems which seems particularly appealing to me is to keep the
current
"one environment = one project", because this is now quite clear
conceptually:
one environment => one db, one repository, one set of milestones,
one wiki
space, etc.
At the same time, it should be possible to "aggregate" several
environments,
in a kind of virtual environment, that would provide an unified view
(one timeline, a common virtual root for browsing the repositories, an
aggregated wiki, consolidated search and queries, etc.)
I think it's worth thinking about it.
IMHO, multi-proj/single-env is a much more intuitive model that is
also more powerful in most respects. A very important advantage is
that the database is shared, making cross-project queries trivial and
cross-project changes atomic. Sharing a central list of users is
simple and natural. Adding a new project doesn't require creating an
environment directory with a database, configuration file, etc: it's
just a new record in the DB.
In that perspective, having environments know about each other would
be natural.
But not under the multi-project/single-env model... the siblings
support assumes "your model", so it shouldn't be in Trac until
there's agreement that it's the approach we should take (which I
think is unlikely, but that's just me).
Cheers,
Chris
--
Christopher Lenz
cmlenz at gmx.de
http://www.cmlenz.net/
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
