Project assessment with focus on research software/open science aspects

I did an assessment with the recommendations regarding research software in mind. Here are my suggestions (some of them I will apply via PR later on, marked with (PR)):

1. Readme/Documentation: Add a short statement right in the beginning who will/should be the users of SaQC
2. Readme/Documentation: Try to describe your software in 1-2 sentences only right in the beginning
3. Documentation: Already any existing case studies for your software? If there is no 'real live' example yet try describe a common workflow
4. Readme (PR): Add Sections: Changelog (just in case: https://keepachangelog.com/), Contributing, Copyright and License, Acknowledgements, Repo Status (https://www.repostatus.org/)
5. Add citation.cff to Repo (PR) (https://citation-file-format.github.io/)
6. Documentation: if applicable add any troubleshooting information
7. Readme/Documentation: Add information how a user can get help/report issues (contact, wiki, gitlab, mailing list etc)
8. Do you support your (future) users in any way? I guess there is no initial plan for that yet, UFZ users maybe? Maybe a user support email address?
9. Tags are not described/release notes (just link them tags later to the changelog :)
10. Documentation: You probably have any dependencies that should be listed here
11. Twitter: when you officially release, just give me a shot and I will do the promotion limbo on twitter :)
12. Readme: Add Section: Publications (applicable in the future, I guess :), How to cite
13. Source code files: copyright information in each file header recommended
14. CLA - Contributor license agreement - something for the future to think about (if not done already), especially when using GPL (http://contributoragreements.org/ https://cla-assistant.io/)