Adding links to vmb's fork/clone clarifcation, and to our incredible journey to disambiguate type of merges considered

morus
D. Joe 4 years ago
parent 84d27b32e1
commit 355a76818d
  1. 13
      README.md

@ -2,11 +2,11 @@
This is a collection of software project forks, collected primarily to
exemplify the assertion of software freedoms.
The term 'fork' here is used in the older, pre-GitHub sense of a division of
community development effort into two distinct projects, rather than the
trivial sense of a clone or branch of a source code corpus used in the
normal course of development and testing of those working with or within a
project.
The term 'fork' here is used in the older, pre-GitHub sense of
[a division of community development effort into two distinct projects](https://opensource.com/article/17/12/fork-clone-difference),
rather than the trivial sense of a clone or branch of a source code corpus
used in the normal course of development and testing of those working with
or within a project.
In the simplest form, it should make apparent any child-parent relationships
amongst projects
@ -19,5 +19,6 @@ disposition of the child projects, influence on other projects,
characterization of cooperation between or among child projects after the
fork including any later merging of the projects.
Merges of distinctly-originated projects will also be considered.
Merges of distinctly-originated projects will also be considered. If so, the
focus is on code bases rather than on [companies](https://ourincrediblejourney.tumblr.com/).

Loading…
Cancel
Save