Open Source Licensing: Recent Developments and Events

Total Page:16

File Type:pdf, Size:1020Kb

Open Source Licensing: Recent Developments and Events Open Source Licensing: Recent Developments and Events Gordon & Glickson LLC Law Seminars International Current Developments in Copyright Law Philadelphia, Pennsylvania September 28, 2005 2 This presentation is intended to alert the reader to some of the legal issues discussed herein. The impact of the law for each particular situation depends on a variety of factors, therefore we strongly recommend you engage legal counsel to assess and help minimize your legal liability based on the particular requirements of your institution. Like any presentation, this is not meant to be used as a substitute for legal counsel. © 2005 Gordon & Glickson LLC. 3 Open Source Licensing • Brief History – GPL – General Public License (Version 2) • Free Software Foundation – Richard Stallman • Source Code Available to End Users • No Copying Restrictions • No Redistribution Restrictions • “Forcing” Restrictions – Distribution Ramifications – “Free As In Speech – Not As In Price” – Non-Proprietary Model – Antithesis of Copyright Model – FSF Preparing GPL 3 – Due In 2007 • Growth/Development – Over Time Many Alternatives Have Arisen • Academic/Government • Private – Multiple Levels of Complexity Depending on Source © 2005 Gordon & Glickson LLC. 4 Open Source Front Line • Open Source Initiative – www.opensource.org – Outlines 50+ Variations – Excellent Templates – Certification Process – Cutting Back on Varieties • Free Software Foundation – http://www.gnu.org/home.html – Focal Point of “Movement” – Source of the GPL – Working on GPL 3 (For 2007 Distribution) • More Global Perspective • Software Patent Considerations • Web Services © 2005 Gordon & Glickson LLC. 5 Open Source Variations • Academic/Government – GPL – General Public License (v.2) – LGPL – Less General Public License (v.2.1) – BSD – Berkeley Software Directive (“New” – see MIT) – MIT – MIT Public License NASA Open Source Agreement (v.1.3) – NASA – NASA Open Source Agreement (v.1.3) • Private – Apache Software License (v.2) – Computer Associates (v.1.1) – IBM Public License – Intel Public License (Recently Withdrawn) – MPL – Mozilla Public License (1.1) – Sun Public License – Sybase Open Watcom Public License © 2005 Gordon & Glickson LLC. 6 Open Source Variations • Noteworthy Characteristics (Academic) – GPL • Highly viral – use infects “new code” • No Control Over “Forced” Distribution Rights • LGPL has less coverage (allowing for proprietary libraries) – BSD (www.bsd.org) • Much less viral than GPL – allow code to go “closed” • Focuses on warranty/damage limitation – MIT • Focuses on “substantial portions” of code • Much less viral than GPL – allow code to go “closed” • Does not apply to “new code” – NASA • Focus on Patent Rights/Distribution Issues • Also contemplates issuance of warranties © 2005 Gordon & Glickson LLC. 7 Open Source Variations • Private Flavors – Apache (v.2.0) • Focus on “Derivative Works” For Coverage • Covers IP Rights • Parallels MIT Regarding Non-Covered Code – Mozilla (v.1.1) (www.mozilla.org) • Clearly worded/much use of defined terms • Focus on “Larger Works” and “Covered Code” • Much less viral than GPL • One of most popular versions over last several years – Computer Associates • Less Viral • More Choice of Allowing Coverage For “Modifications” – IBM • Focus on “Derivative Works” For Coverage • Less Viral – Sun and Sybase • Parallels IBM and CA © 2005 Gordon & Glickson LLC. 8 Open Source Today • Alive and Vibrant – Very Much In State of Evolution – Focus on Lower Costs/Reaches For Best Part of Model • International Scope – Australia – Mandates Public Entities To Use – Brazil – Backs Use of Open Source At Federal Level – China/Japan/ROK – Private Joint Ventures/Banks – Denmark – Promotion of Use By Public Entities – Germany – Municipal Shifts/Insurance Companies – India – Continuation of eCommerce Activities – Malaysia – Stepped Up Implementation – Spain – Part of Hardware Distribution – South Africa – Development Efforts – United Kingdom – Government Use © 2005 Gordon & Glickson LLC. 9 Open Source Today – U.S. • Huge Momentum Play – Government and Private • Avalanche Corporate Technology Cooperative – www.avalanchecorporatetechnology.net – Best Buy, Jostens, Select Comfort, Cargill, Medtronic – Cost Sharing/Indemnification of Members • Government Open Code Collaborative (www.gocc.gov) – Group of Agencies (State and Local) – Share Open Source Code • Federal Efforts – DOL – Workforce Connections (GPL) – NASA/OSHA/DOD – http://workforceconnections.dol.gov/ • Other States/Cities – Massachusetts – Total Conversion To Open Source By 2007 – Indiana – Implementation of Linspire On High School Desktops – CA, MO, KS, OK, OR, PA, RI, TX, WI, WV – Los Angeles/Chicago © 2005 Gordon & Glickson LLC. 10 Private Endeavors – U.S. • Networking Level Seeing Most Effort – Great Penetration – Internet Infrastructure – Network Environments – Same Level of Effort – Market For Servers Running Linux – $9 Billion by 2008 – Growing Use of Programming Libraries – Growing Acceptance By Management – Note Unilever Cancellation of Migration Plan • Was To Be Completed In 2006 • Cost Advantage “No Longer Clear” • Microsoft Brick Wall – 90+% Desktop Penetration – Transition Costs – Data Issues/Staff Training – Familiarity Concerns – Look and Feel Issues – Shared Source Initiative – 20 Products – Watch Linspire 5.0 (Formerly Lindows) – Growing Fast © 2005 Gordon & Glickson LLC. 11 Industry Efforts – U.S. • Internet Services – Amazon.com – Linux – Google – Linux – Yahoo – FreeBSD • Financial Services – Credit Suisse First Boston – Merrill Lynch – NASDAQ • Entertainment – Industrial Light and Magic – Linux – DreamWorks – Linux – Pixar Animation – Linux – Ritz Camera – Linux • Oil Exploration – Royal Dutch Shell – Linux/IBM – WesternGeco – Linux © 2005 Gordon & Glickson LLC. 12 Technology Suppliers – U.S. • Acer – Linux Option For Home PCs • BEA Systems – Application Server Platform (Linux) • BMC Software – Provides Service For Linux • Borland Software – Linux Version of Delphi • Computer Associates – Multiple Linux Apps – Replicating IBM – Releasing 14 Patents • HP – Linux Division Established • IBM – January 2005 Release of Patents • Novell – Multiple Apps • Oracle – Linux Support For Apps • SAP – mySAP on Linux • Sun – Linux Desktop Including StarOffice • Veritas – Storage Management (Linux) © 2005 Gordon & Glickson LLC. 13 Open Source Traps/Issues • Licensing Issues To Consider – Good For Internal Use Applications – Problems For Distributed Code • Forces Application of Provisions Onto “Proprietary” Portions • Potential Loss of Revenue Stream – Debate Over Coverage • Stallman – No Difference • Torvalds – Exceptions • Know What You’re Getting – Huge Trap For Unwary – Know Code Pedigree – Title To Code Can Be Jeopardized © 2005 Gordon & Glickson LLC. 14 Open Source Considerations • Model #1 – Development For Distribution – Development Staff Creates Code For Software Product – Product To Be Sold/Licensed – Proprietary Model – Lines From OSS Are Inserted Into Code – What Happens To Your Rights To Product? – What Happens As Your (Indemnified) Customers Find Out? • Model #2 – Development For Internal Use Only – Development Staff Creates Code For Internal Use – Product Not To Be Licensed (No Income Stream) – Is The App Going To Be A Competitive Breakthrough? • Model #3 – Acquisitions of Third Parties – Each of Above Considerations Applies Here Also – Due Diligence Is Key • Know What You’re Getting ! ! ! © 2005 Gordon & Glickson LLC. 15 OSS Best Practices/Thoughts • Create Implementation Policy – Key Considerations – Business Model • Products To Be Licensed? • Revenue Stream? – Integration of OSS Into Company Products • Restrictions on Distribution Rights • Licensing Fees May Be Undercut – Track Pedigree of Sources • Where Did Your Code Come From? – 56% Admit To Using Open Source Code – Up From 38% In 2001 • Copyright Infringement From “Community” • Internal Developer Handling Policies – Educate Developers On Copyright Law – Keep Careful Records of Authorship – Make Sure Trade Secrets/Copyrights Not Being Waived © 2005 Gordon & Glickson LLC. 16 OSS Best Practices/Processes • Oversight Committee – Pre-Approval of OSS Use Necessary • Staffing – Legal and Technical • Careful Documentation of Decisions – Access To All Necessary Expertise – Focal Point – Train Staff As To Terms and Enforcement • Approval Process – Careful Documentation – Should Create Detailed Product Pedigree • Timing of Process – Impose Very Early In Development – Avoid Production/Integration Conflicts © 2005 Gordon & Glickson LLC. 17 SCO Group v. IBM. • Suit Filed in March 2003 – $1 Billion – SCO Allegedly Controls Rights To UNIX – IBM Distributes AIX Flavor of UNIX – SCO Alleges Linux Infringes UNIX Code • “Substantial” Amount of Code Involved • Unfair Competition w/ UNIX • No Copyright Claims • Public Battles – SCO Warning Letters To UNIX Users (Few Takers) – SCO Warning (in June 2003) To IBM Rescinding AIX Rights – SCO Licensing Initiative on Linux – IBM Counterclaims – Patent Infringement and GPL © 2005 Gordon & Glickson LLC. 18 SCO Effects • SCO Litigation Status – Trial Set For February 2007 – Suits Against UNIX Licensees • Red Hat v. SCO (8/4/03) • SCO v. Novell (1/20/04) • SCO v. Autozone (3/2/04) • SCO v. Daimler-Chrysler (3/4/04) • All Stayed Pending SCO/IBM Decision – Check SCO’s Litigation Website • www.sco.com/scoip/lawsuits • Links to Actual Filings – Evolution of Theories • From Trade Secrets • To Copyrights – IBM Very Aggressive – Copyright Violations – IBM SJ Motion Denied – SCO Case Weakened © 2005 Gordon & Glickson
Recommended publications
  • IBM Websphere Studio Application Developer for Windows, Version 4.0 Helps Java Developers to Build, Test, and Deploy J2EE-Based E-Business Applications
    Software Announcement November 6, 2001 IBM WebSphere Studio Application Developer for Windows, Version 4.0 Helps Java Developers To Build, Test, and Deploy J2EE-based e-business Applications Overview flexible source control management, pluggable At a Glance Introducing IBM′s premier Java repositories, as well as adapters development environment for for Concurrent Versioning System WebSphere Studio Application professional developers, the first (CVS) and for Rational ClearCase Developer for Windows, V4.0 product in the WebSphere Studio LT (CCLT) (Application Developer) provides product suite, WebSphere Studio • A comprehensive visual XML an advanced development Application Developer for development environment, environment for J2EE application Windows , V4.0 (Application including components for building development. Developer). DTDs, XML Schemas, XML files, and XSL style sheets Application Developer offers the Application Developer is built on the • Built-in WebSphere test following key functions: WebSphere Studio Workbench, an environment • integrated platform designed to A powerful Java development provide a common set of services Application Developer is next environment, that includes and frameworks unparalleled generation technology for support for JDK 1.3, a development tool integration and VisualAge for Java Enterprise configurable runtime, tool construction. Edition. It combines many popular incremental compilation, features of VisualAge for Java scrapbook, dynamic debugging, Application Developer includes the Enterprise Edition and WebSphere and a Java text editor • following functions: Studio Advanced Edition integrated Advanced Web, Java, and XML development environments • on top of WebSphere Studio An advanced development Workbench. designed to J2SE and J2EE environment for J2EE application specifications development that meets J2SE and Application Developer is focused on • A Relational Schema Center J2EE specifications and EJB optimizing J2EE application (RSC) focused on relational development and deployment and development.
    [Show full text]
  • An Introduction to Linux and Open Source
    IBM Systems and Technology Group An Introduction to Linux and Open Source Jim Elliott Consulting Sales Specialist – System z Product Manager – System z Operating Systems IBM Canada Ltd. 1 SHARE 109 - Session 9200 2007-08-13 © 2007 IBM Corporation IBM Systems and Technology Group 9200 – An Introduction to Linux and Open Source Linux and Open Source continue to see substantial growth around the world This session will provide an overview of Open Source and an introduction to Linux (including concepts and terminology) Jim will also provide an overview of Novell's SUSE Linux Enterprise (SLE) 10 and Red Hat Enterprise Linux (RHEL) 5 2 SHARE 109 - Session 9200 2007-08-13 IBM Systems and Technology Group Topics Introduction to Open Source Introduction to Linux Novell SUSE Linux Enterprise 10 Red Hat Enterprise Linux 5 Linux and Open Source on the Web at IBM 3 SHARE 109 - Session 9200 2007-08-13 IBM Systems and Technology Group Linux user presentations on Wednesday All sessions on the 3rd floor, Ford A&B Session Speaker Title 9215 Marcy Cortes – Penguins Board the Stagecoach 1:30pm Wells Fargo for the Linux Frontier: A User Experience with Linux on zSeries 9230 Alain Leclerc – How to Rise Above the Challenges 3:00pm CSPQ and of Deploying z/VM and Linux on David Kreuter – the Mainframe and Thrive VM Resources 9231 Alain Leclerc – Building a Strong z/VM and Linux 4:30pm CSPQ and Architecture on the Mainframe David Kreuter – VM Resources 4 SHARE 109 - Session 9200 2007-08-13 IBM Systems and Technology Group Linux user presentations on Thursday
    [Show full text]
  • Introducing... the IBM Toolbox for Javatm
    Session Number: 403552 Introducing... The IBM Toolbox for Java TM Jeff Lee ([email protected]) © 2010 IBM Corporation IBM Power Systems IBM Toolbox for Java™ What is the Toolbox/JTOpen? A set of Java classes and utilities which provide access to IBM i® data and resources class { Integer id; String name; String address; BigDecimal balance; String ccnumber; String expdate; } 2 © 2010 IBM Corporation 1 IBM Power Systems IBM Toolbox for Java The big picture - Client/Server Your Java TM program IBM Toolbox for Java Java Virtual Machine TCP/IP IBM i Access for Windows is not required! TCP/IP IBM i Host Servers *PGM IFS IBM i data and resources DB2/400 *CMD 3 © 2010 IBM Corporation IBM Power Systems IBM Toolbox for Java The big picture - Toolbox and data on same IBM i Your JavaTM program IBM Toolbox for Java TCP/IP JNI IBM i Host Servers IFS *PGM IBM i data and resources DB2/400 *CMD 4 © 2010 IBM Corporation 2 IBM Power Systems IBM Toolbox for Java Using the Toolbox in client/server applications • Toolbox installed on client • Java application runs on client • IBM i Access for Windows is not required • The same Java application runs on any client with a Java-compatible JVM! TCP/IP • Server running IBM i • Uses existing IBM i host servers • IBM i Java Virtual Machine (JVM) is not required on the server 5 © 2010 IBM Corporation IBM Power Systems IBM Toolbox for Java Using the Toolbox in server applications • Toolbox installed on IBM i • Java application runs on IBM i • Use Toolbox instead of JNI • "Local" sockets used to communicate between Toolbox
    [Show full text]
  • FOSS Philosophy 6 the FOSS Development Method 7
    1 Published by the United Nations Development Programme’s Asia-Pacific Development Information Programme (UNDP-APDIP) Kuala Lumpur, Malaysia www.apdip.net Email: [email protected] © UNDP-APDIP 2004 The material in this book may be reproduced, republished and incorporated into further works provided acknowledgement is given to UNDP-APDIP. For full details on the license governing this publication, please see the relevant Annex. ISBN: 983-3094-00-7 Design, layout and cover illustrations by: Rezonanze www.rezonanze.com PREFACE 6 INTRODUCTION 6 What is Free/Open Source Software? 6 The FOSS philosophy 6 The FOSS development method 7 What is the history of FOSS? 8 A Brief History of Free/Open Source Software Movement 8 WHY FOSS? 10 Is FOSS free? 10 How large are the savings from FOSS? 10 Direct Cost Savings - An Example 11 What are the benefits of using FOSS? 12 Security 13 Reliability/Stability 14 Open standards and vendor independence 14 Reduced reliance on imports 15 Developing local software capacity 15 Piracy, IPR, and the WTO 16 Localization 16 What are the shortcomings of FOSS? 17 Lack of business applications 17 Interoperability with proprietary systems 17 Documentation and “polish” 18 FOSS SUCCESS STORIES 19 What are governments doing with FOSS? 19 Europe 19 Americas 20 Brazil 21 Asia Pacific 22 Other Regions 24 What are some successful FOSS projects? 25 BIND (DNS Server) 25 Apache (Web Server) 25 Sendmail (Email Server) 25 OpenSSH (Secure Network Administration Tool) 26 Open Office (Office Productivity Suite) 26 LINUX 27 What is Linux?
    [Show full text]
  • Open Source Software 101
    What Every Attorney Needs to Know About Open Source Licenses and Their Obligations: Open Source Software 101 2020 Edition LawPracticeCLE Unlimited All Courses. All Formats. All Year. ABOUT US LawPracticeCLE is a national continuing legal education company designed to provide education on current, trending issues in the legal world to judges, attorneys, paralegals, and other interested business professionals. New to the playing eld, LawPracticeCLE is a major contender with its oerings of Live Webinars, On-Demand Videos, and In-per- son Seminars. LawPracticeCLE believes in quality education, exceptional customer service, long-lasting relationships, and networking beyond the classroom. We cater to the needs of three divisions within the legal realm: pre-law and law students, paralegals and other support sta, and attorneys. WHY WORK WITH US? At LawPracticeCLE, we partner with experienced attorneys and legal professionals from all over the country to bring hot topics and current content that are relevant in legal practice. We are always looking to welcome dynamic and accomplished lawyers to share their knowledge! As a LawPracticeCLE speaker, you receive a variety of benets. In addition to CLE teaching credit attorneys earn for presenting, our presenters also receive complimentary tuition on LawPracticeCLE’s entire library of webinars and self-study courses. LawPracticeCLE also aords expert professors unparalleled exposure on a national stage in addition to being featured in our Speakers catalog with your name, headshot, biography, and link back to your personal website. Many of our courses accrue thousands of views, giving our speakers the chance to network with attorneys across the country. We also oer a host of ways for our team of speakers to promote their programs, including highlight clips, emails, and much more! If you are interested in teaching for LawPracticeCLE, we want to hear from you! Please email our Directior of Operations at [email protected] with your information.
    [Show full text]
  • Working with the Linux Community
    Working with the Linux Community A Guest Lecture for CS 378 class at the University of Texas at Austin Khoa Huynh, Ph.D. IBM Linux Technology Center Austin, TX Linux Technology Center TopicsTopics Open source software development Open source licences Common risks Working with the Linux community General advices & tips Submitting your work to Linux kernel community Source code control Bug tracking Submitting your work to Linux distributors Linux debug tools Linux Technology Center OpenOpen SourceSource SoftwareSoftware (OSS)(OSS) Freely available software in source code format Often distributed via Internet or CD (e.g., Red Hat) Redistribution cannot be prohibited or royalty imposed Often developed in a collaborative community effort OSS community very sensitive about meaning & use of term "open source" For the current definition, see: http://www.opensource.org/osd/ Not "Public Domain" Copyright law gives author rights author determines appropriate uses of a work e.g. you can't reproduce or modify a work without author's permission author may grant permission via a license which can impose obligations Linux Technology Center OpenOpen SourceSource LicensesLicenses There are many open source licenses e.g. GPL, LGPL, CPL, IPL, BSD, Apache, etc. Some common features Governs use, modification and distribution of code Grant of rights (e.g. modification, redistribution, etc.) Obligations (e.g. attribution, redistribution, etc.) Different licenses have different objectives GPL = "General Public License" LGPL = "Lesser/Library Public License" CPL/IPL
    [Show full text]
  • Abstract: Modern Open Source (“OS”) Software Projects Are Increasingly Funded by Commercial Firms That Expect to Earn a Profit from Their Investment
    GSPP10-006 Abstract: Modern open source (“OS”) software projects are increasingly funded by commercial firms that expect to earn a profit from their investment. This is usually done by bundling OS software with proprietary goods like cell phones or services like tech support. This article asks how judges and policymakers should manage this emerging business phenomenon. It begins by examining how private companies have adapted traditional OS institutions in a commercial setting. It then analyzes how OS methods change companies’ willingness to invest in software. On the one hand, OS cost-sharing often leads to increased output and benefits to consumers. On the other, these benefits tend to be limited. This is because sharing guarantees that no OS company can offer consumers better software than any other OS company. This suppresses incentives to invest much as a formal cartel would. In theory, vigorous competition from non-OS companies can mitigate this effect and dramatically increase OS output. In practice, however, de facto cartelization usually makes the OS sector so profitable that relatively few proprietary companies compete. This poses a central challenge to judges and policymakers. Antitrust law has long recognized that the benefits of R&D sharing frequently justify the accompanying cartel effect. This article argues that most commercial OS collaborations can similarly be organized in ways that satisfy the Rule of Reason. It also identifies two safe harbors where unavoidable cartel effects should normally be tolerated. That said, many OS licenses contain so-called “viral” clauses that require users who would prefer to develop proprietary products to join OS collaborations instead.
    [Show full text]
  • Installing CM System Version
    CM System Installing CM System Version 7.3 Printed on 12 June 2013 Copyright and Licensing Statement All intellectual property rights in the SOFTWARE and associated user documentation, implementation documentation, and reference documentation are owned by Percussion Software or its suppliers and are protected by United States and Canadian copyright laws, other applicable copyright laws, and international treaty provisions. Percussion Software retains all rights, title, and interest not expressly grated. You may either (a) make one (1) copy of the SOFTWARE solely for backup or archival purposes or (b) transfer the SOFTWARE to a single hard disk provided you keep the original solely for backup or archival purposes. You must reproduce and include the copyright notice on any copy made. You may not copy the user documentation accompanying the SOFTWARE. The information in CM System documentation is subject to change without notice and does not represent a commitment on the part of Percussion Software, Inc. This document describes proprietary trade secrets of Percussion Software, Inc. Licensees of this document must acknowledge the proprietary claims of Percussion Software, Inc., in advance of receiving this document or any software to which it refers, and must agree to hold the trade secrets in confidence for the sole use of Percussion Software, Inc. The software contains proprietary information of Percussion Software; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. Due to continued product development this information may change without notice. The information and intellectual property contained herein is confidential between Percussion Software and the client and remains the exclusive property of Percussion Software.
    [Show full text]
  • Open Source Software: What Business Lawyers, Entrepreneurs and IT Professionals Should Know
    Open Source Software: What Business Lawyers, Entrepreneurs and IT Professionals Should Know Stuart R. Hemphill Partner Minneapolis P: (612) 340-2734 F: (612) 340-8856 [email protected] © 2016 Dorsey & Whitney LLP Source vs. Object Source Code Object Code Programmer readable statements in Machine readable Binary: a computer language, such as C, C++, Cobol, Fortran, Java, Perl, 000010100010001010 PHP 110001010000010100 000100101010001011 // Create a button and add it to the applet. // Also, set the button's colors clear_button = new Button("Clear"); Or Hexadecimal clear_button.setForeground(Color.black); clear_button.setBackground(Color.lightGray); 3F7A this.add(clear_button); (translates to the following binary number: 0011 1111 0111 1010) 2 History of Open Source Software . Term coined in February 1998 by Silicon Valley insiders in anticipation of Netscape’s announcement that it would release the source code for its browser software . This meant software coders could understand the browser’s working details and potentially modify them . 1998 was a momentous time for open source movement given mainstream adoption of internet . But concept significantly pre-dates coining of term 3 Free Software Foundation . Free Software Foundation (FSF), created in 1983 by Richard Stallman of MIT with goal of developing free version of UNIX operating system; everyone could share and change this version . According to FSF, “‘Free software’ is a matter of liberty, not price … think of ‘free’ as in ‘free speech,’ not as in ‘free beer.’” . Stallman wrote a license leveraging copyright in base code and intended to keep derivatives of base software “free” by requiring source code disclosure . Non-negotiable terms; accept by use .
    [Show full text]
  • Livecycle ES 2
    LiveCycle ES2 Readme The contents of this file are subject to the Mozilla Public License Version 1.1 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.mozilla.org/MPL/ Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. Portions licensed under the Mozilla Public License Version 1.1, available at www.mozilla.org. Recipients can obtain a copy of the Adobe modifications in source form. The contents of this file are subject to the Netscape Public License Version 1.1 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.mozilla.org/NPL/ Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. The Original Code is Mozilla Communicator client code, released March 31, 1998. The Initial Developer of the Original Code is Netscape Communications Corporation. Portions created by Netscape are Copyright (C) 1998-1999 Netscape Communications Corporation. All Rights Reserved. This product contains either BSAFE and/or TIPEM software by RSA Security Inc. Copyright (C) 1995-1997 Eric Young ([email protected]) All rights reserved. This package is an SSL implementation written by Eric Young ([email protected]).
    [Show full text]
  • Open Source Software Packages
    Hitachi Ops Center V. 10.3.0 Open Source Software Packages Contact Information: Hitachi Ops Center Project Manager Hitachi Vantara LLC 2535 Augustine Drive Santa Clara, California 95054 Name of Product/Product Version License Component aesh 2.4 Apache License, Version 2.0 aesh Extensions 1.8 Apache License, Version 2.0 aesh Readline 2.0 Apache License, Version 2.0 aesh Terminal API 2.0 Apache License, Version 2.0 "Java Concurrency in Practice" 1.0-redhat- Creative Commons Attribution 2.5 Generic book annotations 4 @angular-builders/custom- 8.0.0-RC.0 The MIT License webpack @angular-devkit/build-angular 0.800.0-rc.2 The MIT License @angular-devkit/build-angular 0.803.25 The MIT License @angular-devkit/core 7.3.8 The MIT License @angular-devkit/schematics 7.3.8 The MIT License @angular/animations 7.2.15 The MIT License @angular/animations 8.2.14 The MIT License Name of Product/Product Version License Component @angular/cdk 7.3.7 The MIT License @angular/cli 8.0.0 The MIT License @angular/cli 8.3.25 The MIT License @angular/common 7.2.15 The MIT License @angular/common 8.2.14 The MIT License @angular/compiler 7.2.15 The MIT License @angular/compiler 8.2.14 The MIT License @angular/compiler-cli 8.2.14 The MIT License @angular/core 7.2.15 The MIT License @angular/forms 7.2.13 The MIT License @angular/forms 7.2.15 The MIT License @angular/forms 8.2.14 The MIT License @angular/forms 8.2.7 The MIT License @angular/language-service 8.2.14 The MIT License @angular/platform-browser 7.2.15 The MIT License Name of Product/Product Version License
    [Show full text]
  • Open Source and Proprietary Software Colleen Toth and Nan Hu How Open Is Open Enough? Melding Proprietary and Open Source Platform Strategies
    Open Source and Proprietary Software Colleen Toth and Nan Hu How Open is Open Enough? Melding Proprietary and Open Source Platform Strategies Abstract: Computer platforms provide an integrated architecture of hardware and software standards as a basis for developing complementary assets. The most successful platforms were owned by proprietary sponsors that controlled platform evolution and appropriated associated rewards. Responding to the Internet and open source systems, three traditional vendors of proprietary platforms experimented with hybrid strategies which attempted to combine the advantages of open source software while retaining control and differentiation. Such hybrid standards strategies reflect the competing imperatives for adoption and appropriability, and suggest the conditions under which such strategies may be preferable to either the purely open or purely proprietary alternatives. The Author : Joel West ● Professor at KGI — the Keck Graduate Institute of Applied Life Sciences (Claremont, Calif.) ● Blogger on technology strategy, innovation and entrepreneurship ● Researcher on innovation and entrepreneurship ● Teacher of strategy, technological innovation and entrepreneurship ○ Professor Emeritus at San José State University, Department of Organization and Management ○ Lecturer at UC Irvine, Pepperdine and Temple University Japan ○ Author of teaching cases on Qualcomm, Live365 and Solar Energy The Author (Cont.) ○ Strategy consultant to IT companies in areas such as open source strategy and business model development
    [Show full text]