Mercurial > hg > blitz_condensed
comparison docs/licensing.html @ 0:3dc0c5604566
Initial checkin of blitz 2.0 fcs - no installer yet.
author | Dan Creswell <dan.creswell@gmail.com> |
---|---|
date | Sat, 21 Mar 2009 11:00:06 +0000 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
-1:000000000000 | 0:3dc0c5604566 |
---|---|
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> | |
2 <html> | |
3 <head> | |
4 <title>Blitz Licensing</title> | |
5 </head> | |
6 <body> | |
7 <h1>Blitz Licensing</h1> | |
8 | |
9 <h2>Introduction</h2> | |
10 | |
11 The key factor in determining how Blitz's licensing (and that of Sleepycat's with respect to Db) affects you, is whether you plan to use it as is or with modifications. | |
12 | |
13 <h3>Using Blitz Unmodified</h3> | |
14 | |
15 <p>In all cases where you wish to use Blitz unmodified (compiled from source or using binaries), there are minimal licensing requirements. You may do as you wish, including: | |
16 </p> | |
17 <ol> | |
18 <li>Incorporating Blitz into a commercial product.</li> | |
19 <li>Using Blitz for research.</li> | |
20 <li>Using Blitz in another open source project.</li> | |
21 </ol> | |
22 | |
23 <p>The only stipulation is that you obey the requirements in Blitz's license file which, amongst other things, requires that you include a copy of the license in your software release (be it a commercial product or source code release for research purposes).</p> | |
24 | |
25 <h3>Using Blitz in Modified Form</h3> | |
26 | |
27 <p>In the case where you release your modifications publicly, in source code form, the licensing restrictions are identical to those for using Blitz unmodified.</p> | |
28 | |
29 <p>If you make modifications to Blitz and wish to keep them proprietary, you become subject in full to the Sleepycat <a href="http://www.sleepycat.com/download/licensinginfo.shtml">licensing conditions</a>. Under some very limited circumstances, Sleepycat permits usage of Blitz/Db without requiring a commercial license but in the majority of such cases, you will be required to pay for a commercial Db license.</p> | |
30 | |
31 <a NAME="sleepycat"></a><h3>Appendix A - Sleepycat's position on Licensing</h3> | |
32 | |
33 Explained in this email from the Sleepycat sales team: | |
34 | |
35 <pre> | |
36 Dan, I think as long as the customer doesn't see BDB at all, but BDB only runs behind your BSD-licensed Blitz | |
37 application, that your users can use Blitz (and indirectly Berkeley DB) without buying a separate license from | |
38 Sleepycat. As long as they don't modify Blitz or call the Berkeley DB APIs directly, then this use should be all | |
39 right under Sleepycat's public license. | |
40 | |
41 If they should make proprietary modifications to Blitz, or make direct calls to Berkeley DB APIs, then they'd need | |
42 to come to us for a commercial license, or make their own source code publicly available. | |
43 </pre> | |
44 | |
45 <p><div align="center"><a href="../index.html">Back to Documentation</a></div></p> | |
46 </body> | |
47 </html> |