"F/OSS expecting everyone to contribute back is the problem. Not everyone can or has the means."
Of course everyone has the means. It's not just code and massive test server y'know.
"The cost of a product that has already implemented the required feature and is not trying to harang me for money for something that should be in their product if they want me to use it. Which they do want me/ as many as possible to use or it would fail. "
Err...it does harang you. It's called "the price". If a piece of pay-for software does what you need, go buy it.
"it pays money and licenses for what it needs now. Not for future needs."
My comment was poorly written, I apologise. What I meant was the cash currently being spent on license fees and support contracts; some of that could be used to fund the development of their chose F/OSS tool. I fully expect them to still have a support contract, hopefully with an organisation feeding back into F/OSS (probably to make support easier...)
"but if a business needs a process now and it exists, why pay for someone to implement it maybe in the future. Somewhen."
I did not say they should. If another tool does what they need, go use that tool. What they should not do it select a tool that doesn't do what they want, moan about it and not lift one finger to fix the problem they have caused themselves.
Further more, many places do not have vanilla installs of (say) MS Office because they do not provide all the features. They go out and buy add-ons, or pay someone to write those add-ons. How is that any different to buying add-ons for F/OSS software, or paying someone to add to the F/OSS code base?
"If they want to beat the propriety software they need to put the features in."
Who said they wanted to "beat the proprietary software"? The most they want to do is scratch their own itch and fix their own problems. There will be some vendor somewhere who does want to beat proprietary software, I'll grant you that. But that isn't the project's problem and said vendor would almost certainly be involved in the project at some level, seeing to it that what they need gets done.
"Also note not everyone can contribute"
Everyone can contribute. Don't place limits. Even a decent bug report (or the steps to hit a problem) helps.