Convincing Your Employer To Go With FOSS?
mark72005 writes "My employer is currently looking at adopting a content management system for use by our technical support staff (primarily first-line end user support, but hopefully it will include deeper levels of support personnel eventually). The candidates are currently Plone (OSS) and Confluence (proprietary, closed-source). For those with experience in each, what arguments in favor of Plone could be made to managers more interested in pragmatism than idealism?"
You've obviously decided which piece of software you want to recommend even though the only reason you can think of to recommend it is that it is FOSS? If the open software isn't as good it just isn't as good; just because it's FOSS doesn't mean that it is the be all and end all to solve your problems. Compare features, stability, cost, and support; if your boss is actively against FOSS make a point to explain it's advantages (and disadvantages if you want to be fair) and leave the decision to him. After all, it's entirely possible that the closed, proprietary solution fits your situation better; basically, its dishonest to make your decision and then go digging specifically for evidence to support that decision.
I haven't used either system but the podcast FLOSS weekly recently did a whole episode about PLONE that may help you decide if it is right you.
"UNIX is very simple, it just needs a genius to understand its simplicity." -Dennis Ritchie
Atlassian makes the source for all of their products available to anybody who buys a license. It doesn't cost anything extra, and even the $10 starter licenses come with full source.
Tell them Open Office comes from Oracle.
Depending on corporate culture(and the exact policies RE: demos of the proprietary vendor) cost can actually be a huge factor; but not for the obvious "cheap=better" reason.
In some institutional cultures there is a surprising power(assuming you don't step on the wrong toes) in Just Fucking Doing It. Obviously, unless you have really impressive guts and not too much sense, this doesn't mean putting a production server on an internet facing IP and hacking the company's DNS records to point to it; but showing up with a solid, functioning demo that everyone can gather around the projector and poke around at on their laptops can really sell something.
If a proprietary product isn't either available as a free demo version, and not through some subscription program you have to sign up for, or so expensive that the company will send a guy in a nice suit to do the demo, hand out some swag, and give everyone a really nice handshake, doing that with a proprietary product is hard and/or illegal.
Doing it with a FOSS(or freeware, admittedly) product is easy. You just throw something together in a VM and show it off.
That was my experience when I was trying to convince my employer to drop sharepoint for a wiki. They weren't turned off by the cost of sharepoint; but the fact that I was able to ask my boss for some time at one of our department meetings, get behind the projector and say "Hey, I threw this demo together in a weekend and put in some example content so you can get an idea of how we would use it. Easy web interface, versioning, strong ability to create links between otherwise disparate pieces of technical knowledge, check it out at $INTERNAL_IP..." Everyone pulled out their laptops, poked around a bit, there was some discussion, and the boss green-lighted it.
Had I given a speech about how we had to, like, fight the proprietary power, man, it would have gone nowhere. However, being able to just sit down, turn on, and show off, all without any serious backing or funding(because everything was free) allowed me to go from "nothing" to "green light-full production status". "Free" never entered into it in a hard financial way. However, had it not been free, I couldn't have done what I did. Now, Anecdote doesn't equal data, much less proof; but it is something to consider.
You say that like it's a good thing.
To the people who make decisions, it is.