Lmst

#SoftwareHeritage

Yesterday @rougier and I gave an informal #ReproducibleResearch workshop at Inria with ~20 scientists, half of whom working in HPC, the rest of them working on user interfaces, computer graphics, number theory, and robotics—very insightful to see how each community approaches these issues.

@rougier had excellent examples to get the discussion started. I followed up on computational reproducibility with #HPC examples and a touch of #Guix and #SoftwareHeritage:
https://gitlab.inria.fr/lcourtes/atelier-recherche-reproductible

Blog post: What Guix could offer in computational medical environments?

French national agency for secure drug and medicine (ANSM) requires for a medical device to have unambiguous identifications:

1. reference of the product
2. reference of the maker
3. serial number

Well, through my lenses applied to software, it reads:

1. #SoftwareHeritage identifier (#SWHID)
2. #Guix

and 3. is redundant. 😁

Well, a quick summary of a 30min talk I gave past week.

Thanks my previous colleague Sam from APHP to give me the opportunity to brainstorm on this topic. 🤩

https://simon.tournier.info/posts/2025-06-04-aphp-guix.html

#ReproducibleResearch #OpenScience #Debian #ReproducibleBuilds

Si vous êtes chercheur.se à l'Université de Rennes / Rennes 2 ou dans des écoles de l'EPE, l'atelier ARDoISE peut vous accompagner lors d'une éventuelle candidature au prix SO du logiciel libre de recherche #FAIR #replicability #SoftwareHeritage #HAL https://scienceouverte.univ-rennes.fr/ardoise-atelier-rennais-de-la-donnee https://www.ouvrirlascience.fr/les-candidatures-pour-le-prix-science-ouverte-du-logiciel-libre-de-recherche-2025-sont-ouvertes/

Do you have a sensitive package you cannot live without, built on a codebase or tarball ?

Double check there is a backup available at #softwareheritage

https://archive.softwareheritage.org

#Guix will fall back to using it in case the upstream code or tarball just vanishes. And it happens (gnat-x86_64-linux-15.1.0-1.tar.gz, looking at you ... ).

Also possible with tarballs.nixos.org and web.archive.org.

#guixtips

Journée de lancement de la collaboration UNESCO institut coréen de l'information. Software heritage en guest star ! #softwareheritage On y parle de données et de codes sources ouvert, d'accès pour tous, de biens communs, de solidarité et de durabilité. On coche presque toutes les cases que je défend depuis des décennies. Tout avance, c'est bien, mais il faut de l'énergie... Et tout n'est pas rose, les éditeurs scientifiques font de la résistance "financière"...

Asking for news from a colleague now in Univ. of Tours – long time, no see.

Nicolas pointed me a recent publication where… guess what? … they archived the source code in #SoftwareHeritage.

https://pubmed.ncbi.nlm.nih.gov/39487603/

Section « Open Research, data availability statement » reads:

