EU Publishes Open Source Migration Guidelines
Skunil writes "The IDA Open Source Migration Guidelines provide practical and detailed recommendations on how to migrate to Open Source Software (OSS)-based office applications, calendaring, e-mail and other standard applications. These guidelines have been designed to help public administrators decide whether a migration to OSS should be undertaken and describe, in broad technical terms, how such a migration could be carried out. They are based on practical experience of a limited number of publicly available case studies, and cover a wide range of management and technical concerns."
Boot cdrom format load linux
Anyone else find the humor in the spreadsheet being an XLS file? I figure if the target audience is a group of people who use MS products, then they'll have no problem opening that XLS file.
I'd feel better about these "how to transition your project to open source" guidelines if the first step weren't
Okay, okay, just kidding.
You cannot apply a technological solution to a sociological problem. (Edwards' Law)
Step one... stop bending over
Step two... remove Microsoft "probe"
*FREEDOM*
SCO: 800-726-8649
Verisign: 800-361-8319, 888-642-9675
Diebold: 800-433-VOTE (8683)
Now if only they were talking in the terms of Free Software instead of merely Open Source I would be sure that they are indeed motivated by our freedom and not only technical superiority of GNU. But I am sure that it is only a matter of time until the Freedom ideals are widely recognised in EU parlament. This is a step in the right direction. There are other steps which must follow.
Sincerely,
Pan Tarhei Hosé, PhD.
"Homo sum et cogito ergo odi profanum vulgus et libido."
OSS advocates should also advocate to businesses that are just starting up and households that are just purchasing their first PC.
It would make more sense to start fresh with free software rather than to switch after paying for proprietary software.
I'd really suggest you download the pdf before commenting. It's really quite a piece of work. In fact it looks like it might be the most comprehensive guide yet written on how to migrate to opensource. This is good stuff.
Armed with this and of course google and you'd be way ahead of the curve in planning or evaluating a migration to opensource.
Kudos to the authors.
If you wanna get rich, you know that payback is a bitch
Here is the short form for deciding whether migration to OSS is appropriate:
1. Are you OK with a foreign company having complete control of your data?
Answers:
Yes -- Continue using MS products.
No -- Switch.
That's "Mr. Soulless Automaton" to you, Bub.
Windows ..... Linux, OpenBSD, FreeBSD,etc.
MS Office ....... OpenOffice, ????
Outlook, OulookExpress ...... ????
you get the idea.
Unless you know what the OSS version's name is, you wouldn't know what to replace it with.
I don't know what all the OSS replacements are, if there are any, or what functionality they have (haven't). This would greatly help someone trying to migrate. Otherwise, I'm afraid, they'll just throw up their hands, and say,"I don't know where to start."
There is no spoon or sig.
11.6.2. Personal databases held centrally or locally
Ad hoc personal databases are not well supported in OSS. There is no direct equivalent to Access, nor is one being developed. Several of the groupware packages do offer some capability in this area using a variety of OSS SQL databases as a back-end. In some cases (such as NullLogic) ordinary users can only use pre-defined queries. Some offer the ability to define forms that can be used to store and access data.
Is there someone who could either rebut this statement, or would want to work on a replacement? Yes, Access sucks and is the bane of any data-warehousing project... but it's utility is the reason there are so many small but completely critical .mdb files out there.
Make sure everyone's vote counts: Verified Voting
Don't you think step two should precede, rather than follow, step one? I mean, ouch...
1984 was supposed to be a warning, not an instruction manual.
before bashing it?
First of all, it is for EU agencies. Using this material to back up your decisions might be the difference between a promotion and getting fired if you work for such an organization. This is important for the audience it was written for.
Also, if you are into migrations to OSS, you might find some useful information, regardless of its target audience.
Anyway, the FASB is as bureaucratic as the EU and their publications are much more boring, but as a CPA I hang on every word they publish and so should anyone working in the accounting field, throughout the world. This is not about inspiring people, it is about setting standards, which is not as entertaining as the former but is just as important.
Personally, I think it is great for ANY institution to write on this subject, especially when it has a degree of objectivity on the subject. Many of the "case studies" that this was based on have never been published, so this adds additional observational information on the subject, at the very least.
Sdelat' Ameriku velikoy Snova!
The first dozen pages of the document that I read tell how to make such a switch. So here's the second short form:
Do you want to be branded a political failure in the switch?
If you chose 2, switch gradually, one system at a time, starting with the least-critical systems and the systems farthest away from direct interaction with users. Once you get to the users, switch their interfaces one piece at a time, starting by introducing Free Software that runs within the existing proprietary framework (examples include Mozilla and OpenOffice.org products for Windows OS).
Will I retire or break 10K?
In fact, I would expect it to be in an MS format since the document (I assume) is about _how_ to migrate from MS to Open Source. Putting it in some Open Source format would be ironic, because, then how could those using MS possibly read it and thereby learn how to migrate?
Irony occurs when the conveyed meaning is contrary to expectation or the literal meaning.