Repository: iterative/dvc

Issue:
zenodo
Zenodo (https://zenodo.org/) can archive datasets and software, providing unique DOIs per-version as well as one DOI for all versions (e.g. https://doi.org/10.5281/zenodo.595120). Uploading can be automated (github releases automatically triggers a new DOI). It's a nice first step for people to cite `dvc`.

Things to discuss:

- author list (contributors/company name/etc). If left blank, GitHub contributors are automatically used.
  + `creators`
  + `contributors`
zenodo
Zenodo (https://zenodo.org/) can archive datasets and software, providing unique DOIs per-version as well as one DOI for all versions (e.g. https://doi.org/10.5281/zenodo.595120). Uploading can be automated (github releases automatically triggers a new DOI). It's a nice first step for people to cite `dvc`.

Things to discuss:

- author list (contributors/company name/etc). If left blank, GitHub contributors are automatically used.
  + `creators`
  + `contributors`


Discussion:
@casperdcl It would be great if you could elaborate on what this is about. I don't think many of us are familiar with zenodo 🙂 
Well it's nice to have a DOI for people to cite `dvc`, and Zenodo can issue DOIs. This I think is its main relevance for software packages.

e.g. badges: [![](https://img.shields.io/badge/DOI-10.5281/zenodo.012345-blue.svg)](https://doi.org/10.5281/zenodo.012345) or a citation: "[1] iterative.ai, *dvc: Data Version Control - Git for Data & Models* (2019) [DOI:10.5281/zenodo.012345](https://doi.org/10.5281/zenodo.012345)" for people to use in papers & dependencies.

It won't require much set-up from our end.
@casperdcl it is a good idea. Several people (3?) have already asked how they can reference DVC in their papers. I was thinking about writing some paper and publish in arxiv.org but zenodo.org can be a temporary workaround.
@dmpetrov I'd recommend writing a paper *after* zenodo.
@casperdcl It would be great if you could elaborate on what this is about. I don't think many of us are familiar with zenodo 🙂 
Well it's nice to have a DOI for people to cite `dvc`, and Zenodo can issue DOIs. This I think is its main relevance for software packages.

e.g. badges: [![](https://img.shields.io/badge/DOI-10.5281/zenodo.012345-blue.svg)](https://doi.org/10.5281/zenodo.012345) or a citation: "[1] iterative.ai, *dvc: Data Version Control - Git for Data & Models* (2019) [DOI:10.5281/zenodo.012345](https://doi.org/10.5281/zenodo.012345)" for people to use in papers & dependencies.

It won't require much set-up from our end.
@casperdcl it is a good idea. Several people (3?) have already asked how they can reference DVC in their papers. I was thinking about writing some paper and publish in arxiv.org but zenodo.org can be a temporary workaround.
@dmpetrov I'd recommend writing a paper *after* zenodo.

Resolving patch:
diff --git a/setup.py b/setup.py
--- a/setup.py
+++ b/setup.py
@@ -148,7 +148,8 @@ def run(self):
         "hdfs": hdfs,
         "tests": tests_requirements,
     },
-    keywords="data science, data version control, machine learning",
+    keywords="data-science data-version-control machine-learning git"
+    " developer-tools reproducibility collaboration ai",
     python_requires=">=3.5",
     classifiers=[
         "Development Status :: 4 - Beta",


Test patch: