Hacker News Reader

I like that the DOI association is with a tagged release, making it easy to identify specific versions of the repository. In principle, this will make duplication/checking of research results easier, as one can ensure use of the same version of the software as the original work.

View on HN

Tags can be moved in Git. How much you want to trust the tags depends upon your use-case.

The DOI is linked to a zip archive on zendodo / figshare, which will not change, even if you change the tag.

So if you publish the DOI as a part of a paper, and then later improve the code in the Github repo (but of course not in the archived snapshot), is there some way that the people who follow the DOI could also find the improvements?

If you sign your tags with your GPG key, and only rely on tags signed by GPG keys that you trust, then you can trust the tag as much as you trust the holder of the key.

Reply on news.ycombinator.com