DOCSLIB.ORG

Measuring Inner Source Collaboration

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Measuring Inner Source Collaboration Measuring Inner Source Collaboration Vermessung von Inner-Source-Zusammenarbeit Der technischen Fakultät der Friedrich-Alexander-Universität Erlangen-Nürnberg zur Erlangung des Doktorgrades Doktor-Ingenieur (Dr.-Ing.) vorgelegt von Maximilian Capraro Als Dissertation genehmigt von der Technischen Fakultät der Friedrich-Alexander-Universität Erlangen-Nürnberg Tag der mündlichen Prüfung: 19. Mai 2020 Vorsitzender des Promotionsorgans: Prof. Dr.-Ing. Andreas P. Fröba Gutachter: Prof. Dr. Dirk Riehle Prof. Dr. Brian Fitzgerald Copyright © 2020 – Maximilian Capraro. All rights reserved. Abstract Inner source (IS) is the use of open source software development practices and the establish- ment of open source-like communities within an organization. The organization may still de- velop proprietary software but internally opens up its development. IS promises to resolve problems of traditional software development by easing software reuse and enabling parties within an organization to collaborate across organizational boundaries. However, it is unclear what elements constitute IS (problem I) and how to measure the pres- ence and magnitude of IS collaboration (problem II). The large majority of research articles on IS to date are limited to qualitative results regarding IS. There are yet no quantitative studies on IS collaboration exploring how much IS collaboration takes place or how IS practices affect it (problem III). Wefollowed a three-phase research approach to address these problems. First, we performed an extensive literature survey and analyzed 43 IS publications. We found that four key elements constitute IS (shared cultural values, open development environment, communities around software, IS-specific scenarios) but that IS programs and projects differ on at least five dimen- sions (addressing problem I). Second, we developed the patch-flow method (and a software tool implementing it) for measur- ing IS collaboration. Patch-flow is the flow of code contributions across organizational bound- aries (“silos”) such as organizational unit or cost center boundaries. We evaluated the method using case study research with a non-trivial industry organization and found it to be viable and useful to practitioners (addressing problem II). Third, we performed a multiple-case case study with three large software organizations running a total of five IS program. We identified the used IS practices and the resulting patch-flow. We found patch-flow to exist in all organizations but that only fraction of all code contributions to IS projects constitute patch-flow. We observed that the number of IS practices implemented correlates with the distance of parties involved in collaboration. This indicates that IS is par- ticularly suited to enable collaboration between parties of high distance in an organization (ad- dressing problem III). This thesis delivers a holistic definition of IS and the first classification framework for IS pro- grams and projects. Researchers can use such a framework to reason about generalizability of their results more precisely. The patch-flow measurement method is the first of its kind to measure and quantify IS collaboration and can serve as a base for further quantitative analyses of IS collaboration. The exploration of the patch-flow in the three industry cases can serve as example and benchmark for practitioners. v Zusammenfassung Inner Source (IS) ist die Verwendung von Softwareentwicklungspraktiken aus dem Open- Source-Umfeld und die Etablierung von open-source-artigen Communities innerhalb der Gren- zen einer Organisation. Die Organisation kann dabei weiterhin proprietäre Software entwick- eln und öffnet die Softwareentwicklung lediglich für interne Teilnehmer. IS löst Probleme der traditionellen Softwareentwicklung, in dem es Wiederverwendung vereinfacht und Parteien innerhalb einer Organisation erlaubt, über organisationsinterne Grenzen hinweg, zusammen- zuarbeiten. Allerdings ist unklar, welche Elemente IS definieren (Problem I) und wie man das Vorhan- densein und Ausmaß von IS-Zusammenarbeit messen kann (Problem II). Die Mehrheit an existierenden Forschungsartikeln zu IS präsentiert lediglich qualitative Ergebnisse. Es gibt bis jetzt keine quantitativen Studien, die explorieren wie viel IS-Zusammenarbeit vorkommt oder wie IS-Praktiken sie beeinflussen (Problem III). Wir adressieren diese Probleme mit einem Forschungsansatz in drei Phasen: Im der ersten Phase führen wir ein umfangreiches Literatur-Survey durch und analysieren 43 Publikationen zu IS. Wir stellen vier Schlüsselelemente vor, die IS ausmachen (gemeinsame kulturelle Werte, eine of- fene Entwicklungsumgebung, Communities um Software, IS-spezfische Szenarios) und zeigen, dass IS-Programme und -Projekte sich in mindestens fünf Dimensionen unterscheiden können (adressiert Problem I). Im zweiten Schritt entwickelen wir die Patch-Flow Methode (und ein Softwarewerkzeug, dass sie implementiert) um die Vermessung von IS-Zusammenarbeit zu ermöglichen. Patch-Flow ist der Fluss von Codebeiträgen über organisationsinterne Grenzen (“Silos”) wie beispielsweise Organisationseinheiten oder Kostenstellen hinweg. Wir evaluieren die Methode mittels Fallstu- dienforschung in einer nicht-trivialen Organisation und zeigen, dass die Methode in der Praxis umsetzbar und für Praktiker von Nutzen ist (adressiert Problem II). Im dritten Schritt führen wir eine Fallstudie mit drei großen Softwareorganisationen durch, die insgesamt fünf IS-Programme betreiben. Wir identifizieren verwendete IS-Praktiken und vermessen den Patch-Flow. Patch-flow existiert in allen untersuchten Organisationen, jedoch ist nur ein Bruchteil aller Codebeiträge Patch-Flow. Wir beobachteten, dass die Anzahl der IS- Praktiken mit der Distanz der zusammenarbeitenden Parteien korreliert. Das deutet darauf hin, dass IS besonders geeignet ist, um Zusammenarbeit zwischen Parteien in hoher Distanz zu ermöglichen (adressiert Problem III). Diese Thesis präsentiert eine umfassende Definition von IS sowie das erste Klassifikationsrah- menwerk für IS-Programme und -Projekte. Forscher können das Rahmenwerk nutzen um die Generalisierbarkeit ihrer Ergebnisse präziser zu diskutieren. Die Patch-Flow Methode ist die er- ste Methode zur Vermessung und Quantifizierung der IS-Zusammenarbeit. Sie kann als Basis für weitere quantitative Analysen der IS-Zusammenarbeit dienen. Die Exploration des Patch- Flow in drei Organisationen dient als Beispiel und Benchmark für Praktiker. vii Contents 1 Introduction 1 1.1 Motivation, Research Questions, Contributions ............... 2 1.1.1 Inner Source Taxonomy ....................... 3 1.1.2 Method for Measuring Inner Source Collaboration . 4 1.1.3 Influence of Inner Source Practices on Collaboration . 5 1.2 Inner Source Definitions ........................... 6 1.3 Thesis Structure ................................ 7 2 Inner Source Taxonomy 9 2.1 Related Work ................................. 10 2.1.1 Elements of Inner Source ....................... 10 2.1.2 Classification Framework ....................... 11 2.2 Research Approach .............................. 11 2.2.1 Literature Selection .......................... 11 2.2.2 Resulting Literature ......................... 13 2.2.3 Literature Analysis .......................... 16 2.3 Key Elements of Inner Source ......................... 17 2.3.1 Open Environment .......................... 19 2.3.2 Shared Cultural Values ........................ 21 2.3.3 Communities around Software .................... 22 2.3.4 Inner Source Scenarios ........................ 23 2.4 Classification Framework for Inner Source . 25 2.4.1 Classification of Inner Source Programs . 25 2.4.2 Classification of Inner Source Projects . 29 2.5 Application of the Classification Framework . 32 2.5.1 Application to Inner Source Programs . 32 2.5.2 Application to Inner Source Projects . 37 2.6 Conclusion .................................. 38 3 Patch-Flow Measurement Method 39 3.1 Related Work ................................. 40 3.1.1 Measuring Inner Source Collaboration . 40 3.1.2 Measuring Software Development Collaboration . 41 3.2 Patch-Flow Measurement Method ...................... 43 3.2.1 Contribution-Flow Phenomenon . 43 3.2.2 Patch-Flow Phenomenon ....................... 43 3.2.3 Data Structures ............................ 45 3.2.4 Measurement Process ......................... 47 3.2.5 Relationship to Classification ..................... 48 3.3 Evaluation Approach ............................. 50 ix 3.3.1 Case Selection ............................. 50 3.3.2 Data Gathering ............................ 51 3.4 Evaluation Results ............................... 53 3.4.1 Organizational Structure ....................... 53 3.4.2 Patch-Flow Overview ......................... 55 3.4.3 Patch-Flow Over Time ........................ 57 3.4.4 Patch-Flow into IS Projects ...................... 58 3.5 Discussion ................................... 61 3.5.1 Evaluation .............................. 61 3.5.2 Operational Inner Source Definition . 63 3.6 Trustworthiness ................................ 63 3.6.1 Credibility .............................. 64 3.6.2 Dependability ............................ 64 3.6.3 Confirmability ............................ 64 3.6.4 Transferability ............................ 64 3.7 Conclusion .................................. 65 4 Patch-Flow Crawler: A Toolfor Measuring Patch-Flow 67 4.1 Requirements ................................. 68 4.1.1 Overview ............................... 69 4.1.2 Identify and Persist Inner Source Projects
Load more

