firebird/firebird-mirror
firebird/firebird-mirror
8
0
Fork 1
mirror of https://github.com/FirebirdSQL/firebird.git synced 2025-01-22 12:43:02 +01:00
Code Issues

Fix licenses urls , sourcecode tree is moved to SVN from CVS

Browse Source
This commit is contained in:
mapopa 2013-03-28 10:15:31 +00:00
parent e5ee578454
commit 6fd54c9871
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/license/IDPL.txt
View File

@ -3,7 +3,7 @@
* Developer's Public License Version 1.0 (the "License");
* you may not use this file except in compliance with the
* License. You may obtain a copy of the License at
* http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_idpl.
* http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/.
*
* Software distributed under the License is distributed AS IS,
* WITHOUT WARRANTY OF ANY KIND, either express or implied.

10
doc/license/README.license.usage.txt
View File

@ -6,10 +6,10 @@ The applicable and approved licenses for the source files
of the Firebird RDBMS project are:
1) InterBase Public License (IPL), version 1.0
http://www.firebirdsql.org/index.php?op=doc&id=ipl
http://www.firebirdsql.org/en/interbase-public-license
2) Initial Developer's Public License (IDPL), version 1.0
http://www.firebirdsql.org/index.php?op=doc&id=idpl
http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/
The IPL is copyright of Borland Corp., the other licenses are copyright
by the source code authors and contributors.
@ -31,14 +31,14 @@ USAGE RULES
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 SVN 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
5) Every non-binary file that exists in the SVN 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.
of the SVN tree.