From c61f6463b17158bdb1a8741038cb7c54a951e2cd Mon Sep 17 00:00:00 2001 From: Ton Roosendaal Date: Mon, 6 Jun 2005 12:18:44 +0000 Subject: Updated BL text. This option has not been used for 3 years, and is very unlikely to happen anytime. --- doc/BL-license.txt | 63 ++++++++++++++++++++++-------------------------------- 1 file changed, 25 insertions(+), 38 deletions(-) diff --git a/doc/BL-license.txt b/doc/BL-license.txt index 606d3ef6cef..2ba19e96ec3 100644 --- a/doc/BL-license.txt +++ b/doc/BL-license.txt @@ -1,48 +1,35 @@ -Blender License 1.0 (the "BL", see http://www.blender.org/BL/ ). +Blender License (the "BL", see http://www.blender.org/BL/ ). -Copyright (C) 2002 Blender Foundation. All Rights Reserved. +Copyright (C) 2002-2005 Blender Foundation. All Rights Reserved. -For teams that don't want to operate under the GPL, we're also offering -this "non-GPL" Blender License option. This means that you can download -the latest sources and tools via FTP or CVS from our site and sign an -additional agreement with the Blender Foundation, so you can keep your -source modifications confidential. Contact the Blender Foundation via -email at license@blender.org so we can discuss how we handle the -practical matters. +This text supersedes the previous BL description, called Blender License 1.0. -A signed agreement allows you to do business with proprietary code, make -special derived versions, sell executables, projects or services, -provided that: +When the Blender source code was released in 2002, the Blender Foundation reserved +the right to offer licenses outside of the GNU GPL. This so-called "dual license" +model was chosen to provide potential revenues for the Blender Foundation. -1. The BL-ed code remains copyrighted by the original owners, and cannot -be transferred to other parties +The BL has not been activated yet. Partially because; -2. The BL-ed code cannot be published or re-distributed in any way, and -only be available for the internal staff that works directly on the -software itself. Employees of partners with which you co-develop on the -projects that include BL-ed code are considered 'internal staff' also. +- there has to be a clear benefit for Blender itself and its community of + developers and users. +- the developers who have copyrighted additions to the source code need to approve + the decision. +- the (c) holder NaN Holding has to approve on a standard License Contract -3. The BL-ed code can be used (sold, distributed) in parts or in its -whole only as an executable or as a compiled library/module and its -header files. +But most important; -4. The usage of the name Blender or the Blender logo is not included in -this license. Instead 'including Blender Foundation release X' (or -similar) can be used, with 'X' the version number of the initial Blender -Foundation release which you started with. +- the Blender Foundation is financially healthy, based on community support + (e-shop sales), sponsoring and subsidy grants +- current focus for the Blender Foundation is to not set up any commercial + activity related to Blender development. +- the GNU GPL provides sufficient freedom for third parties to conduct business + with Blender -5. Note that this BL has no authority over some of the external -libraries licenses which Blender links with. +For these reasons we've decided to cancel the BL offering for an indefinite period. -Additionally you get : +Third parties interested to discuss usage or exploitation of Blender can email +license@blender.org for further information. -1. The right to use Blender Foundation source updates for a 1 year -period. - -2. Support. Details to be determined by the additional agreement. - -You are invited to donate your proprietary changes back to the open -source community after a reasonable time period. You are of course free -to choose not to do this. - -End of BL terms and conditions. +Ton Roosendaal +Chairman Blender Foundation. +June 2005 \ No newline at end of file -- cgit v1.2.3