Skip to content

FEATURE: Add a step to our ci job that updates the editorial team #884

@lwasser

Description

@lwasser

Is your feature request related to a problem? Please describe.
Currently, the editorial team is listed on our website however it only gets updated manually. And that step we often forget to do! The good news is that we have a team for editors and a team for emeritus editors that tracks who is active and we do update that because we need that for permissions!

Describe the solution you'd like

https://github.com/pyOpenSci/metrics/blob/main/scripts/get-editors.py

It would be lovely to add a workflow either here
in our action - which would involve parsing yaml so might not be idea OR

to pyosmeta here that parses the editorial team each time we update contributors and updates them. It's likely that it's best to do that work in pyosmeta and not on the website now that I think about this further. So I'll move this issue once opened to pyosmeta.

Describe alternatives you've considered
I thought about adding this to our website cron job but it probably belongs in pyosmeta so when we update contributors it also checks the editorial status there.

Another option is to create a separate editorial list that populates the website, but I am not convinced that is the most efficient option. It would be a list of GitHub usernames that Jekyll or Hugo could parse, and when we list editors, it would perform the check via Liquid.

Additional context

Our editorial teams:

https://github.com/orgs/pyOpenSci/teams/emeritus-editors/members
https://github.com/orgs/pyOpenSci/teams/editorial-board

the editors are listed here
https://www.pyopensci.org/about-peer-review/index.html#meet-our-editorial-board

Image

and it's also a title here:

https://www.pyopensci.org/our-community/index.html#pyopensci-editorial-board

Add any other context or screenshots about the feature request here.

Image

Note that when we implement this, we want a way to sort the editorial team so that the EIC and peer review leads are listed first as the leadership role hierarchy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request
    No fields configured for Feature.

    Projects

    Status
    python programming

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions