The OBO Foundry Operations Committee discusses, oversees, and ensures the completion of the fundamental day-to-day activities of the Foundry. The Committee is composed of three working groups. Anyone who is active in a working group (active being based on both attendance at WG meetings and actual work done for working groups) is considered a member of the Operations Committee.

There are currently three working groups. Each page lists their respective members:

Picture Name ORCID GitHub Affiliation Country Groups
Alan Ruttenberg photo Alan Ruttenberg 0000-0002-1604-3078 alanruttenberg University at Buffalo, Buffalo USA outreach
Alexander Diehl photo Alexander Diehl 0000-0001-9990-8331 addiehl University at Buffalo, Buffalo, NY USA technical
Barry Smith photo Barry Smith 0000-0003-1384-116X phismith University at Buffalo, Buffalo, NY USA outreach
Bill Duncan photo Bill Duncan 0000-0001-9625-1899 wdduncan University of Florida, Gainseville, FL USA editorial
Bill Hogan photo Bill Hogan 0000-0002-9881-1017 hoganwr University of Florida, Gainseville, FL USA editorial
Bjoern Peters photo Bjoern Peters 0000-0002-8457-6693 bpeters42 La Jolla Institute for Immunology, La Jolla, CA USA editorial
Chris Mungall photo Chris Mungall 0000-0002-6601-2165 cmungall Lawrence Berkeley National Laboratory, Berkeley, CA USA technical
Chris Stoeckert photo Chris Stoeckert 0000-0002-5714-991X cstoeckert University of Pennsylvania, Philadelphia, PA USA outreach, editorial
Damion Dooley photo Damion Dooley 0000-0002-8844-9165 ddooley Centre for Infectious Disease Genomics and One Health, Simon Fraser University, BC Canada outreach
Darren Natale photo Darren Natale 0000-0001-5809-9523 nataled Georgetown University Medical Center, Washington DC USA editorial
David Osumi-Sutherland photo David Osumi-Sutherland 0000-0002-7073-9172 dosumis EMBL-EBI, Cambridge UK outreach
Hande Küçük McGinty photo Hande Küçük McGinty 0000-0002-9025-5538 handemcginty Kansas State University, Manhattan, KS USA editorial, outreach
James A. Overton photo James A. Overton 0000-0001-5139-5557 jamesaoverton Knocean Inc., Toronto Canada technical
Jie Zheng photo Jie Zheng 0000-0002-2999-0103 zhengj2007 University of Pennsylvania, Philadelphia, PA USA outreach, technical
Jim Balhoff photo Jim Balhoff 0000-0002-8688-6599 balhoff RENCI, University of North Carolina, Chapel Hill, NC USA technical
Lynn Schriml photo Lynn Schriml 0000-0001-8910-9851 lschriml University of Maryland School of Medicine, Baltimore, MD USA editorial, outreach
Matt Brush photo Matt Brush 0000-0002-1048-5019 mbrush Unversity of Colorado Anschutz Medical Campus, Auroa, CO USA technical
Melissa Haendel photo Melissa Haendel 0000-0001-9114-8737 mellybelly Unversity of Colorado Anschutz Medical Campus, Auroa, CO USA outreach
Nico Matentzoglu photo Nico Matentzoglu 0000-0002-7356-1779 matentzn Semanticly, Athens Greece technical
Nicole Vasilevsky photo Nicole Vasilevsky 0000-0001-5208-3432 nicolevasilevsky Unversity of Colorado Anschutz Medical Campus, Auroa, CO USA editorial, outreach
Nomi Harris photo Nomi Harris 0000-0001-6315-3707 nlharris Lawrence Berkeley National Laboratory, Berkeley, CA USA outreach, technical
Philippe Rocca-Serra photo Philippe Rocca-Serra 0000-0001-9853-5668 proccaserra University of Oxford e-Research Centre, Department of Engineering Science, Oxford UK outreach
Pier Luigi Buttigieg photo Pier Luigi Buttigieg 0000-0002-4366-3088 pbuttigieg Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research, Bremerhaven Germany editorial, outreach
Ramona Walls photo Ramona Walls 0000-0001-8815-0078 ramonawalls CyVerse, University of Arizona, Tucson, AZ USA technical, editorial
Randi Vita photo Randi Vita 0000-0001-8957-7612 rvita La Jolla Institute for Immunology, La Jolla, CA USA outreach
Rebecca Jackson photo Rebecca Jackson 0000-0003-4871-5569 beckyjackson Intelligent Medical Objects (IMO), Rosemont, IL USA technical
Richard Scheuermann photo Richard Scheuermann 0000-0003-1355-892X scheuerm J. Craig Venter Institute, La Jolla, CA USA outreach
Seth Carbon photo Seth Carbon 0000-0001-8244-1536 kltm Lawrence Berkeley National Laboratory, Berkeley, CA USA technical
Shawn Tan photo Shawn Tan 0000-0001-7258-9596 shawntanzk European Bioinformatics Institute, Cambridge UK technical

