| |
@@ -30,8 +30,10 @@
|
| |
|
| |
This document is divided into two parts, the first part is yours to fill.
|
| |
It is basically the what and why of your request:
|
| |
- - What do you want the CPE team to work on
|
| |
- - Why do you think it is worth for the CPE team to work on it
|
| |
+
|
| |
+ * What do you want the CPE team to work on
|
| |
+ * Why do you think it is worth for the CPE team to work on it
|
| |
+
|
| |
The second part will be filled out later by you and the CPE team once your
|
| |
proposal has been accepted based on its what and why.
|
| |
|
| |
@@ -43,6 +45,7 @@
|
| |
To do this, simply open a ticket on the link:https://pagure.io/cpe/initiatives-proposal[CPE-initiatives issue tracker].
|
| |
|
| |
You will be asked in this ticket a few things:
|
| |
+
|
| |
- a link to your requirement document
|
| |
- potential dependencies for this initiative (dependencies on people or
|
| |
other initiatives)
|
| |
@@ -52,8 +55,8 @@
|
| |
=== First decision point: is this initiative for the CPE team?
|
| |
|
| |
Based on these information the CPE team will decide if this initiative is
|
| |
- in the scope of the CPE team (ie: does it fit its [mission statement]()?)
|
| |
- but also if there is a clear benefit for the communities the CPE team is
|
| |
+ in the scope of the CPE team (ie: does it fit its xref:mission_statement.adoc[Mission
|
| |
+ Statement]), but also if there is a clear benefit for the communities the CPE team is
|
| |
involved in.
|
| |
|
| |
If your initiative doesn't fit for the CPE team, it does not mean your
|
| |
@@ -76,7 +79,7 @@
|
| |
This step may involve calling for feedback the communities affected by this
|
| |
change.
|
| |
|
| |
- The part II of the requirement document should be kept up to date to
|
| |
+ The second part of the requirement document should be kept up to date to
|
| |
reflect the technical solution of choice and possibly the solutions
|
| |
considered with why they were rejected (this could also be stored in a
|
| |
different document linked to).
|
| |
@@ -109,6 +112,6 @@
|
| |
This new workflow will be a change from how the CPE team has worked up
|
| |
until now. Its core idea is to maximize the output of the team to the
|
| |
community. We are not able to accept everything and anything and we want to
|
| |
- make sure what we accept is properly limited in scoped and time.
|
| |
- Hopefully this will allow us to work on more initiative and bring more
|
| |
+ make sure what we accept is properly limited in scope and time.
|
| |
+ Hopefully this will allow us to work on more initiatives and bring more
|
| |
beneficent changes to our communities.
|
| |
Signed-off-by: Michal Konečný mkonecny@redhat.com