3 ms·
"Pay extra"? Like you were paying for it in the first place. At the end of the day, somebody gotta pay the ramen. Besides, a certain project you might be famili
by toyg 11y ago
"Pay extra"? Like you were paying for it in the first place. At the end of the day, somebody gotta pay the ramen. Besides, a certain project you might be familiar with is basically monetizing automated security patching, so throwing stones is really not a great sport.
(also, projects like requests are not desperate for users. One user paying to contribute to the well-being of the codebase is worth hundreds of users who won't even bother sending in a patch. Again, a certain project you might be familiar with is awfully aware of this state of things.)
- enraged_camel 11y agoThe problem with the "pay them to fix the bugs" model is that it turns bugs into a source of revenue and creates the wrong incentive for the developer. I'm much more inclined to agree to a "pay for additional features" model instead. Because then, by definition, you are paying for extra stuff, vs. fixing what should have been working correctly in the first place.
- nickpsecurity 11y agoThat's clever but wrong here: labor is what's being monetized. The people that they're asking probably require payment for their own labor and pay others w.r.t. other goods. Then, they OSS developers owe them free products and support of highest quality. Quite a double standard. Requiring pay for fixes only incentivizes pay for labor, which is rare for OSS.