# HG changeset patch # User František Kučera # Date 1569077466 -7200 # Node ID 2cbf4c472a6727162e3b35d59547f5841187622b # Parent ccbe2cf582bb5ea4cf8137a1c4bad07cd05f0384 remove superfluous whitespace diff -r ccbe2cf582bb -r 2cbf4c472a67 ssm.en.xml --- a/ssm.en.xml Sat Sep 21 14:24:33 2019 +0200 +++ b/ssm.en.xml Sat Sep 21 16:51:06 2019 +0200 @@ -25,8 +25,8 @@ a755410b-6264-4094-b339-aeca55448e8d Every piece of Sane software is also Free software (as originally defined by Richard Stallman). Which means that the user has freedom to - run the program for any purpose, - to study and change it (i.e. has access to the source code under a free software license) + run the program for any purpose, + to study and change it (i.e. has access to the source code under a free software license) and to distribute modified or unmodified copies. see https://www.gnu.org/philosophy/free-sw.html see https://www.gnu.org/philosophy/who-does-that-server-really-serve.html @@ -61,7 +61,6 @@ f39b90ae-0054-467e-a9e2-43379b7c2331 If the software is distributed with a hardware, the hardware must support instalation of independently built software without any restrictions or requirements (e.g. digital signature from the original author). - @@ -91,8 +90,6 @@ documentation should focus on all target groups: users, administrators, developers there must be a big picture and software architercure described --> - - @@ -125,7 +122,6 @@ The released version e.g. 2.3.1 should be tagged as v2.3.1 and be placed in the v_2.3 branch. Where the v_2.3 branch was forked from the v_2 branch – from the v2.3 tag. - @@ -156,7 +152,6 @@ f4826891-e732-45e8-b929-25d1182fa141 Upgrade scripts and upgrade documentation must be provided. - @@ -187,7 +182,6 @@ also configuration should have machine readable description and should be testable by executing a command - @@ -209,12 +203,10 @@ ac722cec-0734-4d80-9885-d70a97b6402b whole system should be compilable (buildable) with only selected modules – must not require compilation or even distribution of all modules, if they are not necessary - Extensible - d333af72-b5b5-432f-b564-a008d54a85d1 a7bc51ba-9832-4f75-983c-e75dc0801113 @@ -244,7 +236,6 @@ e41134a4-715c-4926-a7df-01ff3759eda1 there should be public directory of extensions/scripts - @@ -266,7 +257,6 @@ e85baeda-8fcb-42d1-bb53-d7386a941ae7 each external interface should contain procedure/function that does nothing important or heavy, is idempotent and returns simple response which proves that the interface (connection) is working (e.g. echo, print version, status or current time); if authentication and authorization mechanisms are present, there should be one procedure/function callable anonymously and one that requires authorization - @@ -296,7 +286,6 @@ b9345a0e-c672-45d3-b93b-8d0fb4ece8b3 fail fast – errors in the code should be reported during build time or at least on first execution – do not silently continue if given error would lead to failure later in another part of the code – bad weak coupling leads to difficult debugging - @@ -314,7 +303,6 @@ b07fe0f0-2be7-4c1c-9b19-b671269c5e58 use code generators (during build process, not to generate code to be manually edited and versioned) - @@ -361,7 +349,6 @@ from the whole system point-of-view, Bootstrappable builds should be taken into account see http://bootstrappable.org/ - @@ -379,7 +366,6 @@ e4db77b8-f145-4e43-bf8b-eb775b9352c8 refactoring/reformatting changesets should be separated from substantive changes - @@ -393,7 +379,6 @@ a3b0c164-4dde-4e33-b3be-5478d2a187e2 if not, it should be documented, why and how build products mihgt differ, and there should be plan/task to make it reproducible - @@ -413,7 +398,7 @@ c1f83b3a-e564-4483-91de-9c08723efd13 - the attacker should not be able to suppress updates – the program must not be silent in such case and must warn the user that something possibly nasty and dangerous is happening + the attacker should not be able to suppress updates – the program must not be silent in such case and must warn the user that something possibly nasty and dangerous is happening c6a755c9-a54e-4ffb-8f70-bfbd851b93c5 @@ -423,7 +408,6 @@ f9275c3c-2b09-4aec-ac28-76ff827d52ce source code repository must be accessible through an encrypted connection - @@ -445,7 +429,6 @@ f55c2ebd-c3ba-44f7-ae92-06f679780ec7 if any network connection is used, it must be cryptographically secured against MITM attacks - @@ -496,7 +479,6 @@ ce45c382-6ec5-41e8-869a-a0e758621b13 the metric system should be used as default - @@ -594,7 +576,6 @@ b6cf8d5f-0fc9-46f7-8e38-8342a1229037 every security incident must be clearly documented and investigated – do not obscure it - @@ -652,7 +633,6 @@ b5a128a2-31d9-49df-890c-59a770f7afa9 the contributor must not loose the right to use or distribute the contributed code under any license (of his choice) - @@ -675,5 +655,4 @@ plan of supported versions/branches -