News for hackers. Stuff that matters.
Re:Amazon: Not OK – Why we had to change Elastic licensing by signal11 on Tuesday January 19, 2021 @10:22AM (#25834248)
I think "OSI Approved Open Source License" could easily be an OSI trademark, if it's not already.

Ironicallly, like many other organizations, Elastic themselves have used OSI's approval as a benchmark for 'open source'[1]:

> Is X-Pack now open source?

> Updated on 2018-04-24 with a link to the Elastic License

> Open source licensing maintains a strict definition from the Open Source Initiative (OSI).

> As of 6.3, the X-Pack code is open under the Elastic License. However, it will not be 'open source' as it will not be covered by an OSI approved license. The interaction model for open X-Pack will be identical to the open source Elastic Stack, including the ability to inspect code, create issues and open pull requests via our existing GitHub repositories.

[1] https://www.elastic.co/what-is/open-x-pack

Re:Amazon: Not OK – Why we had to change Elastic licensing by un_ess on Tuesday January 19, 2021 @10:36AM (#25834446)
https://opensource.org/trademark-guidelines lists OSI's policy for trademark usage.

3. Usage that Require Prior Written Approval 3.1. Distributing software under a license approved by OSI ("OSI Approved License")

Re:Amazon: Not OK – Why we had to change Elastic licensing by gpm on Tuesday January 19, 2021 @10:27AM (#25834310)
> I think "OSI Approved Open Source License" could easily be an OSI trademark, if it's not already.

Something along those lines is trademarked