DOCSLIB.ORG

FREE CODE: Pros and Cons of Using Open Source

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
FREE CODE: Pros and Cons of Using Open Source FREE CODE: Pros and Cons of Using Open Source May 22, 2018 Alternatives to common licensed software Open Source is everywhere The use of open source software is an essential part of application development. 96% of analyzed software The average app includes 147 applications utilize unique open source open source components * According to the analysis done by Black Duck’s Center for Open Source Research and Innovation (COSRI) in 2017. Pros of Using Open Source ★ Free to use ★ Free to modify and improve ★ Can be free to commercialize ★ Comparable to paid software ★ Accelerates software development ★ Lower hardware requirements in many cases Open Source for small businesses and start-ups ★ Reducing time to market ★ Driving costs down ★ Technological enablement for any business Developer toolbox Learning with Raspberry Pi ★ Training programming skills ★ Community support and interactions ★ Research tools Raspberry Pi sold over 14 million boards in five years Cons of Using Open Source ❖ You are responsible for the installation & configuration ❖ Little or no support / paid support ❖ Comes with no guarantee / SLA ❖ Bugs (one thing that is guaranteed) ❖ Less functionality & Compatibility issues (LibreOffice vs MS Office) ❖ Poorer UI/UX ❖ Updates depend on popularity and community enthusiasm ❖ Security & Reliability - research, do not just trust! ❖ Cost: using SaaS may be cheaper than implementing open source Open Source Licensing Copyleft Licenses Permissive Licenses ★ Freedom to run, copy, distribute, ★ Minimal requirements on study, change & improve distribution ★ Matter of liberty, not price: “free ★ Attribution, disclaimers still speech”, not “free beer”! required, no requirement to open ★ Viral: Derived work inherits the the derived code license! Richard Stallman, 1989 Distribution is the key Open Source Licensing Copyleft Licenses Permissive Licenses ★ GNU General Public License (GPL) ★ Apache License 2.0 ★ GNU Library or "Lesser" General Public ★ MIT license License (LGPL - weak copyleft) ★ BSD 3-Clause "New" or "Revised" license ★ Eclipse Public License ★ BSD 2-Clause "Simplified" or "FreeBSD" ★ Mozilla Public License 2.0 (weak copyleft) license ★ Common Development and Distribution License (weak copyleft) Talk to your lawyer first! This is not a legal advice & others Open Source Licensing Open Source Licensing Open Source License Compliance Cases ★ Jacobson V. Katzer - (model train software - breach of contract or copyright infringement?) - Jacobson wins - 2008 ★ Versata V. Ameriprise + XimpleWare( XML parsing utility, GPLv2 Licensing, Ameriprise reverse engineered the code and found GPLv2) - 2015 ★ Artifex V. Hancom (incorporating GPL-licensed Ghostscript, settlement) - 2017 ★ Automattic (Wordpress) V. Wix (GPLv2 text editor used & released under MIT) - 2016 ★ Christoph Hellwig V. VMware - 2015 (Linux Kernel, LGPLv2, dismissed) ★ CoKinetic Systems V. Panasonic Avionics - (unfair advantage, settlement in 2018) Open Source Licensing License conflicts are widespread ★ Over 85% of applications contain components with licenses out of compliance* ★ 53% of applications have “unknown” licenses, meaning no one has permission from the creator(s) of the software to use, modify, or share the software* ★ https://opensource.com/article/17/9/9-open-source- software-rules-startups ★ https://saperlaw.com * According to the analysis done by Black Duck’s Center for Open Source Research and Innovation (COSRI) in 2017. Why companies invest in open code? ★ Creating visibility & building audience Rank Company Employees Contributed ★ Attracting the right employees to the company to GitHub in 2017 ★ Promoting services 1 Microsoft 4,550 ★ Creating possibilities for third-party developers ★ Saving money: code.gov 2 Google 2,267 3 Red Hat 2,027 4 IBM 1,813 5 Intel 1,314 6 Amazon 881 7 SAP 747 8 ThoughtWorks 739 9 Alibaba 694 10 GitHub 676 Why contributing to Open Source? ★ Portfolio (GitHub is the best business card for a programmer) ★ Free resources to manage a product ★ Licensing obligations ★ Keeping up with community updates ★ Non-profit Social Projects ★ Passion! Thank you! Questions?.
Load more

