arXiv subjects

James Herbsleb

Publications and source records attributed to James Herbsleb.

5 recordsLinked to original sources

arXiv2025

The Strength of Weak Ties Between Open-Source Developers

In a real-world social network, weak ties (reflecting low-intensity, infrequent interactions) act as bridges and connect people to different social circles, giving them access to diverse information and opportunities that are not available within one's immediate, close-knit vicinity. Weak ties can be crucial for creativity and innovation, as they introduce ideas and approaches that people can then combine in novel ways, leading to innovative solutions. Do weak ties facilitate creativity in software in similar ways? This paper suggests that the answer is "yes." Concretely, we study the correlation between developers' knowledge acquisition through three distinct interaction networks on GitHub and the innovativeness of the projects they develop, across over 37,000 Python projects hosted on GitHub. Our findings suggest that the topical diversity of projects in which developers engage, rather than the volume, correlates positively with the innovativeness of their future code. Notably, exposure through weak interactions (e.g., starring) emerges as a stronger predictor of future novelty than via strong ones (e.g., committing)

cs.SE↗

arXiv2024

Power and Play: Investigating "License to Critique" in Teams' AI Ethics Discussions

Past work has sought to design AI ethics interventions--such as checklists or toolkits--to help practitioners design more ethical AI systems. However, other work demonstrates how these interventions may instead serve to limit critique to that addressed within the intervention, while rendering broader concerns illegitimate. In this paper, drawing on work examining how standards enact discursive closure and how power relations affect whether and how people raise critique, we recruit three corporate teams, and one activist team, each with prior context working with one another, to play a game designed to trigger broad discussion around AI ethics. We use this as a point of contrast to trigger reflection on their teams' past discussions, examining factors which may affect their "license to critique" in AI ethics discussions. We then report on how particular affordances of this game may influence discussion, and find that the hypothetical context created in the game is unlikely to be a viable mechanism for real world change. We discuss how power dynamics within a group and notions of "scope" affect whether people may be willing to raise critique in AI ethics discussions, and discuss our finding that games are unlikely to enable direct changes to products or practice, but may be more likely to allow members to find critically-aligned allies for future collective action.

cs.CY↗

arXiv2021

Global Software Engineering in the Age of GitHub and Zoom

Much has changed since the inaugural ICGSE conference in 2006. Tools have improved, awareness of cultural differences is widespread, and developments such as the foregrounding of open source have all enhanced our ability to work across geographic divides. But the pervasive and profound impact of software in the world -- especially for societal scale systems such as social media -- forces new and deeply challenging responsibilities on both developers and academics. We must find better ways of incorporating ethics into our development practices and pay far more attention to harmful unintended consequences as deployed systems interact with and often disrupt crucial social systems.

cs.SE↗

arXiv2020

Guiding Development Work Across a Software Ecosystem by Visualizing Usage Data

Software is increasingly produced in the form of ecosystems, collections of interdependent components maintained by a distributed community. These ecosystems act as network organizations, not markets, and thus often lack actionable price-like signals about how the software is used and what impact it has. We introduce a tool, the Scientific Software Network Map, that collects and displays summarized usage data tailored to the needs of actors in software ecosystems. We performed a contextualized walkthrough of the Map with producers and stewards in six scientific software ecosystems that use the R language. We found that they work to maximize diversity rather than quantity of uses, and to minimize coordination costs. We also found that summarized usage data would be useful for justifying ecosystem work to funding agencies; and we discovered a variety of more granular usage needs that would help in adding or maintaining features.

cs.SE↗

arXiv2019

A Preliminary Theory for Open Source Ecosystem Micro-economics

While there has been substantial empirical work identifying factors that influence the contribution to, and use of open source software, we have as yet little theory that identifies the key constructs and relationships that would allow us to explain and predict how open source ecosystems function. What is needed is a clearly articulated and empirically validated theory of open source ecosystems. Such a theory should: $\bullet$ Explain why, how, and when key resources---primarily the work of developers---are attracted to or depart from a project or an ecosystem. $\bullet$ Explain why, how, and when projects and ecosystems move through a life cycle, from initiation, growth, maturity, and decline and death. $\bullet$ Explain how decisions about use are made, and how the cumulatively influence the socio-technical position of a project within an ecosystem, and the relations of ecosystems to each other.The remainder of this chapter provides a sketch of such a theory in the form of a set of propositions, which may form the foundation for future empirical work

cs.CY↗