react-transition-group icon indicating copy to clipboard operation
react-transition-group copied to clipboard
verified publisher icon reactjs

Move license to MIT to be consistent with React

Open jasonmorita opened this issue 6 years ago • 3 comments

Most other React community modules as well as React itself have MIT license.

Can this repo move to MIT as well?

Is this an oversight that this repo still has BSD-3?

See: https://github.com/facebook/react/blob/master/LICENSE

jasonmorita avatar Dec 09 '19 18:12 jasonmorita

I am not sure it makes sense to talk about "license consistency". It is not because most of React packages are MIT that this one should be.

I don't think "consistency" is a valid argument for changing license.

lcswillems avatar Dec 10 '19 11:12 lcswillems

Note that there's no PATENTS clause here, unlike in the previous licensing situation for the React repos.

I don't know what it would take to re-license to MIT, though. Would we need to get sign-off from all our contributors, or can we just do it?

taion avatar Dec 10 '19 13:12 taion

I resonate with the proposal of @jasonmorita. In the case of Material UI, react-transition-group is our only dependency that is not MIT:

Screenshot 2022-10-15 at 14 27 36

https://deps.dev/npm/%40mui%2Fmaterial/5.10.9. It looks a bit "odd", meaning, developers have to consider two different licenses, rather than one before adopting our library.

I don't know what it would take to re-license to MIT, though. Would we need to get sign-off from all our contributors, or can we just do it?

I suspect that meta Facebook could do it https://github.com/facebook/react/commit/b765fb25ebc6e53bb8de2496d2828d9d01c2774b because of the SLA they make all contributors sign. I don't know for this project.

oliviertassinari avatar Oct 15 '22 12:10 oliviertassinari