 | | Re: Contributor Agreement License details - updated version
|
|
(...) This is also not true. BlockCAD has its own part library, not at all connected to the LDRAW library, but BlockCAD *can* save a model in the LDRAW format, thereby making it possible to render a BlockCAD model with the LDRAW compatible programs. (...) (18 years ago, 5-Feb-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details - updated version
|
|
(...) This is definitely wrong! There is nothing unique with the LDRAW library. It doesn't have a special place in the universe - it's just another information collection. My BlockCAD program can load *some* LDRAW model files and render a picture (...) (18 years ago, 5-Feb-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details - updated version
|
|
(...) Actually there is. Anton Raves' library comes immediately to mind. Using that you're not using any information from the LDRAW parts, only the placement information in the model file. And his is not the only library of Lego parts in the (...) (18 years ago, 5-Feb-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details - updated version
|
|
In lugnet.cad.dev.org.ldraw, Timothy Gould wrote: [snip-snap] (...) the steerco has considered the option to change the license but considering that we weren't able to track down 18 people last time (URL) (we are still 33 parts behind in the rewrite (...) (18 years ago, 5-Feb-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details - updated version
|
|
(...) don, you wouldn't have a model file at all without the parts library. at least not without extreme effort because of the missing visual feedback. I'll give you some codes: CM051P09.dat, HF300P09.dat, CM060P14.dat, CM053P03.dat, CM250P02.dat (...) (18 years ago, 5-Feb-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details - updated version
|
|
(...) If you are referring to the non-pursuit section of the readme it is most definitely in accord with the license. As you say a license is only as good as its enforcement but stating a policy of enforcement does not change the license. As an (...) (18 years ago, 5-Feb-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details - updated version
|
|
(...) I agree. The way the readme puts it is not in accord with what the license requires. Furthermore, because there is a disclaimer in readme that it is not a license, that whole bit can and should be ignored and only the license followed. If (...) (18 years ago, 5-Feb-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details - updated version
|
|
(...) I'm not sure I agree with the ethical imperative argument. There are plenty of old laws on statute books that no-one follows or expects to follow but are still there. Either way, ethical decisions are made on an individual basis (including the (...) (18 years ago, 5-Feb-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details - updated version
|
|
(...) In that case I agree it wouldn't be a derivative work. I am becoming more and more convinced that an MPD isn't actually a derivative work. (...) If people are willing to go to the effort of making or using an alternate part library in order to (...) (18 years ago, 5-Feb-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details - updated version
|
|
(...) Sorry, that doesn't work for me. The license describes how someone must behave; lack of prosecution for non-compliance doesn't erase the ethical imperative to follow the agreement. And, since the non-commercial disclaimer is not actually part (...) (18 years ago, 5-Feb-07, to lugnet.cad.dev.org.ldraw)
|
