Stories of Open Source Failures?

ahodgkinson asks: "We often hear about companies, government agencies, schools and other organizations that migrate from Microsoft to open source based systems. We sometimes hear about organizations that evaluate Open Source and then elect to remain with their existing proprietary system. Both of these events represent represent a 'non-failure' for the open source movement. I'm interested in knowing more about the Open Source 'failure' events, namely when organizations move away from open source to a proprietary solution. Does anyone know of organizations that have moved from an Open Source based IT solution (back) to a proprietary system? Or where such a move was contemplated but not made? I'm specifically interested in larger organizations that have 'undone' a strategic move to Open Source, and their reasons why. Given your examples, is there anything we can learn from them?"

Comments

obligitory....

[Anonymous Coward]

those receiving (and believing) threats from SCO for using Linux....

Here's mine

[PD]

This one time I started writing a program. I built my makefile, put COPYING into the directory, and even made a test program that printed out hello world. Then I got tired of it. I lost the source code a couple years ago. I think it was on a disk that I mistakenly threw away.

It was an open source failure.

Re:When is a failure not really a failure?

[duffbeer703]

I have no idea what you just said, but it sounds absolutely brilliant.