Stepping back from being the person in charge of infrastructure
I got @ mentioned on some bot stuff the other day on Discord and I realized I am no longer in a good position to be considered the person to loop in on that sort of stuff. My code contribution rate in CPython isn't high enough right now for me to drive what our workflow should be, but I'm not a new contributor either so I have obvious bias/blind spots over what's needed.
As such, I wanted to publicly say I shouldn't be leaned on for driving what the bots should do, improvements to make to our workflow, etc. My suggestion would be to look at what our current bots do, see if any of it is outdated compared to what GitHub offers us, and then try to lean on GitHub Actions more instead of hosting on Heroku for easier maintenance and transparency for when things fail (as the vast majority of issues that get brought up around the bots is that GitHub didn't send a message to Heroku, not due to a bug).
P.S. I almost looked up how long I have been driving workflow stuff but I realized it's past a decade from getting off of svn alone and I'm too lazy to looks up when bugs.python.org came about. 😄
participants (1)
-
Brett Cannon