Switch to Mozilla Public License
ChristopherRabotin opened this issue · comments
After careful consideration, starting with version 4.0.0, Hifitime will be licensed in the Mozilla Public License (MPL) -- cf. the Mozilla Public License FAQ and Github's choose a license. This decision isn't taken lightly, nor is it final, and I want to ensure everyone in our community understands the rationale and practical implications. This project exists for its users: please raise any concerns you have in this issue or on the discussion before version 4.0.0 is released.
Why the change?
The primary motivation behind this proposed shift is to better align with the core values of our project - promoting open-source collaboration while ensuring that improvements and derivatives remain open-source. MPL, I believe, will further foster a collaborative environment and ensure that enhancements remain accessible to all.
Practical Implications for Users
-
Source Code Sharing: Under MPL, if you modify Hifitime's code, you are required to share those changes if you distribute the modified version. This requirement is more stringent than the Apache License, encouraging a more collaborative development environment.
-
Compatibility with Other Licenses: MPL is designed to be compatible with other open-source licenses (including BSD and Apache). For internal use within your organization, integrating Hifitime with other software poses no issues under the MPL. However, if distributing the modified version externally, ensure compatibility of MPL's requirements with licenses of external projects, particularly when dealing with restrictive licenses like the GNU General Public License (GPL) version 2.
-
Patent Rights: Like Apache, MPL grants patent rights from contributors to users. It's important to understand these rights, especially if you're using Hifitime in a commercial context.
-
No Warranty: As with most open-source software, Hifitime under MPL would be provided without warranty. This aspect remains unchanged from the Apache License.
Your Feedback Matters
This proposal is not final, and your feedback is crucial. I invite all users and contributors to share their thoughts, concerns, or support for this change. Understanding how this impacts your use and contribution to Hifitime will guide me in making a decision that best serves our community.
Please share your thoughts in this discussion thread or reach out directly if you prefer a more private conversation.
Thank you for your continued support and contributions to Hifitime. Together, we're not just building software; we're fostering a community that drives innovation for spaceflight dynamics.
Originally posted by @ChristopherRabotin in #274
I'm thinking of moving from MIT + AP2 (the "rust" recommendation) myself as well, because I think it is too broad