add OBO ops roles to the website

[nicolevasilevsky]

see slack thread https://obo-communitygroup.slack.com/archives/C01B6MQCDLN/p1664967782409519

[cthoyt]

I think it would make sense to have these either

1. auto-generated from a YAML configuration file
2. layout + markdown that inherits from the layout, similar to how the principles and ontologies are shown

[nicolevasilevsky]

Ok! I'm not sure how to do that. Would you like to get it started and then I can fill in the rest?

[cthoyt]

Make a YAML file in _data/roles.yml and add in the following:

- name: Registry Metadata Steward
  commitment: 2-4 hours per month
  requirements:
    - Love for metadata
    - basic python
    - community mindset
  description: |
    You are responsible for shepherding our registry
    metadata according to our principles and SOPs, merge changes and generally
    protect and guard them. This involves also facilitating the implementation of QC
    checks.
- name: OBO NOR Dashboard maintainer
  commitment: 2-6 hours per month
  requirements:
    - Basic knowledge of dashboard
    - Social skills are a nice to have
    - Infinite patience also helpful
  description: |
    You will be responsible for registering new ontologies at the OBO dashboard and helping their
    owners pass them.

[nicolevasilevsky]

got it, will do!

[jamesaoverton]

Copied from Slack message by Nico, minor edits for @ references:

I currently hold some roles in OBO I would like to find successors for (1 for each? Whatever you like):

• OBO Registry Metadata Steward: You are responsible for shepherding our registry metadata according to our principles and SOPs, merge changes and generally protect and guard them. This involves also facilitating the implementation of QC checks (2-4 hours per month). Requires: Love for metadata, basic python, community mindset.
• OBO NOR Dashboard maintainer: You will be responsible for registering new ontologies at the OBO dashboard and helping their owners pass them (2-6 hours per month, depending on the month). Very prestigious role 😛. Requires: Basic knowledge of dashboard. Social skills are a nice to have. Infinite patience also helpful.
• OBO Website Coordinator: You will be responsible for gatekeeping community changes (mainly @cthoyt, but some others as well) to the website. Requires: Working knowledge of javascript and python. Nice to have: jekyll and liquid (like jinja). No magic but you should have technical background. (2-6 hours per month, depending on the month)
• OBO Dashboard Maintainer: Updating the http://dashboard.obofoundry.org/dashboard/index.html once per month (requires experience with ODK/docker). Fixing horrible bugs in OBO-Dashboard if they come up (should be rare). Working with OBO Ops to find people for extending dashboard when new principles come along. Requires: Strong python skills. Some level of pro-activity helpful. (2-10 hours per month, depending on month).
• TWG OBO Ops liaison: Preparing a short report about all general developments in OBO Technical Working Group (TWG) for the OBO Operations team meeting. Requires: social skills and community mindset (no coding). 2 hours per month (going through pull requests and emails and summarising in bullet points. Reporting to OBO Ops).

The OBO Foundry Operations Committee will check that you act according to OBO principles and SOPs at all times. I would invite anyone interested in any of these roles to contact me. Even if you are not yet part of OBO Ops, consider to apply - Its a nice volunteering engagement to register on your CV, a good service to Open Science, and you will learn a lot about open science community work while you do it. There will be a transition period of 3-6 months where I help you get settled, so don’t worry about being plunged into cold water. (Note: why am I trying to find successors? I want to give other people the opportunities to be involved, get to know some amazing people and leave their mark; I also want to shift my attention now a bit to Open Science outreach, and solve the Base file problem once and for all). Thanks for considering!

------- END OF MESSAGE -------

Just because I was asked, other jobs not currently up for grabs:

• PURL system maintainer (PURL config curation, PURL server maintenance, @jamesaoverton )
• OMO metadata coordinator (I cant say I love it but its at the heart of my interest. @zhengj2007 and me)
• OBO Tools coordinator (@jamesaoverton does this: OBO Tools workshops like the ones at ICBO, and making sure tools align with OBO principles and support them, etc.)
• OBO Academy (maintaining https://oboacademy.github.io/obook/, organising OBO Tutorials: @jamesaoverton, @beckyjackson, @nicolevasilevsky, @matentzn, @shawntanzk, Bradley Varner and some more)
• OBO Issue Tracker Shepherd: assigning incoming issues at https://github.com/OBOFoundry/OBOFoundry.github.io, tagging them, chasing them: @nlharris

Maybe someone would like to start a documentation page describing all these roles!

[jamesaoverton]

Several people volunteered to fill these roles, and OBO Operations and/or the Technical Working Group should sort this out. A general question for OBO Operations is: Must volunteers for these roles be on the Operations committee? We can add more Operations members, of course, but what if someone wants to fill one of these roles without joining Operations?

[wdduncan]

I would prefer such members be on the operations committee, but I suppose there may be good reasons for them not to be. Any ideas of why they don't want to be on the operations committee?

[nicolevasilevsky]

I think we should allow anyone to volunteer if they are interested. Any volunteer help should be welcomed, in my opinion.

[shawntanzk]

Agree that anyone who wants to volunteer should be welcomed, but I would suggest that we invite them to be part the committee when they volunteer? (ps agree that they shouldn’t be required to be part of the comm to take the roles )

From: Nicole Vasilevsky @.> Reply to: "OBOFoundry/OBOFoundry.github.io" @.> Date: Thursday, 13 October 2022 at 16:07 To: "OBOFoundry/OBOFoundry.github.io" @.> Cc: Shawn Tan @.>, Mention @.***> Subject: Re: [OBOFoundry/OBOFoundry.github.io] add OBO ops roles to the website (Issue #2141)

I think we should allow anyone to volunteer if they are interested. Any volunteer help should be welcomed, in my opinion.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[nicolevasilevsky]

I agree @shawntanzk. We should invite them to join OBO ops if they like but they should not be obligated to.

[wdduncan]

Sure ... perhaps not a requirement ... but we should at least try to convince them to join. Being a member just helps improve communication channels. Plus, we need more members.
If they can't attend every meeting that is fine.

[nicolevasilevsky]

I agree we should encourage them to join. We should be sure to make them aware of the responsibilities of joining the ops team, such as attending meetings, chairing calls, etc.

[deepakunni3]

@matentzn Wow, it is amazing just how many things you have been juggling at the same time! :raised_hands:

I am more than happy to be involved in the OBO Foundry with a more formal role. If @matentzn and others think its appropriate - I’d be happy to step into the role of OBO Registry Metadata Steward.

[cthoyt]

@deepakunni3 thanks for volunteering! I think the goal of this PR is just to specify what the roles are and get people thinking about joining. Let's try and get it merged without necessarily having any new commitments in there, then the recruitment can begin :)

agreed, though, for sure it's a good time to acknowledge Nico for effectively single-handedly running most outwards-facing aspects of OBO Foundry community. Would love to see other people getting more active and reducing that burden

[deepakunni3]

Ah yes, thanks for pointing that out @cthoyt . I'll make note in the Slack thread :+1: Cheers!