 | | Re: Moving the License Forward
|
|
(...) I don't follow but see below (...) I think that: a,b,d are covered by the CA "no obigation" clause c is covered by the "Author grants permission to other authors to modify their work" clause but I agree that a rewording may be in order (...) (...) (20 years ago, 12-Jul-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Moving the License Forward
|
|
(...) True. (...) I think the "in perpetuity" phrase above fills this (...) That's good. (...) I think this is good but others might balk at the non-specificness of terms (...) The fist paragraph of the agreement defines "Author" as anyone who (...) (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)
|
| |
| | Re: Moving the License Forward
|
|
(...) Speaking personally [1]: For the initial CA we should contact everyone who's got Submit rights, plus anyone named in a Name: line for whom we have contact details. New users should be asked to accept the CA as part of them getting Submit (...) (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)
|
