Files @ 4aeb4b25b2f2
Branch filter:

Location: Copyleft/guide/GPL-Business/gpl-business-abstract.txt

bkuhn
compliance-guide.tex was originally downloaded from the following URL:
http://softwarefreedom.org/resources/2008/compliance-guide.tex

Since I am herein committing an Adaptation of this compliance-guide.tex work
(this commit includes a one-line change made from the version as downloaded
above), this is now an Adaptation as defined by CC-By-SA-3.0-Unported §1(a).

I am thus hereby permitted, per CC-By-SA-3.0-Unported §4(b)(ii), to relicense
this work under CC-By-SA-4.0, because CC-By-SA has the same License Elements
as CC-By-SA-3.0-Unported. (Therefore, in this case, §4(b)(ii) defines the
"Applicable License" as CC-By-SA-4.0.)

Specifically, the following license text appears in compliance-guide.tex:

Copyright \copyright{} 2008, Software Freedom Law Center. Licensed
\href{http://creativecommons.org/licenses/by-sa/3.0/us/legalcode}{CC-BY-SA
3.0 unported}.

Here are the actions I took to comply with CC-By-SA-3.0-Unported §4(b)(ii):

§4(b)(I): Since the Applicable License is CC-By-SA-4.0, I've now included
the URI and reference to the copy of CC-By-SA-4.0 in this
repository as well.

§4(b)(II): No additional conditions are imposed.

§4(b)(III): This term is confusing. It claims I must "keep intact all
notices that refer to the Applicable License". Of course, the
Applicable License is now the new version of the license, so it
seems reasonable to interpret this clause as to allow, and
almost instruct, a change in reference to the 3.0 license to
the 4.0 license. However, that's not explicitly allowed for in
this section, but I can't come to any reasonable interpretation
of the clause other than updating the notice to refer to the
new license.

§4(b)(IV): No technological measures are imposed.
     The GNU General Public License for Developers and Businesspeople
     ----------------------------------------------------------------

This tutorial gives a section-by-section explanation of the most popular
Free Software copyright license, the GNU General Public License (GNU GPL),
and teaches software developers, managers and businesspeople how to use
the GPL and GPL'ed software successfully in new Free Software business and
in existing, successful enterprises.

Attendees should have a general familiarity with software development
processes.  A vague understanding of how copyright law applies to software
is also helpful.  The tutorial is of most interest to software developers
and managers who run software businesses that modify and/or redistribute
software under terms of the GNU GPL (or who wish to do so in the future),
and those who wish to make use of existing GPL'ed software in their
enterprise.

This is not a legal tutorial.  By contrast, it explains the GNU GPL to
professionals who are not well versed in the details of copyright law.
Presented by a software developer and manager, this tutorial informs
non-lawyers who wish to have a deeper understanding of how the GNU GPL
uses copyright law to protect software freedom and to assist in the
formation of Free Software businesses.

Upon completion of the tutorial, successful attendees can expect to have
learned:

    * the freedom-defending purpose of each term of the GNU GPL

    * the redistribution options under the GPL

    * the obligations when modifying GPL'ed software

    * how to properly apply the GPL to a new software

    * how to build a plan for proper and successful compliance with the GPL

    * the business advantages that the GPL provides

    * the most common business models used in conjunction with the GPL

    * how existing GPL'ed software can be used in existing enterprises
 
The full tutorial take three hours, with time for plenty of questions and
two fifteen minute breaks.  An abbreviated one-hour talk that introduces
the the issues covered in the full tutorial is also an option.