- From: Andreas Jungmaier <ajung AT exp-math.uni-essen.de>
- To: Pablo Salinas <pablopesb AT yahoo.com>, discussion AT sctp.de
- Subject: Re: [SCTP-Discussion] License issues
- Date: Fri Jun 27 12:57:02 2003
- List-id: SCTP Discussions <discussion.sctp.de>
- Organization: University Duisburg-Essen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All,
this is a fairly important point for all people that are using
this code in proprietary products:
You may use the library in your projects, but if you
change it (e.g. if you have found and fixed a bug :-) then you
will have to release that code also under LGPL.
So: please notify us (the maintainers) here on this list so
that we can incorporate any bugfixes/performance enhancements/
new features into the main project, so that everyone can benefit
from it.
Also: the example programs that come with sctplib are under
the normal GPL.
Fo copies of LGPL see
http://www.gnu.org/copyleft/lesser.html and
for copies of GPL see
http://www.gnu.org/copyleft/gpl.html
If you do not understand it, ask a lawyer :->
The final 1.0.0 release of the SCTPLB project will contain copies
of both licenses.
Regards,
Andreas
On Thursday 26 June 2003 18:16, Michael Tüxen wrote:
>
Hi Pablo,
>
>
the sctplib is under the LGPL which allows you to use it with
>
your proprietary code and not have to publish your code.
>
>
Changes to the sctplib your are doing have to be published and
>
released under the LGPL.
>
- --
Dipl.-Ing. Andreas Jungmaier
Computer Networking Technology Group
University of Duisburg-Essen
http://www.exp-math.uni-essen.de/~ajung
My PGP Key-ID: D3824AC0
My PGP Key-Fingerprint: 228C 7C2C 3381 2DD4 9998 2812 5C0B 0B04 D382 4AC0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+/CF3XAsLBNOCSsARAhTHAJ0ePpL4yifO/SrUsdW7VlboQqwLXwCg0VI5
cqXPOe/i3Y/09s5FRWIc9dQ=
=MZxT
-----END PGP SIGNATURE-----
Archive powered by MHonArc 2.6.19+.