I think this was the right decision. Reading through his explanation, it's clear that he was becoming frustrated by having to justify saying no as maintainer, but that's the most important part of it. Not just saying no - explaining why it's such a bad idea that it can't be accepted, and helping provide a way forward that works for everyone. Providing no explanation just spreads the frustration around to everyone else.
Having not worked with the VDG, I don't think anyone here can really properly evaluate if his criticisms are accurate or not. Certainly some of what he says sounds unfortunate, but it's difficult for an outsider to judge if he's overstating his case or not. I do think there is a valid argument to focus on making the majority of your userbase happy while ignoring the 1% who moan the loudest, but I also think that a focus on bug-fixing and polishing over core new features is absolutely needed as well.
Hopefully kwin as a project keeps humming along without too much disruption due to this.
Having not worked with the VDG, I don't think anyone here can really properly evaluate if his criticisms are accurate or not. Certainly some of what he says sounds unfortunate, but it's difficult for an outsider to judge if he's overstating his case or not. I do think there is a valid argument to focus on making the majority of your userbase happy while ignoring the 1% who moan the loudest, but I also think that a focus on bug-fixing and polishing over core new features is absolutely needed as well.
Hopefully kwin as a project keeps humming along without too much disruption due to this.
Comment