Hello Ferran, Thank you for the links, it was very interesting reading. Your experience also seems to caution against similar situations. In my previous job, we were also using Trac for multiple projects (namely 4), but they were really a separate projects so I can't say a lot about MultiProjects settings - but on the other hand, I can easily imagine it.
But the basic question IMHO is whether CDS and INSPIRE need to be separate - whether they are INDEPENDENT - I don't think anyone can answer "yes" to that question, at least for inspire. Or if they are SEPARATE - answer might be yes, but separate in which way? If "not technically", then is there a real need for MultiProjects setup? By this simple consideration array of technical nightmares might be gone, and if that is solved, there is no need to solve other stuff. Especially when 7 days ago Trac rolled out their MultiRepository support: http://trac.edgewall.org/ticket/130#comment:145 roman On Wed, Apr 21, 2010 at 9:03 AM, Ferran Jorba <[email protected]> wrote: > Hello Tibor, Travis et al, >> >> On Tue, 20 Apr 2010, Brooks, Travis C. wrote: >>> So, shall we set up a parallel INSPIRE Trac instance? >> >> Yes, I think so. Let's use the Invenio Trac instance for a few days, >> configure it to the will, and I'll then clone it for INSPIRE. > > Sorry to jump in without being asked. A couple of years ago we > evaluated Trac for internal use for our DDD site and other library > related projectS. The last S is important: we, like many others, are > inveolved in more than one project. > > Doing it in Trac was not possible at that time, but rather, you have to > set several Trac instances, and duplicate users, permissions, and so > on. Then, it is not possible to know all tickets (tasks, or whatever) > assigned to a specific person, or priorise them across projects. > > There are a couple of pages in the Trac site about this: > http://trac.edgewall.org/wiki/TracMultipleProjects and the infamous > http://trac.edgewall.org/ticket/130. In this last ticked > (http://trac.edgewall.org/ticket/130#comment:52) I learned about > DrProject (https://www.drproject.org/), a Trac fork with multiproject > support, that we are very pleased to use here at UAB. > > The trouble is that DrProject is now a dead project. The students at > the University of Toronto that wrote them under the leadership of Dr > Greg Wilson are rewriting it under the Django framework and it will be > called Basie (https://basieproject.org/), but it is not finished yet. > However, there are a couple of alternatives since then: Retrospectiva > (http://retrospectiva.org/) and Redmine (http://www.redmine.org/) both > in Ruby. Redmine seems to be more mature and it is already packaged for > Debian, a big plus for us (http://packages.debian.org/redmine). It is > also multidatabase, multilingual, multi DVCS (including git), etc. etc. > > We have not decided yet which one we will migrate to, since we are not > in a hurry, but my question is: are you sure to want to migrate to a > isolated tool where will be no relation between your (at least) two > different instances? > > A couple of posts about Trac vs Redmine: > > http://changelog.complete.org/archives/696-thoughts-on-redmine > http://changelog.complete.org/archives/701-at-long-last-softwarecompleteorg-migrated-to-redmine > > Again, please excuse my 0.2 cents here, > > Ferran >
