The RIOT-rs project is dedicated to creating a general-purpose operating system (OS) for low-power, microcontroller-based IoT devices, written from scratch in Rust, providing easy portability of application code to diverse microcontroller-based hardware. This governance document explains how the project is run.
RIOT-rs and its leadership embrace the following values:
-
Openness: Communication and decision-making happens in the open and is discoverable for future reference. As much as possible, all discussions and work take place in public forums and open repositories.
-
Fairness: All stakeholders have the opportunity to provide feedback and submit contributions. These contributions will be considered on their merits.
-
Inclusivity: We innovate through different perspectives and skill sets, which can only be accomplished in a welcoming and respectful environment.
RIOT-rs is a digital public good, or digital common, supported by public funding. The project's outcome is open source and freely available for everyone.
Decisions within RIOT-rs are made with consensus, as much as possible, among team members, based on technical arguments. The Founder-leaders have override power, for strategic steering and/or to break ties.
Kaspar Schleiser and Emmanuel Baccelli.
The founder-leaders are the final decision-makers. Emmanuel Baccelli is responsible for selecting team members and funding. Kaspar Schleiser is technical lead.
Specific tasks have been divided among the team members by the founder-leaders. Team members have write access to the project GitHub repository and can merge pull requests. Team members collectively maintain and manage the project's resources and contributors.
This privilege is granted with some expectation of responsibility: team members are people who care about the RIOT-rs project and want to help it grow and improve. A team member is not just someone who can make changes, but someone who has demonstrated their ability to collaborate with the team, get the most knowledgeable people to review code and docs, contribute high-quality code, and follow through to fix issues (in code or tests). A team member is a contributor to the project's success and a citizen helping the project succeed.
Anyone can contribute to the RIOT-rs project, for example via comments on issues or pull requests, writing code or documentation etc.
Decisions about the RIOT-rs project are made in the matrix chat room and during the weekly meetings. If you have questions about the direction the RIOT-rs project is taking, or want to get involved in the decision making process, you can get in contact via these channels.
The RIOT-rs Matrix chat room is the main communication channel for all users, contributors and team members of RIOT-rs. It is open to anyone interested in the project, so feel free to join!
Team members meet weekly online to discuss the current progress of the project. The meeting is open to interested contributors. The link to the meeting is available in the Matrix chat.
All code and documentation of RIOT-rs is available at the RIOT-rs GitHub.
The present text was written by Karin Lammers and is licensed as CC BY 4.0, including components and inspiration from The Maintainer Council Template, licensed likewise.