DOCSLIB.ORG

Adopting and Using Open Source Software: First Annual COSI

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Adopting and Using Open Source Software: First Annual COSI Adopting and Using Open Source Software First Annual COSI Conference Held September 7, 2005 -- Redwood Shores, California Open source software is changing the way that software is being developed and used, with a significant impact on software developers, vendors, and users. Millions of people use the OpenOffice™ productivity suite and/or the Firefox™ web browser. Many of the world’s most heavily used websites are built with open source software, so almost everyone is a user of open source. Software developers also rely on open source development tools and execution environments. Companies are beginning to formulate policies around their use of open source software, as well as adjusting their acquisition, adoption, and development processes. This one-day conference, organized by Carnegie Mellon's Center for Open Source Investigation (COSI), brought together leading experts from industry and academia to discuss key topics in evaluating, adopting, licensing, using, and supporting open source software. These experts have extensive experience with both traditional packaged and open source products. The goal of the conference is to help companies understand technical, business, and organizational issues that influence decisions about open source solutions. The conference is aimed at managers with responsibility for software product development, software acquisition, internal IT operations, and related policy- making. We are grateful to our sponsors for their support. Speakers and topics included: Rod Smith, IBM, “Open source development and use: the big picture” Shaun Connolly, JBoss, “Making the move from packaged software to open source” Wim Coekaerts, Oracle, "Deploying Open Source in an Enterprise Environment" Lawrence Rosen, Attorney, Rosenlaw and Einschlag, “Making sense of open source software licensing” Brian Behlendorf, CollabNet, “Building and working with collaborative communities” Stormy Peters, HP, “Establishing open source policies in your company” From cosi.west.cmu.edu/conference05/ 1 6 January 2006 These presentations were complemented by panel discussions on evaluating, adopting, and supporting open source software. COSI Conference Sponsors Gold Sponsors Silver Sponsors From cosi.west.cmu.edu/conference05/ 2 6 January 2006 Adopting and Using Open Source Software First Annual COSI Conference September 7, 2005 -- Redwood Shores, California Conference Program Welcome Anthony I. Wasserman Conference Chair, Carnegie Mellon West James H. Morris Dean, Carnegie Mellon West Open Source Development and Use: the Big Picture Rod Smith, IBM Panel: Evaluating and Adopting Open Source Software Chair: William Scherlis, Carnegie Mellon University Panelists: Kim Polese, SpikeSource; Matt Thompson, Sun Microsystems Deploying Open Source in an Enterprise Environment Wim Coekaerts, Oracle Making the Move from Packaged Source to Open Source Shaun Connolly, JBoss Building communities for collaboration Brian Behlendorf, CollabNet Making sense of open source software licensing Lawrence Rosen, Attorney, Rosenlaw and Einschlag Panel: Using and Supporting Open Source Software Chair: James D. Herbsleb, Carnegie Mellon University Panelists: Chris DiBona, Google; From cosi.west.cmu.edu/conference05/ 3 6 January 2006 David Intersimone, Borland Establishing open source policies in your company Stormy Peters, Hewlett-Packard Panel: Future directions in open source research and practice Chair: Anthony I. Wasserman, Carnegie Mellon West Panelists: Chris DiBona, Google; Murugan Pal, SpikeSource; William Scherlis, Carnegie Mellon University From cosi.west.cmu.edu/conference05/ 4 6 January 2006 Speaker Biographies Brian Behlendorf Brian Behlendorf founded CollabNet, with O'Reilly & Associates, in July 1999. The company provides tools and services based on open source methods. Before launching CollabNet, Behlendorf was co-founder and CTO of Organic Online, a Web design and engineering consultancy located in San Francisco. During his five years at Organic, Behlendorf helped create Internet strategies for dozens of Fortune 500 companies. During that time, he co-founded and contributed heavily to the Apache Web Server Project, co-founded and supported the VRML (Virtual Reality Modeling Language) effort, and assisted several IETF working groups, particularly the HTTP standardization effort. Before starting Organic, Behlendorf was the first Chief Engineer at Wired Magazine and later HotWired, one of the first large-scale publishing Web sites. Behlendorf is Director of the Apache Software Foundation. Wim Coekaerts Wim Coekaerts is principal member of technical staff, Linux Kernel Group, Corporate Architecture for Oracle Corporation. Within Oracle's "Linux kernel group," Mr. Coekaerts is involved in prototyping and doing research in clustering technologies in Linux as well as single node features. Mr. Coekaerts joined Oracle Belgium in 1995 as a technical engineer for Oracle Support Services, moving to Oracle HQ in 1997, where he held various positions in program management for Oracle's worldwide solutions support group. Two years later he began work on the prototype of Oracle Database Appliance, focused on the tight integration of the database with operating system such as Solaris and Linux. In 2000, Mr. Coekaerts was asked to design, prototype and develop an Oracle Linux-based Internet appliance. Oracle CEO Larry Ellison later spun it off into a new company now called the New Internet Computer. Prior to joining Oracle, Mr. Coekaerts oversaw software projects and Linux migration for the data center at the University of Leuven, Belgium. Mr. Coekaerts received a degree in computer science from Catholic University of Leuven, Belgium. Shaun Connolly As Vice President of Product Management at JBoss, Inc., Shaun Connolly is responsible for managing the products that comprise the JBoss Enterprise Middleware System. Prior to joining JBoss, Shaun was Vice President of Product Integration at Princeton Softech where he led the development of integrated database archiving solutions for the top ERP/CRM applications. Shaun was also Director of Product Management for HP Middleware and Bluestone Software where he focused on creating a modular, service-centric enterprise middleware platform. Before joining Bluestone, Shaun served as Vice President of Development at Primavera Systems, a leading project management software provider. Shaun holds a B.S. in Electrical Engineering from Drexel University and has been a panelist, speaker, and contributor of articles on such topics as aligning IT operations with business goals and getting the most from IT investments. Chris DiBona Chris DiBona is the Open Source Programs Manager for Mountain View, Ca based Google, Inc. His job includes releasing open source software on Google's Code website. Before joining Google, Mr. DiBona was an editor/author for the popular online website slashdot.org and He is an internationally known advocate of open source software and related methodologies. He co-edited the award winning essay compilations "Open Sources" and "Open Sources 2.0" and writes for a great number of publications. He was briefly the Linux guy on TechTV and speaks on a variety of open source issues internationally. James D. Herbsleb James D. Herbsleb is the A. Nico Haberman Associate Professor of Computer Science at Carnegie Mellon University. His research interests lie primarily in the intersection of software engineering and computer- supported cooperative work, focusing on such areas as geographically-distributed development teams, open source software development, and more generally on oordination in software engineering. He holds a JD (1980), and a PhD (1984) in psychology from the University of Nebraska, and a MS (1991) in computer science from the University of Michigan. After completing a post-doctoral fellowship at the University of Michigan, he moved to Carnegie Mellon's Software Engineering Institute, where he led an effort to empirically validate the CMM for Software. He then joined the Software Production Research Department at Lucent Technologies, where he initiated and led the Bell Labs Collaboratory Project, which conducted empirical studies and designed collaborative technologies and practices for global software development. David Intersimone As Vice President of Developer Relations and Borland's Chief Evangelist, David (David I) Intersimone is responsible for the Borland Developer Network Web site, an online community that allows software developers to communicate, collaborate, and gain access to unique content. He is also responsible for Borland's Technology Partner (BTP) program, building full-service developer programs for third-party software developers whose components, tools, libraries, and class libraries integrate with and add value to Borland's products. Additionally, David works with enterprise customers, professional programmers, user groups, the technical press, book authors, and educators around the world, conducting technical presentations and ensuring that their needs and requirements are folded into Borland's strategic product plans. James H. Morris Dr. James H. Morris is a Professor of Computer Science and Dean of Carnegie Mellon West. He is a native of Pittsburgh and received a Bachelor's degree from Carnegie Mellon, an MS in Management from MIT and Ph.D. in Computer Science from MIT. He taught at the University of California at Berkeley where he developed some important underlying principles of programming languages: inter-module protection and lazy evaluation. He was a co-discoverer of the
Load more

