DOCSLIB.ORG

Adopting Innersource

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Adopting Innersource Compliments of Adopting InnerSource Principles and Case Studies Danese Cooper & Klaas-Jan Stol with foreword by Tim O’Reilly Adopting InnerSource Principles and Case Studies Danese Cooper and Klaas-Jan Stol Beijing Boston Farnham Sebastopol Tokyo Adopting InnerSource by Danese Cooper and Klaas-Jan Stol Copyright © 2018 O’Reilly Media. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online edi‐ tions are also available for most titles (http://oreilly.com/safari). For more information, contact our corporate/institutional sales department: 800-998-9938 or [email protected]. Editor: Andy Oram Proofreader: Jasmine Kwityn Production Editor: Justin Billing Interior Designer: David Futato Copyeditor: Octal Publishing, Inc. and Charles Cover Designer: Karen Montgomery Roumeliotis Illustrator: Melanie Yarbrough July 2018: First Edition Revision History for the First Edition 2018-06-15: First Release The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. Adopting InnerSource, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. The views expressed in this work are those of the authors, and do not represent the publisher’s views. While the publisher and the authors have used good faith efforts to ensure that the informa‐ tion and instructions contained in this work are accurate, the publisher and the authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own risk. If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with such licenses and/or rights. This work is part of a collaboration between O’Reilly and PayPal. See our statement of editorial inde‐ pendence. 978-1-492-04183-2 [LSI] Table of Contents Foreword. vii 1. The InnerSource Approach to Innovation and Software Development. 1 Old Patterns of Development: Closed and Slow 1 Factors Driving Open Source 4 Proprietary Hierarchies 4 The Open Source Way 6 What Is InnerSource? 9 Why Do Companies Adopt InnerSource? 12 InnerSource Today 15 Why We Wrote This Book 16 Who Should Read This Book 17 How This Book Is Organized 18 2. The Apache Way and InnerSource. 21 Origins of The Apache Way 21 Fundamentals of The Apache Way 22 3. From Corporate Open Source to InnerSource: A Serendipitous Journey at Bell Laboratories. 29 Background on Internet Protocols for Voice Communication 30 SIP: A Brief Background 32 The Project: The Common SIP Stack (CSS) 34 Reflections, Insights, and Discussion 42 Acknowledgments 45 4. Living in a BIOSphere at Robert Bosch. 47 Why InnerSource 48 Starting the BIOS Journey 48 iii Establishing and Growing the BIOSphere 49 From BIOS to Social Coding 53 Success Stories 55 Success Factors 57 Challenges 59 Lessons Learned 60 Conclusion 62 Acknowledgments 62 5. Checking Out InnerSource at PayPal. 63 A Little Background 64 Attributes of InnerSource 64 The CheckOut Experiment 69 The Onboarding Experiment 71 Executive Air Cover 72 Meanwhile, in India 73 Beginning Symphony and InnerSource Brand Dilution 74 Initial Symphony Training 75 The Contributing.md File 77 Cadence of Check-Ins 78 Outcomes 80 The Rhythm of InnerSource Work 82 The Future of InnerSource at PayPal 83 Acknowledgments 86 6. Borrowing Open Source Practices at Europace. 87 Looking for New Ways of Organizing 88 Starting the Journey Toward InnerSource 89 Steps Toward InnerSource 93 InnerSource Principles 96 InnerSource Challenges 99 Conclusion and Future Outlook 101 Acknowledgments 102 7. Connecting Teams with InnerSource at Ericsson. 103 The Changing Telecommunications Landscape 103 Why InnerSource? 105 Starting the Community Developed Software Program 106 Selecting Components and Development Models 109 Making Collaborations Happen 112 Pillars of Community-Developed Software 113 Success: The User Interface SDK Framework 115 Lessons Learned 115 iv | Table of Contents The Future of InnerSource at Ericsson 117 Acknowledgments 117 8. Adopting InnerSource. 119 Comparison of the Case Studies 120 Guidelines for Adopting InnerSource 129 The InnerSource Commons 137 9. Epilogue. 139 Glossary. 141 Table of Contents | v Foreword Tim O’Reilly I’m told that I coined the term “InnerSource” in 2000, and sure enough there’s a blog post to prove it. I don’t remember writing it. What I do remember is an ear‐ lier conversation, in the summer or fall of 1998, not long after the so-called Open Source Summit in April of that year, to talk to an IBM team that was thinking of embracing this new movement. They were cautious. How might it affect IBM’s business? How would they con‐ tinue to own, control, and profit from their software? What kind of license might they use to get the benefit of user contribution but still manage and control their creations? The GNU Public License seemed hostile to business; the Berkeley Unix and MIT X Window System licenses were permissive but perhaps gave too much freedom. The just-released Mozilla Public License tried to find a new bal‐ ance between the needs of a corporate owner and a community of developers. Should they use that or develop their own license? I was never a big fan of the idea that licenses defined what was most important about free and Open Source software. I’d begun my career in computing in the heady days of the Berkeley Software Distribution of Unix, BSD 4.1, and AT&T’s Version 7. I had seen how Unix, based on the original architecture developed by Ken Thompson and Dennis Ritchie at Bell Labs, could attract a wide range of outside contributions from university computer science researchers despite being owned by AT&T. Many of the features that made the system most valuable had been developed at UC Berkeley and other universities. It was the architecture of Unix, not its license, that allowed these contributions to be treated as first-class components of the system. The system defined a protocol, so to speak, for the cooperation between programs, a design by which anyone could bring a new program to the party, and it just worked, as long as it followed that protocol. I’d then watched as the Internet and its killer application, the World Wide Web, had followed the same model, defining itself not by license but by the rules of interoperability and cooperation. I loved Linux, but it seemed a kind of blindness vii in Open Source advocates to focus so much on it. Open Source was the native development methodology of the internet, and the internet was its greatest suc‐ cess story. Network-centric architectures require interoperability and loose cou‐ pling. And the Internet allowed distributed development communities to evolve, and shifted power from corporations to individuals. I’d also been steeped in the culture of the Perl programming language, the idea that “there’s more than one way to do it,” and the sprawling extensibility of CPAN, the Comprehensive Perl Archive Network, which allowed programmers to share modules they’d built on top of Perl without ever touching the source code of the language interpreter itself. So I was convinced that much of the magic of Open Source was independent of the license. The things to think about were collaboration, community, and low barriers to entry for those who wanted to share with each other. And so I told Dan Frye, Pierre Fricke, and the other attendees at that IBM meeting, that yes, they could and should release software under Open Source licenses, but if they weren’t ready to do so, there was no reason that they couldn’t take advantage of these other elements. Given a large enough pool of customers using the same software, I told them, there was no reason they couldn’t create a “Gated Open Source Community.” For that matter, given a large enough pool of developers inside a company, there was no reason, I told them, why they couldn’t apply many of the principles and practices of Open Source within their own walls. That was what later came to be called InnerSourcing. I defined it at the time as as “helping [companies] to use Open Source development techniques within the corporation, or with a cluster of key customers—even if they aren’t ready to take the step all the way to releasing their software as a public Open Source project.” Not long afterwards, I heard the first stories of InnerSourcing in the wild. And as is so often the case, they weren’t planned. In 1998 or 1999, two Microsoft devel‐ opers, Scott Guthrie and Mark Anders, wanted to create a tool that would make it easier to build data-backed websites. They built a project on their own time over the Christmas holidays; other Microsoft developers heard about their work and adopted it, and eventually word reached Bill Gates. When the CEO called the two into his office, they didn’t know what to expect. In the end, their project became one of Microsoft’s flagship software offerings, ASP.NET. Twenty years later, Scott Guthrie heads all software development at Microsoft, and what was once a rene‐ gade InnerSource project is now a major part of Microsoft’s software strategy. Eric Raymond, the author of The Cathedral and The Bazaar, and one of the first theorists of the Open Source movement, once coined what he called Linus’ Law, “Given enough eyeballs, all bugs are shallow.” I propose a corollary, which we might call Scott’s Law, or The Law of Innersourcing: “Given enough connected viii | Foreword developers, all software development emulates the best practices of Open Source software.” Foreword | ix CHAPTER 1 The InnerSource Approach to Innovation and Software Development With Andy Oram InnerSource is a software development strategy rapidly spreading throughout large corporations—and it is also more.
Load more

Recommended publications
  • L'exemple De Wikipédia Laure Endrizzi Chargée D'études Et De Recherche, Cellule Veille Scientifique Et Technologique, INRP, Lyon
    La communauté comme auteur et éditeur : l’exemple de Wikipédia Laure Endrizzi To cite this version: Laure Endrizzi. La communauté comme auteur et éditeur : l’exemple de Wikipédia. Journée nationale du réseau des URFIST : Evaluation et validation de l’information sur internet, Jan 2007, Paris, France. edutice-00184888 HAL Id: edutice-00184888 https://edutice.archives-ouvertes.fr/edutice-00184888 Submitted on 2 Nov 2007 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Journée d'études des URFIST 31 janvier 2007, Paris « Evaluation et validation de l'information sur internet » La communauté comme auteur et éditeur : l'exemple de Wikipédia Laure Endrizzi chargée d'études et de recherche, cellule Veille scientifique et technologique, INRP, Lyon Résumé L’ensemble des technologies dites 2.0 place l’usager au cœur de la création des contenus numériques tout en l’inscrivant dans une dynamique collective. Ces transformations remettent en cause le modèle éditorial traditionnel, sans offrir de représentations claires et stabilisées des modes de production et de validation qui sont à l’œuvre. Avec l’exemple de Wikipédia, nous tenterons de comprendre les mécanismes de la régulation éditoriale, pour ensuite nous interroger sur les formes d’expertise sollicitées et les figures de l’auteur.
    [Show full text]
  • Are Encyclopedias Dead? Evaluating the Usefulness of a Traditional Reference Resource Rachel S
    St. Cloud State University theRepository at St. Cloud State Library Faculty Publications Library Services 2012 Are Encyclopedias Dead? Evaluating the Usefulness of a Traditional Reference Resource Rachel S. Wexelbaum St. Cloud State University, [email protected] Follow this and additional works at: https://repository.stcloudstate.edu/lrs_facpubs Part of the Library and Information Science Commons Recommended Citation Wexelbaum, Rachel S., "Are Encyclopedias Dead? Evaluating the Usefulness of a Traditional Reference Resource" (2012). Library Faculty Publications. 26. https://repository.stcloudstate.edu/lrs_facpubs/26 This Article is brought to you for free and open access by the Library Services at theRepository at St. Cloud State. It has been accepted for inclusion in Library Faculty Publications by an authorized administrator of theRepository at St. Cloud State. For more information, please contact [email protected]. Are Encyclopedias Dead? Evaluating the Usefulness of a Traditional Reference Resource Author Rachel Wexelbaum is Collection Management Librarian and Assistant Professor at Saint Cloud State University, Saint Cloud, Minnesota. Contact Details Rachel Wexelbaum Collection Management Librarian MC135D Collections Saint Cloud State University 720 4 th Avenue South Saint Cloud, MN 56301 Email: [email protected] Abstract Purpose – To examine past, current, and future usage of encyclopedias. Design/methodology/approach – Review the history of encyclopedias, their composition, and usage by focusing on select publications covering different subject areas. Findings – Due to their static nature, traditionally published encyclopedias are not always accurate, objective information resources. Intentions of editors and authors also come into question. A researcher may find more value in using encyclopedias as historical documents rather than resources for quick facts.
    [Show full text]
  • 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]
  • Íslenska Wikipedia Greining Á Þróun
    Íslenska Wikipedia Greining á þróun Hrafn H. Malmquist Lokaverkefni til MLIS–gráðu í bókasafns- og upplýsingafræði Félagsvísindasvið Íslenska Wikipedia Greining á þróun Hrafn H. Malmquist Lokaverkefni til MLIS–gráðu í bókasafns- og upplýsingafræði Leiðbeinendur: Dr. Jóhanna Gunnlaugsdóttir og Salvör K. Gissurardóttir Félags- og mannvísindadeild Félagsvísindasvið Háskóla Íslands Febrúar 2013 Ritgerð þessi er lokaverkefni til MLIS–gráðu í bókasafns- og upplýsingafræði og er óheimilt að afrita ritgerðina á nokkurn hátt nema með leyfi rétthafa. © Hrafn H. Malmquist 2013 Reykjavík, Ísland 2013 Útdráttur Markmið þessarar rannsóknar var að bera kennsl á þróun íslensku Wikipediunnar að gerð og umfangi. Notuð var blönduð aðferðafræði. Í megindlega hluta rannsóknarinnar eru dönsku og færeysku Wikipediurnar notaðar sem viðmið fyrir þá íslensku. Til þess að framkvæma rannsóknina var notast við WikiDAT-hugbúnað sem var þróaður gagngert af Dr. Felipe Ortega til þess að framkvæma slíkar greiningar. Gildi rannsóknarinnar felst m.a. í því að slík rannsókn hefur ekki verið gerð áður á þessum Wikipedium. Meðal þess sem athugað var er þróun stærðar Wikipedianna yfir tíma, uppbygging Wikipedianna, dreifing á framlögum notenda og sá tími sem notendur eru virkir á. Einnig voru tekin tölvupóstviðtöl við átta notendur íslensku Wikipediu sem voru eða höfðu verið mjög virkir notendur á tímabili. Spurt var um hvaða augum þeir litu þátttöku sína og hvers vegna þeir tækju þátt. Niðurstaðan er sú að það hægir á vexti íslensku Wikipediu, án þess að orsök þess liggi fyrir og að uppbygging Wikipedianna sé breytileg. Þá er ljóst að fámennur hópur mjög virkra notenda stendur að baki mestri vinnu á íslensku Wikipediu og að flestir nýjir notendur hætti fljótt afskiptum.
    [Show full text]
  • Complete Issue
    Culture Unbound: Journal of Current Cultural Research Thematic Section: Changing Orders of Knowledge? Encyclopedias in Transition Edited by Jutta Haider & Olof Sundin Extraction from Volume 6, 2014 Linköping University Electronic Press Culture Unbound: ISSN 2000-1525 (online) URL: http://www.cultureunbound.ep.liu.se/ © 2014 The Authors. Culture Unbound, Extraction from Volume 6, 2014 Thematic Section: Changing Orders of Knowledge? Encyclopedias in Transition Jutta Haider & Olof Sundin Introduction: Changing Orders of Knowledge? Encyclopaedias in Transition ................................ 475 Katharine Schopflin What do we Think an Encyclopaedia is? ........................................................................................... 483 Seth Rudy Knowledge and the Systematic Reader: The Past and Present of Encyclopedic Reading .............................................................................................................................................. 505 Siv Frøydis Berg & Tore Rem Knowledge for Sale: Norwegian Encyclopaedias in the Marketplace .............................................. 527 Vanessa Aliniaina Rasoamampianina Reviewing Encyclopaedia Authority .................................................................................................. 547 Ulrike Spree How readers Shape the Content of an Encyclopedia: A Case Study Comparing the German Meyers Konversationslexikon (1885-1890) with Wikipedia (2002-2013) ........................... 569 Kim Osman The Free Encyclopaedia that Anyone can Edit: The
    [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]
  • The Free Encyclopaedia That Anyone Can Edit: the Shifting Values of Wikipedia Editors
    The Free Encyclopaedia that Anyone can Edit: The Shifting Values of Wikipedia Editors By Kim Osman Abstract Wikipedia is often held up as an example of the potential of the internet to foster open, free and non-commercial collaboration. However such discourses often con- flate these values without recognising how they play out in reality in a peer- production community. As Wikipedia is evolving, it is an ideal time to examine these discourses and the tensions that exist between its initial ideals and the reality of commercial activity in the encyclopaedia. Through an analysis of three failed proposals to ban paid advocacy editing in the English language Wikipedia, this paper highlights the shift in values from the early editorial community that forked encyclopaedic content over the threat of commercialisation, to one that today val- ues the freedom that allows anyone to edit the encyclopaedia. Keywords: Wikipedia, encyclopaedias, encyclopaedism, mass collaboration, in- ternet studies, grounded theory, online community. Osman, Kim: “The Free Encyclopaedia that Anyone can Edit” Culture Unbound, Volume 6, 2014: 593–607. Hosted by Linköping University Electronic Press: http://www.cultureunbound.ep.liu.se Introduction Wikipedia is an encyclopaedia in transition. Its core values are being called into question as an increasing number of users are paid to contribute to the encyclo- paedia. How then is the open editorial community of this free encyclopaedia re- sponding to the increasing presence of commercial interests and paid editors? Through an analysis of three failed proposals by the community to impose bans or limits on paid editing, this study reveals how the values of the English language Wikipedia editorial community are in transition and how these shifts reflect wider changes in assumptions about commerciality in digital media.
    [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]