Free/Libre Open Source Software Communities Research Articles

Managing Episodic Volunteers in Free/Libre/Open Source Software Communities

We draw on the concept of episodic volunteering (EV) from the general volunteering literature to identify practices for managing EV in free/libre/open source software (FLOSS) communities. Infrequent but ongoing participation is widespread, but the practices that community managers are using to manage EV, and their concerns about EV, have not been previously documented. We conducted a policy Delphi study involving 24 FLOSS community managers from 22 different communities. Our panel identified 16 concerns related to managing EV in FLOSS, which we ranked by prevalence. We also describe 65 practices for managing EV in FLOSS. Almost three-quarters of these practices are used by at least three community managers. We report these practices using a systematic presentation that includes context, relationships between practices, and concerns that they address. These findings provide a coherent framework that can help FLOSS community managers to better manage episodic contributors.

An empirical verification of a-priori learning models on mailing archives in the context of online learning activities of participants in free\libre open source software (FLOSS) communities

Free\Libre Open Source Software (FLOSS) environments are increasingly dubbed as learning environments where practical software engineering skills can be acquired. Numerous studies have extensively investigated how knowledge is acquired in these environments through a collaborative learning model that define a learning process. Such a learning process, identified either as a result of surveys or by means of questionnaires, can be depicted through a series of graphical representations indicating the steps FLOSS community members go through as they acquire and exchange skills. These representations are referred to as a-priori learning models. They are Petri net-like workflow nets (WF-net) that provide a visual representation of the learning process as it is expected to occur. These models are representations of a learning framework or paradigm in FLOSS communities. As such, the credibility of any models is estimated through a process of model verification and validation. Therefore in this paper, we analyze these models in comparison with the real behavior captured in FLOSS repositories by means of conformance verification in process mining. The purpose of our study is twofold. Firstly, the results of our analysis provide insights on the possible discrepancies that are observed between the initial theoretical representations of learning processes and the real behavior captured in FLOSS event logs, constructed from mailing archives. Secondly, this comparison helps foster the understanding on how learning actually takes place in FLOSS environments based on empirical evidence directly from the data.

Assessing the Open Source Development Processes Using OMM

The assessment of development practices in Free Libre Open Source Software (FLOSS) projects can contribute to the improvement of the development process by identifying poor practices and providing a list of necessary practices. Available assessment methods (e.g., Capability Maturity Model Integration (CMMI)) do not address sufficiently FLOSS-specific aspects (e.g., geographically distributed development, importance of the contributions, reputation of the project, etc.). We present a FLOSS-focused, CMMI-like assessment/improvement model: the QualiPSo Open Source Maturity Model (OMM). OMM focuses on the development process. This makes it different from existing assessment models that are focused on the assessment of the product. We have assessed six FLOSS projects using OMM. Three projects were started and led by a software company, and three are developed by three different FLOSS communities. We identified poorly addressed development activities as the number of commit/bug reports, the external contributions, and the risk management. The results showed that FLOSS projects led by companies adopt standard project management approaches as product planning, design definition, and testing, that are less often addressed by community led FLOSS projects. The OMM is valuable for both the FLOSS community, by identifying critical development activities necessary to be improved, and for potential users that can better decide which product to adopt.

Division of Effort, Productivity, Quality, and Relationships in FLOSS Virtual Teams: Evidence from the FreeBSD Project

Research in virtual teams and distributed work argues that the lack of collocation places an overhead on the performance potential of large, globally distributed teams. In this paper, we revisit this tenet through a case study of Free/Libre Open Source Software (FLOSS) development to demonstrate how globally dispersed FLOSS communities manage to overcome the problem of geographic separation of their members. Our results show that successful FLOSS teams demonstrate a truly global distribution of members, who perform different types of work so as to achieve consistent round-the-clock development, without any apparent ill effects on team productivity and the quality of the resulting outcomes. Cooperation between team members is abundant, especially at more complex work items, and does not seem to be affected by distance; only mentoring relationships appear in some cases to be easier to cultivate between individuals living closer together. These findings challenge the conventional wisdom of research in distributed work, in cases where virtual teams consist of highly skilled and motivated individuals, who leverage the power of communication technologies to overcome problems associated with physical distance.

