You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: