/ Check-in [05bae020]
Login

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

Overview
Comment:Amplify and clarify reasons for wanting to get a license to use SQLite. (CVS 3681)
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:05bae0204d2387201be4783a11d54b220a4a40e8
User & Date: drh 2007-03-10 20:47:50
Context
2007-03-10
20:50
Fix another typo in copyright.html (CVS 3682) check-in: 92f15864 user: drh tags: trunk
20:47
Amplify and clarify reasons for wanting to get a license to use SQLite. (CVS 3681) check-in: 05bae020 user: drh tags: trunk
18:30
Fix typos in the copyright.html webpage. Ticket #2267 (CVS 3680) check-in: 74a4bfce user: drh tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to www/copyright.tcl.

     1         -set rcsid {$Id: copyright.tcl,v 1.4 2007/03/10 18:30:31 drh Exp $}
            1  +set rcsid {$Id: copyright.tcl,v 1.5 2007/03/10 20:47:50 drh Exp $}
     2      2   source common.tcl
     3      3   header {SQLite Copyright}
     4      4   puts {
     5      5   <h2>SQLite Copyright</h2>
     6      6   
     7      7   <table align="right" vspace="0" hspace="10" border="1" cellpadding="20">
     8      8   <tr><td align="center">
................................................................................
    42     42   No code has been taken from other projects or from the open
    43     43   internet.  Every line of code can be traced back to its original
    44     44   author, and all of those authors have public domain dedications
    45     45   on file.  So the SQLite code base is clean and is
    46     46   uncontaminated with licensed code from other projects.
    47     47   </p>
    48     48   
    49         -<h2>Obtaining A License To Use SQLite</h2>
           49  +<h2>Obtaining An Explicit License To Use SQLite</h2>
           50  +
           51  +<p>
           52  +Even though SQLite is in the public domain and does not require
           53  +a license, some users want to obtain a license anyway.  Some reasons
           54  +for obtaining a license include:
           55  +</p>
           56  +
           57  +<ul>
           58  +<li> You are using SQLite in a jurisdiction that does not recognize
           59  +     the public domain.  </li>
           60  +<li> You are using SQLite in a jurisdiction that does not recognize
           61  +     the right of an author to dedicate their work to the public
           62  +     domain. </li>
           63  +<li> You want to hold a tangible legal document
           64  +     as evidence that you have the legal right to use and distribute
           65  +     SQLite. </li>
           66  +<li> Your legal department tells you that you have to purchase a license.
           67  +     </li>
           68  +</ul>
    50     69   
    51     70   <p>
    52         -If you are using SQLite in a jurisdiction that does not recognize
    53         -the public domain, or if your legal department is uncomfortable with
    54         -the concept of the public domain, you can purchase a license to use
    55         -and distribute SQLite from <a href="http://www.hwaci.com/">Hwaci</a>,
    56         -the company that employees the architect and principal developers
    57         -of SQLite.  For additional information on how to purchase a license
    58         -to use SQLite, please contact:
           71  +If you feel like you really have to purchase a license for SQLite,
           72  +<a href="http://www.hwaci.com/">Hwaci</a>, the company that employees 
           73  +the architect and principal developers of SQLite, will sell you
           74  +one.
           75  +Please contact:
    59     76   </p>
    60     77   
    61     78   <blockquote>
    62     79   D. Richard Hipp <br />
    63     80   Hwaci - Applied Software Research <br />
    64     81   704.948.4565 <br />
    65     82   <a href="mailto:drh@hwaci.com">drh@hwaci.com</a>