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:
- Remove yourself from
@serving-helpusergroup 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. - Send updates to this process.
- See All days
- Check the Serving 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.
- Check the knative-users@ mailing list.
- Check Slack channel #knative and #knative-serving for unanswered questions. Any questions that relates to usability please instruct user to open an usablity issue and to join the channel #knative-documentation to capture user feedback.
- Triage issues. Quick links:
- Untriaged issues
- User feedback issues updated more than 3 days ago -- YOU NEED TO UPDATE THE DATE IN THE QUERY
- Check Docs unassigned issues / untriaged issues for unanswered questions.
- Answer relevant Stack Overflow Questions
Participation is voluntary and based on good faith. We are only expected to participate during our local office hour.
We seed this rotation with all approvers from all the Serving 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.
See 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).