Documentation community triage 26-04-09

Events
1

A member of the documentation community conducts a triage of open PRs and issues. The purpose is to minimize the number of stalled PRs and issues and help community members move forward.

There is no meeting. The triage lead reviews open PRs and issues, and leaves comments on GitHub or messages in the #theforeman-doc:matrix.org channel.

1 Like
2

A suggestion for how to run the triage:

1. Look at list of open PRs, excluding the ones in draft state, sorted by least recently updated: Pull requests · theforeman/foreman-documentation · GitHub

  • Are there any blockers?
  • If you spot a blocker, can you help resolve it? For example, you can notify a reviewer or leave a reminder for the author to continue working on the PR.
  • If the chances of moving the PR forward are low for any reason, consider suggesting to switch the PR into draft state. This excludes the PR from the triage list.

2. Look at list of open issues, sorted by least recently updated: GitHub · Where software is built

  • Are there any blockers?
  • If you spot a blocker, can you help resolve it? For example, you can identify someone to provide missing input or share the link in the Matrix channel to ask if anyone can assign the issue to themselves.
  • If the chances of ever fixing the issue are low for any reason, consider closing the issue with an explanation.
1 Like
3

Thanks Anet, I think it went well from what I saw on GitHub. I would volunteer to do it in April.

4

One more thing that worked for me (and I forgot to add it to the suggestion above) was to make this a time-boxed activity: A triage lead should set an allotted time to conduct the triage, such as 15 minutes for PRs and 15 minutes for issues. This makes it clear that it’s not expected to review all PRs and issues, and sticking to a reasonable time slot makes this task easier to fit into a person’s schedule.

5

Due to downstream obligations, I will postpone this to Mon April 20th or Tue April 21st.