Building the universal archive of source code

Abramatic, J.; Cosmo, Roberto Di; Zacchiroli, Stefano

doi:10.1145/3183558

Cited by 49 publications

(59 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Software Heritage (SWH) was started in 2015 to collect, preserve and share the source code of all software ever written, together with its full development history [1]. As of today, it has already collected almost 6 billions unique source code files coming from over 85 million software origins that are regularly harvested.…”

Section: Reproducible Researchmentioning

confidence: 99%

Attributing and Referencing (Research) Software: Best Practices and Outlook From Inria

et al. 2020

View full text Add to dashboard Cite

Software is a fundamental pillar of modern scientific research, across all fields and disciplines. However, there is a lack of adequate means to cite and reference software due to the complexity of the problem in terms of authorship, roles and credits. This complexity is further increased when it is considered over the lifetime of a software that can span up to several decades. Building upon the internal experience of Inria, the French research institute for digital sciences, we provide in this paper a contribution to the ongoing efforts in order to develop proper guidelines and recommendations for software citation and reference. Namely, we recommend: (1) a richer taxonomy for software contributions with a qualitative scale; (2) to put humans at the heart of the evaluation; and (3) to distinguish citation from reference.

show abstract

Section: Reproducible Researchmentioning

confidence: 99%

Attributing and Referencing (Research) Software: Best Practices and Outlook From Inria

et al. 2020

View full text Add to dashboard Cite

show abstract

“…In this paper we describe an already operational system of identifiers that satisfies all these extra properties: high granularity, integrity, and no middleman. We argue that, when used in conjunction with the long-term archival provided by Software Heritage [2], such a system provides a suitable…”

Section: B References For Reuse and Reproducibilitymentioning

confidence: 99%

“…In order to develop an identifier system for billions of source code artifacts archived for the long-term in Software Heritage [2] we use a data model based on Merkle DAG (Direct Acyclic Graph) [3]. Nodes and edges are connected using hashing functions and represent the history of software development as captured by modern version control systems.…”

Section: Data Modelmentioning

confidence: 99%

“…We recall the schema of software source code identifiers that has been developed and deployed in the context of Software Heritage [2], a long term initiative aiming to collect, preserve, and share the entire body of software source code and its development history. We show that these identifiers are wellsuited for addressing the need of scientific reproducibility when source code is involved.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Referencing Source Code Artifacts: A Separate Concern in Software Citation

2020

Self Cite

View full text Add to dashboard Cite

Among the entities involved in software citation, software source code requires special attention, due to the role it plays in ensuring scientific reproducibility. To reference source code we need identifiers that are not only unique and persistent, but also support integrity checking intrinsically. Suitable identifiers must guarantee that denoted objects will always stay the same, without relying on external third parties and administrative processes.We analyze the role of identifiers for digital objects (IDOs), whose properties are different from, and complementary to, those of the various digital identifiers of objects (DIOs) that are today popular building blocks of software and data citation toolchains.We argue that both kinds of identifiers are needed and detail the syntax, semantics, and practical implementation of the persistent identifiers (PIDs) adopted by the Software Heritage project to reference billions of software source code artifacts such as source code files, directories, and commits.

show abstract

“…• technical solutions allowing creators of software to automatically publish releases of their software to a data repository, which provides a DOI and landing page for the software publication, e.g., the Zenodo repository automating archival of software releases on GitHub (guides.github.com/activities/citablecode/); • reliance on software archives harvesting open source code repositories, and providing unique identifiers for artifacts, e.g., Software Heritage [7].…”

Section: Challenges For the Retrieval Of Research Citation Graphsmentioning

confidence: 99%

Software and Dependencies in Research Citation Graphs

Druskat

2020

Comput. Sci. Eng.

View full text Add to dashboard Cite

Software is essential for a lot of research, but it is not featured in citation graphs which have the potential to assign credit for software contributions. This is due to a traditionalistic focus on textual research products. In this paper, I propose an updated model for citation graphs that include software. This model takes into account intrinsic properties of software, and requirements for a robust system of software citation. I also give an outlook on future work to implement transitive credit, which is at the core of a fair system of academic citation which accounts for software on par with other research products.

show abstract

Building the universal archive of source code

Abstract: A global collaborative project for the benefit of all.

Cited by 49 publications

References 3 publications

Attributing and Referencing (Research) Software: Best Practices and Outlook From Inria

Attributing and Referencing (Research) Software: Best Practices and Outlook From Inria

Referencing Source Code Artifacts: A Separate Concern in Software Citation

Software and Dependencies in Research Citation Graphs

Contact Info

Product

Resources

About