Documentation Source Text

Check-in [419389e585]
Login

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

Overview
Comment:Clarify the license for SQLite documentation.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 419389e585bdca5d700e0d8c437f9c4fa743a8e2
User & Date: drh 2013-05-28 13:23:04.865
Context
2013-05-29
06:57
Fix minor typo in the virtual table documentation for xCreate and xConnect. (check-in: 44d1e198ca user: mistachkin tags: trunk)
2013-05-28
13:23
Clarify the license for SQLite documentation. (check-in: 419389e585 user: drh tags: trunk)
2013-05-23
22:56
Fix a typo in mmap.html. (check-in: 04448addda user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/copyright.in. 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

33
34
35
36
37
38
39
40
41
42

<title>SQLite Copyright</title>

<h2>SQLite Copyright</h2>

<table align="right" vspace="0" hspace="10" border="1" cellpadding="20">
<tr><td align="center">
<img src="images/nocopy.gif"><br>
SQLite is in the<br>
[http://en.wikipedia.org/wiki/Public_Domain | Public Domain]
</td></tr>
</table>

<p>
All of the deliverable code in SQLite has been dedicated to the
[http://en.wikipedia.org/wiki/Public_Domain|public domain]
by the authors.
All code authors, and representatives of the companies they work for,
have signed affidavits dedicating their contributions to
the public domain and originals of
those signed affidavits are stored in a firesafe at the main offices
of <a href="http://www.hwaci.com">Hwaci</a>.
Anyone is free to copy, modify, publish, use, compile, sell, or distribute
the original SQLite code, either in source code form or as a compiled binary,
for any purpose, commercial or non-commercial, and by any means.
</p>

<p>
The previous paragraph applies to the deliverable code in SQLite - 
those parts of the SQLite library that you actually bundle and
ship with a larger application.  Portions of the documentation and
some code used as part of the build process might fall under
other licenses.  The details here are unclear.  We do not worry

about the licensing of the documentation and build code so much
because none of these things are part of the core deliverable
SQLite library.
</p>

<p>
All of the deliverable code in SQLite has been written from scratch.
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














|













|
|
|
|
|
>
|
<
|








1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

35
36
37
38
39
40
41
42

<title>SQLite Copyright</title>

<h2>SQLite Copyright</h2>

<table align="right" vspace="0" hspace="10" border="1" cellpadding="20">
<tr><td align="center">
<img src="images/nocopy.gif"><br>
SQLite is in the<br>
[http://en.wikipedia.org/wiki/Public_Domain | Public Domain]
</td></tr>
</table>

<p>
All of the code and documentation in SQLite has been dedicated to the
[http://en.wikipedia.org/wiki/Public_Domain|public domain]
by the authors.
All code authors, and representatives of the companies they work for,
have signed affidavits dedicating their contributions to
the public domain and originals of
those signed affidavits are stored in a firesafe at the main offices
of <a href="http://www.hwaci.com">Hwaci</a>.
Anyone is free to copy, modify, publish, use, compile, sell, or distribute
the original SQLite code, either in source code form or as a compiled binary,
for any purpose, commercial or non-commercial, and by any means.
</p>

<p>
The previous paragraph applies to the deliverable code and documentation
in SQLite - those parts of the SQLite library that you actually bundle and
ship with a larger application.  Some scripts used as part of the
build process (for example the "configure" scripts generated by autoconf)
might fall under other open-source licenses.  Nothing from these build 
scripts ever reaches the final deliverable SQLite library, however, and 
so the licenses associated with those scripts should not be 

a factor in assessing your rights to copy and use the SQLite library.
</p>

<p>
All of the deliverable code in SQLite has been written from scratch.
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
︙︙