Copyleft/guide Changeset - 485d11494758

Changeset - 485d11494758

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Bradley Kuhn (bkuhn) - 10 years ago 2014-03-24 09:58:35
bkuhn@ebb.org

Fix the quote here.

1 file changed with 2 insertions and 2 deletions:

presentations/1hr-GPL/1hr-GPL.markdown

0 comments (0 inline, 0 general)

presentations/1hr-GPL/1hr-GPL.markdown

➞

Show inline comments

@@ ... / @@ -35,140 +35,140 @@ @@
     + Holder of copyrights on many key GNU programs &hellip;
     + &hellip; and therefore enforcers of those copyrights.
 + Software Freedom Conservancy
     + Adviser on legal issues of copyright, etc. to Free Software projects.
     + Holder of some copyrights on its member projects.
     + Enforcer of GPL on behalf of many copyright holders in:
     + BusyBox, Samba, Mercurial, and the kernel named Linux.
 # How this Hour Will Go?
 + Materials presented will mix the simple &amp; complex.
 + We cannot possibly cover the entire GPL in one hour.
 + Discuss: motivations, origins, then a few of GPL's sections.
 + I understand the mix of backgrounds in the audience.
 # A Restaurant's Lawyer?
 + Considering why you want to learn this.
 + What if your client was a restaurant?
 + What would you want to need to know?
 # Restaurant Lawyer: What'd You Study?
 + If you were a restaurant's lawyer:
 + Probably three areas of law you'd focus on:
      + building codes.
      + health and safety regulations.
      + tax regulations.
 + Who would want to hear from?
 # Restaurant Lawyer: What'd You Study?
 + Figure out the motivations behind the building code:
       + What parts are arcane and less important to inspectors?
       + How do inspections work?
       + What are the penalties?
 + Figure out the same for health &amp; safety:
       + Who inspects, and when?
       + What's the health code say, and what checklist do inspectors use?
 + Likely Questions:
       + Who's in charge of all this?
       + What's purpose and intent of these regulations?
       + Can I meet the inspectors?
 # Why Listen To Us?
 + FSF: Understanding the purpose and intent of the GPL.
 + Conservancy &amp; FSF:
     + both enforce the GPL.
     + if your client violates, you will hear from one of us.
 + Such access to drafters, interpreters, enforcers is highly unique.
 + Someday, we may (or already have) sit across the table from you.
 + Our transparency does make your job easier.
 # The Mindset of GPL
 + GPL protects software freedom.
 + Ultimate goal: make sure every user has the four freedoms.
      + Freedom to run the software.
      + Freedom to study and modify the software.
      + Freedom to share the software.
      + Freedom to distribute modified versions.
 + Every clause in GPL was designed to uphold one of these freedoms.
      + Or, it's a compromise of drafting in adoption vs. freedom debate.
 # Using Copyright
 + GPL is primarily a copyright license.
       + Software is copyrighted.
       + License grants key freedoms.
       + Requirement prohibit activities that take away freedoms.
 + General concept: copyleft.
 + Specific implementation: GPL.
 <hr/>
 <span class="fitonslide">
-> an original works of authorship fixed in any tangible medium of expression &hellip;  from which they can be perceived, reproduced, or otherwise communicated, either directly or with the aid of a machine or device
+> Copyright protection subsists &hellip; original works of authorship fixed in any tangible medium of expression &hellip;  from which they can be perceived, reproduced, or otherwise communicated, either directly or with the aid of a machine or device.
 <p align=right>
- &mdash; 17 USC \S~102
+ &mdash; <a href="http://www.law.cornell.edu/uscode/text/17/102">17 USC &sect;102</a>
 </p>
 </span>
 # Conditional Permissions
 + A copyleft license grants copyright permissions, conditionally.
 + Think of the phrase: &ldquo;provided that&rdquo;
 + &ldquo;provided that&rdquo;: appears (in some form) only
 + 4 times in GPLv2
 + 9 times in GPLv3.
 # Compare To Proprietary Licenses
 + Yes, the GPL has its requirements.
 + But *none* of these activities are ever permitted under proprietary
   licenses.
 + If you don't like what the GPL requires you to do, then just tell your
   client to use the proprietary software instead.
 + That way, they know the answer to every question is &ldquo;no&;rdquo,
 + rather than: &ldquo;yes, but only as long as you &hellip;&rdquo;
 # The Technical Gap
 + Understanding GPL well requires a some software expertise &amp; legal
   expertise.
 + You don't have to be a professional on either side to grok it.
      + but you're best off if you're a professional in one &amp; an amateur
        in the other.
 + Most important technical concepts you need:
      + source code, binaries, methods of distribution.

0 comments (0 inline, 0 general)