Would you consider creating a release and archiving it at Zenodo so this project can have a DOI? The limitation is that the DOI would reference only a snapshot of the project, but anyone going to the Zenodo page for the project would see the GitHub url and perhaps a README file that informs them that the project is ongoing and the list is growing continuously. I did this for my list of archaeology papers that include R code (https://github.com/benmarwick/ctv-archaeology/blob/master/README.md) because someone wanted to cite it. And now I'm part of a group that want to cite this project in a paper we're drafting. A DOI would make the citation more robust to any changes here at GitHub
Would you consider creating a release and archiving it at Zenodo so this project can have a DOI? The limitation is that the DOI would reference only a snapshot of the project, but anyone going to the Zenodo page for the project would see the GitHub url and perhaps a README file that informs them that the project is ongoing and the list is growing continuously. I did this for my list of archaeology papers that include R code (https://github.com/benmarwick/ctv-archaeology/blob/master/README.md) because someone wanted to cite it. And now I'm part of a group that want to cite this project in a paper we're drafting. A DOI would make the citation more robust to any changes here at GitHub