Add Zlib as a third licensing option

[lunabunn]

With grovesNL's comment below, let's begin the process to relicense glow as MIT OR Apache-2.0 OR Zlib, adding the Zlib license as a third possible licensing option (for the original issue comment, please refer to the edit history).

Rationale for Relicensing

The MIT license, while otherwise being a very permissive license, forces the burden of including the license text on all end users of the crate. Considering that this license text can (legally) be put literally anywhere, in practice this is often little more than a hassle. This requirement is especially bothersome for glow because it is a low-level bindings crate that most users interact with through other intermediary libraries.

On the other hand, the Zlib license only requires the license text to be included with source distributions of the crate. This grants a degree of protection amongst developers while freeing end users. In goodwill, the license also includes the following notice:

If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

For compatibility with the rest of the Rust ecosystem and downstream crates, which predominantly use MIT OR Apache-2.0, those two licenses should obviously remain as options. Therefore, glow should be relicensed as MIT OR Apache-2.0 OR Zlib to allow users to choose any of the MIT, Apache 2.0, or the Zlib licenses at their option.

Contributor Checkoff

Being a change in license, this requires all contributors who have made copyrightable changes to the glow repository to agree.

Given below is a list of all contributors to the glow project. If you agree to relicensing, please comment

I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to choose any one at their option.

Alternatively, you can also directly tick the checkbox next to your name. If you have any concerns, please comment those in this issue thread as well so that they can be discussed.

• [x] grovesNL
• [x] kvark
• [x] kyren
• [x] Lokathor
• [x] IcanDivideBy0
• [x] TannerRogalsky
• [x] coderedart
• [x] 17cupsofcoffee
• [x] segfault87
• [x] ryanisaacg
• [x] Frizi
• [x] cormac-obrien
• [x] memoryruins
• [x] iceiix
• [x] notdanilo
• [x] tronical
• [x] pum-purum-pum-pum
• [x] rspencer01
• [x] zicklag
• [x] cwfitzgerald
• [x] vtavernier
• [x] Gordon-F
• [x] aqrs
• [x] theypsilon
• [x] Hperigo
• [x] mrk-its
• [x] derezzedex
• [x] jaynus
• [x] DarkRyu550
• [x] SnoozeTime
• [x] Nazariglez
• [x] flukejones
• [x] rhelmot
• [x] Tazdevil971
• [x] prokopyl
• [x] mrDIMAS
• [x] Atul9
• [x] iamralpht
• [x] UE2020
• [x] katyo
• [x] morr0ne
• [x] surban
• [x] caiiiycuk
• [x] icefoxen
• [x] alvinhochun +
• [x] expenses (#216)
• [x] xyning (#217)

[Hperigo]

I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to choose any one at their option.

:)

[derezzedex]

I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to choose any one at their option.

[grovesNL]

Thanks everyone! We'll include zlib from now on 🎉

[mrk-its]

I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to choose any one at their option.

śr., 6 kwi 2022, 10:38 użytkownik Davide @.***> napisał:

I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to choose any one at their option.

— Reply to this email directly, view it on GitHub https://github.com/grovesNL/glow/issues/212#issuecomment-1090004579, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHAVDC2BRXXXLBGIQOCQJ3VDVEP3ANCNFSM5RM5V62A . You are receiving this because you were mentioned.Message ID: @.***>