An example of this was my department wanted a certain feature in the Moose library, so we offered to pay one of the developers to write it. Then it turned out we didn't actually have funding for this ("pay someone to work on free software? fuck that") and so it never happened. But for a company with it's act together, this is a great way to make your internal codebase cleaner, and you get to say, "thanks to us, everyone gets this".
If this is his business model, it's a good one.
He likely would let them pay for:
* advice on how to work around the lack of their proposed language feature (as a subset of "advice on how to solve problems in or with the language").
* some influence over prioritisation of the roadmap. If there are two language features Rich was planning to add anyway, pushing one that a paying customer desperately needs up the priority list wouldn't interfere much with the creative direction of the language.
they'll have influence over you, wouldn't they?
Only for the items relevant to the contract terms.All I was originally saying was that I just feel he'll end up in the same situation. I'm not suggesting he can't say no. :)
If you're pointing out that people are acting irrationally, then, yes, they are. The difference is that we tend to treat "business transactions" different from other kinds - I think monetary donations are not seen as business transaction, so the expectations are different. See this excerpt from Dan Ariely's Predictably Irrational: http://www.npr.org/templates/story/story.php?storyId=8923395...
2) I have run into people that will say that. It is usually a bluff.
3) In the rare cases it is not a bluff, you can either drop the business (figuring you don't want to deal with person X) or, if you think they are out-of-line take it to their superiors.
All that being said, if you aren't willing to call the bluff for whatever reason, then they do exert an influence over you. That's really your fault though. If you have backed yourself into a corner where a single contract will make-or-break you and you aren't on really good terms with the people involved you are screwed no matter what.
When you get a support contract from Red Hat (for example), you aren't donating money to the development of Linux like a sponsorship; you're indirectly supporting Linux development, but really what you're interested in is either (a) specific solutions to specific problems, or (b) getting access to people should a problem arise in the future during the term of the contract.