License Integration Patterns: Dealing with Licenses Mismatches in Component-Based Development

Total Page:16

File Type:pdf, Size:1020Kb

License Integration Patterns: Dealing with Licenses Mismatches in Component-Based Development License Integration Patterns: Dealing with Licenses Mismatches in Component-Based Development Daniel M. German Department of Computer Science University of Victoria, Canada [email protected] Ahmed E. Hassan School of Computing Queen’s University, Canada [email protected] To appear at the 31st International Conference on Software Engineering (ICSE) 2009 Abstract for the creation of many successful projects. Over the last decade, various research efforts have In this paper we address the problem of combining focused on the technical aspects of supporting and im- software components with different and possibly incom- proving component-driven software development pro- patible legal licenses to create a software application cesses. For example, Garlan et al. discuss the chal- that does not violate any of these licenses while poten- lenges of component development due to architecture tially having its own. We call this problem the license and interface mismatches [8]. However, little atten- mismatch problem. The rapid growth and availability tion has been directed toward the legal complexities of Open Source Software (OSS) components with vary- surrounding component based software development. ing licenses, and the existence of more than 70 OSS li- Builders of component based applications must com- censes increases the complexity of this problem. Based bine components with different licenses to create a new on a study of 124 OSS software packages, we developed software application, i.e., derivative work, with its own a model which describes the interconnection of compo- licensing terms. nents in these packages from a legal point of view. We used our model to document integration patterns that With the widespread of open source components, are commonly used to solve the license mismatch prob- practitioners are likely to pick open source components lem in practice when creating both proprietary and OSS when building their next large component based appli- applications. Software engineers with little legal exper- cation. In contrast to commercial components, open tise could use these documented patterns to understand source components have a large number of licenses. At and address the legal issues involved in reusing compo- last count there are 70 approved open source licenses. nents with different and possibly conflicting licenses. Each license has its own set of permissions and restric- tions. Combining components of differing and possibly conflicting licenses is the next big challenge for compo- nent based development. We call this challenge - the 1. Introduction license-mismatch problem. The Bugzilla software application [31] is a great ex- Most large software applications are not built from ample to highlight the sheer complexity of this prob- scratch, instead they are built by combining several lem in modern component-driven development. In its components such as reused code snippets, self con- most common instance, Bugzilla makes use of 82 pack- tained binary libraries, or other applications. Compo- ages. These packages use 10 different licenses including nent based development (e.g., [19]) has been a catalyst original 4-clauses BSD, new 3-clauses BSD, Artistic v1, 1 GNU General Public License (GPL) v1, GNU GPL v2, problem. Through a detailed study of the licenses and GNU Lesser General Public License v2.1, MIT, Apache architecture of 124 OSS packages, we identified and v2, and IBM Public License v1.0. Many of these li- documented patterns that are commonly used to in- censes conflict with each other, for example, the GPL tegrate components with different licenses. By docu- licenses insist that all code linked to them must be menting these patterns, we aim to 1) Demonstrate the GPL-licensed as well; one would expect that the fi- effect of legal issues on the architecture of modern soft- nal product, i.e., Bugzilla, would be licensed under the ware applications, 2) Define common vocabulary for GPL. However, Bugzilla is licensed under the Mozilla discussing and analyzing the effects of licenses on soft- Public License 1.1. To combine all these conflicting ware, 3) Provide a set of cookbook advice, i.e., patterns licenses, the developers of Bugzilla had to adapt and for practitioners to learn best practices, for academic modify their technical solutions and architecture to en- to improve research and education matters associated sure that Bugzilla complies with the other ten licenses. with software licensing issues. Several models have been proposed in the past to model the selection of components (such as [3]) but 1.1. Overview Of Paper do not address how its license affects the requirements and potential uses of a component-based system, and This paper is organized as follows. Section 2 gives a its architecture. Others have warned about the diffi- brief overview of the legal protections available for soft- culties of including open source software in commer- ware. Section 3 presents our model to describe licenses cial software [1, 16, 25, 29]. IBM’s Ariadne Ariadne and the legal consequences of combining components of appears to be the only tool that fully incorporates the different licenses. Section 4 presents our system of pat- management of intellectual property in software devel- terns. In Section 5 we conclude the paper and outline opment [4]. Some organizations, however, have poli- possible venues for future work. cies and procedures on how open source components should be selected for inclusion in proprietary prod- ucts [16, 10]. 2. Legal protections for Software License compliance is rapidly becoming an im- portant and critical challenge for many software or- From a legal point of view, software, or more specif- ganizations worldwide. Companies like Hewlett- ically, a “‘computer program’ is a set of statements or Packard (http://www.hp.com), Black Duck Soft- instructions to be used directly or indirectly in a com- ware (http://blackducksoftware.com) and Palimida puter in order to bring about a certain result.”[37]. (http://palamida.com) have created infrastructures Computer programs are usually protected using one or and toolsets to help software organizations tackle the more legal alternatives: a) trademarks–which protect license mismatch problem. For example, Koders.com the software name, logos, and any specific mark as- by Black Duck Software is a source code search engine sociated with the software; b) trade secret–the source which permits developers to limit their code search to code of the program is kept secret, only binary or specific licenses; and the FOSSology Project by HP obfuscated versions of the program are distributed, provides the infrastructure to automatically detect li- c) patents–software related inventions are patentable, censes in software packages to aid in identifying possi- giving the owner of the patent a monopoly on its ble license mismatches [10]. exploitation though not all countries permit software In contrast to technical challenges, the license mis- patents, d) copyright–gives its owner certain exclu- match problem is a more complex challenge for which sive rights such as making copies of the software. See software engineers have limited training and knowl- [2, 11, 14, 24] for comprehensive discussions on how edge. Undergraduates exposure to legal issues is con- these protections are applied to software. This paper fined to a few lectures in a single course as per the focuses on the use of copyright to protect software. ACM Software Engineering Curriculum guidelines. The main contributions of this paper are twofold. 2.1. Exclusive rights and licenses First, the development of a model to describe licenses, and the implications of licenses on components reuse The copyright owner of a software system has var- efforts. This model is the first step for creating frame- ious exclusive rights over it, namely [37]: 1) to make works which could automatically verify legal compli- copies of it, 2) to prepare derivative works based on it, ance. Second, we highlight and document the efforts of 3) to distribute copies for sale, rent, lease or lending, the open source community in addressing the mismatch 4) to perform the work in public, and 5) to display the 2 work in public. A copyright owner can exploit these 2.3. Open source licenses exclusive rights for a fixed period of time, as long as 95 years if the owner is an organization, from the first Open source licenses create a legal framework which publication of a piece of software. An owner can ex- permits the collaboration of different individuals and plicitly forfeit the copyright of a work. A work with no organizations in the creation of software: “Open source copyright owner is said to be in the public domain. licensing has become a widely used method of creative A license is a legal mechanism used by the copyright collaboration that serves to advance the arts and sci- or patent owner (the licensor) to grant permission to ences in a manner and at a pace that few could have others (the licensees) to use and exploit her intellectual imagined just a few decades ago.” [13]. property in ways that would otherwise be forbidden by The Open Source Initiative (OSI) (http://www. copyright or patent law [15, 17, 28]. For example, an opensource.org/) defines and promotes the “Open integrator who wants to modify and include a compo- Source Definition” (OSD). The OSD defines open nent as part of a larger software application and sell the source as software that is distributed under a license application will require the rights to create a derivative that satisfies 11 specific criteria for an open source work of the component, make copies of it, to distribute license[32]. These criteria include: the source code it and to sell it. The integrator would have these rights should be available; the license should allow modifi- if a) she owns the intellectual property of the compo- cations and derived works, the distribution of such de- nent, b) the intellectual property of the component is rived works are licensed under the same terms as the in the public domain, or c) she has a license for the original license; and the license must not discriminate component which grants her these rights.
Recommended publications
  • Third-Party License Acknowledgments
    Symantec Privileged Access Manager Third-Party License Acknowledgments Version 3.4.3 Symantec Privileged Access Manager Third-Party License Acknowledgments Broadcom, the pulse logo, Connecting everything, and Symantec are among the trademarks of Broadcom. Copyright © 2021 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. For more information, please visit www.broadcom.com. Broadcom reserves the right to make changes without further notice to any products or data herein to improve reliability, function, or design. Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does not assume any liability arising out of the application or use of this information, nor the application or use of any product or circuit described herein, neither does it convey any license under its patent rights nor the rights of others. 2 Symantec Privileged Access Manager Third-Party License Acknowledgments Contents Activation 1.1.1 ..................................................................................................................................... 7 Adal4j 1.1.2 ............................................................................................................................................ 7 AdoptOpenJDK 1.8.0_282-b08 ............................................................................................................ 7 Aespipe 2.4e aespipe ........................................................................................................................
    [Show full text]
  • Web Application for Generating a Standard Coordinated Documentation for CS Students’ Graduation Project in Gaza Universities Ibrahim M
    International Journal of Engineering and Information Systems (IJEAIS) ISSN: 2000-000X Vol. 1 Issue 6, September – 2017, Pages: 155-167 Web Application for Generating a Standard Coordinated Documentation for CS Students’ Graduation Project in Gaza Universities Ibrahim M. Nasser, Samy S. Abu-Naser Faculty of Engineering and Information Technology, Al-Azhar University, Gaza, Palestine [email protected] Abstract: The computer science (CS) graduated students suffered from documenting their projects and specially from coordinating it. In addition, students’ supervisors faced difficulties with guiding their students to an efficient process of documenting. In this paper, we will offer a suggestion as a solution to the mentioned problems; that is an application to make the process of documenting computer science (CS) student graduation project easy and time-cost efficient. This solution will decrease the possibility of human mistakes and reduce the effort of documenting process. Keywords: web applications, cost efficient, time-cost efficient, documenting, software engineering, graduation projects. 1. INTRODUCTION Computer science (CS) is the study of the occurrences adjoining computers [1]. It's also defined as the study of computers and computational systems, computer scientists deal usually with software (unlike electrical and computer engineers), Primary parts of study inside Computer Science consist of computer systems, operating systems, networks, database systems, artificial intelligence, computer architecture, security, computer graphics, human computer interaction, systems analysis, software engineering, theory of computing and programming languages [11,17-28]. In computing, a web application is a client–server application that means, the client (like user interface) works in a web browser [2]. The general distinction between a web application and a dynamic web page is vague, web sites that we can name them as "web applications" are those have comparable functionality to a mobile application or to a desktop applications [3].
    [Show full text]
  • 2002 USENIX Annual Technical Conference
    Announcement and Call for Papers 2002 USENIX Annual Technical Conference http://www.usenix.org/events/usenix02 June 10–15, 2002 Monterey Conference Center, Monterey, California Important Dates Three days of tutorials start the conference receive notification by Friday, November 23, FREENIX Refereed Track submission deadline: with practical tutorials on timely topics. The 2001, please contact: [email protected]. November 12, 2001 three-day technical session of the conference Papers should be 8 to 12 single-spaced 8.5 x General Session Refereed Track submission follows and includes a track of General Session 11 inch pages (about 4000-6000 words), not deadline: November 19, 2001 Refereed Papers selected by the Program counting figures and references. Papers longer Notification to authors: January 22, 2002 Committee; a track of Invited Talks by experts than 14 pages and papers so short as to be FREENIX Track papers due for final and leaders in the field; and FREENIX, a track considered extended abstracts (e.g., five pages or shepherding approval: April 8, 2002 of refereed papers on freely available POSIX- less) will not be reviewed. Camera-ready papers due: April 16, 2002 based software and systems. It is imperative that you follow the General Session Refereed Papers instructions for submitting a quality paper. Conference Organizers Specific questions about submissions may be The 2002 USENIX Technical Conference seeks Program Committee: sent to the program chair via email to: original and innovative papers about the Chair: Carla Ellis, Duke University [email protected]. applications, architecture, implementation, and Darrell Anderson, Duke University A good paper will clearly demonstrate that performance of modern computing systems.
    [Show full text]
  • Ian Parmenter Approved: Professor Lee A. Becker
    Project Number: LAB-99MP -.5 / MAJORING IN PIRACY An Interactive Qualifying Project Report submitted to the Faculty of the WORCESTER POLYTECHNIC INSTITUTE In partial fulfillment of the requirements for the Degree of Bachelor of Science by Ian Parmenter Joshua Colson Date: October 15, 1999 Approved: Professor Lee A. Becker, Project Advisor -2- Abstract A look at the state of piracy on college campuses finds that the policies used to inform students just what is acceptable are sorely lacking. These policies are reviewed and analyzed, and a generic policy is put for as being an ideal choice to base college policies off of. A thorough review of literature on campus piracy is given, along with results of surveys on the matter. Table of Contents 1. Introduction 4 2. Background 5 2.1 Organization 5 2.2 Defining Software Piracy 5 2.3 Defining Copyright Piracy 6 2.4 Extent of Campus Software Piracy 6 2.5 Methods of Software Piracy 8 2.6 Methods to Combat Software Piracy 10 2.7 Methods to Combat Copyright Piracy 14 2.8 Arguments over Software Piracy 15 2.9 Conclusion 16 3. Methodology 17 3.1 Literature Search 17 3.2 Student Survey 17 3.3 System Administrator Survey 19 3.4 College Software Policy Analysis 23 3.5 Methodology of the Generic Policy 23 4. Results 24 4.1 Student Survey 24 4.2 College Software Policy Analysis 29 4.3 Ideal Generic Policy 33 5. Conclusion 36 6. Bibliography 37 -4- Introduction The goals of this project are: to provide a review of college policies regarding piracy; to show that the average college policy is lacking in what needs to be included to help stem piracy; to put forward a generic policy that can be used by colleges and universities to help educate students and prevent the spread of piracy.
    [Show full text]
  • An Extreme Programming Method for Innovative Software Based on Systems Design and Its Practical Study
    International Journal of Software Engineering & Applications (IJSEA), Vol.5, No.5, September 2014 EPISODE: AN EXTREME PROGRAMMING METHOD FOR INNOVATIVE SOFTWARE BASED ON SYSTEMS DESIGN AND ITS PRACTICAL STUDY Takaaki Goto 1, Kensei Tsuchida 2 and Tetsuro Nishino 1 1Graduate School of Informatics and Engineering, The University of Electro- Communications, Japan 2Faculty of Information Science and Arts, Toyo University, Japan ABSTRACT In software development, the waterfall model is commonly used, especially for large-scale software systems. For smaller-scale software development, agile software development approaches such as extreme programming or scrum are used. Traditional software development methodologies are mainly targeted toward customer-centric development, and therefore, new software methodologies are often not well received in the industry. In this study, we propose a new software development methodology that is aimed at developing innovative software using artificial intelligence (AI), idea creation, value engineering, and systems design. The name of our method is named as EPISODE (Extreme Programming method for Innovative SOftware based on systems DEsign). EPISODE supports the efficient and creative development of open source software (OSS) by small groups. Moreover we describe an evaluation of EPISODE in a class. KEYWORDS Software Development Methodology, Value Engineering, Open Source Software 1. INTRODUCTION In software development, the waterfall model is commonly used at present. Recent years have, however, witnessed the increasing use of agile software development methodologies, especially for small- or mid-scale projects and even in some large-scale projects. Both the waterfall and agile software development models feature developers and clients, where the developers obtain the project requirements from the clients.
    [Show full text]
  • Schaum's Outline of Software Engineering.Pdf
    Y L F M A E T Team-Fly® Want to learn more? We hope you enjoy this McGraw-Hill eBook! If you’d like more information about this book, its author, or related books and web- sites, please click here. SCHAUM’S OUTLINE OF Theory and Problems of SOFTWARE ENGINEERING This page intentionally left blank. Theory and Problems of SOFTWARE ENGINEERING DAVID A. GUSTAFSON Computing and Information Sciences Department Kansas State University Schaum’s Outline Series McGRAW-HILL New York Chicago San Francisco Lisbon London Madrid Mexico City Milan New Delhi San Juan Seoul Singapore Sydney Toronto McGraw-Hill abc Copyright © 2002 by The McGraw-Hill Companies,Inc. All rights reserved. Manufactured in the United States of America. Except as per- mitted under the United States Copyright Act of 1976, no part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written permission of the publisher. 0-07-140620-4 The material in this eBook also appears in the print version of this title:0-07-137794-8. All trademarks are trademarks of their respective owners. Rather than put a trademark symbol after every occurrence of a trademarked name, we use names in an editorial fashion only, and to the benefit of the trademark owner, with no intention of infringement of the trademark. Where such designations appear in this book, they have been printed with initial caps. McGraw-Hill eBooks are available at special quantity discounts to use as premiums and sales promotions, or for use in corporate train- ing programs.
    [Show full text]
  • Master Thesis Innovation Dynamics in Open Source Software
    Master thesis Innovation dynamics in open source software Author: Name: Remco Bloemen Student number: 0109150 Email: [email protected] Telephone: +316 11 88 66 71 Supervisors and advisors: Name: prof. dr. Stefan Kuhlmann Email: [email protected] Telephone: +31 53 489 3353 Office: Ravelijn RA 4410 (STEPS) Name: dr. Chintan Amrit Email: [email protected] Telephone: +31 53 489 4064 Office: Ravelijn RA 3410 (IEBIS) Name: dr. Gonzalo Ord´o~nez{Matamoros Email: [email protected] Telephone: +31 53 489 3348 Office: Ravelijn RA 4333 (STEPS) 1 Abstract Open source software development is a major driver of software innovation, yet it has thus far received little attention from innovation research. One of the reasons is that conventional methods such as survey based studies or patent co-citation analysis do not work in the open source communities. In this thesis it will be shown that open source development is very accessible to study, due to its open nature, but it requires special tools. In particular, this thesis introduces the method of dependency graph analysis to study open source software devel- opment on the grandest scale. A proof of concept application of this method is done and has delivered many significant and interesting results. Contents 1 Open source software 6 1.1 The open source licenses . 8 1.2 Commercial involvement in open source . 9 1.3 Opens source development . 10 1.4 The intellectual property debates . 12 1.4.1 The software patent debate . 13 1.4.2 The open source blind spot . 15 1.5 Litterature search on network analysis in software development .
    [Show full text]
  • Licensing Information User Manual Oracle® ILOM
    Licensing Information User Manual ® Oracle ILOM Firmware Release 3.2.x October 2018 Part No: E62005-12 October 2018 Licensing Information User Manual Oracle ILOM Firmware Release 3.2.x Part No: E62005-12 Copyright © 2016, 2018, Oracle and/or its affiliates. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government
    [Show full text]
  • Introduction of Software Engineering Concepts for Electrical and Computer Engineering Students and Application to Senior Projects
    Paper ID #29402 Introduction of Software Engineering Concepts for Electrical and Computer Engineering Students and Application to Senior Projects Dr. Danielle Marie Fredette, Cedarville University Danielle Fredette received her Ph.D. degree from The Ohio State University’s College of Engineering (Columbus, OH) in 2017, her M.S. also from The Ohio State Univeristy in 2016, and her B.S.E.E. from Cedarville University (Cedarville, OH) in 2012, during which time she participated in research as an intern at the Air Force Institute of Technology at Wright Patterson Air Force Base, OH, in the Radar Instrumentation Lab. While researching for her Ph.D, she was a University Fellow and then a GATE Fellow with The Ohio State University’s Center for Automotive Research and its Control and Intelligent Transportation Research Lab. She is currently serving as an Assistant Professor of Electrical and Com- puter Engineering at Cedarville University. Research interests include control for multi-agent systems and autonomous ground vehicles. Nathan Jessurun, University of Florida Nathan Jessurun received his B.S. in Computer Engineering from Cedarville University in 2019. Currently he is a PhD candidate at the University of Florida, working toward a degree in Electrical and Computer Engineering. His research interests include x-ray and terahertz wave applications, multi-modal imaging, tomographic reconstruction algorithms, and machine learning applications. c American Society for Engineering Education, 2020 Introduction of Software Engineering Concepts for Electrical and Computer Engineering Students and Application to Senior Projects Danielle M. Fredette, Nathan T. Jessurun Cedarville University Abstract This paper describes results of incorporating basic software engineering principles into the senior design curriculum for electrical and computer engineering students who have no prior software engineering exposure.
    [Show full text]
  • An Environment for Comprehending the Behavior of Software Systems
    An Environment for Comprehending the Behavior of Software Systems A Thesis Submitted to the Faculty of Drexel University by Maher M. Salah in partial fufillment of the requirements for the degree of Doctor of Philosophy July 2005 c Copyright 2005 Maher M. Salah. All Rights Reserved. iii Dedication In memory of my Mother (1935-1992) iv Acknowledgements I would like to express my deepest gratitude and appreciation to my advisor Professor Spiros Mancoridis, who inspired my interest in software engineering and software comprehension. Prof. Mancoridis has spent countless hours of discussions of all aspects of my research. His continuous support, encouragement and guidance are admirable. Also, I would like to thank the other members of my thesis committee: Dr. A. Shokoufandeh, Dr. E. Gansner, Dr. V. Prevelakis, Dr. F. Vokolos for their input and thoughtful feedback. I would like to thank two former committee members, Dr. Hewett and Dr. Souter, for their input and contribution to my work. I would like to thank and recognize Dr. Vokolos, Dr. Shokoufandeh and his graduate student T. Denton for their contribution and the countless discussion sessions I had with them. I am grateful to the National Science Foundation and Lockhead Martin Corporation for sponsoring my equipment and travelling expenses to attend conferences. I would like to express my gratitude and appreciation to the University of Pennsylvania Health System for their sponsorship and the financial support throughout my journey. Also, I would like to thank all members of the Web Applications Group. Specially, I want to recognize Mark Newman and Ying Xing for making work a little bit more fun.
    [Show full text]
  • The Secret Life of Software Communities: What We Know and What We Don’T Know
    The Secret Life of Software Communities: What we know and What we Don't know Gemma Catolino Fabio Palomba Delft University of Technology University of Salerno [email protected] [email protected] Damian A. Tamburri Eindhoven University of Technology and Jheronimus Academy of Data Science (JADS) [email protected] driven civil societies are dense with communities, the software makers are also organized into communities of Abstract practice (e.g., in open-source), of intent (e.g., in stan- dardization groups), of purpose (e.g., as part of agile Communities of software practice are increas- movements). Recent studies showed how the commu- ingly playing a central role in the develop- nity's health can reflect the quality of the software pro- ment, operation, maintenance, and evolution duced [1,2], for this reason the research community has of good-quality software, as well as DevOps tried to deeper analyze and characterize the structure pipelines, lean Organizations and Global Soft- of software communities (i.e., defined as social units ware Development. However, the structures of size, dense strongly-typed and diverse interactions and characteristics behind such communities across diverse roles and fluid characteristics) [3]. are still unknown. For this reason, in this paper, we tried to explore the organizational secret of communities, trying to offer a few In this paper, we discuss about a few basic facts and practical extracts of (1) what we know and observations about the secret life of software commu- is known, (2) what we know to be unknown, nities which we were able to empirically establish over and (3) what we know to be tentatively dis- previous research studies as well as our own practice coverable in the near future from an empiri- as part of software communities themselves.
    [Show full text]
  • The Current State of Software Preservation Nicole Contaxis, National Digital Stewardship Resident at the National Library of Medicine
    Contaxis 1 The Current State of Software Preservation Nicole Contaxis, National Digital Stewardship Resident at the National Library of Medicine Executive Summary Software preservation is an important part of the stewardship of cultural, scientific and social history. This report outlines several ongoing projects and their preservation strategies. While many of these strategies include preserving software as an interactive digital object, strategies that simply document the software, like recording game play in online video games, are also included. The paper begins by outlining key tools and concepts as well as the over-arching obstacles to software preservation, including a lack of contemporaneous documentation, the wide variety of use cases for software, and copyright. Afterwards it discusses three categories of software preservation projects: software collections in libraries and archives, digital art conservation, and computational reproducibility. With in-depth discussions of the benefits and problems with many of these projects, the paper discusses how different strategies best serve different types of software, institutions, and budgets. Both technical and administrative strategies are considered. Projects addressed include the National Software Reference Library (NSRL), the Olive Archive, Emulation as a Service, the work at Rhizome, the Game Play Capture Project at the Strong Museum of Play, the Astrophysics Code Library (ACL), and others. Introduction Preserving software is a vital aspect of the stewardship of cultural, scientific, and social history. The 2015 National Agenda for Digital Stewardship calls for serious action in the realm of software preservation. It states, “[Software] is both the key to accessing and making sense of digital objects and an increasingly important historical artifact in its own right.”1 The document argues that preserving software is necessary for two reasons: (1) it is a cultural artifact worthy of historic study in its own right; and (2) it is a means to access data and content held in obsolete formats.
    [Show full text]