Dear AoIR community, I want to share with you all the CfP for a special issue that I am co-editing with Abel Guerra (LSE) on software libraries. Please have a look below, and feel free to share it with your colleagues and students. And of course, reach out if you have any questions! Thank you, Gabriel Pereira — Call for Proposals: Software Libraries: Following the Infrastructures of Code Special Issue for Computational Culture, a Journal of Software Studies (deadline 1 November 2026) Full details on: https://computationalculture.net/cfps-events/ Guest Editors: Gabriel Pereira, Assistant Professor in AI and Digital Culture (University of Amsterdam) Abel Guerra, LSE Fellow (London School of Economics) Keywords: software studies; infrastructures; platforms; epistemic regimes; digital methods; code. Description: A programmer who needs to build a website with a login form will not write from scratch the code that encrypts the password and manages the user’s session. Instead, they can import software libraries that already solve these tasks, for example bcrypt to encrypt the passwords and Flask to create the web server. With a single command in the terminal, pip install flask bcrypt, they can install these libraries and make them available in their project. As explained by David Berry (2011, p. 40), nowadays “code is written through a process of collage, whereby different fragments of code (usually called ‘#includes’) are glued together to form the final software product.” This imported code, known as software libraries, contains modular functions created and maintained by other people, companies, or foundations (Fink et al., 2020; cf. Krysa & Sedek, 2008). These libraries reduce programmers’ workload and allow them to focus their attention on the functions specific to their software, rather than recreating functions that are already widely used. Libraries thus operate as central infrastructural objects of computing, defining how a range of computational practices can develop (cf. Bowker & Star, 1999; Sandvig, 2013). Although they are not visible to end users and frequently recede even from developers’ own awareness, libraries play a fundamental role in organizing sociotechnical relations. They have direct impacts on how problems are defined and systems are programmed. The field of software studies is therefore central to understanding this materiality of code and how it is part of a social, collective construction (cf. Chun, 2011; Berry, 2011; Mackenzie, 2025). Because decisions about how libraries are developed directly shape how future information systems will function, there is often wide debate and preparation. In widely used libraries, such as the scientific computing library numpy, decisions are made by a large community of developers and maintainers. Potential changes are debated extensively because they may alter how the library is used by thousands of projects around the world. The popular user interface library React, by contrast, is maintained by Meta, while the well-known Artificial Intelligence library Transformers is maintained by Hugging Face. Software libraries must therefore be understood as sociotechnical, through both their code and their political economy: how they are funded, standardized, and operated. Are these essential code infrastructures becoming platformized (Plantin et al., 2018; Bounegru & Gray, 2024), given that Big Tech platforms have come to define the way essential functions are standardized? The intersection between infrastructure, platform, and software studies makes it possible to interrogate libraries both as programmable artifacts open to reappropriation and in their normative function in the organization of sociotechnical relations across different contexts of use. This Special Issue addresses the underresearched topic of software libraries by inviting submissions on topics that may include: Following libraries as sociotechnical objects The biography of a specific library, traced across institutional, geographic, and disciplinary contexts. The dependencies, forks, and version histories through which libraries accrete, fracture, or fall into disrepair. Inventive and digital methods for mapping libraries, their maintainers, and their downstream uses, including emerging forms of walkthrough and situational analysis. The labor of maintenance, documentation, and community management that keeps a library usable, and what happens when it breaks. The political economy and platformization of libraries How libraries are funded, governed, and standardized, and by whom, from volunteer maintainers to foundations to Big Tech. The platformization of essential code infrastructures, including the role of hubs, registries, and package managers as points of control, such as the npm registry, PyPI, or the Hugging Face Hub. Dependency and lock-in as forms of power, and the asymmetries between those who set standards and those who must adopt them. The geopolitics of libraries, including their adoption, refusal, or reappropriation by public institutions outside the centres where they are produced. Libraries as epistemic and normative infrastructures The normativity inscribed in defaults, abstractions, and application programming interfaces (APIs), as when a library’s defaults quietly become the standard way a task is done. The ways libraries define problems in advance, foreclosing some practices while affording others. Histories and media archaeologies of the software library, attending to how earlier forms (e.g. the idea of a reusable card library proposed for Babbage’s Analytical Engine, later subroutine libraries, package repositories) shaped what a library is today and its politics. Creative and critical (re)appropriation Artistic, activist, and critical making practices that repurpose, subvert, or rebuild libraries against their intended logics. Counter-libraries, forks, and “minor infrastructures” built as forms of resistance or refuge. Schedule 500-word abstracts should be emailed to Gabriel Pereira (g.pereira@uva.nl) and Abel Guerra (A.Goncalves-Guerra@lse.ac.uk) by November 1st, 2026. Abstracts will be reviewed by the special issue editors and the Computational Culture editorial board. Abstracts can be for articles, interviews or software/special projects (‘Comments’ are editorially reviewed rather than peer-reviewed articles or projects). Authors of selected abstracts will be notified by November 22nd, 2026 and invited to submit full manuscripts following a workshop (see below). A (hybrid) workshop for authors of selected papers will take place early February 2027 at the University of Amsterdam, to enable peer feedback prior to final submission. The full manuscript will be due April 1st, 2027. These manuscripts are subject to full blind peer review according to Computational Culture’s policies. Possible costs for proofreading incurred by the authors are not covered by the editors or the journal. There are no open access or processing charges for Computational Culture. The publication of the Special Issue is envisioned for October 2027. Computational Culture is an online open-access peer-reviewed journal of interdisciplinary enquiry into the nature of cultural computational objects, practices, processes and structures. Any queries can be addressed to the special issue editors: Gabriel Pereira (g.pereira@uva.nl) and Abel Guerra (A.Goncalves-Guerra@lse.ac.uk).