On Tue, Jul 08, 2025 at 12:35:19AM +0300, Jani Partanen wrote: > Maybe you should find some front(man/woman/person) who deals pull requests > and other communication. You clearly cannot do both, code and communicate. > And there is nothing wrong about that. Not everyone is good with > communication. I will base my claim to what I have seen here. Drama after > drama and very stupid reasons.
There's been a lot of misunderstanding about what the job of deciding what patches go out when and sending pull requests entails. Some of it is communication, but not the majority. A partial list of responsibilities includes: - Following and triaging bug reports - Keeping in active communication with users who are QAing - Watching test dashboards (and this is a big one, we collect a ton of test data) - Understanding the coverage of those tests (and realistically, this means we'll need automated code coverage analysis before someone new can take it over) It also requires a fairly intimate knowledge of the codebase and the engineering techniques we use for assuring correctness, as well as deep filesystem experience to understand the different "gotchas" that can happen. It's a serious job with serious responsibilites, and not something to be handed over lightly. Were you volunteering to take all that on? I do spend time teaching those who are willing :)
