Impact of stakeholder type and collaboration on issue resolution time in OSS Projects

Born as a movement of collective contribution of volunteer developers, Open source software (OSS) attracts an increasing involvement of commercial firms. Many OSS projects are composed of a mix group of firm- paid and volunteer developers, with different motivation, collaboration practices and working styles. As OSS is collaborative work in nature, it is important to know whether these differences have an impact on project outcomes. In this paper, we empirically investigate the firm-paid participation in resolving OSS evolution issues, the stakeholder collaboration and its impact on OSS issue resolution time. The results suggest that though a firm-paid developer resolves much more issues than a volunteer developer does, there is no difference in issue resolution time between firm-paid and volunteer developers. Besides, the more important factor that influences the issue resolution time comes from the collaboration among stakeholders rather than from measures of individual characteristics.Peer ReviewedPostprint (author’s final draft

Impact of Stakeholder Type and Collaboration on Issue Resolution Time in OSS Projects

Abstract. Initialized by a collective contribution of volunteer developers, Open source software (OSS) attracts an increasing involvement of commercial firms. Many OSS projects are composed of a mix group of firm-paid and volunteer developers, with different motivations, collaboration practices and working styles. As OSS development consists of collaborative works in nature, it is important to know whether these differences have an impact on collaboration between difference types of stakeholders, which lead to an influence in the project outcomes. In this paper, we empirically investigate the firm-paid participation in resolving OSS evolution issues, the stakeholder collaboration and its impact on OSS issue resolution time. The results suggest that though a firm-paid assigned developer resolves much more issues than a volunteer developer does, there is no difference in issue resolution time between them. Besides, the more important factor that influences the issue resolution time comes from the collaboration among stakeholders rather than from individual characteristics

How Firms Adapt and Interact in Open Source Ecosystems: Analyzing Stakeholder Influence and Collaboration Patterns

[Context and motivation] Ecosystems developed as Open Source Software (OSS) are considered to be highly innovative and reactive to new market trends due to their openness and wide-ranging contributor base. Participation in OSS often implies opening up of the software development process and exposure towards new stakeholders. [Question/Problem] Firms considering to engage in such an environment should carefully consider potential opportunities and challenges upfront. The openness may lead to higher innovation potential but also to frictional losses for engaged firms. Further, as an ecosystem progresses, power structures and influence on feature selection may fluctuate accordingly. [Principal ideas/results] We analyze the Apache Hadoop ecosystem in a quantitative longitudinal case study to investigate changing stakeholder influence and collaboration patterns. Further, we investigate how its innovation and time-to-market evolve at the same time. [Contribution] Findings show collaborations between and influence shifting among rivaling and non-competing firms. Network analysis proves valuable on how an awareness of past, present and emerging stakeholders, in regards to power structure and collaborations may be created. Furthermore, the ecosystem’s innovation and time-to-market show strong variations among the release history. Indications were also found that these characteristics are influenced by the way how stakeholders collaborate with each other

Enforcing public data archiving policies in academic publishing: A study of ecology journals

To improve the quality and efficiency of research, groups within the scientific community seek to exploit the value of data sharing. Funders, institutions, and specialist organizations are developing and implementing strategies to encourage or mandate data sharing within and across disciplines, with varying degrees of success. Academic journals in ecology and evolution have adopted several types of public data archiving policies requiring authors to make data underlying scholarly manuscripts freely available. Yet anecdotes from the community and studies evaluating data availability suggest that these policies have not obtained the desired effects, both in terms of quantity and quality of available datasets. We conducted a qualitative, interview-based study with journal editorial staff and other stakeholders in the academic publishing process to examine how journals enforce data archiving policies. We specifically sought to establish who editors and other stakeholders perceive as responsible for ensuring data completeness and quality in the peer review process. Our analysis revealed little consensus with regard to how data archiving policies should be enforced and who should hold authors accountable for dataset submissions. Themes in interviewee responses included hopefulness that reviewers would take the initiative to review datasets and trust in authors to ensure the completeness and quality of their datasets. We highlight problematic aspects of these thematic responses and offer potential starting points for improvement of the public data archiving process.Comment: 35 pages, 1 figure, 1 tabl

Collaborative Requirements Engineering Notation for Planning Globally Distributed Projects

Requirements engineering represents a critical phase of the software development lifecycle in which requirements describing the functional and non-functional behaviors of a system are elicited, modeled, analyzed, negotiated, agreed, and specified. In traditional software systems these tasks are typically performed in face-to-face meetings between requirements engineers and the project level stakeholders. However, in today’s global software development environment, it is becoming increasingly commonplace for stakeholders to be dispersed across multiple geographical locations and time zones. Under these circumstances, face-to-face meetings become expensive, and often impossible to facilitate, and as a result the success of the requirements process relies, at least partially, on tools and processes that support distributed communication and collaboration. To investigate the challenges and effective practices for performing requirements activities in distributed environments, we conducted a series of in-depth interviews with project managers and business analysts who have worked with non-co-located stakeholders. Since many project managers fail to plan and deploy the necessary infrastructures to support quality communication, and in practice requirements are often elicited and managed via email exchanges; we introduced a visual modeling notation to help project managers proactively plan the collaboration infrastructures needed to support requirements-related activities in globally distributed projects. An underlying meta-model defines the elements of the modeling language, including locations, stakeholder roles, communication flows, critical documents, and supporting tools and repositories. The interview findings were further analyzed to identify practices that led to success or created significant challenges for the projects; resulting in a set of patterns for globally distributed requirements engineering

Collaborative resolution of requirements mismatches when adopting open source components

[Context and motivation] There is considerable flexibility in requirements specifications (both functional and non-functional), as well as in the features of available OSS components. This allows a collaborative matching and negotiation process between stakeholders such as: customers, software contractors and OSS communities, regarding desired requirements versus available and thus reusable OSS components. [Problem] However, inconclusive research exists on such cooperative processes. Not much empirical data exists supporting the conduction of such research based on observation of industrial OSS adoption projects. This paper investigates how functional and non-functional requirement mismatches are handled in practice. [Results] We found two common approaches to handle functional mismatches. The main resolution approach is to get the components changed by the development team, OSS community or commercial vendor. The other resolution approach is to influence requirements, often by postponing requirements. Overall, non-functional requirements are satisfactorily achieved by using OSS components. Last but not least, we found that the customer involvement could enhance functional mismatch resolution while OSS community involvement could improve non-functional mismatch resolution. [Contribution] Our data suggests that the selecting components should be done iteratively with close collaboration with stakeholders. Improvement in requirement mismatch resolution to requirements could be achieved by careful consideration of mismatches size, requirements flexibility and components quality.Peer ReviewedPostprint (author's final draft

Requirements Management in an Open Source Software Project : Empirical Case Study

In the past few decades there has been increasing interest towards open innovation both among academia and in businesses. Especially software intensive companies face rapid technological change, which forces them to seek new sources of innovation. Companies can do this by using various open innovation approaches where they can share their knowledge and resources or utilize the knowledge and resources of outsiders ranging from other companies to individual developers. Open source software (OSS) is a blooming open innovation strategy used by a growing number of companies. OSS communities can have a large number of members, making the requirements management process challenging. This thesis aims to build an understanding of the requirements management process in a company that is leading an actively developed open source project. The studied OSS community doesn’t only have individual developers, but many companies participate in it as well. The thesis explores first open innovation, open source software development, and requirements engineering with means of a literature review. The goal of the literature review is to investigate open innovation and requirements management in OSS context. The literature review also provides a theoretical background for studying the open innovation and the requirements management process in the case company called Qt Company. The Qt Company leads an OSS project, which is the subject of this study. The project’s requirements management process was studied with the help of several information sources. These included interviews of Qt’s employees. The interviews were conducted in a research project called OpenReq. Additional information was gathered from the company’s websites and the project’s requirements management system. To verify the results, we first studied a few issues from the requirements management system to see whether they followed our conceptual model built based on the interviews, and illustrated as a swimlane diagram. Finally, we had a follow up interview with an employee from Qt Company (Qt’s community manager) to verify the results, and to correct any inaccuracies or misunderstandings. We found Qt Company using both inbound and outbound open innovation approaches in the studied OSS project. The project, and the community around it has many similarities to the OSS community descriptions found in the literature. For example, as often in OSS, the requirements in the studied project are unstructured. The requirements management process in the studied OSS project was found to include 12 different stakeholders. Also a diagram summarizing the whole requirements management process is constructed based on the interviews and presented at the results section of the thesis

Polycentric Information Commons: A Theory Development and Empirical Investigation

Decentralized systems online—such as open source software (OSS) development, online communities, wikis, and social media—often experience decline in participation which threatens their long-terms sustainability. Building on a rich body of research on the sustainability of physical resource systems, this dissertation presents a novel theoretical framing that addresses the sustainability issues arising in decentralized systems online and which are amplified because of their open nature. The first essay develops the theory of polycentric information commons (PIC) which conceptualizes decentralized systems online as “information commons”. The theory defines information commons, the stakeholders that participate in them, the sustainability indicators of information commons and the collective-action threats putting pressure on their long-term sustainability. Drawing on Ostrom’s factors associated with stable common pool resource systems, PIC theory specifies four polycentric governance practices that can help information commons reduce the magnitude and impact of collective-action threats while improving the information commons’ sustainability. The second essay further develops PIC theory by applying it in an empirical context of “digital activism”. Specifically, it examines the role of polycentric governance in reducing the threats to the legitimacy of digital activism—a type of information commons with an overarching objective of instigating societal change. As such, it illustrates the applicability of PIC theory in the study of digital activism. The third essay focuses on the threat of “information pollution” and its impact on open collaboration, a type of information commons dedicated to the creation of value through open participation online. It uncovers the way polycentric governance mechanism help reduce the duration of pollution events. This essay contributes to PIC theory by expanding it to the realm of operational governance in open collaboration

‘Open source has won and lost the war’: Legitimising commercial–communal hybridisation in a FOSS project

International audienceInformation technology (IT) firms are paying developers in Free and Open Source Software (FOSS) projects, leading to the emergence of hybrid forms of work. In order to understand how the firm–project hybridisation process occurs, we present the results of an online survey of participants in the Debian project, as well as interviews with Debian Developers. We find that the intermingling of the commercial logic of the firm and the communal logic of the project requires rhetorical legitimation. We analyse the discourses used to legitimise firm–project cooperation as well as the organisational mechanisms which facilitate this cooperation. A first phase of legitimation, based on firm adoption of open licenses and developer self-fulfilment, aims to erase the commercial/communal divide. A second more recent phase seeks to professionalise work relations inside the project and, in doing so, challenges the social order which restricts participation in FOSS. Ultimately, hybridisation raises the question of the fair distribution of the profits firms derive from FOSS