On 3/16/07, Vlad <[EMAIL PROTECTED]> wrote:
The only alternative to the paperwork-intensive approach described above is to explicitly list the conditions for submitting code in every file. This way, no contributor can claim to not have known or agreed to the conditions, because they themselves are either uploading the conditions (in the case of "svn add") or leaving the conditions intact within an existing file that they've modified (in the case of "svn commit"). So I think the policy that Timothy has outlined at http://wiki.duskglow.com/tiki-index.php?page=Subversion+Commit+Policy is appropriate.
There are still some files in the repository that don't bear the license agreement. Some of them were written by Patrick McNamara who I'm sure is highly unlikely to object. Also, some of what he wrote is not code that would be put into a driver but rather code that produces code that would be put into a driver. I think a sensible thing to do would be to go through each file, identify the author, and ask them to add the copyright/license notice. If they refuse (or don't give explicit concent for someone else to do it for them), they get write access revoked, and their files get deleted. This isn't to be harsh--it's to protect THEM from getting ripped off by US. I don't want to steal anyone's stuff, legally or morally. This applies only to critical stuff. There is, for instance, an alternative memory controller. Since I don't intend to use it, I don't care very much what the license is. We should be careful about the exceptions we make, though. -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Favorite book: The Design of Everyday Things, Donald A. Norman, ISBN 0-465-06710-7 _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
