DOCSLIB.ORG

From Proprietary to Open Source, a Case Study of Citrix Xenserver

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
From Proprietary to Open Source, a Case Study of Citrix Xenserver FROM PROPRIETARY TO OPEN SOURCE, A CASE STUDY OF CITRIX XENSERVER Harm Roelof Pieters s1537687 - [email protected] MarCH 25, 2014 Master THESIS INDUSTRIAL Engineering AND Management Faculty OF Mathematics AND NaturAL Sciences University OF GrONINGEN Supervisors PRof. dr. ir. M. Aiello University OF GrONINGEN dr. ir. I.ten Have, MBA University OF GrONINGEN M. McClurG Citrix ResearCH AND DeVELOPMENT ExECUTIVE SUMMARY Open SOURCE IS AN INDISPENSABLE PART OF THE SOFTWARE INDUSTRY, AND IS GROWING AS AN ATTRACTIVE AND VIABLE STRATEGIC OPTION FOR COMMERCIAL Exploitation. Organizations, WITH AN EXISTING PROPRIETARY PRODUCT AND THE DESIRE TO SWITCH TO AN OPEN SOURCE STRATEGY, ARE REQUIRED TO UNDERGO A TRANSITION PROFOUNDLY IMPACTING THE ORganization. The FOLLOWING DOCUMENT PRESENTS THE STUDY INTO THE INITIAL STAGES OF THE TRANSITION OF XenServer TOWARDS OPEN SOURce, CONDUCTED AT Citrix ResearCH AND Development. IN ORDER TO PROVIDE THE ORGANIZATION WITH A PROCESS ON HOW TO PROCEED WITH THE OPEN SOURcing, GIVEN THE ORGANIZATIONAL goals. ResearCH IN THE fiELD OF TRANSITIONING TO OPEN SOURCE IS limited, AND IN ORDER TO GAIN INSIGHTS EXISTING LITERATURE ON OPEN SOURCE PROJECTS IS GATHERed. Resulting IN A SEGMENTATION OF TRANSITION PROJECTS IN CHARac- teristics, PROVIDING A SEGMENTED STRUCTURE TO THE STUDY. The CHARACTERISTICS ARE LEGALITY, COMMUNITY, PROCESS, INFRASTRUCTURE, SOFTWARE, COMMUNITY, MARKETING, BUSINESS MODEL AND MOTIVATION. IN ADDITION TO THE LITERATURE CASE STUDIES ON HISTORICAL TRANSITIONS TO OPEN SOURCE AND RELATED WORK ARE GATHERED IN ORDER TO ANALYSE THE CURRENT STATE OF THE ORganization. The ANALYSIS OF THE ORGANIZATION IS CONDUCTED THROUGH A CASE STUDY OF THE CURRENT STATE OF THE TRansition, BASED ON THE CHARACTERISTICS AND THE EXISTING LITERATURE AND CASE studies. The RESULT IS AN OVERVIEW OF im- PROVEMENT AReas, MOST NOTABLY THE COMMUNITY AND ITS ACTIVITY AND GROwth. Further RESULTS SUGGEST A MORE TRANSPARENT ORganization, PROVIDING INFORMATION AND DOCUMENTATION TO THE public. Maintain ACTIVITY WITHIN THE EXISTING COMMUNITY AND IMPLEMENT INFRASTRUCTURE TO FACILITATE BUG TRACKING AND documentation. Selec- TION OF AN EXISTING TARGET COMMUNITY TO ACT AS ROLE model, ALLOWING AMONGST OTHERS THE IMPLEMENTATION OF GOVERNANCE STRUCTURes. The INFORMATION IS COMBINED TO PRESENT A TRANSITION PROCESS FOR THE ORganization, DIVIDED INTO THREE PHASES IN ACCORDANCE TO PRIORITY. The fiRST PHASE INCLUDES MAKING DECISIONS AND IMPLEMENTING INFRastruc- TURE, IN ADDITION THE ADJUSTMENT OF THE INTERNAL PROCESSES AND PUBLICIZINGINFORMATION IS initiated. The SECOND PHASE CONSISTS OF CREATION AND PUBLICATION OFDOCUMENTATION, THE REMAINDER OF PROCESSES AND INFORMATION AND THE fiRST PART OF COLLABORATION INITIATING BETWEEN ORGANIZATION AND COMMUNITY. Lastly, THE fiNAL PHASE INCLUDES THE WEBSITE AND THE fiNAL SECTION OF COLLABORATION. PrODUCT IMPROVEMENTS AND Metrics GATHERING SPAN THE THREE PHASES OF THE PRocess, BEGINNING AT THE fiRST phase. The PROPOSED PROCESS IS THE contribu- TION OF THE STUDY TO THE ORganization, WHILST THE CASE STUDY AND METHODOLOGICAL PROCESS CONTRIBUTE TO THE UNDERSTANDING OF THE OPENING OF PROPRIETARY SOFTWARE fiELD IN FLOSS RESEARch. KeYWORds: Open SOURce, Opening PROPRIETARY SOFTWARe, Open SourCE CHARacteristics, Open SOURCE engi- neering, FLOSS. II PrEFACE The DOCUMENT PRESENTED HERE IS THE RESULT OF MY MASTER THESIS RESEARCH FOR "INDUSTRIAL Engineering AND Management - INFORMATION Engineering" CONDUCTED AT Citrix ResearCH AND Development. IN THE PREFACE I WOULD LIKE TO TAKE THE OPPORTUNITY TO THANK THE PEOPLE WHO MADE MY RESEARCH possible. First I WOULD LIKE TO THANK MY supervisors, PRof. dr. MarCO Aiello, FOR TAKING ME ON AS A STUDENT AND PROVIDING ME WITH SUPPORT THROUGHOUT THE RESEARch, AND dr. ir. INGRID TEN Have FOR PROVIDING ME WITH THE OPPORTUNITY OF DOING MY MASTER THESIS ABROAD AT Citrix AND THE DIffERENT INSIGHTS AND feedback. Second I WOULD LIKE TO THANK Citrix ResearCH AND Development, AND AndrEW HalleY FOR PROVIDING THE OPPORTUNITY OF PERFORMING MY MASTER THESIS AND GIVING INITIAL DIRections. Special THANKS GOES OUT TO MikE McClurG FOR BEING MY MENTOR THROUGHOUT MY PERIOD IN Cambridge. During OUR WEEKLY MEETINGS YOU PRo- VIDED ME WITH DIffERENT perspective, discussions, INTERESTS AND KEPT ME SANE DURING THE PRocess. Last, BUT DEfiNITELY NOT least, I WOULD LIKE TO THANK MY PARENTS FOR THEIR UNCONDITIONAL SUPPORT DURING THE RESEARCH AND MY ENTIRE TIME AS A student. Harrie Pieters - MarCH 2014 III TABLE OF Contents List OF TABLES VI List OF FigurES VI 1 INTRODUCTION 1 1.1 Citrix ResearCH AND DeVELOPMENT . .1 1.2 State OF THE ART . .1 1.3 PrOBLEM . .2 1.4 Contribution . .2 1.5 Document STRUCTURE . .3 2 BackgrOUND 4 2.1 PrOPRIETARY . .5 2.2 Open SOURCE . .5 2.3 Summary . .8 3 Related WORK 9 3.1 OSCOMM FRAMEWORK . .9 3.2 Open SOURCE STRATEGIES . 12 3.3 Release PrOCESS . 13 3.4 Summary . 14 4 PrOBLEM STATEMENT 15 4.1 PrOBLEM DefiNITION . 15 4.2 PrOBLEM Analysis . 16 4.3 StakEHOLDERS . 17 4.4 Goal & RESEARCH QUESTION . 19 4.5 Conceptual MODEL . 20 4.6 ResearCH sub-questions . 22 4.7 Methodology . 23 4.8 ResearCH PROCESS . 24 5 LiterATURE 26 5.1 Open SOURCE CHARACTERISTICS . 26 5.2 State OF THE ART ON CHARACTERISTICS . 26 5.3 Case STUDIES . 35 6 Citrix RESEARCH AND DeVELOPMENT CASE STUDY 46 6.1 OrGANIZATION . 46 6.2 Business Model . 48 6.3 CharACTERISTICS . 49 6.4 FuturE ORGANIZATIONAL CONSIDERATIONS . 55 IV 7 Analysis 58 7.1 INTRODUCTION . 58 7.2 Motivation . 58 7.3 Business Model . 59 7.4 CharACTERISTICS . 60 7.5 Summary . 67 8 TRANSITION 70 8.1 INTRODUCTION . 70 8.2 PrOCESS . 70 8.3 Discussion . 76 9 Results 78 9.1 KeY Findings . 78 9.2 OrGANIZATIONAL GOALS . 81 9.3 ResearCH GOALS . 82 9.4 VALIDATION . 82 10 Conclusion 84 10.1 Discussion . 84 10.2 Further ResearCH . 85 11 ReferENCES 86 Appendices 90 Glossary 91 A OrGANIZATION DESCRIPTION 94 1.1 Citrix ResearCH AND DeVELOPMENT . 94 1.2 XenServer . 95 1.3 StrATEGY . 97 1.4 TEAMS . 99 B Release PROCESS 101 V List OF TABLES 2.1 A SoftwarE Licensing TAXONOMY [17, p. 60]. .7 3.1 Release Readiness Rating (R3) FrAMEWORK [26]. 10 3.2 Community WATCHDOG MeasurEMENTS [26]. 12 3.3 IMPORTANT MeasurES TO AchieVE Success [16][p. 55-65] . 13 5.1 TECHNOLOGICAL motivations. 27 5.2 Economical motivations. 28 5.3 OvervieW OF MOST COMMON USED LICENSES IS Open SourCE (OS). 31 List OF FigurES 2.1 Continuum OF GOVERNANCE IN SOFTWARE PROJECTS [7, 15, 43, 54, 57]. .4 3.1 Elements OF OSS Community Building [52, p. 59]. .9 3.2 OSCOMM FRAMEWORK PHASES [26, p. 1470]. 10 3.3 Conceptual FrAMEWORK FOR Open SourCE Engineering [51, p. 4] . 11 4.1 Conceptual Model . 21 4.2 RegulatieVE CYCLUS OF VAN Strien (VAN AkEN ET al., P 13) . 23 4.3 ResearCH PROCESS ILLUSTRated. 24 5.1 Community BUILDING DIMENSIONS [26, p. 1468]. 26 5.2 License DECISION MODEL [33, p. 34]. 31 6.1 XenServer MOVING FROM A PROPRIETARY TO SPONSORED OS. 47 7.1 Analysis PROCESS OF THE OPEN SOURCING AT Citrix ResearCH AND DeVELOPMENT (Citrix R&D). 58 8.1 TRANSITION PROCESS DIVIDED IN PHASES AND actions. 71 9.1 TRANSITION PROCESS OF THE ORganization. 78 VI 1. INTRODUCTION Open SOURCE (OS) IS EVERYWHERe. IT IS USED TO RUN SMART PHONES (e.g. Android), SERVERS (e.g. Linux, Apache, MySQL), EMBEDDED DEVICES (e.g. Java), BROWSERS (e.g. MoZILLA FirEFOx) AND MUCH MORe. As A RESULT A ma- JORITY OF THE WORLDWIDE ORGANISATIONS ARE NOW DEPENDING ON SOME FORM OF Open SourCE SoftwarE (OSS) FOR MISSION CRITICAL PRocesses, AN EXAMPLE IS THE Mars ExplorATION RoVER [40]. The adoption, IN COMBINATION WITH THE CURRENT ECONOMICAL DECLINE [27] AND PROPERTIES AS flEXIBILITY, EASY INTEGRATION AND SECURITY [11], IS PUSHING THE EMBRACE OF OPEN SOURCE OVER PROPRIETARY PRODUCTS IN THE MARKet. Resulting IN A FUNDAMENTAL IMPACT ON THE CReation, DISTRIBUTION AND USE OF SOFTWARE [8]. The PHENOMENON IN THE MARKET DOES NOT APPEAR TO BE SLOWING DOwn, OSS IS GROWING AND AS MORE OS PROJECT EMERge, COMMERCIAL ORGANISATIONS ARE STARTING TO INCREASINGLY COMMERCIALISE OPEN SOURCE PRojects. The HISTORIC SITUATION WHERE OSS IS EXCLUSIVELY DEVELOPED BY VOLUNTEERS IS NO LONGER ACCURate. The INITIAL COMMERCIAL PARADOx, HOW A COMMERCIAL ORGANISATION CAN EARN MONEY WHEN IT IS OffERING.
Load more

