4 ms·
Uh, I think this is wrong. Your code is not a derivative work of Opa, you can release it under whatever permissive license you want. (Of course, if users run it
by a3_nm 15y ago
Uh, I think this is wrong. Your code is not a derivative work of Opa, you can release it under whatever permissive license you want. (Of course, if users run it using Opa, they might have obligations with respect to Opa's license, but this is a different matter.)
- anonymoushn 15y agoThe Opa web site says that I cannot: "Firstly, `‘if I'm using AGPL Opa to develop an app does it need to be AGPL, too?’'. Long story short — yes, it does." It would probably be better for me to consult the license, but I don't plan on reading the license just to make sure that I really can't use a language whose developers don't want me to be able to use it
- Yoric 15y agoI confirm (I'm the one who wrote that FAQ entry). However, if you wish to make your code open-source with a different license, don't hesitate to contact Mathieu.Baudet@mlstate.com, he'll certainly be happy to arrange something.
- a3_nm 15y agoI agree that under the right circumstances, the code would have to be released under the AGPL. I disagree with the fact that you could not also release the code (your code, not including any of MLstate's code) under a permissive license like MIT or WTFPL. If you think you are in a position to forbid this, I would be interested to know your reasoning.