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 <[email protected]> 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 < > > [email protected]> 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" <[email protected]> > >> > >> 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 > >>> > >>> > >> > >
