Extracting Rationale for Open Source Software Development Decisions — A Study of Python Email Archives

Abstract

A sound Decision-Making (DM) process is key to the successful governance of software projects. In many Open Source Software Development (OSSD) communities, DM processes lie buried amongst vast amounts of publicly available data. Hidden within this data lie the rationale for decisions that led to the evolution and maintenance of software products. While there have been some efforts to extract DM processes from publicly available data, the rationale behind how the decisions are made have seldom been explored. Extracting the rationale for these decisions can facilitate transparency (by making them known), and also promote accountability on the part of decision makers. This work bridges this gap by means of a large-scale study that unearths the rationale behind decisions from Python development email archives comprising about 1.5 million emails. This paper makes two main contributions. First, it makes a knowledge contribution by unearthing and presenting the ratio nale behind decisions made. Second, it makes a methodological contribution by presenting a heuristics-based rationale extraction system called Rationale Miner that employs multiple heuristics, and follows a data-driven, bottom-up approach to infer the rationale behind specific decisions (e.g., whether a new module is implemented based on core developer consensus or benevolent dictator s pronouncement). Our approach can be applied to extract rationale in other OSSD communities that have similar governance structures.

Runtime Evolution of Bitcoin's Consensus Rules

“…The similarities between open source software and blockchain evolution are seen in the decision-making on a code repository level [61], [62]. Anyone is free to propose a change, and it is up to the maintainers of a repository whether they want to include that change.…”

“…The main similarities between blockchain evolution and open software evolution can be seen in the decision-making on a code repository level [37,66]. In a blockchain, anyone can propose changes, depending on whether the repository's maintainers want to include that change.…”

Decisions in Continuous Integration and Delivery: An Exploratory Study

“…Li et al [11] tried to identify decisions discussed in the Hibernate developer mailing list and explore decision-making from several aspects (i.e., description, classification, underlying rationale, supporting approaches, related artifacts, and trend). Sharma et al [15] explored the rationale behind 'how' the decisions are made, and made a methodological contribution by presenting a heuristics-based rationale extraction system employing multiple heuristics, and following a data-driven, bottom-up approach to infer the rationale behind specific decisions. Liu et al [16] intended to understand how decisions are made in requirements engineering through the student projects in a requirements engineering course.…”

OSCMS: A Decentralized Open-Source Coordination Management System Using a Novel Triple-Blockchain Architecture

“…Although the introduction of open-source software (OSS) can improve development efficiency and save costs, there are still some problems in OS project management and OS ecosystem governance. Due to the dispersion of OSS and participants, the problems to be solved in OS ecosystems include code control [3,4], incentive [5], interaction and cooperation [6,7], automation [8,9], transparency and fairness of rights and responsibilities [10][11][12][13]. Traditional solutions and architectural models focus on perspectives such as communities, projects, OS participants, enterprises and organizations but are limited to centralization.…”