Slashdot Mirror

← Back to Stories (view on slashdot.org)

License for Open-Source Software w/ Plugins?

Posted by Cliff on from the stuck-in-a-tricky-situation dept.

ThiagoHP asks: "I have developed MultiMAD, a rapid application development and prototyping for for mobile devices in my master's course, and now I want to share it with the community. It's written in Java and it has a plugin architecture in order to support different mobile device platforms (WAP, J2ME, PalmOS, etc). I want to give the freedom to anybody write their plugins, even closed-source, as long as the tool itself is not modified for them to run. This implies that GPL cannot be used. At the same time, I do not want any closed-source tool based in MultiMAD code, so licenses such as the Apache one cannot be used. Am I right in my assumptions regarding licenses? What license do you suggest?"

3 of 91 comments (clear)

  1. Re:LGPL by NotoriousQ · · Score: 3, Insightful

    Even better is to split the program into two parts. LGPL the core, and GPL the interface.

    --
    badness 10000
  2. That or by hummassa · · Score: 3, Insightful

    license your code under the GPL, and grant an additional exception that plugins can be proprietary. It would work, too... supposing the GPL really forbids dynlinking to proprietary modules, which is disputed.

    --
    It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  3. Just don't sue people who write closed plugins by Anonymous Coward · · Score: 3, Insightful

    Uhm, the GPL doesn't control your app, YOU do. Here's what you can do.

    #1) place the GPL in a file called "GPL".

    #2) Place the following text in a file called "COPYING":

    This program is copyright XYZ and can be distributed under the terms of the GPL (see the file "GPL") plus the following exception: any plugins written for this application are expressly exempt from any obligations required by the GPL. You must include this entire paragraph in any copies you make of this application.

    Jeezuz people, it's YOUR application, you can license it any way you want! You can make it GPL on Tuesdays and MIT on Saturdays. This isn't rocket science, RMS doesn't control your app, you don't assign copyright to the FSF, a little bearded man doesn't pop out of your screen if you choose not to sue people who make closed-source plugins. The GPL doesn't enforce your copyright, YOU DO!