Create CITATION.md
State: closed

Addresses #24036 by adding a `CITATION.md` file to the repository.

I copied the citation instructions from here: https://pandas.io/about/citing.html
and added a section for the published software on Zenodo. Following [this recommendation](https://github.com/sherpa/sherpa/pull/634#issuecomment-553668211), I did this for the latest released version (v1.0.1) with a note for the user to go fetch the citation from Zenodo for the version they are actually using.

Tagging @TomAugspurger and @jreback since you were active in the linked issue.

I still recommend to update the citation request on the pandas website directly (https://pandas.io/about/citing.html), as well as on the Scipy website (https://www.scipy.org/citing.html#pandas), on https://pandas.pydata.org/ and maybe provide a `<package>.__citation__` variable as suggested [here](https://github.com/pandas-dev/pandas/issues/24036#issuecomment-585672595).


Labels:
name: Docs

Comments:
> Is `CITATION.md` a standard place for this information?

Yes, the format doesn't matter, but authors will look for either citation instructions on a website or a `CITATION` file on the repository. The format doesn't matter (I just find markdown more neat than a plain text file). STScI has released a recommended style-guide for software releases based on what the community usually uses, and it [recommends including a CITATION file.](https://github.com/spacetelescope/style-guides/blob/master/guides/software-versioning.md#citing-software)
I don't see numpy, scipy or matplotlib implementing a `CITATION.md` file, and they are much more academic than us. I'd update the website and avoid duplication if this is not a standard in the scientific Python world.
The point is to make it easy for anyone searching for information how to cite it properly. There doesn't seem to be a standard yet; adding this information to the Readme would also do the trick.
I fully agree with @JoKeyser. This is not a standard **yet**, and yes adding it to the readme would do the same trick. The fact that numpy, Scipy et al. don't have something like this is annoying to problematic, rather than leading the way.
I don't think adding a `CITATION.md` file in pandas is going to create a standard. And I don't think it's great having to maintain two copies of the same information.

There is a link "Citing pandas" in the navigation bar of the website. If you want to add a comment in the `README` linking to that page, since people may go to the GitHub and not the website to look for it, that sounds good. And if you want to improve the citation page, that's also welcome.

We can surely discuss it again if other projects are happy to adopt this as a standard, but I think at this stage this adds little value, and gives us extra work of maintaining duplicate information, and adds even more noise to our root directory.
The whole point of this is not actually to create a `CITATION` file but to update the citation instructions in general because there is no mention at all about the actual software citation. Adding that information into the `README` works just as well, but the website definitely needs to get updated.

And you're right, pandas adding a `CITATION` file wouldn't set a standard - it would make it follow it. And yes, it would not be necessary if the existing places were up to date.
Ok, that sounds good. Closing this, feel free to open a PR to update the existing citing page https://pandas.pydata.org/about/citing.html

Thanks!