[riot-notifications] [RIOT-OS/RIOT] doc/rdm: RFC - design goals (#10162)

Matthias Wählisch notifications at github.com
Wed Jan 30 23:48:03 CET 2019

Here comes a proposal for the Introduction. It should give enough context.
By linking to the sections, the reader can easily jump to the topics he or she is interested in. If we really want to spell out the design choices in the Introduction, you could just add something like "These building blocks include ..."

The RIOT developer community has grown from a state of a few developers in
relatively close contact to a highly distributed worldwide organisation with
members joining continuously. As a result, passing on underlying understanding
and assumptions that drive design decisions via word-of-mouth is no longer

This document lists a set of generalised, loose requirements for RIOT (in a
voluntary open source context, gathering strict requirements is neither
possible nor welcome). As RIOT is driven by real-world challenges, we will start 
with the discussion of some concrete [use cases](#2-use-cases). 
Based on this bigger picture that RIOT tries to solve, we will introduce 
building blocks of the [design choices](#3-design-philosophies) in RIOT.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190130/7f2fb76f/attachment.html>

More information about the notifications mailing list