InnerSource (IS) is increasingly viewed as a way to improve large-scale software development. However, evidence on its adoption in public sector organizations remains limited. This paper reports a study of IS adoption in a Swedish Public Sector Organization. Drawing on nine semi-structured interviews and an internal workshop with 13 participants, we examine motivations, challenges, and improvement strategies for IS adoption. The results show that the main motivations are improving reuse, strengthening cross-team collaboration, and enabling faster and more cost-efficient development. Key challenges relate to a lack of an open culture and mindset, management of reusable assets (e.g., ownership, documentation, and code visibility), and ways of working (e.g., siloed practices and limited time for contributions). The study also identified improvements to address challenges, including fostering an enabling culture and mindset for IS and knowledge sharing, strengthening management support, and establishing internal platforms and governance for reusable assets.

Context: Open Source Software (OSS) is a crucial component of over 90% of digital infrastructure underpinning industry and public digital services, facilitating collaborative software development and dissemination. Its significance in the European public sector has been emphasised through various Ministerial Declarations, highlighting its potential to accelerate digitalisation, transform businesses, and foster a digitally skilled population. Research Aim: This study aims to explore how the adoption, development, and collaboration on OSS can be enabled through organisational support functions or centres of competency, also known as Open Source Programme Offices (OSPOs) within Public Sector Organisations (PSOs) in the European Union, Norway, Liechtenstein, and Iceland. Methodology: A qualitative research approach was adopted, involving an interview survey of 18 OSPO representatives across 16 cases of public-sector OSPOs. These cases were cross-analysed and categorised into six OSPO archetypes. The findings were validated and enriched through two follow-up focus groups that included earlier interviewees and additional experts. Results: The study identified six distinct OSPO archetypes, providing insights into their organisational structures, responsibilities, and contributions to OSS adoption. The archetypes, along with policy recommendations, offer guidance on how PSOs can design their own OSPOs, taking into account their specific context, resources, and policy goals. Conclusions: The findings enhance the understanding of OSPOs as strategic endeavours aimed at promoting OSS adoption. The study offers practical guidance for PSOs and policymakers on leveraging OSS to achieve strategic objectives, foster digital sovereignty, drive economic growth, and improve the interoperability and quality of digital services.

The increasing reliance on Open Source Software (OSS) in organizations’ software supply chains necessitates robust mechanisms in the intake process to ensure sourced components’ long-term viability and maintenance. Assessing OSS project health in the intake process is complex due to the wide range of socio-technical factors involved. This study aims to explore how the health of OSS projects may be assessed by practitioners from organizations’ intake perspective. We conducted a qualitative interview survey with 17 industry experts to identify aspects and related metrics of OSS health. These were mapped against literature and two existing industry frameworks. A subset was identified and applied through a case study at a large international automotive manufacturer. 21 health aspects with 72 connected metrics were identified covering community productivity and stability, orchestration, production processes, and outputs. Many metrics map against industry frameworks, while qualitative aspects are missing support. Special consideration is needed when assessing and comparing the health of OSS projects, including their life-cycle stage, complexity, governance concentration, and strategic importance for the focal organization. The case study shows that not all aspects and metrics may be leveraged due to resource constraints and complexity. Instead, subsets of metrics need to be prioritized, and applied in a structured approach using qualitative and quantitative means. The study provides a foundation and a starting point for developers in introducing health assessments of OSS components in their intake processes, while also pushing convergence towards a common corpus of health assessment in practice.

Context:Open Source Software (OSS) is a vital public good forming the foundation of nearly all modern software stacks. Its licensing enables reuse and collaboration, fueling innovation, competitiveness, and digital sovereignty. European and global policy frameworks recognize OSS as key to public sector transformation, advancing interoperability, transparency, and technological independence. However, systematic awareness and measurement of governmental OSS adoption remain limited.Objectives:This study contributes to digital government maturity indexes by analyzing how policies and institutional actions leverage OSS for software reuse and collaborative development across 16 digitally mature countries. It proposes potential indicators for inclusion in such indexes by examining OSS policy goals, key actors, and support mechanisms.Methods:A qualitative approach combines desk research of policy documents with semi-structured interviews of government representatives, producing detailed country reports. Cross-analysis focuses on policy rationales, promotion strategies, and implementation support.Results:OSS reuse policies are widespread, targeting both inbound adoption and outbound sharing, and are often led by central public sector organizations. Policy objectives emphasize interoperability, sovereignty, transparency, cost efficiency, and security—framed as both challenge and strength. Implementation is supported by Open Source Program Offices (OSPOs) that facilitate capacity building, resource pooling, and sustainable governance. Thirteen indicator areas are proposed, spanning policy design, incentives, implementation, and support.Conclusions:OSS is a strategic enabler of digital transformation. Realizing its full value requires coherent policy frameworks, institutional capacity, and integration of OSS indicators within global maturity assessments to enhance transparency, interoperability, and sovereignty.

