Subject:
|
Re: License - again
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Wed, 13 Dec 2000 01:29:00 GMT
|
Viewed:
|
1413 times
|
| |
|
|
I like the artistic license, but not for a library of parts.
The key issue to deal with in the LCAD library is "abandonment".
The license must allow active LCAD people to maintain, modify,
convert and distribute parts that people author. The artistic
license would prevent people from fixing a "bug" in your part,
or modifying it to use new curve primitives.
It would also prevent them from taking your part and making it
look really ugly, which is why some people like it. Whether or
not you want to permit someone to create an image of a
concentration camp and list your name in the credits is a
another topic entirely...
And, IMHO (IANAL), TLG would not touch the DAT format with a
10 foot pole, due to legal concerns. The best we can hope for
is that they produce a text output file that would be simple
to convert. OTOH, I'm suprised no one has been approached by
Ritvik -- I imagine an LDRAW disk in a Megabloks set would
increase their market image.
To the best of my knowledge, TLG does have a database of all
parts. Only trouble is, the mold-quality 3D file for a
helmet is over 10 MB. <shameless plug> Not all rendering
programs could handle sets made from parts of that
size</shameless plug>.
-gyug
In lugnet.cad.dev, Erik Olson writes:
> In lugnet.cad.dev, Leonardo Zide writes:
>
> > 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
>
> 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. If GPL were somehow a
> requirement, I would just kill the project out of principle.
>
> My reasons are probably the usual ones that led to the creation of the LGPL and
> other licenses, which don't try to impose terms on your original work (requiring
> distribution of just the LGPL portions.)
>
> As part of developing BrickDraw3D, I contribute source code to an LGPL project,
> Quesa, a 3D graphics framework. Portions of my code are also in LDGLite. I
> believe I am giving adequate value in trade by contributing to the libraries I
> use--perhaps eventually the parts library too. Certainly I am creating a parts-
> editor, which opens even more doors.
>
> Like your position on the parts themselves, I am protective of my work too. The
> way I see it, strict GPL undermines cooperation.
>
> For the record, I intend to release source code to my app under Artistic
> License. (I like Perl...) Beyond some level of development, I will try to go
> the shareware route--and there, again, is why a parts license is necessary.
>
> -Erik
|
|
Message has 2 Replies:
 | | Re: License - again
|
| (...) Oh, artistic is definitely not the best license to start from for parts. I don't think it achieves anyone's goals in that direction. Artistic is well suited for an application. I'd have to review this thread's history to be aware of the (...) (24 years ago, 13-Dec-00, to lugnet.cad.dev)
| | | Re: License - again
|
| (...) BTW, you're talking about the "contributor's agreement" here, not a user or distribution license. I agree completely. My ideal "contributor's agreement" would be to act like each contributed work existed as two independent entities, which had (...) (24 years ago, 13-Dec-00, to lugnet.cad.dev)
|
Message is in Reply To:
| | 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)
|
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
|
|
|
|
