firebird-mirror

mirror of https://github.com/FirebirdSQL/firebird.git synced 2025-01-23 00:03:02 +01:00

History

robocop c63be603a3 small typo		2003-10-05 06:10:10 +00:00
..
IDPL.txt	Added license texts.	2003-09-26 14:25:24 +00:00
LGPL_w_exception.txt	Added license texts.	2003-09-26 14:25:24 +00:00
README.license.usage.txt	small typo	2003-10-05 06:10:10 +00:00

README.license.usage.txt

LICENSES
--------

The applicable and approved licenses for the source files
of the Firebird RDBMS project are:

  1) InterBase Public License (IPL), version 1.0
     http://bdn.borland.com/article/0,1410,30198,00.html

  2) Initial Developer's Public License (IDPL), version 1.0
     http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_idpl

  3) GNU Lesser General Public License (LGPL), version 2.1 or higher
     http://www.gnu.org/licences/lgpl.html
     NOTE: MUST BE USED WITH A SPECIAL EXCEPTION CLAUSE
     (see /doc/license/LGPL_w_exception.txt for details)

The IPL is copyright of Borland Corp., the other licenses are copyright
by the source code authors and contributors.


USAGE RULES
-----------

1) The source code which was released under the IPL must keep this license.
   All modifications / adaptations of this code are still subjects of the IPL.

2) The files that are derived from the IPL covered code, must also keep
   this license. It means that if any new file contains some code covered by
   the IPL, then this file should be released under the IPL too.

3) The new files developed by the members of the Firebird project should
   be released under either the IDPL or the LGPL with exception clause.
   It's up to an author (initial developer) to decide which license should
   be used for his/her code.

4) The new files contributed by people who are not members of the Firebird
   project should follow the rule #3. If an author (initial developer) doesn't
   care about the license to be used, the person who applies the contributed code
   to the CVS tree (a committer) becomes responsible for the license for the
   contributed code.

5) Every non-binary file that exists in the CVS tree, should have a header
   section which describes the license this code is released under. If a file
   contains no header, it means that this code is freeware and nobody owns the
   appropriate copyrights.


You may find the exhibits for the approved licenses in /doc/license directory
of the CVS tree.