Merge pull request #32 from messerli-informatik-ag/remove-glossary

Remove the failed glossary concept

Author: Ruben Schmidmeister

documentation/src/guidelines.md

@@ -10,9 +10,9 @@ The rules will not be enforced for old code, which has not been changed.
 In a review, these coding guidelines should be checked for all code, which has changed.
 Changes necessary due to the coding guidelines should be in a reasonable ratio to the functional changes.
 
-## Update to the rules and glossary
+## Update to the rules
 
-Updates to the rules and glossary should be sent to the developer council. The developer council will integrate new rules or new words in the glossary in a timely fashion when the board approves and will give feedback otherwise.
+Updates to the rules should be sent to the developer council. The developer council will integrate new rules in a timely fashion when the council approves and will give feedback otherwise.
 
 ## Definition of done
 

documentation/src/naming.md

@@ -12,7 +12,6 @@ Give a descriptive name, but be specific. Do not worry about saving horizontal s
 * It is a lot easier to create plurals in English (-s, -ies) where in German it might be difficult: Kapitel, Mitarbeiter, Unternehmer, Fenster, Artikel (see also next point)
 * Proper Nouns  should not be translated even if possible.
 * We try to use the same word for the same abstraction. It is either a project or a tenant. (DDD)
-* All widely used concepts should be listed in the glossary
 
 ## Be specific