Documentation Source Text

Check-in [1e4dabf140]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Improve the focus of the "open-source, not open-contribution" section of the Copyright page.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:1e4dabf14044d7418678fcd13713c9d682173a42f5b202c499ea70af179fd579
User & Date: drh 2018-04-14 11:12:50
Context
2018-04-14
11:48
Add a link to the lobsters discussion to whynotgit.html. check-in: 08879e07be user: drh tags: trunk
11:12
Improve the focus of the "open-source, not open-contribution" section of the Copyright page. check-in: 1e4dabf140 user: drh tags: trunk
11:02
Add a link to the revision history of the whynotgit.html document. check-in: 34c5347f0b user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/copyright.in.

47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82

<tcl>hd_fragment notopencontrib {not open-contributin}</tcl>
<h2>Open-Source, not Open-Contribution</h2>

<p>
SQLite is open-source, meaning that you can make as many copies of it as
you want and do whatever you want with those copies, without limitation.
But SQLite is not open-contribution.  The project does not accept patches.
Only 27 individuals have ever contributed any code to SQLite, and of those
only 16 still have traces in the latest release.  
Only 3 developers have contributed
non-comment changes within the previous five years and 96.4% of the latest
release code was written by just two people.
(The statistics in this paragraph were gathered on 2018-02-05.)

<p>
Furthermore, all of the code in SQLite is original, having been written
specifically for use by SQLite.  No code has been copied from unknown
sources on the internet.

<p>
Many people associated "open-source" software with software that has
grown organically through contributions from countless individuals.
And, indeed, there is some open-source software that works that way.
But not SQLite.  SQLite uses the the
[https://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar|cathedral development philosophy]
not the bazaar approach.  All of the SQLite code has been written
by people who are well known to each other.

<tcl>hd_fragment warrantyoftitle {Warranty of Title}</tcl>

<div class="rightsidebar">
<form method="GET" action="https://www.hwaci.com/cgi-bin/license-step1">
<input type="submit" value="Buy An SQLite License">
</form>
</div>







|
|
|
<
<
<
<


|



<
<
<
<
<
<
<
<
<







47
48
49
50
51
52
53
54
55
56




57
58
59
60
61
62









63
64
65
66
67
68
69

<tcl>hd_fragment notopencontrib {not open-contributin}</tcl>
<h2>Open-Source, not Open-Contribution</h2>

<p>
SQLite is open-source, meaning that you can make as many copies of it as
you want and do whatever you want with those copies, without limitation.
But SQLite is not open-contribution.  In order to keep SQLite in the public
domain and ensure that the code does not become contaminated with proprietary
or licensed content, the project does not accept patches from unknown persons.





<p>
All of the code in SQLite is original, having been written
specifically for use by SQLite.  No code has been copied from unknown
sources on the internet.










<tcl>hd_fragment warrantyoftitle {Warranty of Title}</tcl>

<div class="rightsidebar">
<form method="GET" action="https://www.hwaci.com/cgi-bin/license-step1">
<input type="submit" value="Buy An SQLite License">
</form>
</div>