These are chat archives for cltk/cltk
the way I'd like to see it work is a DOI for each release AND overall project so you can cite either a release or the overall project
That would work for me, at least “significant” releases. I realize that’s a really subjective term, but presumably, if someone were to write a paper about, just for example, improvements in algorithms used in two later releases and you wanted to point to a persistent ID for each release, you’d want a DOI or ARK for each.
dev-requirements.txt… logic being that anyone building from source is what I'd consider a dev
gitattributesoptions can help, but I've never used them
git log); (b) tag versions (
git tagor through GitHub (what I do))