Continuous experimentation (CE) is a software development approach where product decisions are data-driven. Large global internet-facing companies such as Microsoft, Google, and Facebook apply the practice by leveraging their massive user bases to obtain high statistical significance in experimentation results. However, companies with smaller user bases, such as small- and medium-sized enterprises (SMEs) and early-stage software startups, struggle to adopt CE due to limitations in user data. Our goal is to increase understanding of situations in CE where data limitations occur, as observed in the research literature. We investigate data limitations and challenges related to them, including their characteristics, and solutions and practices that may address these. We conducted a rapid review of CE papers from a previous systematic literature review, and analysed these to identify scenarios that exhibit data limitations in CE. We present a framework that illustrates different dimensions of data-limited CE (DLC) and connects scenarios to challenges and their potential future solutions. Most challenges and potential solutions that we found are related to the amount of data. We also note examples of other limitations related to, e.g., evaluation metrics, that provide interesting avenues for further research.

Context: Open Source Software (OSS) is a vital public good, included across most of modern software stacks, significantly impacting GDP and national tech growth, while supporting interoperability, sovereignty, and transparency. However, systematic measurement of governmental OSS adoption remain limited. Research Aim: This study contributes to digital government maturity indexes by analyzing policies and support actions leveraging OSS for software reuse and collaborative development across 16 digitally mature countries, and proposing potential indicators for said indexes. It examines OSS policy formation, stated goals, key actors, and support mechanisms. Methodology: A qualitative approach is used combining desk research of policy documents with semi-structured interviews of government representatives, producing detailed country reports. These are cross-analyzed, focusing on OSS policy promotion, rationale, and implementation support. Results: Policies facilitating OSS reuse are widespread, targeting both inbound acquisition and outbound sharing, and are predominantly governed by central public sector organizations. Policy goals include interoperability, digital sovereignty, transparency, and cost efficiency, with security framed both as a risk and strength. Implementation is supported by diverse Open Source Program Offices (OSPOs) at multiple government levels, which foster capacity building, resource pooling, and sustainable project governance. Indicators are synthesized and proposed across 14 areas covering policy incentives and design, and implementation and support. Conclusions: OSS is a strategic enabler for public sector digital transformation. Clear policy frameworks, coupled with institutional support such as OSPOs, are essential. International digital maturity frameworks should expand OSS indicators to better guide and assess government adoption and impact.

Background: Open Source Software (OSS) started as an effort of communities of volunteers, but its practices have been adopted far beyond these initial scenarios. For instance, the strategic use of OSS in industry is constantly growing nowadays in different verticals, including energy, automotive, and health. For the public sector, however, the adoption has lagged behind even if benefits particularly salient in the public sector context such as improved interoperability, transparency, and digital sovereignty have been pointed out. When Public Sector Organisations (PSOs) seek to engage with OSS, this introduces challenges as they often lack the necessary technical capabilities, while also being bound and influenced by regulations and practices for public procurement. Aim: We aim to shed light on how public sector OSS projects, i.e., projects initiated, developed and governed by public sector organizations, are developed and structured. We conjecture, based on the challenges of PSOs, that the way development is organized in these type of projects to a large extent disalign with the commonly adopted bazaar model (popularized by Eric Raymond), which implies that development is carried out collaboratively in a larger community. Method: We plan to contrast public sector OSS projects with a set of earlier reported case studies of bazaar OSS projects, including Mockus et al.'s reporting of the Apache web server and Mozilla browser OSS projects, along with the replications performed on the FreeBSD, JBossAS, JOnAS, and Apache Geronimo OSS projects. To enable comparable results, we will replicate the methodology used by Mockus et al. on a purposefully sampled subset of public sector OSS projects. The subset will be identified and characterized quantitatively by mining relevant software repositories, and qualitatively investigated through interviews with individuals from involved organizations.

