Repositories, Contributors, and Continuity: An Empirical Study of Foundational Quantum Software

Nicole Hoess; Ralf Ramsauer; Vincent Gierisch; Wolfgang Mauerer

REVIEW 3 major objections 3 minor 20 references

Repositories, Contributors, and Continuity: An Empirical Study of Foundational Quantum Software

T0 review · 3 major / 3 minor · reviewed 2026-08-01 · deepseek-v4-flash

Challenge this review Re-run · record.json Download PDF Read on arXiv ↗

Pith's one-line read By tracking contributor moves across sixteen quantum projects, this study shows that ideas from short-lived research repositories persist in industry frameworks through the same developers.

desk verdict Useful first cross-repository map of quantum software contributors; the knowledge-transfer claim is honestly hedged but rests on a proxy that needs more content-level support. read the letter →

arxiv 2607.25437 v1 pith:HEP7UULY submitted 2026-07-28 cs.SE quant-ph

Vincent Gierisch , Nicole Hoess , Ralf Ramsauer , Wolfgang Mauerer This is my paper · ORCID

classification cs.SEquant-ph

keywords QuantumsoftwareengineeringMiningrepositoriesecosystemsContributoranalysisKnowledgetransferDevelopermigrationcompilersOpen-source

verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

The paper asks whether the ideas encoded in quantum-software repositories outlive the repositories themselves. By tracking contributor activity across sixteen foundational quantum-computing projects, it finds that developers from short-lived research prototypes often reappear later in large, industry-backed frameworks such as CUDA-Q and Catalyst. The authors read this pattern as evidence of developer-mediated knowledge transfer: even after a repository stops receiving commits, its concepts can persist by moving, through the same people, into projects that keep developing. The finding matters because much quantum software starts in academia and remains active for only a short time; if its ideas did not migrate, the field's early investments would be lost.

What carries the argument

The central mechanism is developer-mediated knowledge transfer, operationalised through a merged contributor identity: the same developer recognised in multiple repositories by matching full name and email, email, GitHub username, or exact name. The paper links these identities to every project they contributed to, builds an ecosystem network of contributors and projects, and computes both structural metrics (core vs. peripheral developers, exclusive vs. cross-project developers) and temporal sequences of monthly commits. The temporal ordering is what converts a static overlap into a directional claim about knowledge moving from earlier, smaller projects to later, larger ones.

What would settle it

Inspect the commit histories of the three commits the paper manually verified (catalyst a93629f, qcor 28a61e4, cuda-q da88cb5) and of other overlapping-contributor commits: if none of the later commits reuse or adapt concepts, code, or design elements from the earlier project, and if every overlap is fully explained by a shared employer, the knowledge-transfer interpretation loses its empirical support.

Watch

Extended reading notes

Core claim

The paper's central observation is that repository activity alone does not reflect a project's continued influence in the quantum software ecosystem. Using identity-merged contributor graphs, it shows that repositories with short active lifetimes—such as the research prototypes QIRO, XACC, and QCOR—are connected to sustained industry frameworks through the subsequent commits of their own developers. The temporal order of those commits (earlier in the research project, later in the larger project) supports the interpretation that know-how, for example about intermediate representations, was carried across repository boundaries. The authors thereby establish an empirical baseline for a phenome

Load-bearing premise

The claim rests on treating co-membership of the same merged developer identity in two repositories, combined with the temporal order of their commits, as sufficient evidence that knowledge from the earlier project was actually transferred to the later one.

Editorial extensions

If this is right

Inactive repositories can still exert long-term influence when their contributors join active frameworks, so repository activity is an incomplete proxy for impact.
Quantum software development follows at least three distinct paths: sustained community growth, concept integration into an established ecosystem, and continuation in a follow-up project.
Shared institutional origins explain many of the strongest cross-project contributor overlaps, suggesting that existing collaborations are a primary channel for knowledge transfer.
Publishing code and reproduction packages alongside papers appears to increase the chance that research concepts are absorbed into sustained frameworks.
The ecosystem shows no fully isolated project; every repository has at least some cross-project contributors, which means potential knowledge channels exist everywhere.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

A natural extension would be to weight the inferred knowledge flow by commit content similarity, not just identity overlap, to measure how much actual code or design is carried over rather than merely people changing jobs.
The same identity-tracking methodology could be applied to other emerging software ecosystems whose research artefacts are short-lived, and would likely reveal whether the migration pattern is peculiar to quantum computing or general.
If the author's interpretation is right, research funders could treat contributor migration to industrial frameworks as an early, low-cost signal of research impact that complements citation counts.
A follow-up interview-based study—which the paper itself suggests—could test whether the developers themselves perceive a conceptual transfer, or whether the observed overlaps are coincidental.

