From: Nuklear Z. <nuk...@gm...> - 2008-10-10 01:25:05
|
i have a concern about the licensing of wxDevIDE. i realized after thinking about it that using the wxWindows license on a full application, not just a library could allow for some hot head to pretty much make their living on our hard work. hack in the designer for a couple hours and they have a new gui that would take minimal code changes and now they have a new commercial product. (along with a graphic designer for new images.) i have seen dual licensing in some projects, like scintilla. and i know many projects use dependencies of several different licenses. (wxWidgets, TinyXML, ...) instead of releasing the whole code base under one license, i propose we split it. what would make the most sense to gain the largest possible audience and still do what we want would seem to be using a the gnu licenses. one can easily use a free software program on a commercial operating system. it is also available to the free software users and is acceptable to open source as well. the worst that would happen is one would have to write a new "front end" to use in their commercial product. (gui). so gnu gpl for the gui and gnu lgpl for the rest. the linking is a little annoying perhaps, but with a little fore though the plugin manager itself could be written to be a shared library anyway. the basic design of the program as been described would work just fine with this model. and other than the gui code, everything is a separate library. that keeps joe hot head from taking easy road and still gives us what we want. i am not very farmiliar with many other licenses, so that is why i suggested those. i do not like gpl3, i'd license with "gpl2 or at your option any other version." what does everyone else think of that? i did a search on sourceforge.net and i did not see anything in the first three pages that was obviously a complete application using the wxWindows license. i searched for "wxWindows license". Nuklear |