faq: update link to bindist example #143
Merged
Conversation
This file contains hidden or 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
|
🚀 PR preview deployed to https://RIOT-OS-riot-os-org-preview-143.surge.sh |
miri64
reviewed
Mar 3, 2025
| Studies such as [this one](https://www.gartner.com/en/newsroom/press-releases/2014-10-09-gartner-says-by-2017-50-percent-of-internet-of-things-solutions-will-originate-in-startups-that-are-less-than-three-years-old) show that small companies and start-ups are going to determine IoT. More than bigger companies, such small structures need to spread development and maintenance costs for the kernel and all the software that is not their core business. Our analysis is that this is more compatible with LGPL than with BSD/MIT. | ||
|
|
||
| We are of the opinion that, compared to BSD/MIT, LGPL will improve final user experience, security and privacy, by hindering device lock-down, favoring up-to-date, and field-upgradable code. We think this a more solid base to provide a consistent, compatible, secure-by-default standard system which developers can build upon to create trustworthy IoT applications, while not hindering business models based on closed source linked with RIOT (see the [automated tools](https://github.com/RIOT-OS/RIOT/tree/master/examples/bindist) provided to help check LGPL compliance, and/or [this technical guide](https://github.com/RIOT-OS/RIOT/wiki/LGPL-compliancy-guide)) | ||
| We are of the opinion that, compared to BSD/MIT, LGPL will improve final user experience, security and privacy, by hindering device lock-down, favoring up-to-date, and field-upgradable code. We think this a more solid base to provide a consistent, compatible, secure-by-default standard system which developers can build upon to create trustworthy IoT applications, while not hindering business models based on closed source linked with RIOT (see the [automated tools](https://github.com/RIOT-OS/RIOT/tree/master/examples/advanced/bindist) provided to help check LGPL compliance, and/or [this technical guide](https://github.com/RIOT-OS/RIOT/wiki/LGPL-compliancy-guide)) |
Member
There was a problem hiding this comment.
I guess the wiki link could be updated, too. But that's out of scope of this PR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As follow-up of RIOT-OS/RIOT#21135 and RIOT-OS/RIOT#21221