Volume 02} Issue 01}June 2010

Total Page:16

File Type:pdf, Size:1020Kb

Volume 02} Issue 01}June 2010 Volume 02} Issue 01} June 2010 Contents Articles Licence Profi le: BSD 1 Andrew Sinclair GNU GPL 2.0 and 3.0: obligations to include license text, and provide source code 7 Neil Brown Copyright in Open Source Software - Understanding the Boundaries 15 Omar Johnny, Marc Miller, Mark Webbink Package Review as a Part of Free and Open Source Software Compliance 39 Martin von Willebrand, Mikko-Pekka Partanen Case law reports Italian Constitutional Court gives way to Free-Software friendly laws 61 Carlo Piana Book reviews Butterworths e-commerce and IT Law Handbook, 5th Edition 67 Daniel Hopkin Moral Panics and the Copyright Wars 69 Andrew Katz Platform Lawyers in the Bazaar: Challenges and Opportunities for Open Source Legal 77 Communities Luis Villa Consensus-Oriented Specifi cation System 85 Pieter Hintjens Call for Papers 100 Available online at: http://www.ifosslr.org Volume 02} Issue 01} June 2010 About IFOSS L. Rev. Editorial Committee This publication is managed by a rotating Editorial Committee. Ywein Van den Brande Ywein Van den Brande (b. 1977) studied law, information science and economics The membership of the Committee for this issue is as follows: at the Catholic University of Leuven and Groep T (Leuven, Belgium), the Université de Rouen (Rouen, France) and U.C.L.A. (Los Angeles, USA). Ywein is an active Malcolm Bain member of the Free Software Foundation Europe and is a member of workgroups Malcolm is partner at id law partners, a Barcelona based law firm specialising in on information architecture and usability. Ywein is the author of several legal contri- IT law, with a focus on FOSS projects. As well as his private practice, Malcolm butions on law and technology, and regularly speaks at conferences. He is a guest participates pro bono in a number of FOSS related initiatives and teaches the legal lecturer at Groep T and blogs on the CIF blog of the journal www.tijd.be. aspects of FOSS at university. Martin von Haller Groenbaek Amanda Brock Martin von Haller Groenbaek is a founding partner at the leading Scandinavian IT Amanda Brock is General Counsel of Canonical, the commercial sponsor of the law firm, Bender von Haller Dragsted. Among other thing he specialises in open Ubuntu project. Having graduated with Honours from Glasgow University, Amanda source, open content and open data licences. He is a co-founder of the Danish went on to obtain a Masters in Comparative Jurisprudence from New York Uni- Open Source Vendors Association and of the Danish chapters of the Internet Soci- versity Law School and a LLM in IT and IP law from Queen Mary and Westfield, ety and Creative Commons. His blog is at http://www.openlife.dk . His online CV is University of London. She is author of E:Business; The Practical Guide to the Laws at http://www.linkedin.com/in/vonhaller . and has written extensively on commercial and IT law. Martin von Willebrand Richard Fontana Partner, HH Partners Attorneys-at-law; Chairman, Validos Association, Chairman, Richard Fontana is Open Source Licensing and Patent Counsel at Red Hat, Inc. Finnish IT law Association; Managing Director, Inventors Factory Association. Martin Before joining Red Hat, Fontana was Counsel at the Software Freedom Law Center. is a Finnish technology lawyer with particular specialisation in the areas of copy- Fontana is admitted to practice law in the State of New York. right, licensing and open source. He has authored and co-authored books on legal aspects of e-commerce, and has introduced collaborative models for delivering legal and other services. Michel Jaccard Michel Is a partner in the technology and corporate practice groups of BCCC Avocats, an independent business law firm in Switzerland. He studied and worked Mark Webbink in Lausanne, Geneva and New York, and taught and published extensively on legal Mark Webbink is a Visiting Professor of Law and Executive Director of the Center issues relating to software licensing, information technology / business process for Patent Innovations at New York Law School. Webbink is also a Senior Lecturing outsourcing structures, data protection and online services. He regularly advises Fellow at Duke Law School and has served as an Adjunct Professor at NCCU Law clients in Switzerland and abroad on intellectual property and technology as well as School. From 2000 to 2007 Webbink served in various capacities with Red Hat, Inc., on corporate acquisitions, disposals and collaboration. including General Counsel, Deputy General Counsel for Intellectual Property, Senior Vice President and Secretary. Webbink presently serves on the board of directors of the Software Freedom Law Center. Andrew Katz Andrew Katz studied Natural Sciences and Law at Cambridge University where he graduated with honours in 1989. In 1991 he was called to the Bar, and in 1993 requalified as a solicitor. He moonlighted as a programmer during his studies at Bar Editorial Coordinators School, programming in Turbo Pascal. He has released software under the GPL. He The editors wish to thank the Editorial Coordinators for their hard is currently a partner at Moorcrofts LLP, a boutique law firm in England’s Thames work and contribution to making the Review happen. Valley and advises a wide range of businesses on free and open source related issues. He has lectured and published widely on the subject. Graeme R. West ( [email protected] ) Graeme is a Masters student at the University of Edinburgh law school’s SCRIPT IP Iain G. Mitchell QC and technology law centre, and is a former intern at the Free Software Foundation Europe. His academic background is in political science, in particular the global Chairman, Scottish Society for Computers and Law; Chairman, Scottish Lawyers’ politics of IP. He has also worked in large-scale digital archival projects and web European Group; Chairman, Faculty of Advocates IT Group; Lecturer, Honorary application development. Board of Lecturers, Institut für Informations-, Telekommunikations- und Medienrecht, Westfälische Wilhelms-Universtät, Münster; Freeman, Worshipful Company of Information Technologists. Shane Martin Coughlan ( [email protected] ) Shane’s academic background is in linguistics and politics, and his postgraduate research focused on cybernetic warfare. He founded FSFE’s legal department Carlo Piana in 2006, established the European Legal Network in 2007, and today focuses on Independent lawyer specialising in Information Technology and Telecommunica- improving efficiency in international technology markets. tion Law and Free Software Advocate. Started by using GNU/Linux and became intrigued by the legal and philosophical implications of it. Serves as Counsel to the Free Software Foundation Europe and advises projects and companies active in Peer reviewers Free and Open Source Software. The Editorial Committee wishes to thank the work of the many referees and peer reviewers whose professional expertise and Tomasz Rychlicki dedication to high standards have made the publication of this Tomasz Rychlicki graduated from the University of Gdańsk, the Faculty of Law, Center of European Law. He also studied at Chicago-Kent College of Law in the issue possible. LL.M. Program in International Intellectual Property Law. Tomasz currently works for PATPOL, Warsaw. He is a member of the Editorial Board (Copyright, Related Rights and Designs, including sui generis database right) at the Journal of Intellectual Contact Property Law & Practice published by Oxford University Press, Oxford. All administrative, bibliographic and pre-publication enquiries Brendan Scott should be directed to the Editorial Coordinators via email at: Brendan runs a legal practice based in Sydney, Australia. Brendan is a founding [email protected] member and a director of Open Source Industry Australia Limited. He is a past president of the NSW Society for Computers and the Law and a past editor of its journal. He has over 15 years of experience in Technology and Telecommunications The Editorial Committee can be contacted via email at: law and has a special interest in open source and the law related to it. [email protected] Available online at: http://www.ifosslr.org The Black Duck Legal Webinar Series Watch live and recorded webinars covering basic and advanced topics on open source software issues. www.blackducksoftware.com/legalwebinars Visit to see a list of on-demand webinars and dates for new upcoming topics. www.blackducksoftware.com A Distinct Mission: Keeping Open Source Open Open Invention NetworkSM is a collaborative enterprise Open Invention Network (OIN) has considerable industry backing. that enables innovation in open source and an increasingly It was launched in 2005, and has received investments from IBM, vibrant ecosystem around Linux by acquiring and licensing NEC, Novell, Philips, Red Hat and Sony. patents, influencing behaviors and policy and protecting One of the key methods in which OIN promotes Linux is by acquiring the integrity of the ecosystem through strategic programs patents across a wide range of technologies. such as Linux Defenders. It enables the growth and continuation of open source software by fostering a Patents owned by OIN are available royalty-free to any company, healthy Linux ecosystem of investors, vendors, institution or individual that agrees not to assert its patents against developers and users. the Linux Community. Linux Defenders (www.linuxdefenders.org) Open Invention Network is seeking creative and energetic individuals from the Open Source Community to actively contribute to Linux Defenders. Linux Defenders offers the Linux and broader open source community a unique opportunity to harness its collaborative passion, intelligence and ingenuity to ensure Linux’s natural path of growth Research Triangle Park Center and innovation. The free program is designed to benefit open source innovation by significantly reducing 4819 Emperor Boulevard the number of poor-quality patents that might otherwise be used by patent trolls, or other organizations, Suite 400 whose behaviors and business models are in opposition to those of the open source community. Durham, NC USA 27703 T: +1 919 313 4904 The success of the program will be driven by contributions from the open source community.
Recommended publications
  • Misc Thesisdb Bythesissuperv
    Honors Theses 2006 to August 2020 These records are for reference only and should not be used for an official record or count by major or thesis advisor. Contact the Honors office for official records. Honors Year of Student Student's Honors Major Thesis Title (with link to Digital Commons where available) Thesis Supervisor Thesis Supervisor's Department Graduation Accounting for Intangible Assets: Analysis of Policy Changes and Current Matthew Cesca 2010 Accounting Biggs,Stanley Accounting Reporting Breaking the Barrier- An Examination into the Current State of Professional Rebecca Curtis 2014 Accounting Biggs,Stanley Accounting Skepticism Implementation of IFRS Worldwide: Lessons Learned and Strategies for Helen Gunn 2011 Accounting Biggs,Stanley Accounting Success Jonathan Lukianuk 2012 Accounting The Impact of Disallowing the LIFO Inventory Method Biggs,Stanley Accounting Charles Price 2019 Accounting The Impact of Blockchain Technology on the Audit Process Brown,Stephen Accounting Rebecca Harms 2013 Accounting An Examination of Rollforward Differences in Tax Reserves Dunbar,Amy Accounting An Examination of Microsoft and Hewlett Packard Tax Avoidance Strategies Anne Jensen 2013 Accounting Dunbar,Amy Accounting and Related Financial Statement Disclosures Measuring Tax Aggressiveness after FIN 48: The Effect of Multinational Status, Audrey Manning 2012 Accounting Dunbar,Amy Accounting Multinational Size, and Disclosures Chelsey Nalaboff 2015 Accounting Tax Inversions: Comparing Corporate Characteristics of Inverted Firms Dunbar,Amy Accounting Jeffrey Peterson 2018 Accounting The Tax Implications of Owning a Professional Sports Franchise Dunbar,Amy Accounting Brittany Rogan 2015 Accounting A Creative Fix: The Persistent Inversion Problem Dunbar,Amy Accounting Foreign Account Tax Compliance Act: The Most Revolutionary Piece of Tax Szwakob Alexander 2015D Accounting Dunbar,Amy Accounting Legislation Since the Introduction of the Income Tax Prasant Venimadhavan 2011 Accounting A Proposal Against Book-Tax Conformity in the U.S.
    [Show full text]
  • Release 2021-03
    Metrics Release 2021-03 https://chaoss.community/metrics MIT License Copyright © 2021 CHAOSS a Linux Foundation® Project CHAOSS Contributors include: Aastha Bist, Abhinav Bajpai, Ahmed Zerouali, Akshara P, Akshita Gupta, Amanda Brindle, Anita Ihuman, Alberto Martín, Alberto Pérez García-Plaza, Alexander Serebrenik, Alexandre Courouble, Alolita Sharma, Alvaro del Castillo, Ahmed Zerouali, Amanda Casari, Amy Marrich, Ana Jimenez Santamaria, Andre Klapper, Andrea Gallo, Andy Grunwald, Andy Leak, Aniruddha Karajgi, Anita Sarma, Ankit Lohani, Ankur Sonawane, Anna Buhman, Armstrong Foundjem, Atharva Sharma, Ben Lloyd Pearson, Benjamin Copeland, Beth Hancock, Bingwen Ma, Boris Baldassari, Bram Adams, Brian Proffitt, Camilo Velazquez Rodriguez, Carol Chen, Carter Landis, Chris Clark, Christian Cmehil- Warn, Damien Legay, Dani Gellis, Daniel German, Daniel Izquierdo Cortazar, David A. Wheeler, David Moreno, David Pose, Dawn Foster, Derek Howard, Don Marti, Drashti, Duane O’Brien, Dylan Marcy, Eleni Constantinou, Elizabeth Barron, Emily Brown, Emma Irwin, Eriol Fox, Fil Maj, Gabe Heim, Georg J.P. Link, Gil Yehuda, Harish Pillay, Harshal Mittal, Henri Yandell, Henrik Mitsch, Igor Steinmacher, Ildiko Vancsa, Jacob Green, Jaice Singer Du Mars, Jaskirat Singh, Jason Clark, Javier Luis Cánovas Izquierdo, Jeff McAffer, Jeremiah Foster, Jessica Wilkerson, Jesus M. Gonzalez- Barahona, Jilayne Lovejoy, Jocelyn Matthews, Johan Linåker, John Mertic, Jon Lawrence, Jonathan Lipps, Jono Bacon, Jordi Cabot, Jose Manrique Lopez de la Fuente, Joshua Hickman, Joshua
    [Show full text]
  • PDF (611K, 38 Pages)
    Getting Unstuck A Sampler of Advice for Open Source Projects by Sumana Harihareswara © 2020 Sumana Harihareswara under the Creative Commons Attribution-ShareAlike 4.0 license (CC BY-SA) Please feel free to share this book, translate it, and reuse it per the license.1 Sumana Harihareswara Changeset Consulting LLC P.O. Box 721160 Jackson Heights, NY 11372 https://changeset.nyc/ +1 (929) 255-4578 Written in emacs and in New York City, 2020. Cover design and layout by Julia Rios Cover photograph by Susanne Stöckli For Leonard, my foundation. And for Aaron Swartz, our lighthouse. Table of Contents • Introduction • Conducting a SWOT analysis • How to start thinking about budgets and money • Teaching and including unskilled volunteers • An outline of the full book • Acknowledgments • About the author • Feedback welcome Introduction Getting Open Source Projects Unstuck (or, in other words: maintaining legacy open source projects. Below is the introduction for the full, forthcoming book.) Who this book is for and what you should get out of it You are about to get an open source project unstuck. Maybe a bunch of work is piling up in the repository and users are getting worried, waiting for a release. Maybe developers have gotten bogged down, trying to finish a big rewrite while maintaining the stable release. Maybe the project's suffering for lack of infrastructure — testing, money, an institutional home. You noticed the problem. So that means it's up to you to fix it. Or you're getting paid to fix it, even though you didn't start this thing. A while ago I blurted out the phrase "dammit-driven leadership." Because sometimes you look around, and you realize something needs doing, and you're the only one who really gets why, so you say, “Dammit, okay, I'll do it, then.” After reading this book, you should be prepared to: 1.
    [Show full text]
  • Annual Report 2006
    Annual Report 2006 Table of contents Foreword Letter from the Chairman, Dave Neary 4–5 A year in review 2006—a year in GNOME 8–10 Distributions in 2006 11 Events and community initiatives GUADEC—The GNOME Conference 12–13 GNOME hackers descend on MIT Media Center 14–15 GNOME User Groups 16 The www.gnome.org revamp 17 GNOME platform 17 GNOME Foundation Administrator 17 Foundation development The Women’s Summer Outreach Program 18–20 The GNOME Mobile and Embedded Initiative 21 The GNOME Advisory Board 22–23 PHOTO The GNOME Foundation Board and Advisory Board members by David Zeuthen (continued on the inside back cover) GNOME Foundation 3 Dear Friends, All traditions need a starting point, they say. What you now hold in your hands is the first annual report of the GNOME Foundation, at the end of what has been an eventful year for us. Each year brings its challenges and rewards for the members of this global project. This year, many of our biggest challenges are in the legal arena. European countries have been passing laws to conform with the European Union Copyright Directive, and some, including France, have brought into law provisions which we as software developers find it hard to understand, but which appear to make much of what we do illegal. We have found our- selves in the center of patent wars as bigger companies jockey for position with offerings based on our hard work. And we are scratching our heads trying to figure out how to deal with the constraints of DRM and patents in multimedia, while still offering our users access to their media files.
    [Show full text]
  • How Bad Can It Git? Characterizing Secret Leakage in Public Github Repositories
    How Bad Can It Git? Characterizing Secret Leakage in Public GitHub Repositories Michael Meli Matthew R. McNiece Bradley Reaves North Carolina State University North Carolina State University North Carolina State University [email protected] Cisco Systems, Inc. [email protected] [email protected] Abstract—GitHub and similar platforms have made public leaked in this way have been exploited before [4], [8], [21], [25], collaborative development of software commonplace. However, a [41], [46]. While this problem is known, it remains unknown to problem arises when this public code must manage authentication what extent secrets are leaked and how attackers can efficiently secrets, such as API keys or cryptographic secrets. These secrets and effectively extract these secrets. must be kept private for security, yet common development practices like adding these secrets to code make accidental leakage In this paper, we present the first comprehensive, longi- frequent. In this paper, we present the first large-scale and tudinal analysis of secret leakage on GitHub. We build and longitudinal analysis of secret leakage on GitHub. We examine evaluate two different approaches for mining secrets: one is able billions of files collected using two complementary approaches: a to discover 99% of newly committed files containing secrets in nearly six-month scan of real-time public GitHub commits and a public snapshot covering 13% of open-source repositories. We real time, while the other leverages a large snapshot covering focus on private key files and 11 high-impact platforms with 13% of all public repositories, some dating to GitHub’s creation. distinctive API key formats. This focus allows us to develop We examine millions of repositories and billions of files to conservative detection techniques that we manually and automat- recover hundreds of thousands of secrets targeting 11 different ically evaluate to ensure accurate results.
    [Show full text]
  • Github Pull Request Review
    Github Pull Request Review Archaic and delegable Pierre prenotifying her longboat reactivating while Hartley reflow some intercross fadelessly. Narratable and thickhydropathic when Pincus Francois emerged reintegrate his timing. her bedchambers filigree or deactivate tamely. Unlearned and chiromantic Bearnard never outmeasuring There is merged soon, optimize this can request review status becomes quite clear based on their code management repositories that we would react to uninstall the pros and By dzone contributors, required for projects have fixed by everyone who can. In this palace, the toolbar will show why green Checks donut, a grey Changes revision, and grey zero counters in the remaining boxes. For this page with each other process, critical security expert from empirical and. Do at production data obtained from visual studio code review so that you if you want you selected, you a pull request that bad practice. Github will see? In github pull request review your first was this. Program readability: procedures versus comments. If any change on changes in progress and effective code coverage changes in that all pull request? Stripe is not have made for other reviewers are. Haacked is a blog about Technology, Software, Management, and fast Source. Even if there is in github or bandwidth costs go read way you can be detected by submitting are changes into new posts in github pull request review time for agility, requiring signed out. Rbac rules and code and more hunting down a nice aspect of incoming pr will update it more merge methods to! Review apps will spend some changes might require a pull reminders for.
    [Show full text]
  • Large Free Software Projects and Bugzilla Lessons from GNOME Project QA
    Large Free Software Projects and Bugzilla Lessons from GNOME Project QA Luis Villa Ximian, Inc. [email protected], http://tieguy.org/ Abstract itory for quality assurance and patch track- ing. This was not a process without problems- The GNOME project transitioned, during the hackers resisted, QA volunteers did too lit- GNOME 2.0 development and release cycle, tle, or too much, we learned things we need from a fairly typical, mostly anarchic free soft- to know too late, or over-engineered the pro- ware development model to a more disciplined, cess too early. Despite the problems, though, release driven development model. The ed- GNOME learned a great deal and as a result, ucational portion of this paper will focus on GNOME’s latest releases have been more sta- two key components that made the GNOME ble and reliable than ever before (even if far QA model successful: developer/QA interac- from perfect yet :) tion and QA process. Falling into the first cat- The purpose of this paper isn’t to teach some- egory, it will discuss why GNOME develop- one to do QA, or to impress upon the reader ers bought in to the process, how Bugzilla was the need for good QA—other tomes have been made easier for them and for GNOME as a written on each of those subjects. Instead, it whole, and why they still believe in the pro- will focus on QA in a Free Software context— cess despite having been under Bugzilla’s lash how it works in GNOME, what needed to be for more than a year.
    [Show full text]
  • Resolver El Problema: “
    Cuando coges un arma para atacar, lo más natural es que te defiendas. Y somos millones de personas que defenderemos a quien nos liberó y trajo la transparencia desde la oscuridad de internet. Esto es una guerra que ha comenzado por parte de los canceladores de Stallman. Y lo han hecho sin pensarlo mucho, sólo cegados por las mentiras y manipulaciones de los medios afines al complot: Red Hat, Microsoft, Google, Canonical, Justice Social Warriors & gilipolles, al ala más reaccionaria de la sociedad norteamericana, esa hipócrita ante lo más hipócrita. No lo han pensado mucho porque olvidan que somos mayoría. Ellos tienen el dinero, nosotros somos el pueblo y llegaremos hasta el final, hasta que Red Hat salga de la FSF, al igual que la OSI y Microsoft y los reaccionarios fascistas de la cancelación abandonen sus ansias de arruinar al padre del software libre. Somos millones que tomaremos represalias. Ya habéis perdido. He aquí un listado de canceladores hispanos de Richard Stallman y otros personajes que quieren arruinar su vida, y de paso implantar el open source fagocitando el software libre. Son tan convencidos del software libre que casi todos tienen cuentas en Facebook, Twitter, Instagram. El listado de nombres es público y cualquiera puede tener acceso. También se añaden aquellas distribuciones y/o entornos de escritorio que deberíamos no apoyarles económicamente, así como organizaciones. La lista es dinámica y se irán añadiendo nombres conforme vayan firmando. Ruego entiendan que esto no es un listado de personas para ser atacados, sino que por favor, no tengan apoyo económico de la comunidad pro-Stallman.
    [Show full text]
  • Veni, Vidi, Vici
    Code Review: Veni, ViDI, Vici Yuriy Tymchuk, Andrea Mocci, Michele Lanza REVEAL @ Faculty of Informatics - University of Lugano, Switzerland Abstract—Modern software development sees code review as For example many of them leverage static code analysis a crucial part of the process, because not only does it facilitate techniques, like the ones provided by FindBugs [5], to spot the sharing of knowledge about the system at hand, but it may implementation problems. However, the results from such also lead to the early detection of defects, ultimately improving techniques are poorly integrated in a code review process, as the quality of the produced software. Although supported by we will see later. numerous approaches and tools, code review is still in its infancy, and indeed researchers have pointed out a number of We propose an approach to augment code review by inte- shortcomings in the state of the art. grating software quality evaluation, and more general design We present a critical analysis of the state of the art of code assessment, not only as a first class citizen, but as the core review tools and techniques, extracting a set of desired features concern of code review. Our approach, called Visual Design that code review tools should possess. We then present our vision Inspection (ViDI), uses visualization techniques to drive the and initial implementation of a novel code review approach quality assessment of the reviewed system, exploiting data named Visual Design Inspection (ViDI), illustrated through a set obtained through static code analysis. ViDI enables intuitive of usage scenarios. ViDI is based on a combination of visualization and easy defect fixing, personalized annotations, and review techniques, design heuristics, and static code analysis techniques.
    [Show full text]
  • How to Trust Auto-Generated Code Patches? a Developer Survey And
    How to trust auto-generated code patches? A developer survey and empirical assessment of existing program repair tools Yannic Noller∗ Ridwan Shariffdeen∗ National University of Singapore National University of Singapore Singapore Singapore [email protected] [email protected] Xiang Gao Abhik Roychoudhury National University of Singapore National University of Singapore Singapore Singapore [email protected] [email protected] ABSTRACT works on generating multi-line fixes [12, 29], or on transplanting Automated program repair is an emerging technology that seeks patches from one version to another [37] — to cover various use to automatically rectify bugs and vulnerabilities using learning, cases or scenarios of program repair. search, and semantic analysis. Trust in automatically generated Surprisingly, there is very little literature or systematic study patches is necessary for achieving greater adoption of program from either academia or industry — on the developer trust in pro- repair. Towards this goal, we survey more than 100 software practi- gram repair. In particular, what changes do we need to bring into tioners to understand the artifacts and setups needed to enhance the program repair process so that it becomes viable to have conver- trust in automatically generated patches. Based on the feedback sations on its wide-scale adoption? Part of the gulf in terms of lack from the survey on developer preferences, we quantitatively evalu- of trust comes from a lack of specifications — since the intended ate existing test-suite based program repair tools. We find that they behavior of the program is not formally documented, it is hard to cannot produce high-quality patches within a top-10 ranking and trust that the automatically generated patches meet this intended an acceptable time period of 1 hour.
    [Show full text]
  • Indicators for Missing Maintainership in Collaborative Open Source Projects
    TECHNISCHE UNIVERSITÄT CAROLO-WILHELMINA ZU BRAUNSCHWEIG Studienarbeit Indicators for Missing Maintainership in Collaborative Open Source Projects Andre Klapper February 04, 2013 Institute of Software Engineering and Automotive Informatics Prof. Dr.-Ing. Ina Schaefer Supervisor: Michael Dukaczewski Affidavit Hereby I, Andre Klapper, declare that I wrote the present thesis without any assis- tance from third parties and without any sources than those indicated in the thesis itself. Braunschweig / Prague, February 04, 2013 Abstract The thesis provides an attempt to use freely accessible metadata in order to identify missing maintainership in free and open source software projects by querying various data sources and rating the gathered information. GNOME and Apache are used as case studies. License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license. Keywords Maintenance, Activity, Open Source, Free Software, Metrics, Metadata, DOAP Contents List of Tablesx 1 Introduction1 1.1 Problem and Motivation.........................1 1.2 Objective.................................2 1.3 Outline...................................3 2 Theoretical Background4 2.1 Reasons for Inactivity..........................4 2.2 Problems Caused by Inactivity......................4 2.3 Ways to Pass Maintainership.......................5 3 Data Sources in Projects7 3.1 Identification and Accessibility......................7 3.2 Potential Sources and their Exploitability................7 3.2.1 Code Repositories.........................8 3.2.2 Mailing Lists...........................9 3.2.3 IRC Chat.............................9 3.2.4 Wikis............................... 10 3.2.5 Issue Tracking Systems...................... 11 3.2.6 Forums............................... 12 3.2.7 Releases.............................. 12 3.2.8 Patch Review........................... 13 3.2.9 Social Media............................ 13 3.2.10 Other Sources..........................
    [Show full text]
  • CHAOSS Metrics
    Metrics Release 202001 https://chaoss.community/metrics MIT License Copyright © 2020 CHAOSS a Linux Foundation® Project CHAOSS Contributors include: Ahmed Zerouali, Akshita Gupta, Amanda Brindle, Alberto Martín, Alberto Pérez García-Plaza, Alexander Serebrenik, Alexandre Courouble, Alolita Sharma, Alvaro del Castillo, Ahmed Zerouali, Ana Jimenez Santamaria, Andre Klapper, Andrea Gallo, Andy Grunwald, Andy Leak, Aniruddha Karajgi, Anita Sarma, Ankit Lohani, Ankur Sonawane, Anna Buhman, Armstrong Foundjem, Atharva Sharma, Ben Lloyd Pearson, Benjamin Copeland, Bingwen Ma, Boris Baldassari, Bram Adams, Brian Proffitt, Camilo Velazquez Rodriguez, Carol Chen, Carter Landis, Chris Clark, Christian Cmehil-Warn, Damien Legay, Dani Gellis, Daniel German, Daniel Izquierdo Cortazar, David A. Wheeler, David Moreno, David Pose, Dawn Foster, Derek Howard, Don Marti, Drashti, Dylan Marcy, Eleni Constantinou, Emma Irwin, Fil Maj, Gabe Heim, Georg J.P. Link, Gil Yehuda, Harish Pillay, Harshal Mittal, Henri Yandell, Henrik Mitsch, Ildiko Vancsa, Jacob Green, Jaice Singer Du Mars, Jason Clark, Javier Luis Cánovas Izquierdo, Jeff McAffer, Jeremiah Foster, Jessica Wilkerson, Jesus M. Gonzalez-Barahona, Jocelyn Matthews, Johan, Johan Linåker, John Mertic, Jon Lawrence, Jonathan Lipps, Jono Bacon, Jordi Cabot, Jose Manrique Lopez de la Fuente, Joshua R. Simmons, Josianne Marsan, Kate Stewart, Keanu Nichols, Kevin Lumbard, Kristof Van Tomme, Lars, Laura Gaetano, Lawrence Hecht, Leslie Hawthorne, Luis Cañas-Díaz, Luis Villa, Lukasz Gryglicki, Mark Matyas, Martin Coulombe, Matthew Broberg, Matt Germonprez, Matt Snell, Michael Downey, Miguel Ángel Fernández, Mike Wu, Neil Chue Hong, Nick Vidal, Nicole Huesman, Nishchith K Shetty, Nithya Ruff, Parth Sharma, Patrick Masson, Peter Monks, Pranjal Aswani, Prodromos Polychroniadis, Quan Zhou, Ray Paik, Remy DeCausemaker, Robert Lincoln Truesdale III, Robert Sanchez, Rupa Dachere, Saloni Garg, Saleh Motaal, Samantha Logan, Santiago Dueñas, Sarvesh Mehta, Sarah Conway, Sean P.
    [Show full text]