Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Distilled the points about "GPL + CLA = commrecial interests" to only the bits essential to the "Fossil vs Git" argument. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | bsd-vs-gpl |
| Files: | files | file ages | folders |
| SHA3-256: |
ba1fa73b8708f51702c848fab12fe98e |
| User & Date: | wyoung 2019-07-12 15:29:34.478 |
Context
|
2019-07-12
| ||
| 15:41 | Removed a final sentence in a paragraph that basically just restated the paragraph in the new Fossil vs Git doc. check-in: f5a39a7e1d user: wyoung tags: bsd-vs-gpl | |
| 15:29 | Distilled the points about "GPL + CLA = commrecial interests" to only the bits essential to the "Fossil vs Git" argument. check-in: ba1fa73b87 user: wyoung tags: bsd-vs-gpl | |
| 14:53 | Applied rewording suggested in https://fossil-scm.org/forum/forumpost/1af94ddea9 check-in: 840f2b3929 user: wyoung tags: bsd-vs-gpl | |
Changes
Changes to www/fossil-v-git.wiki.
| ︙ | ︙ | |||
153 154 155 156 157 158 159 | Git was specifically designed to support the development of the Linux kernel. Fossil was specifically designed to support the development of SQLite. SQLite is much more widely deployed than the Linux kernel, but for Linux-based systems, the kernel is the more fundamental component. Although both projects must rank high on any objective list of "most | > | | 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 | Git was specifically designed to support the development of the Linux kernel. Fossil was specifically designed to support the development of SQLite. SQLite is much more widely deployed than the Linux kernel, but for Linux-based systems, the kernel is the more fundamental component. Although both projects must rank high on any objective list of "most important [https://en.wikipedia.org/wiki/Free_and_open-source_software|FOSS] projects," the two projects are almost entirely unlike one another, and this shows up in the design choices of the tools created to support them. The Linux kernel uses a bazaar-style development model. There are thousands and thousands of contributors, most of whom do not know each others names. These thousands are responsible for producing roughly 89⨉ more code than is in SQLite. (10.7 |
| ︙ | ︙ | |||
298 299 300 301 302 303 304 | from that source code. This difference in outlook allows a GPL-based project to do without a [https://en.wikipedia.org/wiki/Contributor_License_Agreement|constributor license agreement] (CLA) because by the very act of distributing binaries, you are bound to also distribute the source under a compatible license. There are GPL-based projects that do require a CLA, but this is | | < < < < | < | < | 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 | from that source code. This difference in outlook allows a GPL-based project to do without a [https://en.wikipedia.org/wiki/Contributor_License_Agreement|constributor license agreement] (CLA) because by the very act of distributing binaries, you are bound to also distribute the source under a compatible license. There are GPL-based projects that do require a CLA, but this is usually done to further commercial interests rather than to maintain the legal integrity of the [https://en.wikipedia.org/wiki/Free_and_open-source_software|FOSS] project itself. Contrast a BSD-style project, where contributions are not automatically relicensed merely by being distributed with the preexisting BSD code. Such projects often require a CLA even when there are no corporate interests, to ensure that all contributions are compatibly licensed with the existing body of code. It's a way to add a "no takebacks" clause to the basic BSD |
| ︙ | ︙ |