Create documents explaining how to contribute and what to look out for.

[Jonas-Sander]

Some random notes:

• Create CONTRIBUTING.md
• Explain Pull-Request Flow (WIP/Review - first create issue if you're unsure about the change)
• Definition of done (Testing (Unit / E2E), Analytics, ....)
• How to do local testing (is this possible? Might we need to create another Firestore project?)
• Where does which code go?
• Which structure do we use for our code (BLOC, Domain logic, etc.)
• We do not gurantee that we add your change
• Code of Conduct?

[Jonas-Sander]

Also we should create a general overview about the structure of the code (e.g. what are the general domains and how do they relate to each other?) and the repository (what folders are there and where are things located? - e.g. translations, helper scripts, etc).

[nilsreichardt]

The CONTRIBUTING.md of other open source projects:

• FlutterFire
• leaf
• Flutter

This can help us to get inspiration for our CONTRIBUTING.md and understand what the best practice is.