Understanding Code Forking in Open Source Software

Total Page:16

File Type:pdf, Size:1020Kb

Understanding Code Forking in Open Source Software EKONOMI OCH SAMHÄLLE ECONOMICS AND SOCIETY LINUS NYMAN – UNDERSTANDING CODE FORKING IN OPEN SOURCE SOFTWARE SOURCE OPEN IN FORKING CODE UNDERSTANDING – NYMAN LINUS UNDERSTANDING CODE FORKING IN OPEN SOURCE SOFTWARE AN EXAMINATION OF CODE FORKING, ITS EFFECT ON OPEN SOURCE SOFTWARE, AND HOW IT IS VIEWED AND PRACTICED BY DEVELOPERS LINUS NYMAN Ekonomi och samhälle Economics and Society Skrifter utgivna vid Svenska handelshögskolan Publications of the Hanken School of Economics Nr 287 Linus Nyman Understanding Code Forking in Open Source Software An examination of code forking, its effect on open source software, and how it is viewed and practiced by developers Helsinki 2015 < Understanding Code Forking in Open Source Software: An examination of code forking, its effect on open source software, and how it is viewed and practiced by developers Key words: Code forking, fork, open source software, free software © Hanken School of Economics & Linus Nyman, 2015 Linus Nyman Hanken School of Economics Information Systems Science, Department of Management and Organisation P.O.Box 479, 00101 Helsinki, Finland Hanken School of Economics ISBN 978-952-232-274-6 (printed) ISBN 978-952-232-275-3 (PDF) ISSN-L 0424-7256 ISSN 0424-7256 (printed) ISSN 2242-699X (PDF) Edita Prima Ltd, Helsinki 2015 i ACKNOWLEDGEMENTS There are many people who either helped make this book possible, or at the very least much more enjoyable to write. Firstly I would like to thank my pre-examiners Imed Hammouda and Björn Lundell for their insightful suggestions and remarks. Furthermore, I am grateful to Imed for also serving as my opponent. I would also like to express my sincere gratitude to Liikesivistysrahasto, the Hanken Foundation, the Wallenberg Foundation, and the Finnish Unix User Group. They gave me the financial freedom to spend years scratching my stubble while pondering a truly fascinating topic. The time spent at work was made enjoyable by a great bunch of people. First off, many thanks to Catarina and Sofia for their excellent company during our shared first year of PhD coursework and confusion. We were fortunate to catch the tail end of the “Third Floor”, a marvelous group of people one could not but enjoy spending time with – yes, I’m looking at you Jennie, Sanne, Hertta, Markus, and Matte. (The Third Floor is dead, long live the Third Floor!) I was a wanna-be geek hoping to go native during the course of writing about computer-related stuff. It was Mikael who helped me take step after faltering step toward geekdom. Our countless hours in the Nerd Cave discussing Humble Bundles and daily deals on Steam, assembling a new computer (or, as my wife usually put it, “another new computer?”), or debating the correct coleslaw moisture ratio made even the mundane enjoyable. Many thanks also go to the rest of the department, past and present, the so-called FLOsters: Pekka, Dmitri, Eric, Mikko, Olga, Jonnu, Fille, Wille, Inkku, Patrik, Mats, Martin von W. and Martin F., Jan(ne), Sari, Tom, Henrika, Kari, Paulina, and all of the others. Last but not least, Chris deserves thanks, not just for being who he is, but also for making me appear to be considerably more eloquent than I ever will be. My aversion to getting a real job deserves only part of the credit for inspiring me to write a dissertation. The majority of the credit goes to Saku Mantere, who supervised me through the writing of my Master’s thesis, and encouraged me to take on something more challenging. Further thanks are owed to Saku and Eero Vaara for serving as my supervisors for the first year of my dissertation. A big debt of gratitude is owed to both Bo-Christer Björk (aka Bobi) and Turid Hedlund, who took me in at the Information Systems Science department once it became clear that my interests were driving the book in that direction. Bobi and Juho Lindman served as my supervisors, granting me my request to freely stumble around in a little-researched field until I smacked my head into something interesting. I am grateful to both of them for offering the perfect mix of freedom, guidance, and feedback. Further thanks go to Juho for being an insightful and knowledgeable co-author. I owe a great debt of gratitude to the many researchers and industry professionals who helped with ideas and feedback along the way. In addition to co-authoring one of the papers of this dissertation, Tommi Mikkonen offered help and guidance whenever needed, even back when I had only a vague notion of what I was doing. Tommi and the other open source researchers at the Tampere University of Technology, most notably Imed and Terhi, always made me feel like part of the gang. Walt Scacchi deserves a special mention for sharing his insights in general, but also in particular for suggesting that I look into the history of the term fork. Susanna Taimitarha was my go-to stats wizard, and I could imagine no one more pleasant or knowledgeable. ii Few things are as valuable to the confused PhD student as an expert willing to answer emails. I thank Glyn Moody, Jesper Nevalainen, and Heather Meeker for being such experts. Few things are as valuable to the procrastination-prone PhD student as a journal editor who spurs article submissions beyond even what was promised. I thank Chris McPhee for being such an editor. This book would have amounted to little more than dubious speculation, were it not for the many programmers and open source experts who shared their views and insights with me over the years. In addition to those already mentioned, I am very grateful to Lars Wirzenius, Artem Goutsoul, Niklas von Hertzen, Stefano Campadello, Patrik Welling, Jukka Z., Kalle H., Pekka B., Rasmus J., and the many other programmers who shared so freely of their time. Thanks also go to Olivier (“Olli”) Beutels for being both knowledgeable and approachable, and to Camilla Z. and Ralf W. for sharing their experiences, opinions, and insights. Monty Widenius offered so generously of his time and insights, it requires a special mention. From the multiple interviews included in this book, to the later co-authored papers on the inner workings of open source, this dissertation benefitted immensely from both his knowledge and his willingness to share his stories and views. I would also like to thank Monty’s assistant Andrea for all her help in making things happen. Tracking the history of the term fork, both in finding its way into the English language as well as into computing, was only possible due to the help of many people, all deserving of thanks. For sharing freely of their time and recollections of years past, as well as for their help in attempting to track down the original source code from Project Genie, my humble thanks go to: L Peter Deutsch, Butler Lampson, Ken Thompson, Melvin Conway, Jack Dennis, Jerry Saltzer, Tom van Vleck, Brian Randell, Wayne Lichtenberger, and Dag Spicer. Mark Riley and Elizabeth Tucker are to thank for sharing their knowledge of the early history of the term fork, and Anton Granvik has my eternal gratitude both for helping dig up obscure Latin references as well as for his oversight of my lackluster knowledge of Portuguese. While on the topic of uncovering and understanding yesteryear, Steve Russell and Peter Samson both deserve and have my thanks for shedding light on the early days of Spacewar!, and Reino Kurki-Suonio likewise for sharing his insights and stories about the history of computing in Finland. If it is indeed true that one can judge a man by the company he keeps then I owe an enormous debt of gratitude to my friends outside of academia for their continued bad judgment. Petteri, Anssi, Arno, Stefu, Markku & Hajam (the PhD slippers have been in regular use!) and the rest – thanks for all the great times! Thanks also go to my wife’s many wonderful friends (as well as wife’s-friend’s-brother: I’m looking at you, Andu). I have had the delightful marital duty of every so often spending time with Kata & Osku, Minna & Tomas, and Ann-Sofie & Bertrand (some of whom I already knew, most of whom I did not), and now consider them my friends as well. For their pleasant company, pre-opening Coffee Club, and inventing of the Humanoid, I am grateful to Mika, Ansku (aka Anastasia), and the rest of the staff, past and present, at Shaker. Heartfelt thanks go to my mother and father, Kate and Ebbe, for their support, encouragement, and especially their babysitting services! Thanks also to my godfather Konschin, who accepted the role of Bullshit Bingo Detector, tasked with keeping fashionable nonsense out of my dissertation. And to my mother-in-law Kisa and father- iii in-law Georg, for being not only great grandparents, but also great babysitting grandparents! Finally, immeasurable thanks go to my wife Yrsa, and my two wonderful sons Sebastian and Benjamin, both born during the writing of this book. Completing my PhD before they learned to say, “Daddy, are you still working on your dissertation?” served as a constant source of panicked encouragement. One of the defining characteristics of the Finnish male is his inability to express emotions like love and gratitude when sober. Another defining characteristic is his inability to stop expressing them when intoxicated. Were I to have written these acknowledgements while considerably less sober, I would have said something to the effect of: “Without you, there would be nothing. Somewhere beneath the thick layers of cynical skepticism that I define myself by, there is an unquenchable warm and cuddly glow that exists because you all are part of my life.” Helsinki, 9.1.2015 Linus Nyman iv CONTENTS 1 INTRODUCTION......................................................................................
Recommended publications
  • Chapter 12 Calc Macros Automating Repetitive Tasks Copyright
    Calc Guide Chapter 12 Calc Macros Automating repetitive tasks Copyright This document is Copyright © 2019 by the LibreOffice Documentation Team. Contributors are listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (http://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (http://creativecommons.org/licenses/by/4.0/), version 4.0 or later. All trademarks within this guide belong to their legitimate owners. Contributors This book is adapted and updated from the LibreOffice 4.1 Calc Guide. To this edition Steve Fanning Jean Hollis Weber To previous editions Andrew Pitonyak Barbara Duprey Jean Hollis Weber Simon Brydon Feedback Please direct any comments or suggestions about this document to the Documentation Team’s mailing list: [email protected]. Note Everything you send to a mailing list, including your email address and any other personal information that is written in the message, is publicly archived and cannot be deleted. Publication date and software version Published December 2019. Based on LibreOffice 6.2. Using LibreOffice on macOS Some keystrokes and menu items are different on macOS from those used in Windows and Linux. The table below gives some common substitutions for the instructions in this chapter. For a more detailed list, see the application Help. Windows or Linux macOS equivalent Effect Tools > Options menu LibreOffice > Preferences Access setup options Right-click Control + click or right-click
    [Show full text]
  • Building Online Content and Community with Drupal
    Collaborative Librarianship Volume 1 Issue 4 Article 10 2009 Building Online Content and Community with Drupal Gabrielle Wiersma University of Colorado at Boulder, [email protected] Follow this and additional works at: https://digitalcommons.du.edu/collaborativelibrarianship Part of the Collection Development and Management Commons Recommended Citation Wiersma, Gabrielle (2009) "Building Online Content and Community with Drupal," Collaborative Librarianship: Vol. 1 : Iss. 4 , Article 10. DOI: https://doi.org/10.29087/2009.1.4.10 Available at: https://digitalcommons.du.edu/collaborativelibrarianship/vol1/iss4/10 This Review is brought to you for free and open access by Digital Commons @ DU. It has been accepted for inclusion in Collaborative Librarianship by an authorized editor of Digital Commons @ DU. For more information, please contact [email protected],[email protected]. Wiersma: Building Online Content and Community with Drupal Building Online Content and Community with Drupal Gabrielle Wiersma ([email protected]) Engineering Research and Instruction Librarian, University of Colorado at Boulder Libraries use content management systems Additionally, all users are allowed to post in order to create, manage, edit, and publish content without using code, which enables content on the Web more efficiently. Drupal less tech savvy users to contribute content (drupal.org), one such Web-based content just as easily as their more proficient coun- management system, is unique because it terparts. For example, a library could use employs a bottom-up strategy for Web de- Drupal to allow library staff to view and sign that separates the content of the site edit the library Web site, blog, and staff from the formatting which means that “you intranet.
    [Show full text]
  • The Document Foundation and Libreoffice Presentation
    Liberating Open Office development Or – How we will fix your office suite Michael Meeks [email protected] “Stand at the crossroads and look; ask for the ancient paths, ask where the good way is, and walk in it, and you will find rest for your souls...” - Jeremiah 6:16 1 Overview & disclaimer ... I am not speaking for the Document Foundation These views are mine, but you're welcome to borrow them. LibreOffice is better, and fun too How is it going ? What are we doing ? Progress so far Release process Check the license applies to everyone LibreOffice appreciates your help and/or ways to get involved Conclusions 2 What / Why of LibreOffice 3 4 5 What is LibreOffice / The Document Foundation Finally “doing it right” vendor neutral, no code ownership aggregation a real Free Software / hackers project Volunteers + RedHat + Novell + Debian + Canonical + Google … FSF + OSI support, boycott + Novell support etc. Freedesktop hosting LGPLv3+ / MPL for new code ... An idea – whose time has finally come … a beautiful, Office suite we can be proud of (in due course) backed by a real, open community Shipping now on Windows, Mac, GNU / Linux, *BSD etc. ODF enables trivial migration with your data ... 6 11 months in: how is it going ? - extremely well 205+ entirely new code contributors with included patches 200+ active translators, for ~100 languages (in Pootle) Two stable branches: 3.3.3 and 3.4.2 – 7 stable releases in 10 months Development continues apace: 3.5.0 due early Feb 2012 140 120 Tata C.S. SUSE 100 s r SIL o t Redhat u b Oracle i 80
    [Show full text]
  • Designing a Licence for Open Collaboration: Andrew Katz
    Designing a Licence for Open Collaboration: insights from the development and use of the CERN Open Hardware Licence Andrew Katz University of Skövde, Moorcrofts LLP www.moorcrofts.com [email protected] Javier Serrano CERN OHL History • March 2011: CERN OHL 1.0 • July 2011: CERN OHL 1.1 • September 2013: CERN OHL 1.2 • 2017: CERN OHL 2, beta 1 • 2019 : CERN OHL 2, beta 2 • Original drafting team: Myriam Ayass and Javier Serrano and the CERN Knowledge Transfer Group. • AK became involved in 2012 with v1.2 Accelerators Detectors Dissemination How to interpret one’s dissemination mandate in the 21st century How to interpret one’s dissemination mandate in the 21st century • Standard Ethernet network • Ethernet features (VLAN) & protocols (SNMP) • Sub-nanosecond synchronisation • Guaranteed (by design) upper bound in frame latency White Rabbit Switch • Central element of White Rabbit network • 18 port gigabit Ethernet switch with WR features • Optical transceivers: single-mode fibre, originally 10 km range • Fully open design, commercially available WR Node: SPEC board FMC-based Hardware Kit: • All carrier cards are equipped with a White Rabbit port. • Mezzanines can use the accurate clock signal and “TAI” (synchronous sampling clock, trigger time tag, . ). White Rabbit application examples • CERN and GSI (Germany) near Darmstadt White Rabbit application examples • CERN and GSI • The Large High Altitude Air Shower Observatory White Rabbit application examples • CERN and GSI • The Large High Altitude Air Shower Observatory • KM3NET:
    [Show full text]
  • FOSS Philosophy 6 the FOSS Development Method 7
    1 Published by the United Nations Development Programme’s Asia-Pacific Development Information Programme (UNDP-APDIP) Kuala Lumpur, Malaysia www.apdip.net Email: [email protected] © UNDP-APDIP 2004 The material in this book may be reproduced, republished and incorporated into further works provided acknowledgement is given to UNDP-APDIP. For full details on the license governing this publication, please see the relevant Annex. ISBN: 983-3094-00-7 Design, layout and cover illustrations by: Rezonanze www.rezonanze.com PREFACE 6 INTRODUCTION 6 What is Free/Open Source Software? 6 The FOSS philosophy 6 The FOSS development method 7 What is the history of FOSS? 8 A Brief History of Free/Open Source Software Movement 8 WHY FOSS? 10 Is FOSS free? 10 How large are the savings from FOSS? 10 Direct Cost Savings - An Example 11 What are the benefits of using FOSS? 12 Security 13 Reliability/Stability 14 Open standards and vendor independence 14 Reduced reliance on imports 15 Developing local software capacity 15 Piracy, IPR, and the WTO 16 Localization 16 What are the shortcomings of FOSS? 17 Lack of business applications 17 Interoperability with proprietary systems 17 Documentation and “polish” 18 FOSS SUCCESS STORIES 19 What are governments doing with FOSS? 19 Europe 19 Americas 20 Brazil 21 Asia Pacific 22 Other Regions 24 What are some successful FOSS projects? 25 BIND (DNS Server) 25 Apache (Web Server) 25 Sendmail (Email Server) 25 OpenSSH (Secure Network Administration Tool) 26 Open Office (Office Productivity Suite) 26 LINUX 27 What is Linux?
    [Show full text]
  • Third-Party Licenses Ezeep
    Licensing Terms of Additional Components Supplied by Third- Party Manufacturers “ezeep for Azure” ................................................................................................................................1 “ezeep Connector / ezeep Connector PS” ...........................................................................................1 “ezeep Connector Mac” .......................................................................................................................4 “ezeep print App macOS” ....................................................................................................................4 “ezeep for Azure” “ezeep Connector / ezeep Connector PS” “Microsoft Visual C++ 2013 Runtime Libraries”, “Microsoft Visual C++ 2017 Runtime Libraries” Appendix 1 Microsoft Visual C++ 2013 Runtime Libraries MICROSOFT SOFTWARE LICENSE TERMS MICROSOFT VISUAL C++ REDISTRIBUTABLE FOR VISUAL STUDIO 2013 These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its affiliates) and you. Please read them. They apply to the software named above, which includes the media on which you received it, if any. The terms also apply to any Microsoft updates, supplements, Internet-based services, and support services for this software, unless other terms accompany those items. If so, those terms apply. BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THEM, DO NOT USE THE SOFTWARE. IF YOU COMPLY WITH THESE LICENSE TERMS, YOU HAVE THE PERPETUAL RIGHTS BELOW. 1. INSTALLATION AND USE RIGHTS. You may install and use any number of copies of the software on your devices. 2. SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you may use the soft- ware only as expressly permitted in this agreement. In doing so, you must comply with any technical limitations in the soft- ware that only allow you to use it in certain ways.
    [Show full text]
  • Pfc6168.Pdf (438.8Kb)
    ESCUELA TÉCNICA SUPERIOR DE INGENIERÍA DE TELECOMUNICACIÓN UNIVERSIDAD POLITÉCNICA DE CARTAGENA Proyecto Fin de Carrera TÍTULO: Iphone Bookshelf AUTOR: David Zamora Gutiérrez DIRECTOR: Francesc Burrull i Mestres Febrero / 2015 INDEX IPhone application………………………………………………………………... o Tools……………………………………………………………………… . Iphone…………………………………………………………….. Objective-C……………………………………………………….. o Code………………………………………………………………………. Web site…………………………………………………………………………... o Tools……………………………………………………………………… . Codeigniter……………………………………………………….. Php………………………………………………………………... Http……………………………………………………………….. Html………………………………………………………………. Mysql……………………………………………………………... Apache……………………………………………………………. CSS……………………………………………………………….. E-books…………………………………………………………… o Code………………………………………………………………………. References……………………………………………………………………....... IPHONE APPLICATION TOOLS IPHONE The iPhone is a line of Internet- and multimedia-enabled smartphones designed and marketed by Apple Inc. The first iPhone was unveiled by Apple CEO Steve Jobs on January 9, 2007, and released on June 29, 2007. An iPhone can function as a video camera (video recording was not a standard feature until the iPhone 3GS was released), a camera phone, can send texts and receive visual voicemail, a portable media player, and an Internet client with email and web browsing capabilities, and both Wi-Fi and 3G connectivity. The user interface is built around the device's multi-touch screen, including a virtual keyboard rather than a physical one. Third-party as well as Apple application software is available from the App Store, which launched in mid-2008 and now has over 350,000 "apps" approved by Apple. These apps have diverse functionalities, including games, reference, GPS navigation, social networking, e-books... To create applications for this device it’s use the APPLE SDK. APPLE SDK The SDK basically consists of a set of tools that Apple provides to build, debug and test our developments. It contains the following programs: - XCODE: Xcode is a suite of tools, developed by Apple, for developing software for Mac OS X and iOS.
    [Show full text]
  • Master Thesis Innovation Dynamics in Open Source Software
    Master thesis Innovation dynamics in open source software Author: Name: Remco Bloemen Student number: 0109150 Email: [email protected] Telephone: +316 11 88 66 71 Supervisors and advisors: Name: prof. dr. Stefan Kuhlmann Email: [email protected] Telephone: +31 53 489 3353 Office: Ravelijn RA 4410 (STEPS) Name: dr. Chintan Amrit Email: [email protected] Telephone: +31 53 489 4064 Office: Ravelijn RA 3410 (IEBIS) Name: dr. Gonzalo Ord´o~nez{Matamoros Email: [email protected] Telephone: +31 53 489 3348 Office: Ravelijn RA 4333 (STEPS) 1 Abstract Open source software development is a major driver of software innovation, yet it has thus far received little attention from innovation research. One of the reasons is that conventional methods such as survey based studies or patent co-citation analysis do not work in the open source communities. In this thesis it will be shown that open source development is very accessible to study, due to its open nature, but it requires special tools. In particular, this thesis introduces the method of dependency graph analysis to study open source software devel- opment on the grandest scale. A proof of concept application of this method is done and has delivered many significant and interesting results. Contents 1 Open source software 6 1.1 The open source licenses . 8 1.2 Commercial involvement in open source . 9 1.3 Opens source development . 10 1.4 The intellectual property debates . 12 1.4.1 The software patent debate . 13 1.4.2 The open source blind spot . 15 1.5 Litterature search on network analysis in software development .
    [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]
  • The Document Foundation and Libreoffice Presentation Template
    The wonderful world of: Or – How we will fix your office suite Michael Meeks [email protected] “Stand at the crossroads and look; ask for the ancient paths, ask where the good way is, and walk in it, and you will find rest for your souls...” - Jeremiah 6:16 1 Overview & disclaimer ... I am not speaking for the Document Foundation These views are mine, but you're welcome to borrow them. LibreOffice is better, and fun too How is it going ? What are we doing ? Progress so far Check the license applies to everyone More general legal interest LibreOffice appreciates your help and/or ways to get involved Conclusions 2 What / Why of LibreOffice 3 What is LibreOffice / The Document Foundation Finally “doing it right” vendor neutral, no code ownership aggregation a real Free Software / hackers project Volunteers + RedHat + Novell + Debian + Canonical + Google … FSF + OSI support, boycott + Novell support etc. Freedesktop hosting LGPLv3+ / MPL for new code ... An idea – whose time has finally come … a beautiful, Office suite we can be proud of (in due course) backed by a real, open community Shipping now on Windows, Mac, GNU / Linux, *BSD etc. ODF enables trivial migration with your data ... 4 Why now ? Is it all Oracle's fault ? ten years after the promise of a foundation … “a foundation is a great idea … the time is not yet ripe … perhaps in another three years” etc. etc. Patience – a virtue, but not an inexhaustible resource. some truly fantastic 'opportunities' for improvement Vendor neutrality / no copyright assignment barrier ~unrelated to Oracle – StarDivision have real autonomy please don't hate them, they have hard problems the 'community' has '~failed' them for many years we have great friends & hackers there motivated by a love of freedom, not by hatred.
    [Show full text]
  • What Is Pcmark 8?
    Technical Guide Updated December 16, 2020 ⚠ Support for PCMark 8 will end on January 14, 2021. What is PCMark 8? .......................................................................................................... 4 Latest version numbers ................................................................................................... 6 System requirements ....................................................................................................... 7 Benchmark accuracy ........................................................................................................ 8 How to benchmark performance ................................................................................... 9 How to benchmark battery life ..................................................................................... 10 PCMark 8 settings ........................................................................................................... 12 Home benchmark ......................................................................................................... 14 Home benchmark version history ................................................................................ 15 Creative benchmark ..................................................................................................... 16 Creative benchmark version history ............................................................................ 17 Work benchmark .........................................................................................................
    [Show full text]
  • Open Source Software As Intangible Capital: Measuring the Cost and Impact of Free Digital Tools Preliminary Draft October 31, 20181 Carol A
    Open Source Software as Intangible Capital: Measuring the Cost and Impact of Free Digital Tools Preliminary Draft October 31, 20181 Carol A. Robbins*(1), Gizem Korkmaz (2), José Bayoán Santiago Calderón (3), Daniel Chen (2), Claire Kelling (4) , Stephanie Shipp (2), Sallie Keller (2) Abstract Open source software is everywhere, both as specialized applications nurtured by devoted user communities, and as digital infrastructure underlying platforms used by millions daily, yet its value and impact are not currently measured (with small exceptions). We develop an approach to document the scope and impact of open source software created by all sectors of the economy: businesses, universities, government research institutions, nonprofits, and individuals. We use a bottom-up approach to measure subset of OSS projects and languages, collecting data on open source software languages R, Python, Julia, and JavaScript, as well as from the Federal Government’s code.gov website. Using lines of code and a standard model to estimate package developer time, we convert lines of code to resource cost. We estimate that the resource cost for developing R, Python, Julia, and JavaScript exceeds $3 billion dollars, based on 2017 costs. Applying this approach to open source software available on code.gov results in an estimated value of more than $1 billion, based on 2017 costs, as a lower bound for the resource cost of this software. We analyze the dependencies between software packages through network analysis and estimate re-use statistics. This reuse is one measure of relative impact. Key words: Open Source Software, Intangibles, Network Analysis National Center for Science and Engineering Statistics, National Science Foundation; 2) Social & Decision Analytics Division, Biocomplexity Institute & Initiative, University of Virginia; 3) Claremont Graduate University; 4) Pennsylvania State University 1 An earlier version of this paper was presented August 21, 2018 at the International Association for Research on Income and Wealth.
    [Show full text]