On Mon, Aug 20, 2012 at 11:23 AM, Alex Harui <aha...@adobe.com> wrote:
> > > > On 8/20/12 11:01 AM, "Carlos Rovira" <carlos.rov...@codeoscopic.com> > wrote: > > > Hi Alex, > > > > when we get the official repo in Apache we'd not need to have github, but > > if you use it or not it would not be important. Git is "distributed" so > > unlike SVN you always have a "distributed" full repo. The one at apache > > will be the so called "origin" and well all flows will converge, but the > > one in my local machine will be another full repo (when is full synced) > and > > the fork at github as well be valid... > > > > But...although we don't need github, I must say that many people would > like > > to use due to it's "pull request" feature, that , as other said is not in > > git and only available in github. Pull request is what make github so > > social, since nobody has any responsabilities. you only develop and share > > through pull request and if you (PPMC with full write access to the > forked > > official repo) like the pull request you can integrate into the official > > repo. Github makes that extremely easy and funny and for that reason is > why > > it's model is a big success in open source and all people wants to use > it. > > > > > What would be the steps to integrate a GitHub pull request back to the > official Apache Git repo? > There are no known/accepted solutions yet to integrate GitHub into the Apache workflow. I have seen a bunch of JIRA tickets opened regarding this, but no consensus. There are a few techniques projects have tried, but none of them are blessed by INFRA as far as i know. > > What would be the steps to integrate a proposed change if we didn't use > GitHub and we retired the GitHub mirror? > I am sorry, but why would we want to retire the GitHub mirror? Right now, it is read-only. If we leave it like that, the community can at least fork the projects and work on it. > > GitHub might be great for sharing, if the committers have lots of extra > steps to deal that will be a dis-incentive for reviewing patches. > Agreed. We will have to come up with a way and put pressure on infra (ha!) to use such a workflow. >From my side, I am HIGHLY interested in removing the barriers for community participation. Getting an acceptable GitHub workflow is something I will be working on soon (after I wrap up what I am doing right now) Thanks, Om
