Munich Delays Linux Conversion 181
It doesn't come easy writes "A short blurb over at The Register reports that Munich has decided to extend the pilot phase of their Linux migration project. One smart move mentioned: Many of their office workers will switch to OpenOffice on Windows first where it is comfortable, easing the transition."
waiting for the discount offers from microsoft to (Score:4, Funny)
Re:waiting for the discount offers from microsoft (Score:5, Informative)
Great, if it actually brings the price down... (Score:3, Insightful)
Re:Great if they don't use GPL 2006 (Score:2, Informative)
Linux is under GPL 2 not GPL 2 or later so that is no issue. Open Office is under the LGPL not the GPL.
You're not paying attention to the *or* in there.. (Score:3, Informative)
If the software was released under with an "AND" instead of the "OR" then it would require you to follow future revisions of the GPL (although the AND clause is fairly foggy and it should be better written then that.) If the license said "You must follow the latest revision of the GPL" then you'd obviously have to honor that.
Personally, I prefer the LGPL for mos
Re:Great if they don't use GPL 2006 (Score:5, Informative)
for example you write a compression algorithim, patent it and release source code for it under GPL, People can make projects with your compression algo and as long as they release it under gpl its all good... but if some company wants to include you compression algo without making their code subject to the gpl they cant without infringing on you patent
in other words patented software released under the gpl is good
Re:Great if they don't use GPL 2006 (Score:2)
Maybe the solution to the GPL software patents "problem" is for GPL software authors to begin aggressively patenting their work?
I mean, there are certainly lots of things that exist in the various flavors of the Linux operating system that could be patentable (certainly by the low standards the Patent Office here in the U.S. seems to be using). Rather than just scream and yell about how evil software patents are, maybe as a community we should start actively and encouraging auth
Re:Great if they don't use GPL 2006 (Score:2, Insightful)
Re:Great if they don't use GPL 2006 (Score:3, Insightful)
It's a nice suggestion and all but i have a hard time seeing it work. Perhaps in a few limited occassions like for some kernel stuff where the patents could be used for cross l
Re:Great if they don't use GPL 2006 (Score:2)
As I've thought about it more, the way to use patents in the FOSS world wouldn't be as an 'offensive' weapon, something that you'd use against a commercial company just because they weren't liked, but as a deterrent.
It's the reverse of the above scenario. The commercial company says that some piece of Free Software violates its patents. The FS people can come back and show that the commercial software is also violating a number of their patents.
The result is a sort of 'mexican standoff.'
By
Re:Great if they don't use GPL 2006 (Score:2)
Re:waiting for the discount offers from microsoft (Score:5, Informative)
Re:waiting for the discount offers from microsoft (Score:2)
Re:No, Open Office 2 (Score:2)
This has come up a couple times in the past.
What is better (if anything) about how OO handles styles? (This is a legitimate question BTW; I'm not trolling.)
I did note that they have more categories of styles; Word has character and paragraph styles but OO has list and a couple others.
(However, even if OO support for styles is better, I have a list of many other things that OO 2 *doesn't* have but Word does, or Word does better. For instance, OO writer doesn't have a view that equates with Wo
Re:No, Open Office 2 (Score:2)
And that's supposed to be a bad thing? OO2's word completion is utter crap. It should't insert the word when you try to enter a return instead of a letter - typing while something is selected replaces the selection... except if you type return. This is completely contrary to any GUI interface guideline I know of, and is very, very dumb.
Open Office is Open Office... Or is it? (Score:4, Interesting)
Isn't OpenOffice on Windows the same as OpenOffice on Linux? I see in the story at The Register that they have various office templates and scripts that they want to port to OpenOffice, yet why waste time removing Office from each machine, then installing OpenOffice, then getting all the scripts and templates to work, then having to recreate things when done again in the Linux environment? Why not just cut out the middle steps and go directly from Office on Windows, to OpenOffice on Linux?
People, am I missing something here, or would it not just be best to just go to Linux with openOffice functionality directly, and not even bother with this middle step? If you ask me, it sounds like something else here is amiss, as their reasoning seems flawed to me...
I can understand people being concerned about switching from a Microsoft Windows environment, using Office for their word processing, spreadsheet, database, and presentation tasks... yet as far as things go, Linux can do the same things with OpenOffice just as easily...
Also, Linux has a web browser, music player, everything that a company could need to do business with, and these days, with the majority of applications that companies needing built on web-based infrastructures, there really is very little reason to run Windows these days. Of course some companies still have applications that are Windows-only, but with time I can see more applications being able to function on Linux...
Another bonus of running Linux is the amount of spyware that will be cut down drastically, as windows is well known for how easy spyware can infect it and totally ruin a system image. If they would just hurry up and switch to Linux, so many problems would be solved...
Oh well, at least they can build cars right over in Germany...
Re:Open Office is Open Office... Or is it? (Score:5, Insightful)
makes sense to me.
Re:Open Office is Open Office... Or is it? (Score:1, Interesting)
It's the fancy stuff. (Score:2, Insightful)
Can you imagine what most geeks would do if copy went from ctrl-c to ctrl-k or something like that?
Just a thought.
Re:It's the fancy stuff. (Score:2)
You mean like copy is Ctrl+C sometimes, y in Vim, C-w in Emacs, etc?
I rarely have any trouble, except when I try to do things like "copy next word" or "copy this line" that aren't available in the application I'm currently in.
Re:It's the fancy stuff. (Score:2, Insightful)
Fortunately, isn't harmful in anything but vi.
Re:It's the fancy stuff. (Score:2, Funny)
Of course, the opposite slant you could put on that would be that vi is more likely to be encountered on any random system you might come across than nano or pico, which means you have an advantage if you do know some of the keystrokes.
And
Re:Open Office is Open Office... Or is it? (Score:3, Insightful)
It's more about psychology. People generally don't like change. And big change is more disrupting than small change. Part of that comes from fear of the unknown.
You get people transitioned to OO still on their familiar windows platform. It gets them used to the new OO system, while also helping build confidence in the overall changes to come.
While it might make more sense from an IT standpoint to just make the change and be done with it, from a human ma
Re:Open Office is Open Office... Or is it? (Score:2)
Re:Open Office is Open Office... Or is it? (Score:2)
Re:Open Office is Open Office... Or is it? (Score:5, Insightful)
Which quite honestly is a bigger change than changing from M$ Office to OpenOffice.
The effect will be that they will be able to convert there templates and scripts while still using an OS they are comfortable with, then copy those Templates/scripts to there Linux setup once they are accustomed to OpenOffice.
You and I may have no problem changing OS'es just like that, but they are dealing with general users that wont be, and will simply be expecting there computers to just work.
Re:Open Office is Open Office... Or is it? (Score:3, Insightful)
Which quite honestly is a bigger change than changing from M$ Office to OpenOffice.
You and I may have no problem changing OS'es just like that, but they are dealing with general users that wont be, and will simply be expecting there computers to just work.
Having performed exactly this sort of migration, I completely disagree. It is the switch between Office systems that is the main issue. For a typical
Re:Open Office is Open Office... Or is it? (Score:2, Insightful)
Explain to me how the switch from Office on Windows to Open Office on Linux is not two steps to beging with. I would say going to Open Office first, then to Linux would more easing into OSS then the other way around. Switching your OS is a much bigger step than switching your word processor/office suite software. And if you switch your OS to L
What you missed (Score:1)
What you missed was the 'large number of complex applications.' To me this implies that there are applications (outside of Office) that will need to be 'transitioned.' They'll need to wean people off the applications or create Linux-compatible equivalents.
Re:Open Office is Open Office... Or is it? (Score:5, Insightful)
Training, primarily, as well as care and feeding of the myriad process monkeys with their taproots in the flow.
Seriously, large organisations - including municipal governments - are notoriously risk-adverse. Not adverse to change, but adverse to unmanaged change. And if you're working with people who are extraordinarily process-minded (the nursing profession comes to mind) then you're not going to get the ball over the line without showing a step-by-step progress from point A to point B. Smaller steps will be seen as less-risky, and therefore better. Chaos in any bureaucracy is considered irreligeous.
Re:Open Office is Open Office... Or is it? (Score:5, Insightful)
Secondly why migrate the apps first? Think about it. You want to make sure everything works. This usually means migrating in stages and slowly. The last thing you want to do is migrate everything all at once and then have to shut down everything for a month while you rebuild certain areas of your infrastructure. So you start with the easiest to replace areas (Mozilla/Firefox, OOo) and work down from there. You have some people on a pilot program using Linux and finding all the issues with it, and this makes it easier to migrate additional areas. Also moving everyone over to OOo as soon as possible makes a lot of sense because it helps the people on Linux use the same software as the people on Windows.
Ideally this pilot program would be done by those people with the least specific requirements and the fewest software tools they rely on. Once these users are stabilized, then you can expand the pilot to a larger group with slightly more complex needs. And so forth. I figure that a well orchistrated migration of a large organization will take at least 3-5 years to complete assuming all goes well.
Mod parent up! (Score:3, Insightful)
The best way to approach this is to have a lot of small steps. That way, any minor advance that has a problem can be rolled back without killing the entire project.
The trick is to space out the changes that the end user has to deal with so they don't get overwhelmed by them.
And neither do your techs.
It's all about the migration plan.
Re:Open Office is Open Office... Or is it? (Score:4, Interesting)
So basically, despite trying to sound like you know what you're talking about, you don't know enough about large scale human-office-computer dynamics to closely estimate the completion time.
I came up with that estimate based on my experience working at major corporations and seeing how they made migrations. An OS migration on the desktop has to be one of the most painful migrations you can put an organization through.
I would also point out that so far the large migrations in progress are either being scaled back or are moving towards the 4-year timeline (+/- a year).
There are also some other good reasons for this estimate. Often this is the OS upgrade lifecycle (and sometimes even line of business tools lifecycle) in many organizations, so it makes sense that you can phase out other line of business apps in favor of those that are cross-platform in this length of time. In essence, I figure one can probably go with a 4-year migration plan without spending a huge sum more on the migration.
Re:Open Office is Open Office... Or is it? (Score:2, Insightful)
For the IT department, switching the O/S is more complicated than switching the office suite because of all the details (user accounts, profiles, mail, printers, and so on).
But for a end user which spend most of its time in the mail client,
Re:Open Office is Open Office... Or is it? (Score:2)
What I got from re
Re:Open Office is Open Office... Or is it? (Score:5, Informative)
Probably because they'll install OpenOffice before removing MS Office, so they can continue to use their scripts and templates while they get them working in OpenOffice. It's a lot easier to write a new version of your templates if you can see how the old version works with software you have available.
Re: (Score:2)
Re:Open Office is Open Office... Or is it? (Score:2)
It is about the
Blarg - a non story (Score:5, Insightful)
Re:Blarg - a non story (Score:2, Insightful)
But I think that holding back to check a few more issues (when no deadline is fixed on stone) is a good attitude to be prised.
If more managers were keen to "hold back and take a fairly good look at it" instead of "rush for delivery" I'm sure the overall quality of work would benefit enormously.
My 2 cents
--
Grammar Zealotes: please spare a non-english [lastknight.com] writer
Re:Blarg - a non story (Score:2)
see http://www.it-cortex.com/Stat_Failure_Rate.htm [it-cortex.com]
for a good start on the stats.
Sounds like a good idea (Score:3, Insightful)
To see such a move going so well that they intend to do more of it is certainly heartening. I know that I wish the American government would allocate its funds better. Switching to low-cost, high-quality solutions like Linux provides us taxpayers with more bang for our buck.
Let's see how well it goes in Germany and see what lessons we can take away from it!
Re:Sounds like a good idea (Score:2)
True and not true. Supporting American companies is Good® for America - but the governments efforts should be for funding open source software, this is true.
There is no reason that the government shouldn't be able to enter into contracts for solutions. Blanket contracts are another story all together. It doesn't work with Halliburton and it doesn't work with Microsoft. Spending tax money on some pr
Nothing to see here (Score:5, Insightful)
Re:Nothing to see here (Score:3, Funny)
According to the /. collective, I thought that's EXACTLY how it should go.
Re:Nothing to see here (Score:2)
Office compatibility (Score:4, Interesting)
For God's Sake! (Score:2)
The advantages of using OpenOffice are not, primarily, cost based (although that is a consideration), it's the fact that the City of Munich has ultimate control over what happens with their software. They can review the source code, they can modify the source code, and they are beholden to one less American corporation.
Re:For God's Sake! (Score:2)
Actually, more like free as in speech and free as in beer, but not free of consequences. Even if I gave you all the free beer you'd like, there'd be consequences to your present (intoxicated), short-term (headache) and long-term (health issues) condition. All that should be counted in the TCB (Total Cost of Beer)
Kjella
Re:Office compatibility (Score:2)
How well it works depends on what version of word you are using, what version the document is, what version of openoffice you have etc. However the main issue is that the word document form
Somewhere in Redmond... (Score:5, Funny)
Re:Somewhere in Redmond... (Score:2)
Re:Somewhere in Redmond... (Score:2)
Now my brain is dirty.
Re:Somewhere in Redmond... (Score:5, Funny)
Another scene today at Balmer's office in Redmond, Washington
Adjunct: Good morning, Mr. Balmer
Balmer: Good morning to you, sir. I'm smelling the nice aroma of freshly printed $100 bills coming to our empire today. Hopefully Windows Vista and MS Office 12 preorder sales are through the roof. I can hear geeks online shouting about the virtues of IE 7, Avalon, and C#. Do you have any good news to tell me today, sir?
Adjunct: Well, I'm afraid another one of your customers made a switch. This time, it's Munich, and they're dumping MS Office.
Balmer: WHAAAAAAT! They're switching? To what?
Adjunct: Well....
Balmer: Please don't tell me it's OpenOffice. Just tell me it's not OpenOffice.
Adjunct: It is. They're switching to OpenOffice.
Balmer then roars into a rage. Roaring and pounding his chest with his fists, he then picks up a chair and throws it at his table, splitting the chair into two.
Balmer: "I'm going to f***ing bury Munich, I have done it before, and I will do it again. I'm going to f***ing kill OpenOffice."
Balmer: "I'm going to kill every single OpenOffice developer that I find. Them dang developers. Developers. Developers, developers, developers, developers...."
Balmer then runs around the entire Microsoft campus like an angry 800-pound gorilla and sings his "Developers" hit.
Re:Somewhere in Redmond... (Score:4, Funny)
Re:Somewhere in Redmond... (Score:2)
Balmer always reminds me of... (Score:2)
Re:Somewhere in Redmond... (Score:2, Funny)
Some questions (Score:4, Interesting)
Re:Some questions (Score:2)
Re:Some questions (Score:5, Informative)
Let me try to remember what I heard on the speech of Florian Schießl at the LinuxTag 2005.
User resistance: people like to stay with what they know rather than being pushed to use something unfamiliar.
True. To convince the users they did a sort of "tournee" through all departments and showed them how Linux looks like. And they got some funny feedback like "I didn't expect to see a GUI".
Extensive use of MS Office only features such as VBA or features that work differently in Open Office.
True. One of the biggest problem is a custom installed VBA something installed by a "primadonna". Its a hard job to convince the people to change to something completely new.
Applications using Active-X or other COM controls that are not easily converted to WINE or similar.
I have no details on that, but it could be an issue as well.
Third party software products that are only supported under Windows.
According to Mr. Schießl they contacted all their software vendors who provide specific applications and asked them if a Linux port is available or if they can port it to Linux. The feedback to this action was very little so Munich needs to find new partners that are able to provide Linux apps as well.
What else?
Mr. Schießl pointed out that switching is not that easy since the service that the municipality is offering has to remain "online". People would get a lot annoyed if they couldn't register for a car number plate because the city is switching to Linux. So they have to develop a strategy that does the move, but transparent to the citizen that expects full availability of the services.
One other issue could be that since the Munich solution is based on Debian and Debian did the transition from Woody to Sarge recently that might affect the schedule as well. Maybe there are some dependencies on custom software that need to be adjusted to the new environment now. Even if I think that shouldn't be a big deal we need to keep it in mind.
Re:Some questions (Score:2)
Re:Some questions (Score:3, Insightful)
Now, all the effort at replacing them will be blamed on the OS switch, as opposed to just being written off as a necessary upgrade in order to use the new framework and remain competitive. And of course the end users will still bitch and m
Re:Some questions (Score:2)
Re:Some questions (Score:2)
Re:Some questions (Score:2)
Interoperability with other business units/companies/organizations.
OOo is good, but still falls down sometimes when conversing with outide units using MSOffice.
Re:Some questions (Score:2)
Companies that need to exchange documents with a lot of other organizations (that are already using MSOffice) would probably have a harder time switching to OOo, than a company who doesn't really do a lot of outside contact.
Re:Some questions (Score:2)
And that requires an operating shift on that end. Oft times, your clients/collaborators are far larger than you. Forcing a change in their business practices isn't possible. You conform to your market.
Extending a pilot project is A Good Thing (Score:5, Insightful)
This is often a much more sure road to successful acceptance than big-bang rollout projects, where any issues tend to be magnified in that short window when the powers that be see themselves politically vulnerable to errors in execution and might pull the plug.
When going after user acceptance, a pull is better than a push; if users want the change, they're on your side and will work to show the change in the best light. When pushing the technology out to people who would rather have a bit of control over the process, you risk their ire if you tread on their schedules.
It's no wonder the transition is taking time... (Score:5, Funny)
Re:It's no wonder the transition is taking time... (Score:1)
I can't imagine waiting for Gentoo to compile on 30,000 PCs.
Especially since Munich is going to use a Debian based solution...
Re:It's no wonder the transition is taking time... (Score:2)
Re:It's no wonder the transition is taking time... (Score:2)
Re:It's no wonder the transition is taking time... (Score:2)
cd ~/gento
time gmake -j 30000
I'll let you know when it's done!
Re:It's no wonder the transition is taking time... (Score:2)
Re:It's no wonder the transition is taking time... (Score:2)
a. Image 1 PC and dump onto others.
b. Create binary packages on 1 PC and install on others
c. Use thin clients
it isn't OpenOffice's fault (Score:5, Insightful)
One point I see made constantly (wonder how many MS shills there are out there) is the concern and finger pointing at OpenOffice about ensuring smooth interoperability and compatibility with Office documents. This is frustrating.
First (but not foremost) in my opinion the sooner "compatibility with Microsoft" is dropped as the IT yardstick (really it is just a canard), the better. As posted in previous /. articles there are other and emerging standards. The other standards aren't necessarily better (since that's an esoteric discussion unto itself anyway), but I can think of one that in the long run if adopted hints at greater interoperability than seen in a long time.
Second (and foremost AFIC), I've posted on this point many times (hmmm, time to start keeping a list of links), there really isn't such a thing as Microsoft and Office interoperability and compatibility. It's time to push back and start pointing that out to the puff-piece MS standard bearers. How many times have you wasted valuable time at a meeting while attendees share paper copies of the pre-distributed incompatible (with their version of WORD) Word documents? If you don't remember, you're not trying.
It's just not OpenOffice's fault anymore, and it's time to start defending it. I know it's a long shot. I know it's a long haul. And I know I'm getting modded troll and flamebait.
Re:it isn't OpenOffice's fault (Score:5, Insightful)
Sorry, *ding* thank you for playing, join us in reality as soon as you're ready. In your own time, don't rush.
It isn't compatibility with Microsoft that's at issue, but compatibility with business systems that are bulwharked with rivers of existing code. VBA code stuffed inside the gentle spreadsheet and word doc. There are cubic miles of it in banks. This must be managed, and it's a massive change. Yes, they will be far better off from the experience, but there are up-front costs to convert that must be addressed and not to do so would be seen as grossly negligent. Bureaucrats (and yes, I speak fluent Bureaucrat) must be seen as covering all the bases before they make the change. MS standards (particularly document standards and those devilish EULA's) are ugly on so many levels, but nobody wants to push their existing business systems over a cliff to accomplish the change any quicker than they can.
It ain't ideology, it's survival.
Re:spreadsheets or spreadshits? (Score:2)
Like it or not, a startling amount of the worlds wealth resides purely as numbers in columns on Excel spreadsheets. This is particularly true of bulk investments such as managed funds, where you have hundreds of different independent fund managers sending financial data - real value, financial instructions -- to each other. Yes there are controls, but Excel is lingua franca in the halls
Re:Reality called, you were out. (Score:2)
Over A$35B funds under custody running through that stuff, last week -- and that's just one division of the bank. Seems real enough to me, mate. Are you going to tell the bankers they can't have it? I try that and they give me funny looks and award the contract to the next guy. Each doc has several thousand lines of code in it doing strange things like AS400 SWIFT conversions to command line based legacy systems from the oppos
Yes and No (Score:2)
First (but not foremost) in my opinion the sooner "compatibility with Microsoft" is dropped as the IT yardstick (really it is just a canard), the better.
This is correct, in a larger sense. The only way OpenOffice will be successful is if they can drop the "compatibility with Microsoft" claim. That is to say, when your primary measuring stick is comparing your product to the other guys and saying "Hey, we're a
Re:it isn't OpenOffice's fault (Score:3, Insightful)
I agree. As an example, a lot of payrolls systems are based on Excel macros with extensive VBA coding. Most of it sucks and was done by non-skilled techies, but it is doing the job and the amount of work required to replace these homemade solutions is gigantic.
It's not enough (no, it's not) to just sing the Open And Free Standards Song when I have to tell a user that there's no
Re:it isn't OpenOffice's fault (Score:2)
From my point of view, it's much better to get rid of these power user hacks and replace them with proper applications. It's a big task but (similar to Y2K) worth it in the long run.
Re:it isn't OpenOffice's fault (Score:2)
When was that. I use it (although not heavily) and I have not had those problems.
OO is fine if you want to write letters and do simple spreadsheets.
So it is fine for almost everything that MS Office is used for! A good chunk of the remaining (tiny) minority usage is stuff for which MS Office the the wrong solution anyway (e.g. writing what are essentially database apps in Excel).
The only thing
Re:it isn't OpenOffice's fault (Score:2)
I didn't know that more than 30 minutes without freezing would be a problem. Maybe the OOo developers can address your special need with an additional option in the preferences: "freeze every 30 minutes" (the interval could probably be configurable, too).
SCNR
Re:it isn't OpenOffice's fault (Score:2)
Edit > Changes > and it's all there... just click the "Record" option to turn change tracking On
Yes, people will bitch (Score:5, Insightful)
Re:Yes, people will bitch (Score:2)
In a corporate setting where the owner or the person properly appointed by the collective will of the owners(shareholders) it's perfectly fine to force things on employees.
This is a city in Germany. After the previous century, I would suspect that the German people are going to be quite resistant to the idea of having anything forced on them.
LK
Re:Yes, people will bitch (Score:2)
Not citizens, not townspeople. Government employees, on their work computers. These are the 'end users' in this discussion, not the actual recipients of the government's services.
Nobody is saying that the customers (in this case, the citizens who get their services from the government) have to change anything. In fact it seems as though one of the main objectives of the m
Re:Yes, people will bitch (Score:2)
You suddenly hear loud goose-steeping footsteps and your door breaking in..
AND suddenly, the lead penguin has a RAIL GUN!!!!!
"DEBIAN OR DIE, MS weenie!"
(you survey that many are wearing white sheets with RMS's face masks)
You begin to realize that you really are in Hell.
Re:Yes, people will bitch (Score:2)
LK
Yes, there's a delay (Score:4, Funny)
After all, these opensource nuts are the only ones that experience delays, and its only because of the poor caliber of opensource programmers.
Microsoft, of course, never experiences delays. If they had gone with a Microsoft Solution 3 years (projected started in 2001), they'd be running on Longhorm, ahem, I mean, Vista, today!
Smart Move (Score:4, Insightful)
Am I the only one who read (Score:3, Funny)
I had to blink for a second; I knew slashdot has some slow news days but that takes the cake; is it now news that someone had to stop talking about Linux long enough to eat some food?
Look for a new Microsoft Ad (Score:2, Funny)
];)
Re:Delayed??? Nah... (Score:2, Insightful)
I've been using it since 8.0 and every version doing a fresh install (backing up and restoring
Re:Delayed??? Nah... (Score:1)
Re:Delayed??? Nah... (Score:1)
Give it a break... Slackware=simple+stable+speed
Re:Delayed??? Nah... (Score:2, Informative)
As far as I understood the speech of Florian Schießl (project leader in Munich) on the LinuxTag 2005 they are using a Debian based solution. So there is no need to figure out how to install Slackware.
Re:Delayed??? Nah... (Score:3, Insightful)