Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 08/05/2011 02:39 PM, webmaster for Kracked Press Productions wrote:

The new chief information officer for the federal government - White
House Chief of Information Technology - is a former Microsoft Executive
[and assistant to Bill Gates].

Since all these big wigs in Microsoft get large blocks of stock in the
company, which he most likely still has, this new guy in the White House
as a good reason to keep the government using MS products over free and
open source ones.

So I say; there goes the government's push to go open source and start
using packages like LibreOffice.

Well, MS tries to control the world's computers, and now they have a man
in the White House to control the government's computer system and other
technology to MS's favor.

The problem is not with the Chief Information Officer, buy with the Chief Community Organizer that appointed him knowing that the CIO is a MS shill, and with those who elected a know-it-all know-nothing to move into the White House.


--
Stan Goodman
Qiryat Tiv'on
Israel

--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.