News for hackers. Stuff that matters.
Re:Octotree – Proprietary Firefox extension contains AGPL-li... by pjfin123 on Saturday October 31, 2020 @07:54PM (#24956241)
Is there a recommended way to license a project as permissively as possible? I like the MIT license because it's widely accepted and short enough that it can be read and understood but what if you're OK with someone using a small (but large enough to be a copyrighted work) piece of your code without bothering to maintain the license.

There's the WTFPL License (https://en.wikipedia.org/wiki/WTFPL) but that doesn't seem like a great option either. For my project (https://github.com/argosopentech/argos-translate) I dual licensed under the MIT and CC0 licenses even though CC0 isn't really designed for software but it seemed reasonable. It seems surprisingly difficult to release code with no conditions besides limiting liability.

There are no comments on this comment yet.