On Jan 28, 2009, at 1:47 AM, Kevan Miller wrote:
There are some usages of GIT that would not fit well into an Apache project. For instance, I would not want to see project members using GIT as a private means of sharing code updates. Ultimately, code needs to get into our svn repo -- that's where we should be sharing code.

Why do you have a problem with users sharing code via their own GIT repos? I guess I can kinda see your concern, but I'd expect folks with significant changes to the codebase to want to share their GIT repos with others *before* pushing those changes back into SVN.

Right. So, I wouldn't want a few people to decide to implement some new function, start sharing code (privately amongst themselves), and then dump it into svn. IIUC, GIT makes this pretty easy to do. Currently, this sort of activity would happen in an svn sandbox or via patches posted to a Jira. In either case the collaboration and work should be public. I want to make sure we maintain this.

Jay's example of a security-related patch is a very compelling example as to why sharing code directly via GIT instead of SVN can be a good idea at times.


Until *everyone* is using GIT and we have community policies governing its usage, svn and our mailing lists are where we need to be collaborating.

Why does *everyone* need to use GIT? IMO it is just a tool, some folks might prefer BZR, HG or SVK, making use of the features/ advantages that each tool provides. I don't see why there would ever need to be a point where *everyone* is on the same tool since ATM the underlying authoritative and definitive location for the codebase is the ASF SVN.

 * * *

I really don't see what the harm is that you seem worried about. I'm not sure that we need any "policies governing its usage" either, no more than we need guidelines on how some one uses /bin/vi or notepad.exe, unless you mean the content not the tool, and in that case I think the general docs we have on that is sufficient.

IMO GIT allows for a much more flexible development model, and I really don't see why we'd want to take away that flexibly with tape (of the red kind).

:-\

--jason

Reply via email to