Share X Bluesky LinkedIn Reddit HN

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Desk Editor's Note

read the letter

Dear colleague,

This is a solid, transparent exploratory study that does something new for quantum software engineering: it takes 16 foundational compilation-focused repositories and links them through shared contributors, then looks at the temporal order of contributions to find migration patterns. That cross-repository view is the actual contribution; prior work mostly analyzed isolated repositories. They also ship a reproduction package, which is real evidence and the right habit for this subfield.

What I like: the methodology is standard MSR, applied carefully. They filter bots, merge identities with stated criteria, and manually sanity-check. The claims are mostly hedged as "indications" and "patterns," not proof. The examples (XACC/QCOR to CUDA-Q; QIRO to Catalyst) are plausible, and the paper explicitly acknowledges that commit activity alone misses other channels. They also give a clear follow-up direction: interviews.

The soft spots are real but not fatal. The strongest claim—that repository activity alone doesn't capture continued influence, and concepts persist across boundaries—rests on contributor overlap as a proxy for knowledge transfer. Overlap plus temporal order could be generic skill transfer, job rotation, shared institutional affiliation, or coincidental interest. The identity-merging step uses exact name as a sufficient criterion, which risks over-merging common names; the manual sanity check is not quantified, so we can't see how often that happened. And the content-level evidence is only three manually inspected commits (footnote 3), which is thin for the general claim. The stress-test note has it about right: if over-merging or skill-based overlap accounts for a big share of the links, the claim weakens to "people sometimes work on more than one project." But the paper already frames these as indications, and the authors flag the limitation themselves in Section IV. So I wouldn't call it a load-bearing flaw; I'd call it an exploratory study whose inference is weaker than its strongest phrasing.

My bottom line: worth peer review. A good referee would ask for a quantified sanity check on identity merging, a larger or more systematic repository census, and content-level evidence on a bigger sample than three commits. The paper is honest enough to accept those revisions. It's not a paradigm shift, but it's a useful first measurement for a young subfield, and the reproduction package makes it a decent baseline for follow-ups. I'd bring it to reading group as an example of how to do a transparent, hedged empirical study, and I'd cite it if I were working on quantum software ecosystems.

Recommendation: send to peer review, conditional on the identity-merging sanity check being quantified and the knowledge-transfer claim being kept suitably provisional.

Referee Report

3 major / 3 minor

Summary. The paper reports an exploratory empirical study of 17 foundational quantum software repositories, combining repository activity (commits from git via Perceval) with contributor relationships to study cross-project continuity. It constructs an ecosystem network (Fig. 2, Table I) and a temporal view (Fig. 3), and interprets observed contributor overlap between short-lived research projects and sustained industry ecosystems (e.g., XACC/QCOR to CUDA-Q; QIRO to Catalyst/PennyLane) as evidence of knowledge transfer and concept persistence across repository boundaries. The authors explicitly frame the study as exploratory, provide a reproduction package, and discuss threats to validity, but the central inference rests on contributor co-membership and temporal ordering rather than on direct content-level evidence.

Significance. If the central claim is supported, the paper would be a useful contribution to the emerging area of quantum software engineering and to MSR studies of cross-project knowledge flow in a niche ecosystem. The strengths are the self-contained reproduction package, the use of established MSR tools, the clear description of the pipeline, and the appropriately hedged language in several places. However, the headline contribution—that repository inactivity does not imply disappearing influence and that concepts persist via contributor migration—depends on an evidential chain that is currently too weak to carry the conclusion. The paper is therefore more a descriptive network study with candidate hypotheses than a confirmed account of knowledge transfer. Addressing the identity-matching threat and adding a quantitative baseline or systematic content-level validation would materially improve the paper; without such changes, the central claim remains plausible but not well supported.

major comments (3)

