@jorge yeah, locking is basically what happens as soon as the folks from the green site, the orange site, or the redditors descend en masse on the issue tracker… but I’d rather have something that proactively prevents brigading, rather than passively respond to it
Yeah, it’s hard to lock an issue before the brigaders insert 50 comments trolling for bile … then watch helplessly as the shrapnel hits other issues on other projects.
@ebassi Yeah unfortunately it doesn't fix the desktop's culture problem.
This happens all over open source but client is the one that suffers the most because it's just normalized to these absurdly extreme levels.
Sorry I don't have any solutions to share! I tend to avoid it by consuming Linux in a way that 1990s linux guy hates so much that they ignore it. I hope it lasts, haha.
@ebassi that is one of the main reasons the short while I did software engineering/dev work a couple years ago, I avoided dealing with community/oss projects as much as I could, the entitlement and amount of toxicity is absurd.
@ebassi You're not helping the image of Gnome devs not caring about what the users want, here. I have spent a ton of time contributing bug reports and feature requests to software projects that I love, because I love them and want to help make them better. I understand that too many people write issues with too little info, or too many demands or bad ones in different ways that are exhausting to handle. But getting inputs from real users with different perspectives make things better @JCWasmx86
@forteller@JCWasmx86 No, no: I care about what users want. I care a bit less about what people write.
In any case, if you think I don't help the image of GNOME you're free to block me, so you don't have to read what I write, and ignore the fact that free and open source maintainers are actually people doing stuff out of the goodness of their heart, and opening issues does not entitle you to their time.
@that_leaflet@forteller@JCWasmx86 but, more importantly, it should not require intervention of the project maintainers. Of course, we can’t ask volunteers to act as a firewall between users and developers, either…
@ebassi@forteller@JCWasmx86 Oh I guess that makes sense. Just letting the original reporter and contributors making comments would cut down on that stuff, and maybe an upvote mechanism so that there's some gauge on how many people are affected.
@JCWasmx86 Don't know you, but my software is perfect.
Okay, outside of the joke: direct public access is the problem. Having reports is fine, but having randos leaving comments, or direct interaction between developers and users is a recipe for disaster as soon as your project gathers a sizeable user base that has no idea about how anything works, but still wishes to leave a comment because it looks like it does something.
@JCWasmx86 Not just GTK: I think GNOME as a whole is too big have a decent public issue tracker, without a team of people in charge of everything that happens on it.
Quick reminder: your own personal FLOSS project with 15 users is not the same as a 25+ years old project with millions of users. Do not try to extrapolate behaviours at scale, it won't end well
Add comment