Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Switch PyPOTS ecosystem license from GPL-v3 to BSD-3-Clause #227

Closed
WenjieDu opened this issue Nov 5, 2023 · 0 comments
Closed

Switch PyPOTS ecosystem license from GPL-v3 to BSD-3-Clause #227

WenjieDu opened this issue Nov 5, 2023 · 0 comments
Labels
keep Keep this issue away from being stale. new feature Proposing to add a new feature
Milestone

Comments

@WenjieDu
Copy link
Owner

WenjieDu commented Nov 5, 2023

Issue description

When I created PyPOTS, my thought was simple: open-sourcing some useful SOTA algorithms with quality code. Quality code is so important to open-source communities, and I expect projects using PyPOTS to be open-source as well. Therefore I applied GPL-v3 license in PyPOTS.

Now, more and more people are noticing this project and using it in their research and engineering work. Also, our community is always trying to make PyPOTS better. Considering the infectious nature of GPL licenses that could make a small part of our users concerned, I think PyPOTS and its ecosystem projects should all switch to using BSD license, and this should be done synchronously in their version 0.2 release.

@WenjieDu WenjieDu added question Further information is requested new feature Proposing to add a new feature keep Keep this issue away from being stale. and removed question Further information is requested labels Nov 5, 2023
@WenjieDu WenjieDu added this to the v0.2 milestone Nov 5, 2023
@WenjieDu WenjieDu closed this as completed Nov 6, 2023
Repository owner locked and limited conversation to collaborators Nov 7, 2023
@WenjieDu WenjieDu converted this issue into discussion #231 Nov 7, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
keep Keep this issue away from being stale. new feature Proposing to add a new feature
Projects
None yet
Development

No branches or pull requests

1 participant