Roles Overview

Operations Committee

Editorial Working Group

Technical Working Group

Outreach Working Group

OBO Foundry Organizational Roles

Registry Metadata Steward

Responsible for shepherding our registry metadata according to our principles and SOPs, merging changes and generally protecting and guarding them. This also involves facilitating the implementation of QC checks.

Standard Operating Procedures

See here.

Requirements

  1. love for metadata
  2. basic python
  3. community mindset

Responsibilities

  1. Checking OBOFoundry.github.io at least weekly for metadata related issues and pull requests.
  2. Tagging metadata related issues and pull requests with 'attn: OFOC call' if they need to be discussed by the Operations Committee. Provide instructions what needs to be discussed.
  3. Assessing pull requests to be in line with OBO SOPs. Unless covered by an explicit exception, metadata changes must be signed off by registered ontology contacts.
  4. Providing guidance for metadata-related issues and pull requests.
  5. Implement additional checks for metadata integrity if necessary.
  6. The Registry Metadata Steward is not required to fix issues with the metadata proactively, but may choose to do so at their own discretion.
  7. Provide monthly summary to Technical Working Group OBO Operations liaison for report to OBO Operations Committee.

People

Name GitHub ORCID Status Start
Nico Matentzoglu matentzn 0000-0002-7356-1779 support 0000-00-00
Deepak Unni deepakunni3 0000-0002-3583-7340 lead 2022-12

OBO New Ontology Request (NOR) Manager

Responsible for assinging reviewers to new ontology requests, registering new ontologies in the OBO dashboard and helping their owners pass all the dashboard checks.

Standard Operating Procedures

See here.

Requirements

  1. Basic knowledge of OBO dashboard
  2. Community mindset
  3. Stakeholder support

