Open matentzn opened 3 months ago
@matentzn Update process ongoing. 2 questions:
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.
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 ?
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.
Personally, I like that the second tab serves as a history of ontology reviews
@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 (https://github.com/OBOFoundry/OBOFoundry.github.io/pull/2571) and I will continue to update the document in the coming weeks.
When a new member is added to OBO Foundry, the reigning OBO NOR Manager should add their names to the Duty Rotation table.