Suppose, hypothetically, that there's a very important piece of work that you know needs to be
done on a project. It needs buttons.
But, the project's leaders and main contributors are sure their new plan makes that work
unnecessary. They have a six month plan to build a framework for general fastening, including
a heuristic zip-and-velcro system that should render buttons obsolete. So they tell you not to
even bother writing a patch, because hey in six months they'll just have to rip it out again.
Several years later the six month plan has been "delayed" because it turns out that solving
the general problem of fastening isn't as trivial as it seemed when they were drunk at a
conference. But there's now a timeline, a schedule, two new source code repositories and a
paid bounty system. But there still aren't any buttons, and buttons were all the users
actually asked for in the first place.
Now, what exactly do you win by standing up and saying "I told you so" when that's already
what everyone except a few deluded developers is thinking? Do you fork, causing a year long
flamewar in which many people will decide that it's better to abandon the entire project than
to put up with so much childish spite ?
Sometimes projects, whether Free Software projects, or just the project of redecorating the
bathroom, get mired down somehow and should rightly be abandoned. You can always move home