News for hackers. Stuff that matters.
Re:New GitHub Terms of Service require removing many open-so... by eikenberry on Wednesday March 01, 2017 @03:29PM (#13767995)
With the exception of CC0, of which there is no equivalent available and which they do say is suitable for software.
Re:New GitHub Terms of Service require removing many open-so... by garaetjjte on Thursday March 02, 2017 @08:38AM (#13773880)
Maybe Unlicense? http://unlicense.org/
Re:New GitHub Terms of Service require removing many open-so... by eridius on Wednesday March 01, 2017 @04:12PM (#13768411)
CC0 looks to be equivalent to the WTFPL.
Re:New GitHub Terms of Service require removing many open-so... by azrazalea on Wednesday March 01, 2017 @05:24PM (#13769141)
More likely to be legally upheld in court though IMHO
Re:New GitHub Terms of Service require removing many open-so... by mirabilos on Thursday March 02, 2017 @07:18AM (#13773508)
True. But CC0 is deprecated by CC themselves and CC requested the OSI to not approve it. It is unclear whether there will be a successor.

But any of the BSD/MIT-ish licences should be close enough to a “gift” for this to work (well they do protect the author/licensor a bit more, but…).

Re:New GitHub Terms of Service require removing many open-so... by incongruousa on Tuesday March 07, 2017 @12:22PM (#13812369)
> CC0 is deprecated by CC themselves

As far as I can tell this is simply false. At https://creativecommons.org/retiredlicenses/ there is a list of "retired" (deprecated) legal tools, which does include a "Public Domain Dedication and Certification" but in the right column says "Replaced by two separate tools: the CC0 Public Domain Dedication and the Public Domain Mark." Furthermore, at the top of the page it says "CC will no longer offer these licenses via its license chooser or other mechanism for any future work" and if you click on the link (https://creativecommons.org/choose/) there is a "Want public domain instead?" link to https://creativecommons.org/publicdomain/ which prominently features the CC0 dedication.

So you can see that CC0 is still recommended it and it is in current use. Mike Linksvayer (former VP of Creative Commons) uses and recommends it: http://gondwanaland.com/mlog/2013/11/25/upgrade-to-0/

> CC requested the OSI to not approve it

I actually read through the OSI mailing list thread about the CC0 dedication once, and as far as I recall the OSI people (I think it was Bruce Perens) had reservations and eventually the CC side decided it wasn't worth pursuing, see https://opensource.org/faq#cc-zero for the OSI summary.