feat: add citation file #908
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| # This CITATION.cff file was generated with cffinit. | ||
| # Visit https://bit.ly/cffinit to generate yours today! | ||
|
|
||
| cff-version: 1.2.0 | ||
| title: pixi | ||
| message: >- | ||
| If pixi contributes to a project that leads to a | ||
| scientific publication, please acknowledge this fact by | ||
| citing according to this file. | ||
| type: software | ||
| authors: | ||
| - given-names: pixi open-source contributors | ||
|
There was a problem hiding this comment. While I understand the idea to want to give credit to everyone who contributed, I would recommend adding the names of people who have "responsibility" for There was a problem hiding this comment. Followed your advice! |
||
| repository-code: 'https://github.com/prefix-dev/pixi' | ||
ruben-arts marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| url: 'https://pixi.sh' | ||
ruben-arts marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| abstract: >- | ||
| A cross-platform, language agnostic, package/project management tool for | ||
| development in virtual environments. | ||
| keywords: | ||
| - package-management | ||
| - project-management | ||
| - virtual-environments | ||
| - conda | ||
| - pypi | ||
| - development-tools | ||
| license: BSD-3-Clause | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I haven't checked the codebase to see how you handle versioning release information, but I would add the
versionkey here too.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.
If you decide to incorporate the version here, please make a CI check that the version is synced with the one in
Cargo.toml, otherwise it will drift 100%.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.
More an "and" than an "or" but even if you only use VCS information for version information I would use some sort of version bump tool like
tbumpto try to go through and update information everywhere it exists.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.
I would love to automate this but I want to automate the complete release and add this part to it. I've been experimenting with
release-plzasrattleruses it but I haven't figure it out nicely yet. So in this PR I added the tbump as a preperation but it is not used in CI yet.Added the versions to the urls 👍