mirror of
https://github.com/foo-dogsquared/website.git
synced 2025-01-30 22:57:59 +00:00
64 lines
5.0 KiB
BibTeX
64 lines
5.0 KiB
BibTeX
@online{allanconSoftwareHeritageFilesystem2021a,
|
|
title = {The {{Software Heritage Filesystem}} ({{SwhFS}}): {{Integrating Source Code Archival}} with {{Development}}},
|
|
shorttitle = {The {{Software Heritage Filesystem}} ({{SwhFS}})},
|
|
author = {Allançon, Thibault and Pietri, Antoine and Zacchiroli, Stefano},
|
|
date = {2021-02-12},
|
|
eprint = {2102.06390},
|
|
eprinttype = {arxiv},
|
|
eprintclass = {cs},
|
|
url = {http://arxiv.org/abs/2102.06390},
|
|
urldate = {2023-04-28},
|
|
abstract = {We introduce the Software Heritage filesystem (SwhFS), a user-space filesystem that integrates large-scale open source software archival with development workflows. SwhFS provides a POSIX filesystem view of Software Heritage, the largest public archive of software source code and version control system (VCS) development history.Using SwhFS, developers can quickly "checkout" any of the 2 billion commits archived by Software Heritage, even after they disappear from their previous known location and without incurring the performance cost of repository cloning. SwhFS works across unrelated repositories and different VCS technologies. Other source code artifacts archived by Software Heritage-individual source code files and trees, releases, and branches-can also be accessed using common programming tools and custom scripts, as if they were locally available.A screencast of SwhFS is available online at dx.doi.org/10.5281/zenodo.4531411.},
|
|
pubstate = {preprint},
|
|
keywords = {Computer Science - Software Engineering},
|
|
file = {/home/foo-dogsquared/Zotero/storage/3ACWTS4G/Allançon et al. - 2021 - The Software Heritage Filesystem (SwhFS) Integrat.pdf;/home/foo-dogsquared/Zotero/storage/HM59NKPP/2102.html}
|
|
}
|
|
|
|
@inproceedings{cosmoIdentifiersDigitalObjects2018,
|
|
title = {Identifiers for {{Digital Objects}}: The {{Case}} of {{Software Source Code Preservation}}},
|
|
shorttitle = {Identifiers for {{Digital Objects}}},
|
|
author = {Cosmo, Roberto Di and Gruenpeter, Morane and Zacchiroli, Stefano},
|
|
date = {2018-09-24},
|
|
pages = {1},
|
|
doi = {10.17605/OSF.IO/KDE56},
|
|
url = {https://hal.science/hal-01865790},
|
|
urldate = {2023-04-28},
|
|
abstract = {In the very broad scope addressed by digital preservation initiatives, a special place belongs to the scientific and technical artifacts that we need to properly archive to enable scientific reproducibility. For these artifacts we need identifiers that are not only unique and persistent, but also support integrity in an intrinsic way. They must provide strong guarantees that the object denoted by a given identifier will always be the same, without relying on third parties and external administrative processes. In this article, we report on our quest for this identifiers for digital objects (IDOs), whose properties are different from, and complementary to, those of the various digital identifiers of objects (DIOs) that are in widespread use today. We argue that both kinds of identifiers are needed and present the framework for intrinsic persistent identifiers that we have adopted in Software Heritage for preserving billions of software artifacts.},
|
|
eventtitle = {{{iPRES}} 2018 - 15th {{International Conference}} on {{Digital Preservation}}},
|
|
langid = {english},
|
|
file = {/home/foo-dogsquared/Zotero/storage/46VTZINW/Cosmo et al. - 2018 - Identifiers for Digital Objects the Case of Softw.pdf}
|
|
}
|
|
|
|
@online{marponsAsciiDocProcessorPandoc,
|
|
title = {An {{AsciiDoc}} Processor and {{Pandoc}} Front-End in {{Haskell}}},
|
|
author = {Marpons, Gulliem},
|
|
url = {https://www.tweag.io/blog/2021-06-15-asciidoc-haskell-pandoc/null},
|
|
urldate = {2023-05-04},
|
|
abstract = {Announcing asciidoc-hs, a new AsciiDoc parser and converter in Haskell, adapted for use with Pandoc.},
|
|
langid = {english},
|
|
file = {/home/foo-dogsquared/Zotero/storage/CD9MC6JP/2021-06-15-asciidoc-haskell-pandoc.html}
|
|
}
|
|
|
|
@online{mtndewforbreakfastCombiningTraditionalDotfiles2023,
|
|
type = {Reddit Comment},
|
|
title = {Combining {{Traditional Dotfiles}} and {{NixOS Configurations}} with {{Nix Flakes}}},
|
|
author = {{mtndewforbreakfast}},
|
|
date = {2023-03-07T03:00:45},
|
|
url = {www.reddit.com/r/NixOS/comments/11kme1n/combining_traditional_dotfiles_and_nixos/jb80qgy/},
|
|
urldate = {2023-04-28},
|
|
organization = {{r/NixOS}},
|
|
annotation = {Post URL: www.reddit.com/r/NixOS/comments/11kme1n/combining\_traditional\_dotfiles\_and\_nixos/}
|
|
}
|
|
|
|
@video{softwareheritageTutorialCitingSoftware2020,
|
|
entrysubtype = {video},
|
|
title = {Tutorial: Citing Software Using Biblatex-Software},
|
|
shorttitle = {Tutorial},
|
|
editor = {{Software Heritage}},
|
|
editortype = {director},
|
|
date = {2020-07-07},
|
|
url = {https://www.youtube.com/watch?v=UhQCeAj9yKM},
|
|
urldate = {2023-04-28},
|
|
abstract = {This tutorial shows how one can cite software in research articles using the dedicate biblatex-software package available on CTAN as: https://www.ctan.org/tex-archive/macr... This style supports the Software Heritage Identifiers (SWHIDs) that allow to link citations directly to software source code in the Software Heritage archive.}
|
|
}
|