Within several other open-source projects, I've seen the concept of "component/subsystem" "leads/owners".
I have difficulties to identify the relevant component-owner within the trac project. Possibly the project should provide a document which mentions the responsibilities of the trac team members. Component Owners: * get the tickets subjecting the component assigned * delegate tasks to contributors or to themselves * communicate requirements and requerst to other component owners * assing subcomponent ownership (e.g. file level) for external contributors Subcomponent ownership can be either temporarily (e.g. for a refactoring or small extension), or long-time (e.g. for active keeping a file and it's functionality up-to-date). Other team members (and the Project Lead) do not 'touch' the components, but instead pass requirements or change-requests to the component owner. This protects the thinking-flow of the component-owner (e.g. does not have to deal with introduced code-changes e.g. during a brain-ripening phase). And: this ensures a consisten coding style (e.g. functional form ComponentOwner A, OO from ComponentOwnerB). - I think Component Ownership is the best way to manage a project which becomes larger and larger. Those are of course just suggestions. But it would be nice to have at least a very basic document with and overview of subsystems (components) and the developers working on them. . -- http://dev.lazaridis.com/base/wiki/SubsystemLead --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
