Skip to content
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

Update package info in package.yml file to support new website view. #102

Closed
lwasser opened this issue Oct 17, 2022 · 3 comments
Closed

Comments

@lwasser
Copy link
Member

lwasser commented Oct 17, 2022

Currently this issue has been opened as i noticed many review headers are missing final information AND i added a few more items to the template. Right now it just skips info that the site doesn't have like a missing DOI but would be good if maintainers, or reviewers and editors who reviewed the package could update their packages info.

Screen Shot 2022-10-17 at 3 14 18 PM

So we need to update headers there but then we need to add some info to our repo here in the _data dir including

  • DOI
  • documentation link
  • Github link (make sure it's current - pandera was dated)
  • Date accepted
  • Version accepted
  • List of maintainers (We want all maintainers listed)

https://github.com/pyOpenSci/pyopensci.github.io/blob/main/_data/packages.yml

Really this should be a database kept item but for now we can continue to use yaml. ultimately i thijnk database is best and we can have a build that pulls from the DB and converts to yaml maybe as a cron job?

@lwasser
Copy link
Member Author

lwasser commented Oct 17, 2022

Thinking about this more, it might be better to somehow parse the DB into .md files vs having a growing yaml list that will get super long at some point... need to think this through and potentially work on this in phases to consider growth.

@lwasser
Copy link
Member Author

lwasser commented Jul 3, 2023

this might be largely done - pyOpenSci/software-submission#109 but we need to reconcile both issues and see what else needs to be updated if anything.

each issue should have a DOI, documentation link, etc

@lwasser
Copy link
Member Author

lwasser commented Oct 26, 2023

ok this is done. i'll close. we will want to go back and update the cards with DOI information and whatever other metadata we want to surface but everything is in place that we need at this point!

@lwasser lwasser closed this as completed Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant