Yeah, the GitHub guys decided to somewhat redefine the word, but not totally (ie it's an extension of the fork concept that turns it back into something like a remote branch). A git fork is still a fork, it's just that git has some tools that allow you to use the fork somewhat like a remote branch.
What I was saying was in response to what Jacques wrote as much as what you wrote, and Jacques was asking why you wanted to "fork" OFBiz. Here's one for the GitHub folks: they're jerks for causing probably thousands of confusing discussions like this. I guess they hoped it would result in people embracing the concept of forking, which they are clearly advocates of and think the world will get better the more forking is done. Back to my point, what you want to do is create a "vendor branch", and using a GitHub Fork is one way to do that. It's not a fork, it's a GitHub Fork. Using a GitHub fork is NOT the best way to create a vendor branch for OFBiz, because OFBiz does not use GitHub. Apache OFBiz is managed in the ASF SVN repository. The way to get patches back into OFBiz is not to use GitHub's Pull Request feature (who knows where that will go and who, if anyone, will see it), it is to create a patch and submit it in a Jira issue. -David On Mar 15, 2011, at 1:28 PM, chris snow wrote: > Hi David, I was using GitHub's definition of a fork: > > "Before GitHub, *forking* was a subgroup of developers going in a different > direction with the codebase — a rift in the community. Today a project can > have hundreds of forks, each trying out ideas that may get merged back in to > the main project. Forks now represent a vibrant and active community." > > On Tue, Mar 15, 2011 at 6:45 PM, David E Jones <d...@me.com> wrote: > >> >> It sounds like what you want to do is not a "fork" (which implies breaking >> away from the project and never looking back), but rather a "branch" and >> more specifically something along the lines of the "vendor branch" pattern >> which is something very common. >> >> -David >> >> >> On Mar 14, 2011, at 1:27 AM, chris snow wrote: >> >>> Thanks for the reply Jacques. >>> >>> The current process of waiting and relying on the goodwill of >> contributors >>> to commit my patches does not fit well with agile development. Forking >> will >>> allow me to develop at my own pace, but still allow my to synchronise >>> upsteam for bugfixes, etc. >>> >>> >>> >>> On Mon, Mar 14, 2011 at 6:56 AM, Jacques Le Roux < >>> jacques.le.r...@les7arts.com> wrote: >>> >>>> I think nobody manages it. It's done by default by the ASF for all >>>> projects: http://git.apache.org/ >>>> I have no ideas about the diff. >>>> Why do you want to fork OFBiz? >>>> >>>> Jacques >>>> >>>> From: "chris snow" <chsnow...@gmail.com> >>>> >>>> Hi Forum, >>>>> >>>>> I would like to create an ofbiz fork in GitHub. It seams like there >> are >>>>> two >>>>> main options: >>>>> >>>>> 1) Use GitHub to fork from apache/ofbiz at >>>>> https://github.com/apache/ofbiz >>>>> 2) Use git to create a clone directly from >>>>> http://git.apache.org/ofbiz.git >>>>> >>>>> What are the main differences in these two approaches? >>>>> >>>>> If I go with option 1, and I want to do "Pull Requests" who manages >>>>> https://github.com/apache/ofbiz? I.e. who will receive my "Pull >>>>> Requests"? >>>>> >>>>> Cheers, >>>>> >>>>> Chris >>>>> >>>>> >>>> >> >>
