Change License from AGPL-3.0 to MIT
License Change: AGPL-3.0 → MIT License
Overview
This PR implements the license change from AGPL-3.0 to MIT License as proposed and discussed in issue #324. This change aligns PyPulseq with the upstream MATLAB Pulseq implementation.
PR Status
⚠️ This is currently a DRAFT PR as we are still awaiting final agreement from all contributors listed in #324. However, we're opening this draft to:
- Allow the community to review the proposed changes
- Discuss the implementation approach
- Ensure we haven't missed any important aspects of the license transition
Once all contributors have confirmed their agreement in #324, this PR will be ready for final review and merge. I suggest that all maintainers approve this PR.
Changes Included
This PR includes all necessary steps for a complete license change:
Core License Updates
- LICENSE file: Completely replaced AGPL-3.0 text with standard MIT License
- pyproject.toml: Added
"License :: OSI Approved :: MIT License"classifier for proper PyPI display - README.md: Updated license badge from AGPL v3 to MIT
Verification & Compatibility
- Codebase scan: Confirmed no remaining AGPL references in the codebase (please double check)
- Documentation review: No license references found in documentation files that need updating (please double check)
Third-Party License Analysis
All existing third-party code in the repository remains compatible with the MIT License:
| File | License | Status |
|---|---|---|
| src/pypulseq/make_adiabatic_pulse.py | BSD-3-Clause (SigPy) | ✅ Compatible |
| src/pypulseq/utils/safe_pns_prediction.py | BSD-3-Clause (Szczepankiewicz & Witzel) | ✅ Compatible |
| src/pypulseq/SAR/SAR_calc.py | Columbia University Copyright | ✅ Compatible |
All third-party licenses are permissive and shold be fully compatible with MIT. The existing copyright notices and license texts have been preserved to maintain proper attribution.
Post-Merge Actions
After this PR is merged, we should create a new PyPI release to update the license information displayed on the PyPI page.
Legal Compliance
This license change has been properly coordinated with all contributors as documented in #324, ensuring we have the necessary rights to relicense all contributed code under the MIT License. However, I would like to add that I am not a lawyer nor an expert with regard to licenses.