Clean up issues and setup cycle milestones for fall

[dcwalk]

Per July 10 Archiving/Tech Working Group meeting, we are going to:

• clean up current issue labels in overview repo
• review and close out issues that no longer reflect current projects/ways of working
• add milestones to begin to experiment with tracking planning/goal cycles

In addition I'd like to

• ping decision-holders when unclear about status of issue (i.e., is this wontdo or closable?)'
  • resolve status for Deploy halpy bot on Archivers slack #139 Democratize ability of community members to run video calls #150 Onboarding feedback #156 Create Awesome lists for our tool tracking needs #130 Configure and document IRC bridge for Archivers Slack #166 trello-based onboarding to webmonitoring dev #143
• identify stalled issues

[dcwalk]

Hey, this might have been a noisy day for @titaniumbones and @patcon -- if so here is why!

[dcwalk]

Issues that may be resolved, potentially wontdo or unclear about status/next step:

• Deploy halpy bot on Archivers slack #139
• Democratize ability of community members to run video calls #150
• Onboarding feedback #156
• Create Awesome lists for our tool tracking needs #130
• Configure and document IRC bridge for Archivers Slack #166
• trello-based onboarding to webmonitoring dev #143

[dcwalk]

Hey @patcon this is the collector github issue I was talking about!

[patcon]

Do you think stalled label can be applied to blocked issues? Should there be a distinction?

[dcwalk]

Hmmmm, I think they are distinct, and don't have strong feelings either way about adding another label if that feels more descriptive!

That said the outcome (no ability to move forward) is the same, which I think is the status I'm more concerned in capturing! I'd understand that with two or one labels tho.

[dcwalk]

This has been done! The conversation around stalled v blocked can be moved to a new issue (reticketing!)