[Section II.c (identity matching)] The identity-consolidation step merges contributors if they share any of: full name plus e-mail, e-mail address, GitHub username, or exact name. The 'exact name' criterion alone can merge distinct individuals with common names, creating spurious cross-project links. This directly affects Table I's Cross-Project Dev. Ratio and the network in Fig. 2, which are the primary evidence for migration and knowledge transfer. The manuscript says the matches were 'manually sanity-checked' but does not quantify how many matches were checked, how many were rejected, or the precision/recall of the merge procedure. Please report the number of merges per criterion, validate exact-name matches with additional signals (e.g., e-mail domain, commit time overlap, or GitHub activity), and give a quantitative estimate of the false-merge rate.
[Section III.b / Fig. 3 / footnote 3] The claim that 'repository activity alone does not fully capture the continued influence of research-driven quantum software artefacts' and that know-how moves across repositories is supported only by temporal overlap of merged contributor identities. Overlap is consistent with generic skill transfer, institutional job rotation, shared affiliations, or coincidental participation in a small community; it does not demonstrate that specific concepts (e.g., intermediate representations) moved. The only content-level evidence is the manual inspection of three commits (catalyst a93629f, qcor 28a61e4, cuda-q da88cb5). Three commits are far too few to support the paper's generalization to 'multiple development paths' across the ecosystem described in Section IV. Please either systematically sample and classify a larger set of commits/issues/PRs for conceptual content, use code-similarity or docu
[Section III.a / Table I / Fig. 2] The analysis lacks a quantitative baseline or null model. The selected projects are all quantum compiler related and several share institutional origins (XACC/QCOR, Catalyst/PennyLane, Qiskit/Qiskit-QIR), so some overlap is expected by construction. Without comparing the observed cross-project overlap to a randomized null model (e.g., a permutation test that preserves contributor counts and project sizes) or to a control set of less-related repositories, the statement that 'no project forms an entirely isolated community' is difficult to interpret as evidence of knowledge transfer. Adding such a baseline would strengthen the claim that the observed connectivity is non-trivial.

minor comments (3)

[General] There are minor typographical issues, e.g., 'Index T erms' in the header, inconsistent capitalization of project names (cuda-q vs CUDA-Q), and inconsistent use of 'e-mail' and 'email'.
[Section III.b / Fig. 3] The choice of the top 20% of contributors for highlighting in Fig. 3 is not justified; please state that this is an arbitrary visualization cut and mention its rationale, or use a more principled threshold.
[Section IV] The transition to 'actionable guidelines [13], [14]' is abrupt; a brief explanation of how those guidelines relate to the findings would help readers see the practical implication.

Circularity Check

0 steps flagged · score 0.0 of 10

No significant circularity: the central claim is an observational MSR analysis; self-citations are non-load-bearing and the acknowledged construct-validity limits are not definitional loops.

full rationale

The paper's derivation chain is self-contained: it extracts commit histories from 16 repositories via perceval, merges contributor identities, constructs ecosystem and temporal networks, and reports migration patterns. The central claim—contributor migration and indications of cross-project knowledge transfer—is directly based on these measured data, not on a parameter fitted to the conclusion. Thresholds such as the 80% core-developer cut and top-20% contributor highlight are descriptive analysis choices, not fitting-to-target. The only self-citations are to established MSR/network methodology (Joblin et al. [1],[3],[18]), to a long-term sustainability study (Ramsauer et al. [4]), to reproducibility guidelines in the discussion (Mauerer et al. [13],[14]), and to a known-threats paper (Hoess et al. [20]); none of these supplies the paper's empirical conclusion or forbids alternative explanations. The possible weakness—that co-membership plus temporal order is only indirect evidence of knowledge transfer—is explicitly acknowledged in Section IV ('we detect knowledge flows from commit activity without other channels') and is a construct-validity threat, not circularity. The manual checks of three commits are evidence, and their small number is a limitation, not a circular step. Therefore no prediction or result reduces to its inputs by construction.

Assumptions & free parameters 3 free parameters · 4 assumptions · 0 invented entities

No numerical parameters are fitted to achieve a target result. The analysis depends on methodological choices (thresholds, identity merging, main-branch commit proxy) and on the interpretive premise that contributor co-membership signals knowledge transfer. These choices are made transparently in Section II.

free parameters (3)

Core developer threshold (80% of commits) = 0.80
Chosen by hand to split core vs peripheral developers; shapes Table I metrics and Fig. 2 node scaling, but is not central to the migration claims.
Fig. 3 highlighted contributor threshold (top 20%) = top 20% (24 of 118 cross-project contributors)
Visual emphasis threshold for tracing cross-project contributors; arbitrary and affects readability rather than statistical conclusions.
Cross-project developer definition (active in > 1 project) = binary split at 1 project vs >1 project
Determines the exclusive/cross-project developer ratios reported in Table I; no alternative thresholds are tested, so the quantitative ratios are sensitive to this modelling choice.

assumptions (4)

