|
|
 | | Re: License - again
|
| (...) Pardon me for jumping into the middle here, but as an application developer, this is my statement on this point: I've put in about a hundred hours into my parts-using app BrickDraw3D. I'm willing to give the program away but not on GPL terms. (...) (24 years ago, 12-Dec-00, to lugnet.cad.dev)
| | | | | Re: License - again
|
| (...) Right. And that's my problem with GPL in a nutshell. It leaks into stuff. Now, we've reasonably outlined how the parts license doesn't leak into stuff like published designs, renderings, instruction sets, etc. But if licensing the parts (...) (24 years ago, 12-Dec-00, to lugnet.cad.dev)
| | | | | Re: License - again
|
| (...) I'm not absolutely convinced that it's good to require any program which uses the library to be GPLed, but what I am absolutely convinced is that we don't want to restrict a program which uses a proprietary file format and parts library from (...) (24 years ago, 12-Dec-00, to lugnet.cad.dev)
| | | | | Re: License - again
|
| "Leonardo Zide" <leonardo@centroin.com.br> wrote in message news:3A35795E.D2224C....com.br... (...) create a (...) way (...) such a (...) VMRL (...) authorship. (...) The ideal would be to somehow have the author's name associated with the part, (...) (24 years ago, 12-Dec-00, to lugnet.cad.dev)
| | | | | Re: License - again
|
| (...) Someone gave an example about a text that was written with a copyrighted font, I think the same principle applies here. (...) In this case the person is redistributing a part of the library, so he must comply to the license terms. IANAL. (...) (...) (24 years ago, 12-Dec-00, to lugnet.cad.dev)
|
|