Responsibilities

  1. Checking OBOFoundry.github.io at least weekly for NOR-related issues and pull requests.
  2. Managing the NOR Process (https://obofoundry.org/docs/SOP.html#NOR)
  3. Assisting NOR submitters to understanding the NOR process and passing the NOR Dashboard
  4. Assigning and reminding OBO Operations Committee Members as reviewers
  5. Assisting successful NOR submitters to making registry metadata and PURL pull requests

People

Name GitHub ORCID Status Start
Nico Matentzoglu matentzn 0000-0002-7356-1779 support 0000-00-00
Paul Fabry pfabry 0000-0002-3336-2476 lead 2022-12

OBO Website Coordinator

Responsible for gatekeeping community changes to the website.

Standard Operating Procedures

See here.

Requirements

  1. Working knowledge of javascript
  2. Working knowledge of python
  3. Nice to have: knowledge of jekyll and liquid (like jinja)
  4. Should have technical background

People

Name GitHub ORCID Status Start
Nico Matentzoglu matentzn 0000-0002-7356-1779 support 0000-00-00
James Stevenson jsstevenson 0000-0002-2568-6163 lead 2025-00-00

OBO Slack Community Manager

Responsible for managing the OBO Slack community, including tasks like welcoming new members, deleting old ones, sending invites and directing people to the right channels.

Requirements

  1. love for communication
  2. passion for community building
  3. community mindset

Responsibilities

  1. Adding people to the OBO Slack space on request, using the 'invite members' feature
  2. Welcoming new members once per week in the #general channel
  3. Directing people to the appropriate channels to use for an inquiry
  4. Inactivating accounts on request

People

Name GitHub ORCID Status Start
Nico Matentzoglu matentzn 0000-0002-7356-1779 lead 2023-06-15

OBO Newsletter Steward

Responsible for managing, compiling and disseminating the OBO Newsletter. Instructions for archiving the newsletter on the OBO Foundry’s GitHub Repository can be found here.

This role is open to new members.

Requirements

  1. Should have a basic journalistic instinct, compiling the most relevant discussion points, decisions and issues for the wider community

Responsibilities

  1. Manage a Google doc with the current and previous newsletter drafts based on the newsletter skeleton
  2. Add GitHub issues and/or pull requests tagged with "newsletter" to the newsletter, with one or two sentences of summary
  3. Summarise key developments (ongoing and past) to the community, based on reports of the working groups to the Operations Committee meeting
  4. Summarise key decisions from the OBO operations calls
  5. Proactively finalise the newsletter draft for the last meeting of March, June, September and December, and requesting feedback
  6. Once the newsletter content has been approved, send the newsletter to the obo-discuss mailing list

People

Name GitHub ORCID Status Start
Leila Kiani LK112019 0009-0009-6722-6147 lead 2023-05-01

OBO Dashboard Maintainer

Keep OBO Dashboard up to date

Standard Operating Procedures

See here.

Requirements

  1. Basic knowledge of dashboard
  2. Social skills are nice to have
  3. Infinite patience also helpful

Responsibilities

  1. Updating the OBO Dashboard once per month.
  2. Fixing horrible bugs in OBO-Dashboard if they come up (should be rare).
  3. Working with OBO Ops to find people for extending dashboard when new principles come along.

People

Name GitHub ORCID Status Start
Anita Caron anitacaron 0000-0002-6523-4866 lead 2022-12
Nico Matentzoglu matentzn 0000-0002-7356-1779 support 0000-00-00

Technical Working Group OBO Operations liaison

Technical Working Group (TWG) representative who serves as a liaison to the OBO Foundry Operations Committee (OFOC).

Standard Operating Procedures

See here.

Requirements

  1. No programming ability needed, but should be able to follow technical discussions
  2. Willingness to attend TWG meetings and collect notes

Responsibilities

  1. Report TWG progress at OFOC calls
  2. Serve as a first point of contact for OFOC and OBO Community for technical Q/A
  3. Mark relevant GitHub issues for discussion during OFOC call
  4. Summarise TWG activities to OBO Newsletter steward

People

Name GitHub ORCID Status Start
Ray Stefancsik rays22 0000-0001-8314-2140 lead 2022-12
Nico Matentzoglu matentzn 0000-0002-7356-1779 support 0000-00-00

PURL system maintainer

PURL config curation and PURL server maintenance.

People

Name GitHub ORCID Status Start
James A. Overton jamesaoverton 0000-0001-5139-5557 lead 2015-11

OMO metadata coordinator

Responsible for coordinating changes to the OBO Metadata Ontology (OMO). OMO reflects OBO consensus on term and ontology metadata in OBO ontologies. Changes need to be carefully reviewed and votes called if needed. No PR should be merged in OMO without the consent of the OMO metadata coordinator.

People

Name GitHub ORCID Status Start
Jie Zheng zhengj2007 0000-0002-2999-0103 lead 0000-00-00
Nico Matentzoglu matentzn 0000-0002-7356-1779 lead 0000-00-00

OBO Tools coordinator

Coordinate and host OBO Tools workshops at meetings and conferences such as ICBO, make sure tools align with OBO principles and support them, etc.

People

Name GitHub ORCID Status Start
James A. Overton jamesaoverton 0000-0001-5139-5557 lead 2017

OBO Academy

Maintain https://oboacademy.github.io/obook/; organize and advertise OBO Tutorials.

People

Name GitHub ORCID Status Start
Nicole Vasilevsky nicolevasilevsky 0000-0001-5208-3432 lead 2021-06
Nico Matentzoglu matentzn 0000-0002-7356-1779 lead 2021-06
James A. Overton jamesaoverton 0000-0001-5139-5557 support 2021-06

OBO Issue Tracker Shepherd

Keep an eye on issues in the GitHub issue tracker and help keep them prioritized appropriately

Responsibilities

  1. Monitor issues at https://github.com/OBOFoundry/OBOFoundry.github.io, tag them, follow up on them as needed

People

Name GitHub ORCID Status Start
Nomi Harris nlharris 0000-0001-6315-3707 lead 2019-01

OBO Google Service Manager

Manage the OBO Google Drives, calendars, mailing list (Google Group) and meeting minutes

This role is open to new members.

Responsibilities

  1. Adding and removing people from OBO Mailing Lists
  2. Adding new OBO Ops members to Google Drive and removing alumni
  3. Adding important OBO events to the OBO calendar and sending out invites
  4. Managing public and internal OBO Google Drives

People

Name GitHub ORCID Status Start
Nomi Harris nlharris 0000-0001-6315-3707 lead 2019-01

Code of Conduct Committee Member

Code of Conduct (COC) Committee members are responsible for ensuring the OBO Code of Conduct is upheld. They are, in particular, available for anyone in the community to be contacted individually or as a group.

This role is open to new members.

Requirements

  1. being able to deal with sensitive interpersonal issues discreetly
  2. being willing to mediate between conflicting viewpoints
  3. being highly available when issues arise
  4. fully embracing the OBO Code of Conduct

Responsibilities

  1. Being available to receive COC-related issues via email from anyone in the community, and dealing with them discreetly (not sharing any part of the communication without permission)
  2. Developing strategies for dealing with COC-related issues according to established COC protocols
  3. Ensuring that the OBO Code of Conduct is upheld around matters directly related to the OBO Foundry
  4. (Other responsibilities are yet to be defined for this role)

People

Name GitHub ORCID Status Start
Alexander Diehl addiehl 0000-0001-9990-8331 support 2023-06-16
Lynn Schriml lschriml 0000-0001-8910-9851 support 2023-06-16
Nico Matentzoglu matentzn 0000-0002-7356-1779 support 2023-06-16