Recommended publications
  • An Empirical Investigation Into the Adoption of Inner Source in IT Companies: a Case Study Master’S Thesis in Software Engineering and Management
    An Empirical Investigation into the Adoption of Inner Source in IT Companies: A Case Study Master’s Thesis in Software Engineering and Management NILOOFAR SAFAVI Department of Computer Science and Engineering Chalmers University of Technology University of Gothenburg Gothenburg, Sweden 2019 An Empirical Investigation into the Adoption of Inner Source in IT Companies: A Case study NILOOFAR SAFAVI Department of Computer Science and Engineering Chalmers University of Technology University of Gothenburg Göteborg, Sweden 2019 ii An Empirical Investigation into the Adoption of Inner Source in IT Companies: A Case Study NILOOFAR SAFAVI © NILOOFAR SAFAVI, 2019 Supervisor: Imed Hammouda Examiner: Eric Knaus Master’s Thesis 2019 Department of Computer Science and Engineering Chalmers University of Technology University of Gothenburg SE-412 96 Göteborg Sweden Telephone + 46 (0)31-772 1000 Cover: Inner Source in a corporation [51] iii An Empirical Investigation into the Adoption of Inner Source in IT Companies: A Case Study NILOOFAR SAFAVI Department of Computer Science and Engineering Chalmers University of Technology and University of Gothenburg Abstract Inner Source is a rather new concept and introducing it to companies involves some challenges. In this thesis, we investigate the challenges and obstacles of adopting Inner Source in a large IT company. The results are then analyzed and summarized. In addition, the company owns many products and needs to decide which products are suitable for inner sourcing purpose. The criteria for selection of the products are investigated and the results are compared to the results of the previous studies. In the final stage, we investigate a framework for adoption of Inner Source tailored to the needs of the company and compared the results to other available frameworks.
    [Show full text]
  • 18 Key Factors for Adopting Inner Source
    Key Factors for Adopting Inner Source KLAAS-JAN STOL, Lero, University of Limerick PARIS AVGERIOU , University of Groningen MUHAMMAD ALI BABAR, IT University of Adelaide YAN LUCAS, Neopost Technologies BRIAN FITZGERALD, Lero, University of Limerick A number of organizations have adopted Open Source Software (OSS) development practices to support or augment their software development processes, a phenomenon frequently referred to as Inner Source. However the adoption of Inner Source is not a straightforward issue. Many organizations are struggling with the question of whether Inner Source is an appropriate approach to software development for them in the first place. This article presents a framework derived from the literature on Inner Source, which identifies nine important factors that need to be considered when implementing Inner Source. The framework can be used as a probing instrument to assess an organization on these nine factors so as to gain an understanding of whether or not Inner Source is suitable. We applied the framework in three case studies at Philips Healthcare, Neopost Technologies, and Rolls-Royce, which are all large organizations that have either adopted Inner Source or were planning to do so. Based on the results presented in this article, we outline directions for future research. Categories and Subject Descriptors: D.2.9 [Software Engineering]: Management—Software process models; K.6.3 [Management of Computing and Information Systems]: Software Management—Soft- ware development, Software maintenance, Software process General Terms: Human Factors, Management, Theory Additional Key Words and Phrases: Case study, inner source, open-source development practices, framework ACM Reference Format: Klaas-Jan Stol, Paris Avgeriou, Muhammad Ali Babar, Yan Lucas, and Brian Fitzgerald.
    [Show full text]
  • Department Informatik Inner Source in Platform-Based Product Engineering
    Department Informatik Technical Reports / ISSN 2191-5008 Dirk Riehle, Maximilian Capraro, Detlef Kips, Lars Horn Inner Source in Platform-Based Product Engineering Technical Report CS-2015-02 Please cite as: Dirk Riehle, Maximilian Capraro, Detlef Kips, Lars Horn, “Inner Source in Platform-Based Product Engineering,” Friedrich-Alexander-Universitat¨ Erlangen-Nurnberg,¨ Dept. of Computer Science, Technical Reports, CS-2015-02, . Friedrich-Alexander-Universitat¨ Erlangen-Nurnberg¨ Department Informatik Martensstr. 3 · 91058 Erlangen · Germany www.cs.fau.de Inner Source in Platform-Based Product Engineering Dirk Riehle, Maximilian Capraro, Detlef Kips, Lars Horn Abstract—Inner source is an approach to collaboration across intra-organizational boundaries for the creation of shared reus- able assets. Prior project reports on inner source suggest improved code reuse and better knowledge sharing. Using a multiple- case case study research approach, we analyze the problems that three major software development organizations were facing in their platform-based product engineering efforts. We find that a root cause, the separation of product units as profit centers from a platform organization as a cost center, leads to delayed deliveries, increased defect rates, and redundant software com- ponents. All three organizations assume that inner source can help solve these problems. The article analyzes the expectations that these companies were having towards inner source and the problems they were experiencing or expecting in its adoption. Finally, the article presents our conclusions on how these organizations should adapt their existing engineering efforts. Index terms—Inner source, product line engineering, product families, platform-based product engineering, open source, open collaboration, case study research. 1. INTRODUCTION aforementioned articles to their situation.
    [Show full text]
  • Wednesday October 4
    We offer 20 tracks to help you navigate the schedule. Like tracks are color coded for even easier exploration. CAREER ARTIFICIAL WEDNESDAY INTELLIGENCE COMMUNITY OCTOBER 4 COMPUTER SYSTEMS CRA-W ENGINEERING STUDENT DATA SCIENCE OPPORTUNITY LAB HUMAN COMPUTER ACM RESEARCH INTERACTION COMPETITION INTERACTIVE MEDIA GENERAL POSTER SESSION SECURITY/PRIVACY GENERAL SESSION SOFTWARE ENGINEERING LUNCHES & RECEPTIONS OPEN SOURCE SPECIAL SESSIONS ORGANIZATION IOT / WEARABLE TECH TRANSFORMATION PRODUCTS A TO Z //////////////////////////////////////////////// TUESDAY, OCTOBER 3 / 5 - 6 p.m. GENERAL SESSION PRESENTATION First Timers Orientation OCCC W230C All NOTE: OCCC stands for the Orange County Convention Center #GHC17 DAY 1: WEDNESDAY #GHC17 DAY 1: WEDNESDAY //////////////////////////////////////////////// //////////////////////////////////////////////// 9 - 10:30 a.m. 11 a.m. - 6:30 p.m. GENERAL SESSION CAREER Wednesday Keynote Interviews OCCC WA2 Melinda Gates OCCC WB3/4 (Bill & Melinda Gates Foundation), Fei-Fei Li //////////////////////////////////////////////// (Stanford University; Google Cloud) 11:30 a.m. - 12:30 p.m. ARTIFICIAL INTELLIGENCE PRESENTATIONS //////////////////////////////////////////////// 10:30 a.m. - 5:30 p.m. Presentations: AI for Social Good OCCC W304C Jennifer Marsman (Microsoft), CAREER EXPO Neelima Kumar (Oracle) Beginner/Intermediate Career Fair CAREER PANEL OCCC WA3/4 & WB1/2 All For Good and For Profit: Exploring Careers in SPECIAL SESSIONS Social Enterprise Speaker Lounge OCCC W305 All Hyatt Regency Ballroom V Hannah SPECIAL SESSIONS Calhoon (Blue Ridge Labs@Robin Hood), Kamla Kasichainula (Change.org), Erin Mote Faculty Lounge OCCC W209C Faculty (InnovateEDU), Morgan Berman (MilkCrate), Donnovan Andrews (Overture) All //////////////////////////////////////////////// 10:30 a.m. - 6 p.m. CAREER PANEL Women in Tech: Get a Seat @ the Table! SPECIAL SESSIONS Hyatt Regency Ballroom S Monique Student Lounge sponsored by D.E.
    [Show full text]
  • An Investigation Into Inner Source Software Development
    An Investigation into Inner Source Software Development: Preliminary Findings from a Systematic Literature Review Henry Edison Noel Carroll Kieran Conboy Lero, National University of Lero, National University of Lero, National University of Ireland Galway Ireland Galway Ireland Galway [email protected] [email protected] [email protected] Lorraine Morgan Lero, National University of Ireland Galway [email protected] ABSTRACT INTRODUCTION Given the value and effectiveness of open source software Open Source Software (OSS) has been highly prevalent in development to date, practitioners are keen to replicate these both practice and research. Given the value and effectiveness practices inside their respective corporations. This application of open source development to date, practitioners are keen to of open source practices inside the confines of a corporate replicate these practices inside their respective corporations. entity has been coined inner source software development. This application of open source practices inside the confines However, while organisations have found ways to directly ben- of a corporate entity has been coined inner source software efit from revenue streams as a result of leveraging open source (ISS) development [7, 49, 16, 41]. ISS development has been practices internally, the current research on inner source is seen as a way in which organisations adopt OSS [17, 19]. scattered among different areas. Thus gaining clarity on the Leading organisations such as Lucent Technologies, Nokia, state-of-the-art in inner source research is challenging. In Philips, IBM and HP etc, have provided example of inner particular, there is no systematic literature review of known source implementations [5], which has led to the emergence research to date on inner source.
    [Show full text]
  • The Patch-Flow Method for Measuring Inner Source Collaboration
    The Patch-Flow Method for Measuring Inner Source Collaboration Maximilian Capraro Michael Dorner∗ Dirk Riehle Friedrich-Alexander-Universität Friedrich-Alexander-Universität Friedrich-Alexander-Universität Erlangen-Nürnberg Erlangen-Nürnberg Erlangen-Nürnberg Erlangen, Germany Erlangen, Germany Erlangen, Germany [email protected] [email protected] [email protected] ABSTRACT ACM Reference Format: Inner source (IS) is the use of open source software development Maximilian Capraro, Michael Dorner, and Dirk Riehle. 2018. The Patch- (SD) practices and the establishment of an open source-like culture Flow Method for Measuring Inner Source Collaboration. In MSR ’18: MSR ’18: 15th International Conference on Mining Software Repositories , May 28– within an organization. IS enables and requires developers to collab- 29, 2018, Gothenburg, Sweden. ACM, New York, NY, USA, 11 pages. https: orate more than traditional SD methods such as plan-driven or agile //doi.org/10.1145/3196398.3196417 development. To better understand IS, researchers and practitioners need to measure IS collaboration. However, there is no method yet for doing so. In this paper, we present a method for measuring IS 1 INTRODUCTION collaboration by measuring the patch-flow within an organization. Open source software plays a key role in today’s software industry. Patch-flow is the flow of code contributions across organizational Open source (OS) development tools help to build software and boundaries such as project, organizational unit, or profit center open source components are used as part of proprietary software boundaries. We evaluate our patch-flow measurement method us- products. OS is recognized to be capable of delivering high quality ing case study research with a software developing multi-industry software [5].
    [Show full text]
  • Open Source Development Models in Satellite Communications
    Open Source Development Models in Satellite Communications A report from the OpenSatCom.org activity of the European Space Agency implemented by Libre Space Foundation and inno3 Open Source Development Models in Satellite Communications 1. Intro 3 1.1 Open source models 3 1.2 Main licenses and their differences 3 1.3 Open Standards are not Open Source methodologies 4 1.4 Open Source pervasiveness 4 1.5 Business models in Open Source, a non settled dispute 6 1.6 Open Source Business models are not only vendor-centric 7 Single-vendor centric or open governance 7 Open Source as opposed to proprietary or as opposed to Custom software development 8 1.7 Qualification of success for an Open Source business model 8 Intrinsic limitations of financial gains 8 Distribution of the generated value 8 Creation of value other than direct financial value 9 2. Open Source Development Models 10 2.1 Assessing Open Source models in the context of specific industries/ecosystems 18 2.1.1 A model Open Source ecosystem : the Linux kernel 18 Business models involved 18 Factors allowing the success 19 2.1.2 The Open Source GIS industry 20 Business models and revenue streams 20 Factors allowing the success 21 2.1.3 The automotive industry 21 The Genivi project 22 Factors allowing the success 22 The OpenMDM project 22 Factors allowing the success 23 Automotive Grade Linux 23 Baidu’s Apollo 23 Open Source Vehicles (Open Hardware/Software) 23 Business models and revenue streams 24 2.1.4 Open Source in terrestrial communications industry 24 Asterisk, Open Source PBX 24 Business models and revenue streams 24 Factors allowing the success 25 Network virtualisation 25 Business models and revenue streams 25 Factors allowing the success 26 Virtual Radio Access Networks: example of a different kind of openness 26 2.1.5 Open Hardware in telecom 27 3.
    [Show full text]
  • Open Source Systems: Towards Robust Practices
    IFIP AICT 496 Federico Balaguer Roberto Di Cosmo Alejandra Garrido Fabio Kon Gregorio Robles Stefano Zacchiroli (Eds.) Open Source Systems: Towards Robust Practices 13th IFIP WG 2.13 International Conference, OSS 2017 Buenos Aires, Argentina, May 22–23, 2017 Proceedings IFIP Advances in Information and Communication Technology 496 Editor-in-Chief Kai Rannenberg, Goethe University Frankfurt, Germany Editorial Board TC 1 – Foundations of Computer Science Jacques Sakarovitch, Télécom ParisTech, France TC 2 – Software: Theory and Practice Michael Goedicke, University of Duisburg-Essen, Germany TC 3 – Education Arthur Tatnall, Victoria University, Melbourne, Australia TC 5 – Information Technology Applications Erich J. Neuhold, University of Vienna, Austria TC 6 – Communication Systems Aiko Pras, University of Twente, Enschede, The Netherlands TC 7 – System Modeling and Optimization Fredi Tröltzsch, TU Berlin, Germany TC 8 – Information Systems Jan Pries-Heje, Roskilde University, Denmark TC 9 – ICT and Society Diane Whitehouse, The Castlegate Consultancy, Malton, UK TC 10 – Computer Systems Technology Ricardo Reis, Federal University of Rio Grande do Sul, Porto Alegre, Brazil TC 11 – Security and Privacy Protection in Information Processing Systems Steven Furnell, Plymouth University, UK TC 12 – Artificial Intelligence Ulrich Furbach, University of Koblenz-Landau, Germany TC 13 – Human-Computer Interaction Marco Winckler, University Paul Sabatier, Toulouse, France TC 14 – Entertainment Computing Matthias Rauterberg, Eindhoven University of Technology, The Netherlands IFIP – The International Federation for Information Processing IFIP was founded in 1960 under the auspices of UNESCO, following the first World Computer Congress held in Paris the previous year. A federation for societies working in information processing, IFIP’s aim is two-fold: to support information processing in the countries of its members and to encourage technology transfer to developing na- tions.
    [Show full text]
  • Starting an Open Source Program in Your Company
    Starting an Open Source Program in your Company Chris Aniszczyk (LF) Jag Gadiyaram (Capital One) Agenda › Introductions › Rise of Open Source Programs › OSPO Case Study: Capital One › TODO Group › Starting an Open Source Program › Q&A Trend: We all see Open Source is Accelerating 23M+ 41B+ 10,000+ Open Source Lines of Code New Versions Developers per Day 64M+ 1,100 Repositories on New Projects a Day GitHub Sources: Sourceclear, Sonatype, Github Trend: Open Source is Eating the World • “78% of companies are using open source… 63% are participating… ” (https://www.blackducksoftware.com/future-of-open-source) iOS: General->About->Legal->Legal Notices http://www4.mercedes-benz.com/manual-cars/ba/foss/content/en/assets/FOSS_licences.pdf https://www.tesla.com/blog/all-our-patent-are-belong-you Trend: Data Growth is Accelerating • More services/things are being connected to to the internet and generating data that will help companies optimize their business: http://www.kpcb.com/internet-trends • Cost to store data is getting much cheaper (also for fun follow @InternetOfShit) Trend: Web Scale Companies Open Up and Share › Software is a means to an end for internet/web scale companies › Google, Facebook, Netflix, Twitter, LinkedIn, etc… › Google: Kubernetes, Tensorflow › Facebook: OpenCompute, HHVM, OpenCellular › Twitter: Mesos/Aurora/Parquet/Heron › LinkedIn: Kafka › Netflix: NetflixOSS: https://netflix.github.io/ Trend: Open Source Isn’t Slowing Down Any Time Soon! Rise of Open Source Programs Trend: Web Scale Companies + Open Source Programs The internet scale companies pioneered the creation of open source programs: › Google: https://developers.google.com/open-source/ › “…tasked with maintaining a healthy relationship with the open source software development community" › Facebook: https://code.facebook.com/opensource › “…we’re keen users and publishers of open software.
    [Show full text]
  • Patrick Masson's Presentation
    Working in Open Source Patrick Masson General Manager & Board Director [email protected] ® Adobe, Amazon, Apache Software Foundation, Apple, Benetech, The Open Source Initiative Harvard University, Capital One, Carnegie Mellon, Canonical, Cisco, protects and promotes open Creative Commons, Debian, Dell, Drupal Association, Dropbox, Eclipse source software, development Foundation, edX, Elastic, Electronic Frontier Foundation, Facebook, and communities, Free Software Foundation, Gates Foundation, Github, Google, Hewlett- championing software Packard, IBM, Intel, LibreOffice, Linux Foundation, Lucidworks, freedom in society through Microsoft, MIT, Mozilla, NASA/Goddard Space Flight Center, Novell, collaboration, education, and Oracle, O'Reilly Media, PayPal, Perl Foundation, Python Foundation, infrastructure, stewarding the Open Source Definition, and Red Hat, Sunlight Foundation, Sun Microsystems, Sony, SUNY, Tufts preventing abuse of the ideals University, Twitter, UCLA, UMass, VMware, The White House, and ethos inherent to the Wikimedia Foundation, Wipro, World Wide Web Foundation... open source movement. OSI Affiliate Membership Apache Foundation Creative Commons Debian Project Document Foundation (LibreOffice) Drupal Association Eclipse Foundation Fedora Project FreeBSD Foundation Joomla (Open Source Matters) KDE e.V. Linux Foundation Mozilla Foundation Open EdX Plone Python Software Foundation Software Freedom Conservancy The Perl Foundation Wikimedia Foundation Wordpress Foundation Helping organizations authentically engage. Self-Proclaimed
    [Show full text]
  • COOPERATIVE SIGNALING BEHAVIOR: SIGNALS for OPEN SOURCE PROJECT HEALTH Georg John Peter Link
    University of Nebraska at Omaha DigitalCommons@UNO Information Systems and Quantitative Analysis Department of Information Systems and Theses, Dissertations, and Student Creative Activity Quantitative Analysis 5-2019 COOPERATIVE SIGNALING BEHAVIOR: SIGNALS FOR OPEN SOURCE PROJECT HEALTH Georg John Peter Link Follow this and additional works at: https://digitalcommons.unomaha.edu/isqastudent Part of the Computer Sciences Commons COOPERATIVE SIGNALING BEHAVIOR: SIGNALS FOR OPEN SOURCE PROJECT HEALTH By Georg John Peter Link A DISSERTATION Presented to the Faculty of The Graduate College at the University of Nebraska In Partial Fulfillment of Requirements For the Degree of Doctor of Philosophy Major: Information Technology Under the Supervision of Dr. Matt Germonprez Nebraska, Omaha May 2019 Supervisory Committee: Matt Germonprez Robin Gandhi Brian Dorn Paige Toller COOPERATIVE SIGNALING BEHAVIOR: SIGNALS FOR OPEN SOURCE PROJECT HEALTH Georg John Peter Link, Ph.D. University of Nebraska at Omaha, 2019 Advisor: Matt Germonprez The core contribution is a critique of signaling theory from investigating cooperative signaling behavior in the context of organizational engagement with open source projects. Open source projects display signals of project health which are used by organizations. Projects and organizations engage in cooperative signaling behavior when they work together to create signals. Signaling theory is critiqued in the cooperative context of organizational engagements with open source projects by describing how cooperative signaling behavior occurs in three processes: identifying, evaluating, and filtering new signals. The contribution is informed through engaged field research and interviews, which are presented as a thick description of the CHAOSS Diversity & Inclusion Working Group and of how its community members create D&I signals.
    [Show full text]
  • Who Will Pay the Piper for Open Source Software Maintenance? Can We Increase Reliability As We Increase Reliance?
    COLUMNS Who Will Pay the Piper for Open Source Software Maintenance? Can We Increase Reliability as We Increase Reliance? DAN GEER AND GEORGE P. SIENIAWSKI Dan Geer is the CISO for In-Q- “A little neglect may breed mischief ... Tel and a security researcher for want of a nail, the shoe was lost; with a quantitative bent. He has for want of a shoe, the horse was lost; a long history with the USENIX and for want of a horse, the rider was lost.” Association, including officer —Benjamin Franklin, Poor Richard’s Almanac (1758) positions, program committees, etc. [email protected] s software eats the world and open source eats software, IT supply chains and enterprise risk management postures are evolving. Top- George P. Sieniawski is a tech- down, CIO-led commercial software procurement is shifting towards nologist at In-Q-Tel Labs, which A bottom-up, developer-driven choices that increasingly involve open source develops open source tools and data sets that address challenges software (OSS) [1]. Security in this context requires visibility, starting with at the intersection of national a comprehensive inventory (software bill of materials) as well as an under- security, the public interest, and the private sec- standing of code provenance (software composition analysis). It also entails tor. He specializes in data visualization research application testing, automated vulnerability scanning, instrumentation, and and prototype development for a wide variety of observability, which can provide insights for defenders. For organizations use cases. [email protected] that plan over longer time horizons, however, mitigating OSS risk sometimes means taking on direct responsibility for software maintenance.
    [Show full text]