On Wed, 21 Apr 2010, Roman Chyla wrote: > All of the three points that were noted can be done in one instance of > Trac, by assigning tickets to different components.
That's the invenio/inspire prefix alternative I mentioned. It is definitely a possibility, but it involves more than just creating additional ticket components. We would need to have conventions for wikis, code browsers, timelines, milestones, and blog entries, so that they could be easily viewable separated, e.g. to populate news tickers. And it would have to be done in a UI smart way, so that when a University of Foo comes to Invenio wiki/tracker to learn about the software, it would not be confused by all those instance-specific tickets. > I think it is worth evaluating scenarios that prevent DID, or > otherwise at the end of the day, the argument that "it has been done > so in the past" sneaks in and is applied on everything without any > evaluation, whatsoever. Definitely worth evaluating, I mentioned that already. Just as `past' does not necessarily mean `good', it does not necessarily mean `bad' either. Best regards -- Tibor Simko
