I fear that ignoring tickets just makes them stack. Similarly, closing and locking tickets arbitrarily may affect your reputation. This may or may not be a problem depending on how you feel about your reputation. Still, it is worth remembering that some maintainers do care, and that they don’t want to look bad (even though most would understand).
I personally don’t think that setting a bar high to deter less motivated people from contributing is a sane approach. I suffer from poor quality bug reports every single day, at work, and yet, they often are an indicator of something that IS broken in my software. I need them.
The key difference is that I am paid for it, and that my contributors are also paid employees, that I have to work with every day, and that will learn over time.
Being on the receiving end of an endless streams of negative comments, for no other reason that being willing to share some of your work, as-is, is not an appropriate retribution. And even if that was a paid job, I’m not sure one would want to keep it.
I don’t think the issue is whether contributors are tech pros or not, and whether one should do gatekeeping. I think that the point is that it is worth remembering, when you contribute an issue to a project, that the maintainer is a human being, probably giving some of its own free time, out of passion and compassion, to fix your issue, and that negative comments are plainly abusive and should probably be worded in a gentler way.
i’ve been on Linux for over 2 years and have wanted to file a big report many times, but the process is intimidating - looked like learning an entire project or new software. FOSS is not easy usually.
The best luck i’ve ever had was offering to test a new markdown software out and emailing the dev with screen shots - using Flameshot to circle the things i wanted him to see.He made many improvements based on my feedback. If he’d made me fill out a lengthy bug report - especially one unique to his software/project, I wouldn’t have done it.
You will always suffer, as a developer, from low-quality comments, pull requests and argumentation. There is no tool to change that since you cannot influence, change or put force on people doing XZZ. Over 70 Percent of FOSS work is talking talking talking and it is annoying and boring, but this is the way how it is.
You are incorrect saying this is not a user thing, it absolutely is. The only way is to enforce something on them, platform wise or manually, but that is all you can do. The more experience a user has with FOSS or contribution in general, the more advance he will become, and therefore the overall quality of his interaction will usually go up. As always, there are exceptions.
I fear that ignoring tickets just makes them stack. Similarly, closing and locking tickets arbitrarily may affect your reputation. This may or may not be a problem depending on how you feel about your reputation. Still, it is worth remembering that some maintainers do care, and that they don’t want to look bad (even though most would understand).
I personally don’t think that setting a bar high to deter less motivated people from contributing is a sane approach. I suffer from poor quality bug reports every single day, at work, and yet, they often are an indicator of something that IS broken in my software. I need them.
The key difference is that I am paid for it, and that my contributors are also paid employees, that I have to work with every day, and that will learn over time. Being on the receiving end of an endless streams of negative comments, for no other reason that being willing to share some of your work, as-is, is not an appropriate retribution. And even if that was a paid job, I’m not sure one would want to keep it.
I don’t think the issue is whether contributors are tech pros or not, and whether one should do gatekeeping. I think that the point is that it is worth remembering, when you contribute an issue to a project, that the maintainer is a human being, probably giving some of its own free time, out of passion and compassion, to fix your issue, and that negative comments are plainly abusive and should probably be worded in a gentler way.
i’ve been on Linux for over 2 years and have wanted to file a big report many times, but the process is intimidating - looked like learning an entire project or new software. FOSS is not easy usually. The best luck i’ve ever had was offering to test a new markdown software out and emailing the dev with screen shots - using Flameshot to circle the things i wanted him to see.He made many improvements based on my feedback. If he’d made me fill out a lengthy bug report - especially one unique to his software/project, I wouldn’t have done it.
You will always suffer, as a developer, from low-quality comments, pull requests and argumentation. There is no tool to change that since you cannot influence, change or put force on people doing XZZ. Over 70 Percent of FOSS work is talking talking talking and it is annoying and boring, but this is the way how it is.
You are incorrect saying this is not a user thing, it absolutely is. The only way is to enforce something on them, platform wise or manually, but that is all you can do. The more experience a user has with FOSS or contribution in general, the more advance he will become, and therefore the overall quality of his interaction will usually go up. As always, there are exceptions.
deleted by creator