OSS V. Perens
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Intellectual Property Law Week Helpful Diversity Or Hopeless Confusion?
Intellectual Property Law Week Open Source License Proliferation: Helpful Diversity or Hopeless Confusion? Featuring Professor Robert Gomulkiewicz University of Washington School of Law Thursday, March 18, 2010 12:30-2:00 PM Moot Courtroom Abstract: One prominent issue among free and open source software (FOSS) developers (but little noticed by legal scholars) has been "license proliferation." "Proliferation" refers to the scores of FOSS licenses that are now in use with more being created all the time. The Open Source Initiative ("OSI") has certified over seventy licenses as conforming to the Open Source Definition, a key measure of whether a license embodies FOSS principles. Many believe that license proliferation encumbers and retards the success of FOSS. Why does proliferation occur? What are the pros and cons of multiple licenses? Does the growing number of FOSS licenses represent hopeless confusion (as many assume) or (instead) helpful diversity? To provide context and color, these issues are examined using the story of his creation of the Simple Public License (SimPL) and submission of the SimPL to the OSI for certification. Professor Robert Gomulkiewicz joined the UW law school faculty in 2002 to direct the graduate program in Intellectual Property Law and Policy. Prior to joining the faculty, he was Associate General Counsel at Microsoft where he led the group of lawyers providing legal counsel for development of Microsoft's major systems software, desktop applications, and developer tools software (including Windows and Office). Before joining Microsoft, Professor Gomulkiewicz practiced law at Preston, Gates & Ellis where he worked on the Apple v. Microsoft case. Professor Gomulkiewicz has published books and law review articles on open source software, mass market licensing, the UCITA, and legal protection for software. -
Lifecycle Management in Government-Driven Open Source Projects – Practical Framework
ISSN (print):2182-7796, ISSN (online):2182-7788, ISSN (cd-rom):2182-780X Available online at www.sciencesphere.org/ijispm Lifecycle management in government-driven open source projects – practical framework Katja Henttonen VTT Technical Research Centre of Finland Tietotie 3, 02150 Espoo Finland www.shortbio.org/[email protected] Jukka Kääriäinen VTT Technical Research Centre of Finland Kaitoväylä 1, 90530 Oulu Finland www.shortbio.org/[email protected] Jani Kylmäaho National Land Survey of Finland (NLS) Opastinsilta 12C, 00521 Helsinki Finland www.shortbio.org/[email protected] Abstract: In many parts of the world, public sector organizations are increasingly interested in collaborating across organizational (and even national) boundaries to develop software solutions under an open licence. However, without sound lifecycle management practices, the full benefits of open collaboration are not achieved and projects fail to achieve sustained success. This paper introduces a lifecycle management model and framework for government-driven open-source projects and reports about its use in a real-life case study. Our focus is on lifecycle management activities which take place between deployment and end-of-life. The framework was developed iteratively through a series of focus group discussions with representatives of public sector organizations. After the framework had been taken into use in our real-life case project, individual qualitative interviews were conducted to collect experiences on its benefits and weaknesses. According to the initial evidence, the deployment of the framework seems to have brought concrete benefits to the project, e.g. by contributing positively to community growth, software quality and inter-organizational learning. -
FOSS Philosophy 6 the FOSS Development Method 7
1 Published by the United Nations Development Programme’s Asia-Pacific Development Information Programme (UNDP-APDIP) Kuala Lumpur, Malaysia www.apdip.net Email: [email protected] © UNDP-APDIP 2004 The material in this book may be reproduced, republished and incorporated into further works provided acknowledgement is given to UNDP-APDIP. For full details on the license governing this publication, please see the relevant Annex. ISBN: 983-3094-00-7 Design, layout and cover illustrations by: Rezonanze www.rezonanze.com PREFACE 6 INTRODUCTION 6 What is Free/Open Source Software? 6 The FOSS philosophy 6 The FOSS development method 7 What is the history of FOSS? 8 A Brief History of Free/Open Source Software Movement 8 WHY FOSS? 10 Is FOSS free? 10 How large are the savings from FOSS? 10 Direct Cost Savings - An Example 11 What are the benefits of using FOSS? 12 Security 13 Reliability/Stability 14 Open standards and vendor independence 14 Reduced reliance on imports 15 Developing local software capacity 15 Piracy, IPR, and the WTO 16 Localization 16 What are the shortcomings of FOSS? 17 Lack of business applications 17 Interoperability with proprietary systems 17 Documentation and “polish” 18 FOSS SUCCESS STORIES 19 What are governments doing with FOSS? 19 Europe 19 Americas 20 Brazil 21 Asia Pacific 22 Other Regions 24 What are some successful FOSS projects? 25 BIND (DNS Server) 25 Apache (Web Server) 25 Sendmail (Email Server) 25 OpenSSH (Secure Network Administration Tool) 26 Open Office (Office Productivity Suite) 26 LINUX 27 What is Linux? -
The General Public License Version 3.0: Making Or Breaking the FOSS Movement Clark D
Michigan Telecommunications and Technology Law Review Volume 14 | Issue 2 2008 The General Public License Version 3.0: Making or Breaking the FOSS Movement Clark D. Asay Follow this and additional works at: http://repository.law.umich.edu/mttlr Part of the Computer Law Commons, and the Science and Technology Law Commons Recommended Citation Clark D. Asay, The General Public License Version 3.0: Making or Breaking the FOSS Movement, 14 Mich. Telecomm. & Tech. L. Rev. 265 (2008). Available at: http://repository.law.umich.edu/mttlr/vol14/iss2/1 This Article is brought to you for free and open access by the Journals at University of Michigan Law School Scholarship Repository. It has been accepted for inclusion in Michigan Telecommunications and Technology Law Review by an authorized editor of University of Michigan Law School Scholarship Repository. For more information, please contact [email protected]. THE GENERAL PUBLIC LICENSE VERSION 3.0: MAKING OR BREAKING THE FOSS MOVEMENT? Clark D. Asay* Cite as: Clark D. Asay, The GeneralPublic License Version 3.0: Making or Breaking the Foss Movement? 14 MICH. TELECOMM. TECH. L. REV. 265 (2008), available at http://www.mttlr.org/volfourteen/asay.pdf I. INTRODUCTION ......................................................................... 266 II. FREE SOFTWARE V. OPEN SOURCE ........................................... 268 A. The FSF's Vision of Free Software..................................... 268 B. The OSI's Vision: A Different Movement? ......................... 270 C. PracticalDifferences? ....................................................... 271 III. G PLv3: ITS T ERM S................................................................... 274 A. GPLv3 's Anti-DRM Section ............................................... 274 1. Its C ontents ................................................................. 274 2. FSF's Position on DRM .............................................. 276 3. The Other Side of the Coin? OSI Sympathizers ........ -
Table of Contents
Table of Contents Preface . ix 1. Open Source Licensing, Contract, and Copyright Law . 1 Basic Principles of Copyright Law 1 Contract and Copyright 3 Open Source Software Licensing 4 Issues with Copyrights and Patents 7 The Open Source Definition 8 Warranties 11 2. The MIT, BSD, Apache, and Academic Free Licenses . 14 The MIT (or X) License 14 The BSD License 15 The Apache License, v1.1 and v2.0 17 The Academic Free License 24 Application and Philosophy 30 3. The GPL, LGPL, and Mozilla Licenses . 34 GNU General Public License 35 GNU Lesser General Public License 49 The Mozilla Public License 1.1 (MPL 1.1) 62 Application and Philosophy 81 4. Qt, Artistic, and Creative Commons Licenses . 85 The Q Public License 85 Artistic License (Perl) 90 Creative Commons Licenses 98 vii 5. Non-Open Source Licenses . 114 Classic Proprietary License 114 Sun Community Source License 120 Microsoft Shared Source Initiative 144 6. Legal Impacts of Open Source and Free Software Licensing . 147 Entering Contracts 148 Statutory Developments Related to Software Contracts 150 The Self-Enforcing Nature of Open Source and Free Software Licenses 151 The Global Scope of Open Source and Free Software Licensing 153 The “Negative Effects” of Open Source and Free Software Licensing 154 Community Enforcement of Open Source and Free Software Licenses 158 Compatible and Incompatible Licensing: Multiple and Cross Licensing 159 7. Software Development Using Open Source and Free Software Licenses . 164 Models of Open Source and Free Software Development 164 Forking 171 Choosing an Open Source or Free Software License 174 Drafting Open Source Licenses 176 Appendix: Creative Commons Attribution-NoDerivs License . -
Free and Open Source Software: “Commons” Or Clubs
To be published in the book “Conference for the 30th Anniversary of the CRID” (Collection du CRIDS) Free and Open Source Software Licensing: A reference for the reconstruction of “virtual commons”?1 Philippe LAURENT Senior Researcher at the CRIDS (University of Namur - Belgium) Lawyer at the Brussels Bar (Marx, Van Ranst, Vermeersch & Partners) The impact of the Free, Libre and Open Source Software (FLOSS) movement has been compared to a revolution in the computing world2. Beyond the philosophical and the sociological aspects of the movement, its most outstanding achievement is probably its penetration in the ICT market3. FLOSS has indeed reached a high level of economical maturity. It is not “just” an alternative movement any more, nor is it a simple option that companies of the field can choose to take or simply ignore. It is a reality that everyone has to acknowledge, understand and deal with, no matter which commercial strategy or business model is implemented. FLOSS is based upon an outstanding permissive licensing system coupled with an unrestricted access to the source code, which enables the licensee to modify and re-distribute the software at will. In such context, intellectual property is used in a versatile way, not to monopolize technology and reap royalties, but to foster creation on an open and collaborative basis. This very particular use of initially “privative” rights firstly amazed… then became source of inspiration. Indeed, scientists, academics and other thinkers noticed that the free and open source system actually worked quite well and gave birth to collaborative and innovative, but also commercially viable ecosystems. -
Elements of Free and Open Source Licenses: Features That Define Strategy
Elements Of Free And Open Source Licenses: Features That Define Strategy CAN: Use/reproduce: Ability to use, copy / reproduce the work freely in unlimited quantities Distribute: Ability to distribute the work to third parties freely, in unlimited quantities Modify/merge: Ability to modify / combine the work with others and create derivatives Sublicense: Ability to license the work, including possible modifications (without changing the license if it is copyleft or share alike) Commercial use: Ability to make use of the work for commercial purpose or to license it for a fee Use patents: Rights to practice patent claims of the software owner and of the contributors to the code, in so far these rights are necessary to make full use of the software Place warranty: Ability to place additional warranty, services or rights on the software licensed (without holding the software owner and other contributors liable for it) MUST: Incl. Copyright: Describes whether the original copyright and attribution marks must be retained Royalty free: In case a fee (i.e. contribution, lump sum) is requested from recipients, it cannot be royalties (depending on the use) State changes: Source code modifications (author, why, beginning, end) must be documented Disclose source: The source code must be publicly available Copyleft/Share alike: In case of (re-) distribution of the work or its derivatives, the same license must be used/granted: no re-licensing. Lesser copyleft: While the work itself is copyleft, derivatives produced by the normal use of the work are not and could be covered by any other license SaaS/network: Distribution includes providing access to the work (to its functionalities) through a network, online, from the cloud, as a service Include license: Include the full text of the license in the modified software. -
Emergent Computing Joint ERCIM Actions: ‘Beyond the Horizon’ Anticipating Future and Emerging Information Society Technologies
European Research Consortium for Informatics and Mathematics Number 64, January 2006 www.ercim.org Special: Emergent Computing Joint ERCIM Actions: ‘Beyond the Horizon’ Anticipating Future and Emerging Information Society Technologies European Scene: Routes to Open Access Publishing CONTENTS JOINT ERCIM ACTIONS THE EUROPEAN SCENE 4 Fourth ERCIM Soft Computing Workshop The Routes to Open Access by Petr Hajek, Institute of Computer Science, Academy of 16 Open Access: An Introduction Sciences / CRCIM, Czech Republic by Keith G Jeffery, Director IT, CCLRC and ERCIM president 4 Cor Baayen Award 2006 18 Publish or Perish — Self-Archive to Flourish: The Green Route to Open Access 5 Second ERCIM Workshop ‘Rapid Integration of Software by Stevan Harnad, University of Southampton, UK Engineering Techniques’ by Nicolas Guelfi, University of Luxembourg 19 The Golden Route to Open Access by Jan Velterop 5 Grid@Asia: European-Asian Cooperation Director of Open Access, Springer in Grid Research and Technology by Bruno Le Dantec , ERCIM Office 20 ERCIM Statement on Open Access 6 GFMICS 2005 — 10th International Workshop on Formal 21 Managing Licenses in an Open Access Community Methods for Industrial Critical Systems by Renato Iannella National ICT Australia by Mieke Massink and Tiziana Margaria 22 W3C at the Forefront of Open Access Beyond-The-Horizon Project by Rigo Wenning, W3C 7 Bits, Atoms and Genes Beyond the Horizon 23 Cream of Science by Dimitris Plexousakis, ICS-FORTH, Greece by Wouter Mettrop, CWI, The Netherlands 8 Thematic Group 1: Pervasive Computing and Communications SPECIAL THEME: by Alois Ferscha, University of Linz, Austria EMERGENT COMPUTING 24 Introduction to the Special Theme 9 Thematic Group 2: by Heather J. -
The Community Data License Agreement (”CDLA”) an Introduction and Overview
The Community Data License Agreement (”CDLA”) An Introduction and Overview Christopher W. O’Neill Associate General Counsel Intellectual Property Law IBM Corporation [email protected] As systems require data to learn and evolve, no one organization can build, maintain and source all data required. 2 The CDLA license agreements enable sharing data openly, embodying best practices learned over decades sharing source code. 3 New advancements are driving interest in “open data” • Interest in sharing data has grown significantly due to machine learning, AI, blockchain and expansion of open geolocation solutions • Governments, companies and organizations are interested in sharing data “just like we share source code” • They’re looking to open source principles for how they may be applied to data problems • Open source development is viewed as an ideal model for collaborating on datasets • Connected civil infrastructure and private systems are starting to intersect (e.g. infrastructure-to-vehicle systems) with data created and shared 4 CDLA Summary • The Community Data License Agreement (“CDLA”) family is a set of two model agreements, introduced and sponsored by the Linux Foundation • Announced on October 23, 2017 • Modeled on the structure of leading open source agreements • Designed for use by independent data communities looking for “open” licenses that reflect the nuances of data licensing (as opposed to software or copyright licensing) • CDLA promotes free exchange of data • Permits data to be freely used, modified, and republished • Authorship -
Open Source Semiconductor Core Licensing
Harvard Journal of Law & Technology Volume 25, Number 1 Fall 2011 OPEN SOURCE SEMICONDUCTOR CORE LICENSING Eli Greenbaum* TABLE OF CONTENTS I. INTRODUCTION .............................................................................. 131 II. TECHNICAL BACKGROUND ........................................................... 134 III. THE GPL AND LGPL ................................................................... 139 IV. DISTRIBUTION ............................................................................. 141 V. LINKING ........................................................................................ 144 A. Hard Cores ............................................................................... 145 B. Soft Cores ................................................................................. 147 C. Libraries ................................................................................... 149 VI. DISTRIBUTION OF PHYSICAL DEVICES ........................................ 151 VII. CONCLUSION ............................................................................. 156 I. INTRODUCTION Semiconductor cores are not software in the conventional sense of that term. Even so, perhaps for lack of a readily available and more tailored framework, the tools used to license software have increas- ingly been applied to these works. This Article reviews the technology and structure of the semiconductor core industry and analyzes the ap- plication of open source license principles to semiconductor cores. Specifically, this Article -
Table of Contents
Table of Contents Preface xiii Foreword xv Chapter 1 Introduction 1 Chapter 2 Genesis of the Institution 9 2.1. Introduction 9 2.2. Open Source Software: Early Developments and Evolution 10 2.2.1. Property Domains 10 2.2.2. ‘Opening’ of Software ‘Freedom’ 17 2.2.3. Defining Open Source Software 22 2.3. Conclusion 26 Chapter 3 The Legal Governance Structure 29 3.1. Introduction 29 3.2. Legal Governance Structure of Open Source Software 30 3.2.1. Existing Intellectual Property Protection and Open Source Software 31 3.2.1.1. Trade Secret Protection 32 3.2.1.2. Copyright Protection 33 3.2.1.3. Moral Rights 37 3.2.1.4. Patent Protection 39 3.2.1.5. Trademarks 43 3.2.2. Existing Contractual-License Protection and Open Source Software 44 3.3. Conclusion 46 Table of Contents Chapter 4 The Licensing Regime 47 4.1. Introduction 47 4.2. A Taxonomy of Licenses 48 4.2.1. GNU General Public License (GPL) and Other Related Licenses 51 4.2.2. The Berkeley Software Distribution (BSD) and Other Related Licenses 54 4.2.3. The Mozilla Public License and Related Commercial Licenses 56 4.2.4. Other Open Source Software Licenses 59 4.3. Conclusion 60 Chapter 5 Licensing and Rights Management 61 5.1. Introduction 61 5.2. Groundwork Definitions 62 5.3. The Granting Clause 64 5.3.1. Intellectual Property Grant 65 5.3.1.1. Copyright Grant 65 5.3.1.2. Patent Grant 70 5.3.1.3. -
Gpl) Had Been Patented?
CLAIMING COPYLEFT IN OPEN SOURCE SOFTWARE: WHAT IF THE FREE SOFTWARE FOUNDATION’S GENERAL PUBLIC LICENSE (GPL) HAD BEEN PATENTED? Greg R. Vetter† 2008 MICH. ST. L. REV. 279 TABLE OF CONTENTS INTRODUCTION...........................................................................................280 I. BUSINESS METHOD PATENTS AT THE INTERSECTION OF SOFTWARE AND LICENSING............................................................................................286 II. CLAIMING COPYLEFT: FOSS LICENSING UNDER GPLV2 AS A PATENT PROTECTED ACTIVITY .........................................................................288 A. A Hypothetical Claim for the GPLv2 Patent...............................289 B. Utility...........................................................................................291 C. Objective Disclosure...................................................................292 D. Novelty and Statutory Bars..........................................................293 E. Non-Obviousness ........................................................................294 1. Differences Compared to the Prior Art of Software Licensing...............................................................................295 2. Secondary Considerations: Particularly “Unexpected Results”.................................................................................296 III. CLAIMED COPYLEFT: ENFORCEMENT MOMENTS IN THE FOSS MOVEMENT..........................................................................................298 A. The FSF and Copyright