Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Add the "Open-source not open-contribution" section to the copyright.html page. Try to clarify the meaning of "Warranty of Title". |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | branch-3.22 |
Files: | files | file ages | folders |
SHA3-256: |
a2ec6275f0b006dbaad18bf2267554d3 |
User & Date: | drh 2018-02-05 21:14:35.306 |
Context
2018-02-05
| ||
21:18 | Fix typo on the new copyright.html page. (check-in: c5661b456c user: drh tags: branch-3.22) | |
21:14 | Add the "Open-source not open-contribution" section to the copyright.html page. Try to clarify the meaning of "Warranty of Title". (check-in: a2ec6275f0 user: drh tags: branch-3.22) | |
20:00 | Rework the CGI scripts for search so that they use the Wapp framework (https://wapp.tcl.tk). Cherry-pick from trunk. (check-in: 6a06e6c785 user: drh tags: branch-3.22) | |
Changes
Changes to pages/copyright.in.
︙ | ︙ | |||
41 42 43 44 45 46 47 48 49 50 51 52 53 | No code has been taken from other projects or from the open internet. Every line of code can be traced back to its original author, and all of those authors have public domain dedications on file. So the SQLite code base is clean and is uncontaminated with licensed code from other projects. </p> <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> | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | | > | | > | > > > > | < < < < < | < < < < < < < | < < < < < < < < | < < < < < < | < < < < < < | 41 42 43 44 45 46 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 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 | No code has been taken from other projects or from the open internet. Every line of code can be traced back to its original author, and all of those authors have public domain dedications on file. So the SQLite code base is clean and is uncontaminated with licensed code from other projects. </p> <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 grow 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 philosopy] 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> <h2>Warrany of Title</h2> <p> SQLite is in the public domain and does not require a license, some organizations want legal proof of their right to use SQLite. Some reasons for obtaining a license include: </p> <ul> <li> Your company desires warranty of title and/or indemnity against claims of copyright infringement. <li> You are using SQLite in a jurisdiction that does not recognize the public domain. </li> <li> You are using SQLite in a jurisdiction that does not recognize the right of an author to dedicate their work to the public domain. </li> <li> You want to hold a tangible legal document as evidence that you have the legal right to use and distribute SQLite. </li> <li> Your legal department tells you that you have to purchase a license. </li> </ul> <p> If you feel like you really need to purchase proof of your right to use SQLite, <a href="https://www.hwaci.com/">Hwaci</a>, the company that employs all the developers of SQLite, will <a href="https://www.hwaci.com/cgi-bin/license-step1">sell you a Warranty of Title</a>. A Warranty of Title is a legal document that asserts that the claimed authors of SQLite are the true authors, and that the authors have the legal right to dedicate the SQLite to the public domain, and that Hwaci will vigorously defend against challenges to those claims. All proceeds from the sale of SQLite Warranties of Title are used to fund continuing improvement and support of SQLite. </p> <h2>Contributed Code</h2> <p> In order to keep SQLite completely free and unencumbered by copyright, the project does not accept patches. If you would like to make a suggested change, and include a patch as a proof-of-concept, that would be great. However please do not be offended if we rewrite your patch from scratch. |