License Change
0 views
Skip to first unread message
Stephen Chin
Feb 2, 2009, 7:32:20 AM2/2/09
to widget...@googlegroups.com
I know we had this discussion before, but it looks like the GPL +
Classpath Exception is not doing exactly what we thought it was.
The intent of the open-source license change was to keep the core framework protected, while allowing Widget authors to choose their own licenses for their Widgets. Unfortunately, someone a little better versed in open-source licensing pointed out the following from the GPL FAQ:
*If a program released under the GPL uses plug-ins, what are the requirements for the licenses of a plug-in?*
It depends on how the program invokes its plug-ins. If the program
uses fork and exec to invoke plug-ins, then the plug-ins are
separate programs, so the license for the main program makes no
requirements for them.
If the program dynamically links plug-ins, and they make function
calls to each other and share data structures, we believe they
form a single program, which must be treated as an extension of
both the main program and the plug-ins. This means the plug-ins
must be released under the GPL or a GPL-compatible free software
license, and that the terms of the GPL must be followed when those
plug-ins are distributed.
If the program dynamically links plug-ins, but the communication
between them is limited to invoking the ‘main’ function of the
plug-in with some options and waiting for it to return, that is a
borderline case.
As a result, anyone who creates widgets for WidgetFX would also be required to choose a GPL-compatible license for their Widget, which was not the original intent of the license change.
I am proposing that we change the licensing of WidgetFX to a BSD-style license for the following reasons:
The plan would be to change the license on the next major version (1.1) due out in a couple weeks after the JavaFX 1.1 release.
Cheers,
The intent of the open-source license change was to keep the core framework protected, while allowing Widget authors to choose their own licenses for their Widgets. Unfortunately, someone a little better versed in open-source licensing pointed out the following from the GPL FAQ:
*If a program released under the GPL uses plug-ins, what are the requirements for the licenses of a plug-in?*
It depends on how the program invokes its plug-ins. If the program
uses fork and exec to invoke plug-ins, then the plug-ins are
separate programs, so the license for the main program makes no
requirements for them.
If the program dynamically links plug-ins, and they make function
calls to each other and share data structures, we believe they
form a single program, which must be treated as an extension of
both the main program and the plug-ins. This means the plug-ins
must be released under the GPL or a GPL-compatible free software
license, and that the terms of the GPL must be followed when those
plug-ins are distributed.
If the program dynamically links plug-ins, but the communication
between them is limited to invoking the ‘main’ function of the
plug-in with some options and waiting for it to return, that is a
borderline case.
As a result, anyone who creates widgets for WidgetFX would also be required to choose a GPL-compatible license for their Widget, which was not the original intent of the license change.
I am proposing that we change the licensing of WidgetFX to a BSD-style license for the following reasons:
- This would remove the restriction on widget authors to have a GPL-compatible license (which is important for commercial users)
- The BSD license is compatible with GPL v2, which is used widely by Sun on Java libraries (Apache License v2 is incompatible, and may produce licensing issues)
The plan would be to change the license on the next major version (1.1) due out in a couple weeks after the JavaFX 1.1 release.
Cheers,
Stephen Chin
Feb 16, 2009, 3:08:06 AM2/16/09
to widget...@googlegroups.com
Since no one responded, I guess we are go for the license change.
Since we have a release vehicle due to the JavaFX 1.1 release, this
seems as good a time to make the change as any.
You mind doing the honors, Keith? (Take a look at the JFXtras codebase for the basic BSD template, and don't forget to update the Google Code website)
Cheers,
--Steve
You mind doing the honors, Keith? (Take a look at the JFXtras codebase for the basic BSD template, and don't forget to update the Google Code website)
Cheers,
--Steve
Pär Dahlberg
Feb 16, 2009, 4:49:32 AM2/16/09
to widget...@googlegroups.com
The first license message was strange, it looks like I got it about two weeks after you sent it.
Anyway to give some response, BSD sounds good :)
BTW, it's also good to know that plugins are treated as part of the original program in GPL.
Reply all
Reply to author
Forward
0 new messages