I think that text is from melroy, so according to him. From seeing his interactions in the kbin issue tracker I get somewhat of an egotistical impression of him, because he would often take an issue that has just been opened and not triaged or discussed what the best fix is, and he would open a PR with how he thinks it should be fixed, and it sounds like his frustration is that his hasty PRs weren’t getting merged quickly because people wanted to come to a consensus.

Maybe I’m just reading into it but it felt like he just wanted his name on something and it wasn’t happening with kbin.

Edit: I want to add that I don’t mean to shit on him as a dev or as a person - it’s possible that I’ve only seen a one-sided view of his interactions as a busy contributor who just wants to whittle down the issue list as fast as possible and that he’s got good intentions, and regardless he seems like a very capable dev. It’s just that based on my perusing of issues and discussions I’ve come across, it doesn’t seem fun to work with him to contribute, and if I were to treat the contributors list as a scoreboard and had the goal of having my name on as many commits as possible, I think it would be hard to tell us apart. I was just going to keep my thoughts about this to myself but I’ve seen some other people comment similar things in other threads about mbin so maybe it’s worth sharing my skepticism about mbin. Take from it what you will.

Not sure what you mean by management, or which aspect of management? The issue was more about acceptance of community enhancements through the open source code project. Some contributors felt they could move faster with more diverse enhancements. It may be something like the LibreOffice fork from OpenOffice, where some wanted to just move faster with changes.