domain assumption A developer active in more than one project mediates knowledge transfer between those projects.
Methodology Section II states the premise of developer-mediated knowledge transfer; used to interpret contributor overlap as knowledge flow. The paper acknowledges it cannot capture other channels (Section IV).
domain assumption Commit activity on a project's main branch, after bot and merge-commit filtering, is a valid proxy for development activity.
Section II-b extracts commits via Perceval, filters main branch, bots, and merge commits; no validation against other activity measures is provided.
domain assumption Merging contributor identities by exact name, e-mail, username, or exact name produces correct cross-repository identity matches.
Section II-c merges authors/committers with manual sanity checks; false splits or merges would distort network links and migration evidence.
domain assumption The 16 selected projects constitute a representative set of foundational quantum compilation software.
Section II-a selects repositories 'based on expert knowledge' rather than a systematic census; the network structure may not generalize to all quantum software.

how reviews work

0 comments

Cite this review

Pith. "Pith review of Repositories, Contributors, and Continuity: An Empirical Study of Foundational Quantum Software." pith.science (2026). https://pith.science/paper/HEP7UULY

@misc{pith2026260725437,
  author       = {Pith},
  title        = {Pith review of: Repositories, Contributors, and Continuity: An Empirical Study of Foundational Quantum Software},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/HEP7UULY}},
  note         = {Machine review of arXiv:2607.25437}
}

read the original abstract

Driven by contributions from academia, industry, and open-source communities, the quantum software ecosystem is rapidly growing. Across this ecosystem, new concepts often emerge through software artefacts accompanying scientific publications as well as through sustained development in larger communities. However, many repositories receive development efforts only over a limited period of time, raising the question whether their concepts persist beyond individual repositories. In this paper, we apply established empirical software engineering techniques to analyse a set of foundational quantum software repositories. We combine cross-repository activity with contributor relationships to study the evolution of communities. Our analysis provides empirical evidence of contributor migration patterns and indications of cross-project knowledge transfer. We observe multiple development paths: projects may evolve into sustained communities, contributors may integrate concepts into established ecosystems, or activity may continue through new and follow-up software artefacts. Our observations provide an initial empirical perspective on how concepts and influence persist across repository boundaries in quantum software ecosystems.

Figures

Figures reproduced from arXiv: 2607.25437 by the authors.

**Figure 1.** Overview of the analysis workflow. We first relate quantum software repositories to associated publications and derive repository-level observations [PITH_FULL_IMAGE:figures/full_fig_p002_1.png] view at source ↗

