LICENSE: append LGPL license #1
Open
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
|
@kaspar030 could we add the RIOT maintainers group to this repo? |
|
Do we want this to be LGPL? I'm not sure the reasons for LGPL we have in RIOT apply here, and once we switch over here there's no easy going back. |
|
... and since #1 (comment) started using this for meta discussion a bit as well: Could we open this up for issues? AIU this is now about to become the upstream repository. |
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description
As discussed offline with @flmeyer, it would be ok to set the fork license to LGPL.
This PR appends the LGPL license to the existing license file.
I also copied the first 15 lines of the LICENSE to the README.md file and added a pointer to the exsiting openDSME website.