Open Source Licenses in Scientific Research Andres Guadamuz Gonzalez
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
“The Future Is Open” for Composition Studies: a New
THE FLORIDA STATE UNIVERSITY COLLEGE OF ARTS AND SCIENCES “THE FUTURE IS OPEN” FOR COMPOSITION STUDIES: A NEW INTELLECTUAL PROPERTY MODEL IN THE DIGITAL AGE By CHARLES LOWE A Dissertation submitted to the Department of English in partial fulfillment of the requirements for the degree of Doctor of Philosophy Degree Awarded Summer Semester, 2006 Copyright © 2006 Charles Lowe All Rights Reserved The members of the committee approve the dissertation of Charles Lowe defended on May 25, 2006. ______________________________ John Fenstermaker Professor Directing Dissertation ______________________________ Ernest Rehder Outside Committee Member ______________________________ Eric Walker Committee Member ______________________________ Deborah Coxwell-Teague Committee Member Approved: ______________________________ Hunt Hawkins, Chair, Department of English The Office of Graduate Studies has verified and approved the above named committee members. ii This text is dedicated to Wendy Bishop, John Lovas, Candace Spigelman, and Richard Straub, four teachers and researchers in the field of composition studies with whom it was my pleasure to work. I only wish I could have the opportunity again. iii TABLE OF CONTENTS ABSTRACT...............................................................................................................................vi INTRODUCTION.......................................................................................................................1 The Future Is Open............................................................................................................. -
An Introduction to Software Licensing
An Introduction to Software Licensing James Willenbring Software Engineering and Research Department Center for Computing Research Sandia National Laboratories David Bernholdt Oak Ridge National Laboratory Please open the Q&A Google Doc so that I can ask you Michael Heroux some questions! Sandia National Laboratories http://bit.ly/IDEAS-licensing ATPESC 2019 Q Center, St. Charles, IL (USA) (And you’re welcome to ask See slide 2 for 8 August 2019 license details me questions too) exascaleproject.org Disclaimers, license, citation, and acknowledgements Disclaimers • This is not legal advice (TINLA). Consult with true experts before making any consequential decisions • Copyright laws differ by country. Some info may be US-centric License and Citation • This work is licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0). • Requested citation: James Willenbring, David Bernholdt and Michael Heroux, An Introduction to Software Licensing, tutorial, in Argonne Training Program on Extreme-Scale Computing (ATPESC) 2019. • An earlier presentation is archived at https://ideas-productivity.org/events/hpc-best-practices-webinars/#webinar024 Acknowledgements • This work was supported by the U.S. Department of Energy Office of Science, Office of Advanced Scientific Computing Research (ASCR), and by the Exascale Computing Project (17-SC-20-SC), a collaborative effort of the U.S. Department of Energy Office of Science and the National Nuclear Security Administration. • This work was performed in part at the Oak Ridge National Laboratory, which is managed by UT-Battelle, LLC for the U.S. Department of Energy under Contract No. DE-AC05-00OR22725. • This work was performed in part at Sandia National Laboratories. -
Creator's Guide to Commercializing Copyrighted Work
STANFORD UNIVERSITY OFFICE OF Creator’s Guide to TECHNOLOGY Commercializing LICENSING Copyrighted Work OURSES WEB C PHY BOOKS S SI E GRA OFT TE D TO WA S O HO R C P E V M S U ID Y M S H E I E O C O P P C A S H F R G O N R I I C G E D O T O R G I O E R O C A R E N P R H O Y S M H P C C P O O A D B E E C L I I I C L B S O E O U U R M A S M N E P O S I T W P E C I E F B S R S O I T E A E D I S V B W O T O F K O S S he Stanford University Office of Technology Licensing (OTL) promotes the transfer of Stanford technology for Tsociety’s use and benefit. This technology grows out of the CONTENTS boundless creativity found in the faculty, staff, and students at the University. When that creative expression is protected by copyright, OTL and our Stanford creators face a distinct set THE BASICS .......................................................................................2 of commercialization and distribution issues that they do not STanford’s copyrighT POLICY .......................................................5 encounter for other forms of intellectual property. SOFTWARE .........................................................................................8 OTL created this booklet to help Stanford creators successfully identify and CONTENT AND COURSES..................................................................15 navigate those issues. The booklet is focused on out-licensing or distributing OPEN SOURCE SOFTWARE LICENSING ..............................................18 creative works owned by Stanford. -
Article Title
International In-house Counsel Journal Vol. 5, No. 20, Summer 2012, 1 Corporate Use of Open Source Software: Dispelling the Myths with a Policy HEATHER E. MCNAY Senior Intellectual Property Counsel, Landis+Gyr, USA Abstract Many companies do not understand open source software and choose to avoid it completely instead of creating an informed policy. Avoiding the issue can lead to developers using open source software incorrectly and potentially exposing proprietary company intellectual property through mandated public disclosure. The legal department for every technology company needs to work with the software development group to create a comprehensive Open Source Policy. The policy should ensure that every piece of open source code that is used by the company is reviewed pursuant to a prescribed process. A good policy will require that the requesting developer list the planned use of the open source code and provide the name of the license covering the code, if known. The proposed use of the code is important because stand-alone, or separably compilable, applications will not trigger certain license’s obligations, such as the publication of source code. There are many distinct open source licenses being used today, each with very different terms. With knowledge of the use and the license, the legal department can investigate the license and make a recommendation based on whether it is a ‘viral license’ (requiring publication) or not. Then, together with the technical point of contact, an informed decision can be made about all source code used by the company. Organisations will discover that using open source software in controlled manner can provide actual cost savings without exposing the company to any risk. -
Open Source Software: Avoiding the Pitfalls; Reaping the Rewards
McCarthy Tétrault LLP Open Source Software: Avoiding the Pitfalls; Reaping the Rewards Charles Morgan Presentation to the ALAI Auberge Le Saint-Gabriel September 24, 2003 McCarthy Tétrault Open Source »What is Open Source? »Brief History of Open Source »OSI Open Source Definition »Open Source Licenses »Open Source Business Models »Rewards & Pitfalls »Open Source Tips McCarthy Tétrault LLP What is Open Source? » Open source software can generally be defined by four freedoms: • The freedom to use the program • The freedom to examine and change the source code • The freedom to distribute the program • The freedom to distribute any changes to the source code McCarthy Tétrault LLP What is Open Source? » Nine core principles: • Free Distribution – no restriction on distribution of the software as a component of an aggregate software distribution (including royalty or fee) • Source Code - the source code must be accessible • Derived Works - license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software • Integrity of the Author’s Source Code - the license may restrict source code from being distributed in modified form only if the license allows the distribution of ‘patch files’ with the source code McCarthy Tétrault LLP What is Open Source? • No Discrimination Against Persons or Groups - the license must not discriminate against any person or group of persons • No Discrimination Against Fields of Endeavor - the license must not restrict anyone from making -
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 Penguin and the Cartel: Rethinking Antitrust and Innovation Policy for the Age of Commercial Open Source
The Penguin and the Cartel: Rethinking Antitrust and Innovation Policy for the Age of Commercial Open Source Stephen M. Maurer1 Abstract: Modern open source (“OS”) software projects are increasingly funded by commercial firms that expect to earn a profit from their investment. This is usually done by bundling OS software with proprietary goods like cell phones or services like tech support. This article asks how judges and policymakers should manage this emerging business phenomenon. It begins by examining how private companies have adapted traditional OS institutions in a commercial setting. It then analyzes how OS methods change companies’ willingness to invest in software. On the one hand, OS cost-sharing often leads to increased output and benefits to consumers. On the other, these benefits tend to be limited. This is because sharing guarantees that no OS company can offer consumers better software than any other OS company. This suppresses incentives to invest much as a formal cartel would. In theory, vigorous competition from non-OS companies can mitigate this effect and dramatically increase OS output. In practice, however, de facto cartelization usually makes the OS sector so profitable that relatively few proprietary companies compete. This poses a central challenge to judges and policymakers. Antitrust law has long recognized that the benefits of R&D sharing frequently justify the accompanying cartel effect. This article argues that most commercial OS collaborations can similarly be organized in ways that satisfy the Rule of Reason. It also identifies two safe harbors where unavoidable cartel effects should normally be tolerated. That said, many OS licenses contain so-called “viral” clauses that require users who would prefer to develop proprietary products to join OS collaborations instead. -
Shrinking the Commons: Termination of Copyright Licenses and Transfers for the Benefit of the Public Timothy K
University of Cincinnati College of Law University of Cincinnati College of Law Scholarship and Publications Faculty Articles and Other Publications Faculty Scholarship 1-1-2010 Shrinking the Commons: Termination of Copyright Licenses and Transfers for the Benefit of the Public Timothy K. Armstrong University of Cincinnati College of Law Follow this and additional works at: http://scholarship.law.uc.edu/fac_pubs Part of the Intellectual Property Commons Recommended Citation Armstrong, Timothy K., "Shrinking the Commons: Termination of Copyright Licenses and Transfers for the Benefit of the ubP lic" (2010). Faculty Articles and Other Publications. Paper 144. http://scholarship.law.uc.edu/fac_pubs/144 This Article is brought to you for free and open access by the Faculty Scholarship at University of Cincinnati College of Law Scholarship and Publications. It has been accepted for inclusion in Faculty Articles and Other Publications by an authorized administrator of University of Cincinnati College of Law Scholarship and Publications. For more information, please contact [email protected]. ARTICLE SHRINKING THE COMMONS: TERMINATION OF COPYRIGHT LICENSES AND TRANSFERS FOR THE BENEFIT OF THE PUBLIC TIMOTHY K. ARMSTRONG* Federallaw limits the free alienabilityof copyright rights to preventpower- ful transfereesfrom forcing authors into unremunerative bargains. The limiting mechanism is a statutory provision that permits authors or their heirs, at their sole election, to terminate any transfer or license of any copyright interest dur- ing a defined period. Indeed, the applicable provisions of the Copyright Act go so far as to invalidate purported waivers by authors of their statutory termina- tion powers. These statutory provisions may constitute an impediment to the effective grant of rights for the benefit of the public under widely used "open content" licensing arrangements, such as the GNU General Public License ("GPL") for software or the Creative Commons family of licenses for other sorts of expres- sive works. -
Open Content Licensing
Open Content Licensing Open Content Licensing From Theory to Practice Edited by Lucie Guibault & Christina Angelopoulos Amsterdam University Press Cover design: Kok Korpershoek bno, Amsterdam Lay-out: JAPES, Amsterdam ISBN 978 90 8964 307 0 e-ISBN 978 90 4851 408 3 NUR 820 Creative Commons License CC BY NC (http://creativecommons.org/licenses/by-nc/3.0) L. Guibault & C. Angelopoulos / Amsterdam University Press, Amsterdam, 2011 Some rights reversed. Without limiting the rights under copyright reserved above, any part of this book may be reproduced, stored in or introduced into a retrieval system, or transmitted, in any form or by any means (electronic, mechanical, photocopying, recording or otherwise). Contents 1. Open Content Licensing: From Theory to Practice – An Introduction 7 Lucie Guibault, Institute for Information Law, University of Amsterdam 2. Towards a New Social Contract: Free-Licensing into the Knowledge Commons 21 Volker Grassmuck, Humboldt University Berlin and University of Sao Paulo 3. Is Open Content a Victim of its Own Success? Some Economic Thoughts on the Standardization of Licenses 51 Gerald Spindler and Philipp Zimbehl, University of Göttingen 4. (Re)introducing Formalities in Copyright as a Strategy for the Public Domain 75 Séverine Dusollier, Centre de Recherche Informatique et Droit, Université Notre- Dame de la Paix (Namur) 5. User-Related Assets and Drawbacks of Open Content Licensing 107 Till Kreutzer, Institute for legal questions on Free and Open Source Software (ifrOSS) 6. Owning the Right to Open Up Access to Scientific Publications 137 Lucie Guibault, Institute for Information Law, University of Amsterdam 7. Friends or Foes? Creative Commons, Freedom of Information Law and the European Union Framework for Reuse of Public Sector Information 169 Mireille van Eechoud, Institute for Information Law, University of Amsterdam 8. -
Using Open Source Software in Business
Using Open Source Software in Business November 26, 2018 This post was first published on February 19, 2010. Open Source Software (OSS) has certain advantages when compared to proprietary software. It comes with the following benefits: a. The software may be downloaded for free; b. Source code of the software is available, which enables improvement and customization; c. The software generally has a community and the development is faster; d. Support and implementation services are available from multiple sources; and so on. As OSS always comes with a license, the rights and limitations with respect to the use of the software is defined by the kind of license that governs the software. Based on the restrictions imposed, licenses may be classified into viral, restrictive and flexible. A viral license is one that spreads to every software it comes in contact. In other words, if any software is combined with OSS that is governed by a viral license, such software will also be governed by the license. GNU General Public License (GPL) and Affero General Public License (AGPL) are popular examples of viral licenses. If OSS governed by any such license is distributed along with a proprietary software, more often than not the source code of the proprietary software also must be made available and the proprietary software will also become open source. Restrictive licenses generally have all provisions of a viral license but do not spread to every software combined with OSS. These licenses generally provide flexibility with respect to distributing OSS combined with a proprietary software. In such a case, the source code of the proprietary software need not be made available and it may be distributed under a license of choice. -
Creative Commons Licenses Legal Pitfalls: Incompatibilities and Solutions
INSTITUTE FOR INFORMATION LAW Creative Commons Licenses Legal Pitfalls: Incompatibilities and Solutions Melanie Dulong de Rosnay Institute for Information Law University of Amsterdam Version 1.1 20 December 2010 This work is licensed under a Creative Commons Attribution 3.0 Nederland license available at http://creativecommons.org/licenses/by/3.0/nl/ TABLE OF CONTENTS Foreword .................................................................................................................................... 1 Executive summary .................................................................................................................... 2 1. Introduction ............................................................................................................................ 7 1.1 Sources of legal incompatibilities .................................................................................... 9 1.2 Scope, methodology and outline .................................................................................... 10 2. Creative Commons licenses diversity .................................................................................. 13 2.1 Creative Commons: an organization and a set of licenses ............................................. 15 2.1.1 The licensing infrastructure: a technical standard .................................................. 15 2.1.2 Creative Commons policy strategy: not quite a legal standard ............................... 18 2.2 The different licenses available .................................................................................... -
A Practical Guide to Open Source Software1 Michael Pavento
1 A Practical Guide to Open Source Software Michael Pavento I. Introduction Open source software (“OSS”) is software that is freely available in source-code form for anyone to use, copy, modify and distribute. Generally speaking, however, OSS is not “public domain” software. Like any other software, OSS is copyrighted intellectual property. Authors have the right to control or condition the use of their original OSS code and typically do so through license agreements. Unlike traditional software licenses that seek to limit or prohibit further dissemination of the licensed software and certainly the underlying source code, OSS license agreements generally seek to encourage dissemination and to ensure that the source code remains open and accessible to all. Like any other software acquired from an outside source, the applicable license agreement is the starting point for understanding and managing the obligations imposed upon and the risks undertaken by an organization with respect to OSS. A careful review of some of the more common license agreements, for example the GNU General Public Licenses, the Apache License, the Common Development and Distribution License and the Berkley Software Development License,2 will dispel some of the common misperceptions regarding OSS. For example, it is sometimes said that OSS cannot be used with proprietary software. To the contrary, OSS licenses do not limit the manner in which the licensed OSS may be used; they typically permit all uses, but impose reciprocal obligations that are triggered when the licensee distributes the licensed OSS or modifications of it. It is also often said that all OSS licenses require the release of source code for any proprietary software used in conjunction with the OSS.