| 30 | | '''Note:''' this solution obviously owes much to the work of others; I'm not claiming to be an innovator here, just an integrator. |
| 31 | | |
| 32 | | == Just How Comprehensive Is This Solution, ''Really?'' == |
| 33 | | |
| 34 | | Ticket #130 contains a long, rambling, and extremely enlightening discussion of what people need from multi-project support. Anyone who has read that thread, and the [TracMultipleProjects other pages] proposing different ways to support multiple projects, knows that my solution isn't going to work for everyone. Nonetheless, I think I've hit a "sweet spot" that gives most people most of what they're looking for, and more importantly, can be (relatively) easily set up today by anyone. So while my claim of having a "comprehensive" solution might be seen as grandiose, I think it's supportable. |
| | 32 | * This approach '''isn't going to work for ''everybody'''''. Ticket #130 contains a long, rambling, and extremely enlightening discussion of what people need from multi-project support. Anyone who has read that thread, and the [TracMultipleProjects other pages] proposing different ways to support multiple projects, knows that no single approach is going to satisfy everone. Nonetheless, I think I've hit a "sweet spot" that gives most people most of what they're looking for, and more importantly, can be (relatively) easily set up today by anyone who is willing to use bleeding-edge Trac software and ''my'' choice of database technology. |
