Corporations and OSS Do Not Mix (coglib.com)
An anonymous reader writes: Ian Cordasco, a prolific open source developer, wrote a lengthy post about his experiences working on code that gets used by companies as part of their business. His basic thesis is that the open source development process is not particularly compatible with for-profit corporations, and having them involved frequently makes progress more difficult. "As soon as a bug affects them, they want it fixed immediately. If you don't fix it in 24 hours (because maybe you have a real life or a family or you're sick or any number of other very valid reasons) then the threats start." He adds, "When companies do 'contribute,' it's often not in the best interest of the community, it isn't enough, or it's thoroughly misguided." Cordasco is quick to note that there are exceptions, but he has an idea why the majority behave that way: "I don't have the complete answer, but one important point is that there is toxicity in the community, its leaders, and or its contributors, and the companies have learned their behavior from this toxicity." He provides a list of suggestions both for companies using open source software, and also some further reading on the subject from Ashe Dryden, David MacIver, and Cory Benfield.
Sounds like some bullshit. As someone who works in IT for a major corporation and has to deal with bugs that affect us in COTS software (such as MS Windows and MS Office), threatening people after 24 hours would be ridiculous. If the issue is currently unknown, expect a minimum of 2 weeks with a norm of more like 2 months for a fix - if the vendor will even agree to fix it. Why would a corporation threaten some OSS developer? It just doesn't scan and seems like BS.
"Well if you're not going to take this seriously, we'll have to start using another project."
I've never exactly gotten this. Why does anyone who is giving something away particularly care if someone who is getting it for free uses it or not?
This guy clearly doesn't understand that Open Source means "Free to Use" not "Free Beer", and that most corporations (the executives, not the software engineers or managers) are plenty happy to pay for support from the subject matter experts in it, so long as it saves them overall money. In fact, many corporation's resistance to OSS is due to the lack of such support - because their customers aren't so understanding..
This is the very business model that Red Hat uses. All this guy needs to do is put up a "priority payment" system for bug fixes, and post it publicly. Done and done.
Well done for condescendly making the parent's point while claiming he's wrong.
RedHat sell expertise (i.e. support). If you just want the software, you can get it for free from CentOS.
SJW n. One who posts facts.
Because business NEEDS to have the illusion that they "have a neck to choke" when something goes wrong, so they need to have a "contract" with a "company". I've heard this from the C-suite for years. (That is what Red Hat is selling, and why they're successful!)
It's nuts, really: Anyone who reads common software company contracts/EULAs knows that they have NO recourse if something goes wrong, but if they think they can somehow hang blame on a vendor if they have a problem, then that makes them feel safe.
In truth, the OSS model means that if something goes wrong and the vendor tells you to f**k off or goes bankrupt, you can find someone else to help you. If a closed-source vendor can't/won't help or goes under, you're screwed much harder.
Sometimes the "writing on the wall" is blood spatter...