summaryrefslogtreecommitdiff
path: root/community-staging/libfbclient/LICENSE
diff options
context:
space:
mode:
authorroot <root@rshg047.dnsready.net>2011-06-05 22:48:57 +0000
committerroot <root@rshg047.dnsready.net>2011-06-05 22:48:57 +0000
commit3695b5d62c2aef6e82abc95d775a2ebd89bce081 (patch)
treedb3a874c568e5f5ad3dfe651ceda1df63d5f354f /community-staging/libfbclient/LICENSE
parent80ba845c7cb571644d9dea61b9872c393d128c37 (diff)
Sun Jun 5 22:48:57 UTC 2011
Diffstat (limited to 'community-staging/libfbclient/LICENSE')
-rw-r--r--community-staging/libfbclient/LICENSE44
1 files changed, 44 insertions, 0 deletions
diff --git a/community-staging/libfbclient/LICENSE b/community-staging/libfbclient/LICENSE
new file mode 100644
index 000000000..e735b0cc1
--- /dev/null
+++ b/community-staging/libfbclient/LICENSE
@@ -0,0 +1,44 @@
+
+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
+
+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 the IDPL.
+
+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
+ specify the license to be used, the person who applies the contributed code
+ to the CVS tree (a committer) becomes responsible for the license assigned
+ to 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.