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

Add a glossary and expand on the day to day workflow in Fedora #12

Merged
zlopez merged 2 commits from glossary_and_more into master 2026-06-09 02:37:25 +00:00
Conversation 19 Commits 2 Files changed 4 +130 -28
pingou commented 2020-09-18 09:06:47 +00:00
Contributor
Copy link
No description provided.
pingou commented 2020-09-18 09:07:16 +00:00
Author
Contributor
Copy link

The resulting doc can be viewed at: http://ambre.pingoured.fr/cpe-docs/cpe/

The resulting doc can be viewed at: http://ambre.pingoured.fr/cpe-docs/cpe/
siddharthvipul1 commented 2020-09-18 09:25:54 +00:00
Contributor
Copy link

all looks good to me
+1 to merge

all looks good to me +1 to merge
pingou commented 2020-09-18 09:27:26 +00:00
Author
Contributor
Copy link

2 new commits added

  • Adjust the day to day with Fedora page
  • Add a glossary page
**2 new commits added** * ``Adjust the day to day with Fedora page`` * ``Add a glossary page``
lgriffin commented 2020-09-18 13:54:33 +00:00
First-time contributor
Copy link

I'd like to see a section on ticket stagnation. So we have a big ticket backlog and often when time goes by we don't know if the ticket is still valid.....has a complimentary change fixed it, is it back working now and just an intermittent issue. This costs us time in comms and debugging / recreation and we also want our community involved and hopefully helping out. So effectively we want a pulse on the priority of the ticket. How about a small section on that to ask for priority pings and tickets >X days old with no actions from the person who opened it and / or no follow up by CPE will be deemed low priority and may ultimately be closed. As an aside a really nice side project for someone would be to create a script to ping any tickets >X days without an update asking is this still valid and if we don't hear from you it will be closed in X days.

Other than that, +1, merge

I'd like to see a section on ticket stagnation. So we have a big ticket backlog and often when time goes by we don't know if the ticket is still valid.....has a complimentary change fixed it, is it back working now and just an intermittent issue. This costs us time in comms and debugging / recreation and we also want our community involved and hopefully helping out. So effectively we want a pulse on the priority of the ticket. How about a small section on that to ask for priority pings and tickets >X days old with no actions from the person who opened it and / or no follow up by CPE will be deemed low priority and may ultimately be closed. As an aside a really nice side project for someone would be to create a script to ping any tickets >X days without an update asking is this still valid and if we don't hear from you it will be closed in X days. Other than that, +1, merge
pingou commented 2020-09-18 15:18:15 +00:00
Author
Contributor
Copy link

@lgriffin we have:

It is your responsibility as ticket reporter to follow your ticket, provide information that is asked for, and keep us aware of any urgency you may have. Do not simply file and forget your ticket.

Your ticket may take a while to process, depending on the current workload of 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 already be working on tickets that are blocking more people.

at: http://ambre.pingoured.fr/cpe-docs/cpe/day_to_day_fedora/#_general_ticket_considerations

Though I realize it doesn't cover the: "if you don't respond to an old ticket in X days, we reserve the right to close it".

@lgriffin we have: ```` It is your responsibility as ticket reporter to follow your ticket, provide information that is asked for, and keep us aware of any urgency you may have. Do not simply file and forget your ticket. Your ticket may take a while to process, depending on the current workload of 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 already be working on tickets that are blocking more people. ```` at: http://ambre.pingoured.fr/cpe-docs/cpe/day_to_day_fedora/#_general_ticket_considerations Though I realize it doesn't cover the: "if you don't respond to an old ticket in X days, we reserve the right to close it".
lgriffin commented 2020-09-18 15:22:46 +00:00
First-time contributor
Copy link

+1 this is a good start and the latter half of my request is disconnected. Ship it!

+1 this is a good start and the latter half of my request is disconnected. Ship it!
pingou commented 2020-09-18 15:26:13 +00:00
Author
Contributor
Copy link

2 new commits added

  • Adjust the day to day with Fedora page
  • Add a glossary page
