Lesson plan

Fork and pull model

Fork and pull model refers to a software development model mostly used on GitHub, where multiple developers working on an open, shared project make their own contributions by sharing a main repository and pushing changes after granted pull request by integrator users. Followed by the advent of distributed version control systems (DVCS), Git naturally enables the usage of a pull-based development model, in which developers can copy the project onto their own repository and then push their changes to the original repository, where the integrators will determine the validity of the pull request. Since its appearance, pull-based development has gained popularity within the open software development community. On GitHub, over 400,000 pull-requests emerged per month on average in 2015. It is also the model shared on most collaborative coding platforms, like Bitbucket, Gitorious, etc. More and more functionalities are added to facilitate pull-based model.

Back to article

Article summary

Fork and pull model refers to a software development model mostly used on GitHub, where multiple developers working on an open, shared project make their own contributions by sharing a main repository and pushing changes after granted pull request by integrator users. Followed by the advent of distributed version control systems (DVCS), Git naturally enables the usage of a pull-based development model, in which developers can copy the project onto their own repository and then push their changes to the original repository, where the integrators will determine the validity of the pull request. Since its appearance, pull-based development has gained popularity within the open software development community. On GitHub, over 400,000 pull-requests emerged per month on average in 2015. It is also the model shared on most collaborative coding platforms, like Bitbucket, Gitorious, etc. More and more functionalities are added to facilitate pull-based model.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.