DOCSLIB.ORG

Non-Open Source Licenses

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Non-Open Source Licenses CHAPTER 5 Chapter 5 Non-Open Source Licenses In the previous chapters, we have examined open source and free software licenses, all of which permit, to varying extents, substantial inroads on the protections other- wise available under copyright or patent law. In this chapter, by contrast, we exam- ine one variety of a classic proprietary license, as well as the Sun Community Source licenses and the Microsoft Shared Source Initiative. Classic Proprietary License The classic proprietary license needs relatively little explanation. The license does not need to distinguish, for example, between source and binary code: the source code is simply not made available. The license need not distinguish between distribution of derivative and original works: with one very narrow exception, neither is permitted. Proprietary licenses, like the one described below, may contain “open source” licensed software (under the more permissive licenses, like the MITand BSD Licenses), but the code they license may not be included in any open source project, unless the code is licensed under a parallel non-proprietary license that permits such use. The following license is the creation of the author. It licenses the hypothetical soft- ware of the Mildew Corporation, using terms found in virtually all proprietary licenses. 1. General. The software, documentation and any fonts accompanying this License whether on disk, in read only memory, on any other media or in any other form (col- lectively the “Software”) are licensed, not sold, to you by Mildew Computer, Inc. (“Mildew”) for use only under the terms of this License, and Mildew reserves all rights not expressly granted to you. The rights granted herein are limited to Mildew’s intel- lectual property rights in the Mildew Software and do not include any other patents or intellectual property rights. You own the media on which the Mildew Software is recorded but Mildew and/or Mildew’s licensor(s) retain ownership of the Software itself. 114 This is the Title of the Book, eMatter Edition Copyright © 2004 O’Reilly & Associates, Inc. All rights reserved. This provision provides that the software and associated documentation provided by Mildew are only licensed, not sold, to the consumer. This provision is substantially similar in effect to language used in the open source and free software licenses already described. The only rights granted are those specifically described in the license; all other rights are reserved. The sentence stating that Mildew does not license any property rights other than those that it owns is likely meaningless. By licensing the Software, Mildew is implic- itly representing that it has the authority to license all of its components, whether those components are its own work or not. It seems unlikely that a court would hold that Mildew was not responsible for damages to a consumer arising from infringe- ment if the Software turned out to infringe the intellectual property rights of a third party. After all, given the closed nature of the licensed software, consumers are not allowed to determine for themselves whether the software was infringing, even if they have the inclination or the resources to do so. The second section of the license makes clear the very strict limitations on the use of the software: not only may the end user not distribute the software, he cannot even install more than one copy of it at a time. 2. Permitted License Uses and Restrictions. This License allows you to install and use one (1) copy of the Software on a single device or computer at a time. This License does not allow the Software to exist on more than one such device or computer at a time, and you may not make the Software available over a network where it could be used by multiple devices or multiple computers at the same time. Because of these limitations, every user of the software, whether on a network or oth- erwise, must be individually licensed. This type of restriction is contained in almost every proprietary license and is universally enforced by the courts. The second para- graph continues with a narrow exception to this restriction. You may make one copy of the Software in machine-readable form for backup pur- poses only; provided that the backup copy must include all copyright or other propri- etary notices contained on the original. The next part of this sentence expressly bars any attempt to derive any of the utility of the code for use other than in the licensed Software. Except as and only to the extent expressly permitted in this License or by applicable law, you may not copy, decompile, reverse engineer, disassemble, attempt to derive the source code of, modify, or create derivative works of the Software or any part thereof. Any attempt to do so is a violation of the rights of Mildew and its licensors of the Software. If you breach this restriction, you may be subject to prosecution and damages. Breaching this provision would certainly terminate the license and would render the user liable for damages for further use. Although it is hard to see what damages, if any, Mildew would suffer from such unauthorized use beyond the sales price of another unit of the Software, such use could obviously lead to more substantial forms of infringement through the creation and distribution of derivative works. In Classic Proprietary License | 115 This is the Title of the Book, eMatter Edition Copyright © 2004 O’Reilly & Associates, Inc. All rights reserved. addition, reverse engineering or otherwise trying to derive the source code from soft- ware could violate U.S. copyright law or the Digital Millennium Copyright Act. Such source code certainly could not be used or distributed in any event, without violat- ing the civil and criminal laws of the United States. The final provision is a special disclaimer of liability, noting that the Software is not intended for use in high-risk applications. THE SOFTWARE IS NOT INTENDED FOR USE IN WHICH THE FAILURE OF THE SOFTWARE COULD LEAD TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE. The third section bars transfers or sales of the licensed software, except for the exception provided under law by the first-sale doctrine, which permits users to sell the rights acquired by license along with the physical medium, regardless of the terms under which the work was originally acquired. 3. Transfer. You may not rent, lease, lend or sublicense the Software. You may, how- ever, make a one-time permanent transfer of all of your license rights to the Software to another party, provided that: (a) the transfer must include all of the Software, including all its component parts, original media, printed materials and this License; (b) you do not retain any copies of the Software, full or partial, including copies stored on a computer or other storage device; and (c) the party receiving the Software reads and agrees to accept the terms and conditions of this License. This paragraph does not grant any rights to the licensee that he or she would not otherwise have by operation of law. Like most of the open source and free software licenses already examined, the license provides for automatic termination upon any breach of the license. 4. Termination. This License is effective until terminated. Your rights under this License will terminate automatically without notice from Mildew if you fail to comply with any term(s) of this License. Upon the termination of this License, you shall cease all use of the Mildew Software and destroy all copies, full or partial, of the Mildew Software. However, because the rights granted by the license are so limited in the first place, the effects of the termination are not likely to be severe, at least for programs pur- chased by individual consumers. As already noted, the measure of damages for con- tinuing use of the licensed program is not likely to be greater than the sales price of the Software. It should be noted, however, that U.S. copyright laws provide for potentially severe penalties for unlawful distribution of copyrighted material, includ- ing punitive damages. The fifth section provides a limited warranty for the medium on which the code of the Software is carried. Commercial software usually carries at least this minimal a warranty. 5. Limited Warranty on Media. Mildew warrants the media on which the Software is recorded and delivered by Mildew to be free from defects in materials and workman- ship under normal use for a period of ninety (90) days from the date of original retail 116 | Chapter 5: Non-Open Source Licenses This is the Title of the Book, eMatter Edition Copyright © 2004 O’Reilly & Associates, Inc. All rights reserved. purchase. Your exclusive remedy under this Section shall be, at Mildew’s option, either a refund of the purchase price of the product containing the Software or replace- ment of the Software which is returned to Mildew. THIS LIMITED WARRANTY AND ANY IMPLIED WARRANTIES ON THE MEDIA INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND OF FITNESS FOR A PARTICULAR PURPOSE, ARE LIMITED IN DURATION TO NINETY (90) DAYS FROM THE DATE OF ORIGINAL RETAIL PURCHASE. SOME JURISDICTIONS DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. THE LIMITED WARRANTY SET FORTH HEREIN IS THE ONLY WAR- RANTY MADE TO YOU AND IS PROVIDED IN LIEU OF ANY OTHER WARRAN- TIES (IF ANY) CREATED BY ANY DOCUMENTATION OR PACKAGING. THIS LIMITED WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS, AND YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY BY JURISDICTION. The following provisions restate the same limitations articulated by the second to last sentence of the fifth paragraph: Mildew disclaims all responsibility for any dam- ages caused by the Software, except to the extent it is prohibited from doing so by law.
Load more

