[riot-notifications] [RIOT-OS/RIOT] doc/rdm: RFC - design goals (#10162)
notifications at github.com
Thu Jan 24 17:18:22 CET 2019
>>In this document we need to get to the point as quickly as possible, the point being: design philosophies/principles (do we agree on this?)
>Why should this be? The document is not long anyway, and an RDM should be a comprehensive presentation of the subject. So no pressure at this side, I suppose.
I would say that, rather than necessarily getting to the design philosophies quickly, that the document should be engaging and informative from start to finish. If the use cases section fits that description, then great. It seems it doesn't at the moment, at least not by everyone's opinion.
>> Hitting the key aspects
>> Being exhaustive on an appropriate layer of abstraction
> I don't see this as conflicting with the comments I made previously, quite the contrary ;)
So then do we all agree that this section needs to do the following:
- Hit all the key aspects
- Be exhaustive
- Not include any use case or aspect unless it strongly supports the key message that the section is making
Specifically, the "key messages" are the design implications of these use cases: how to design RIOT in such a way that it addresses these use cases as pertinently as possible.
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...
More information about the notifications