Changeset - 957fff699cf7
[Not reviewed]
0 1 0
Donald Robertson, III - 10 years ago 2014-03-20 20:02:03
donald@fsf.org
FLOSS to free software
1 file changed with 24 insertions and 24 deletions:
0 comments (0 inline, 0 general)
compliance-guide.tex
Show inline comments
...
 
@@ -55,3 +55,3 @@ which holds copyrights in many GNU programs, was the only visible entity
 
actively enforcing its GPL'd copyrights on behalf of the community of
 
Free/Libre and Open Source Software (FOSS) developers.  FSF's enforcement
 
Free/Libre and Open Source Software (free software) developers.  FSF's enforcement
 
was generally a private process; the FSF contacted violators
...
 
@@ -83,3 +83,3 @@ GPL's terms, and poor communication between software developers and their
 
management.  In this document, we highlight these problems and describe
 
best practices to encourage corporate users of FOSS to reevaluate their
 
best practices to encourage corporate users of free software to reevaluate their
 
approach to GPL'd software and avoid future violations.
...
 
@@ -98,3 +98,3 @@ when a violation occurs.
 

	
 
Unlike highly permissive FOSS licenses (such as the ISC license), which
 
Unlike highly permissive free software licenses (such as the ISC license), which
 
typically only require preservation of copyright notices, the GPL places a
...
 
@@ -112,3 +112,3 @@ internal development environment.  In this section, we introduce some best
 
practices for software tool selection, integration and distribution,
 
inspired by and congruent with FOSS methodologies.  We suggest companies
 
inspired by and congruent with free software methodologies.  We suggest companies
 
establish such practices before building a product based on GPL'd
...
 
@@ -141,3 +141,3 @@ resulting unequivocally in a derivative work.  Alongside these programs,
 
companies often distribute fully independent, proprietary programs,
 
developed from scratch, which are designed to run on the FOSS operating
 
developed from scratch, which are designed to run on the free software operating
 
system but do not combine with, link to, modify, or otherwise derive from
...
 
@@ -185,6 +185,6 @@ arrangement and management/legal oversight before the developers
 
incorporate the software.  By contrast, your developers often obtain and
 
integrate FOSS without intervention. The ease of acquisition, however,
 
integrate free software without intervention. The ease of acquisition, however,
 
does not mean the oversight is any less necessary.  Just as your legal
 
and/or management team negotiates terms for inclusion of any proprietary
 
software, they should be involved in all decisions to bring FOSS into your
 
software, they should be involved in all decisions to bring free software into your
 
product.
...
 
@@ -192,4 +192,4 @@ product.
 
Simple, engineering-oriented rules help provide a stable foundation for
 
FOSS integration.  Ask your software developers to send an email to a
 
standard place describing each new FOSS component they add to the system,
 
free software integration.  Ask your software developers to send an email to a
 
standard place describing each new free software component they add to the system,
 
and have them include a brief description of how they will incorporate it
...
 
@@ -205,3 +205,3 @@ difficult.  If you are in that situation, we recommend the
 
\href{http://fossology.org/}{Fossology system}, which analyzes a
 
source-code base and produces a list of FOSS licenses that may apply to
 
source-code base and produces a list of free software licenses that may apply to
 
the code.  Fossology can help you build a catalog of the sources you have
...
 
@@ -620,3 +620,3 @@ programs, including some GPL'd binaries, alongside some proprietary
 
binaries that are separate works (i.e., not derived from, nor based on
 
FOSS sources).  Consider what, in this case, constitutes adequate
 
free software sources).  Consider what, in this case, constitutes adequate
 
``scripts to control compilation and installation'' or items ``needed to
...
 
@@ -663,5 +663,5 @@ Nonetheless, in the interest of goodwill and the spirit of the GPL, most
 
companies do provide the compiler itself when they are able, particularly
 
when the compiler is based on GCC\@ or another FOSS compiler.  If you have
 
when the compiler is based on GCC\@ or another free software compiler.  If you have
 
a GCC-based system, it is your prerogative to redistribute that GCC
 
version (binaries plus sources) to your customers.  We in the FOSS
 
version (binaries plus sources) to your customers.  We in the free software
 
community encourage you to do this, since it often makes it easier for
...
 
@@ -683,3 +683,3 @@ choose not to distribute the compiler, you should include a {\sc readme}
 
about where you got it, what version it was, and who to contact to acquire
 
it, regardless of whether your compiler is FOSS, proprietary, or
 
it, regardless of whether your compiler is free software, proprietary, or
 
internally developed.
...
 
@@ -765,5 +765,5 @@ communications sent by non-reliable means (such as email) were received.
 

	
 
Remember that the FOSS community generally values open communication and
 
Remember that the free software community generally values open communication and
 
cooperation, and these values extend to GPL enforcement.  You will
 
generally find that FOSS developers and their lawyers are willing to
 
generally find that free software developers and their lawyers are willing to
 
have a reasonable dialogue and will work with you to resolve a violation
...
 
@@ -842,3 +842,3 @@ copyright holders often require.
 

	
 
\item {\bf Compliance on all FOSS copyrights}.  Copyright holders of FOSS
 
\item {\bf Compliance on all free software copyrights}.  Copyright holders of free software
 
  often want a company to demonstrate compliance for all GPL'd software in
...
 
@@ -846,3 +846,3 @@ copyright holders often require.
 
  reinstate your right to distribute one program unless and until you
 
  comply with the licenses of all FOSS in your distribution.
 
  comply with the licenses of all free software in your distribution.
 
 
...
 
@@ -856,6 +856,6 @@ copyright holders often require.
 

	
 
\item {\bf Appointment of a GPL Compliance Officer.}  The FOSS community
 
\item {\bf Appointment of a GPL Compliance Officer.}  The free software community
 
  values personal accountability when things go wrong.  Copyright holders
 
  often require that you name someone within the violating company
 
  officially responsible for FOSS license compliance, and that this
 
  officially responsible for free software license compliance, and that this
 
  individual serve as the key public contact for the community when
...
 
@@ -954,3 +954,3 @@ view of the redistributor).
 
Consider the cost of potential violations in your acquisition process.
 
Using FOSS allows software vendors to reduce costs significantly, but be
 
Using free software allows software vendors to reduce costs significantly, but be
 
wary of vendors who have done so without regard for the licenses.  If your
...
 
@@ -990,3 +990,3 @@ notice that they risk voiding their warranties and losing their update and
 
support services when they make modifications.\footnote{A popular t-shirt
 
  in the FOSS community reads: ``I void warranties.''.  Our community is
 
  in the free software community reads: ``I void warranties.''.  Our community is
 
  well-known for modifying products with full knowledge of the
...
 
@@ -1013,3 +1013,3 @@ well-informed and well-coordinated.  The receptionists should know how to
 
route a GPL source request or accusation of infringement.  The lawyers
 
should know the basic provisions of FOSS licenses and your source
 
should know the basic provisions of free software licenses and your source
 
disclosure requirements, and should explain those details to the software
...
 
@@ -1022,3 +1022,3 @@ on target.  With these practices in place, any organization can comply
 
with the GPL without serious effort, and receive the substantial benefits
 
of good citizenship in the FOSS community, and lots of great code
 
of good citizenship in the free software community, and lots of great code
 
ready-made for their products.
0 comments (0 inline, 0 general)