At current, we rely on slackbot cross-posting community issues and PRs to track issues / PRs that need maintainer responses - but we don't include tracking these issues in our ZenHub workflows.
In this issue, we'll determine a new mechanism to add to our standard workflows to enable better tracking of community issues / PRs.
This might look like: new ZH pipelines / board for community issues, ConjBot auto-add community GH issues / PRs to the right ZH pipelines on the right board, etc.
May be related to #85 and potentially #84.
AC:
[ ] Define how we'll improve our community issue / PR tracking
[ ] File issues to implement the changes needed to implement the improvement plan.
At current, we rely on slackbot cross-posting community issues and PRs to track issues / PRs that need maintainer responses - but we don't include tracking these issues in our ZenHub workflows.
In this issue, we'll determine a new mechanism to add to our standard workflows to enable better tracking of community issues / PRs.
This might look like: new ZH pipelines / board for community issues, ConjBot auto-add community GH issues / PRs to the right ZH pipelines on the right board, etc.
May be related to #85 and potentially #84.
AC: