Learn more about how recoin is licensed and how this affects you.
1. What license is recoin released under?
- The net.sourceforge.recoin packages are released under the GNU
LGPL. A copy of this is included with your copy of recoin and can also
be found at http://www.fsf.org/licenses/lgpl.html. Unofficial translations can also be found at http://www.fsf.org/licenses/translations.html.
- The
reclipse Eclipse plugins are released under the Recoin License. A copy
of this is included with your copy of the plugins and can also be found
here.
2. Who owns the copyright to recoin?
The
copyright to recoin and reclipse is held by Jan Hendrik Scheufen. He was the
original author of recoin and continues to actively support the project.
3. Are there any restrictions to your use of recoin?
Any
commercial use, selling or distribution of the reclipse Eclipse
plugins is strictly prohibited. The recoin library which is distributed
under the LGPL may be used, modified and even sold as stated in the
LGPL.
4. May I charge money for recoin?
The
LGPL allows everyone the freedom to do this. The right to charge money
to distribute recoin is part of the definition of "free" software. You
may not sell the reclipse Eclipse plugins since they are released under
a different license (see above).
5. May I remove the "copyright" statements from the source code to recoin?
No, you must keep all copyright notices and credits in the source code.
6. I have modified recoin for my own use. Do I have to release these modifications?
The
LGPL permits anyone to make a modified version for their own use without
the requirement to distribute it or pass on those changes to others.
7. I have written an extension for the reclipse framework. Do I have to release it under the LGPL?
No.
The LGPL allows you to write your own extensions for recoin and to
release those extensions under whatever license you chose.
DISCLAIMER
This
document refers to the software program recoin, Version 0.3 and all
subsequent versions, released under the Recoin License and
copyright recoin.org.
This document is subject to additions, modifications and other changes at any time without notice.
A
lawyer has not prepared this document. You should consult a lawyer
experienced in copyright, licensing and intellectual property for
clarification.
Document Rev. 1 - 7th March 2005
|
