openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robw...@apache.org
Subject svn commit: r1443512 - in /openoffice/ooo-site/trunk/content/why: leftnav.mdtext why_compliance.mdtext why_new_computers.mdtext why_office2003-end-of-life.mdtext
Date Thu, 07 Feb 2013 14:50:15 GMT
Author: robweir
Date: Thu Feb  7 14:50:14 2013
New Revision: 1443512

URL: http://svn.apache.org/viewvc?rev=1443512&view=rev
Log:
various content additions/updates

Added:
    openoffice/ooo-site/trunk/content/why/why_new_computers.mdtext
Modified:
    openoffice/ooo-site/trunk/content/why/leftnav.mdtext
    openoffice/ooo-site/trunk/content/why/why_compliance.mdtext
    openoffice/ooo-site/trunk/content/why/why_office2003-end-of-life.mdtext

Modified: openoffice/ooo-site/trunk/content/why/leftnav.mdtext
URL: http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/why/leftnav.mdtext?rev=1443512&r1=1443511&r2=1443512&view=diff
==============================================================================
--- openoffice/ooo-site/trunk/content/why/leftnav.mdtext (original)
+++ openoffice/ooo-site/trunk/content/why/leftnav.mdtext Thu Feb  7 14:50:14 2013
@@ -19,5 +19,7 @@ divid: leftnav
 
   - [ODF](/why/why_odf.html)
   - [Volunteers](/why/why_volunteers.html)
-  
+  - [New Computers](/why/why_new_computers.html)
+  - [Compliance](/why/why_compliance.html)
+  - [Office 2003 End of Life](/why/why_office2003-end-of-life.html)
 

Modified: openoffice/ooo-site/trunk/content/why/why_compliance.mdtext
URL: http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/why/why_compliance.mdtext?rev=1443512&r1=1443511&r2=1443512&view=diff
==============================================================================
--- openoffice/ooo-site/trunk/content/why/why_compliance.mdtext (original)
+++ openoffice/ooo-site/trunk/content/why/why_compliance.mdtext Thu Feb  7 14:50:14 2013
@@ -45,25 +45,28 @@ However, organizations that use open sou
 of some open source licenses.  If one of your employees or contractors inadvertently includes
some copyleft code in your proprietary product, then you could be required by that license
 to make the source code for your entire product freely available to the public.  That could
kill your business.
 
-This is not just a theoretical concern.  As aggressively as the BSA protects the interests
of its commercial members, the Software Freedom Law Center protects the GPL license 
-in [high-profile lawsuits against large corporations][2], including Westinghouse, Samsung
and Best Buy.
+This is not just a theoretical concern.  As aggressively as the BSA protects the interests
of its commercial members, the Software Freedom Law Center (SFLC) protects the GPL license

+in [high-profile lawsuits against large corporations][2], including Westinghouse, Samsung
and Best Buy.  The Free Software Foundation (FSF), in their [November 2012 Bulletin][4], 
+writes about their expansion of "active licence enforcement".
 
 So the cost of compliance with copyleft code can be even greater than the use of proprietary
software, since an organization risks being forced to make the source code
 for their proprietary product public and available for anyone to use, free of charge.  To
mitigate this risk requires more employee education, more approval cycles, more internal audits

-and more worries.  This is the increased cost of compliance when copyleft software is brought
into an organization.
+and more worries.  This is the increased cost of compliance when copyleft software is brought
into an organization.  This is not necessarily a bad thing.  It is just the reality of 
+using open source software under these licences, and must be weighed in considered as one
cost-driver among many.
 
 
 ##The Apache Advantage
 
-Not all open source licenses are copyleft license.  Not all of them have that viral quality
that radically increases the risk for an organization.  A subset of open source licenses,
-generally called "permissive" licenses, are much more friendly for corporate use.  These
licenses include the MIT and BSD licenses, as well as the [Apache Software License 2.0][3]

-that we use for Apache OpenOffice.
+However, not all open source licenses are copyleft license.  Not all of them have that viral
quality that radically increases the risk for an organization.  A subset of open source 
+licenses, generally called "permissive" licenses, are much more friendly for corporate use.
 These licenses include the MIT and BSD licenses, as well as the 
+[Apache Software License 2.0][3] that we use for Apache OpenOffice.
 
 Like other open source licenses, the Apache License explicitly allows you to copy and redistribute
the covered product, without any license fees or royalties.  But because it is a
-permissive license, it also allows you to prepare and distribute derivative products, without
any requirement to make your own source code public.  So both BSA and SFLC risks
-are eliminated, and the cost, to your businessa, of license compliance is drastically reduced.
+permissive license, it also allows you to prepare and distribute derivative products, without
any requirement to make your own source code public.  So both BSA and SFLC/FSF risks
+are eliminated, and the cost, to your business, of license compliance is drastically reduced.
 
 
 [1]: https://reporting.bsa.org/r/report/add.aspx?src=us
 [2]: http://www.softwarefreedom.org/news/2009/dec/14/busybox-gpl-lawsuit/
 [3]: http://www.apache.org/licenses/LICENSE-2.0
+[4]: http://www.fsf.org/bulletin/2012/fall/why-gpl-compliance-work-matters

Added: openoffice/ooo-site/trunk/content/why/why_new_computers.mdtext
URL: http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/why/why_new_computers.mdtext?rev=1443512&view=auto
==============================================================================
--- openoffice/ooo-site/trunk/content/why/why_new_computers.mdtext (added)
+++ openoffice/ooo-site/trunk/content/why/why_new_computers.mdtext Thu Feb  7 14:50:14 2013
@@ -0,0 +1,32 @@
+Title:     Apache OpenOffice for New Computers
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+##Save money on your new computer
+
+Are you buying yourself a new computer?, or buying one for someone else? If so, here is a
money saving tip that your computer vendor may not be telling you.
+
+You are not required to spent $100, $200 more for a copy of Microsoft Office. You can buy
a computer without Office installed, and save that money. Then when you go home, 
+try the free, [Apache OpenOffice (AOO)][1]. It has a word processor, a spreadsheet and a
presentation editor. It can read Microsoft files. It can export to PDF. It works on 
+Windows XP-Windows 8, Mac OS and Linux. And it is absolutely free!
+
+How can we give this to you for free? We're a nonprofit organization with the charitable
mission to publish free software for the public. That's what we do. We want you to 
+have free software.
+
+So when the salesman tries to load up your computer invoice with all those "extras", just
say "Thank you, but No.  I will install AOO".
+
+[1]: http://www.openoffice.org/download
\ No newline at end of file

Modified: openoffice/ooo-site/trunk/content/why/why_office2003-end-of-life.mdtext
URL: http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/why/why_office2003-end-of-life.mdtext?rev=1443512&r1=1443511&r2=1443512&view=diff
==============================================================================
--- openoffice/ooo-site/trunk/content/why/why_office2003-end-of-life.mdtext (original)
+++ openoffice/ooo-site/trunk/content/why/why_office2003-end-of-life.mdtext Thu Feb  7 14:50:14
2013
@@ -16,16 +16,18 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
 
-##What will happen in April 2014?
+##The April 2014 deadline
 
 Microsoft has [announced][1] that they are ending support of Office 2003 and Windows XP on
April 8th, 2014.  What does this mean?  As they describe,
 "After April 8, 2014, there will be no new security updates, non-security hotfixes, free
or paid assisted support options or online technical content updates."  This,
 according to Microsoft, exposes Office 2003 users to greater "Security & Compliance Risks".
 
-##Time to explore alternatives
+##Exploring the alternatives
+
+Some companies and users will write a big check to Microsoft and upgrade to a new version
of Windows and a new version of Office.  But other companies will see this as an opportunity

+to explore the alternatives, including open source products like Apache OpenOffice, the leading
free productivity suite.  It is not too early to start planning for a migration off 
+of Microsoft Office 2003 and Windows XP.  Many companies have already started.
 
-Most companies know that it is not too early to start planning for a migration off of Microsoft
Office 2003 and Windows XP.  The smartest companies are taking this time 
-to explore other available in the market, including Apache OpenOffice, the leading free productivity
suite.   
 
 [1]: http://www.microsoft.com/en-us/windows/endofsupport.aspx
 



Mime
View raw message