Recommended publications
  • State of the Art of Libraries in Python and Ruby
    STATE OF THE ART OF SOAP LIBRARIES IN PYTHON AND RUBY Pekka Kanerva Helsinki Institute for Information Technology August 6, 2007 HIIT TECHNICAL REPORT 2007-02 State of the Art of SOAP Libraries in Python and Ruby Pekka Kanerva Helsinki Institute for Information Technology HIIT Technical Reports 2007-2 ISSN 1458-9478 Copyright c 2007 held by the authors. Notice: The HIIT Technical Reports series is intended for rapid dissemination of articles and papers by HIIT authors. Some of them will be published also elsewhere. ii State of the Art of SOAP Libraries in Python and Ruby Pekka Kanerva <[email protected]> Helsinki Institute for Information Technology August 6, 2007 Abstract Web services are gaining more and more attention in the business field and in the academic research. Simple Object Access Protocol (SOAP) is the stan- dard messaging format for Web services. The single services are described in Web Services Description Language (WSDL). More recently, the REST architecture specified by Roy T. Fielding has received more attention in cre- ating better Web services. This technical report describes our experiments on building simple, composable Web services. We describe our findings on us- ing both Python and Ruby SOAP libraries for prototyping. A simple REST interface is created for a commercial Web service called SyncShield. Chapter 1 Introduction The ITEA Services for all (S4All) research project aimed to create a world of easy-to-use, easy-to-share, and easy-to-develop services from a user point of view. S4All describes a visionary software component called a Service Composer which is used to combine public small-scale web-services into a more complex series of meaningful series of simple tasks enqueued into a workflow.
    [Show full text]
  • Ubuntu Unleashed 2013 Edition: Covering 12.10 and 13.04
    Matthew Helmke with Andrew Hudson and Paul Hudson Ubuntu UNLEASHED 2013 Edition 800 East 96th Street, Indianapolis, Indiana 46240 USA Ubuntu Unleashed 2013 Edition Editor-in-Chief Copyright © 2013 by Pearson Education, Inc. Mark Taub All rights reserved. No part of this book shall be reproduced, stored in a retrieval Acquisitions Editor system, or transmitted by any means, electronic, mechanical, photocopying, record- Debra Williams ing, or otherwise, without written permission from the publisher. No patent liability is assumed with respect to the use of the information contained herein. Although every Cauley precaution has been taken in the preparation of this book, the publisher and author Development Editor assume no responsibility for errors or omissions. Nor is any liability assumed for damages resulting from the use of the information contained herein. Michael Thurston ISBN-13: 978-0-672-33624-9 Managing Editor ISBN-10: 0-672-33624-3 Kristy Hart Project Editor The Library of Congress cataloging-in-publication data is on file. Jovana Shirley Printed in the United States of America Copy Editor First Printing December 2012 Charlotte Kughen Trademarks Indexer All terms mentioned in this book that are known to be trademarks or service marks have Angie Martin been appropriately capitalized. Sams Publishing cannot attest to the accuracy of this information. Use of a term in this book should not be regarded as affecting the validity Proofreader of any trademark or service mark. Language Logistics Warning and Disclaimer Technical Editors Every effort has been made to make this book as complete and as accurate as Chris Johnston possible, but no warranty or fitness is implied.
    [Show full text]
  • Diverted Derived Design
    Diverted Derived Design Table of Contents Introduction 0 Motivations 1 Licenses 2 Design (as a) process 3 Distributions 4 Economies 5 Propositions 6 This book 7 Glossary 8 2 Diverted Derived Design Introduction The term open source is becoming popular among product designers. We see websites and initiatives appear with a lot of good intentions but sometimes missing the point and often creating confusion. Design magazines and blogs are always rushing into calling an openly published creation open source but rarely question the licenses or provide schematics or design files to download. We are furniture designers, hackers and artists who have been working with free/libre and open source software for quite some time. For us, applying these prirciples to product design was a natural extension, providing new areas to explore. But we also realized that designers coming to this with no prior open source experience had a lot of information to grasp before getting a clear picture of what could be open source product design. So we set ourselves to mobilize our knowledge in this book. We hope that this tool can be a base for teaching and learning about open source product design; a collective understanding of what one should know today to get started and join the movement; a reference students, amateurs and educators can have in their back pocket when they go out to explain what they are passionate about. How to read this book We have divided this book in sections that make sense for us. Each of these tries to address what we think is a general question you might have about open source product design.
    [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]
  • 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
    [Show full text]
  • Python for S60 (Pys60)
    PYTHON FOR S60 (PYS60) MATOVU RICHARD Matrich Email: [email protected] Website: http://www.matrich.net/ Twitter: http://twitter.com/matrich/ SMART PHONES: OPERATING SYSTEMS Symbian Runs on most of today‟s phones and jointly owned by major portion of mobile phone industry Many various favours i.e. Nokia Series 60, UIQ, Series 80, Microsoft SmartPhone OS Windows Compact Edition and Pocket PC OS Windows Mobile Android Brings Internet-style innovation and openness to mobile phones iPhone OS Runs on iPhone and iPod touch devices Linux OS Rare and „invisible‟ SMART PHONES: PROGRAMMING LANGUAGES Java Platform, Micro Edition Most used but major sandboxing C++ (Symbian) Very steep learning curve Frustrating features Designed for „serious‟ developers .NET Programming on Mobile Phones Open C Python on Symbian SO WHY PYTHON? Cross Platform Free and Open Source Scripting Language Extending and embedding abilities Good standard library Access to full phone functionality… IT’S SO EASY import appuifw appuifw.note(u”Hello World”, “info”) COMPARISON BETWEEN PYTHON AND JAVA ME import appuifw appuifw.note(u”Hello World”, “info”) SO WHICH PYTHON S60 WORKS FOR YOU? 1st Edition 2nd Edition FP 1 2nd Edition For more details at FP 3 http://croozeus.com/devices.htm 3rd Edition FP 1 TESTING YOUR PYS60 SCRIPTS Install PyS60 on Mobile Phone Interactive Console Bluetooth Console Benefits of PC while running on the phone Install an emulator Test and debug your code on PC Though some functionality misses such as camera, GPS, calling,
    [Show full text]
  • Ubuntu: Unleashed 2017 Edition
    Matthew Helmke with Andrew Hudson and Paul Hudson Ubuntu UNLEASHED 2017 Edition 800 East 96th Street, Indianapolis, Indiana 46240 USA Ubuntu Unleashed 2017 Edition Editor-in-Chief Copyright © 2017 by Pearson Education, Inc. Mark Taub All rights reserved. Printed in the United States of America. This publication is protected Acquisitions Editor by copyright, and permission must be obtained from the publisher prior to any prohib- Debra Williams ited reproduction, storage in a retrieval system, or transmission in any form or by any means, electronic, mechanical, photocopying, recording, or likewise. For information Cauley regarding permissions, request forms and the appropriate contacts within the Pearson Managing Editor Education Global Rights & Permissions Department, please visit www.pearsoned.com/ permissions/. Sandra Schroeder Many of the designations used by manufacturers and sellers to distinguish their Project Editor products are claimed as trademarks. Where those designations appear in this book, and Lori Lyons the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. Production Manager The author and publisher have taken care in the preparation of this book, but make Dhayanidhi no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in Proofreader connection with or arising out of the use of the information or programs contained Sasirekha herein. Technical Editor For information about buying this title in bulk quantities, or for special sales opportunities (which may include electronic versions; custom cover designs; and content José Antonio Rey particular to your business, training goals, marketing focus, or branding interests), Editorial Assistant please contact our corporate sales department at [email protected] or (800) 382-3419.
    [Show full text]
  • Sfara Mobile SDK FOSS DISCLOSURE DOCUMENT Sfara Inc
    Sfara Mobile SDK FOSS DISCLOSURE DOCUMENT Sfara Inc. Version 5.0.1, 2020-12-15 TABLE OF CONTENTS 1 FOSS Notices .......................................................................................................................................... 2 2 Used FOSS Packages and Licenses ........................................................................................................... 2 2.1 Overview ........................................................................................................................................................... 2 2.2 Package details ................................................................................................................................................. 3 2.2.1 Google Test .......................................................................................................................................................................................... 3 2.2.2 DSP FIlters ............................................................................................................................................................................................ 3 2.2.3 FFTReal .................................................................................................................................................................................................. 3 2.2.4 Persistence1D ....................................................................................................................................................................................
    [Show full text]
  • 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 .
    [Show full text]
  • Open Source Licenses Applicable to Hitachi's Products Earlier Versions
    Open Source Licenses Applicable to Hitachi’s Products EARLIER VERSIONS Several products are listed below together with certain open source licenses applicable to the particular product. The open source software licenses are included at the end of this document. If the open source package has been modified, an asterisk (*) appears next to the name of the package. Note that the source code for packages licensed under the GNU General Public License or similar type of license that requires the licensor to make the source code publicly available (“GPL Software”) may be available for download as indicated below. If the source code for GPL Software is not included in the software or available for download, please send requests for source code for GPL Software to the contact person listed for the applicable product. The materials below are provided “AS IS,” without warranty of any kind, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement. Access to this material grants you no right or license, express or implied, statutorily or otherwise, under any patent, trade secret, copyright, or any other intellectual property right of Hitachi Vantara Corporation (“Hitachi”). Hitachi reserves the right to change any material in this document, and any information and products on which this material is based, at any time, without notice. Hitachi shall have no responsibility or liability to any person or entity with respect to any damages, losses, or costs arising from the materials
    [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]
  • 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.
    [Show full text]