Effort estimation of FLOSS projects: a study of the Linux kernel

Empirical research on Free/Libre/Open Source Software (FLOSS) has shown that developers tend to cluster around two main roles: “core” contributors differ from “peripheral” developers in terms of a larger number of responsibilities and a higher productivity pattern. A further, cross-cutting characterization of developers could be achieved by associating developers with “time slots”, and different patterns of activity and effort could be associated to such slots. Such analysis, if replicated, could be used not only to compare different FLOSS communities, and to evaluate their stability and maturity, but also to determine within projects, how the effort is distributed in a given period, and to estimate future needs with respect to key points in the software life-cycle (e.g., major releases). This study analyses the activity patterns within the Linux kernel project, at first focusing on the overall distribution of effort and activity within weeks and days; then, dividing each day into three 8-hour time slots, and focusing on effort and activity around major releases. Such analyses have the objective of evaluating effort, productivity and types of activity globally and around major releases. They enable a comparison of these releases and patterns of effort and activities with traditional software products and processes, and in turn, the identification of company-driven projects (i.e., working mainly during office hours) among FLOSS endeavors. The results of this research show that, overall, the effort within the Linux kernel community is constant (albeit at different levels) throughout the week, signalling the need of updated estimation models, different from those used in traditional 9am–5pm, Monday to Friday commercial companies. It also becomes evident that the activity before a release is vastly different from after a release, and that the changes show an increase in code complexity in specific time slots (notably in the late night hours), which will later require additional maintenance efforts.

Flat for the Few, Steep for the Many

A discrepancy exists between the emphasis posed by practitioners on decentralized and non-hierarchical communication in Free Libre/Open Source Software (FLOSS) communities and empirical evidence of their hierarchical structure. To explain this paradox, it is hypothesized firstly that in FLOSS communities local sub-groups exist and are less hierarchical, more decentralized than the whole social network. Secondly, it is hypothesized that the bulk of communication exchanges taking place in the community happens inside local sub-groups formed by the most active community members. The recollection that practitioners have of FLOSS communities to which they participate would then be influenced by the position that they occupy inside those sub-groups. A measure of structural cohesion based on network node connectivity is proposed as an effective method to test whether FLOSS communication networks can be decomposed in nested hierarchies of progressively less centralized sub-groups. The recently introduced measure of weighted rich-club effect is adopted to test for the tendency of the most active community members to control communication by interacting more intensely with each other than with other members of the network. Results from a case study that are consistent with the hypotheses are presented and discussed.

Developing 'FLOSS', a Market Driven Investment

Over the last few years, FLOSS (“Free Libre Open Source Software”) has become a commercially viable reality of the first order. It is viewed as an extreme case of open innovation, and thus of a laboratory for analysing innovation production in Internet based/knowledge based industries. A increasing number of companies are getting involved in the communities of development and scholars have analysed FLOSS communities and product as a complementary asset for firms. The question is thus to understand how firms right tune their level of investment in FLOSS production and communities to support their business, but without over give back its intellectual production to potential competitors. In this article, we debate this question, defending the idea that this involvement can be of different intensity, from complementary to specific asset, and that this intensity depends of the market of the firm. To do so, we surveyed francophone companies (France, Belgium, Switzerland) affirming a utilization of FLOSS in their commercial activity. Based on roughly 500 companies concerned, we obtained 141 usable responses and, via a cluster analysis (hierarchical ascendant classification, HAC) we statistically verified a link between FLOSS commercial strategies and degree of involvement into communities. This AHC produces a typology of commercial strategies, with differences in involvement, we explain.

Hybrid innovation: The dynamics of collaboration between the FLOSS community and corporations

Unlike innovation based on a strong professional culture involving close collaboration between professionals in academia and/or corporations, the current Free/Libre Open Source Software (FLOSS) development entails a global knowledge network, which consists of 1) a heterogeneous community of individuals and organizations who do not necessarily have professional backgrounds in computer science but have developed the competency to understand programming and working in a public domain; 2) corporations. This paper describes the operation of the hybrid form of developing and implementing software, and also identifies several key factors shaping the collaboration between FLOSS firms and the community.