I think Anon136 has a point, it isn't really a tax, it is a price for a product (sort of), or a continuing service (attention from the developer team) if you prefer to look at it that way. If you don't like the product, you can always use another one. It isn't as if there is a lack of choice of cryptocoins (1000+ and cointing) or even cryptocoins based on CN technology (10 or so and counting, including one that has been abandoned and you can adopt yourself for nothing if you want it).
That logic doesn't work. You don't "develop" a product (i.e. the code), because if that was correct then I could just merge your changes into CryptoNoteX and derive the same benefit. That is clearly not the case as the distribution of coins is at least as important as the code (otherwise anyone could clone Bitcoin1-2-3-10 and they would be fungible with the original). You develop money, and an economy. Not a product, and not a service.
In this sense you are the central bankers (with limited powers).
Remember, the market for miners is completely open. If you guys don't like the way the miners vote, you can start mining yourselves, and vote differently, or you can shift your hash rate to different pools with different voting policies. We likely wouldn't accept a negative miner vote immediately and just give up, so if the community really wanted to influence the vote in a different direction, it could.
If ultimately the community votes (or votes by default) for no funding then the will of the community is pretty clear, and will proceed from there, continuing as a (slow and underfunded) volunteer project, or considering other monetization strategies that don't necessarily require direct community buy in, or as you say, dropping the project. Though everything ultimately requires community buy in because the community can walk away too, or fork the code and do it their way instead.
This is not what I meant. My point is that the vote is not credible.
Suppose miners voted against, then they would damage your reputation and Monero. Thus, even if they might not agree to the screw-turn, the alternative is worse (i.e. why don't people rebel against inflation all the time? why do people just
swallow injustices? because the alternative is often worse -- boiling frogs, slippery slopes, tragedies of the common and all that).
From this argument, a positive miners' vote would not indicate miners' approval, and the validity of the vote is under question.
Alternatively, suppose miners voted for and the motion passed smoothly (no pun intended). Then, even if this was indeed optimal, there would be suspicion of collusion between devs and miners, not unlike that between the corporations and the governments of the world. Monero's reputation, as well as the devs', would be damaged again.
From this argument, a negative miners' vote would not indicate miners' disapproval, and the validity of the vote is under question.
This is what I mean by misaligned incentives. No matter the outcome, it will not convince those who "lose" that their rationalization is incorrect and that Monero has not been corrupted by (a) greedy devs (b) greedy devs and miners colluding. From a reputation/credibility point of view, it's a lose-lose scenario unless transparency can counter both options (a) and (b) above.
We don't want grant proposals, we want transparency and accountability. We don't want to continue the "voluntarist" approach, in which you place a hat and start playing the instruments. We want to participate in a crowdfunding platform, which has been promised to us. We want to be able to back tasks and to observe how and what others back. But to do this, we simply need a list of SOME tasks in just marginally finer grain and more detail than what fluffypony already posted.
1. task id/name/description
2. estimated cost interval (XMR)
3. estimated time interval (weeks?)
4. estimated urgency
5. estimated impact
It probably takes you less than half an hour to compile this. But the non-developers among us need to understand more to throw our cash. Like aminorex said, again, "telling me to <
> does not inspire confidence" (paraphrasing).
We just want your best first guess. Again, just marginally finer grain and more detail than what fluffypony already posted. And if it doesn't work and no other solution seems workable, then it's time for the manual override.