« Anonymized raw data, the source code of the analyses, instructions to reproduce the computing environment, unformatted analysis reports and figures are available online (https://gitlab.com/nivall/car-lacates) and long term preserved at Software Heritage (https://archive.softwareheritage.org/swh:1:dir:a5c9b94421a6b5d6d0ab89e4aee752b540e7364f). »

And guess what else? The computational environment is managed using #Guix.

It makes my day! 😎

I’m happy to see #Guix and #SoftwarHeritage mentioned in the European Journal Of Clinical Investigation.

#ReproducibleResearch #OpenScience #EuropeanJournalOfClinicalInvestigation

Le catalogue des #LogicielsLibres de l'#ESR est disponible depuis mi-avril en version bêta 👉 https://logiciels.catalogue-esr.fr/

🔅 Une belle façon de mettre en lumière les logiciels développés dans la recherche académique française ! 🔆

💡 Pour que votre logiciel soit référencé dans ce catalogue : archivez votre code dans #SoftwareHeritage et déposez-le dans #HAL !

@ouvrirlascience #OpenSource #ResearchSoftware #ScienceOuverte

« The integration of #Guix and #SoftwareHeritage paves the way for more transparency and verification of the whole computational environment involved in scientific research.

Scientific production should be robust to external service failures; for example, being able to audit or reuse scientific findings should not depend on the availability of platforms hosting source code.

That’s why backing package managers with Software Heritage appears vitally important. »

Thanks @swheritage for the spotlight! 😀

https://www.softwareheritage.org/2025/05/21/software-heritage-guix-deployment/

#ReproducibleResearch #OpenScience

A pretty big piece of news came in last week. #SWHID , a identifier and referencing scheme for software source devised by our friends at #SoftwareHeritage is now an ISO standard! https://www.iso.org/standard/89985.html . If you need to cite software, you know how to do so now.

Et en plus ces identifiants #SWHID sont maintenant une norme ISO. Plus d’excuse ! 😉

https://www.iso.org/standard/89985.html

#ReproducibleResearch #OpenScience #Softwareheritage

3/3

#SoftwareHeritage ouvre un chemin…

Hop! Allez on utilise collectivement des identifiants intrinsèques dans nos papiers de recherche. Qu’est-ce que c’est ? Par exemple, petite explication là :

https://www.softwareheritage.org/2020/07/09/intrinsic-vs-extrinsic-identifiers

#ReproducibleResearch #OpenScience

2/3

« Réfléchissons collectivement à la lourde tâche d'archivage de certains savoirs spécifiques. Je pense aux travaux aussi de #SoftwareHeritage, qui, en France, archive l'ensemble des logiciels créés dans le monde, avec une initiative européenne à construire sur le sujet. Je souhaite, au-delà de la question de notre capacité, à attirer chercheurs, enseignants-chercheurs, que nous ayons aussi une capacité à préserver, consolider, attirer plateformes de collaboration et données au service de l'intérêt général. »

Bravo @swheritage !

(peu importe ce qu’il y a avant et après ce petit passage 😀)

https://www.elysee.fr/emmanuel-macron/2025/05/05/lancement-de-choose-europe-for-science-a-la-sorbonne

#ReproducibleResearch #OpenScience

1/3

#softwareheritage #gdpr request:

I came across your project and my accounts have been archived by Software Heritage.

According to $17 GDPR (https://gdpr-info.eu/art-17-gdpr) I ask for the deletion of all links referring to my GitHub accounts (and the other data sources listed below). I also ask to block my accounts and data sources (repositories) from being archived ($21 GDPR | right to object https://www.privacy-regulation.eu/en/article-21-right-to-object-GDPR.html).

Huh, I must've missed the announcement.

@swheritage is now providing citation metadata to download as #BibTeX and use via #BibLaTeX (biblatex-software) for archived software with a CITATION.cff file or codemeta.json in the root directory! 🎉

Very cool!

#CitationFileFormat #SoftwareHeritage #ResearchSoftware #SoftwareCitation

@kirschwipfel@nerdculture.de

In fact, the two groups overlaps more often that not: if you look, say, at the sponsors of most of the organizations that signed the infamous "RMS open letter" you'll find #Microsoft, #Google, #Meta, #Amazon, #IBM and so forth...

Like it or not, if you take their money, you serve their goals.

Compare, for example, #FSF sponsors with #FSFE (!) or #SoftwareHeritage (that in turn is a sponsor of #Guix), to get an idea of why groups that pretend to advance #FreeSoftware did (and do) their best to destroy the #GNU project.

@ekaitz_zarraga@mastodon.social

@ekaitz_zarraga@mastodon.social

Indeed if you were leading #Guix, I'd likely be a user and contributor (I think you know I have the technical skills required).

And I also know other people working there, people I respect despite not being always aligned with their opinion (for example I had a long debate with a friend that work on Guix a few months ago about the right to be mentioned with the preferred name by a transitioned trans developer whose code was archived with their dead-name and #SoftwareHeritage was refusing to update. I think hackers have the right to be named as they wish in their works and no script, tool or hash chain matter more than this right).

Yet there's a huge difference between a technical or even philosophical argument and a (politically motivated) personal attack in form of a shitstorm.

Courtès might even be the best #scheme hacker out there, with a solid architectural vision of how to make #linux more reliable.

But I chose free software for political goals that he actively damaged with that attack to RMS.