DOCSLIB.ORG

Licensing, Multi-Licensing

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Licensing, Multi-Licensing Software Licenses, Free and Open Source Software Péter Jeszenszky Faculty of Informatics, University of Debrecen [email protected] Last modified: April 16, 2020 Terminology ● Non-Free Software, Closed-Source Software, Proprietary Software ● Free Software ● Open-Source Software ● Free and Open-Source Software (FOSS) ● Commercial Software ● Freeware, Shareware ● Software License ● End-User License Agreement (EULA) ● License Compatibility ● Copyleft, Copyleft License ● Public Domain ● Dual Licensing, Multi-Licensing 2 Non-Free Software ● Non-free software is any software that is not free. – Its use, redistribution or modification is prohibited or restricted, or requires permission. – It is also called as closed source software or proprietary software. – Non-free software is the complementary set of free software. 3 Free Software ● The four essential freedoms: – The freedom to run the program for any purpose. – The freedom to study how the program works. – The freedom to redistribute copies of the program. – The freedom to modify the program. ● Access to the source code is a precondition for the second and the fourth freedom. ● See: The Free Software Definition https://www.gnu.org/philosophy/free-sw.html.en 4 Open Source Software (1) ● The terms “free software” and “open source software” refer to almost the same range of software. However, they represent two different approaches. – Definition: The Open Source Definition https://opensource.org/docs/osd ● The term “open source” is more suitable for marketing purposes than the “term free” software. – Free is an ambiguous word. One meaning of the word is “at no cost”. ● See, for example, “free speech” vs “free beer”. 5 Open Source Software (2) ● The free software movement emphasizes the ethical aspects of freedom. ● By contrast, the open source movement emphasizes the practical advantages of openness. ● Despite the ideological differences between the two camps, the terms free software and open source software practically have the same meaning. 6 Open Source Software (3) ● Open Source Initiative (OSI) https://opensource.org/ – A non-profit organization founded 1998 to promote and support open source software. – Eric S. Raymond, a leading advocate of the open source movement, was its president until 2005. 7 Open Source Software (4) ● See also: – Richard Stallman. Why Open Source misses the point of Free Software. https://www.gnu.org/philosophy/open-source-misse s-the-point.html – Eric S. Raymond. The Cathedral and the Bazaar. February 18, 2010. http://www.catb.org/esr/writings/cathedral-bazaar/ 8 Alternative Name ● Free and Open-Source Software (FOSS) – A category that includes both free software and open source software. – Also known as: Free/Libre and Open-Source Software (FLOSS). ● See also: Richard Stallman. FLOSS and FOSS. https://www.gnu.org/philosophy/floss-and-foss.h tml 9 Commercial Software ● Commercial software is software developed by a business as part of its business. ● Most commercial software is proprietary, but there is commercial free software. ● See: Categories of Free and Nonfree Software – Commercial software https://www.gnu.org/philosophy/categories.html #commercialSoftware 10 Freeware, shareware ● Freeware: – The term “freeware” has no clear accepted definition. – It is commonly used for packages which permit redistribution but not modification (and their source code is not available). – Freeware is not free software. – See: Categories of Free and Nonfree Software – Freeware https://www.gnu.org/philosophy/categories.html#freeware ● Shareware: – Shareware is software which comes with permission for people to redistribute copies, but says that anyone who continues to use a copy is required to pay a license fee. – Shareware is not free software. – See: Categories of Free and Nonfree Software – Shareware https://www.gnu.org/philosophy/categories.html#shareware 11 Software License ● A software license is a legal instrument that regulates the distribution and use of software. – In the case of proprietary software, the term end- user license agreement (EULA) is used. 12 License Compatibility ● We say that several licenses are compatible if there is a way to merge code under those various licenses while complying with all of them. – See: Richard Stallman. License Compatibility and Relicensing. https://www.gnu.org/licenses/license-compatibility.ht ml 13 FOSS Licenses (1) ● Numerous FOSS licenses exist. – For example, the OSI maintains of list of approved open source licenses: Licenses & Standards https://opensource.org/licenses – Another useful source: Various Licenses and Comments about Them https://www.gnu.org/licenses/license-list.html 14 FOSS Licenses (2) ● The lists of FOSS licenses approved by the FSF and the OSI include all widely used software licenses. – For example, the NASA Open Source Agreement v1.3 is an OSI-approved open source license, however, the FSF does not consider it to be a free software license. ● See: – https://opensource.org/licenses/NASA-1.3 – Various Licenses and Comments about Them – NASA Open Source Agreement https://www.gnu.org/licenses/license-list.html#NASA 15 Permissive Software Licenses (1) ● Permissive licenses constitute a subset of FOSS licenses. ● These licenses permit almost any use of the code. – See: Categories of Free and Nonfree Software – Lax Permissive Licensed Software https://www.gnu.org/philosophy/categories.html#LaxPe rmissiveLicensedSoftware ● Also known as: non-copyleft licenses. – See: Open Source Initiative – Frequently Answered Questions https://opensource.org/faq#permissive 16 Permissive Software Licenses (2) ● Examples: – Apache License 2.0 https://www.apache.org/licenses/LICENSE-2.0 – BSD license: ● 3-Clause BSD License/New BSD License/Modified BSD License https://opensource.org/licenses/BSD-3-Clause ● 2-Clause BSD License (Simplified BSD License/FreeBSD License) https://www.freebsd.org/copyright/freebsd-license.html – X11 License (MIT License) https://opensource.org/licenses/MIT 17 Permissive Software Licenses (3) ● Each license mentioned here permits software distributed under it to be used for closed source software projects. – Including modification of the source code and incorporating the original or the modified source code into proprietary software. 18 Permissive Software Licenses (4) ● Examples of uses: – Apache Maven (license: Apache License 2.0) https://www.apache.org/licenses/ – FreeBSD (license: FreeBSD License) https://www.freebsd.org/copyright/freebsd-license.html – Gradle (license: Apache License 2.0) https://gradle.org/license/ – HSQLDB (license: 3-clause BSD license) http://hsqldb.org/web/hsqlLicense.html – MINIX 3 (license: MINIX 3 License) http://www.minix3.org/doc/faq.html#legal – PostgreSQL (license: PostgreSQL License) https://www.postgresql.org/about/licence/ – … 19 Copyleft (1) ● The term copyleft is a twist on the term copyright. ● Copyleft is a legal instrument whose goal is the exact opposite of that of the copyright. ● The idea was invented by Richard Stallman in 1985. ● Definition: What is Copyleft https://www.gnu.org/copyleft/ 20 Copyleft (2) ● Symbol: – Source: Wikimedia Commons / Public Domain https://commons.wikimedia.org/wiki/File:Copyleft.sv g 21 Copyleft (3) ● The copyleft ensures that the protected work and any derivative works remain free forever. – When the copyleft is in effect, then all derivative works inherit the license of the original work. ● It was first used in the Emacs General Public License. – See: http://www.free-soft.org/gpl_history/emacs_gpl.html ● Not all free software licenses incorporate the copyleft mechanism. 22 Copyleft Licenses (1) ● Software licenses using the copyleft mechanism are called copyleft licenses. – They are also called as viral licenses, pejoratively. ● Copyleft licenses represent a subset of FOSS licenses that is disjoint with the set of permissive licenses. ● Copyleft licenses are further divided into strong and weak copyleft licenses. 23 Copyleft Licenses (2) ● Strong copyleft license: the copyleft applies with full force, that excludes the use of the software covered by the license for developing closed source software. – Example: GNU General Public License (GNU GPL) https://www.gnu.org/licenses/gpl.html ● Weak copyleft license: they permit the limited use of the software covered by the license such that derivative works do not fall under the copyleft. – Examples: ● GNU Lesser General Public License (GNU LGPL) https://www.gnu.org/licenses/lgpl.html ● Mozilla Public License (MPL) https://www.mozilla.org/MPL/ 24 GNU General Public License (GNU GPL) ● The latest version is version 3. https://www.gnu.org/licenses/gpl-3.0.html ● Examples of uses: – GIMP (license: GPLv3) https://www.gimp.org/about/COPYING – Linux Kernel (license: GPLv2) https://www.kernel.org/pub/linux/kernel/COPYING – Notepad++ (license: GPLv2) https://github.com/notepad-plus-plus/notepad-plus-plus/blob/master/LICENS E – R (license: GPLv2 or GPLv3) https://www.r-project.org/Licenses/ – VirtualBox (license: GPLv2) https://www.virtualbox.org/wiki/Licensing_FAQ – VLC (license: GPLv2) http://www.videolan.org/legal.html – … 25 Using GPL-Covered Software (1) ● Copyleft licenses impose limitations on the distribution of derivative works that are unacceptable for developing non-free software. ● However, they do not limit the use of the software itself. ● Example: Blender https://www.blender.org/ – It is distributed under the GPLv3. The program can be used for developing non-free software, the license does not apply to the artworks created by the program. – See: https://www.blender.org/about/license/
Load more

