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

Licensing question #1064

Open
rimas-kudelis opened this issue Nov 4, 2024 · 0 comments
Open

Licensing question #1064

rimas-kudelis opened this issue Nov 4, 2024 · 0 comments

Comments

@rimas-kudelis
Copy link
Contributor

rimas-kudelis commented Nov 4, 2024

I started a project based on Sylius Standard today, and I'm a bit unsure what to do with the LICENSE file.

On the one hand, the project I'm creating will not be open-source, so it seems incorrect to keep the LICENSE file as-is.

On the other hand, the file specifies how Sylius Standard itself is licensed, and the project I've started will definitely include "substantial portions of the Software" so, at least from a very strict point of view, I'm supposed to retain pretty much the whole contents of the file somewhere in my repo. But this doesn't make sense from a practical point of view, because "the Software" in this case is just a barebones skeleton, which wraps around sylius/sylius and a few other packages.

I wonder what your take on this is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant