Apollo-11: Archive the Apollo-11 repo

[dbouquin]

It would be great to be able to cite this repo directly in papers. There is a version of a fork of this on Zenodo ("Apollo-11 v1") from about 3 years ago but there aren't any archived releases of the repo itself. There's a guide on how to archive the repo and mint a doi for it here. Willing to create an archived release?

[oldmud0]

Hi, thanks for reaching out!

Unfortunately, we are not sure at what point in time it would be appropriate to create a tag/release. The goal is to make the code here fall in line exactly with the GAP printouts, but we've still got a long way to go. @wopian what do you think?

As an alternative, perhaps it is possible to cite a specific commit hash?

[wopian]

The final checks of the Comanche055 digitisation is almost complete - we're only a few subroutines from having checked everything is 100% identical to the GAP printouts. Will tag a release when that's done, before moving on to do the same with Luminary099.

More info on goal of this repository: https://github.com/chrislgarry/Apollo-11/pull/403#issuecomment-512734261

[dbouquin]

Glad it's getting close. Until there's an archived release I'll just plan on using a commit hash. In the meantime it would be helpful if you just listed a preferred citation with the attribution info (or you could make a CITATION.cff file) just so it's clear whether or not there are specific people who should be listed as "authors".

[darthrodolfo]

AWESOME!!!!!!!!

[moranegg]

Hi @dbouquin,
This repository is archived on Software Heritage and you can use for a persistent identifier for the software source code artifact this identifier:
swh:1:snp:206c27c0c031c6aac6b5fedddba8fe082dea9836;origin=https://github.com/chrislgarry/Apollo-11 [[link](https://archive.softwareheritage.org/swh:1:snp:206c27c0c031c6aac6b5fedddba8fe082dea9836;origin=https://github.com/chrislgarry/Apollo-11/)]

This identifier identifies a snapshot, which means the complete state of the repository at the day of archival with all the branches and refs.
When there is a release, you can use the release identifier to identify the exact release (without all the other branches).
The usage of origin at the end of the identifier is to locate the provenance of the artifact, because the same artifact might be present in all the forks.

This identifier is appropriate to use to retrieve the source code from an archive instead of GitHub, but might not answer your problem on giving credit at the moment.

Also, I was surprised that the Apollo-11 software wasn't described on Wikidata.

This example could be a good test case for identifying a software.
If we create a page on Wikidata for the software concept the Qxxxx we can reference this repository and add a reference to the archived copy on the SWH archive.

This might be one proposition for identifying the Apollo-11 project and its source code artifact.

The credit aspect is might be complicated, because I imagine there have been many people working on this project on different time and it might not fit a standard CITATION file.