Contribution Barriers to Open Source Projects

Contribution barriers are properties of Free/Libre and Open Source Software (FLOSS) projects that may prevent newcomers from contributing. Contribution barriers can be seen as forces that oppose the motivations of newcomers. While there is extensive research on the motivation of FLOSS developers, little is known about contribution barriers. However, a steady influx of new developers is connected to the success of a FLOSS project. The first part of this thesis adds two surveys to the existing research that target contribution barriers and motivations of newcomers. The first exploratory survey provides the indications to formulate research hypotheses for the second main survey with 117 responses from newcomers in the two FLOSS projects Mozilla and GNOME. The results lead to an assessment of the importance of the identified contribution barriers and to a new model of the joining process that allows the identification of subgroups of newcomers affected by specific contribution barriers. The second part of the thesis uses the pattern concept to externalize knowledge about techniques lowering contribution barriers. This includes a complete categorization of the existing work on FLOSS patterns and the first empirical evaluation of these FLOSS patterns and their relationships. The thesis contains six FLOSS patterns that lower specific important contribution barriers identified in the surveys. Wikis are web-based systems that allow its users to modify the wiki's contents. They found on wiki principles with which they minimize contribution barriers. The last part of the thesis explores whether a wiki, whose content is usually natural text, can also be used for software development. Such a Wiki Development Environment (WikiDE) must fulfill the requirements of both an Integrated Development Environment (IDE) and a wiki. The simultaneous compliance of both sets of requirements imposes special challenges. The thesis describes an adapted contribution process supported by an architecture concept that solves these challenges. Two components of a WikiDE are discussed in detail. Each of them helps to lower a contribution barrier. A Proof of Concept (PoC) realization demonstrates the feasibility of the concept

Is the source strong with you? A fit perspective to predict sustained participation of FLOSS developers

Despite the notable success of some Free Libre Open Source (FLOSS) projects, the overwhelming majority of FLOSS initiatives fail, mostly because of insufficient long-term participation of developers. In contrast to previous research which focuses on the individual perspective, we approach developer retention from an organizational perspective to help existing project members identify potential long-term contributors who are worth spending their time on. Methodically, we transfer two concepts from professional recruiting, Person-Job (P-J) and Person-Team (P-T) fit, to the FLOSS domain and evaluate their usage to predict FLOSS developer retention. An empirical analysis reveals that both fit concepts are appropriate to explain FLOSS retention behavior. Looking at contributor retention in Google Summer of Code (GSoC) projects, we find a moderate correlation with P-J fit and a weak correlation with P-T fit

Adopting Free/Libre/Open Source Software Practices, Techniques and Methods for Industrial Use

Today’s software companies face the challenges of highly distributed development projects and constantly changing requirements. This paper proposes the adoption of relevant Free/Libre/Open Source Software (FLOSS) practices in order to improve software development projects in industry. Many FLOSS projects have proven to be very successful, producing high quality products with steady and frequent releases. This study aims to identify FLOSS practices that can be adapted for the corporate environment. To achieve this goal, a framework to compare FLOSS and industrial development methodologies was created. Three successful FLOSS projects were selected as study targets (the Linux Kernel, the FreeBSD operating system, and the JBoss application server), as well as two projects from Ericsson, a large telecommunications company. Based on an analysis of these projects, FLOSS best practices were tailored to fit industrial development environments. The final results consisted of a set of key adoption opportunities that aimed to improve software quality and overall development productivity by importing best practices from the FLOSS environment. The adoption opportunities were then validated at three large corporations

Why We Engage in FLOSS: Answers from Core Developers

