You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you're going to re-license, might I cheekily suggest that you also include the Zlib license as an option? The main difference from MIT is that you don't need to include the license text with compiled copies. SDL2 uses the Zlib license, I think it's quite nice for libraries to use.
madsmtm
changed the title
Relicense under dual MIT/Apache-2.0
Relicense under dual (tri-al?) MIT/Apache-2.0/Zlib
Sep 1, 2022
@madsmtm, I read @SSheldon's comment here as confirmation that he's ok with at least the licensing under MIT+Apache.
Are you awaiting a more explicit confirmation? Or awaiting Zlib's one? If it's the latter, can you at least proceed forward with the dual licensing?
And thanks for keeping this crate moving forward, and building upon @SSheldon's already fantastic work.
EDIT: never mind, I realise that that comment was in reply to Josh. @SSheldon, can you please provide a closure on this either way? It would be useful to have clarity on the licensing.
I'd also like to remove the copyright notice from the MIT license (see rust-lang/rust@2a8807e).
Upstream issues:
Will probably need permission from (won't tag most of them yet):
@jrmuizel
@alexbool
@bvssvni
@mehcode
@pcwalton
@burtonageo
@syntheorem
@ddrmanxbxfr
@waywardmonkeys
@ngrewe
@codesmythe
@kvark
@frewsxcv
@jdm
The text was updated successfully, but these errors were encountered: