2011/7/3 Rodrigo Rosenfeld Rosas <[email protected]>: > Then, I would like to start a discussion of a feature I always missed in > Gitorious. That discussion is also in alignment with the recent concerns > about Gitorious versioning. > > Mailing list are ineffective as an issue tracking system and Gitorious > definitely needs an issue tracking system. > > Writing a good tracking system from scratch and integrating it to Gitorious > is too much work. That means it won't happen any time soon. It also means > more code to maintain. > > 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.
Of course, external issue-tracking is probably the most simple solution. But why not promoting more and more distributed model? I know that many distributed issue tracking tools exist. Why not selecting and integrating one with gitorious? This would give gitorious many advantages over other solution. At the same time, you can regularly ignore my proposition as I do not have any spare time to invest on this topic. -- Guilhem BONNEFILLE -=- JID: [email protected] MSN: [email protected] -=- mailto:[email protected] -=- http://nathguil.free.fr/ -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
