Hi Kevin - this kind of copyright attribution is usually only useful if you're starting a project with a restrictive license such as the GPL, where you fear that you might one day need to have the freedom to choose a less restrictive license. The point being that one institution owns the copyright so they can choose to offer it strategically under less restrictive licenses.
By choosing a liberal license from the start, it really doesn't matter who owns the copyright so long as it's licensed with an utterly liberal license like new BSD or MIT. Daniel On Jan 25, 2010, at 11:04pm, Kevin van Haaren wrote: > Has > any consideration been given to assigning copyright of code (of at > least the general framework and core) to the project itself? I could > see where this might discourage some developers so I'm not convinced > it's a good idea but some other projects use it. Additionally a > distributed copyright, like the linux kernel has, can be a good defense > again license hijacking since all holders would have to agree (but it > gives a minority veto as well.) _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
