June 9, 2020

Normally Open & Normally Closedsimple templates for restricted terms

I finally heard enough calls for simple templates devs can use to prohibit or allow only specific uses they describe. I’ve tentatively dubbed the results “Normally Open” and “Normally Closed”.

Normally Open says “Everything not prohibited is permitted.” You get to fill in what’s prohibited.

Normally Closed says “Everything not permitted is prohibited.” You get to fill in what’s permitted.

I’m short on time. But those interested in more context, and how these might be useful, can look at “Ethical Subcommons Starter Kit”, published in March of 2019.

A comparison, or “diff”, from Normally Open to Normally Closed follows. A lot this language comes from the Blue Oak Model License 1.0.0, with some later readability improvements from Round Robin 1.0.0. Hopefully the text remains easy to read and follow.

Normally OpenClosed Public License 1.0.0-pre.1

Acceptance

To receive this license, you have to agree to its rules. Those rules are both obligations under that agreement and conditions to your license. Don’t do anything with this software against any rule you can’t or won’t follow.

ProhibitedPermitted Purposes

  1. {You may not use this software for ….}

  2. {You may not use this software to ….}

Each contributor licenses you to do everything with this software that would otherwise infringe their copyright in it, except for Prohibited Purposesbut you may only run this software for Permitted Purposes.

Notices

You must ensure that everyone who gets a copy of any part of this software from you, with or without changes, also gets the text of this license.

Excuse

You’re excused for unknowingly breaking Notices if you take all practical steps to comply within thirty days of learning you broke the rule.

Patent

Each contributor licenses you to do everything with this software that would otherwise infringe any patent claims they can license or become able to license, except for Prohibited Purposesbut you may only run this software for Permitted Purposes.

Reliability

No contributor can revoke this license.

No Liability

As far as the law allows, this software comes as is, without any warranty or condition, and no contributor will be liable to anyone for any damages related to this software or this license, under any kind of legal claim.

There’s a GitHub repository for those into that.

more posts about: Licenses Software

Your thoughts and feedback are always welcome by e-mail.

back to topedit on GitHubrevision history