Recommended publications
  • An Introduction to Software Licensing
    An Introduction to Software Licensing James Willenbring Software Engineering and Research Department Center for Computing Research Sandia National Laboratories David Bernholdt Oak Ridge National Laboratory Please open the Q&A Google Doc so that I can ask you Michael Heroux some questions! Sandia National Laboratories http://bit.ly/IDEAS-licensing ATPESC 2019 Q Center, St. Charles, IL (USA) (And you’re welcome to ask See slide 2 for 8 August 2019 license details me questions too) exascaleproject.org Disclaimers, license, citation, and acknowledgements Disclaimers • This is not legal advice (TINLA). Consult with true experts before making any consequential decisions • Copyright laws differ by country. Some info may be US-centric License and Citation • This work is licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0). • Requested citation: James Willenbring, David Bernholdt and Michael Heroux, An Introduction to Software Licensing, tutorial, in Argonne Training Program on Extreme-Scale Computing (ATPESC) 2019. • An earlier presentation is archived at https://ideas-productivity.org/events/hpc-best-practices-webinars/#webinar024 Acknowledgements • This work was supported by the U.S. Department of Energy Office of Science, Office of Advanced Scientific Computing Research (ASCR), and by the Exascale Computing Project (17-SC-20-SC), a collaborative effort of the U.S. Department of Energy Office of Science and the National Nuclear Security Administration. • This work was performed in part at the Oak Ridge National Laboratory, which is managed by UT-Battelle, LLC for the U.S. Department of Energy under Contract No. DE-AC05-00OR22725. • This work was performed in part at Sandia National Laboratories.
    [Show full text]
  • FOSS Licensing
    FOSS Licensing Wikibooks.org March 13, 2013 On the 28th of April 2012 the contents of the English as well as German Wikibooks and Wikipedia projects were licensed under Creative Commons Attribution-ShareAlike 3.0 Unported license. An URI to this license is given in the list of figures on page 61. If this document is a derived work from the contents of one of these projects and the content was still licensed by the project under this license at the time of derivation this document has to be licensed under the same, a similar or a compatible license, as stated in section 4b of the license. The list of contributors is included in chapter Contributors on page 59. The licenses GPL, LGPL and GFDL are included in chapter Licenses on page 65, since this book and/or parts of it may or may not be licensed under one or more of these licenses, and thus require inclusion of these licenses. The licenses of the figures are given in the list of figures on page 61. This PDF was generated by the LATEX typesetting software. The LATEX source code is included as an attachment (source.7z.txt) in this PDF file. To extract the source from the PDF file, we recommend the use of http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/ utility or clicking the paper clip attachment symbol on the lower left of your PDF Viewer, selecting Save Attachment. After extracting it from the PDF file you have to rename it to source.7z. To uncompress the resulting archive we recommend the use of http://www.7-zip.org/.
    [Show full text]
  • Third-Party License Acknowledgments
    Symantec Privileged Access Manager Third-Party License Acknowledgments Version 3.4.3 Symantec Privileged Access Manager Third-Party License Acknowledgments Broadcom, the pulse logo, Connecting everything, and Symantec are among the trademarks of Broadcom. Copyright © 2021 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. For more information, please visit www.broadcom.com. Broadcom reserves the right to make changes without further notice to any products or data herein to improve reliability, function, or design. Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does not assume any liability arising out of the application or use of this information, nor the application or use of any product or circuit described herein, neither does it convey any license under its patent rights nor the rights of others. 2 Symantec Privileged Access Manager Third-Party License Acknowledgments Contents Activation 1.1.1 ..................................................................................................................................... 7 Adal4j 1.1.2 ............................................................................................................................................ 7 AdoptOpenJDK 1.8.0_282-b08 ............................................................................................................ 7 Aespipe 2.4e aespipe ........................................................................................................................
    [Show full text]
  • Exploring Open Source Options the Redmonk Going Open Source Series, Part 1
    April 19, 2007 Page 1/9 Exploring Open Source Options The RedMonk Going Open Source Series, Part 1 Overview Now more than ever, one of the top questions for a software company is: Michael Coté to what degree should we participate in open source? Open source is James Governor indisputably the most significant trend affecting the software world at the current time. More than any other single approach, strategy, or tactic, open Stephen O'Grady source has compelled vendors once thought to be unassailable in their respective markets - such as IBM, Microsoft and Oracle – to significantly alter their strategies. While substantial attention is paid to the source aspects of the code –the fact that it is visible, and in some cases alterable and distributable – the distribution advantages may be the most transformative, at least in the commercial world. From application servers to operating systems to programming languages to relational databases to web servers, very few categories of infrastructure software have been immune to open source competition. The packaged application market appears to be the next archipelago in the path of the tsunami, and vertical applications are undoubtedly close behind. None of this is to say that open source is necessarily the single path forward for software vendors; while that may or may not be true in the distant future, it is being actively refuted by the continuing ability of vendors such as Microsoft and Oracle to sell products that are less freely available and higher priced than their open source competition. In the case of many, if not most, of these established vendors, however, success rests more on the basis of significant market barriers to entry than on pure technical grounds.
    [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]
  • Pfc6168.Pdf (438.8Kb)
    ESCUELA TÉCNICA SUPERIOR DE INGENIERÍA DE TELECOMUNICACIÓN UNIVERSIDAD POLITÉCNICA DE CARTAGENA Proyecto Fin de Carrera TÍTULO: Iphone Bookshelf AUTOR: David Zamora Gutiérrez DIRECTOR: Francesc Burrull i Mestres Febrero / 2015 INDEX IPhone application………………………………………………………………... o Tools……………………………………………………………………… . Iphone…………………………………………………………….. Objective-C……………………………………………………….. o Code………………………………………………………………………. Web site…………………………………………………………………………... o Tools……………………………………………………………………… . Codeigniter……………………………………………………….. Php………………………………………………………………... Http……………………………………………………………….. Html………………………………………………………………. Mysql……………………………………………………………... Apache……………………………………………………………. CSS……………………………………………………………….. E-books…………………………………………………………… o Code………………………………………………………………………. References……………………………………………………………………....... IPHONE APPLICATION TOOLS IPHONE The iPhone is a line of Internet- and multimedia-enabled smartphones designed and marketed by Apple Inc. The first iPhone was unveiled by Apple CEO Steve Jobs on January 9, 2007, and released on June 29, 2007. An iPhone can function as a video camera (video recording was not a standard feature until the iPhone 3GS was released), a camera phone, can send texts and receive visual voicemail, a portable media player, and an Internet client with email and web browsing capabilities, and both Wi-Fi and 3G connectivity. The user interface is built around the device's multi-touch screen, including a virtual keyboard rather than a physical one. Third-party as well as Apple application software is available from the App Store, which launched in mid-2008 and now has over 350,000 "apps" approved by Apple. These apps have diverse functionalities, including games, reference, GPS navigation, social networking, e-books... To create applications for this device it’s use the APPLE SDK. APPLE SDK The SDK basically consists of a set of tools that Apple provides to build, debug and test our developments. It contains the following programs: - XCODE: Xcode is a suite of tools, developed by Apple, for developing software for Mac OS X and iOS.
    [Show full text]
  • Web Application License Php
    Web Application License Php Biosynthetic Ragnar peens or jeopardize some farceurs saltato, however sloshy Blaine confederates sagaciously or fother. Anhydrous and unworked Shelley labialize: which Udale is ablaze enough? Teddie easing overtime if delightsome Locke irrupt or wrote. Please user accounts directly in any other term of a website, the license is a new release. Developer website with such material without registration for confluence server. May be used by thus, not roast any cookbook. Product licensed physical therapy strongly encourages licensees to license or licenses to configure your web framework is applicable law and this tool enabling us more than the. Subsequent sections on php? If you choose this frog, will be considered Confidential Information of the Disclosing Party made this Agreement. Required for manager accounts only: up the login customer ID used to authenticate API calls. Math and licenses are the applicant company to subscribe to see a week. Take control of grace and mold your images are used with record free Pixsy account. There are also tasks for the reader to work on, make sure to consider lighting and background framing. Duo Care is our premium support package. If a form application frameworks preceding it automatically cancelled and commercial products. PHP is better suited for applications contain a prime focus on user interfaces. Send this temper your user. You can grab a copy of the file to use and tweak as fits you best. Permitted Disclosures by Developers. This section outlines the basic steps for obtaining permission. Deploy without a single fee to on local IIS. At the php app service business customers how can i platform for users happy to.
    [Show full text]
  • Extremewireless Open Source Declaration
    ExtremeWireless Open Source Declaration Release v10.41.01 9035210 Published September 2017 Copyright © 2017 Extreme Networks, Inc. All rights reserved. Legal Notice Extreme Networks, Inc. reserves the right to make changes in specifications and other information contained in this document and its website without prior notice. The reader should in all cases consult representatives of Extreme Networks to determine whether any such changes have been made. The hardware, firmware, software or any specifications described or referred to in this document are subject to change without notice. Trademarks Extreme Networks and the Extreme Networks logo are trademarks or registered trademarks of Extreme Networks, Inc. in the United States and/or other countries. All other names (including any product names) mentioned in this document are the property of their respective owners and may be trademarks or registered trademarks of their respective companies/owners. For additional information on Extreme Networks trademarks, please see: www.extremenetworks.com/company/legal/trademarks Software Licensing Some software files have been licensed under certain open source or third-party licenses. End- user license agreements and open source declarations can be found at: www.extremenetworks.com/support/policies/software-licensing Support For product support, phone the Global Technical Assistance Center (GTAC) at 1-800-998-2408 (toll-free in U.S. and Canada) or +1-408-579-2826. For the support phone number in other countries, visit: http://www.extremenetworks.com/support/contact/
    [Show full text]
  • GNU / Linux and Free Software
    GNU / Linux and Free Software GNU / Linux and Free Software An introduction Michael Opdenacker Free Electrons http://free-electrons.com Created with OpenOffice.org 2.x GNU / Linux and Free Software © Copyright 2004-2007, Free Electrons Creative Commons Attribution-ShareAlike 2.5 license http://free-electrons.com Sep 15, 2009 1 Rights to copy Attribution ± ShareAlike 2.5 © Copyright 2004-2007 You are free Free Electrons to copy, distribute, display, and perform the work [email protected] to make derivative works to make commercial use of the work Document sources, updates and translations: Under the following conditions http://free-electrons.com/articles/freesw Attribution. You must give the original author credit. Corrections, suggestions, contributions and Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license translations are welcome! identical to this one. For any reuse or distribution, you must make clear to others the license terms of this work. Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. License text: http://creativecommons.org/licenses/by-sa/2.5/legalcode GNU / Linux and Free Software © Copyright 2004-2007, Free Electrons Creative Commons Attribution-ShareAlike 2.5 license http://free-electrons.com Sep 15, 2009 2 Contents Unix and its history Free Software licenses and legal issues Free operating systems Successful project highlights Free Software
    [Show full text]
  • Open Source Issues and Opportunities (Powerpoint Slides)
    © Practising Law Institute INTELLECTUAL PROPERTY Course Handbook Series Number G-1307 Advanced Licensing Agreements 2017 Volume One Co-Chairs Marcelo Halpern Ira Jay Levy Joseph Yang To order this book, call (800) 260-4PLI or fax us at (800) 321-0093. Ask our Customer Service Department for PLI Order Number 185480, Dept. BAV5. Practising Law Institute 1177 Avenue of the Americas New York, New York 10036 © Practising Law Institute 24 Open Source Issues and Opportunities (PowerPoint slides) David G. Rickerby Boston Technology Law, PLLC If you find this article helpful, you can learn more about the subject by going to www.pli.edu to view the on demand program or segment for which it was written. 2-315 © Practising Law Institute 2-316 © Practising Law Institute Open Source Issues and Opportunities Practicing Law Institute Advanced Licensing Agreements 2017 May 12th 2017 10:45 AM - 12:15 PM David G. Rickerby 2-317 © Practising Law Institute Overview z Introduction to Open Source z Enforced Sharing z Managing Open Source 2-318 © Practising Law Institute “Open” “Source” – “Source” “Open” licensing software Any to available the source makes model that etc. modify, distribute, copy, What is Open Source? What is z 2-319 © Practising Law Institute The human readable version of the code. version The human readable and logic. interfaces, secrets, Exposes trade What is Source Code? z z 2-320 © Practising Law Institute As opposed to Object Code… 2-321 © Practising Law Institute ~185 components ~19 different OSS licenses - most reciprocal Open Source is Big Business ANDROID -Apache 2.0 Declared license: 2-322 © Practising Law Institute Many Organizations 2-323 © Practising Law Institute Solving Problems in Many Industries Healthcare Mobile Financial Services Everything Automotive 2-324 © Practising Law Institute So, what’s the big deal? Why isn’t this just like a commercial license? In many ways they are the same: z Both commercial and open source licenses are based on ownership of intellectual property.
    [Show full text]
  • A Framework for Purposeful Open Source
    Open Source Archetypes: A frameworkFramework For For Purposeful Open Source May 2018 Open Source Archetypes: A Framework For Purposeful Open Source Table of Contents Preface. 03 Introduction . 04 How to Use This Document. 05 Benefits of Open Source . 06 Open Source Project Archetypes. 10 Business-to-Business (B2B) Open Source . 11 Multi-Vendor Infrastructure . 12 Rocket Ship to Mars . 14 Controlled Ecosystem . 16 Wide Open. .. 17 Mass Market . 19 Specialty Library . 21 Trusted Vendor . 22 Upstream Dependency . 24 Bathwater . 25 Quick-Reference Comparison Of All Archetypes . 28 Practical Questions To Ask About A Project . 29 Basics of Open Source Licensing . 33 Methodology . 37 Acknowledgements . 38 Appendix – Work On ‘Openness’ At Mozilla . 38 BACK TO CONTENTS 02 Open Source Archetypes: A Framework For Purposeful Open Source Preface This report was originally commissioned by Mozilla for internal purposes. Mozilla wanted a shared framework for discussing its options in running open source projects, and requested a survey and comparative analysis of open source project archetypes — the various shapes that open source projects take in order to meet their various goals. For example, should a project prioritize development momentum over early collaborator acquisition, or vice versa? Should it optimize for individual contributors or for institutional partners? Different projects will have different answers to these and many other questions. The benefits of having a common vocabulary of archetypes extend beyond Mozilla, however, and the vocabulary is more useful and more easily improvable the more widely it is shared. Accordingly, Mozilla decided to release the report publicly. Very little has been changed from the original internal version: the Mozilla-specific orientation has been left intact, on the theory that the analysis will be clearer if tuned to a specific (and fortunately well-known) organization rather than rewritten for a hypothetical general audience.
    [Show full text]
  • Oracle Database Licensing Information, 11G Release 2 (11.2) E47877-17
    Oracle®[1] Database Licensing Information 11g Release 2 (11.2) E47877-17 September 2021 Oracle Database Licensing Information, 11g Release 2 (11.2) E47877-17 Copyright © 2004, 2021, Oracle and/or its affiliates. Contributor: Manmeet Ahluwalia, Charlie Berger, Michelle Bird, Carolyn Bruse, Rich Buchheim, Sandra Cheevers, Leo Cloutier, Bud Endress, Prabhaker Gongloor, Kevin Jernigan, Anil Khilani, Mughees Minhas, Trish McGonigle, Dennis MacNeil, Paul Narth, Anu Natarajan, Paul Needham, Martin Pena, Jill Robinson, Jenny Tsai-Smith This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
    [Show full text]