8000 Escalation path for technical decisions · Issue #262 · eclipse-score/score · GitHub

More Web Proxy on the site http://driver.im/

Escalation path for technical decisions #262

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Closed

antonkri opened this issue Jan 30, 2025 · 2 comments

Assignees

Contributor

antonkri commented

Proposal: technical lead circle should make proposal till 31.01.2025, @antonkri will create a ticket.
The overall goal: in S-CORE we should have for every problem only one solution. Distributors could still replace some S-CORE modules with their own ones.
We should enforce, that all our solutions look the same and fit each other ("wie aus einem Guss").

antonkri moved this to Todo in Technical Lead Circle LOP

antonkri added this to Technical Lead Circle LOP

Contributor

johannes-esr commented

Proposal:

CFT & Communities should find consens
If no consens is found, esclation to Technical Lead Circle
Technical problems to be solved in Technical Lead Circle, Strategical problems to be further escalated to Project Lead Circle
Voting in Technical & Project Lead Circle, one vote per project / technical lead
--> to be presented in Project Lead Circle on 2025-02-14 @antonkri

Contributor Author

antonkri commented

Proposal agreed and needs to be documented in Project Handbook

8131

antonkri self-assigned this

antonkri removed the status in Technical Lead Circle LOP

FScholPer closed this as completed

github-project-automation bot moved this to Done in Technical Lead Circle LOP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

0