Re:Why I’d like a “license type” setting for GitHub projects
by tptacek on Thursday April 05, 2012 @10:50AM
(#3802745)
And when the drop-down disagrees with the COPYING or LICENSE file...?
[ Parent
| on HN ]
Re:Why I’d like a “license type” setting for GitHub projects
by madrobby on Thursday April 05, 2012 @11:03AM
(#3802832)
The LICENSE or COPYING file in the repository wins, obviously. Also, not everyone would set the setting. But it's a start.
Re:Why I’d like a “license type” setting for GitHub projects
by tptacek on Thursday April 05, 2012 @11:06AM
(#3802847)
Just seems like a source of potentially expensive misunderstandings.
Re:Why I’d like a “license type” setting for GitHub projects
by there on Thursday April 05, 2012 @11:48AM
(#3803080)
Sourceforge and Google Code have had these license options available to show on project pages forever. I think it'll be fine.
Re:Why I’d like a “license type” setting for GitHub projects
by tptacek on Thursday April 05, 2012 @01:00PM
(#3803462)
Fair enough!
Re:Why I’d like a “license type” setting for GitHub projects
by yummyfajitas on Thursday April 05, 2012 @11:31AM
(#3802990)
One obvious solution is for github to autodetect the license if a LICENSE file is present. This will work in most cases, most people just copy&paste one of a small set of licenses.
Re:Why I’d like a “license type” setting for GitHub projects
by Manfred on Thursday April 05, 2012 @10:52AM
(#3802760)
Then you send a quick note to the owner of the repository to ask him what's up.
Re:Why I’d like a “license type” setting for GitHub projects
by DannyBee on Thursday April 05, 2012 @11:00AM
(#3802817)
As a guy who sends these notes, the response rate drops very quickly if the project hasn't been touched in the past year, and this is not uncommon.
So you end up with a lot of badly marked or unmarked open source, which isn't great.
Re:Why I’d like a “license type” setting for GitHub projects
by rubyruy on Thursday April 05, 2012 @11:12AM
(#3802876)
The license/copying file that is actually distributed with the code still is what you have to go by.
Without license information you MUST assume full copyright sadly.
Re:Why I’d like a “license type” setting for GitHub projects
by DannyBee on Thursday April 05, 2012 @11:30AM
(#3802988)
I agree.
Sadly, we also run into plenty of cases distributing LICENSE files that don't match file headers, etc.
Re:Why I’d like a “license type” setting for GitHub projects
by rubyruy on Thursday April 05, 2012 @12:14PM
(#3803232)
Yeah it's just unfortunate. It's effectively like attempting to distribute a broken library. People simply can't use it, and even though it may have had the workings of a good solution for many people, you're just not going to get any users/contributors. shrug