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

Adjust style/layout on the day to day in Fedora

Browse source 
Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
This commit is contained in:
Pierre-YvesChibon 2019-08-01 15:48:11 +02:00
commit 674312ba00
2 changed files with 23 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -7,34 +7,36 @@ do the work you are asking us to do.
== Our Workflow
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 related to security of an application or service we run?
* send email to infra-security@fedoraproject.org
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.
-> If no answer or the oncall person asks you to: go to next step.
2. 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, freenode, /join #fedora-admin and say _.oncall_ and explain the issue to the oncall person.
* If no answer:
** If you cannot authenticate to `pagure.io`, send an email to `admin` @ fedoraproject.org
** Otherwise: go to next step.
2. File a ticket in https://pagure.io/fedora-infrastructure/issues/ with as much information
3. 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.
-> 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.
* 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 the ticket is otherwise closed, it will be with a explaination from a team member.
4. 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.
* f 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:
-> comment in the ticket adding that information or asking for timeframe.
5. If you have an update to your issue/task or want to know when it might be worked on:
* comment in the ticket adding that information or asking for timeframe.
5. When someone is available, your ticket will be assigned to someone to work on.
-> Watch for progress reports/ticket being marked done.
6. When someone is available, your ticket will be assigned to someone to work on.
* Watch for progress reports/ticket being marked done.
6. If the work is not fully completed as required, please re-open the ticket and indicate this.
-> go back to step 5 for additional work.
7. If the work is not fully completed as required, please re-open the ticket and indicate this.
* go back to step 6 for additional work.
== The oncall role in our team

2
modules/cpe/pages/working_with_us.adoc
View file

@ -31,7 +31,7 @@ ticket tracking system :)
In this case, you do not want to send your email or ping a single person
(cf the first point above).
- In Fedora, you can use the email: `contact` @ fedoraproject.org
- In Fedora, you can use the email: `admin` @ fedoraproject.org
- In CentOS, you can contact the sysadmins on the `#centos-devel` channel on irc.freenode.net