openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r841900 - in /websites/staging/ooo-site/trunk: cgi-bin/ content/ content/why/other/compliance.html
Date Wed, 12 Dec 2012 16:26:50 GMT
Author: buildbot
Date: Wed Dec 12 16:26:49 2012
New Revision: 841900

Log:
Staging update by buildbot for openofficeorg

Modified:
    websites/staging/ooo-site/trunk/cgi-bin/   (props changed)
    websites/staging/ooo-site/trunk/content/   (props changed)
    websites/staging/ooo-site/trunk/content/why/other/compliance.html

Propchange: websites/staging/ooo-site/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 12 16:26:49 2012
@@ -1 +1 @@
-1420808
+1420810

Propchange: websites/staging/ooo-site/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 12 16:26:49 2012
@@ -1 +1 @@
-1420808
+1420810

Modified: websites/staging/ooo-site/trunk/content/why/other/compliance.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/why/other/compliance.html (original)
+++ websites/staging/ooo-site/trunk/content/why/other/compliance.html Wed Dec 12 16:26:49
2012
@@ -3,7 +3,7 @@
 <head>
 <link href="/css/ooo.css" rel="stylesheet" type="text/css">
 
-<title>Compliance Costs and the Apache License
</title>
+<title>Compliance Costs and the Apache License</title>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 
 
@@ -20,17 +20,17 @@
   
   <div id="content">
     
-    <h1 class="title">Compliance Costs and the Apache License
</h1>
-    <h2 id="software-licence-compliance-costs">Software Licence Compliance Costs</h2>
-<p>The Business Software Alliance <a href="https://reporting.bsa.org/r/report/add.aspx?src=us">offers
cash rewards</a>, up to $1 million, to disgruntled employees who confidentially turn
in their employer (or ex-exployer) for software piracy.<br />
+    <h1 class="title">Compliance Costs and the Apache License</h1>
+    <h2 id="software-license-compliance-costs">Software License Compliance Costs</h2>
+<p>The Business Software Alliance <a href="https://reporting.bsa.org/r/report/add.aspx?src=us">offers
cash rewards</a>, up to $1 million, to disgruntled employees who confidentially turn
in their employer (or ex-employer) for software piracy.<br />
 They call this campaign, "Bust your Boss!"</p>
 <p>As you probably already know, you don't own commercial software in the same way
you own a chair or a desk.  You license the software from the vendor, and this license gives
you
 permission to use the software, under terms specified by the license.  These terms might
include how many users or PC's may access the software.  The terms might even include
 a clause allowing the vendor to audit your usage of the software.</p>
 <p>In order to avoid the expense and penalties of a BSA audit, companies institute
Software Asset Management (SAM) practices to ensure that their use of commercial software
complies
-with the applicable licenses.  These practices generally include employee education along
with the purchase of software to track licences and software use within the organization.</p>
+with the applicable licenses.  These practices generally include employee education along
with the purchase of software to track licenses and software use within the organization.</p>
 <p>The combined costs of these practices is the "cost of compliance" for using commercial
software.  It is an expense that does not make your organization more productive, does not
benefit
-your customers and adds nothing to the bottom line. It is purely risk mitigation.  Along
with licence, maintanence and training costs, it is one of the costs of working with commercial
+your customers and adds nothing to the bottom line. It is purely risk mitigation.  Along
with license, maintenance and training costs, it is one of the costs of working with commercial
 software.</p>
 <h2 id="open-source-compliance-costs">Open Source Compliance Costs</h2>
 <p>As opposed to commercial EULA-style software licenses, open source software have
licenses that explicitly permit free redistribution.  This reduces the cost of compliance
for many
@@ -39,17 +39,19 @@ organizations.</p>
 of some open source licenses.  If one of your programmers inadvertently includes some copyleft
code into your proprietary product, you could be required to make the source code for
 your entire product freely available to the public.<br />
 </p>
-<p>This is not a theoretical concern.  As aggresively as the BSA, the Software Freedom
Law Center has <a href="http://www.softwarefreedom.org/news/2009/dec/14/busybox-gpl-lawsuit/">gone
after large corporations</a> for GPL licence violations, including 
+<p>This is not 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 <a href="http://www.softwarefreedom.org/news/2009/dec/14/busybox-gpl-lawsuit/">high-profile
lawsuits against large corporations</a>, including 
 Westinghouse, Samsung and Best Buy.</p>
 <p>So the cost of compliance with copyleft code is as bad or 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.  So
more employee education, more approval cycles, more audits, more worries and more risk.  This
-is the increased cost of compliance when copyleft software is brought into an organization.</p>
-<h2 id="advantages-of-the-apache-licence">Advantages of the Apache Licence</h2>
-<p>Not all open source licenses are copyleft licence.  Not all of them have that viral
quality that radically increases the risk for an organization.  A subset of open source licences,
-generally called "permissive" licences, are much friendly for corporate use.  These licences
include the MIT and BSD licences, as well as the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
Software Licence 2.0</a> that we use.</p>
-<p>Like other open source licences, the Apache Licence explicitly allows you to copy
and redistribute the covered product, without any licence fees or royalties.  But because
it is a
-permissive licence, it also allows you to prepare and distribute derivitive products, without
any requirement to make your own source code public.  So both BSA and SFLC risks
-are eliminated.  The cost of licence compliance is drastically reduced.</p>
+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 audits, more worries and more risk. 
This is the increased 
+cost of compliance when copyleft software is brought into an organization.</p>
+<h2 id="advantages-of-the-apache-license">Advantages of the Apache License</h2>
+<p>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 friendly for corporate use.  These licenses
include the MIT and BSD licenses, as well as the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
Software License 2.0</a> that we use.</p>
+<p>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.  The cost of license compliance is drastically reduced.</p>
   </div>
 <!--#include virtual="/footer.html" -->
 </body>



Mime
View raw message