[llimllib]

we use redmine+gitosis at the moment, and man would I love to get my hands on github:fi. Redmine completely fails to be anything other than a bug tracker when you start dealing with public branches, of which it has no concept.

We definitely don't want to host our source on somebody else's machine, and there's no open source solution comparable to github.

It's too expensive for us at the moment, but I can imagine a time when it won't be, and I'll push to get it then.

[aditya]

What do you mean by public branches? Can you clarify a little bit since we're trying to evaluate Redmine and see if it will work on a fairly large sized team of Rails hackers (15+)

[llimllib]

Redmine IME is fine as a bugtracker, but it's not built to handle a DVCS.

So, basically, git works by blessing a branch on some server as "master". Since many of us are working on new stuff at the same time, and we don't want to work in master where our work could conflict, but we do want to see each other's changes. Thus, we make branches on that same server which we all track - these are what I mean by public branches.

So, basically this is how I'll work:

* Pick a bug out of the bug tracker

* make a public branch of the current master and call it [name]-fix-[bug #] or [name]-[new feature]

* push fixes/development to that public branch

* ask a coworker to review the branch for merge (this is easy, since it's a public branch they're tracking already)

* make any changes they recommend, rinse and repeat

* merge the public branch into master and push it to the remote repository

The problem with redmine is that it only tracks the master branch, not any of those feature branches that me and my coworkers are working on, whereas github shows them admirably, e.g.: http://github.com/rails/rails/network .

I love git, but redmine is basically unable to cope with the way we work.

Oh and if you want to work this way, this script is invaluable: http://git-wt-commit.rubyforge.org/git-publish-branch