[Background] The game industry faces fierce competition and games are developed on short deadlines and tight budgets. Continuously testing and experimenting with new ideas and features is essential in validating and guiding development toward market viability and success. Such continuous experimentation (CE) requires user data, which is often limited in early development stages. This challenge is further exacerbated for independent (indie) game companies with limited resources. [Aim] We wanted to gain insights into CE practices in pre-release indie game development. [Method] We performed an exploratory interview survey with 10 indie game developers from different companies and synthesised findings through an iterative coding process. [Results] We present a CE framework for game development that highlights key parts to consider when planning and implementing an experiment and note that pre-release experimentation is centred on qualitative data. Time and resource constraints impose limits on the type and extent of experimentation and playtesting that indie companies can perform, e.g. due to limited access to participants, biases and representativeness of the target audience. [Conclusions] Our results outline challenges and practices for conducting experiments with limited user data in early stages of indie game development, and may be of value also for larger game companies, and for software intensive organisations in other industries.

The integration of machine learning (ML) into software operations (MLOps) has significantly increased the demand for data to train and test models, making data sharing and reuse essential to mitigate the high costs of data collection and preprocessing. This study aims to advance the understanding of data sharing within an MLOps context by examining the establishment and governance of a data ecosystem, specifically focusing on the WARA-Ops initiative.Through a case study approach, this research investigates the technical platform, processes and governance of WARA-Ops data ecosystem by conducting interviews with ecosystem members, as well as observational studies of the technical infrastructure.Six interviews were held, with the platform orchestrators and representatives of four organizations interested in participating, as well as representatives of a different data sharing platform for validation purposes. Observations on the platform and surrounding ecosystem structure, governance and challenges were made, specifically centered around privacy, integrity and trust between the actors.As the WARA-Ops platform is still in the early development stage, it is important for all the parties to align their interest and expectations in order to create a safe and sustainable Open Data Ecosystem.

Background: Open Source Software (OSS) is often seen as an option to mitigate risks of lock-ins. Yet, single-vendor OSS can still result in soft lock-ins due to knowledge asymmetries and technical barriers. Aim: This study explores actors that render such soft lock-ins. Research design: We conduct a qualitative case study of an E-service Platform (ESP) used by over 190+ municipalities. Results: User-driven lock-in factors emerged as a significant category, including limited and non-transparent communication, restrictive qualification requirements in procurement, confusion on maintainership, and comfort in the status quo. Technical lock-in factors include inadequate documentation, dependency management issues, and limited test coverage. Conclusions: Strong leadership and continuous training is needed to address presence of comfort and conservative culture among municipalities. Open Source Stewards, i.e., neutral hosts for OSS projects, can support municipalities in these tasks while also helping to foster an open, competitive collaboration that can enable a broader supplier ecosystem.

The proliferation of open large language models (LLMs) is fostering a vibrant ecosystem of research and innovation in artificial intelligence (AI). However, the methods of collaboration used to develop open LLMs both before and after their public release have not yet been comprehensively studied, limiting our understanding of how open LLM projects are initiated, organized, and governed as well as what opportunities there are to foster this ecosystem even further. We address this gap through an exploratory analysis of open collaboration throughout the development and reuse lifecycle of open LLMs, drawing on semi-structured interviews with the developers of 14 open LLMs from grassroots projects, research institutes, startups, and Big Tech companies in North America, Europe, Africa, and Asia. We make three key contributions to research and practice. First, collaboration in open LLM projects extends far beyond the LLMs themselves, encompassing datasets, benchmarks, open source frameworks, leaderboards, knowledge sharing and discussion forums, and compute partnerships, among others. Second, open LLM developers have a variety of social, economic, and technological motivations, from democratizing AI access and promoting open science to building regional ecosystems and expanding language representation. Third, the sampled open LLM projects exhibit five distinct organizational models, ranging from single company projects to non-profit-sponsored grassroots projects, which vary in their centralization of control and community engagement strategies used throughout the open LLM lifecycle. We conclude with practical recommendations for stakeholders seeking to support the global community building a more open future for AI.