Recommended publications
  • Open Source Software Vs Proprietary Software Sakshi Singh, Madhvik Verma, Naveen Kumar N
    International Journal of Scientific & Engineering Research Volume 8, Issue 12, December-2017 735 ISSN 2229-5518 Open Source Software Vs Proprietary Software Sakshi Singh, Madhvik Verma, Naveen Kumar N Abstract— Open Source software are the most revolutionizing concept that has been put forth in the Information Technology spectrum. This new release has raised quite a lot of brows, similar to when the Internet was launched. For a very long time, there has been a tiff going on between the Proprietary software and the open source software and how the open source software are taking over their ancestors. The technical experts often indulge in conversations as to which of the two software is better and why. People also get confused as to which type of software can be listed as Open source. In this paper we aim to emphasize that the open source development cycle has been there in the market for quite some time and has a huge user base now, thus giving it a strong hold in the software market. It has encouraged the use of new strategically placed actions which has in turn made a huge base for open source software systems. On the other hand, many experts also suggest that this is just momentary and it will pass over a period of time whereas the proprietary software are there to stay. This paper gives the understanding and recommendations for both the kind of software thus giving the user a proper understanding of which software is suitable for their use and thus they can make a better choice for their purpose.
    [Show full text]
  • End User License Agreement
    MICROSOFT SOFTWARE LICENSE TERMS WINDOWS EMBEDDED STANDARD 7 These license terms are an agreement between you and YSI incorporated. Please read them. They apply to the software included on this device. The software also includes any separate media on which you received the software. The software on this device includes software licensed from Microsoft Corporation or its affiliate. The terms also apply to any Microsoft • updates, • supplements, • Internet-based services, and • support services for this software, unless other terms accompany those items. If so, those terms apply. If you obtain updates or supplements directly from Microsoft, then Microsoft, and not YSI incorporated, licenses those to you. As described below, using the software also operates as your consent to the transmission of certain computer information for Internet-based services. By using the software, you accept these terms. If you do not accept them, do not use the software. Instead, contact YSI incorporated to determine its return policy for a refund or credit. If you comply with these license terms, you have the rights below. 1. USE RIGHTS Use. The software license is permanently assigned to the device with which you acquired the software. You may use the software on the device. 2. ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS a. Specific Use. YSI incorporated designed the device for a specific use. You may only use the software for that use. b. Other Software. You may use other programs with the software as long as the other programs directly supports the manufacturer’s specific use for the device, or provide system utilities, resource management, or anti-virus or similar protection.
    [Show full text]
  • ¢¡¤ £¦ ¥ ¡ £ ¥ ¡ £ ¥ ¡ £ ¥ Red Hat §© ¨ / ! " #%$'& ( ) 0 1! 23 % 4'5 6!7 8 9 @%
    ¢¡¤£¦¥ ¢¡¤£¦¥ ¢¡¤£¦¥ Subscription Agreement ¢¡¤£¦¥ ! PLEASE READ THIS AGREEMENT CAREFULLY BEFORE Red Hat §©¨ / PURCHASING OR USING RED HAT PRODUCTS AND "# $% &' ()*+ §©¨ ,- . Red Hat / # # SERVICES. BY USING OR PURCHASING RED HAT # 2©3 456 7 80 9: /.10 PRODUCTS OR SERVICES, CLIENT SIGNIFIES ITS ASSENT ;< 2=©>0 ?@ 'A BC© DE F©G ?1 . TO THIS AGREEMENT. IF YOU ARE ACTING ON BEHALF HI BC© D©: J !K CLM NO1 (P4 Q1RK HI OF AN ENTITY, THEN YOU REPRESENT THAT YOU HAVE STU >0 VWK XY Z1K F©G THE AUTHORITY TO ENTER INTO THIS AGREEMENT ON . 456 , §©¨ ,- M X [!\>0 BEHALF OF THAT ENTITY. IF CLIENT DOES NOT ACCEPT 45©3 Red Hat / THE TERMS OF THIS AGREEMENT, THEN IT MUST NOT PURCHASE OR USE RED HAT PRODUCTS AND SERVICES. @ = ©] ^ _`a b c d e e f gf g 3 e f gf g This Subscription Agreement, including all schedules and e (“ ”) Red Hat Limited hi appendices hereto (the "Agreement"), is between Red Hat # Y j § VWK X k (“Red Hat”) ] Red Hat Limited, Korea Branch ("Red Hat") and the purchaser or user of # §©¨ ©9 9 l ml m n CLo0 l m / (“ l m ”) . Red Hat products and services that accepts the terms of this # pq/r stvustvu 3 456 w,- stvustvu (“ ”) h h Agreement (“Client”). The effective date of this Agreement # !K X k r!9x 456 §©¨ Red Hat / (“Effective Date”) is the earlier of the date that Client signs or h 0 y z{ + |} accepts this Agreement or the date that Client uses Red Hat's r!9 . products or services.
    [Show full text]
  • Shared Source Licensing Program for the Windows Embedded Compact (Formerly Windows CE) Platform
    9/6/2020 Shared Source Initiative | Licensing Program for the Windows Embedded Compact Platform Search Microsoft.com PRODUCTS STORE DOWNLOADS SUPPORT United States Shared Source Initiative > Windows Embedded Compact Source Licensing Program Shared Source Licensing Program for the Windows® Embedded Compact (formerly Windows CE) Platform Shared Source Licensing Programs Overview Microsoft offers a Shared Source licensing program for the Windows Embedded Compact (formerly Windows CE) platform. This program is applicable to the Windows Embedded Compact and Windows Embedded CE products. The Windows Embedded Shared Source program helps OEMs and developers speed development, reduce troubleshooting and code debugging time, receive assistance in remote device support and gain a deeper technical understanding of Windows Embedded Compact software. Public/Sample Source code is built at no additional cost into the purchased copies of the Windows Embedded Compact Platform Builder toolkit and provides access to nearly 4 million lines of code. Depending on a partner’s needs and qualifications, deeper levels of Shared Source code access (Private and Premium) are available. How to Participate Public/Sample Shared Source Public/Sample Shared Source code is available at no additional cost with each purchased copy of the Windows Embedded Compact 7 Platform Builder toolkit. Private Shared Source Private Shared Source Code is an optional component of the Windows Embedded Compact 7 Platform Builder toolkit that can be installed during the setup process. The toolkit user must electronically accept the terms and conditions of the Shared Source licensing agreement (EULA) before the Private source code can be installed. Premium Derivatives Program Microsoft also offers Premium access to advanced Windows Embedded Compact 7 source code through the Premium Derivatives licensing program.
    [Show full text]
  • Software Licensing in the Cloud Age Solving the Impact of Cloud Computing on Software Licensing Models
    The International Journal of Soft Computing and Software Engineering [JSCSE], Vol. 3, No. 3, Special Issue: The Proceeding of International Conference on Soft Computing and Software Engineering 2013 [SCSE’13], San Francisco State University, CA, U.S.A., March 2013 Doi: 10.7321/jscse.v3.n3.60 e-ISSN: 2251-7545 Software Licensing in the Cloud Age Solving the Impact of Cloud Computing on Software Licensing Models Malcolm McRoberts Enterprise Architecture Core Technology Center Harris Corporation GCSD Melbourne, Florida, USA [email protected] Abstract—Cloud computing represents a major shift in identify key issues that require the attention of the industry information systems architecture, combining both new as a whole. deployment models and new business models. Rapid provisioning, elastic scaling, and metered usage are essential A. Characteristics of Cloud Computing (Benefits) characteristics of cloud services, and they require cloud According to the National Institute of Standards and resources with these same characteristics. When cloud services Technology (NIST) [1], cloud computing is a model for depend on commercial software, the licenses for that software enabling ubiquitous, convenient, on-demand network access become another resource to be managed by the cloud. This to a shared pool of configurable computing resources (e.g., paper examines common licensing models, including open networks, servers, storage, applications, and services) that source, and how well they function in a cloud services model. It can be rapidly provisioned and released with minimal discusses creative, new, cloud-centric licensing models and how management effort or service provider interaction. they allow providers to preserve and expand their revenue This translates to a number of benefits for large and small streams as their partners and customers transition to the organizations alike, as well as for individuals.
    [Show full text]
  • Building Online Content and Community with Drupal
    Collaborative Librarianship Volume 1 Issue 4 Article 10 2009 Building Online Content and Community with Drupal Gabrielle Wiersma University of Colorado at Boulder, [email protected] Follow this and additional works at: https://digitalcommons.du.edu/collaborativelibrarianship Part of the Collection Development and Management Commons Recommended Citation Wiersma, Gabrielle (2009) "Building Online Content and Community with Drupal," Collaborative Librarianship: Vol. 1 : Iss. 4 , Article 10. DOI: https://doi.org/10.29087/2009.1.4.10 Available at: https://digitalcommons.du.edu/collaborativelibrarianship/vol1/iss4/10 This Review is brought to you for free and open access by Digital Commons @ DU. It has been accepted for inclusion in Collaborative Librarianship by an authorized editor of Digital Commons @ DU. For more information, please contact [email protected],[email protected]. Wiersma: Building Online Content and Community with Drupal Building Online Content and Community with Drupal Gabrielle Wiersma ([email protected]) Engineering Research and Instruction Librarian, University of Colorado at Boulder Libraries use content management systems Additionally, all users are allowed to post in order to create, manage, edit, and publish content without using code, which enables content on the Web more efficiently. Drupal less tech savvy users to contribute content (drupal.org), one such Web-based content just as easily as their more proficient coun- management system, is unique because it terparts. For example, a library could use employs a bottom-up strategy for Web de- Drupal to allow library staff to view and sign that separates the content of the site edit the library Web site, blog, and staff from the formatting which means that “you intranet.
    [Show full text]
  • Unravel Data Systems Version 4.5
    UNRAVEL DATA SYSTEMS VERSION 4.5 Component name Component version name License names jQuery 1.8.2 MIT License Apache Tomcat 5.5.23 Apache License 2.0 Tachyon Project POM 0.8.2 Apache License 2.0 Apache Directory LDAP API Model 1.0.0-M20 Apache License 2.0 apache/incubator-heron 0.16.5.1 Apache License 2.0 Maven Plugin API 3.0.4 Apache License 2.0 ApacheDS Authentication Interceptor 2.0.0-M15 Apache License 2.0 Apache Directory LDAP API Extras ACI 1.0.0-M20 Apache License 2.0 Apache HttpComponents Core 4.3.3 Apache License 2.0 Spark Project Tags 2.0.0-preview Apache License 2.0 Curator Testing 3.3.0 Apache License 2.0 Apache HttpComponents Core 4.4.5 Apache License 2.0 Apache Commons Daemon 1.0.15 Apache License 2.0 classworlds 2.4 Apache License 2.0 abego TreeLayout Core 1.0.1 BSD 3-clause "New" or "Revised" License jackson-core 2.8.6 Apache License 2.0 Lucene Join 6.6.1 Apache License 2.0 Apache Commons CLI 1.3-cloudera-pre-r1439998 Apache License 2.0 hive-apache 0.5 Apache License 2.0 scala-parser-combinators 1.0.4 BSD 3-clause "New" or "Revised" License com.springsource.javax.xml.bind 2.1.7 Common Development and Distribution License 1.0 SnakeYAML 1.15 Apache License 2.0 JUnit 4.12 Common Public License 1.0 ApacheDS Protocol Kerberos 2.0.0-M12 Apache License 2.0 Apache Groovy 2.4.6 Apache License 2.0 JGraphT - Core 1.2.0 (GNU Lesser General Public License v2.1 or later AND Eclipse Public License 1.0) chill-java 0.5.0 Apache License 2.0 Apache Commons Logging 1.2 Apache License 2.0 OpenCensus 0.12.3 Apache License 2.0 ApacheDS Protocol
    [Show full text]
  • Open Source Software Notice
    Open Source Software Notice This document describes open source software contained in LG Smart TV SDK. Introduction This chapter describes open source software contained in LG Smart TV SDK. Terms and Conditions of the Applicable Open Source Licenses Please be informed that the open source software is subject to the terms and conditions of the applicable open source licenses, which are described in this chapter. | 1 Contents Introduction............................................................................................................................................................................................. 4 Open Source Software Contained in LG Smart TV SDK ........................................................... 4 Revision History ........................................................................................................................ 5 Terms and Conditions of the Applicable Open Source Licenses..................................................................................... 6 GNU Lesser General Public License ......................................................................................... 6 GNU Lesser General Public License ....................................................................................... 11 Mozilla Public License 1.1 (MPL 1.1) ....................................................................................... 13 Common Public License Version v 1.0 .................................................................................... 18 Eclipse Public License Version
    [Show full text]
  • Arxiv:1812.09167V1 [Quant-Ph] 21 Dec 2018 It with the Tex Typesetting System Being a Prime Example
    Open source software in quantum computing Mark Fingerhutha,1, 2 Tomáš Babej,1 and Peter Wittek3, 4, 5, 6 1ProteinQure Inc., Toronto, Canada 2University of KwaZulu-Natal, Durban, South Africa 3Rotman School of Management, University of Toronto, Toronto, Canada 4Creative Destruction Lab, Toronto, Canada 5Vector Institute for Artificial Intelligence, Toronto, Canada 6Perimeter Institute for Theoretical Physics, Waterloo, Canada Open source software is becoming crucial in the design and testing of quantum algorithms. Many of the tools are backed by major commercial vendors with the goal to make it easier to develop quantum software: this mirrors how well-funded open machine learning frameworks enabled the development of complex models and their execution on equally complex hardware. We review a wide range of open source software for quantum computing, covering all stages of the quantum toolchain from quantum hardware interfaces through quantum compilers to implementations of quantum algorithms, as well as all quantum computing paradigms, including quantum annealing, and discrete and continuous-variable gate-model quantum computing. The evaluation of each project covers characteristics such as documentation, licence, the choice of programming language, compliance with norms of software engineering, and the culture of the project. We find that while the diversity of projects is mesmerizing, only a few attract external developers and even many commercially backed frameworks have shortcomings in software engineering. Based on these observations, we highlight the best practices that could foster a more active community around quantum computing software that welcomes newcomers to the field, but also ensures high-quality, well-documented code. INTRODUCTION Source code has been developed and shared among enthusiasts since the early 1950s.
    [Show full text]
  • An Introduction to Malware
    Downloaded from orbit.dtu.dk on: Sep 24, 2021 An Introduction to Malware Sharp, Robin Publication date: 2017 Document Version Publisher's PDF, also known as Version of record Link back to DTU Orbit Citation (APA): Sharp, R. (2017). An Introduction to Malware. General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. Users may download and print one copy of any publication from the public portal for the purpose of private study or research. You may not further distribute the material or use it for any profit-making activity or commercial gain You may freely distribute the URL identifying the publication in the public portal If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. An Introduction to Malware Robin Sharp DTU Compute Spring 2017 Abstract These notes, written for use in DTU course 02233 on Network Security, give a short introduction to the topic of malware. The most important types of malware are described, together with their basic principles of operation and dissemination, and defenses against malware are discussed. Contents 1 Some Definitions............................2 2 Classification of Malware........................2 3 Vira..................................3 4 Worms................................
    [Show full text]
  • Open Source Licensing Information for Cisco IOS Release 15.4(1)T
    Open Source Used In Cisco IOS Release 15.4(1)T Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-15140077 Open Source Used In Cisco IOS Release 15.4(1)T 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-15140077 Contents 1.1 bzip2 1.0.0 1.1.1 Available under license 1.2 C/C++ BEEP Core 0.2.00 1.2.1 Available under license 1.3 cd9660 8.18 1.3.1 Available under license 1.4 cthrift-without-GPL-code 0.3.14 1.4.1 Available under license 1.5 CUDD: CU Decision Diagram Package v2.4.1 1.5.1 Available under license 1.6 Cyrus SASL 2.1.0 1.6.1 Notifications 1.6.2 Available under license 1.7 DTOA unknown 1.7.1 Available under license 1.8 editline 1.11 1.8.1 Available under license 1.9 Expat XML Parser - Series 1 v1.2 1.9.1 Available under license 1.10 freebsd-tty-headers n/a 1.10.1 Available under license 1.11 ftp.h 4.4BSD? 1.11.1 Available under license 1.12 inflate.c c10p1 1.12.1 Available under license 1.13 iniparser 2.8 Open Source Used In Cisco IOS
    [Show full text]
  • Understanding Code Forking in Open Source Software
    EKONOMI OCH SAMHÄLLE ECONOMICS AND SOCIETY LINUS NYMAN – UNDERSTANDING CODE FORKING IN OPEN SOURCE SOFTWARE SOURCE OPEN IN FORKING CODE UNDERSTANDING – NYMAN LINUS UNDERSTANDING CODE FORKING IN OPEN SOURCE SOFTWARE AN EXAMINATION OF CODE FORKING, ITS EFFECT ON OPEN SOURCE SOFTWARE, AND HOW IT IS VIEWED AND PRACTICED BY DEVELOPERS LINUS NYMAN Ekonomi och samhälle Economics and Society Skrifter utgivna vid Svenska handelshögskolan Publications of the Hanken School of Economics Nr 287 Linus Nyman Understanding Code Forking in Open Source Software An examination of code forking, its effect on open source software, and how it is viewed and practiced by developers Helsinki 2015 < Understanding Code Forking in Open Source Software: An examination of code forking, its effect on open source software, and how it is viewed and practiced by developers Key words: Code forking, fork, open source software, free software © Hanken School of Economics & Linus Nyman, 2015 Linus Nyman Hanken School of Economics Information Systems Science, Department of Management and Organisation P.O.Box 479, 00101 Helsinki, Finland Hanken School of Economics ISBN 978-952-232-274-6 (printed) ISBN 978-952-232-275-3 (PDF) ISSN-L 0424-7256 ISSN 0424-7256 (printed) ISSN 2242-699X (PDF) Edita Prima Ltd, Helsinki 2015 i ACKNOWLEDGEMENTS There are many people who either helped make this book possible, or at the very least much more enjoyable to write. Firstly I would like to thank my pre-examiners Imed Hammouda and Björn Lundell for their insightful suggestions and remarks. Furthermore, I am grateful to Imed for also serving as my opponent. I would also like to express my sincere gratitude to Liikesivistysrahasto, the Hanken Foundation, the Wallenberg Foundation, and the Finnish Unix User Group.
    [Show full text]