Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Choose a suitable license to your package and justify your choice #51

Closed
colombe-tolokin opened this issue Jan 27, 2025 · 5 comments
Closed
Assignees
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested
Milestone

Comments

@colombe-tolokin
Copy link
Collaborator

No description provided.

@adrianl726
Copy link
Collaborator

adrianl726 commented Jan 30, 2025

choosealicense.com will help you find a common license that suits your needs.
Important considerations include:

  • Whether you require people distributing derivative works to also require others to distribute their derivative works in the same way.

  • Whether the content you are licensing is source code, and if it is, whether you want to require that derivatives of your work to share the source code

@adrianl726 adrianl726 added documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested labels Jan 30, 2025
@adrianl726 adrianl726 added this to the Milestone 4 milestone Jan 30, 2025
@adrianl726 adrianl726 pinned this issue Jan 31, 2025
@QuanhuaHuang-ubc
Copy link
Collaborator

I think the MIT license will be good enough for our project in two ways:
First the MIT license is business friendly. When our python package is used in a commercial setting, the MIT License allows businesses to incorporate it into their proprietary products without the need to disclose proprietary code, making it convenient and handy to commercial users.
Besides, there's no liability. The MIT license includes a disclaimer of warranty, indicating that our authors are not liable for any issues that arise from using the software. This helps protect developers from legal issues.

@adrianl726
Copy link
Collaborator

I agree with @QuanhuaHuang-ubc. MIT license is a good way to encourage collaboration and contributions too. It is permissive, meaning you can freely use, modify, and distribute the code, even for commercial purposes. By using an open and permissive license, the MIT License encourages others to contribute to your project. It lowers the barriers for others to use and build upon your package, which can lead to faster development and improvements!

@TinLattNandar
Copy link
Collaborator

Okay. I also agree! The MIT license keeps things flexible. It is short, simple, and permissive. A solid choice for our project!

@colombe-tolokin
Copy link
Collaborator Author

Yes, I’m on board with this too! The MIT license offers the right balance of flexibility and protection. Its wide adoption by many successful open-source projects makes it ideal for encouraging contributions, while the permissiveness ensures ease of integration for commercial use. Plus, the simplicity of the license keeps things clear and manageable for us as developers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested
Projects
Status: Done
Development

No branches or pull requests

4 participants