Consider relicensing CC0 code to another license (MIT?)

[Conan-Kudo]

Parts of this project have code under the CC0 license. However, Fedora changed its policy last year on CC0 for code such that it's not longer permitted. The reasoning can be viewed here.

Would you please consider relicensing the code under CC0-1.0 to MIT to align it with the rest of the project?

[checklist below is by @mr-c ]

• https://github.com/nemequ/portable-snippets/
• https://github.com/nemequ/hedley , see Consider an alternative to CC0-1.0 nemequ/hedley#56

The remaining files that would need dual-licensing are

• amalgamate.py
  • @nemequ
  • @tlively
• simde/simde-align.h
  • @nemequ
  • @jsbache
• simde/simde-arch.h
  • @nemequ
  • @himanshi18037
  • @rosbif
  • @FlyGoat
  • @ashnewmanjones
  • @ktgw0316
  • @makise-homura
  • @simba611
  • @tommyvct
  • @Glitch18
  • @dhbloo
• simde/simde-detect-clang.h
  • @nemequ
  • @mr-c
• simde/simde-f16.h
  • contains portions by @nemequ
  • that are heavily based upon CC0 code by @rygorous

[mr-c]

Hello Conan-Kudo.

[I moved the checklist to the original post]

As the authors of each file agree to dual-licensing (even a comment on this issue would suffice) then we can update the file headers & SPDX identifiers

[tommyvct]

I'm fine with the dual licensing.

Why did fedora change its policy that doesn't allow CC0 anymore?

[mr-c]

Thanks @tommyvct ; their reasoning is at https://lists.fedoraproject.org/archives/list/[email protected]/message/RRYM3CLYJYW64VSQIXY6IF3TCDZGS6LM/ ; my understanding is that Fedora doesn't like that CC0 doesn't include patent rights and thus makes it a bad fit for a code license (as opposed to a content license).

[Conan-Kudo]

It's more that it explicitly doesn't allow/include a patent grant. A code license should either include a patent grant or not say anything about patents at all, basically.

[rosbif]

Hi Michael, It seems that I am concerned by a (probably minuscule) part of simde-arch.h. I agree to dual-licensing with MIT for this file and also for any other files you may find in SIMDe for which I have a credit. Best regards, Christopher Moore (aka rosbif) Le 01/04/2023 à 11:09, Michael R. Crusoe a écrit :

…

Hello Conan-Kudo. The affected files are mostly from https://github.com/nemequ/portable-snippets/ & https://github.com/nemequ/hedley ; so I suggest asking there to dual-license with MIT; then I can sync the changes here. For Hedley, I see that nemequ/hedley#56 <nemequ/hedley#56> was already opened The remaining files that would need dual-licensing are * amalgamate.py <https://github.com/simd-everywhere/simde/blob/master/amalgamate.py> by @nemequ <https://github.com/nemequ> and @tlively <https://github.com/tlively> * simde/simde-align.h <https://github.com/simd-everywhere/simde/blob/master/simde/simde-align.h> by @nemequ <https://github.com/nemequ> and @jsbache <https://github.com/jsbache> * simde/simde-arch.h <https://github.com/simd-everywhere/simde/blob/master/simde/simde-arch.h> by @nemequ <https://github.com/nemequ> @himanshi18037 <https://github.com/himanshi18037> @rosbif <https://github.com/rosbif> @FlyGoat <https://github.com/FlyGoat> @ashnewmanjones <https://github.com/ashnewmanjones> @ktgw0316 <https://github.com/ktgw0316> @makise-homura <https://github.com/makise-homura> @simba611 <https://github.com/simba611> @tommyvct <https://github.com/tommyvct> @Glitch18 <https://github.com/Glitch18> @dhbloo <https://github.com/dhbloo> * simde/simde-detect-clang.h <https://github.com/simd-everywhere/simde/blob/master/simde/simde-detect-clang.h> by @nemequ <https://github.com/nemequ> and myself * simde/simde-f16.h <https://github.com/simd-everywhere/simde/blob/master/simde/simde-f16.h> contains portions that @nemequ <https://github.com/nemequ> heavily based upon CC0 code by @rygorous <https://github.com/rygorous> As the authors of each file agree to dual-licensing (even a comment on this issue would suffice) then we can update the file headers & SPDX identifiers — Reply to this email directly, view it on GitHub <#999 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEHHK63LRUFV3P4XDF53R3W67WEPANCNFSM6AAAAAAWJXOT4E>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[FlyGoat]

I’m fine with dual licensing.

[ktgw0316]

I'm fine with the dual licensing, too.

[mr-c]

Thank you @rosbif @ktgw0316 @FlyGoat @tommyvct ; I've noted your agreement to dual-license. Feel free to unsubscribe from this issue :-)

[ashnewmanjones]

I'm fine with dual licensing.

[tlively]

Dual licensing under MIT sounds good to me.

[dhbloo]

I'm fine with the dual licensing.

[simba611]

I am fine with dual licensing

[makise-homura]

I've had issues with github last month or two, so only now I was able to see this.
I'm perfectly fine with dual licensing too.

[junaruga]

I've noted your agreement to dual-license. Feel free to unsubscribe from this issue :-)

@mr-c, where did you note the dual-license in this repository? Shall we add the dual license info in this repository's COPYING or README.md?

[mr-c]

I've noted your agreement to dual-license. Feel free to unsubscribe from this issue :-)

@mr-c, where did you note the dual-license in this repository? Shall we add the dual license info in this repository's COPYING or README.md?

As we are missing Evan's consent, we can't license yet

[junaruga]

As we are missing Evan's consent, we can't license yet

Sure. Okay.