Subject:
|
Re: License - again
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Tue, 12 Dec 2000 01:03:26 GMT
|
Viewed:
|
1691 times
|
| |
|
|
John VanZwieten wrote:
>
> 1. Derivative works:
>
> In a situation where someone uses my parts in an LCad program to create a
> model and make pretty pictures of it, I don't want to restrict in any way
> their claim to copyrights of those pictures or even the model file (as
> long as use of that model file needs the parts library to be viewed.)
Someone gave an example about a text that was written with a
copyrighted font, I think the same principle applies here.
> If that person were to distribute their model in a way that the parts
> library was not needed (for example inlining all the parts) then the
> information about the authorship of the parts should be included in such a
> distribution.
In this case the person is redistributing a part of the library, so he
must comply to the license terms. IANAL.
> Any application which transforms the parts library (i.e. LeoCAD, some VMRL
> converter, or L3P) should also include information about part authorship.
> I know L3P does this nicely, what about LeoCAD?
The text on the homepage says that the parts library was created
mostly by James Jessiman and has a link to his pages. The documentation
also lists the authors (from the time when I wrote it) but it's really
outdated, if anyone has a complete list please send it to me and I'll
update it. If you feel this is not enough, just say what you want to be
changed and I'll do it, I don't want to take credit for other people's
work.
> 2. Commercialization of parts library:
>
> I'm a bit ambivalent about this. On the one hand, I want the parts to be
> used as widely as possible, provided they give proper credit to authors.
> I like the idea that some of the programmers who have contributed here
> would turn LCAD into a commercial success.
>
> At the same time, I'm a little troubled at the thought that I would have
> to pay money to use a product that is completely reliant on the thousands
> of combined hours I and other authors have put into the parts library.
> I'm not quite sure what effect that would have on authors' willingness to
> make future contributions.
I don't think anyone will ever sell a program using our parts but I
also don't want to be forced to pay anything to use such program either.
GPL says that if the library is used in another application then the
application must also be GPL, so you don't need to worry about it.
Leonardo
|
|
Message has 3 Replies:
 | | 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
|
| (...) 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
|
| (...) 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)
|
Message is in Reply To:
| | Re: License - again
|
| "Larry Pieniazek" <lpieniazek@mercator.com> wrote in message news:G58Mzp.JAs@lugnet.com... (...) am (...) wrong (...) vocalism. (...) terms (...) contribute). (...) Perhaps part authors need to do more thinking and talking about this. I must admit (...) (24 years ago, 11-Dec-00, to lugnet.cad.dev)
|
55 Messages in This Thread:
 
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
