Community Shepherd

[usercont-release-bot]

Packit

• Be present in #packit:fedora.im (Matrix), #team-packit:redhat-internal.slack.com and Packit gchat channel to answer community questions or ping some other team member to help answer those questions.

• Keep an eye on incoming issues opened by our users, even those from the past week-end. The unprocessed issues can be found in the new column of our Kanban board. React to them trying to clarify them, if needed, or ask the team to help give a meaningful reaction to them. Use appropriate labels and move the issue to the backlog column once the issue is clear. (We do this together on standups).

• Help new users trying to enable Packit Service to configure their repositories.

• Watch out for incoming issues in github.com/packit/notifications if someone needs help with the automatic approval process (see docs for manual allowlisting). Delete old, unanswered issues, or the ones which look like spam.

• Keep an eye on new and unanswered discussions, try to comment and/or tag other team members if necessary.

• If the team goes on Vacation update channels topics (on Matrix and Slack) and create a new status post.

• Watch our dashboard, in case of failing pull from upstream jobs be proactive. Try to propose a fix to the user. You can ask to the team a help for fixing or understanding the problem.

• Watch deployment repo for new PRs of users opting-in to Fedora CI using enabled_projects_for_fedora_ci (example PR):

  • approve the PR
  • update the packit-config secret and rescale the workers
  • comment in PR that the change was applied and merge the PR

Jotnar

• Respond in Jiras and MRs if someone outside of our team comments there so humans have proper feedback
• Respond to questions and comments in our forum channel
• Check new issues reported in RHELMISC Jira project for component jotnar-package-automation