Template:PT Request for Comments: Difference between revisions

This page exists on the shared resources wiki
Autogenerated
 
Autogenerated
 
Line 4: Line 4:
|-
|-
!Component:
!Component:
|name of the affected component or structure
|name of the affected component or structure
|-
|-
!Stakeholders:
!Stakeholders:
|who is affected by or influences the idea or its results?
|who is affected by the idea or influences its result?
|-
|-
!Created:
!Created:
Line 20: Line 20:
|-
|-
!Status:
!Status:
|'''in draft''' / in discussion / accepted / declined
| class="select" |'''in draft''' / in discussion / accepted / declined
|-
|-
!End date:
!Feedback until:
|mm/dd/yyyy
|mm/dd/yyyy
|}
|}
</div>
</div>
</div>
</div>
==Description==
{{Textbox|boxtype=note|header=How a request for comments works|text=A 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.|icon=yes}}
A Request for Comment (RfC) is a tool for assessing and evaluating internal projects or ideas for change. A maximum of two weeks should elapse before a decision is made. If the RfC is approved, the corresponding tickets for implementation will be created after completion.


Give a brief executive summery of the topic here.
== 📝 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.


==Realisation ==
== 🛠️ Proposed implementation ==
How to proceed:
How would the idea be put into practice?
 
{| class="wikitable" style="width:100%;"
{| class="wikitable wikitablee" style="width:100%;"
!'''Step'''
!'''Step'''
!'''Description'''
!'''Description'''
|-
|-
|What needs to happen
|What needs to happen?
|Details about this step
|Details about this step – who is involved and what is the result?
|-
|-
|..
|..
Line 49: Line 48:
|}
|}


==Advantages / chances==
== ⚖️ Advantages and disadvantages ==
Why we should do this?
{{ProConList
|title-advantages=👍 Advantages / opportunities
|title-disadvantages=👎 Disadvantages / risks
|advantages=
*Which problem disappears?
*Who benefits – and how noticeably?
|disadvantages=
*Which costs, risks or dependencies come with it?
*What could go wrong during the implementation?
}}
 
== 🎯 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.


==Disadvantages / risks==
*'''Effort:''' e.g. approx. 10 person-days
What issues do we expect?
*'''Earliest start:''' mm/dd/yyyy
*'''Expected duration:''' e.g. 4 weeks


==Affected areas / effects==
== 💬 Comments and evaluation ==
Which areas are affected and how?
What does everyone think about the idea? Add your comment and sign it so that questions can be clarified directly.


==Time estimate==
*Comment – ''name''
How long will it take?
*Comment – ''name''


== Comments and evaluation ==
<bs:signhere />
What does everyone think about the idea?


*comment, name / sign
== ✅ Result ==
*comment, name / sign
{{Decision|decision=Record the result here: accepted, declined or postponed – including reason and decision date.}}

Latest revision as of 04:58, 3 November 2026

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
  • Which problem disappears?
  • Who benefits – and how noticeably?
  • Which costs, risks or dependencies come with it?
  • What could go wrong during the implementation?

🎯 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.}}