Hello,
I'd like to propose the reorganization of the components to something
more rational, basically following the hierarchical layout of the code,
which is itself quite close to the functional subsystems.
Here's the current list:
attachment
browser
changeset view
general
log view
mod_python frontend
notification
project
rendering
report system
roadmap
search system
spamfilter
ticket system
timeline
trac-admin
tracd
version control
webadmin
wiki
Here's how I propose to rename them:
admin/console
attachment
general
notification
plugins/spamfilter
plugins/webadmin
project
rendering
ticket
ticket/report
ticket/roadmap
search
timeline
versioncontrol
versioncontrol/browser
versioncontrol/changeset
versioncontrol/revisionlog
web/tracd
web/mod_python
wiki
When the components are grouped in a hierarchy, it becomes possible to
expand the list without making it that much harder to grasp. So I think
we could add those additional components:
admin/web
perm
plugins/mercurial
ticket/query
web/fcgi
One advantage is that an user can pick first the right subsystem, then
the subcomponent if needed, instead of being presented a list of
toplevel components (browser, log view...).
It also allows to disambiguate plugins vs. non-plugin (plugins/webadmin
vs. admin/web).
Finally, by adding a "begins with" option in Trac Query for the
component field, it's more convenient to get all the issues related to a
given subsystem (i.e. #5979).
-- 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
-~----------~----~----~----~------~----~------~--~---
