4 ms·

Agreed - all of this is necessary to keep sane. I maintain UI Bootstrap (over 12k stars on GitHub), and I have to make decisions on bugs and feature requests.

by Bahamut 10y ago

Agreed - all of this is necessary to keep sane. I maintain UI Bootstrap (over 12k stars on GitHub), and I have to make decisions on bugs and feature requests. I prefer erring on inaction of response if I am not sure of how to decide, and I make it a policy to close support issues on the repository. Ultimately, if someone really cared about a particular issue, the person would make an attempt at a pull request to help contribute. I will even often help give most of the important abstract information needed for a contribution too to assist in the general implementation, but I can only do so much work for people. I am also inclined to help bad attitude people the least - it is the quickest way for me to take longer to reapond & implement, so be nice to your friendly open source maintainers people!

rkangel 10y ago
> if someone really cared about a particular issue, the person would make an attempt at a pull request to help contribute That's not always true. They may not have the necessary skills. That's no excuse for laziness in reporting problems though.
- Bahamut 10y ago
  Having the necessary skills does not mean they cannot make an attempt though. If they regress into whining instead of trying, then I'm less sympathetic & less likely to put my best effort forward since it's unnecessary stress.
- Pxtl 10y ago
  Ultimately, that's still laziness. Learn the necessary skill.
  - stinkytaco 10y ago
    Really? I might be able to report a bug in any number of roles (perhaps designer, perhaps administrator, perhaps user) and I may not have the knowledge or experience necessary to fix the problem, but certainly enough to report in a detailed way. If knowing software development is not my job, I can't be a user? What if I am a developer but not familiar with the code? Dismissing users because they do not have the skills to fix every problem is absurd.
    - Pxtl 10y ago
      I'm not dismissing the users, I'm just saying that nobody owes you a bug-fix. If they prioritize your bug, that's great, but if they don't - either submit a pull request or live with it. The knowledge developers put towards their free hobby-projects is hard-earned and shouldn't be treated like public property.
- singlow 10y ago
  In the case of a js/css framework, the users are js/css developers.
- optimiz3 10y ago
  If they cared enough, and can't offer skills (time), they could always offer money.
technion 10y ago
feature requests An understated problem here is that opening an issue to create a "feature request" is seen by Github as a "contribution", one on par with actually fixing bugs. We've got people going around opening hundreds of issues for silly things like variable names in products they don't even use, presumably with the aid of some bot. Nearly everything written in C or C++ has had a issue requesting the build system use autoconf, an issue requesting the use of CMake and a issue declaring scons is the best. Even if you liked all these tools, it would be absurd to satisfy all three requesters. None of these people are "contributing" in the way someone fixing a bug is.

by Bahamut 10y ago

rkangel 10y ago

> if someone really cared about a particular issue, the person would make an attempt at a pull request to help contribute That's not always true. They may not have the necessary skills. That's no excuse for laziness in reporting problems though.

Bahamut 10y ago
Having the necessary skills does not mean they cannot make an attempt though. If they regress into whining instead of trying, then I'm less sympathetic & less likely to put my best effort forward since it's unnecessary stress.
Pxtl 10y ago
Ultimately, that's still laziness. Learn the necessary skill.
- stinkytaco 10y ago
  Really? I might be able to report a bug in any number of roles (perhaps designer, perhaps administrator, perhaps user) and I may not have the knowledge or experience necessary to fix the problem, but certainly enough to report in a detailed way. If knowing software development is not my job, I can't be a user? What if I am a developer but not familiar with the code? Dismissing users because they do not have the skills to fix every problem is absurd.
  - Pxtl 10y ago
    I'm not dismissing the users, I'm just saying that nobody owes you a bug-fix. If they prioritize your bug, that's great, but if they don't - either submit a pull request or live with it. The knowledge developers put towards their free hobby-projects is hard-earned and shouldn't be treated like public property.
singlow 10y ago
In the case of a js/css framework, the users are js/css developers.
optimiz3 10y ago
If they cared enough, and can't offer skills (time), they could always offer money.

technion 10y ago

feature requests An understated problem here is that opening an issue to create a "feature request" is seen by Github as a "contribution", one on par with actually fixing bugs. We've got people going around opening hundreds of issues for silly things like variable names in products they don't even use, presumably with the aid of some bot. Nearly everything written in C or C++ has had a issue requesting the build system use autoconf, an issue requesting the use of CMake and a issue declaring scons is the best. Even if you liked all these tools, it would be absurd to satisfy all three requesters. None of these people are "contributing" in the way someone fixing a bug is.