cle/docs
36
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

Fix typos and improve readability

Browse source 
Signed-off-by: Michal Konečný <mkonecny@redhat.com>
This commit is contained in:
Michal Konečný 2019-08-01 15:08:51 +02:00
commit 399c20da84
4 changed files with 22 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

16
modules/cpe/pages/day_to_day_fedora.adoc
View file

@ -10,21 +10,21 @@ do the work you are asking us to do.
0. Is your issue/problem related to security of an application or service we run?
-> send email to infra-security@fedoraproject.org
1. Is your issue/problem urgent? (A important service is down, you need a change asap)
1. Is your issue/problem urgent? (An important service is down, you need a change asap)
or IS your issue/problem such that you cannot file a ticket (authentication, no account, ticketing system down)
-> on irc /join #fedora-admin and say '.oncall' and explain the issue to the oncall person.
-> on irc /join #fedora-admin and say _.oncall_ and explain the issue to the oncall person.
-> If no answer or the oncall person asks you to: go to next step.
2. File a ticket in https://pagure.io/fedora-infrastructure/issues/ with as much information
as you think will be needed to handle your issue. This initial ticket will be made in the
'Needs review' state. Please note if there is a deadline or this issue blocks you.
_Needs review_ state. Please note if there is a deadline or this issue blocks you.
-> your ticket will be reviewed within 48 hours. (usually sooner)
-> There is no need to ping team members or notify us about the newly filed ticket.
3. your ticket will be triaged by a team member and moved to a new state:
-> If it's moved to 'Waiting on asignee' it's waiting for a team member to start work on it.
-> If it's moved to 'Waiting on reporter' it means that you need to answer questions posed in the ticket before it can be worked on.
-> If the ticket is closed with 'initiative', See xref:initiatives.adoc[New Initiative Workflow]
-> If it's moved to _Waiting on asignee_ it's waiting for a team member to start work on it.
-> If it's moved to _Waiting on reporter_ it means that you need to answer questions posed in the ticket before it can be worked on.
-> If the ticket is closed with _initiative_, See xref:initiatives.adoc[New Initiative Workflow]
-> If the ticket is otherwise closed, it will be with a explaination from a team member.
4. If you have an update to your issue/task or want to know when it might be worked on:
@ -40,7 +40,7 @@ as you think will be needed to handle your issue. This initial ticket will be ma
== The oncall role in our team
Weekly a team member will be designated “oncall”. You can find this
person on IRC by using '.oncall' in any of our various IRC channels.
person on IRC by using _.oncall_ in any of our various IRC channels.
When available, this person:
1. Accepts urgent work items for the team, for example a important
@ -81,7 +81,7 @@ simply file and forget your ticket.
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
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.

4
modules/cpe/pages/index.adoc
View file

@ -25,9 +25,9 @@ image::our_missions.jpg[Our Mission,500,500]
One of the key challenges this team faces is balancing these three axes.
For this reason, we worked on the following Mission Statement.
== Our responsabilities
== Our responsibilities
Our responsabilities are scoped in our mission statement:
Our responsibilities are scoped in our mission statement:
=== Our Mission Statement

6
modules/cpe/pages/initiatives.adoc
View file

@ -31,8 +31,8 @@ for you to use to write down your requirement document.
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 subject and the specified reason.
@ -63,7 +63,7 @@ If your initiative doesn’t fit in the purview of the CPE team, it does not mea
your challenge is not worth pursuing but that the CPE team has limited
resources and needs to be careful on how they are spent.
Every two weeks, the CPE will meet to go over the proposed initiatives. At this
Every two weeks, the CPE team will meet to go over the proposed initiatives. At this
point, the CPE team will decide if it accepts your initiative or, if necessary,
appoint someone who will work with you to polish this document, improve the
user-story, and discuss with you what is in scope and what isn’t.

10
modules/cpe/pages/sle.adoc
View file

@ -115,7 +115,15 @@ items rely on services in their own circle or a circle below them.
with no planned or unplanned outages. This is a combination of high
availability and continuous operations.
* **Level of availability**: | Percentage | Max outage time per day | | 90% | 144.0 minutes | | 95% | 72.0 minutes | | 99% | 14.4 minutes | | 99.9% | 1.4 minutes |
* **Level of availability**:
[options="header"]
|======================================
|Percentage | Max outage time per day |
| 90% | 144.0 minutes |
| 95% | 72.0 minutes |
| 99% | 14.4 minutes |
| 99.9% | 1.4 minutes |
|======================================
* **Commited Hours of Availability**: Hours that an organization will have
staff available to help deal with issues with systems, services, and