WiP check if confluence gets this included

content/en/docs/project/team-process/_index.md

@@ -0,0 +1,38 @@
+---
+title: Team and Work Process 
+weight: 50
+description: The way we work
+linkTitle: Team-Process
+---
+
+
+## Structure
+
+1. each task and/or user story has at least a branch in an existing repo or a new, dedicated task repo
+    > recommended: multi-repo over monorepo
+1. each repo has a main and development branch. development is the intgeration line
+1. pull requests are used to merge work outputs to the integration line
+1. optional (my be too cumbersome9: each PR should be reflected as comment in jira
+
+## Workflow
+
+* `git init` --> always create as fast as possible a new repo
+
+## Definition of Done
+
+1. Jira: there is a final comment summarizimg the outcome (in a bit more verbose from than just the 'resolution' of the ticket) and the main outputs. This may typically be a link to the commit and/or pull request of the final repo state
+2. repo: there is a README.md in the root of the repo. It summarizes in a typical Gihub-manner how to use the repo, so that it does what it is intended to do and reveals all the bells and whistles of the repo to the consumer. If the README doesn't lead to the usable and recognizable added value the work is not done! 
+
+## Review
+
+* Before a ticket gets finished (not defined yet which jira-state this is) there must be a review by a second team member
+* the reviewing person may review whatever they want, but must at least check the README
+
+## Out of scope (for now)
+
+The following topics are optional and do not need an agreement at the moment:
+
+1. Commit message syntax
+1. branch permissions
+1. branch clean up policies
+1. squashing when merging into the integration line