New members: follow the instructions on the onboarding doc

Alumni

Name ORCID GitHub Departed Note
Carlo Tornial 0000-0002-3734-1859 carlotorniai
Colin Batchelor 0000-0001-5985-7429 batchelorc
Eric Douglass 0000-0001-6946-1807 dougli1sqrd
Gareth Owen 0000-0001-7265-5776 G-Owen
Hector Guzman-Orozco 0000-0003-3430-8997 hectorguzor 2022-10-04
James Malone 0000-0002-1615-2899 jamesmalone OBO Industry Liaison
Janna Hastings 0000-0002-3469-4923 jannahastings
Mathias Brochhausen 0000-0003-1834-3856 mbrochhausen
Melanie Courtot 0000-0002-9551-6370 mcourtot
Michael Ashburner 0000-0002-6962-2807
Simon Jupp 0000-0002-0643-3144 simonjupp OBO Industry Liaison
Susanna-Assunta Sansone 0000-0001-5306-5690 SusannaSansone
Suzanna Lewis 0000-0002-8343-612X suzialeksander

Roles

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.

This role is open to new members.

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 ORCID Status Start
matentzn 0000-0002-7356-1779 lead

OBO New Ontology Request (NOR) Manager

You will be responsible for registering new ontologies at the OBO dashboard and helping their owners pass them.

This role is open to new members.

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 ORCID Status Start
matentzn 0000-0002-7356-1779 lead

OBO Website Coordinator

You will be responsible for gatekeeping community changes to the website.

This role is open to new members.

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 ORCID Status Start
matentzn 0000-0002-7356-1779 lead

OBO Dashboard Maintainer

Updating the OBO Dashboard once per month. 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.

This role is open to new members.

Requirements

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

People

Name ORCID Status Start
matentzn 0000-0002-7356-1779 lead

Technical Working Group OBO Operations liaison

Preparing a short report about all general developments in OBO Technical Working Group (TWG) for the OBO Operations team meeting. You will go through pull requests and emails and summarize in bullet points and report to OBO Ops.

This role is open to new members.

Requirements

  1. Strong python skills
  2. Some level of pro-activity helpful
  3. Experience with ODK/docker

People

Name ORCID Status Start
matentzn 0000-0002-7356-1779 lead

PURL system maintainer

PURL config curation and PURL server maintenance.

People

Name ORCID Status Start
jamesaoverton 0000-0001-5139-5557 lead 2015-11

OMO metadata coordinator

You will be responsible for registering new ontologies at the OBO dashboard and helping their owners pass them.

People

Name ORCID Status Start
zhengj2007 0000-0002-2999-0103 lead
matentzn 0000-0002-7356-1779 lead

OBO Tools coordinator

Coordinating and hosting OBO Tools workshops at meetings and conferences such as ICBO, and making sure tools align with OBO principles and support them, etc.)

People

Name ORCID Status Start
jamesaoverton 0000-0001-5139-5557 lead 2017

OBO Academy

Maintaining https://oboacademy.github.io/obook/ and organising OBO Tutorials.

People

Name ORCID Status Start
nicolevasilevsky 0000-0001-5208-3432 lead 2021-06
matentzn 0000-0002-7356-1779 lead 2021-06
jamesaoverton 0000-0001-5139-5557 support 2021-06
beckyjackson 0000-0003-4871-5569 support 2021-06
shawntanzk 0000-0001-7258-9596 support 2022
bvarner-ebi 0000-0002-1773-2692 support 2022

OBO Issue Tracker Shepherd

Assigning incoming issues at https://github.com/OBOFoundry/OBOFoundry.github.io, tagging them, chasing them

Responsibilities

  1. Tagging metadata related issues with 'attn: Technical Working WG' and 'metadata'.

People

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

OBO Google Service Manager

Managing the OBO Google Drives, Calendars, Mailing list 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
  5. Report adding members to the to any OBO Google drive with Write or Admin rights to the OBO Operations Committee

People

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