On Jan 5, 2013, at 1:47 PM, Jacques Le Roux <[email protected]> wrote:
> From: "Ean Schuessler" <[email protected]> >> 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 Can we even restrict commit access to branches in the ASF SVN any more? We moved away from restricted access to framework versus applications a long time ago due to pressure from infra/others, and I'm not sure if we can so easily make someone a committer to just a branch. With GitHub we don't need to do anything, anyone can create a public or private fork of OFBiz and change it all they want. People can also still extract patches across multiple commits so it's not so much work to apply them. It's really a much better approach. -David
