I am proposing to form an automation working group that handles automation outside build (i.e. tools, bots and scripts that make our lives easier)
Related projects:
I am not exactly sure if we should have a charted working group to work on these tools (because that probably means more meetings!), but I think it is a good idea to have a team of people working on them. These projects are somewhat related (e.g. core-validate-commit and branch-diff usually consumes output of node-review) so we should have a place to discuss how to divide the work to address our needs.
Also if IIRC at the collaboration summit we have talked about needing more automation to ease our maintainers' burnout (hopefully doing dev on automation won't make it worse...but meetings definitely make it worse which is why a charted WG may not be a good idea)
I am proposing to form an automation working group that handles automation outside build (i.e. tools, bots and scripts that make our lives easier)
Related projects:
I am not exactly sure if we should have a charted working group to work on these tools (because that probably means more meetings!), but I think it is a good idea to have a team of people working on them. These projects are somewhat related (e.g. core-validate-commit and branch-diff usually consumes output of node-review) so we should have a place to discuss how to divide the work to address our needs.
Also if IIRC at the collaboration summit we have talked about needing more automation to ease our maintainers' burnout (hopefully doing dev on automation won't make it worse...but meetings definitely make it worse which is why a charted WG may not be a good idea)