We just started. we are still going through the applications, db tables... if somebody is doing please guide us.
On Jul 5, 9:18 pm, Rodrigo Rosenfeld Rosas <[email protected]> wrote: > Em 05-07-2011 11:52, Nagaraj escreveu: > > > Hi all, > > > I am trying to integrate gitorious and chiliproject! > > Great news! I was willing to do that after Gitorious has upgraded Rails > from 2 to 3. > > Is the source-code somewhere? > > Best regards, > > Rodrigo. > > > > >> Using an external issue-tracking system integrated to Gitorious, as the > >> Ruby language does with Redmine, seems to be the way to go for now. > > Yes I agree. > > > We are integrating chiliproject with gitorious, our aim is when a > > project is created in gitorious corresponding issue tracking must be > > created in chiliproject. We would like to have links(gantt/calendar, > > issues, forums,etc...) from gitorious to chiliproject and vice versa. > > > We are eagerly looking for community support. > > > Thanks& Regards > > Nagaraj P G > > > On Jul 5, 6:38 pm, Rodrigo Rosenfeld Rosas<[email protected]> wrote: > >> Em 05-07-2011 09:55, Pedro Kiefer escreveu: > > >>> I don't see any advantage in having a distributed issue tracker, maybe > >>> there are some, but I think issue tracking is a central and unique > >>> service. You don't want (at least I don't see a reason for) Q&A, > >>> testing and management to have a clone of your repositories for adding > >>> bug reports. And you definitely don't want to have some issues added > >>> to a fork and not the main repository. > >>> Having a pluggable system, for supporting chiliproject, redmine, jira, > >>> bugzilla, or some other issue tracker is probably the best solution on > >>> the long run. > >> That's exactly what I think too. -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
