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
BSD 3-Clause is FSF & OSI approved, and GPL compatible.
Details
I'm planning to codify our existing "honour rule" around not using the likenesses of contributors for downstream projects. I plan to do this by changing our open source license from MIT to BSD 3-Clause for all future versions of Fusion.
Due to the temperature of some discussions about open-source security audits in the past (specifically around holding unpaid open source maintainers responsible for performing security audits, in the wake of xz and log4j), the new licence will also include a security disclaimer to explicitly protect maintainers from this.
This does not change our commitment to keeping Fusion secure and rigorous.
There are no changes beyond this. Commercial use is still allowed, and derivatives of Fusion are still encouraged.
The text was updated successfully, but these errors were encountered:
Important: please thumbs-up 👍🏻 this post if you are on board with this change, and are willing to relicense your contributions.
Please thumbs down 👎🏻 this post if you do not consent to this change.
I'm looking to relicense future versions of the Fusion project to strengthen protections for maintainers.
We will be switching from MIT to BSD 3-Clause + Security Disclaimer.
BSD 3-Clause is FSF & OSI approved, and GPL compatible.
Details
I'm planning to codify our existing "honour rule" around not using the likenesses of contributors for downstream projects. I plan to do this by changing our open source license from MIT to BSD 3-Clause for all future versions of Fusion.
Due to the temperature of some discussions about open-source security audits in the past (specifically around holding unpaid open source maintainers responsible for performing security audits, in the wake of
xz
andlog4j
), the new licence will also include a security disclaimer to explicitly protect maintainers from this.This does not change our commitment to keeping Fusion secure and rigorous.
There are no changes beyond this. Commercial use is still allowed, and derivatives of Fusion are still encouraged.
The text was updated successfully, but these errors were encountered: