17594
|
1 |
SQLite is in the Public Domain
|
|
2 |
|
|
3 |
All of the deliverable code in SQLite has been dedicated to the public
|
|
4 |
domain by the authors. All code authors, and representatives of the
|
|
5 |
companies they work for, have signed affidavits dedicating their
|
|
6 |
contributions to the public domain and originals of those signed
|
|
7 |
affidavits are stored in a firesafe at the main offices of Hwaci. Anyone
|
|
8 |
is free to copy, modify, publish, use, compile, sell, or distribute the
|
|
9 |
original SQLite code, either in source code form or as a compiled
|
|
10 |
binary, for any purpose, commercial or non-commercial, and by any means.
|
|
11 |
|
|
12 |
The previous paragraph applies to the deliverable code in SQLite - those
|
|
13 |
parts of the SQLite library that you actually bundle and ship with a
|
|
14 |
larger application. Portions of the documentation and some code used as
|
|
15 |
part of the build process might fall under other licenses. The details
|
|
16 |
here are unclear. We do not worry about the licensing of the
|
|
17 |
documentation and build code so much because none of these things are
|
|
18 |
part of the core deliverable SQLite library.
|
|
19 |
|
|
20 |
All of the deliverable code in SQLite has been written from scratch. No
|
|
21 |
code has been taken from other projects or from the open internet. Every
|
|
22 |
line of code can be traced back to its original author, and all of those
|
|
23 |
authors have public domain dedications on file. So the SQLite code base
|
|
24 |
is clean and is uncontaminated with licensed code from other projects.
|
|
25 |
Obtaining An Explicit License To Use SQLite
|
|
26 |
|
|
27 |
Even though SQLite is in the public domain and does not require a
|
|
28 |
license, some users want to obtain a license anyway. Some reasons for
|
|
29 |
obtaining a license include:
|
|
30 |
|
|
31 |
* You are using SQLite in a jurisdiction that does not recognize the
|
|
32 |
public domain.
|
|
33 |
* You are using SQLite in a jurisdiction that does not recognize the
|
|
34 |
right of an author to dedicate their work to the public domain.
|
|
35 |
* You want to hold a tangible legal document as evidence that you
|
|
36 |
have the legal right to use and distribute SQLite.
|
|
37 |
* Your legal department tells you that you have to purchase a
|
|
38 |
license.
|
|
39 |
|
|
40 |
If you feel like you really have to purchase a license for SQLite,
|
|
41 |
Hwaci, the company that employs the architect and principal developers
|
|
42 |
of SQLite, will sell you one. Contributed Code
|
|
43 |
|
|
44 |
In order to keep SQLite completely free and unencumbered by copyright,
|
|
45 |
all new contributors to the SQLite code base are asked to dedicate their
|
|
46 |
contributions to the public domain. If you want to send a patch or
|
|
47 |
enhancement for possible inclusion in the SQLite source tree, please
|
|
48 |
accompany the patch with the following statement:
|
|
49 |
|
|
50 |
The author or authors of this code dedicate any and all copyright
|
|
51 |
interest in this code to the public domain. We make this dedication for
|
|
52 |
the benefit of the public at large and to the detriment of our heirs and
|
|
53 |
successors. We intend this dedication to be an overt act of
|
|
54 |
relinquishment in perpetuity of all present and future rights to this
|
|
55 |
code under copyright law.
|
|
56 |
|
|
57 |
We are not able to accept patches or changes to SQLite that are not
|
|
58 |
accompanied by a statement such as the above. In addition, if you make
|
|
59 |
changes or enhancements as an employee, then a simple statement such as
|
|
60 |
the above is insufficient. You must also send by surface mail a
|
|
61 |
copyright release signed by a company officer. A signed original of the
|
|
62 |
copyright release should be mailed to:
|
|
63 |
|
|
64 |
Hwaci
|
|
65 |
6200 Maple Cove Lane
|
|
66 |
Charlotte, NC 28269
|
|
67 |
USA
|
|
68 |
|
|
69 |
A template copyright release is available in PDF or HTML. You can use
|
|
70 |
this release to make future changes. This page last modified 2007/11/14
|
|
71 |
15:25:42 UTC
|
|
72 |
|