An open source license department within Philips are making problems about the use off ClassBuilder, becasue of the GPL license. It seems that the generated output can be interpret as derived work and thus can potentially fall under the license. I think this was/is never the intention. In order to avoid possible problems and the fact that a potential large group of users can not use ClassBuilder we should consider what to do about this situation. If one company is holding back, others can do the same and I think we want an as large as possible user group. We should perhaps select another license or add a specific statement about the use of the generated output. It seems that a similar statement is made for the gcc compiler. The same holds for the macro's they do not contain any license information, we should perhaps include some statement there as well that people are free to use it as is. How can we resolve these issues? What are the options? Does the use of wxWindows force us to use a certain license or do we have a freedom to select another license such that the commercial use of the generated output is possible. My only intention was to make the ClassBuilder itself public domain and not to imply anything on the use of the generated output. As it is now with the GPL license the use of the generated output seems a bit of a issue.
Jimmy Venema
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
An open source license department within Philips are making problems about the use off ClassBuilder, becasue of the GPL license. It seems that the generated output can be interpret as derived work and thus can potentially fall under the license. I think this was/is never the intention. In order to avoid possible problems and the fact that a potential large group of users can not use ClassBuilder we should consider what to do about this situation. If one company is holding back, others can do the same and I think we want an as large as possible user group. We should perhaps select another license or add a specific statement about the use of the generated output. It seems that a similar statement is made for the gcc compiler. The same holds for the macro's they do not contain any license information, we should perhaps include some statement there as well that people are free to use it as is. How can we resolve these issues? What are the options? Does the use of wxWindows force us to use a certain license or do we have a freedom to select another license such that the commercial use of the generated output is possible. My only intention was to make the ClassBuilder itself public domain and not to imply anything on the use of the generated output. As it is now with the GPL license the use of the generated output seems a bit of a issue.
Jimmy Venema