[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#179804: Bloom Public License



The Bloom Public License (BPL) for this program has been changed to
reflect dual GNU GPL and BPL licensing. See http://www.cbloom.com/bpl.txt

Currently the license is:
The Bloom Public License (BPL)
modified May 14, 2002

0. The software may be used or distributed according to the terms of
	the GPL (GNU Public License) at the distributor's option.
	If you do not wish to adhere to the terms of the GPL, you
	may still use my code, but the following points apply.  If
	you do adhere to the terms of the GPL, you may ignore all
	further points in this license.

1. the BPL applies to all software distributed by myself in
	any way, unless explicitly over-ridden by another
	agreement.

2. If you distribute code covered by the BPL you MUST notify
	the recipient.  All modified versions and re-distributions
	of 'BPL code' are still covered by the BPL.

3. BRIEF :
	A. usage which is legal under the GNU Public License (GPL) is
		also legal under the BPL
	B. usage for academic or research or curiousity purposes
		is allowed
	C. usage in strictly Free programs is allowed
		you are not required to make your code free, just your
		binaries.  You may not distribute BPL code in a free
		component of a system which requires payment for optional
		parts.
	D. for usage which is in any way commercial, see below:

4. definitions :

	"BPL code" is any source code covered by the BPL, or any
		compiled program generated directly from BPL code, or
		by minimal or trival modifications of BPL code.

	"user" is someone using software or source code covered by the BPL.

	"user application" is any program or source code or document
		which contains (modified or not) BPL code.  Note that this
		also includes suites of programs, if any program in the suite
		contains BPL code.

5. BPL code may not be sold in any form.

6. user applications must publicly display the fact that they
		contain BPL code, and provide easily accessible reference
		to the author of that code (name,email,etc.).  Wherever
		the full credits for the user application are shown, the
		credits for the BPL code must also be shown.

7. user applications must in no way mis-represent the fact that
		they are not doing the job which is done by the BPL code.

8. user applications must not charge for functionality contained
		in BPL code used.  For example, direct sale of BPL code is
		prohibited, as is sale of compiled BPL applications.
		Users may not charge "distribution fees" for BPL code.

9. The author of the BPL code must be notified prior to using
		any BPL code in a commercial user application.

10. There are no warranties or gaurantees over the behavior or
		safety of BPL code.  The author has no responsiblity for
		the behavior of BPL code.  The user accepts full liablity
		for any damage caused by use of BPL code.

11. The author asserts that publishing this code on a newsgroup, or
		on the web constitutes a fully legal publication with all
		protections and rights implied therein.





Reply to: