Slashdot Mirror


The State of Munich's Ongoing Linux Migration

christian.einfeldt writes "The Munich decision to move its 14,000 desktops to Free Open Source Software created a big splash back in 2003 as news circulated of the third-largest German city's defection from Microsoft. When it was announced in 2003, the story garnered coverage even in the US, such as an extensive article in USA Today on-line. Currently, about 60% of desktops are using OpenOffice, with the remaining 40% to be completed by the end of 2009. Firefox and Thunderbird are being used in all of the city's desktop machines. Ten percent of desktops are running the LiMux Debian-based distro, and 80% will be running LiMux by 2012 at the latest. Autonomy was generally considered more important than cost savings, although the LiMux initiative is increasing competition in the IT industry in Munich already. The program has succeeded because the city administration has been careful to reach out to all stakeholders, from managers down to simple end users."

7 of 203 comments (clear)

  1. Re:A success? Some people disagree... by Anonymous Coward · · Score: 5, Insightful
    It's not the criticism I can't stand, it's the tone op most of the posts. They way he words his blog shows that this isn't about criticising the project. A few examples perhaps.

    Waaaah! Asus Slapped Linux in THE FACE! Sob! Somebody call the Waahmbulance!

    Linux dreamers have faith that Linux is more than just a niche product for hobbyists and power users.

    Mr. Babcock then goes on for like another 3,000 words, explaining how Microsoft, which makes over a billion dollars profit each month needs to follow the Linux model, which makes zero. Good luck with that!

    Now maybe, in your opinion, that's criticism, in mine it's trolling

  2. Re:Both sides of the story by cryptolemur · · Score: 5, Insightful

    Looks like government job to me:

    • 3 years to plan
    • 1 year to prepare and get selected OS certified
    • 2 years for training, piloting, feedback and revising
    • 1 year for final migration
  3. Re:Both sides of the story by ultrabot · · Score: 5, Insightful

    It's supposed to save money in the long run, of course MS will be cheaper at first because you don't have to cope with defeating the vendor lock-in if you stay with Windows but it matters what happens a few years down the line.

    Additionally, the money they use will be channeled to local companies (which means more jobs, improvement of local skill pool, making it cheaper to repeat such transitions in other cities).

    Definitely beats shoveling the money to american robber baron company by any stretch.

    --
    Save your wrists today - switch to Dvorak
  4. Re:Both sides of the story by jcookeman · · Score: 5, Insightful

    I don't think you read the relevant bits. The project was put on hold a few years ago for patent legality research. And, they are doing a "soft migration" in which relevant open source applications are being installed on Windows to gear up the user base for the switch. Just pulling the rug out from under all the users quickly is stupid and will generate nothing but backlash. I read the OSOR page, and it seems they know what they are doing and doing it well. I drive a Mercedes, and I can say that Germans don't half ass things. Speculatively, I would say the cost is so high because the city most likely dug themselves a hole by developing loads of software that is Windows specific. But, they are doing the right thing here by getting their technology independence. In 10 years from now, their operating costs will be amazingly low since they will ditch millions in MS tax, have a user base acclimatized to Linux, flexible applications, and knowledgeable admins. This should be an example and business case to other governments and large organizations that they too can save themselves tons of cash by just going through the pain of undoing "easy decisions".

  5. Re:Both sides of the story by ReeceTarbert · · Score: 5, Insightful

    Wasn't this suppose to save money?

    Not really. From the article:

    "While the proprietary solution was deemed to be slightly more cost-effective over the full period, the strategic advantage of being free to take its own IT decisions led the city council to decide in favour of the migration to GNU/Linux. "

    and also from the same:

    "The Microsoft solution would have made it necessary to introduce an Active Directory system, which would have meant a strong lock-in and would have caused significant follow-up costs.

    RT

  6. Re:A success? Some people disagree... by Anonymous Coward · · Score: 5, Insightful

    This whole Munchen idea was NOT about how much the company's involved making money. It was about the CONSUMER paying less money.

    You know - I always think it is strange that these arguments are all about how the company's are driving well, but not how the consumers (and that are you and me and the man in the street - make no mistake) are served well. I do not care a bit if Microsoft gets money or gets a lot more money. However - I DO care if it is MY money. Open Source software is cheap, so it is a big bonus for me as consumer. I do not care if Ballmer gets a lot of money - as long it's not my money. Result? If I buy some Microsoft software I shoot myself in the foot. Most consumers - and that's most of you and certainly me - are better off with Open Source software. Simple...

    Try to see all this from a consumer point of view.

  7. Re:Both sides of the story by 99BottlesOfBeerInMyF · · Score: 5, Insightful

    Okay, they want freedom to choose the software they want to use, but considering the state of OS email clients I'm not sure they really have any.

    I disagree, but let's discuss.

    I'm not trying to troll, in fact we looked at migrating our machines at work from Outlook to Thunderbird or another free app on Windows or Linux, but gave up in the end because none of the available clients could replace what we do with Outlook.

    I'll give you the benefit of the doubt when it comes to trolling. Of course every client will have different strengths and weaknesses. Likely Outlook can't replace everything existing Thunderbird users have either. The difference being, Thunderbird can be altered by individual companies while Outlook cannot.

    For example, Thunderbird does not have any kind of default template support, so our users would have to remember to use the right template every time they write an email.

    The real problem here is familiarity and skill of people implementing the system, not limitations of Thunderbird. In this instance you can use the externaltemplateloader extension to load a default template based upon the user. I'd never done it, but it took me all of 30 seconds to figure out how and a 5 minutes to test it and confirm it works. If you haven't hired someone competent enough to do a Google search to do your evaluations (or better yet someone expert in the field to consult) you are unlikely to succeed in any transition and will always fail back to the status quo.

    We looked at Kmail too (not bad, but lacks group calendaring and is Linux only)

    Kmail is fine for parts of a company standardized on Linux or for mixed deployments where you let users have a choice of clients because you're standardized on truly open and standard protocols. I've worked in such places and found it very liberating.

    For us iPhone and Blackberry integration is important too which makes things that much harder.

    Why? Both have good support for both standard and proprietary e-mail protocols. How does this make choosing a desktop client harder?

    What I'm saying is that unless you are willing to do some coding yourself then the freedom of OSS is not really that liberating if the area you are looking at happens to be under developed.

    Well, due to the nature of opensource and its use of standard protocols, you will tend to gain more choice with it, but then the real strength of opensource is the flexibility and cost savings. The advantage multiplies with adoption rates and the size of the deployment. If you're only deploying to ten users, it makes little economic sense to pay someone to implement a feature and add it to en existing OSS client, when compared to the licensing cost of a proprietary client. When you're talking about a deployment of 100,000 users it quickly becomes cost effective to hire someone to make needed changes or even have a full time developer working on a project and adding features and fixing bugs important to your company.

    ...but there is still a lot of important software we need that forces us to stay with commercial software.

    For some instances this is certainly true, but I find that more often people simply think it is true and don't bother consulting anyone who actually knows. If you're seriously considering different applications for some purpose, don't just talk to closed source commercial companies, talk to open source commercial companies. Ask Redhat or Canonical what they have to offer and what the can do for you. It makes a lot of sense especially for new transitions. If you don't feel like paying them in the long term, you can always go it alone later.

    One of the biggest problems with this sort of adoption is people try to sell it as short term cost saving measure, when transitions will always incur expenses. OSS is abo