Recommended publications
  • Practice Tips for Open Source Licensing Adam Kubelka
    Santa Clara High Technology Law Journal Volume 22 | Issue 4 Article 4 2006 No Free Beer - Practice Tips for Open Source Licensing Adam Kubelka Matthew aF wcett Follow this and additional works at: http://digitalcommons.law.scu.edu/chtlj Part of the Law Commons Recommended Citation Adam Kubelka and Matthew Fawcett, No Free Beer - Practice Tips for Open Source Licensing, 22 Santa Clara High Tech. L.J. 797 (2005). Available at: http://digitalcommons.law.scu.edu/chtlj/vol22/iss4/4 This Article is brought to you for free and open access by the Journals at Santa Clara Law Digital Commons. It has been accepted for inclusion in Santa Clara High Technology Law Journal by an authorized administrator of Santa Clara Law Digital Commons. For more information, please contact [email protected]. ARTICLE NO FREE BEER - PRACTICE TIPS FOR OPEN SOURCE LICENSING Adam Kubelkat Matthew Fawcetttt I. INTRODUCTION Open source software is big business. According to research conducted by Optaros, Inc., and InformationWeek magazine, 87 percent of the 512 companies surveyed use open source software, with companies earning over $1 billion in annual revenue saving an average of $3.3 million by using open source software in 2004.1 Open source is not just staying in computer rooms either-it is increasingly grabbing intellectual property headlines and entering mainstream news on issues like the following: i. A $5 billion dollar legal dispute between SCO Group Inc. (SCO) and International Business Machines Corp. t Adam Kubelka is Corporate Counsel at JDS Uniphase Corporation, where he advises the company on matters related to the commercialization of its products.
    [Show full text]
  • Developer Survey
    Developer Survey Questions requiring a response are in r ed . Questions in which a response is NOT required are in blue. This survey is a critical element of the developers workshop. We are using it to capture nuts and bolts information about codes within the community so that we can assess the landscape before the workshop and use this information to drive the discussions. Please collaborate to provide only one submission per code and submit your response using the online survey: h ttps://ucdavis.co1.qualtrics.com/jfe/form/SV_57wtv4gpuaowTsh Basic Information Code identification 1. What is the name of the code? [small text box] 2. Who are the primary authors/maintainers? [medium text box] 3. URL of webpage for the code (if different than the version control repository) [small text box] 4. URL of version control repository (if public) [small text box] Software 1. Which license(s) do you use? Select all that apply. a. Apache license b. BSD license c. GNU General Public License d. GNU Lesser General Public License e. MIT license f. Mozilla Public License g. Common Development and Distribution License h. Eclipse Public License i. Other. Please specify [small text box] j. No license 2. What programming language(s) is your code currently written in? Select all that apply a. Fortran 77 b. Fortran 90 or later c. C d. C++ e. Go f. Python g. Julia h. Matlab i. Other. Please specify. [small text box] 3. List the primary (high-level) code dependencies (e.g., PETSc, deal.ii, FEniCS) [medium text box] 4. List any additional (low-level) code dependencies (e.g., MPI, NetCDF, HDF5) [medium text box] 5.
    [Show full text]
  • 2012 Winners List
    ® 2012 Winners List Category 1: American-Style Wheat Beer, 23 Entries Category 29: Baltic-Style Porter, 28 Entries Gold: Wagon Box Wheat, Black Tooth Brewing Co., Sheridan, WY Gold: Baltic Gnome Porter, Rock Bottom Denver, Denver, CO Silver: 1919 choc beer, choc Beer Co., Krebs, OK Silver: Battle Axe Baltic Porter, Fat Heads Brewery, North Olmsted, OH Bronze: DD Blonde, Hop Valley Brewing Co., Springfield, OR Bronze: Dan - My Turn Series, Lakefront Brewery, Milwaukee, WI Category 2: American-Style Wheat Beer With Yeast, 28 Entries Category 30: European-Style Low-Alcohol Lager/German-Style, 18 Entries Gold: Whitetail Wheat, Montana Brewing Co., Billings, MT Silver: Beck’s Premier Light, Brauerei Beck & Co., Bremen, Germany Silver: Miners Gold, Lewis & Clark Brewing Co., Helena, MT Bronze: Hochdorfer Hopfen-Leicht, Hochdorfer Kronenbrauerei Otto Haizmann, Nagold-Hochdorf, Germany Bronze: Leavenworth Boulder Bend Dunkelweizen, Fish Brewing Co., Olympia, WA Category 31: German-Style Pilsener, 74 Entries Category 3: Fruit Beer, 41 Entries Gold: Brio, Olgerdin Egill Skallagrimsson, Reykjavik, Iceland Gold: Eat A Peach, Rocky Mountain Brewery, Colorado Springs, CO Silver: Schönramer Pils, Private Landbrauerei Schönram, Schönram, Germany Silver: Da Yoopers, Rocky Mountain Brewery, Colorado Springs, CO Bronze: Baumgartner Pils, Brauerei Jos. Baumgartner, Schaerding, Austria Bronze: Blushing Monk, Founders Brewing Co., Grand Rapids, MI Category 32: Bohemian-Style Pilsener, 62 Entries Category 4: Fruit Wheat Beer, 28 Entries Gold: Starobrno Ležák,
    [Show full text]
  • Eclipse IP Management Modernization Sharon Corbett MODERNIZATION
    Eclipse IP Management Modernization Sharon Corbett MODERNIZATION ● Eclipse IP - About ● Issue Statement WELCOME ● Objectives/Benefits ● License Compliance ● Self Service ● New Process Overview ● Futures ● Best Practices ● OSCM ● Wrap Up Eclipse Intellectual Property Management > Eclipse IP Policy (Board Approved) ○ Defines mechanism for accepting and licensing the intellectual property developed and leveraged by Eclipse projects > Legal Agreements ○ Formal - ECA, Committer Agreements, Working Group Participation Agreements > Due Diligence Review Process ○ Provenance, License Compatibility, Scanning for Anomalies ○ IP Ticket (CQ) > Commercial Adoption (Confidence/Safe) > High Bar, Rigorous, Well Respected COPYRIGHT (C) 2019, ECLIPSE FOUNDATION, INC. | MADE AVAILABLE UNDER THE ECLIPSE PUBLIC LICENSE 2.0 (EPL-2.0) What’s at Issue? > Eclipse IP Policy and Procedures (2004) > Significant changes over time > Cannot support agile development nor continuous delivery > Impossible to scale to modern day technology (Node.JS, Electron, NPM, etc.) > Burdensome - Lack of Automation COPYRIGHT (C) 2019, ECLIPSE FOUNDATION, INC. | MADE AVAILABLE UNDER THE ECLIPSE PUBLIC LICENSE 2.0 (EPL-2.0) The Time has Arrived ... > Bring Eclipse IP Policy and Process in line with contemporary expectations! COPYRIGHT (C) 2019, ECLIPSE FOUNDATION, INC. | MADE AVAILABLE UNDER THE ECLIPSE PUBLIC LICENSE 2.0 (EPL-2.0) Eclipse IP Governance Approach (Redefined) > Revise the IP Review requirements for third party content > Update IP Policy ○ Change due diligence approach for
    [Show full text]
  • A Strategy for Addressing the Needs of Advanced Scientific Computing Using Eclipse As a Parallel Tools Platform
    A Strategy for Addressing the Needs of Advanced Scientific Computing Using Eclipse as a Parallel Tools Platform Gregory R. Watson Craig E. Rasmussen Los Alamos National Laboratory P.O. Box 1663, MS B287 Los Alamos, NM 87545 December 2005 LA-UR-05-9114 ABSTRACT If parallel computer systems are to achieve the kinds of productivity improvements necessary to meet the needs of high productivity computing systems (HPCS), then a radical change will be required in how tools are developed for programmers and users of these systems. The number and complexity of tools is making it difficult for developers to access and use the tools effectively, and the lack of a common tool infrastructure significantly complicates tool development efforts. The rapid pace of change means that developing and maintaining the kinds of tools that will be needed to effectively utilize the capacity of future advanced computer systems is an increasingly onerous task. This paper proposes a strategy that will lead directly to productivity and quality improvements in the development and use of parallel applications, and that will provide a framework to guide and foster future tool development. This strategy is based on using the Eclipse platform to form the foundation of an integrated environment for parallel application development. The intention is not just to produce another set of tools, however, but rather to use Eclipse as both a focal point for tool development, and as a platform for producing highly integrated tools that are needed to meet the future needs of the HPC community. A Strategy for Addressing the Needs of Advanced Scientific Computing Using Eclipse as a Parallel Tools Platform 1 1 INTRODUCTION As high productivity computing systems (HPCS) are developed to meet the demands and computational challenges facing advanced scientific research, it is becoming increasingly apparent that existing software infrastructure and tools will need to be substantially improved in order to achieve the goal of sustained performance on terascale machines [17].
    [Show full text]
  • Deposit Systems for One-Way Beverage Containers: Global Overview 2018 Author’S Note
    DEPOSIT SYSTEMS FOR ONE-WAY BEVERAGE CONTAINERS: GLOBAL OVERVIEW 2018 AUTHOR’S NOTE This report was prepared by CM Consulting in association with Reloop Platform, and is intended to provide a comprehensive summary of 39 different deposit-return systems for one-way beverage containers in existence around the world. CM Consulting Inc. Working with industry, government, and not-for-profits, CM Consulting is recognized worldwide for the comprehensive information and analysis it provides – information that is relied upon to make informed policy and programming decisions. Established in 1998 by Clarissa Morawski, CM Consulting was founded on the principle that industry and consumers must assume greater responsibility for ensuring that the manufacture, use, reuse and recycling of their products and packaging has a minimum impact on the environment. CM Consulting specializes in waste minimization and Canadian stewardship policy with a specific focus on extended producer responsibility programs, cost and performance. The CM Consulting team consists of Clarissa Morawski (Principal), Jason Wilcox (Projects Manager), and Samantha Millette (Content Writer & Researcher). Reloop Platform Reloop is a broad platform of like-minded interests that share a common vision for a circular economy. The founding members of the organization bring together industry, government, and non-governmental organizations to form a network for advances in policy that create enabling system conditions for circularity across the European economy. With members coming from different sectors across Europe, the platform aims to work as a catalyst in order to generate economic and environmental opportunities for all stakeholders in the value chain. This includes producers, distributors, recyclers, academia, NGOs, trade unions, green regions, or cities.
    [Show full text]
  • Introducing the Eclipse Foundation Specification Process
    Introducing the Eclipse Foundation Specification Process 1 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Agenda • Background • Creating the EFSP • What is a Specification? • Eclipse Foundation Specification Process • EFSP and the JCP • Certification 2 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Background 3 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Why are we doing this? • Opportunity meets necessity • Java EE migration to Eclipse Foundation requires a spec process to replace the JCP • We expect that this process will be used elsewhere 4 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) What’s the Big Deal? Specifications • Guides you to implement collectively developed idea • Support multiple implementations • Allow for interoperability 5 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Guiding Principles • “Code First” • No more “Spec Lead” • Specifications run as open source projects • “Compatible” implementations, rather than one “Reference” implementation • Self-certification • Branding for compatible implementations of Profiles 6 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Jakarta EE Spec Process: 2018 Key deliverables • Establish spec process for existing (JCP) and new specs • Compatibility process • Brand licensing 7 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Creating the EFSP 8 Copyright (c) 2018, Eclipse Foundation, Inc.
    [Show full text]
  • Eclipse (Software) 1 Eclipse (Software)
    Eclipse (software) 1 Eclipse (software) Eclipse Screenshot of Eclipse 3.6 Developer(s) Free and open source software community Stable release 3.6.2 Helios / 25 February 2011 Preview release 3.7M6 / 10 March 2011 Development status Active Written in Java Operating system Cross-platform: Linux, Mac OS X, Solaris, Windows Platform Java SE, Standard Widget Toolkit Available in Multilingual Type Software development License Eclipse Public License Website [1] Eclipse is a multi-language software development environment comprising an integrated development environment (IDE) and an extensible plug-in system. It is written mostly in Java and can be used to develop applications in Java and, by means of various plug-ins, other programming languages including Ada, C, C++, COBOL, Perl, PHP, Python, Ruby (including Ruby on Rails framework), Scala, Clojure, and Scheme. The IDE is often called Eclipse ADT for Ada, Eclipse CDT for C/C++, Eclipse JDT for Java, and Eclipse PDT for PHP. The initial codebase originated from VisualAge.[2] In its default form it is meant for Java developers, consisting of the Java Development Tools (JDT). Users can extend its abilities by installing plug-ins written for the Eclipse software framework, such as development toolkits for other programming languages, and can write and contribute their own plug-in modules. Released under the terms of the Eclipse Public License, Eclipse is free and open source software. It was one of the first IDEs to run under GNU Classpath and it runs without issues under IcedTea. Eclipse (software) 2 Architecture Eclipse employs plug-ins in order to provide all of its functionality on top of (and including) the runtime system, in contrast to some other applications where functionality is typically hard coded.
    [Show full text]
  • Beer Statistics 2018 Edition
    Beer statistics 2018 edition The Brewers of Europe Beer statistics 2018 edition The Brewers of Europe December 2018 1 TABLE OF CONTENTS Foreword by President of The Brewers of Europe ..........................p. 4 Beer production 2017 ....................................................................p. 6 Beer production 2011 - 2017 ........................................................p. 7 Beer consumption 2017 ................................................................p. 8 Beer consumption 2011 - 2017 .....................................................p. 9 Beer consumption per capita 2017 ...............................................p.10 Beer consumption per capita 2011 - 2017 ...................................p.11 On-trade / off-trade 2017 .............................................................p.12 On-trade / off-trade 2011 - 2017 ..................................................p.13 Total imports 2017 ........................................................................p.14 Imports 2012 - 2014 ....................................................................p.15 Imports 2015 - 2017 ....................................................................p.16 Total exports 2017 ........................................................................p.17 Exports 2012 - 2014 ....................................................................p.18 Exports 2015 - 2017 ....................................................................p.19 Number of active breweries 2017 .................................................p.20
    [Show full text]
  • ASCET V7.0.0 OSS Attributions – 12.2014
    ASCET V7.0 OSS Attributions Copyright The data in this document may not be altered or amended without special notification from ETAS GmbH. ETAS GmbH undertakes no further obligation in relation to this docu- ment. The software described in it can only be used if the customer is in possession of a general license agreement or single license. Using and copying is only allowed in concur- rence with the specifications stipulated in the contract. Under no circumstances may any part of this document be copied, reproduced, transmit- ted, stored in a retrieval system or translated into another language without the express written permission of ETAS GmbH. © Copyright 2014 ETAS GmbH, Stuttgart The names and designations used in this document are trademarks or brands belonging to the respective owners. Document ASCET V7.0.0 OSS Attributions – 12.2014 2 ETAS Contents Contents 1 List of used Open Source Software Components........................................................................ 4 2 Appendix .............................................................................................................................. 11 2.1 Apache License 1.1 ........................................................................................................ 11 2.2 Apache License 2.0 ........................................................................................................ 12 2.3 Artistic License 1.0 ......................................................................................................... 15 2.4 ASM License .................................................................................................................
    [Show full text]
  • Removal of Alcohol from Beer Using Membrane Processes
    Removal of Alcohol From Beer Using Membrane Processes Master's Thesis Supervisors: Author: Henrik Siegumfeldt Andreas Jakob Wedel Falkenberg Jens Christian Sørensen In collaboration with: July 31, 2014 Title page Title: Removal of Alcohol From Beer Using Membrane Processes Author: Andreas Jakob Wedel Falkenberg (zdg243) Duration: 6 months 4/2 - 4/8-2014 30 ECTS Supervisors: Henrik Siegumfeldt Jens Christian Sørensen Copies: Printed in 3 copies, as well as being digitally available Thesis: Master's Thesis in Brewing Science and Technology Number of pages: 94 Written in LATEX Written at: Department of Food Science University of Copenhagen Faculty of Science In collaboration with: Brewhouse Skands A/S and Alfa Laval Nakskov A/S 1 Preface and Acknowledgement Rethinking the process for alcohol free beer (AFB) production focusing on aroma and flavour quality was the original idea of this thesis. An investigation was initiated revealing possible new methods of AFB production. This focusing not only on the process technologies re- lated to alcohol removal from normal alcoholic beer, but in addition looking beyond at the general beer production processes to indicate possible changes resulting in a higher quality AFB with regards to aroma and flavour preservation. I would like to thank all parties involved from the University of Copenhagen Faculty of Science, Brewhouse Skands A/S and Alfa Laval A/S. From the University of Copen- hagen Faculty of Science a special thanks to my supervisors Associate Professor Henrik Siegumfeldt and Associate Professor Jens Christian Sørensen for knowledgeable guidance, participation and support. Furthermore, thanks to my fellow student Tobias Emil Jensen and his supervisor Mikael Agerlin Petersen for guidance and permission to run head space gas chromatographic mass spectrometry samples.
    [Show full text]
  • Introducing the Eclipse Foundation Specification Process
    Introducing the Eclipse Foundation Specification Process 1 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Agenda • Background • Creating the EFSP • What is a Specification? • Eclipse Foundation Specification Process • EFSP and the JCP • Certification 2 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Background 3 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Why are we doing this? • Opportunity meets necessity • Java EE migration to Eclipse Foundation requires a spec process to replace the JCP • We expect that this process will be used elsewhere 4 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) What’s the Big Deal? Specifications • Guides you to implement collectively developed idea • Support multiple implementations • Allow for interoperability 5 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Guiding Principles • “Code First” • No more “Spec Lead” • Specifications run as open source projects • “Compatible” implementations, rather than one “Reference” implementation • Self-certification • Branding for compatible implementations of Profiles 6 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Jakarta EE Spec Process: 2018 Key deliverables • Establish spec process for existing (JCP) and new specs • Compatibility process • Brand licensing 7 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Creating the EFSP 8 Copyright (c) 2018, Eclipse Foundation, Inc.
    [Show full text]