Re:Why I’d like a “license type” setting for GitHub projects
by madrobby on Thursday April 05, 2012 @10:57AM
(#3802796)
A list of every type if license can't work, because it needs to be constantly updated and people may want to write their own, etc.
That's why the general type makes much more sense for a quick glimpse if some code is probably suitable license-wise for your project.
Re:Why I’d like a “license type” setting for GitHub projects
by dobs on Thursday April 05, 2012 @12:04PM
(#3803170)
They could just pull the licenses from the OSI's list (http://opensource.org/licenses/alphabetical). And people writing their own licenses contributes to the license proliferation problem, so should be generally discouraged (http://en.wikipedia.org/wiki/License_proliferation).
Re:Why I’d like a “license type” setting for GitHub projects
by metamattl on Thursday April 05, 2012 @11:28AM
(#3802975)
You're against the GPL, but you're okay with people writing their own new licenses?
Re:Why I’d like a “license type” setting for GitHub projects
by Sanddancer on Thursday April 05, 2012 @08:12PM
(#3805332)
If one feels that the license is flawed, then why not? It's possible to not like the viral clauses for various reasons, such as incompatibility with other viral licenses, but feel there is some issue, like patents, that are not well-covered under the BSD license, for example.
Re:Why I’d like a “license type” setting for GitHub projects
by dave1010uk on Thursday April 05, 2012 @01:01PM
(#3803465)
List the most popular licences and have an "Other" option. Simple.
I don't like grouping them into 'types'. I think that's too much of a value judgement. Any enterprise's legal department is going to approve or disapprove of specific licenses, so that's what developers like me will be looking for.
Potential issues: * Modified licenses (eg: JSLint's MIT + "do no evil" clause)