Every week we dedicate one individual (the community contact) to watch for user issues and either answer them or redirect the questions to other who can. The community contact's duty (subject to change) is as followed:
- Check the knative-users@ mailing list and #eventing-questions Slack channel for new unanswered questions.
- Check Eventing unassigned issues / untriaged issues for unanswered questions.
- Check Slack channel #eventing-questions for unanswered questions. Any questions that relates to usability please instruct user to open an usablity issue and to join the channel #user-experience to capture user feedback.
- Check Docs unassigned issues / untriaged issues for unanswered questions.
- You should already be added to @eventing-help usergroup by the previous contact person, and will be tagged into user questions in other channels.
- Answer relevant Stack Overflow Questions
- Check 'Eventing Triage' Peribolos group https://github.com/knative/community/blob/main/peribolos/knative.yaml and send a PR to add yourself if you aren't already in there.
- Check the Eventing test grid for flakiness to pick a test and focus on fixing it during your week. Once you pick the test flake, assign the corresponding bug filed by flakiness test reporter to yourself so that others won't pick the same test to fix.
- Join the @eventing-help user group if you haven't been invited by the previous contact person using this link
Continue on fixing test flakes and answer
- Remove yourself from @eventing-help usergroup and add the next contact using this link. If you don't have permission, ask in the Slack channel #steering-toc-questions.
- Email the next contacts, cc'ing knative-dev@ with a short summaries of the user questions encountered and links to them.
- File issue or document suggested improvements to this process.
Participation is voluntary and based on good faith. The community contacts are only expected to participate during their local office hour.
We seed this rotation with all approvers and reviewers from all the Eventing workgroups, excluding productivity. If you are no longer active in Knative, or if you are contributing on personal capacity and do not have time to contribute in the rotation, feel free to send a PR to remove yourself and add yourself to the NON_ROSTER file. Similarly, you can trade your timeslot with others by sending PRs.
Those who aren't reviewers or approvers and are interested in volunteering are
welcome to add themselves to the support/VOLUNTEERS file.
The schedule can be regenerated randomly for a new cycle with the command (run from the eventing base directory).
ROSTER=$(cat support/ROSTER support/VOLUNTEERS)
echo ${ROSTER} | sed 's/ /\n/g' | sort | uniq | sort -RSee a machine-readable schedule here. The format is:
# comment lines are okay
#@ metadata: value of the metadata
RFC3339-date | username
You can see the current oncall at https://knative.party/ (which reads the machine-readable file).