[License-review] Request for OSI Approval: Tiwaz License, version 1.0 (New License)

[Loncothad]

-- Repost of the message I sent earlier to Josh Berkus but didn't send to the mailing list because of an error from my side --

Hi. Thank you for your response and questions. 

> where the opinions on these flaws in the MPL, and the revisions to them, drafted by an attorney or with the help of one? 

Opinions on the mentioned "flaws" come from open source community members I know who are concerned that Mozilla, as the steward of MPL 2.0, might exploit the "or later" clause (MPL 2.0 Section 10.2). Another community member developed a different approach to address this concern: the "Immutable License" (https://github.com/cull-os/carcass/blob/master/LICENSE.md). However, that license takes a completely different (more "distributed") approach, and its creator neither wishes to be a License Steward nor seeks OSI approval for it. This is where our views diverge, as I am seeking OSI approval for the Tiwaz License to establish it as a valuable tool for the wider Open Source community. My goal with the Tiwaz License is to offer an OSI-approved option, within a familiar MPL-like structure, that provides this version immutability, thereby guarding against the potential "exploits" associated with "or later" clauses. 

I have no information on whether those community members discussed this with an attorney. Personally, I've discussed licensing matters generally with a friend of mine who is a legal counsel, but software licensing is not his specific line of work. 

The Tiwaz License, version 1.0, was drafted by me, building directly upon the MPL 2.0 framework. While I did discuss general licensing concepts with him, as mentioned, software licensing is not his area of expertise, and this did not constitute formal legal review or drafting assistance for the license text itself. 

> You're aware that removing the Secondary License clauses can make Tiwaz-license software incompatible with GPL-licensed software for combined works? 

Yes, that is intended. 

> Finally, where does the name "Tiwaz" come from? 

The name "Tiwaz" comes from the rune Tiwaz (ᛏ) of the Elder Futhark, the older runic alphabet used by Germanic peoples. Its meaning is often associated with justice, honor, and duty, mirroring qualities attributed to the god Tyr. I initially considered a name like "Software Public License" but chose "Tiwaz" after some reflection. The "rune" inspiration also comes from the game "The Binding of Isaac," in which these symbols serve as usable items that grant unique effects. 

> Note that the tiwaz.fyi domain appears to be non-functional right now. 

The GitHub organization (https://github.com/tiwaz-license/) serves as the primary public repository and central point of information for the Tiwaz License at this time. I do plan to make tiwaz.fyi functional with, at a minimum, the license text and links to the GitHub resources in the near future to provide a dedicated web presence for the license.

----------------------------------------

From: "Josh Berkus" <josh.berkus at opensource.org>
Sent: 5/28/25 3:39 AM
To: me at loncothad.cc, License submissions for OSI review <license-review at lists.opensource.org>
Subject: Re: [License-review] Request for OSI Approval: Tiwaz License, version 1.0 (New License)

On 5/26/25 15:57, Loncothad wrote:

> This license comes as a stricter and disambiguated version of the

> "Mozilla Public License Version 2.0". More info on that in the README of

> the main repository of the "Tiwaz License, version 1.0" - https://

> github.com/tiwaz-license/version-1.0/blob/draft/README.md <https://

> github.com/tiwaz-license/version-1.0/blob/draft/README.md>.

Thank you for submitting this license proposal. Clarification: where

the opinions on these flaws in the MPL, and the revisions to them,

drafted by an attorney or with the help of one? It's not a requirement,

but lets us know how to regard the text of the changes.

You're aware that removing the Secondary License clauses can make

Tiwaz-license software incompatible with GPL-licensed software for

combined works? Just making sure that's intended effect.

Finally, where does the name "Tiwaz" come from? Note that the tiwaz.fyi

domain appears to be non-functional right now.

--

-- Josh Berkus

OSI Board Member
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20250528/03446b60/attachment-0001.htm>