The maintenance and evolution of Free/Libre Open Source Software (FLOSS) projects demand the constant attraction of core developers. In this paper, we report the results of a survey with 52 developers, who recently became core contributors of popular GitHub projects. We reveal their motivations to assume a key role in FLOSS projects (e.g., improving the projects because they are also using it), the project characteristics that most helped in their engagement process (e.g., a friendly community), and the barriers faced by the surveyed core developers (e.g., lack of time of the project leaders). We also compare our results with related studies about others kinds of open source contributors (casual, one-time, and newcomers).Comment: Accepted at CHASE 2018: 11th International Workshop on Cooperative and Human Aspects of Software Engineering (8 pages

Firms' contribution to open source software and the dominant skilled user

: Free/libre or open-source software (FLOSS) is nowadays produced not only by individual benevolent developers but, in a growing proportion, by firms that hire programmers for their own objectives of development in open source or for contributing to open-source projects in the context of dedicated communities. A recent literature has focused on the question of the business models explaining how and why firms may draw benefits from such involvement and their connected activities. They can be considered as the building blocks of a new modus operandi of an industry, built on an alternative approach to intellectual property management. Its prospects will depend on both the firms' willingness to rally and its ability to compete with the traditional “proprietary” approach. As a matter of fact, firms' involvement in FLOSS, while growing, remains very contrasting, depending on the nature of the products and the characteristics of the markets. The aim of this paper is to emphasize that, beside factors like the importance of software as a core competence of the firm, the role of users on the related markets - and more precisely their level of skills - may provide a major explanation of such diversity. We introduce the concept of the dominant skilled user and we set up a theoretical model to better understand how it may condition the nature and outcome of the competition between a FLOSS firm and a proprietary firm. We discuss these results in the light of empirical stylized facts drawn from the recent trends in the software industrySoftware ; Open Source ; Intellectual Property ; Competition ; Users

Free/Libre/Open Source Software (Floss): Lessons for Intellectual Property Rights Management in a Knowledge-Based Economy

International audienceThe aim of this paper is to focus on the emerging situation in which open source software is nowadays produced not only by individual developers but in a growing proportion by firms that hire programmers for their own objectives of development in open source or for contributing to open source projects in the context of dedicated communities. As commercial firms it is important to analyze how and why they are capable of drawing benefits from such involvement and their connected activities. Moreover, we want to stress the different types of business model these firms rely on and the possible evolution they are likely to follow in the near future. We shown how Open Source principles provide an alternative way of thinking and managing intellectual property that do not come up against the same problems but needs a radical change in the way of drawing commercial benefits from knowledge development tasks. Then we analyze the growing involvement of commercial actors by setting up a typology of the different business models that can be observed in the OS landscape, how they correspond to the different strategies of industrial firms according to the main characteristics of their technical skills and market position. Finally, in a conclusive section we will draw the main lessons of the FLOSS experience for a possible enlargement of those principles of IPR management and business to other knowledge based commercial activities

A qualitative enquiry into OpenStreetMap making

Based on a case study on the OpenStreetMap community, this paper provides a contextual and embodied understanding of the user-led, user-participatory and user-generated produsage phenomenon. It employs Grounded Theory, Social Worlds Theory, and qualitative methods to illuminate and explores the produsage processes of OpenStreetMap making, and how knowledge artefacts such as maps can be collectively and collaboratively produced by a community of people, who are situated in different places around the world but engaged with the same repertoire of mapping practices. The empirical data illustrate that OpenStreetMap itself acts as a boundary object that enables actors from different social worlds to co-produce the Map through interacting with each other and negotiating the meanings of mapping, the mapping data and the Map itself. The discourses also show that unlike traditional maps that black-box cartographic knowledge and offer a single dominant perspective of cities or places, OpenStreetMap is an embodied epistemic object that embraces different world views. The paper also explores how contributors build their identities as an OpenStreetMaper alongside some other identities they have. Understanding the identity-building process helps to understand mapping as an embodied activity with emotional, cognitive and social repertoires

Google Summer of Code: Student Motivations and Contributions

Several open source software (OSS) projects expect to foster newcomers' onboarding and to receive contributions by participating in engagement programs, like Summers of Code. However, there is little empirical evidence showing why students join such programs. In this paper, we study the well-established Google Summer of Code (GSoC), which is a 3-month OSS engagement program that offers stipends and mentors to students willing to contribute to OSS projects. We combined a survey (students and mentors) and interviews (students) to understand what motivates students to enter GSoC. Our results show that students enter GSoC for an enriching experience, not necessarily to become frequent contributors. Our data suggest that, while the stipends are an important motivator, the students participate for work experience and the ability to attach the name of the supporting organization to their resum\'es. We also discuss practical implications for students, mentors, OSS projects, and Summer of Code programs.Comment: 30 page