> One might also suggest that Apache should host Git repositories. That > is also a difficult case to make. Apache's infrastructure operates on a > shoestring. Maintaining a reliable and performant source-code > repository is a substantial task, and the infrastucture folks are loath > to add to that task, especially given the doubts in the organization > about the suitability of Git for Apache projects. Yeah. Making Git work for Apache on a large scale is kind of tricky. It doesn't quite have the same features as Subversion when it comes to large, centralized, conglomerate repositories like Apache's. I think it would be better to let Git-friendly projects figure out the details before demanding help from the infrastructure team.
> Thrift needs to decide whether it is CTR or RTC, and, if RTC, the > mechanics of how patches are to be reviewed. For most Apache projects, > every proposed change is discussed in Jira with patch files attached > there. Will Thrift operate this way? If so, what role would Git serve? > At a glance, it appears to provide a simple mechanism for patches to > bypass publication in Jira, which worries an old-school guy like me. Let's do this in a separate thread. I'll start it after I finish responding to this one. :) --David
