| Component: | name of the affected component or structure |
|---|---|
| Stakeholders: | who is affected by the idea or influences its result? |
| Created: | mm/dd/yyyy |
| Initiator / requester: | username |
|---|---|
| Status: | in draft / in discussion / accepted / declined |
| Feedback until: | mm/dd/yyyy |
How a request for comments worksA request for comments (RfC) is used to assess internal projects or change proposals. Everyone concerned comments by the given end date – no more than two weeks should pass until the decision. Once accepted, the implementation tickets are created.
📝 Summary
Describe the idea in three to five sentences: what do you propose, and which problem does it solve? Readers should understand the proposal without any prior knowledge.
🛠️ Proposed implementation
How would the idea be put into practice?
| Step | Description |
|---|---|
| What needs to happen? | Details about this step – who is involved and what is the result? |
| .. | |
| .. |
⚖️ Advantages and disadvantages
| 👍 Advantages / opportunities | 👎 Disadvantages / risks |
|---|---|
|
|
🎯 Affected areas
Which teams, processes or systems are affected – and in which way?
- Area 1: what changes there?
- Area 2: what changes there?
⏱️ Effort and schedule
Estimate the effort and name a realistic time frame.
- Effort: e.g. approx. 10 person-days
- Earliest start: mm/dd/yyyy
- Expected duration: e.g. 4 weeks
💬 Comments and evaluation
What does everyone think about the idea? Add your comment and sign it so that questions can be clarified directly.
- Comment – name
- Comment – name
<bs:signhere />
✅ Result
Record the result here: accepted, declined or postponed – including reason and decision date.
{{#set:Decision=Record the result here: accepted, declined or postponed – including reason and decision date.}}
