Go to file
Joe 012bfb823b Some Go git hosting, Gogs forks
* new file:   gogs-gitea.md
  * new file:   gogs-notabug.md
2017-10-26 08:55:22 -04:00
CONTRIBUTING.md .com not .org, oops 2017-10-12 16:49:49 -04:00
LICENSE.md licensing and contributing, some guidance 2017-10-12 16:44:22 -04:00
README.md * initial rational README 2017-10-03 11:04:57 -04:00
curl-gnurl.md getting this curl-gnurl thing in there while it's fresh to me 2017-10-12 15:38:07 -04:00
gogs-gitea.md Some Go git hosting, Gogs forks 2017-10-26 08:55:22 -04:00
gogs-notabug.md Some Go git hosting, Gogs forks 2017-10-26 08:55:22 -04:00
openwrt-lede.md openwrt and lede via The Reg 2017-10-16 08:17:28 -04:00


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.

In the simplest form, it should make apparent any child-parent relationships amongst projects

Stretch goals include annotations indicating the date of the fork, the nature of the fork, any divergence in goals or features of the child projects, languages used, development environments, documention for the projects or for the motivations for entering the forking process, post-fork 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.