| | 1 | = Multiple Projects within a Single Trac Environment = |
| | 2 | |
| | 3 | This is an alternative conception about how to manage |
| | 4 | multiple projects with Trac. The traditional way is |
| | 5 | to follow the model of TracMultipleProjects/MultipleEnvironments. |
| | 6 | |
| | 7 | Yet there has been since a long time many request for |
| | 8 | being able to manage multiple projects within a single |
| | 9 | Trac environment, in order to have a unified view on |
| | 10 | the development activity. |
| | 11 | |
| | 12 | |
| | 13 | == Possible motivations for having a single Environment == |
| | 14 | |
| | 15 | * one single wiki, which facilitates the building of |
| | 16 | shared knowledge (development guidelines, |
| | 17 | development process documentaion, tips and tricks, |
| | 18 | customer information, etc.) |
| | 19 | * possibility of sharing Milestones between projects |
| | 20 | (useful for coordinating a single release of different |
| | 21 | applications) |
| | 22 | * sharing tickets between projects, and moving them |
| | 23 | between projects |
| | 24 | |
| | 25 | == One or Multiple Repositories? == |
| | 26 | |
| | 27 | The oldest ticket presenting this approach is #130. |
| | 28 | It asked for being able to browse multiple projects |
| | 29 | residing in different repositories. This is unlikely |
| | 30 | to happen in the short term. One of the problems this |
| | 31 | would raise is the ambiguity it introduces in TracLinks |
| | 32 | (however, the InterTrac approach, explained in |
| | 33 | TracMultipleProjects/MultipleEnvironments could be extended to |
| | 34 | adapt to this situation too). |
| | 35 | |
| | 36 | Since then, other people have expressed in #130, #548 and also very |
| | 37 | clearly in #1048, that it would already be a big step ahead |
| | 38 | to support multiple projects located within a single |
| | 39 | (Subversion) repository, in a single Trac environment. |
| | 40 | |
| | 41 | == Possible implementation == |
| | 42 | |
| | 43 | The ticket #1048, as well as ticket #1135, suggest that |
| | 44 | the already existing ''Component'' ticket field could be |
| | 45 | used to represent a project. |
| | 46 | |
| | 47 | cboos explained in ticket #586 (although that ticket belongs to the |
| | 48 | other multiple component support ''family'') how this could |
| | 49 | be implemented using the experimental relationship facility introduced |
| | 50 | in the source:branches/cboos-dev/trac-obj-branch branch. |
| | 51 | |
| | 52 | ''more explanations to come...'' |
| | 53 | |
| | 54 | |
| | 55 | |
