3 ms·
He misses another way to get bugs fixed in open source software: Pay a developer to fix them. However that does raise the problem that it's hard to find a comp
by rwmj 11y ago
He misses another way to get bugs fixed in open source software: Pay a developer to fix them. However that does raise the problem that it's hard to find a competent developer to do piecework (easy to find an incompetent developer of course). All the good open source developers are employed.
- mgbmtl 11y agoAll of my published work clearly states that commercial support is available (and when other companies actively contribute, I list them too). Then again, most of my projects are work-related, not hobbies, so I don't mind developing a funding plan to keep the projects sustainable. In some cases, however, it can also attract poor quality patches from contractors working on gigs, and make life hell for the maintainers. I personally prefer if people contract me directly (as the project/component maintainer). Tangential anecdote: a while back I helped maintain a caching module for a CMS. I was once asked by a user to look into the performance problems of their website. They were a big media company from the Middle East. I had no idea they used my module, which was usually for small websites on cheap hosting. Their contractors had enabled every possible caching module in the world. I basically disabled a few modules, including mine, tweaked their Varnish config, and things ran smoothly afterwards.
- x0x0 11y agoI've responded to user requests with "I'm really busy; if you want this to be a priority my rate is $120". Those conversations almost always end with bitching (theirs) and me emailing something like "You mistook yourself for a paying customer. You aren't and I still don't work for you. Bye!" then adding their email to my delete on receipt rule.