From: "Ean Schuessler" <e...@brainfood.com> > I don't know that its much worse. On GitHub you will see the forks and could > track their changes if you wanted. >I think the complication with handing out SVN branches is that we will end up >with a lot of low quality branches in the core repository.
Depends, if committer/s follow/s the work closely then it can be a could way to share until the work is finished. I don't see what GitHub adds to this. >The nice thing about GIT is that the chaff doesn't get into the wheat bucket. Don't make sense to me. In svn branches in OFBiz repo if the work is of low quality, and dropping a branch is only few clicks. If the work is of low quality in GitHub it will be ignored as well. If the work is of good quality, why wait to have it in GitHub in the meantime and not directly in a svn branch? I still really don't see what GitHub brings here... apart (for me at leat) learning to use Git Jacques > ----- "Jacques Le Roux" wrote: >> Because it's possibly easier for committers to follow the work done and not >> get a big patch at the end. >> With Git you tend to receive either a burst of patches or a big one, both in >> one shoot. >> Then it's hard to review the work done. By steps it's easier >> I don't use GitHub, I have enough to do with OFBiz patches already... > > -- > Ean Schuessler, CTO > e...@brainfood.com > 214-720-0700 x 315 > Brainfood, Inc. > http://www.brainfood.com >
