Pull requests from a fork of the github mirror can be used for RTC, if the community agrees(CouchDB already uses this [1]), but we'd need to discuss bypassing the entire review board - commit by committer workflow separately. This would be a great advantage too.
Making local commits and pushing to your own github fork, I feel is a very efficient workflow, and when ready it can simply be merged through pull requests. I will let this thread continue till Friday, and then contact ASF infra on how to proceed, after which I will start a vote. If infra requires someone to volunteer from the project, I am more than willing to do so. If anyone else is interested, please let me know. Thanks, Hari [1] http://wiki.apache.org/couchdb/ContributorWorkflow -- Hari Shreedharan On Wednesday, July 11, 2012 at 11:39 AM, Brock Noland wrote: > +1 for git > > -- > Brock Noland > Sent with Sparrow (http://www.sparrowmailapp.com/?sig) > > > On Wednesday, July 11, 2012 at 7:19 PM, Ralph Goers wrote: > > > If it isn't obvious, I'm also in favor of this. I think it has the > > potential to make the RTC process much better. > > > > Ralph > > > > On Jul 11, 2012, at 11:11 AM, Ralph Goers wrote: > > > > > If you use a process like what is documented at > > > https://help.github.com/articles/using-pull-requests would patches even > > > be necessary? I would hope that the review board could handle just using > > > the GitHub tools at the very least. > > > > > > Ralph > > > > > > On Jul 11, 2012, at 9:31 AM, Hari Shreedharan wrote: > > > > > > > Ralph, > > > > > > > > Yes, review board does integrate with git pretty well. As of now, there > > > > is a repo called flume-git on review board which you need to select to > > > > submit a git generated patch. In fact, if we use git, we don't need to > > > > select the base folder etc(as we do for an svn patch), simply uploading > > > > the patch is enough. > > > > > > > > Hari > > > > > > > > -- > > > > Hari Shreedharan > > > > > > > > > > > > On Wednesday, July 11, 2012 at 9:11 AM, Ralph Goers wrote: > > > > > > > > > Does the review tool integrate with git? By that I mean will patches > > > > > still need to be added to the review tool or is it capable of > > > > > figuring out the differences on its own if the enhancement/fix is on > > > > > a "branch" (or fork or whatever it is that git calls it). If so, this > > > > > would make RTC much more user friendly. > > > > > > > > > > Ralph > > > > > > > > > > On Jul 10, 2012, at 11:55 PM, Hari Shreedharan wrote: > > > > > > > > > > > Hi all, > > > > > > > > > > > > Apache infra is now allowing projects to choose git as the primary > > > > > > source control, if the project community choose so. I have been > > > > > > using git svn for commits and git to maintain my repo, but recently > > > > > > there have been issues with the git-svn sync (earlier git mirror > > > > > > had substantial delays - but now it looks like it is missing > > > > > > commits). > > > > > > > > > > > > I would like to know how many of you would be interested in such a > > > > > > move, to host Flume as wip git repo at Apache. Please note that > > > > > > this is not meant to be a comparison of git and svn, this is just a > > > > > > discussion to gauge the community's interest in using git as the > > > > > > primary source control. > > > > > > > > > > > > Also, please note that I have not communicated this with ASF Infra > > > > > > about this, and I am not exactly sure how the move would work. I > > > > > > will work on that if there is sufficient interest within the > > > > > > community. > > > > > > > > > > > > > > > > > > Thanks, > > > > > > Hari > > > > > > > > > > > > -- > > > > > > Hari Shreedharan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
