-
Notifications
You must be signed in to change notification settings - Fork 341
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
Update LICENSE.md #194
Update LICENSE.md #194
Conversation
You may keep a copy of this project only for your personal, commercial, and | ||
non-commercial purposes as long as such purposes are not associated with any | ||
religious or distributed ledger (blockchain) subject matter, and the software | ||
is not executed in a replicated environment (e.g. with Tendermint). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The intent is to restrict gno IP usage until gno.land itself is established, and inter-chain licenses are also established.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Otherwise, commercial usage is allowed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can’t it be a limitation for integration tools, like a client, a dApp, a bridge?
Maybe this license could exclude the .proto and generated protobuf files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to allow integration tools, clients, dapps, and bridges?
yes I suppose what's missing is carve-ins to allow these, specifically, as long as the software isn't run replicated. Does that sound right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that’s why I proposed I limit on the interface files if you prefer
but it may be just plain english explaining the limits 👍
One thing I am not sure of-- with for example the docker stuff I would like to pull in-- it has a prior license. Thoughts? |
Anything that requires its own license could live in its own folder with its own LICENSE.md file. |
Updated license.md.
Also published pkgs under Apache2.0.