On 2/7/08 11:28 AM, "Shane Curcuru" <[EMAIL PROTECTED]> wrote:
> In the medium term, I'd like to see a broader desire to use git, along > with some thoughts as to why new projects need it instead of svn. I > definitely understand your comments about infra needing to support > projects. But I also don't think the ASF should try to be all things > to all projects. I'd like to see how git users run projects > differently than svn users, and make sure that it really fits with how > we (the ASF) like to have consensus based community projects. I wasn't involved in the original thread at all, but wanted to chime in. It seems to me that while git is the tool in question, it's really a matter of a distributed versus centralized model. That, unfortunately, heads down the road of religious debate. I happen to like Subversion a lot. It has excellent tool support, is pretty straightforward to admin, and does its job well. However, it can be quite a turn-off for attracting new committers. It's like we're saying "you can contribute, but you can't use a reasonable tool to do it." In the past, to get around this I would mirror the SVN repository with some other tool, such as tailor, for some other SCM, such as darcs. Clearly, this is a less than ideal situation. > git feels like a different enough way to manage the core resource of > any project - the code (and/or docs, test, build, etc.) that I'd like > to put some thought into having us support it, rather than just > jumping in - both on the infra side (scalable repository; admin > expertise), legal side (how to we track all incoming changes?) and the > community side (are they close to The Mythical Apache Way?). If that > means some community that's in a huge hurry wants to go build their > project elsewhere, that's OK with me. You can call me an elephant > sometimes, too. 8-) I don't know enough about git to comment reliably here, but most of the distributed SCMs I've come across have the concept of a pristine, master copy. This copy can be configured such that only certain people can push changes to it. All others would have to submit patches through to the one of these people or via some other channel, such as JIRA. So, while the implementation is slightly different, it seems to model the existing structure fairly well. -- Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
