<p><b>@miri64</b> requested changes on this pull request.</p>

<hr>

<p>In <a href="https://github.com/RIOT-OS/RIOT/pull/10162#discussion_r260362094">doc/memos/rdm-draft-petry-riot-design-goals.md</a>:</p>
<pre style='color:#555'>> +modular as possible so unused features don't use up precious RAM or flash.
+Almost all features are provided as optional modules that have to be enabled
+explicitly at compile time.  A minimal RIOT configuration starts at around
+<2KiB flash and <1.5KiB RAM (including stack space for one thread and ISRs).
+
+Starting from there, the memory usage depends on the enabled features:
+
+- Non-networked control loop / sensing applications can fit on very small MCUs
+(eg., an Atmega328P with 2KiB RAM)
+- 6lowPAN networking currently starts at ~40KiB ROM and ~10KiB RAM
+- A 6lowpan enabled CoAP server requires ~60KiB ROM and ~15KiB RAM
+- a file system adds ~15 KiB ROM and ~2 KiB RAM
+
+#### Constrained networking
+
+RIOT should deliver best-in-class communication robustness and
</pre>
<p>I'm not sure about this economist-linguo "best-in-class". At least I had to look it up (though the meaning turned out to be pretty self-explanatory I wanted to make sure there is no technical meaning to it). Why use this superlative at all (we had criticism of over-claiming in the past already ;-))?</p>
⬇️ Suggested change
<pre style="color: #555">-RIOT should deliver best-in-class communication robustness and
+RIOT should deliver communication robustness and
</pre>


<hr>

<p>In <a href="https://github.com/RIOT-OS/RIOT/pull/10162#discussion_r260390433">doc/memos/rdm-draft-petry-riot-design-goals.md</a>:</p>
<pre style='color:#555'>> +  - Sense temperature, light, humidity, pressure, current, etc.
+  - Control temperature, light, ventilation, etc.
+  - Connect to the building management system, via wired or wireless connectors.
+  - Deliver data with controllable timing and accuracy.
+
+## 2.6. Smart home devices
+
+Easy to use devices can let consumers monitor and control their home
+automatically. The devices need to be able to:
+
+  - Sense temperature, light, humidity, smoke, etc.
+  - Integrate with home appliances to control temperature, light, power usage,
+    etc.
+  - Be usable but secure for people with no technical knowledge.
+  - Connect to a commercial home gateway.
+  - Communicate over common home IoT protocols such as ZigBee, Bluetooth, Wi-Fi,
</pre>
<p>With this sentence from section 3 in mind</p>
<blockquote>
<p>RIOT should support standards once they have reached a certain level of<br>
maturity and popularity.</p>
</blockquote>
<p>I guess it is about high time we write a ZigBee stack then ;-). Question is are we able / allowed to do that (I remember there was some paywall thingy)?</p>

<hr>

<p>In <a href="https://github.com/RIOT-OS/RIOT/pull/10162#discussion_r260398374">doc/memos/rdm-draft-petry-riot-design-goals.md</a>:</p>
<pre style='color:#555'>> +  - Sense temperature, light, humidity, pressure, current, etc.
+  - Control temperature, light, ventilation, etc.
+  - Connect to the building management system, via wired or wireless connectors.
+  - Deliver data with controllable timing and accuracy.
+
+## 2.6. Smart home devices
+
+Easy to use devices can let consumers monitor and control their home
+automatically. The devices need to be able to:
+
+  - Sense temperature, light, humidity, smoke, etc.
+  - Integrate with home appliances to control temperature, light, power usage,
+    etc.
+  - Be usable but secure for people with no technical knowledge.
+  - Connect to a commercial home gateway.
+  - Communicate over common home IoT protocols such as ZigBee, Bluetooth, Wi-Fi,
</pre>
<p>I actually was asked about this at 35C3 by <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=4404502" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/Drakulix">@Drakulix</a>. His use-case is to have a non-intrusive but open integration with his TRÅDFRI home automation setup.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/RIOT-OS/RIOT/pull/10162#pullrequestreview-208052166">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AEn7YAvmXVTiJ30xlYTmYpyRNiLIJw7_ks5vRW3SgaJpZM4Xb9Mj">mute the thread</a>.<img src="https://github.com/notifications/beacon/AEn7YOcfDLFjoGBr1BX2edwrgUsPqMSxks5vRW3SgaJpZM4Xb9Mj.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/RIOT-OS/RIOT","title":"RIOT-OS/RIOT","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/RIOT-OS/RIOT"}},"updates":{"snippets":[{"icon":"PERSON","message":"@miri64 requested changes on #10162"}],"action":{"name":"View Pull Request","url":"https://github.com/RIOT-OS/RIOT/pull/10162#pullrequestreview-208052166"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/RIOT-OS/RIOT/pull/10162#pullrequestreview-208052166",
"url": "https://github.com/RIOT-OS/RIOT/pull/10162#pullrequestreview-208052166",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>