**Figure 2.** Overview of the quantum software ecosystem with projects (grey [PITH_FULL_IMAGE:figures/full_fig_p002_2.png] view at source ↗

**Figure 3.** Contribution activity over time. Violins show the overall commit distribution per project. Coloured points mark the top 20% (24 of 118 cross-project) [PITH_FULL_IMAGE:figures/full_fig_p003_3.png] view at source ↗

Discussion (0). Continue with ORCID to comment.

Reference graph

Works this paper leans on

20 extracted references · 2 linked inside Pith

[1]

Joblin, S

M. Joblin, S. Apel, and W. Mauerer, Evolutionary trends of developer coordination: a network approach,EMSE, 2017

2017
[2]

A. Ait, J. L. C. Izquierdo, and J. Cabot, An empirical study on the survival rate of GitHub projects,MSR, 2022

2022
[3]

Joblin et al., From Developer Networks to Verified Communities: A Fine-Grained Approach,ICSE, 2015

M. Joblin et al., From Developer Networks to Verified Communities: A Fine-Grained Approach,ICSE, 2015

2015
[4]

Ramsauer, D

R. Ramsauer, D. Lohmann, and W. Mauerer, The List is the Process: Reliable Pre-Integration Tracking of Commits on Mailing Lists,ICSE, 2019

2019
[5]

Hemmati et al., The MSR cookbook: Mining a decade of research,MSR, IEEE, 2013

H. Hemmati et al., The MSR cookbook: Mining a decade of research,MSR, IEEE, 2013

2013
[6]

J. M. Murillo et al., Quantum Software Engineering: Roadmap and Challenges Ahead,TOSEM, 2025

2025
[7]

Upadhyay et al., Analyzing the Evolution and Main- tenance of Quantum Software Repositories,QSW, 2025

K. Upadhyay et al., Analyzing the Evolution and Main- tenance of Quantum Software Repositories,QSW, 2025

2025
[8]

Ramalho et al., Mining Quantum Software Patterns in Open-Source Projects,arXiv:2601.06281, 2026

N. Ramalho et al., Mining Quantum Software Patterns in Open-Source Projects,arXiv:2601.06281, 2026

arXiv 2026

Show all 20 references

[9]

M. M. Yousuf and S. A. Sofi, Characterizing Bugs and Quality Attributes in Quantum Software: A Large-Scale Empirical Study,arXiv:2512.24656, 2025

2025
[10]

De Stefano et al., Quantum software engineering issues and challenges: Insights from practitioners,Quan- tum Software

M. De Stefano et al., Quantum software engineering issues and challenges: Insights from practitioners,Quan- tum Software. Springer, 2024

2024
[11]

A. A. Khan et al., Mining Q&A platforms for em- pirical evidence on quantum software programming, arXiv:2503.05240, 2025

2025 arXiv
[12]

McCaskey et al., Extending C++ for Heterogeneous Quantum-Classical Computing,TQC, 2021

A. McCaskey et al., Extending C++ for Heterogeneous Quantum-Classical Computing,TQC, 2021

2021
[13]

Mauerer, S

W. Mauerer, S. Klessinger, and S. Scherzinger, Beyond the badge: Reproducibility engineering as a lifetime skill, SEENG, 2022

2022
[14]

Mauerer and S

W. Mauerer and S. Scherzinger, 1-2-3 Reproducibility for Quantum Software Experiments,SANER, 2022

2022
[15]

Ma et al., How do developers fix cross-project correlated bugs? a case study on the GitHub scientific python ecosystem,ICSE, 2017

W. Ma et al., How do developers fix cross-project correlated bugs? a case study on the GitHub scientific python ecosystem,ICSE, 2017

2017
[16]

S. K. Behfar, E. Turkina, and T. Burger-Helmchen, Knowledge management in OSS communities: Relation- ship between dense and sparse network structures,IJIM, 2018

2018
[17]

Dueñas et al., Perceval: Software Project Data at Your Will,ICSE-Companion, 2018

S. Dueñas et al., Perceval: Software Project Data at Your Will,ICSE-Companion, 2018

2018
[18]

Joblin et al., Classifying Developers into Core and Peripheral: An Empirical Study on Count and Network Metrics,ICSE, 2017

M. Joblin et al., Classifying Developers into Core and Peripheral: An Empirical Study on Count and Network Metrics,ICSE, 2017

2017
[19]

A. J. McCaskey et al., XACC: A System-Level Software Infrastructure for Heterogeneous Quantum-Classical Computing,arXiv:1911.02452, 2019

1911 arXiv
[20]

Hoess et al., Does the Tool Matter? Exploring Some Causes of Threats to Validity in Mining Software Repositories,SANER, 2025

N. Hoess et al., Does the Tool Matter? Exploring Some Causes of Threats to Validity in Mining Software Repositories,SANER, 2025

2025

Pith tools

Reviewed August 1, 2026 · model on record in the stance chip above.

[1] [1]

Joblin, S

M. Joblin, S. Apel, and W. Mauerer, Evolutionary trends of developer coordination: a network approach,EMSE, 2017

2017

[2] [2]

A. Ait, J. L. C. Izquierdo, and J. Cabot, An empirical study on the survival rate of GitHub projects,MSR, 2022

2022

[3] [3]

Joblin et al., From Developer Networks to Verified Communities: A Fine-Grained Approach,ICSE, 2015

M. Joblin et al., From Developer Networks to Verified Communities: A Fine-Grained Approach,ICSE, 2015

2015

[4] [4]

Ramsauer, D

R. Ramsauer, D. Lohmann, and W. Mauerer, The List is the Process: Reliable Pre-Integration Tracking of Commits on Mailing Lists,ICSE, 2019

2019

[5] [5]

Hemmati et al., The MSR cookbook: Mining a decade of research,MSR, IEEE, 2013

H. Hemmati et al., The MSR cookbook: Mining a decade of research,MSR, IEEE, 2013

2013

[6] [6]

J. M. Murillo et al., Quantum Software Engineering: Roadmap and Challenges Ahead,TOSEM, 2025

2025

[7] [7]

Upadhyay et al., Analyzing the Evolution and Main- tenance of Quantum Software Repositories,QSW, 2025

K. Upadhyay et al., Analyzing the Evolution and Main- tenance of Quantum Software Repositories,QSW, 2025

2025

[8] [8]

Ramalho et al., Mining Quantum Software Patterns in Open-Source Projects,arXiv:2601.06281, 2026

N. Ramalho et al., Mining Quantum Software Patterns in Open-Source Projects,arXiv:2601.06281, 2026

arXiv 2026