Clarify licensing #4792
Merged
Clarify licensing #4792
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Move each license to a better named file. Create LICENSE file describing osquery is dual licensed and clarify the user can pick one of the two licenses when using osquery. Add SPDX. This will allow a user that opens the LICENSE file to immediately understand the licensing of osquery which wasn't the case before.
akindyakov
added a commit
to akindyakov/osquery
that referenced
this issue
Aug 8, 2018
akindyakov
added a commit
to akindyakov/osquery
that referenced
this issue
Aug 22, 2018
|
Hi, |
trizt
added a commit
to trizt/osquery
that referenced
this issue
May 24, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Move each license to a better named file. Create LICENSE file describing
osquery is dual licensed and clarify the user can pick one of the two
licenses when using osquery. Add SPDX.
This will allow a user that opens the LICENSE file to immediately
understand the licensing of osquery which wasn't the case before.