| | Re: Moving the License Forward
|
|
(...) And yet you appear to be trying to write one, the contributor agreement. Although I don't have any particular experience in writing licenses, I have done a fair bit of work with them, at one point my company required me to read and understand (...) (20 years ago, 15-Jul-04, to lugnet.cad.dev.org.ldraw)
|
|
| | 2003-2004 LSC Annual Report
|
|
LSC Annual Report August 2003 - July 2004: During this period of time the LSC handled the following issues to completion: - A location was established on the ldraw.org website listing all of the current LDraw library updates. This page is script (...) (20 years ago, 15-Jul-04, to lugnet.cad, lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
|
| | Re: Moving the License Forward
|
|
(...) I agree. (...) Currently LDraw.org has control once it is submitted, so the licence should be agreed to upon submission. You could set it up so authors only have to agree once a file is certified, before including it in the official library, (...) (20 years ago, 14-Jul-04, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: Moving the License Forward
|
|
(...) I think this is a PT policy issue and not a license issue. (...) Per the CA, upon submission to LDraw.org. -Orion (20 years ago, 14-Jul-04, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: Moving the License Forward
|
|
(...) All humor aside, is this really a license issue, or a parts tracker policy issue? I know this has been a big issue in the past and I don't want to ignore it, but I'm not sure it is a license issue. It in some ways asks the question of when (...) (20 years ago, 14-Jul-04, to lugnet.cad.dev.org.ldraw)
|