**2 new commits added** * ``Adjust the day to day with Fedora page`` * ``Add a glossary page``
pingou commented 2020-09-18 15:26:18 +00:00
Author
Contributor
Copy link

@lgriffin added in the same section:

Every now and then, we will go through our old tickets. When this happen we may
ask you to check if the issue still exists (it could be that a complimentary
change fixed it, or that was just an intermittent issue or simply that it got
fixed without us knowing). In those situation, we kindly ask that you reply to
our question/ping within two weeks, otherwise we reserve the right to close the
ticket (knowing that you can always re-open it or open a new one if the issue
persists or re-appeared).
@lgriffin added in the same section: ```` Every now and then, we will go through our old tickets. When this happen we may ask you to check if the issue still exists (it could be that a complimentary change fixed it, or that was just an intermittent issue or simply that it got fixed without us knowing). In those situation, we kindly ask that you reply to our question/ping within two weeks, otherwise we reserve the right to close the ticket (knowing that you can always re-open it or open a new one if the issue persists or re-appeared). ````
kevin commented 2020-09-18 18:51:30 +00:00
Owner
Copy link

Waiting on reporter?

Waiting on reporter?
kevin commented 2020-09-18 18:52:35 +00:00
Owner
Copy link

Otherwise looks great to me... I think we may want to come up with some more detailed plan for backlog at some point, but I think that might take more discussion and agreement.

Otherwise looks great to me... I think we may want to come up with some more detailed plan for backlog at some point, but I think that might take more discussion and agreement.
pingou commented 2020-09-20 18:11:42 +00:00
Author
Contributor
Copy link

indeed, thanks for catching it :)

indeed, thanks for catching it :)
pingou commented 2020-09-20 18:12:17 +00:00
Author
Contributor
Copy link

rebased onto 9342416f31

rebased onto 9342416f31df202b0d16c4a60e0212de0332ef91
zlopez commented 2020-09-21 07:51:01 +00:00
Owner
Copy link

Not sure if this is just on my side, but I spent last two weeks (without Fridays) working on https://pagure.io/fedora-infrastructure/issue/9199 and it is considered a medium trouble.

Not sure if this is just on my side, but I spent last two weeks (without Fridays) working on https://pagure.io/fedora-infrastructure/issue/9199 and it is considered a medium trouble.
pingou commented 2020-09-21 07:52:12 +00:00
Author
Contributor
Copy link

I agree that according to this scale this should be a high trouble one

I agree that according to this scale this should be a high trouble one
zlopez commented 2020-09-21 07:53:38 +00:00
Owner
Copy link

Just one comment about the evaluation of the tickets, otherwise 👍

Just one comment about the evaluation of the tickets, otherwise :thumbsup:
mohanboddu commented 2020-09-21 13:25:15 +00:00
First-time contributor
Copy link

Rather than saying morning, give the timings in UTC or some TZ, US meeting is not technically in the morning depending on TZ, for me its in the afternoon.

Rather than saying `morning`, give the timings in UTC or some TZ, US meeting is not technically in the morning depending on TZ, for me its in the afternoon.
pingou commented 2020-09-21 13:28:15 +00:00
Author
Contributor
Copy link

I feared giving precise times would fall out of date too quickly (another place we need to remember to update if/when we change the stand up time).
Maybe something along the lines of: (one more European-timezone friendly and one more US-timezone friendly). What do you think?

I feared giving precise times would fall out of date too quickly (another place we need to remember to update if/when we change the stand up time). Maybe something along the lines of: ``(one more European-timezone friendly and one more US-timezone friendly)``. What do you think?
pingou commented 2020-10-01 15:37:07 +00:00
Author
Contributor
Copy link

2 new commits added

  • Adjust the day to day with Fedora page
  • Add a glossary page
**2 new commits added** * ``Adjust the day to day with Fedora page`` * ``Add a glossary page``
pingou commented 2020-10-05 10:54:32 +00:00
Author
Contributor
Copy link

Pull-Request has been merged by pingou

Pull-Request has been merged by pingou
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cle/docs!12
No description provided.