#maintainerburnout — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #maintainerburnout, aggregated by home.social.
-
Trying a new way of dealing with GitHub notifications and TinyGo maintenance in general. I've been using Octobox for a while and it's nice, but it's a technological solution and cannot in itself fix the stream of notifications for a project like TinyGo.
Instead, my new approach is:
* Limit what repositories I'm actively going to, to what is realistic. For now, that's tinygo and drivers mostly, and mostly maintenance work.
* Work in two passes. The first pass is going through the notifications, replying where needed, maybe writing a bugfix if it's fast, but ideally not spending more than 15 minutes or so on a single issue/PR. If it's not something I can fix quickly, I'll star and archive it to put on the backlog. I can work on the backlog later. If I keep doing that frequently, I can keep the inbox (close to) zero.
* Decide for myself what I'm going to work on, instead of reacting to issue reports. Working reactively burns me out and leads to tons of unfinished PRs, which doesn't help anybody. Instead, I can pick what I am going to work on, such as: updating dependencies, documentation, refactoring, new features, etc. (Roughly in that order).I'm only starting, but I'm now down from 900+ notifications to just 8. So I should be finished very soon. Then I hope to keep this "inbox zero" approach working. I suspect that's going to be the hard part - sticking with this approach.