Recommended publications
  • 50109195.Pdf
    UNIVERSIDAD DE EL SALVADOR FACULTAD MULTIDISCIPLINARIA ORIENTAL DEPARTAMENTO DE INGENIERÍA Y ARQUITECTURA TRABAJO DE GRADO: IMPACTO DEL SOFTWARE LIBRE EN LAS INSTITUCIONES DE EDUCACIÓN MEDIA DEL MUNICIPIO DE SAN MIGUEL DURANTE EL AÑO 2019 Y CREACIÓN DE PLATAFORMA VIRTUAL PARA EL REGISTRO DE DICHA INFORMACIÓN. PARA OPTAR AL TÍTULO DE: INGENIERO DE SISTEMAS INFORMÁTICOS PRESENTADO POR: EVER FERNANDO ARGUETA CONTRERAS. ROBERTO CARLOS CÁRDENAS RAMÍREZ. GERSON ALEXANDER SANDOVAL GUERRERO. DOCENTE ASESOR: INGENIERO LUIS JOVANNI AGUILAR CIUDAD UNIVERSITARIA ORIENTAL, 11 DE SEPTIEMBRE DE 2020 SAN MIGUEL, EL SALVADOR, CENTRO AMÉRICA UNIVERSIDAD DE EL SALVADOR AUTORIDADES Msc. ROGER ARMANDO ARIAS RECTOR PhD. RAÚL ERNESTO AZCÚNAGA LÓPEZ VICERECTOR ACADÉMICO INGENIERO JUAN ROSA QUINTANILLA VICERECTOR ADMINISTRATIVO INGENIERO FRANCISCO ALARCÓN SECRETARIO GENERAL LICENCIADO RAFAEL HUMBERTO PEÑA MARÍN FISCAL GENERAL LICENCIADO LUIS ANTONIO MEJÍA LIPE DEFENSOR DE LOS DERECHOS UNIVERSITARIOS FACULTAD MULTIDISCIPLINARIA ORIENTAL AUTORIDADES LICENCIADO CRISTÓBAL HERNÁN RÍOS BENÍTEZ DECANO LICENCIADO OSCAR VILLALOBOS VICEDECANO LICENCIADO ISRRAEL LÓPEZ MIRANDA SECRETARIO INTERINO LICENCIADO JORGE PASTOR FUENTES CABRERA DIRECTOR GENERAL DE PROCESOS DE GRADUACIÓN DEPARTAMENTO DE INGENIERIA Y ARQUITECTURA AUTORIDADES INGENIERO JUAN ANTONIO GRANILLO COREAS. JEFE DEL DEPARTAMENTO. INGENIERA LIGIA ASTRID HERNANDEZ BONILLA COORDINADORA DE LA CARRERA DE INGENIERIA EN SISTEMAS INFORMATICOS INGENIERA MILAGRO DE MARÍA ROMERO DE GARCÍA COORDINADORA DE PROCESOS DE GRADUACIÓN TRIBUNAL EVALUADOR INGENIERO LUIS JOVANNI AGUILAR JURADO ASESOR INGENIERO LUDWIN ALDUVÍ HERNÁNDEZ VÁSQUEZ DOCENTE JURADO CALIFICADOR INGENIERA LIGIA ASTRID HERNANDEZ BONILLA DOCENTE JURADO CALIFICADOR AGRADECIMIENTOS A DIOS: Por darme la oportunidad de vivir y por haberme dado la sabiduría para poder culminar mis estudios y por fortalecer mi corazón e iluminar mi mente, por haber puesto en mi camino a aquellas personas que han sido mi soporte y compañía durante todo el periodo de estudio.
    [Show full text]
  • 2004 February
    February 2004 Games and Entertainment Megan Morrone Today you can use the same machine to organize your finances, create a presentation for your boss, and defend the Earth from flesh-eating aliens. But let’s be honest: Even with the crazy advances in software, organizing your finances and creating a presentation for your boss are still not half as much fun as defending the Earth from flesh-eating aliens.That’s why we’ve devoted the entire month of February to the noble pursuit of games and entertainment for PCs, Macs, game consoles, and PDAs. I know what you’re thinking.You’re thinking that you can skip right over this chapter because you’re not a gamer. Gamers are all sweaty, pimpled, 16-year-old boys who lock themselves in their basements sustained only by complex carbohydrates and Mountain Dew for days on end, right? Wrong.Video games aren’t just for young boys anymore. Saying you don’t like video games is like saying you don’t like ice cream or cheese or television or fun.Are you trying to tell me that you don’t like fun? If you watch The Screen Savers,you know that each member of our little TV family has a uniquely different interest in games. Morgan loves a good frag fest, whereas Martin’s tastes tend toward the bizarre (think frogs in blenders or cow tossing.) Kevin knows how to throw a cutting-edge LAN party,while Joshua and Roger like to kick back with old-school retro game emulators. I like to download free and simple low-res games that you can play on even the dinkiest PC, whereas Patrick prefers to build and rebuild the perfect system for the ultimate gaming experience (see February 13).And leave it to Leo to discover the most unique new gaming experience for the consummate early adopter (see February 1).
    [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]
  • Tout, Vous Saurez Tout Sur Google Et L'open Source
    Tout, vous saurez tout sur Google et l’Open Source Profitons de l’actualité récente de Google, qui a fermé plusieurs de ses services ou s’apprête à le faire (exemple parfait qu’il faut développer et encourager les services Web Open Source pour que, à l’instar des logiciels libres "classiques", leur pérennité soit assurée) pour évoquer la politique du géant incontournable de la recherche (mais aussi de la messagerie électronique, des documents en ligne, de la gestion de photos et j’en passe…) concernant l’Open Source. Chacun sait que Google, même s’il garde jalousement l’algorithme de son moteur de recherche, contribue largement au monde de l’Open Source (Google Summer of Code, GoogleCode, Android etc.). [1] Cet article, entretien avec Chris DiBona, responsable de l’Open Source chez Google, n’est pas des plus récents, mais il est d’autant plus intéressant à relire aujourd’hui qu’entre- temps Google a sorti son navigateur Chrome (la question de la relation entre Google et Mozilla est abordée dans l’entretien) et s’apprête par exemple à libérer le code d’applications (parce qu’elles n’étaient pas rentables) telles que le réseau de microblogging Jaiku. Entretien avec Chris DiBona de Google Interview with Chris DiBona of Google Sean Ammirati – 26 avril 2007 – ReadWriteWeb Traduction Framalang : Penguin, Olivier, Don Rico Il y a quelques semaines, j’ai eu l’occasion d’écouter Chris DiBona, le responsable du programme Open Source chez Google, qui a fait une intervention lors du TiE de Pittsburgh. Pendant la conférence, Chris a donné une présentation extrêmement perspicace de l’état du marché de l’Open Source.
    [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]
  • Extensions Vs
    Confidential Information Notice Copyright 2012. All Rights Reserved. Any unauthorized reproduction of this document is prohibited. This document and the information it contains constitute a trade secret of Magento and may not be reproduced or disclosed to non-authorized users without the prior written permission from Magento. Permitted reproductions, in whole or in part, shall bear this notice. Table of Contents Preface ....................................................................................................................... 1 About This Document ...................................................................................................... 1 Updates, Comments, and Suggestions ........................................................................... 1 Disclaimer ........................................................................................................................ 1 Section 1: Introduction .......................................................................................... 2 What is Magento Connect? ............................................................................................. 2 Community Extensions vs. Commercial Extensions ....................................................... 2 Version Compatibility ....................................................................................................... 2 Section 2: How to Package & Publish Your Extension ........................................ 3 Step One: Package Your Extension ...............................................................................
    [Show full text]
  • Course 2: «Open Source Software (OSS) Engineering Data»
    Course 2: «Open Source Software (OSS) Engineering Data». 1st Day: Metrics and Tools for Software Engineering in Open Source Software 1. Open Software / Hardware Technologies: Introduction to Open Source Software and related technologies. 2. Software Engineering FLOSS: Free Libre Open Source Software in Software Engineering. 3. Metrics for Open Source Software: product and project metrics and related tooling. 2nd Day: Research based on Open Source Software Data 4. Facilitating Metric for White-Box Reuse: we will discuss a metric derived from the analysis of Open Source Project which facilitates the white-box reuse (reuse based on the source code analysis). 5. Extracting components from Open-Source: The Component Adaptation Environment Approach (COPE): we will discuss the results of the OPEN-SME EU Research Project and in particular the COPE tool for extracting reusable components from Open Source Software. 6. Software Engineering Research based on Open Source Software Data: Data, A recent example: we will discuss a recent study of open source repository mailing lists for deriving implications for the evolution of an open source project. 7. Improving Component Coupling Information with Dynamic Profiling: we will discuss how dynamic profiling of an open source program can contribute towards its comprehension. In various points during the lectures students will be asked to carry out activities. Open Software / Hardware Technologies Ioannis Stamelos, Professor Nikolaos Konofaos, Associate Professor School of Informatics Aristotle University of Thessaloniki George Kakarontzas, Assistant Professor University of Thessaly 2018-2019 1 F/OSS - FLOSS Definition ● The traditional SW development model asks for a “closed member” team that develops proprietary source code.
    [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]
  • Commercializing Open Source Software: Do Property Rights Still Matter?
    Columbia Law School Scholarship Archive Faculty Scholarship Faculty Publications 2006 Commercializing Open Source Software: Do Property Rights Still Matter? Ronald J. Mann Columbia Law School, [email protected] Follow this and additional works at: https://scholarship.law.columbia.edu/faculty_scholarship Part of the Computer Law Commons, and the Intellectual Property Law Commons Recommended Citation Ronald J. Mann, Commercializing Open Source Software: Do Property Rights Still Matter?, 20 HARV. J. L. & TECH. 1 (2006). Available at: https://scholarship.law.columbia.edu/faculty_scholarship/739 This Article is brought to you for free and open access by the Faculty Publications at Scholarship Archive. It has been accepted for inclusion in Faculty Scholarship by an authorized administrator of Scholarship Archive. For more information, please contact [email protected]. HarvardJournal of Law & Technology Volume 20, Number 1 Fall 2006 COMMERCIALIZING OPEN SOURCE SOFTWARE: Do PROPERTY RIGHTS STILL MATTER? Ronald J Mann* TABLE OF CONTENTS I. IN TRO DU CTIO N .................................................................................. 1 11. THE LANDSCAPE .......................................................................... 5 A. The ProprietarySoftware Model .............................................. 5 1. Formation and Maturation of the Proprietary Software Industry ......................................................................... 5 2. Software Licensing Under Proprietary Models .................... 8 3.
    [Show full text]
  • Business and Sustainability Models Around Free and Open Source Software
    Business and Sustainability Models Around Free and Open Source Software OUCS, 12 January 2009 Event tag: ossw_fosssustain2009 Hashtag: ossw ●Housekeeping ●Who are OSS Watch? http://www.oss-watch.ac.uk [email protected] Objectives for the day ●Understand the varying licensing and community models that underlie free and open source sustainability models. ● Have a greater familiarity with the most commonly-employed sustainability models. ● Recognise where FOSS exploitation strategies may be of value. Fundamentals of Free and Open Source Software Ross Gardler Slides adapted from a deck created by Rowan Wilson What we will cover: ● What is FOSS? ● Some history ● Varieties of FOSS Licence ● How a FOSS project works What is FOSS? ● Software ● Software License ● Software development methodology ● High Quality ● Linux, Apache HTTPD, Firefox, OpenOffice.org, XenSource, MySQL, SugarCRM, Alfresco ●Business model What we will cover: ● What is FOSS? ● Some history ● Varieties of FOSS Licence ● How a FOSS project works Some History (Early days of software) ● Originally specialist software bundled with hardware ● Source code supplied under permissive licences ● Personal computers created a software market ● Bill Gates writes open letter to 'Hobbyists' in 1976: “Hardware must be paid for, but software is something to share... Is this fair?” ● Software was sold ● Some felt this was detrimental to software production Some More History (A turning point - 1984) ● Richard Stallman commences GNU Emacs ● first software from the GNU Project (think GNU/Linux)
    [Show full text]
  • Netscaler® 13.0 - Third Party Notices
    NetScaler® 13.0 - Third Party Notices NetScaler 13.0 may include third party software components licensed under the following terms. This list was generated using third party software as of the date listed. This list may change with specific versions of the product and may not be complete; it is provided “As-Is.” TO THE EXTENT PERMITTED BY APPLICABLE LAW, CITRIX AND ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, WITH REGARD TO THE LIST OR ITS ACCURACY OR COMPLETENESS, OR WITH RESPECT TO ANY RESULTS TO BE OBTAINED FROM USE OR DISTRIBUTION OF THE LIST. BY USING OR DISTRIBUTING THE LIST, YOU AGREE THAT IN NO EVENT SHALL CITRIX BE HELD LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY OTHER DAMAGES WHATSOEVER RESULTING FROM ANY USE OR DISTRIBUTION OF THIS LIST. 1 Table of Contents Adaptive Communication Environment (ACE) 6.3.1 ................................................................................... 17 Apache HTTP Server 2.4.39 ......................................................................................................................... 17 Apache Tomcat 8.5.34 ................................................................................................................................ 17 Apache Xalan C++ 1.10.0 ............................................................................................................................ 17 Apache Xerces C++ 2.7.0 ............................................................................................................................
    [Show full text]
  • Copyright Issues with Open Source Software
    www.dwt.com COPYRIGHT ISSUES WITH OPEN SOURCE SOFTWARE I. INTRODUCTION Today, most companies are using open source software internally, and many are actively distributing open source software either within software programs or embedded in physical products. According to one study, ninety percent of companies will utilize OSS either directly or embedded in other programs by 2012.1 When companies use open source software in development projects, one survey found that twenty-two percent of the software product or application is open source software.2 Software developers, especially those newly educated, view OSS as another resource to use in developing software.3 The term “open source” refers to a concept of freedom of software, not freedom from costs associated with using the software.4 The bottom line is that users are not free to use the software in any way that they might like; if users do not heed the requirements placed on the use of OSS, they might find themselves embroiled in an action claiming copyright infringement.5 Each piece of OSS has an accompanying license. Although these licenses may be grouped into three broad categories, permissive, weak “copyleft,” and strong “copyleft,”6 figuring out which restrictions apply to software programs that combine different pieces of OSS, and, more fundamentally, whether the licenses even allow the pieces to be combined, are daunting tasks. The Open Source Initiative (OSI) has approved approximately seventy separate OSS licenses.7 In addition, open source developers have created hundreds of other versions of software 1 Richard Acello, Opening Up to Open Source: Corporation Counsel Must Be Ready to Deal with “Free” Software and Its Licensing, 94–JUN A.B.A.
    [Show full text]