eclipse-score / eclipse-score/score

EPIC: Document Design Decision process

Open
#2,625 1 comment 0 reactions 1 assignee Claimed by @pahmann View on GitHub
documentation
Dominant language
Starlark
Stars
109
Forks
105
Avg merge
1d 9h
Merged PRs (30d)
24

Description

### What

Currently the Change Management process has a template https://eclipse-score.github.io/process_description/main/process_areas/change_management/guidance/change_management_decision_record_template.html - but it is not described in the process how to use it. Especially:
- Who needs to approve, what is the review process?
- How to plan the consequences of a decision?
- Are there different variants for different affected areas?
- How do we verify that a design decision is respected?

See also https://github.com/orgs/eclipse-score/discussions/2234#discussioncomment-15869210

### How

_No response_

### Estimates for realization

1 week

### Category

- [ ] Affects Detailed Design

### Requirements / Architecture

- [x] Requirements / Architecture are not affected by this change?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.