\logo{\includegraphics[width=2cm]{openlogo.pdf}} \author{Don Armstrong} \title{GPLv3 and Debian} \date{\ } \titlegraphic{\includegraphics{openlogo-crop.pdf}} \subject{GPLv3 and Debian} %\mode{ % \AtBeginSubsection[] % { % \begin{frame} % \frametitle{Outline} % \tableofcontents % \end{frame} % } %} \newcommand{\cdotgpl}{ current draft of the GPLv3 } \newcommand{\CCSC}{ Complete Corresponding Source Code } \newcommand{\gplcite}[2]{% (\textsection #1~\textparagraph #2)% } \begin{document} \mode
{\maketitle} %\setbeamercolor{frametitle}[bg=-red!90!green!10,fg=black] \begin{frame} \titlepage \end{frame} \begin{frame} \frametitle{GPLv3 And Debian} \tableofcontents % You might wish to add the option [pausesections] \end{frame} \section{Introduction} \begin{frame} \frametitle{Introduction} \mode{ \begin{itemize}[<+->] \item Historic Process \begin{itemize} \item Software in Debian under GPL \item Free Software Community in General \end{itemize} \item Important to Debian, and us individually \item Process, Review, Issues \end{itemize} } \end{frame} For the remainder of the year, we have an opportunity to participate in a historic process that affects a large part of the software in Debian, as well as the greater Free Software community. During this calendar year, the FSF is working on drafting a revision of the GNU Public License, and you all are an important part of that process. The current draft has changed many things, and it's quite likely that the subsequent drafts will contain more changes that affect the way that works under the GPLv3 are able to be used. We will attempt in this paper to discuss the process behind the adoption of a GPLv3, that is, how changes to the current draft are going to be suggested, commented upon, stewarded, and made, the changes and the rationale behind the changes that have been made in the current draft of the GPLv3 and the GPLv2, and finally a non-exhaustive look at some of the major issues which have been identified with the current draft. \section{Drafting and Community Review Process} \begin{frame} \frametitle{Review} \mode{ \begin{itemize}[<+->] \item Community \item Committees \item RMS \end{itemize} } \end{frame} The drafting and review process has three important components which are going to interact together to result in subsequent drafts and eventually the final revision of the GPL version 3. These three components are the community at large, four committees made up of community members, and Richard M. Stallman (with the assistance of Eben Moglen and others at the SFLC.) \subsection{Community} \begin{frame} \frametitle{Community} \mode{ \begin{itemize}[<+->] \item Everyone \item Make comments on the draft \item Make suggestions on how to fix problems \item Advise committees where appropriate \end{itemize} } \end{frame} The Free Software community (that includes you if you're reading this) is responsible for reviewing the various drafts of the GPL and making comments about the changes that have been made to the GPL (or even comments about things that haven't been changed, but possibly should have been.) The comments are made currently using a web based application at gplv3.fsf.org, and at the time I'm writing this a few thousand comments have been made. (In fact, almost no substantive portion of the license has not been commented upon.) Hopefully, the community will be able to identify most of the serious issues with each of the revisions of the license, and begin to identify ways that the license can be changed (if necessary) or at the very least identify areas that need change or clarification. Since the community includes not only Free Software developers like yourselves, but attorneys who are either developers or users in their own right spread throughout many of the legal systems on the planet, it's quite likely that at least the obvious issues will be discovered and fixed. (Ideally by the sheer application of many eyeballs even the less obvious issues will be noticed and addressed.) \subsection{Committee} \begin{frame} \frametitle{Committee} \mode{ \begin{itemize}[<+->] \item Five Committees \begin{itemize}[<+->] \item Distributions\footnote{Branden Robinson and Greg Pomerantz} \item Projects \item Companies \item Randoms\footnote{Don Armstrong and Mako Hill} \item International \end{itemize} \item Identify issues from comments \item Steward issues, and make recommendations \end{itemize} } \end{frame} Five committees, four of which were organized at the first GPLv3 conference at MIT in January have been formed. Branden Robinson, Greg Pomerantz, Mako Hill, and Don Armstrong are project members who are also on these committees. Each of the committees was free to organize itself as it wished, although representatives from the FSF acted as guides throughout the process to keep the committees on track and on task. The committee's primary responsibility is to examine the comments that are made by the community, group the comments into issues, and then make recommendations based upon the comments to resolve the issues that have been raised. For example, members of Committee D have been examining all of the comments that have been made on the GPL and assigning them to different categories based on personal assessment. Groups that are made by each member are then brought forward at the weekly meetings in IRC (\#committeed on irc.freenode.net at 22:00 UTC on Tuesday) and if the members agree, are made issues, and someone volunteers to steward the issue. Once an issue is identified, discussion on the issue occurs in committee, and if necessary, more comments/suggestions are made in the commenting system which are included. If changes are required to the GPL to resolve the issue, those changes are also made and discussed. Finally, assuming the members of the committee agree, a final position paper can be made, and the committee can submit the issue for consideration by RMS. \subsection{RMS} \begin{frame} \frametitle[RMS]{Richard M. Stallman (and friends)} \mode{ \begin{itemize}[<+->] \item Responsible for the original draft \item Weigh recommendations/statements from committees \item Make changes to the license for the next draft \end{itemize} } \end{frame} Richard M. Stallman is serving as the final arbitrator of changes that are made to the GPL. The committees will be presenting cases for any changes that need to be made to the license, and RMS will be weighing them, and making a final determination on them. RMS will of course be working in close concert with the FSF's legal representation, so Eben Moglen and the SFLC will also play a role in this part of the process. In the course of the next year, RMS will be involved in publishing two to three drafts of the GPL, culminating at the end of the calendar year in a new version of the GPL, one that the Free Software community in general is content with and willing to license its works under. \section{Overview of the Current Draft} \begin{frame} \frametitle{Current Draft} \mode{ \begin{itemize}[<+->] \item Major changes \item DRM Clause (\textsection 1 \& \textsection 3) \item License Compatibility \item Patent Licensing \end{itemize} } \end{frame} The \cdotgpl changes quite a few things from version 2. We'll discuss some of the more obvious changes here and retread the FSF's rationale for each of the changes that we discuss. We will withhold discussion of the issues that these changes have raised (and other pre-existing issues) for section \ref{sect:open_issues}. % DRM Clauses \subsection{Digital Restrictions Management} \begin{frame} \frametitle{TiVo-ization} \mode{ \begin{itemize}[<+->] \item Using DRM to block modification \item Cryptographic keys in hardware employed \item Software not signed by key doesn't get loaded \item \CCSC definnition clarified to include these codes (\textsection \hyperlink{section1ccsc}{1}) \end{itemize} } \end{frame} The \cdotgpl includes a clause~\gplcite{1}{2} which resolves a possible loophole with the GPL version 2, whereby a distributor could distribute the source code to a program, but restrict the ability of anyone else to make modifications to the program by the means of cryptographic keys or similar to either lock the hardware, or block interoperability between programs. Additionally, it was possible to restrict the output of a work to being unlocked using a specific set of keys (or a specific vetted viewer which was closed source.) This clause requires that these keys be provided as part of the \CCSC. In addition to specifically requiring certain keys, the \cdotgpl indicates that the license should be interpreted in a manner that disallows attempts to restrict users' freedom.\gplcite{3}{1} This clause also disallows the distribution of ``covered works that illegally invade users' privacy''\footnote{We'll discuss the problems with this particular clause in greater deal in section \ref{sect:disallow_illegal_things} on page \pageref{sect:disallow_illegal_things}} The current draft also indicates~\gplcite{3}{2} that covered works do not constitute part of an effective technological protection method in an attempt to obviate DMCA protection for GPLed works. \subsection{License Compatibility} \begin{frame} \frametitle{Current Draft} \mode{ \begin{itemize}[<+->] \item Explicit BSD Compatibility (\textsection \hyperlink{section7a}{7a}) \item Different Warranty Disclaimer (\textsection \hyperlink{section7b}{7b}) \item Prohibit use of names/trademarks for publicity outside of fair use (\textsection \hyperlink{section7c}{7c}) \item Affero Compatibility (\textsection \hyperlink{section7d}{7d}) \item Software Retaliation compatibility (\textsection \hyperlink{section7e}{7e}) \end{itemize} } \end{frame} % License Compatibility clauses A whole set of clauses were added to the \cdotgpl to attempt to increase the compatibility between the GPL and other free software licenses. The first three of these clauses primarily deals with explicit compatibility with BSD-like licenses~\gplcite{7}{4--6}; as the GPL has long been considered to be compatible with the 3-clause BSD,\footnote{That is to say the BSD license which does not have the advertising clause} this just makes the compatibility explicit. The next clause~\gplcite{7}{7} makes the \cdotgpl compatible with the Affero Public License. In other words, it allows the license to require ``functioning facilities that allow users to immediately obtain copies of its Complete Corresponding Source Code.'' \begin{frame} \frametitle{Affero Clause (\textsection \hyperlink{section7d}{7d})} \mode{ \begin{itemize}[<+->] \item ASP Business Model \item Compatibility with AGPL \item Currently Implemented as a Restriction on Modification \end{itemize} } \end{frame} The final clause in this section allows for compatibility with licenses that impose a limited set of patent retaliation terms.~\gplcite{7}{8} Briefly, it allows licenses to revoke permission for use of added parts wholly or partially upon the initiation of a software patent lawsuit, so long as the lawsuit is not retaliating against another software patent lawsuit and the lawsuit specifically targets part of the covered work. \begin{frame} \frametitle{Limited Patent Reciprocity Compatibility (\textsection \hyperlink{section7e}{7e})} \mode{ \begin{itemize}[<+->] \item Counterclaims against agressors must be allowed \item Revoks agressors who claim patent infringement in the covered work \end{itemize} } \end{frame} \subsection{Patent Licensing} Software patents are, unfortunatly, a serious problem that we people in many jurisdictions have been forced to deal with. The \cdotgpl deals with this in a few ways; first the traditional automatic licensing of downstream users survives, with the explicit allowal of patent retaliation restrictions, in all activities allowed by the license, including modified versions of the work. Secondly, the \cdotgpl requires that patent holders who are immune from suits under patent because they have a patent license must act to shield downstream users against possible patent infringment claims which their patent license protects them.\gplcite{11}{2} \subsection{Other Minor Changes} \begin{frame} \frametitle{Other Minor Changes} \mode{ \begin{itemize} \item Removal of the Geographical Limitations \item Explicit indication that it's not a contract (\textsection \hyperlink{section9}{9}) \end{itemize} }\end{frame} \section{Open Issues with the Current Draft} \begin{frame} \frametitle{Open Issues} \mode{ \begin{itemize}[<+->] \item Digital Rights Management \item Treacherous Computing \item Affero Clause (ASP loophole) \item Possible change to be compliance with \textsection 6 \item Patents \item GPL as Free Software \end{itemize} } \end{frame} \label{sect:open_issues} \subsection{Digital Restrictions Management} The current wording of the sections on Digital Restrictions Management has caused a bit of consternation in many camps, including Linus Torvald's rather tepid reception of v3. First and foremost, it appears that the GPLv3 as written requires distributors to provide the keys used to sign a work, just like we do in Debian in order to help users assure that the code that they are installing is actualy the code that we have distributed to them. There are ways to interpret the language as written to not require this, but they are not as straightforward as one would like. Additionally, it appears to require that API keys which are used to uniquely identify the user of a work for billing or bandwidth/resource limitation purposes be provided along with the work. These were most likely not intended, and are merely an artifact of the very complex nature of trying to preserve user's freedom, while granting them the ability to do everything that they wish to do. \begin{frame} \frametitle{DRM And Authentication} \mode{ \begin{itemize}[<+->] \item Prevent TiVo-ization \item Require Keys necessary to update the device \item Appears to provide API keys and signing keys \end{itemize} } \end{frame} \label{sect:disallow_illegal_things} Secondly, the current clauses on DRM as written disallow the illegal invasion of user's privacy. This appears to have been included as a response to the Sony DRM debacle, and a desire to be able to go after people who illegally violate others privacy with a larger stick than the criminal laws in various jurisdictions currently afford. Unfortunatly, restricting users from performing specific sets of actions almost definetly contravenes DFSG \textsection 6\footnote{``The license must not restrict anyone from making use of the program in a specific field of endeavor.''} and more importantly, it doesn't do anything to solve the more serious problem of invasion of user's privacy where it is the government itself that is doing the invasion. Hopefully this clause, while well meaning, will be removed from the second draft of the GPLv3. \begin{frame} \frametitle{Disallowing Illegal Things} \mode{ \begin{itemize}[<+->] \item No illegal invasions of user's privacy (\textsection \hyperlink{section3illegal}{3}) \item Connection to Sony DRM debacle \item Conflict with DFSG \textsection 6 (Anti-``no nuke clause'') \end{itemize} } \end{frame} A final issue with this section comes from the anti-DMCA clause of the \cdotgpl\gplcite{3}{2}. This clause has caused a bit of confusion in various people not familiar with the DMCA and the provisions provided for within. Additionally, it's not clear whether the clause will actually be able to keep a covered work from activating that clause of the DMCA, as very little case law exists in this area. Of course, at worst case, this clause will just become a confusing null-op, in the optimal case it may actually do some good. \begin{frame} \frametitle{anti-DMCA Clause} \mode{ \begin{itemize}[<+->] \item Notification that the work is not an effective method of copyright control (\textsection \hyperlink{section3antidmca}{3}) \item Explicitely disallows the extra protection of the DMCA \end{itemize} } \end{frame} \subsection{Affero Clause} A more contentious clause is in \textsection 7d, the Affero compatibility clause. Briefly, the Affero compatibility clause is an attempt to close the ASP loophole; the ASP loophole being the ability of application service providers to use a GPLed work and make modifications to it without providing the source code to the modifications to their users and/or the community in general. The clause does this by implementing a restriction on modification by requiring the work to maintain a facility to allow users to immediately download the complete corresponding source code to the work. Obstensibly, such a restriction on modification fails the most expansive readings of DFSG \textsection 3; and likewise has problems with Freedom Zero, the freedom to study a program and make modifications to it for any purpose. It also causes problems where a bug in this mechanism could place you in violation of the license, and precludes using code with this restriction in areas where the immediate download of \CCSC is impossible. That being said, the use of ASPs to lock users out of being able to modify their own software is a serious problem that we are going to have to resolve in one way or another, either through software licensing like this, or by users not accepting that computing model. \begin{frame} \frametitle{Affero Clause (The ASP Loophole)} \mode{ \begin{itemize}[<+->] \item Currently written as a restriction on modification, with obvious issues \item May not be possible to implement and retain compliance with the DFSG at all \item Reasonable compromise may be to require non-private use (performance?) satisfy (\textsection \hyperlink{section6}{6}) \end{itemize} } \end{frame} \subsection{Patents} \begin{frame} \frametitle{Patents} \mode{ \begin{itemize}[<+->] \item Explicit patent grants (vs. Implicit) \item Patent Shielding \item Limited Patent Reciprocity \end{itemize} } \end{frame} Software patents are, as those of you have been following the machinations of the EU in this issue know, the night stalker of the entire software world. Basically, if you're not a big player with a few thousand software patents, or an entity whose entire purpose is to litigate patents and not actually make software you're going to be affected by software patents some day. Already there is software in Debian which is likely DFSG free, but we are not able to distribute because of the likelihood of becoming the subject of patent lawsuits. In an attempt to combat this, the GPL has always had a clause which caused patent licenses to flow from the licensee to the licenseor. The addition of the patent shield now forces larger companies with diverse patent portfolios and cross licensing agreements to act to shield downstream users from the possibility of patent lawsuits when their licensing agreements protect them. \subsection{GPL as Free Software} A long time issue is the fact that the GPL itself cannot be modified. The reasons behind disallowing this modification typically boil down to a desire to restrict license proliferation. However, given the interpretation by the FSF that the only part of the license that must be removed from the license if the license is modified is the preamble, it seems that any license proliferation prohibition has been virtually eliminated. Given the sheer number of people who are working on the GPLv3 and the number of issues that have been raised, it seems that no one should take writing a software license or modifying an existing one lightly. In that light, the lack of modifiability to the GPL has not been altogether too important. However, it seems reasonable that we should apply the same philosophy to as many of the works as possible that we, as members of the Free Software community, create. Not that someone should modify the GPL, but just so we are philosophically consistent when we request others to join our community. \section{Conclusion} We're now 5 months into the process to draft the GPLv3; that means we've got less than 7 months left to suggest any changes to the new version of the draft that we can. If you haven't yet, you should take some time and read over the \cdotgpl, and make sure that it protects the freedoms that you feel are important to have as a member of the Free Software Community. Don't take our word for what the changes, problems, and rationale are for the \cdotgpl; think about them, and comment on them too! \begin{frame} \frametitle{Conclusion} \mode{ \begin{itemize} \item Participate \item Don't believe anything I've said; analyze it for yourself. \item Do it soon \end{itemize} } \end{frame} \mode{ \section{Current Draft of the GPLv3} \begin{frame} \frametitle{Preamble: Purpose} The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other program whose authors commit to using it. (Some Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. \end{frame} \begin{frame} \frametitle{Preamble: Freedom} When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. \end{frame} \begin{frame} \frametitle{Preamble: Requirements} To protect your rights, we need to make requirements that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. \end{frame} \begin{frame} \frametitle{Preamble: Giving Rights} For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. \end{frame} \begin{frame} \frametitle{Preamble: Developer Protection} Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software. \end{frame} \begin{frame} \frametitle{Preamble: No Warranty} For the developers' and author's protection, the GPL clearly explains that there is no warranty for this free software. If the software is modified by someone else and passed on, the GPL ensures that recipients are told that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. \end{frame} \begin{frame} \frametitle{Preamble: DRM Prohibition} Some countries have adopted laws prohibiting software that enables users to escape from Digital Restrictions Management. DRM is fundamentally incompatible with the purpose of the GPL, which is to protect users' freedom; therefore, the GPL ensures that the software it covers will neither be subject to, nor subject other works to, digital restrictions from which escape is forbidden. \end{frame} \begin{frame} \frametitle{Preamble: Software Patents} Finally, every program is threatened constantly by software patents. We wish to avoid the special danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, the GPL makes it clear that any patent must be licensed for everyone's free use or not licensed at all. \end{frame} \begin{frame} \frametitle{Preamble: Terms follow} The precise terms and conditions for copying, distribution and modification follow. \end{frame} \begin{frame} \frametitle{0. Definitions} A "licensed program" means any program or other work distributed under this License. The "Program" refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either modified or unmodified. Throughout this License, the term "modification" includes, without limitation, translation and extension. A "covered work" means either the Program or any work based on the Program. Each licensee is addressed as "you". \end{frame} \begin{frame} \frametitle{0. Definitions: Propogation} To "propagate" a work means doing anything with it that requires permission under applicable copyright law, other than executing it on a computer or making private modifications. This includes copying, distribution (with or without modification), sublicensing, and in some countries other activities as well. \end{frame} \begin{frame} \frametitle{1. Source Code} 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source version of a work. \end{frame} \begin{frame} \frametitle{1. Source Code: CCSC} The "Complete Corresponding Source Code" for a work in object code form means all the source code needed to understand, adapt, modify, compile, link, install, and run the work, excluding general-purpose tools used in performing those activities but which are not part of the work. For example, this includes any scripts used to control those activities, and any shared libraries and dynamically linked subprograms that the work is designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work, and interface definition files associated with the program source files. \end{frame} \begin{frame} \frametitle{1. Source Code: CCSC (DRM)} \label{section1ccsc} Complete Corresponding Source Code also includes any encryption or authorization codes necessary to install and/or execute the source code of the work, perhaps modified by you, in the recommended or principal context of use, such that its functioning in all circumstances is identical to that of the work, except as altered by your modifications. It also includes any decryption codes necessary to access or unseal the work's output. Notwithstanding this, a code need not be included in cases where use of the work normally implies the user already has it. \end{frame} \begin{frame} \frametitle{1. Source Code: CCSC (Autogen bits)} Complete Corresponding Source Code need not include anything that users can regenerate automatically from other parts of the Complete Corresponding Source Code. \end{frame} \begin{frame} \frametitle{1. Source Code: OS Exemption} As a special exception, the Complete Corresponding Source Code need not include a particular subunit if (a) the identical subunit is normally included as an adjunct in the distribution of either a major essential component (kernel, window system, and so on) of the operating system on which the executable runs or a compiler used to produce the executable or an object code interpreter used to run it, and (b) the subunit (aside from possible incidental extensions) serves only to enable use of the work with that system component or compiler or interpreter, or to implement a widely used or standard interface, the implementation of which requires no patent license not already generally available for software under this License. \end{frame} \begin{frame} \frametitle{2. Permissions} 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the Program. The output from running it is covered by this License only if the output, given its content, constitutes a work based on the Program. This License acknowledges your rights of "fair use" or other equivalent, as provided by copyright law. \end{frame} \begin{frame} \frametitle{2. Permissions: Private Modification} This License gives unlimited permission to privately modify and run the Program, provided you do not bring suit for patent infringement against anyone for making, using or distributing their own works based on the Program. \end{frame} \begin{frame} \frametitle{2. Permissions: Private Copying} Propagation of covered works is permitted without limitation provided it does not enable parties other than you to make or receive copies. Propagation which does enable them to do so is permitted, as "distribution", under the conditions of sections 4-6 below. \end{frame} \begin{frame} \frametitle{3. DRM: Illegal Invasion} 3. Digital Restrictions Management. \label{section3illegal} As a free software license, this License intrinsically disfavors technical attempts to restrict users' freedom to copy, modify, and share copyrighted works. Each of its provisions shall be interpreted in light of this specific declaration of the licensor's intent. Regardless of any other provision of this License, no permission is given to distribute covered works that illegally invade users' privacy, nor for modes of distribution that deny users that run covered works the full exercise of the legal rights granted by this License. \end{frame} \begin{frame} \frametitle{3. DRM: Anti DMCA Clause} \label{seciton3antidmca} No covered work constitutes part of an effective technological protection measure: that is to say, distribution of a covered work as part of a system to generate or access certain data constitutes general permission at least for development, distribution and use, under this License, of other software capable of accessing the same data. \end{frame} \begin{frame} \frametitle{4. Verbatim Copying} 4.[1] Verbatim Copying. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all license notices and notices of the absence of any warranty; give all recipients of the Program a copy of this License along with the Program; and obey any additional terms present on parts of the Program in accord with section 7. \end{frame} \begin{frame} \frametitle{4. Verbatim Copying: Copy/Warranty for a fee} You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection for a fee. \end{frame} \begin{frame} \frametitle{5. Distributing Modified Versions} 5.[2] Distributing Modified Source Versions. Having modified a copy of the Program under the conditions of section 2, thus forming a work based on the Program, you may copy and distribute such modifications or work in the form of source code under the terms of Section 4 above, provided that you also meet all of these conditions: \end{frame} \begin{frame} \frametitle{5a: Prominent Notices} a) The modified work must carry prominent notices stating that you changed the work and the date of any change. \end{frame} \begin{frame} \frametitle{5b: License applies to the whole work} b) You must license the entire modified work, as a whole, under this License to anyone who comes into possession of a copy. This License must apply, unmodified except as permitted by section 7 below, to the whole of the work. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. \end{frame} \begin{frame} \frametitle{5c: Appropriate Copyright Notice} c) If the modified work has interactive user interfaces, each must include a convenient feature that displays an appropriate copyright notice, and tells the user that there is no warranty for the program (or that you provide a warranty), that users may redistribute the modified work under these conditions, and how to view a copy of this License together with the central list (if any) of other terms in accord with section 7. If the interface presents a list of user commands or options, such as a menu, a command to display this information must be prominent in the list. Otherwise, the modified work must display this information at startup--except in the case that the Program has such interactive modes and does not display this information at startup. \end{frame} \begin{frame} \frametitle{5: Whole work, but can be separated} These requirements apply to the modified work as a whole. If identifiable sections of that work, added by you, are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works for use not in combination with the Program. But when you distribute the same sections for use in combination with covered works, no matter in what form such combination occurs, the whole of the combination must be licensed under this License, whose permissions for other licensees extend to the entire whole, and thus to every part of the whole. Your sections may carry other terms as part of this combination in limited ways, described in section 7. \end{frame} \begin{frame} \frametitle{5: Whole work and your rights} Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. \end{frame} \begin{frame} \frametitle{5: Aggregation} A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. Mere inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. \end{frame} \begin{frame} \frametitle{6: Non-Source Distributions} 6.[3] Non-Source Distribution. \label{section6} You may copy and distribute a covered work in Object Code form under the terms of Sections 4 and 5, provided that you also distribute the machine-readable Complete Corresponding Source Code (herein the "Corresponding Source") under the terms of this License, in one of these ways: \end{frame} \begin{frame} \frametitle{6a: Source Accompanying} a) Distribute the Object Code in a physical product (including a physical distribution medium), accompanied by the Corresponding Source distributed on a durable physical medium customarily used for software interchange; or, \end{frame} \begin{frame} \frametitle{6b: Written Offer Accompanying} b) Distribute the Object Code in a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give any third party, for a price no more than ten times your cost of physically performing source distribution, a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange; or, \end{frame} \begin{frame} \frametitle{6c: Private distribution of WO Copy} c) Privately distribute the Object Code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only for occasional noncommercial distribution, and only if you received the Object Code with such an offer, in accord with Subsection b above. Or, \end{frame} \begin{frame} \frametitle{6d: Distribute by copying from a place} d) Distribute the Object Code by offering access to copy it from a designated place, and offer equivalent access to copy the Corresponding Source in the same way through the same place. You need not require recipients to copy the Corresponding Source along with the Object Code. \end{frame} \begin{frame} \frametitle{6d can be satisfied by separate servers} [If the place to copy the Object Code is a network server, the Corresponding Source may be on a different server that supports equivalent copying facilities, provided you have explicitly arranged with the operator of that server to keep the Corresponding Source available for as long as needed to satisfy these requirements, and provided you maintain clear directions next to the Object Code saying where to find the Corresponding Source.] \end{frame} \begin{frame} \frametitle{6: Must be possible to actually use the source.} Distribution of the Corresponding Source in accord with this section must be in a format that is publicly documented, unencumbered by patents, and must require no special password or key for unpacking, reading or copying. \end{frame} \begin{frame} \frametitle{6: Bits under section 7 may be included} The Corresponding Source may include portions which do not formally state this License as their license, but qualify under section 7 for inclusion in a work under this License. \end{frame} \begin{frame} \frametitle{7. License Compatibility} 7. License Compatibility. When you release a work based on the Program, you may include your own terms covering added parts for which you have, or can give, appropriate copyright permission, as long as those terms clearly permit all the activities that this License permits, or permit usage or relicensing under this License. Your terms may be written separately or may be this License plus additional written permission. If you so license your own added parts, those parts may be used separately under your terms, but the entire work remains under this License. Those who copy the work, or works based on it, must preserve your terms just as they must preserve this License, as long as any substantial portion of the parts they apply to are present. \end{frame} \begin{frame} \frametitle{Limited additional restrictions} Aside from additional permissions, your terms may add limited kinds of additional requirements on your added parts, as follows: \end{frame} \begin{frame} \label{section7a} \frametitle{7a: Preservation of copyright notices} a) They may require the preservation of certain copyright notices, other legal notices, and/or author attributions, and may require that the origin of the parts they cover not be misrepresented, and/or that altered versions of them be marked in the source code, or marked there in specific reasonable ways, as different from the original version. \end{frame} \begin{frame} \label{section7b} \frametitle{7b: Different Warranty disclaimer} b) They may state a disclaimer of warranty and liability in terms different from those used in this License. \end{frame} \begin{frame} \label{section7c} \frametitle{7c: Restrictions on trademark usage} c) They may prohibit or limit the use for publicity purposes of specified names of contributors, and they may require that certain specified trademarks be used for publicity purposes only in the ways that are fair use under trademark law except with express permission. \end{frame} \begin{frame} \label{section7d} \frametitle{7d: Affero Clause} d) They may require that the work contain functioning facilities that allow users to immediately obtain copies of its Complete Corresponding Source Code. \end{frame} \begin{frame} \frametitle{7e: Patent Retaliation} e) They may impose software patent retaliation, which means permission for use of your added parts terminates or may be terminated, wholly or partially, under stated conditions, for users closely related to any party that has filed a software patent lawsuit (i.e., a lawsuit alleging that some software infringes a patent). The conditions must limit retaliation to a subset of these two cases: 1. Lawsuits that lack the justification of retaliating against other software patent lawsuits that lack such justification. 2. Lawsuits that target part of this work, or other code that was elsewhere released together with the parts you added, the whole being under the terms used here for those parts. \end{frame} \begin{frame} \frametitle{7: No additional restrictions permitted} No other additional conditions are permitted in your terms; therefore, no other conditions can be present on any work that uses this License. This License does not attempt to enforce your terms, or assert that they are valid or enforceable by you; it simply does not prohibit you from employing them. \end{frame} \begin{frame} \frametitle{7: Others need not include your permissions} When others modify the work, if they modify your parts of it, they may release such parts of their versions under this License without additional permissions, by including notice to that effect, or by deleting the notice that gives specific permissions in addition to this License. Then any broader permissions granted by your terms which are not granted by this License will not apply to their modifications, or to the modified versions of your parts resulting from their modifications. However, the specific requirements of your terms will still apply to whatever was derived from your added parts. \end{frame} \begin{frame} \frametitle{7: Other terms most be listed centrally} Unless the work also permits distribution under a previous version of this License, all the other terms included in the work under this section must be listed, together, in a central list in the work. \end{frame} \begin{frame} \frametitle{8. Termination} 8.[4] Termination. You may not propagate, modify or sublicense the Program except as expressly provided under this License. Any attempt otherwise to propagate, modify or sublicense the Program is void, and any copyright holder may terminate your rights under this License at any time after having notified you of the violation by any reasonable means within 60 days of any occurrence. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as they remain in full compliance. \end{frame} \begin{frame} \frametitle{9. Not A Contract} \label{section9} 9.[5] Not a Contract. You are not required to accept this License in order to receive a copy of the Program. However, nothing else grants you permission to propagate or modify the Program or any covered works. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating the Program (or any covered work), you indicate your acceptance of this License to do so, and all its terms and conditions. \end{frame} \begin{frame} \frametitle{10. Automatic licensing of downstream users} 10.[6] Automatic Licensing of Downstream Users. Each time you redistribute a covered work, the recipient automatically receives a license from the original licensors, to propagate and modify that work, subject to this License, including any additional terms introduced through section 7. You may not impose any further restrictions on the recipients' exercise of the rights thus granted or affirmed, except (when modifying the work) in the limited ways permitted by section 7. You are not responsible for enforcing compliance by third parties to this License. \end{frame} \begin{frame} \frametitle{11. Licensing of Patents} 11. Licensing of Patents. When you distribute a covered work, you grant a patent license to the recipient, and to anyone that receives any version of the work, permitting, for any and all versions of the covered work, all activities allowed or contemplated by this License, such as installing, running and distributing versions of the work, and using their output. This patent license is nonexclusive, royalty-free and worldwide, and covers all patent claims you control or have the right to sublicense, at the time you distribute the covered work or in the future, that would be infringed or violated by the covered work or any reasonably contemplated use of the covered work. \end{frame} \begin{frame} \frametitle{11: Patent Shield} If you distribute a covered work knowingly relying on a patent license, you must act to shield downstream users against the possible patent infringement claims from which your license protects you. \end{frame} \begin{frame} \frametitle{12. Liberty or Death for the Program} 12.[7] Liberty or Death for the Program. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute the Program, or other covered work, so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute it at all. For example, if a patent license would not permit royalty-free redistribution by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution. \end{frame} \begin{frame} \frametitle{12: LoD does not induce infrigement} It is not the purpose of this section to induce you to infringe any patents or other exclusive rights or to contest their legal validity. The sole purpose of this section is to protect the integrity of the free software distribution system. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. \end{frame} \begin{frame} \frametitle{14. Revised Versions} 14.[9] Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. \end{frame} \begin{frame} \frametitle{14: Continued} Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. \end{frame} \begin{frame} \frametitle{15. Requesting Exceptions} 15.[10] Requesting Exceptions. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. \end{frame} \begin{frame} \frametitle{16. No Warranty} 16.[11] There is no warranty for the Program, to the extent permitted by applicable law. Except when otherwise stated in writing the copyright holders and/or other parties provide the Program "as is" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the Program is with you. Should the Program prove defective, you assume the cost of all necessary servicing, repair or correction. \end{frame} \begin{frame} \frametitle{17. No Liability} 17.[12] In no event unless required by applicable law or agreed to in writing will any copyright holder, or any other party who may modify and/or redistribute the Program as permitted above, be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to use the Program (including but not limited to loss of data or data being rendered inaccurate or losses sustained by you or third parties or a failure of the Program to operate with any other programs), even if such holder or other party has been advised of the possibility of such damages. \end{frame} \begin{frame} \frametitle{18. Not tested for safety} 18. Unless specifically stated, the Program has not been tested for use in safety critical systems. \end{frame} } \end{document}