feat: add contributors to upstream #12
Conversation
These were taken from blogs, and should be extended as needed
|
Hi @agoose77, this looks great! We have a pretty detailed set of author metadata covering many past and present Pythia contributors in the CITATION.cff file for Pythia Foundations. Would it be useful to include the |
|
@brian-rose yes, as much information as you can handle. However, I think it would be really nice if these two had a single source of truth. I know that we can generate a cff export -- did you run into problems with that when you tried it? |
|
I'm not sure. I know that we settled on the CITATION.cff file a couple years back as the version of record for authorship for each repo because it is digested by both GitHub and Zenodo. |
+1 for this! There is a lot of repetition across the cookbook repos since many of the same individuals are attributed as authors across multiple works. |
|
I think it makes sense to go ahead with this now as a "proof of concept" for the blog posts in ProjectPythia/projectpythia.github.io#526. I have some thoughts and questions about the larger question of maintaining a single version of authorship data that can be reused in various ways across our many repos, including automated CITATION.cff generation. But none of that needs to be resolved before merging this and trying it out on the blog. |
|
I can see now that this is well documented: https://mystmd.org/guide/authorship#re-use-author-information-across-repositories-and-projects |
Use the
contributorsfield so that downstream we can refer to authors by their GitHub IDs.These were taken from blogs, and should be extended as needed with new authors and metadata.
@jukent @ktyle @clyne @brian-rose would you mind confirming that your ORCIDs are correct, and add any other metadata you're comfortable aggregating here. It will show up e.g. on blog posts that you're added to as an author or contributor.