#1 Few small fixes
Merged 4 years ago by pingou. Opened 4 years ago by zlopez.
cpe/ zlopez/docs small_fixes  into  master

@@ -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.

@@ -38,7 +38,7 @@ 

  

  == Larger projects / feature requests

  

- All asks involving new applications, major deployments, major development work

+ All tasks involving new applications, major deployments, major development work

  or the like will be asked to follow the xref:initiatives.adoc[New Initiative

  Workflow]. It will then be scoped and prioritized from there.

  
@@ -62,7 +62,7 @@ 

  If you are unsure where to file a ticket or what information

  to place in it, please ask the oncall person or mail the team at https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/

  

- Your ticket may well take a while to process depending on the work

+ Your ticket may take a while to process depending on the work

  that the team has and how important we think it is. If your ticket

  is blocking you, make sure you note that in the ticket but keep in

  mind that we may be working on tickets that are blocking more people.

Pull-Request has been merged by pingou

4 years ago