Re:Why I’d like a “license type” setting for GitHub projects
by nitrogen on Thursday April 05, 2012 @04:59PM
(#3804604)
The problem is, what do you do about dual/multi licensed projects, or projects which contain code that's under a mixture of licenses?
All questions that were answered over a decade ago by sites like SourceForge. Though not perfect, their solution was using tags for each license, and letting developers tag their project with multiple licenses (among other attributes, like language used, development state, etc.). This tagging system was called the Trove system, but since a software company has named itself "Trove Software", my last few Google queries didn't lead me to the origins of the system, only Freshmeat and SourceForge's references to the name.
All questions that were answered over a decade ago by sites like SourceForge. Though not perfect, their solution was using tags for each license, and letting developers tag their project with multiple licenses (among other attributes, like language used, development state, etc.). This tagging system was called the Trove system, but since a software company has named itself "Trove Software", my last few Google queries didn't lead me to the origins of the system, only Freshmeat and SourceForge's references to the name.
http://sourceforge.net/apps/trac/sourceforge/wiki/Software%2...
http://freecode.com/articles/fm3s-fresh-features-tagging