#2539 closed task (invalid)
Branching current Trac development to "trac-2" to support multiple projects/single trac environment/multiple code repositories
| Reported by: | Owned by: | daniel | |
|---|---|---|---|
| Priority: | highest | Milestone: | |
| Component: | project | Version: | |
| Severity: | major | Keywords: | trac-2 |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Firstly, thank edgewall's people for open source such a good tracking tool.
As requested by so many people, we also want to adopt Trac for our internal software project management and issue tracking.
The current Trac's design and architecture are for single project management and ideal for sole developers or the like.
Our aim in the long-term is to transform Trac into a full-scale enterprise project management tool, something that's better than JIRA and…open source :D
To achieve that goal, we need to carefully re-design and architect Trac for long-term gain, and at the same time maintain the current code trunk for single project management. This situation is similar to that of Maven.
I have read some articles for extending Trac and force it to handle multiple projects. IMHO, the current Trac is not designed for it!
I would suggest to branch out from the current trunk and create a new project, called Trac-2, which support multiple inter-related projects.
Anyone wants to take the initial step? I want to participate, email me''
Anyone wants to participate? Do email me.
HAPPY NEW YEAR TO EVERYONE!
Best wishes,
Philip
This would've been more appropriate to send to the MailingList.