| Subject | Re: [Firebird-Java] Re: credits |
|---|---|
| Author | Helen Borrie |
| Post date | 2003-06-24T00:38:28Z |
Roman,
At 06:50 PM 23/06/2003 +0000, you wrote:
it's like GPL, then you have to include the licence as a text file with the
software package. You aren't required to package the Jaybird source code
with the product, as long as there is a link to where it can be found.
If your own source code is a modification of the Jaybird source, you have
to license your source under LGPL and include the proper attributions right
in the source code (usually as an addition to the commented text at the top
of each source file) and sign all of the blocks of code that you
contributed. You are also required to offer your modified code back to the
Jaybird project.
As I understand, the question is about credits for use of Jaybird and
Firebird. Something like this, in an About.. box and a README.licensing
file, would be appropriate:
This product uses the Jaybird JDBC/JCA Type 4 driver to connect to the
Firebird relational database. Both products are developed and distributed
free of charge under open source licensing agreements. Jaybird is subject
to the Lesser General Public License (LGPL, or "Gnu Library
License"). Firebird is subject to the InterBase Public License (IPL)
v.1.0, a variant of the Mozilla Public License (MPL) v.1.1.
Details of the licenses may be found in these locations:
LGPL: http://www.opensource.org/licenses/lgpl-license.php
IPL v.1.0: http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_ipl
MPL v.1.1: http://www.opensource.org/licenses/mozilla1.1.php
Sources for Jaybird and Firebird may be found at
http://sourceforge.net/cvs/?group_id=9028
hth
Helen
At 06:50 PM 23/06/2003 +0000, you wrote:
>Hi,I'm not sure about LGPL requirements wrt to publishing the licence. If
>
> > I am just ending up my application and wanted to add credits to the
> > driver's people in the user manual and on line help. What do you thing
> > I shall write ?
>
>I have forwarded your message to Helen Borrie, she should know more on
>this topic.
>
>While waiting for her reply, you can check the LGPL license, but I was
>not able to figure out what exactly you have to include in your
>documentation. I even do not know if you have to include driver source
>code, since it is publically available via SF.net...
it's like GPL, then you have to include the licence as a text file with the
software package. You aren't required to package the Jaybird source code
with the product, as long as there is a link to where it can be found.
If your own source code is a modification of the Jaybird source, you have
to license your source under LGPL and include the proper attributions right
in the source code (usually as an addition to the commented text at the top
of each source file) and sign all of the blocks of code that you
contributed. You are also required to offer your modified code back to the
Jaybird project.
As I understand, the question is about credits for use of Jaybird and
Firebird. Something like this, in an About.. box and a README.licensing
file, would be appropriate:
This product uses the Jaybird JDBC/JCA Type 4 driver to connect to the
Firebird relational database. Both products are developed and distributed
free of charge under open source licensing agreements. Jaybird is subject
to the Lesser General Public License (LGPL, or "Gnu Library
License"). Firebird is subject to the InterBase Public License (IPL)
v.1.0, a variant of the Mozilla Public License (MPL) v.1.1.
Details of the licenses may be found in these locations:
LGPL: http://www.opensource.org/licenses/lgpl-license.php
IPL v.1.0: http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_ipl
MPL v.1.1: http://www.opensource.org/licenses/mozilla1.1.php
Sources for Jaybird and Firebird may be found at
http://sourceforge.net/cvs/?group_id=9028
hth
Helen