--- a/text/ssm.en.xml Thu Sep 26 00:37:37 2019 +0200
+++ b/text/ssm.en.xml Thu Sep 26 16:27:05 2019 +0200
@@ -220,7 +220,7 @@
<id>f3afbaf2-0933-43d2-aed0-8dc568b9429f</id>
<item>
<id>a96206c9-3e69-483d-b575-6bab9dec4a30</id>
- <text>correctness, safety and readability is prefered to performance</text>
+ <text>correctness, safety and readability is preferred to performance</text>
</item>
<item>
<id>d8eba0dd-4305-44b9-80ea-4c38b6dfa633</id>
@@ -445,103 +445,51 @@
</chapter>
<chapter>
- <name>Communication channels</name>
+ <name>Communication with users and developers</name>
<id>a931dcbb-8043-4e21-838f-8e8122bb8af3</id>
<item>
<id>fff90688-907e-48eb-a48a-2ae6d6b42f0a</id>
- <text>use RSS/Atom or other machine readable format for:</text>
- <item>
- <id>ce9ffd67-627b-4067-ae34-f56ffbcac972</id>
- <text>security announcements</text>
- </item>
- <item>
- <id>f4c0b757-1fee-4d6d-8b30-808b4787fb5e</id>
- <text>new version announcements</text>
- </item>
- <item>
- <id>b17dbc84-4119-4706-acd8-61421a384246</id>
- <text>infrastructure outage announcements</text>
- </item>
- <item>
- <id>f3063520-5e7a-4aa0-95f6-505775556120</id>
- <text>blog, documentation, how-tos etc.</text>
- </item>
- <item>
- <id>e2434bd6-c838-479a-a636-f277003ebe7c</id>
- <text>AFK events (conferences, meetings, hackatons etc.), for calendar data iCal format is strongly recommended</text>
- </item>
+ <text>Following information should be provided in RSS/Atom or other machine readable format:</text>
+ <text>announcements (security, new versions, infrastructure outage),</text>
+ <text>blog posts, tutorials</text>
+ <text>and AFK events (e.g. conferences, meetings or hackatons).</text>
+ <note>for calendar data iCal format is strongly recommended</note>
</item>
<item>
<id>e8b18e02-d7b2-4584-8eee-dbaf823f6800</id>
- <text>mailing list</text>
- </item>
- <item>
- <id>a35328fe-a177-4d6a-a3d2-2cc8fa0cb6f7</id>
- <text>e-mail/SMTP</text>
- <item>
- <id>f40e9a23-b2ca-4052-949e-f4358844f5a2</id>
- <text>use TLS</text>
- </item>
- <item>
- <id>bc444281-5c76-43a9-b5ef-46306cbb2bf9</id>
- <text>use DKIM/ADSP</text>
- </item>
- <item>
- <id>a2852409-806f-480c-8700-141ace86f322</id>
- <text>use signed and encrypted messages (GnuPG or X.509)</text>
- </item>
- <item>
- <id>da2b84bd-a20d-4e76-af14-740a7c9ccfb3</id>
- <text>avoid spam and viruses, do not spam the users, do not push them to subscribe your „newsletter“ – always offer also anonymous channel like RSS/Atom</text>
- </item>
- </item>
- <item>
- <id>ec4c92b6-83e5-4051-9aef-fa7d02e292b8</id>
- <text>Jabber MUC or IRC</text>
- </item>
- <item>
- <id>f50d17bd-701f-45f9-aae4-86bfcf34cd7c</id>
- <text>discussion forum</text>
+ <text>A mailing list (e-mail conference) or other equivalently open and decentralized technology should be used for the many-to-many communication.</text>
+ <note>Having an „old school“ mailing list is not mandatory – it might be e.g. a P2P distributed technology or some self-hosted forum.</note>
</item>
<item>
<id>e746eb5b-8d8b-4ec8-9315-a311f35e156a</id>
- <text>do not push users to register at a proprietary social networks resp. at particular company like Facebook – users without such account must not be discriminated – use open and decentralized networks/protocols instead</text>
- </item>
- <item>
- <id>a1a3c037-37e3-4283-abab-e275f7d17442</id>
- <text>Q&A tool + FAQ</text>
+ <text>Users must not be pushed to register at a proprietary social networks resp. at particular providers of such services.</text>
+ <text>Users without such account must not be disadvantaged – use open and decentralized networks/protocols instead.</text>
</item>
<item>
<id>ff537045-819e-4dec-a020-d2c9f2c3292b</id>
- <text>there should be a second-level internet domain for the project or its team</text>
- </item>
- <item>
- <id>b54d4978-974b-4743-bdba-7d4957bc9ba7</id>
- <text>but do not buy an internet domain if you are not prepared to mainain it for decades – rather use third level domain under some reliable second level domain maintained by a credible group or person – think of that every expired domain helps spammers and scammers and hurts the users</text>
+ <text>There should be a second-level internet domain for the project or its team.</text>
+ <note>But do not buy an internet domain if you are not prepared to mainain it for decades – rather use third level domain under some reliable second level domain maintained by a credible group or person – think of that every expired domain helps spammers and scammers and hurts the users.</note>
</item>
<item>
<id>a1141312-5177-4d68-bb14-fce952d542c3</id>
- <text>URLs should be as stable as possible (do not break old links, set up redirections if needed)</text>
+ <text>URLs should be as stable as possible – accessible in next decade.</text>
+ <note>Do not break old links, set up redirections if needed.</note>
</item>
<item>
<id>c5b6d3d7-2f1f-4371-acfa-d6af1588c2cb</id>
- <text>the website must be independent and must contain everything needed – any content (JavaScripts, CSS, fonts, images etc.) downloaded from other domains must not be required to browse/use the website</text>
+ <text>The website must be independent and must contain everything needed – any content (JavaScripts, CSS, fonts, images etc.) downloaded from other domains must not be required to browse/use the website.</text>
+ <note>Embedded content from the third-party servers causes leaks of sensitive data (tracking of the users) and also denies decentralized nature of the internet.</note>
</item>
<item>
- <id>c1d9052d-dfe5-4fce-a82c-d618dc4689fa</id>
- <text>authors should publish their public keys (GnuPG/OpenPGP or X.509)</text>
+ <id>d5fbcc9e-a12c-44ce-909b-f514a579ab7e</id>
+ <text>JavaScript or other code executed on client computers must be also free software with properly declared license.</text>
+ <note>see https://www.gnu.org/software/librejs/</note>
</item>
<item>
<id>c89e8699-574c-4b28-9f65-6284d6051f68</id>
- <text>crpyptographically secured e-mail address or web form for receiving security vulnerabilities report</text>
- </item>
- <item>
- <id>b6cf8d5f-0fc9-46f7-8e38-8342a1229037</id>
- <text>every security incident must be clearly documented and investigated – do not obscure it</text>
- </item>
- <item>
- <id>e41134a4-715c-4926-a7df-01ff3759eda1</id>
- <text>There should be public directory of extensions/scripts.</text>
+ <text>There must be a crpyptographically secured (GnuPG/OpenPGP or X.509) e-mail address or a secure web form for receiving security vulnerabilities reports.</text>
+ <note>Particular authors should publish their public keys.</note>
+ <note>Every security incident must be clearly documented and investigated – do not obscure it.</note>
</item>
<item>
<id>fed07648-106a-4b7c-9026-509c82109448</id>