License Selection for EEGManySteps Project #5
Description
We Need to Choose a License for Our Project
As EEGManySteps grows, we need to establish clear licensing for our code, data, and documentation to support Open Science principles and clarify usage rights.
Main Options to Consider:
For Code & Software:
- MIT - Very permissive, allows commercial use, minimal restrictions
- BSD-3-Clause - Similar to MIT but prevents using project name for endorsement
- Apache 2.0 - Like MIT but includes patent protections
For Data & Documentation:
- CC0 - Public domain, no rights reserved, maximum openness (Required by OpenNeuro)
- CC-BY - Requires attribution only, very permissive
- CC-BY-SA - Attribution required, derivatives must use same license
Key Considerations:
- Data sharing requirements from funding agencies
- International collaboration - ease of use across institutions
- Integration with other MoBI projects and datasets
- Commercial use - do we want to allow/restrict it?
- Attribution requirements for citations and credit
Questions for Discussion:
- Should we use the same license for everything or different licenses for code vs. data?
- Do funding agencies or institutions have specific requirements?
- How do other "Many" projects (EEGManyLabs, EEGManyPipelines) handle licensing?
- What license would encourage maximum participation and data sharing?
How to Help:
- Share your institution's requirements or preferences
- Comment on what works best for your data sharing needs
- Research what other similar projects use
This decision affects all contributors and data sharing, so your input is valuable!