On 02/26/2011 11:51 AM, Jon Hamkins wrote:
On 02/18/2011 06:11 AM, webmaster for Kracked Press Productions wrote:
So does anyone know a way to get the White House, or the proper people
in the US government, to look at LibreOffice's efforts in the open
source community and to review the software package?
A couple of years ago I started putting together a lengthy seminar for
my employer, NASA/JPL, to explain why ODF and OOo (this was pre-LibO)
were good things to support throughout the laboratory. I never
finished it, but I was thinking of revamping this for LibO. If anyone
wants to help contribute, let me know.
... I am absolutely convinced that the U.S. government could save
quite a bit of money, without sacrificing quality, by moving to LibO.
John,
I'd like to help in this. Two things:
- The federal branch is one substantial target, but there are a lot of
others in the same procurement space [e.g. 1,2]. I think we should, at
least, scope whether to adopt the collateral you worked on to include
interests & requirements for state, province, etc.
1)http://www.cio.ca.gov/Government/IT_Policy/pdf/IT_Policy_Letter_10-01_Open_Source_Software.pdf
2) http://www.sfcoit.org/index.aspx?page=616
Let me know how you'd like to proceed...
Best,
-Craig
--
Unsubscribe instructions: E-mail to marketing+help@us.libreoffice.org
List archive: http://listarchives.libreoffice.org/us/marketing/
*** All posts to this list are publicly archived for eternity ***
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.