3 ms·

In the majority of cases, they are getting paid to code it (by some company, organization, etc). And they benefit from the popularity of the the software. So I

by newen 8y ago

In the majority of cases, they are getting paid to code it (by some company, organization, etc). And they benefit from the popularity of the the software. So I don't think I need to see myself as a charity case or adopt a please please please attitude with them.

domoritz 8y ago
Where do you get "in the majority of cases" from? https://twitter.com/NumFOCUS/status/1017418416725155840 https://twitter.com/NumFOCUS/status/1017418416725155840.
about_help 8y ago
Agreed. No need to be a dick, but bug reports are often pretty cut and dry and often some frustration does leak into the tone. Any big project, whether code or some local government thing, will have some level of assholes.
habosa 8y ago
I maintain a number of open source projects for Google. So yes I am paid to do it and yes the company benefits from it. That said, it doesn't mean that developers who use it can take an entitled stance and expect to get anywhere. I get so many bug reports like "This sux and you have to fix it!!!!" and even when I wake up on the right side of the bed, there's nothing I can do with those. A calm discussion of what the developer is trying to achieve, what they expect to happen, what actually happens, and how I can reproduce will get a quick response from me 100% of the time.
- hangonhn 8y ago
  Also, the paid vs. unpaid is a BS argument. Even if you were paid, it's not the complaining user who's paying you so how can they feel entitled to your time? Some people... That said, when someone open sources something there isn an implicit "contract" between the developers and users. The users' feedback helps the developers and in return they get something valuable. It's more of a group effort rather than some one directional flow of power. I've seen projects where these relationships weren't properly managed or where one group didn't appreciate the other and the end result is always the same: dead projects.
- ychen306 8y ago
  In your case, it only means you owe Google, but not the other user.
pertymcpert 8y ago
You are a charity case.

by newen 8y ago

domoritz 8y ago

Where do you get "in the majority of cases" from? https://twitter.com/NumFOCUS/status/1017418416725155840 https://twitter.com/NumFOCUS/status/1017418416725155840.

about_help 8y ago

Agreed. No need to be a dick, but bug reports are often pretty cut and dry and often some frustration does leak into the tone. Any big project, whether code or some local government thing, will have some level of assholes.

habosa 8y ago

I maintain a number of open source projects for Google. So yes I am paid to do it and yes the company benefits from it. That said, it doesn't mean that developers who use it can take an entitled stance and expect to get anywhere. I get so many bug reports like "This sux and you have to fix it!!!!" and even when I wake up on the right side of the bed, there's nothing I can do with those. A calm discussion of what the developer is trying to achieve, what they expect to happen, what actually happens, and how I can reproduce will get a quick response from me 100% of the time.

hangonhn 8y ago
Also, the paid vs. unpaid is a BS argument. Even if you were paid, it's not the complaining user who's paying you so how can they feel entitled to your time? Some people... That said, when someone open sources something there isn an implicit "contract" between the developers and users. The users' feedback helps the developers and in return they get something valuable. It's more of a group effort rather than some one directional flow of power. I've seen projects where these relationships weren't properly managed or where one group didn't appreciate the other and the end result is always the same: dead projects.
ychen306 8y ago
In your case, it only means you owe Google, but not the other user.

pertymcpert 8y ago

You are a charity case.