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?
What would be the steps to integrate a proposed change if we didn't use
GitHub and we retired the GitHub mirror?
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.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
