The Free Public License (FPL)

Published on 2022-01-07

Permission to use, copy, modify, and/or distribute this work for any purpose with or without fee is hereby granted.

THE WORK IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS WORK INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS WORK.


A link to the FPL in plain text can be found here.

Goal

A professional-environment-friendly license that is Public Domain Equivalent (Like CC0, Unlicense, WTFPL, and 0BSD), but with the distinction of not being specific to software.

Recipe

  1. Copy 0BSD
  2. Replace "software" with "work"
  3. ?????
  4. Profit Freedom

FAQ

Why not the WTFPL?

Personally, I like the WTFPL. Unfortunately, though, it's not available for use in most workplaces.

I am as anti-copyright as they comeI would love for everyone to use the WTFPL or its variants that maintain its vulgarity. Though, if what prevents someone from releasing truly free software out into the wild is the name of the license, then my ego shouldn't step in the way of that.

Why not CC0?

Too much language. The Free Public License is straight to the point. The Free Public License also makes zero mention of Public Domain, which is by-design.

Why not the Unlicense?

Same as CC0, it makes mention of the Public Domain. Additionally, the Unlicense is meant for software only. The Free Public License is not restricted to only software. All works can use the Free Public License.

Why not 0BSD?

Like the Unlicense, 0BSD is meant for software only.