diff options
author | root <root@rshg054.dnsready.net> | 2012-04-11 00:01:18 +0000 |
---|---|---|
committer | root <root@rshg054.dnsready.net> | 2012-04-11 00:01:18 +0000 |
commit | 04aff5f70cb7c04abe06ca8eaf8261cbb0eeb378 (patch) | |
tree | 4935a4f0959f9560df7fba4989a0de1dc361884e /community-testing/libfbclient/LICENSE | |
parent | 223ca251f3ce07eb5484be845e631d6ca645b263 (diff) |
Wed Apr 11 00:01:18 UTC 2012
Diffstat (limited to 'community-testing/libfbclient/LICENSE')
-rw-r--r-- | community-testing/libfbclient/LICENSE | 44 |
1 files changed, 44 insertions, 0 deletions
diff --git a/community-testing/libfbclient/LICENSE b/community-testing/libfbclient/LICENSE new file mode 100644 index 000000000..e735b0cc1 --- /dev/null +++ b/community-testing/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. |