Open and shared government data and services offer an instrument for achieving innovation, interoperability, and transparency in public services but require relevant competency, resources, and culture to realise, something that the public sector actors often lack. In this case study, we exemplify how these challenges to data sharing may be tackled through horizontal coordination in the case of Trafiklab, a public-private collaboration on collecting and publishing open public transport data and services.

Free and Open Source Software (FOSS) communities' sustainability, meaning to remain operational without signs of weakening or interruptions to its development, is fundamental for the resilience and continuity of society's digital infrastructure. Many digital services and products either leverage or entirely rely on FOSS in their software stack. FOSS sustainability is a multifaceted concept, and the impact of its decline on community products is less known. In this study, we sought to understand how the different aspects of FOSS sustainability impact software quality from a life-cycle perspective. Specifically, we investigate whether and how support and incubation of FOSS projects or bypassing incubation correlate with software quality outcomes. We selected 342 FOSS projects from the Apache Software Foundation that have either graduated, retired, or bypassed their incubator program. We used 16 sustainability metrics to examine their impact on eight software quality metrics. Using Bayesian data analysis, we found that our selected sustainability metrics exhibit distinct relationships with software quality across different project trajectories. Graduated projects showed the strongest sustainability-software quality (SWQ) relationship, both during and post-incubation. In contrast, retired projects showed weaker relationships, despite receiving similar governance support. Bypassed projects, while not outperforming graduated ones, showed comparable sustainability-SWQ relationships. While structured incubation strengthens sustainability and SWQ in graduated projects, retired projects struggle to maintain strong sustainability-SWQ relationships, indicating that additional factors internal and specific to projects influence sustainability. This effect was evident among bypassed projects; their self-reliant sustainability practices yielded stronger sustainability-SWQ compared to the retired ones.

Background: Open Source Software (OSS) fuels our global digital infrastructure but is commonly maintained by small groups of people whose time and labor represent a depletable resource. For the OSS projects to stay sustainable, i.e., viable and maintained over time without interruption or weakening, maintenance labor requires an underlying infrastructure to be supported and secured. Aims: Using the construct of human infrastructure, our study aims to investigate how maintenance labor can be supported and secured to enable the creation and maintenance of sustainable OSS projects, viewed from the maintainers’ perspective. Method: In our exploration, we interviewed ten maintainers from nine well-adopted OSS projects. We coded the data in two steps using investigator-triangulation. Results: We constructed a framework of infrastructure design that provide insight for OSS projects in the design of their human infrastructure. The framework specifically highlight the importance of human factors, e.g., securing a work-life balance and proactively managing social pressure, toxicity, and diversity. We also note both differences and overlaps in how the infrastructure needs to support and secure maintenance labor from maintainers and the wider OSS community, respectively. Funding is specifically highlighted as an important enabler for both types of resources. Conclusions: The study contributes to the qualitative understanding of the importance, sensitivity, and risk for depletion of the maintenance labor required to build and maintain healthy OSS projects. Human infrastructure is pivotal in ensuring that maintenance labor is sustainable, and by extension the OSS projects on which we all depend.

Context: Free and Open Source Software (FOSS) communities' ability to stay viable and productive over time is pivotal for society as they maintain the building blocks that digital infrastructure, products, and services depend on. Sustainability may, however, be characterized from multiple aspects, and less is known how these aspects interplay and impact community outputs, and software quality specifically. Objective: This study, therefore, aims to empirically explore how the different aspects of FOSS sustainability impact software quality. Method: 16 sustainability metrics across four categories were sampled and applied to a set of 217 OSS projects sourced from the Apache Software Foundation Incubator program. The impact of a decline in the sustainability metrics was analyzed against eight software quality metrics using Bayesian data analysis, which incorporates probability distributions to represent the regression coefficients and intercepts. Results: Findings suggest that selected sustainability metrics do not significantly affect defect density or code coverage. However, a positive impact of community age was observed on specific code quality metrics, such as risk complexity, number of very large files, and code duplication percentage. Interestingly, findings show that even when communities are experiencing sustainability, certain code quality metrics are negatively impacted. Conclusion: Findings imply that code quality practices are not consistently linked to sustainability, and defect management and prevention may be prioritized over the former. Results suggest that growth, resulting in a more complex and large codebase, combined with a probable lack of understanding of code quality standards, may explain the degradation in certain aspects of code quality.