Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOP addition: Add new members to duty rotation table #2550

Open
1 task done
matentzn opened this issue Mar 19, 2024 · 7 comments
Open
1 task done

SOP addition: Add new members to duty rotation table #2550

matentzn opened this issue Mar 19, 2024 · 7 comments
Assignees
Labels
attn: Operations Committee Issues pertinent to broad Foundry activities, such as policies and guidelines

Comments

@matentzn
Copy link
Contributor

matentzn commented Mar 19, 2024

When a new member is added to OBO Foundry, the reigning OBO NOR Manager should add their names to the Duty Rotation table.

  • Add this to the OBO NOR Manager SOP
@nlharris nlharris added the attn: Operations Committee Issues pertinent to broad Foundry activities, such as policies and guidelines label Mar 25, 2024
@pfabry
Copy link
Contributor

pfabry commented Apr 2, 2024

@matentzn Update process ongoing. 2 questions:

@matentzn
Copy link
Contributor Author

matentzn commented Apr 4, 2024

This is the source of truth for the committee members, not the mailing list:

https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/_data/operations.yml. This is what is also displayed on the website.

Alumni member should not be included in the duty rotation.

@pfabry
Copy link
Contributor

pfabry commented Apr 4, 2024

Some other questions:

  • There is a second tab in the duty rotation spreadsheet that details the ontologies reviewed. Do we need to keep this tab and therefore maintain it, or could we just replace it with a column in the first tab that will point to the corresponding github issue ?
  • Who's in charge of maintaining the operations.yml file? For example, Vinicius de Souza is not on it.

@matentzn
Copy link
Contributor Author

matentzn commented Apr 4, 2024

There is a second tab in the duty rotation spreadsheet that details the ontologies reviewed. Do we need to keep this tab and therefore maintain it, or could we just replace it with a column in the first tab that will point to the corresponding github issue ?

Organise the spreadsheet as you like but remember that every person will be assigned multiple times when the rotation comes back. Thats why I had 2 sheets, but do as you like!

Who's in charge of maintaining the operations.yml file? For example, Vinicius de Souza is not on it.

Everyone is in charge of their own data. I have pinged @souzadevinicius and I am sure he will do it at some point soon.

@addiehl
Copy link

addiehl commented Apr 5, 2024

Personally, I like that the second tab serves as a history of ontology reviews

@pfabry
Copy link
Contributor

pfabry commented Apr 9, 2024

@matentzn @addiehl

Organise the spreadsheet as you like but remember that every person will be assigned multiple times when the rotation comes back. Thats why I had 2 sheets, but do as you like!

Personally, I like that the second tab serves as a history of ontology reviews

Yes, that makes sense.

I have updated the NOR manager SOP for your consideration (#2571) and I will continue to update the document in the coming weeks.

@nlharris
Copy link
Contributor

Note that #2571 has been replaced by #2631

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
attn: Operations Committee Issues pertinent to broad Foundry activities, such as policies and guidelines
Projects
None yet
Development

No branches or pull requests

4 participants