Munich Linux Migration Project LiMux Reports Success
LiMux, a project to convert local government institutions to Linux and open source software in Munich, has exceeded initial expectations. The project has done slightly better than projections of 8,500 and now boasts 9,000 Linux migrated workstations. The progress and evolution of this project that began in 2003 is well worth examination.
LiMux is the name of both the migration project and a specialized Linux distribution. The LiMux distro, which is based on Ubuntu, is certified by the German government for use in both government institutions and private businesses. I've long been an advocate of this approach, and I wish that more was being done in the UK and the US to ratify a standard national Linux distro.
It's nice to be able to report on this success story after the disappointing news, earlier in the year, that the German Foreign Office had abandoned its Linux adoption plan in favor of a return to Windows and other proprietary software. One thing that the community has had to learn is that celebration upon hearing the announcement of a plan for Linux adoption is sometimes premature. The news that migration has been successful and is going well is a more reliable indicator that Linux is establishing a foothold on the desktops of government workers.
In a 2010 webpost, Florian Schießl, one of the architects of the project, admitted that they had underestimated the difficulty of the task and labeled their initial approach “naive”. When the project was first set in motion in 2003, there were found to be 1000 IT workers in 51 data centers serving 33,000 staff. Part of the problem was that the proprietary software that was in use was far from being as homogenized as most people would have guessed. As Schießl says:
"No common directory, no common user, system or hardware management. Different tools for software distribution and system management. More than 300 apps, many of them redundant, e.g. using Dreamweaver, Frontpage, Fusion etc. for HTML-editing. 21 different Windows clients, different patch levels, different security concepts. This was Munich’s IT situation when LiMux started."
So, as part of clearing the way for Linux and open source adoption, the team have to had reorganize government IT policy to move it away from the rag-tag collection of mismatched systems that had organically evolved. Don't forget that in addition to operating systems and applications, a project like this one has to consider document formats and templates. Schießl considers the focus on ODF throughout the organization and across different platfroms to have been a big help for the project as a whole. To help with this, the LiMux project has created WollMux, an open source template creation plugin for OpenOffice.
A lot of attempts at large migrations to open source software seem to be so focused on the software and hardware that they tend to forget the other other important factor: people. Forgetting to win over the staff seems to be a common trait of migration projects that fail to accomplish their goals. From 2008 onwards, the LiMux team began to adopt a more considered approach to migration, beginning with smaller deployments and lots of data gathering in order to gauge success.
Overall, it's good news and a project worth studying by anyone interested in large scale migrations to Linux.
The official LiMux page (English language)
Flag clipart provided by: 1 Page Design
UK based freelance writer Michael Reed writes about technology, retro computing, geek culture and gender politics.
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
|Trying to Tame the Tablet||May 08, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Home, My Backup Data Center
- Android is Linux -- why no better inter-operation
2 hours 1 min ago
- Connecting Android device to desktop Linux via USB
2 hours 29 min ago
- Find new cell phone and tablet pc
3 hours 27 min ago
4 hours 56 min ago
- Automatically updating Guest Additions
6 hours 5 min ago
- I like your topic on android
6 hours 51 min ago
- Reply to comment | Linux Journal
7 hours 13 min ago
- This is the easiest tutorial
13 hours 27 min ago
- Ahh, the Koolaid.
19 hours 6 min ago
- git-annex assistant
1 day 1 hour ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?