roles.yml

- name: Registry Metadata Steward
  open: false
  commitment: 2-6 hours per month
  requirements:
    - love for metadata
    - basic python
    - community mindset
  description: 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.
  sop: /roles/metadata-steward
  responsibilities:
    - Checking OBOFoundry.github.io at least weekly for metadata related issues and pull requests.
    - "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."
    - 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.
    - Providing guidance for metadata-related issues and pull requests.
    - Implement additional checks for metadata integrity if necessary.
    - The Registry Metadata Steward is not required to fix issues with the metadata proactively, but may choose to do so at their own discretion.
    - Provide monthly summary to Technical Working Group OBO Operations liaison for report to OBO Operations Committee.
  people:
    - name: Nico Matentzoglu
      github: matentzn
      orcid: 0000-0002-7356-1779
      status: support
      start: "0000-00-00"
    - github: deepakunni3
      name: Deepak Unni
      orcid: 0000-0002-3583-7340
      status: lead
      start: 2022-12
- name: OBO New Ontology Request (NOR) Manager
  open: false
  commitment: 2-6 hours per month
  requirements:
    - Basic knowledge of OBO dashboard
    - Community mindset
    - Stakeholder support
  description:
    Responsible for assinging reviewers to new ontology requests, registering new ontologies in the OBO dashboard and helping their
    owners pass all the dashboard checks. 
  sop: /roles/nor-manager
  responsibilities:
    - Checking OBOFoundry.github.io at least weekly for NOR-related issues and pull requests.
    - Managing the NOR Process (https://obofoundry.org/docs/SOP.html#NOR)
    - Assisting NOR submitters to understanding the NOR process and passing the NOR Dashboard
    - Assigning and reminding OBO Operations Committee Members as reviewers
    - Assisting successful NOR submitters to making registry metadata and PURL pull requests
  people:
    - name: Nico Matentzoglu
      github: matentzn
      orcid: 0000-0002-7356-1779
      status: support
      start: "0000-00-00"
    - github: pfabry
      name: Paul Fabry
      orcid: 0000-0002-3336-2476
      status: lead
      start: 2022-12
- name: OBO Website Coordinator
  open: false
  commitment: 2-6 hours per month
  requirements:
    - Working knowledge of javascript
    - Working knowledge of python
    - "Nice to have: knowledge of jekyll and liquid (like jinja)"
    - Should have technical background
  description: Responsible for gatekeeping community changes to the website.
  sop: /roles/website-coordinator
  responsibilities:
  people:
    - github: matentzn
      name: Nico Matentzoglu
      orcid: 0000-0002-7356-1779
      status: support
      start: "0000-00-00"
- name: OBO Slack Community Manager
  open: false
  commitment: 1-3 hours per month
  requirements:
    - love for communication
    - passion for community building
    - community mindset
  description: 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.
  responsibilities:
    - Adding people to the OBO Slack space on request, using the 'invite members' feature
    - "Welcoming new members once per week in the #general channel"
    - Directing people to the appropriate channels to use for an inquiry
    - Inactivating accounts on request
  people:
    - name: Nico Matentzoglu
      github: matentzn
      orcid: 0000-0002-7356-1779
      status: lead
      start: "2023-06-15"
- name: OBO Newsletter Steward
  open: true
  commitment: 2-4 hours per month
  requirements:
    - Should have a basic journalistic instinct, compiling the most relevant discussion points, decisions and issues for the wider community
  description: 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](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/CONTRIBUTING.md#newsletter).
  responsibilities:
    - Manage a Google doc with the current and previous newsletter drafts based on the newsletter skeleton
    - Add GitHub issues and/or pull requests tagged with "newsletter" to the newsletter, with one or two sentences of summary
    - Summarise key developments (ongoing and past) to the community, based on reports of the working groups to the Operations Committee meeting
    - Summarise key decisions from the OBO operations calls
    - Proactively finalise the newsletter draft for the last meeting of March, June, September and December, and requesting feedback
    - Once the newsletter content has been approved, send the newsletter to the obo-discuss mailing list
  people:
    - github: LK112019
      name: Leila Kiani
      orcid: 0009-0009-6722-6147
      status: lead
      start: "2023-05-01"
- name: OBO Dashboard Maintainer
  open: false
  commitment: 2-10 hours per month
  requirements:
    - Basic knowledge of dashboard
    - Social skills are nice to have
    - Infinite patience also helpful
  description: Keep OBO Dashboard up to date
  sop: /roles/dashboard-manager
  responsibilities:
    - 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.
  people:
    - github: anitacaron
      name: Anita Caron
      orcid: 0000-0002-6523-4866
      status: lead
      start: 2022-12
    - github: matentzn
      name: Nico Matentzoglu
      start: "0000-00-00"
      orcid: 0000-0002-7356-1779
      status: support
- name: Technical Working Group OBO Operations liaison
  open: false
  commitment: 2 hours per month
  requirements:
    - No programming ability needed, but should be able to follow technical discussions
    - Willingness to attend TWG meetings and collect notes
  description: Technical Working Group (TWG) representative who serves as a liaison to the OBO Foundry Operations Committee (OFOC).
  sop: /roles/twg-ops-liaison
  responsibilities:
    - Report TWG progress at OFOC calls
    - Serve as a first point of contact for OFOC and OBO Community for technical Q/A
    - Mark relevant GitHub issues for discussion during OFOC call
    - Summarise TWG activities to OBO Newsletter steward
  people:
    - github: rays22
      name: Ray Stefancsik
      orcid: 0000-0001-8314-2140
      status: lead
      start: 2022-12
    - github: matentzn
      name: Nico Matentzoglu
      orcid: 0000-0002-7356-1779
      status: support
      start: "0000-00-00"
- name: PURL system maintainer
  open: false
  description: |
    PURL config curation and PURL server maintenance.
  responsibilities:
  people:
    - name: James A. Overton
      github: jamesaoverton
      orcid: 0000-0001-5139-5557
      status: lead
      start: 2015-11
- name: OMO metadata coordinator
  open: false
  description: |
    OMO is the OBO Metadata Ontology. This description needs to be filled in.
  responsibilities:
  people:
    - name: Jie Zheng
      github: zhengj2007
      orcid: 0000-0002-2999-0103
      status: lead
      start: "0000-00-00"
    - name: Nico Matentzoglu
      github: matentzn
      orcid: 0000-0002-7356-1779
      status: lead
      start: "0000-00-00"
- name: OBO Tools coordinator
  open: false
  description: |
    Coordinate and host OBO Tools workshops at meetings and conferences such as ICBO, 
     make sure tools align with OBO principles and support them, etc.
  responsibilities:
  people:
    - name: James A. Overton
      github: jamesaoverton
      orcid: 0000-0001-5139-5557
      status: lead
      start: "2017"
- name: OBO Academy
  open: false
  description: |
    Maintain https://oboacademy.github.io/obook/; organize and advertise OBO Tutorials.
  responsibilities:
  people:
    - name: Nicole Vasilevsky
      github: nicolevasilevsky
      orcid: 0000-0001-5208-3432
      status: lead
      start: 2021-06
    - name: Nico Matentzoglu
      github: matentzn
      orcid: 0000-0002-7356-1779
      status: lead
      start: 2021-06
    - name: James A. Overton
      github: jamesaoverton
      orcid: 0000-0001-5139-5557
      status: support
      start: 2021-06
- name: OBO Issue Tracker Shepherd
  open: false
  description: |
    Keep an eye on issues in the GitHub issue tracker and help keep them prioritized appropriately
  responsibilities:
    - Monitor issues at https://github.com/OBOFoundry/OBOFoundry.github.io, tag them, follow up on them as needed
  people:
    - name: Nomi Harris
      github: nlharris
      orcid: 0000-0001-6315-3707
      status: lead
      start: 2019-01
- name: OBO Google Service Manager
  open: true
  description: |
    Manage the OBO Google Drives, calendars, mailing list (Google Group) and meeting minutes
  responsibilities:
    - Adding and removing people from OBO Mailing Lists
    - Adding new OBO Ops members to Google Drive and removing alumni
    - Adding important OBO events to the OBO calendar and sending out invites
    - Managing public and internal OBO Google Drives
  people:
    - github: nlharris
      name: Nomi Harris
      orcid: 0000-0001-6315-3707
      status: lead
      start: 2019-01
- name: Code of Conduct Committee Member
  open: true
  description: |
    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.
  commitment: 0-6 hours per month
  requirements:
    - being able to deal with sensitive interpersonal issues discreetly
    - being willing to mediate between conflicting viewpoints
    - being highly available when issues arise
    - fully embracing the OBO Code of Conduct
  responsibilities:
    - 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)
    - Developing strategies for dealing with COC-related issues according to established COC protocols
    - Ensuring that the OBO Code of Conduct is upheld around matters directly related to the OBO Foundry
    - (Other responsibilities are yet to be defined for this role)
  people:
    - github: addiehl
      name: Alexander Diehl
      orcid: 0000-0001-9990-8331
      status: support
      start: "2023-06-16"
    - github: lschriml
      name: Lynn Schriml
      orcid: 0000-0001-8910-9851
      status: support
      start: "2023-06-16"
    - github: matentzn
      name: Nico Matentzoglu
      orcid: 0000-0002-7356-1779
      status: support
      start: "2023-06-16"