| [LICENSE] - Clarify EPL Licensing Terms 'human readable' [message #48761] |
Tue, 12 October 2004 23:38 |
Eclipse User |
|
|
|
Originally posted by: ilias.lazaridis.com
[followup to .foundation]
Eclipse should inform the community with 'human readable' short forms of the CPL/EPL license (see footnote [1] as an example).
This would ensure that users, developers, committers and especially Project Leads know about the essential mechanics of the EPL license.
This way confusion and wrong expectations could be avoided (and thus frustrating 'wake-up-experience', which has a negative influence on the image of eclipse).
Documents & faq's are available, but not everyone reads them fully or has the time to extract the complete essence.
-
Some example entries for a compact document:
- If you modify _and_ distribute an EPL licenced plugin, you are *obligated*
- to make the source publicly available
- to keep the source easy modifiable to other programmers, which means essentially
- to have no dependencies to private code
- to included a build process (prefered the original one)
- target: plugin which can be used to replace original plugin
- If you create _and_ distribute an commercial add-in plugin...
[...]
-
An practical example for this is the webtools project:
http://www.eclipse.org/newsportal/article.php?id=1523&gr oup=eclipse.webtools
-
Many time gets lost due to inefficient information of the community.
-
[1]
http://creativecommons.org/licenses/by/2.0/
..
--
http://lazaridis.com
|
|
|
Powered by
FUDForum. Page generated in 0.04681 seconds
Home