Click the fork button. People that release free software have no obligation to their users; they wrote some code, made it available, and that is that. That's all free software is about: instead of being at the mercy of some Supreme Entity that makes your software, you have the power to do anything that Supreme Entity does. Fix the bug. Pay someone to fix the bug. Write your own database, and include the parts of MySQL that you like.
People who dedicate their time and money to hosting free software are not the ones to blame for your problems. Yup, they made a fucking dumb coding error that's costing you millions of dollars a second. But that's your problem, not theirs. All they did was share their creative work for your enjoyment; if you don't enjoy it, it's your problem.
As free software becomes more popular, people are forgetting what it means. It means that everyone has the same opportunity as the original author to fix stuff and freely share their fixes. It doesn't mean that the author has to do whatever you tell them to.
It doesn't mean that the author has to do whatever you tell them to.
Right. Likewise, you're not obligated to help people pick things up or hold doors open for people. But you do it because it's a reasonable response. The maintainer had the right to respond how he did, that doesn't mean he should have, if he was interested in building rapport with the community, or improving the product. (This is sort of how companies have the right to provide poor customer service, but may prefer to yield that right even at added costs.) This is about bug reporting etiquette and the fact that being uptight about code sample procedures may be in bounds, but also counterproductive.
The blog post is not about someone unhappy that some feature was not implemented or some bug wasn't fixed. It's about how feedback is being treated. That doesn't change when you fork a project. In fact, the whole point of such a blog post is to explain how this would unnecessarily, and at a loss to all those involved, lead to forking. You're trotting out an old hobby horse without properly considering the problem. That just leads to the boring 'forking can't solve everything and also causes problems' debate.
People who dedicate their time and money to hosting free software are not the ones to blame for your problems. Yup, they made a fucking dumb coding error that's costing you millions of dollars a second. But that's your problem, not theirs. All they did was share their creative work for your enjoyment; if you don't enjoy it, it's your problem.
As free software becomes more popular, people are forgetting what it means. It means that everyone has the same opportunity as the original author to fix stuff and freely share their fixes. It doesn't mean that the author has to do whatever you tell them to.