FAQ

---

• Under what licence is RIOT code released?

LGPLv2

---

• Why LGPL?

We want to ensure that improvements to RIOT itself find their way back to the project, but we'd also allow proprietary projects to use RIOT without GPLing their code. LGPL allows linking proprietary code to RIOT code whithout tainting the proprietary code's license.

---

• How is RIOT development organized?

In short there are certain Coding Conventions to follow and we are using github's forks for code review. So for new features and fixes create a fork of the RIOT repository and open a pull request with a detailed description of your changes.

For a more in depth description check out the dedicated page on development procedures.

---

• What should be my first steps to get started?

So we attracted your attention? That's great!
There is an introduction to RIOT giving a short overview of its structure, some example toolchains for different platforms and a more in depth introduction to selected features of RIOT. All to get you up and running quickly.

---

• I want to contribute. How should I proceed?

First of all, welcome to the RIOT community! There is a dedicated page on contributing listing opportunities to interact with other people contributing and some suggestions how to get started. While developing keep the development procedures under your pillow.

---

• I have an issue with RIOT code I can't solve. How can I get help?

Log an issue in github. Then post to the mailing list [email protected] and/or [email protected]. You're also welcome to ask in the IRC channel #riot-os at irc.freenode.net, but don't be disappointed if everyone there is busy.

---

• Does RIOT run as-is on my hardware?

Check out this page on supported hardware. If your hardware is not listed there, you're welcome to provide a port for your hardware!

---