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?"

1 of 91 comments (clear)

  1. LGPL by A.K.A_Magnet · · Score: 5, Informative

    That's exactly what the LGPL is for.

    Derivative of your code will be in LGPL, but code linked to it (as plugins or using it as a library) have no license requirement.

    Check it out