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

Create archive process and then Archive nbless #320

Open
2 tasks
lwasser opened this issue Jan 17, 2024 · 1 comment
Open
2 tasks

Create archive process and then Archive nbless #320

lwasser opened this issue Jan 17, 2024 · 1 comment
Assignees
Labels
feature:content New content, guide, or writing needed

Comments

@lwasser
Copy link
Member

lwasser commented Jan 17, 2024

I am updating this issue to address the infra that we need to archive a package.

Step 1 - update pyosmeta model for packages

  1. add a new yaml key to the package data file
    let’s come up with a key together in our packages yaml file to indicate an archived package.

Suggestion:
archive: True

to implement this you will have to add a archive: bool which defaults to false to this ReviewModel in pyosMeta.

Once the above is done, we can update the nbless item to be True through a manual commit.

Step 2 - update the website


The NBless package has not been updated in several years. I have also tried to reach out to the maintainer via email and GitHub with no response. As such, we should archive nbless following our pyOpenSci policies.

This issue begins that process. To accommodate this, I'll need to update our website package listing with an archived package section.

pyOpenSci/software-submission#109 <- this is the issue where we discussed updating all of the older review metadata to support website search.

@willingc willingc added the feature:content New content, guide, or writing needed label Apr 3, 2024
@lwasser lwasser changed the title Archive nbless Create archive process and then Archive nbless Oct 14, 2024
@banesullivan
Copy link

To do this, I'm going to add a field to the pyosMeta ReviewModel to track this archived status and populate that value from a new label on issues. This will let us go back and simply add a label to a package's review issue to mark it as "archived".

Trouble is, we already have a field named "archive" on the ReviewModel so a question arises: what do we want to call this field and what should we name the label that would be applied to these issues? Right now, I'm thinking:
GitHub issue label is archived and the model field is a boolean with name active. All reviews will default to active=True and if the archived label is applied then active will be set to False.

Implementation is proposed here: pyOpenSci/pyosMeta#242

You can view the new archived label and currently archived packages here: https://github.com/pyOpenSci/software-submission/issues?q=label%3Aarchived

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature:content New content, guide, or writing needed
Projects
None yet
Development

No branches or pull requests

3 participants