You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Write to the #packit channel to inform everyone about the possible service disruption during the upgrade
Work with the Chief of Monitors to handle sentry alerts that may happen during the upgrade
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.
The text was updated successfully, but these errors were encountered:
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 thebacklog
column once the issue is clear.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.
Watch auto-packit-shared-infra mailing list for planned cluster upgrades. Once one is scheduled:
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.The text was updated successfully, but these errors were encountered: