-
Notifications
You must be signed in to change notification settings - Fork 35
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 issue metadata for all reviews #109
Comments
Notes while doing this:
|
Thank you for your work on this david!! a few other notes for whomever takes this on at another time!
And then i'm pulling from david's list above:
|
Just an update on this issue: everything was unchecked to start from the beginning again with the updated metadata to include JOSS DOI. Everything that has been re-checked off will have the exact format of
and if anything is missing, I've been marking with N/A (including the slash). |
I have removed the label as the all the packages have been checked: we just need to decide how to communicate about Nbless |
@cmarmo so sorry i missed this. i'll open an issue about nbless separately in our website repo. we created an archive package procedure in our software peer review guide (but rright now the navigation is broken so i need to fix that to get the link!) but essentially no author response after a year and no commit history means we archive it. i'll add a flag to the submission issue and then i'll also update the website (so i'll go ahead and make that website issue now). then we can close this issue. i really appreciate all of the work you did and @isabelizimm did on cleaning up our package submission history. many many thanks! |
ok closing this via this issue |
All of our new software submission issues have metadata that look like this:
but older issues have something like this:
We need to go through older issues and update metadata
For all issues we need to add:
JOSS DOI:
For all those older issues, we should add the following two things (some issues may have this already given Davids work):
The text was updated successfully, but these errors were encountered: