 | | Re: License - again
|
|
"Frank Filz" <ffilz@mindspring.com> wrote in message news:3A36A7C6.2C67@m...ing.com... MAJOR SNIPPAGE: (...) Heh... I kinda like the way that sounds :-) Good ideas, BTW, Frank. -- Tim Courtney - tim@zacktron.com (URL) - Centralized LDraw Resources (...) (24 years ago, 12-Dec-00, to lugnet.cad.dev)
|
| |
| | Re: License - again
|
|
(...) If we take that route then I assume that (L)GPL is not going to be used. I think we can also add a clause "other licenses can be negociated with the authors". I also liked the idea of requiring the source code for a conversion program, if the (...) (24 years ago, 12-Dec-00, to lugnet.cad.dev)
|
| |
| | Re: License - again
|
|
(...) Sometimes it's scary how in agreement we are... (...) A differentiation which I think would also be valuable to make is a differentiation between any sort of converter program which uses the definition of the parts in the library to create an (...) (24 years ago, 12-Dec-00, to lugnet.cad.dev)
|
| |
| | Re: License - again
|
|
"Erik Olson" <olsone@spamcop.net> wrote in message news:G5G03K.E93@lugnet.com... (...) either. (...) developer, (...) I'm (...) somehow a (...) LGPL and (...) (requiring (...) project, (...) I (...) libraries I (...) parts- (...) too. The (...) (...) (24 years ago, 12-Dec-00, to lugnet.cad.dev)
|
| |
| | Re: License - again
|
|
(...) I've written some thoughts further down in this thread, but what I know about license details I'll write here (but hasn't this been gone over before?) GPL infects derivative works. LGPL need not. If you want to prohibit commercialization, take (...) (24 years ago, 12-Dec-00, to lugnet.cad.dev)
|
| |
| | 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)
|
