mirror of
https://github.com/openvk/openvk
synced 2024-12-23 00:51:03 +03:00
README.md: minor spelling mistake (#1074)
This commit is contained in:
parent
49e061f563
commit
d60df69825
1 changed files with 2 additions and 2 deletions
|
@ -71,7 +71,7 @@ Once you are done, you can login as a system administrator on the network itself
|
||||||
### Looking for Docker or Kubernetes deployment?
|
### Looking for Docker or Kubernetes deployment?
|
||||||
See `install/automated/docker/README.md` and `install/automated/kubernetes/README.md` for Docker and Kubernetes deployment instructions.
|
See `install/automated/docker/README.md` and `install/automated/kubernetes/README.md` for Docker and Kubernetes deployment instructions.
|
||||||
|
|
||||||
### If my website uses OpenVK, should I release it's sources?
|
### If my website uses OpenVK, should I release its sources?
|
||||||
|
|
||||||
It depends. You can keep the sources to yourself if you do not plan to distribute your website binaries. If your website software must be distributed, it can stay non-OSS provided the OpenVK is not used as a primary application and is not modified. If you modified OpenVK for your needs or your work is based on it and you are planning to redistribute this, then you should license it under terms of any LGPL-compatible license (like OSL, GPL, LGPL etc).
|
It depends. You can keep the sources to yourself if you do not plan to distribute your website binaries. If your website software must be distributed, it can stay non-OSS provided the OpenVK is not used as a primary application and is not modified. If you modified OpenVK for your needs or your work is based on it and you are planning to redistribute this, then you should license it under terms of any LGPL-compatible license (like OSL, GPL, LGPL etc).
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue