-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CITATION.cff file #3723
Add CITATION.cff file #3723
Conversation
Thanks for the PR! We can steal what's in the footer of the documentation:
And I'd discourage maintaining a copy of the version number in the citation file. I recognize it may be helpful for citers, but it would introduce more friction during releases (which I'd like to avoid). A changelog entry isn't necessary here, but it would be nice either way. Putting it under |
I think I'd actually prefer a changelog entry, as presumably we want users to know about this. We should omit a changelog entry only if users don't need to know about the change. |
I have updated the authorship information and the changelog. Hopefully the authorship information looks okay. If not, I can change it to a single author with the literal string "Łukasz Langa and contributors to Black" instead of divided into 2 author fields. Regarding version number, I agree, it is much more friction. Also, while version number is important, most citation styles don't include version numbers anyway. So if a user wants to be explicit, they can include that information manually, usually directly in the text. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks!
I see Linting is failing. The message looks like it is making the changes itself, is that correct? Or do I need to make the changes it suggests and commit them? |
You need to commit the changes. |
Description
This pull request adds a CITATION.cff file to the root of the repository. This resolves #3722 and follows GitHub's recommendation.
It will achieve several things:
Hopefully, this will make it easier to give due credit to Black!
Further considerations
What metadata to include in this file is subjective, and up to the Black development team. Here are a few considerations. Most are tradeoffs between accuracy and increased maintenance:
Checklist - did you ...
CHANGES.md
if necessary?I don't believe that anything needs to be added to
CHANGES.md
. Maybe it could be added to the Documentation section?