To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.dev.org.ldrawOpen lugnet.cad.dev.org.ldraw in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / Organizations / LDraw / 3221
  Re: Moving the License Forward
 
(...) I would hope that any changes made to a part file would include attribution to the original author(s). Perhaps this should be spelled out in the license? Other than this one little issue, I like what I see. Putting these two licenses into (...) (20 years ago, 12-Jul-04, to lugnet.cad.dev.org.ldraw)
 
  Re: Moving the License Forward
 
(...) That might be a good idea. We do have standing policies for most situations; everything from making minor fixes to using someone else's code in a new part to rearranging an existing file into new file(s) to entirely rewriting an existing part. (...) (20 years ago, 12-Jul-04, to lugnet.cad.dev.org.ldraw)
 
  Re: Moving the License Forward
 
(...) Standing policies, yes, but programmatic enforcement, no. Too much in this arena relies on you and I applying those policies correctly in the parts updates. And there is always going to have to be some flexibility that needs admin judgement. (...) (20 years ago, 12-Jul-04, to lugnet.cad.dev.org.ldraw)
 
  Re: Moving the License Forward
 
BTW, for everything I wrote earlier in this thread, c/Name:/Author:/. Thanks. (...) I'm open to more programmatic enforcement, but I'm not seeing what that would be like. For this discussion, I'd be happy if there is mention that attribution (...) (20 years ago, 12-Jul-04, to lugnet.cad.dev.org.ldraw)

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR