Define selection criteria for open source software

🧩 User Story

As a developer and architect for CIVITAS/CORE I want to have selection criterias for open source software, in order to know if I can use them.

🎯 Goal & Context

CIVITAS/CORE is very strict about being published as open source software. So should we when choosing a new piece os software, e.g. a component or framework to extend it. The use of new method to be implemented should result in a decision within a few minutes.

🛑 Boundaries & Implementation Notes

Please see this discussion in an internal miro Board (Dev V2) and update it according to the notes there. This issue depends on documentation#35.

✅ Acceptance Criteria

This issue is considered done when:

• a proposal exist that takes the previous discussions into account
• the proposal was approved by the product owner
• the new method shall give a result within less or equal 10 minutes
• the proposal is published in the documentation (docusaurus)