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

Update SOP.md to add guidance on community contributions to review #2528

Merged
merged 2 commits into from Feb 28, 2024

Conversation

nataled
Copy link
Contributor

@nataled nataled commented Feb 27, 2024

Fixes #2459.

@nataled nataled self-assigned this Feb 27, 2024
Copy link
Contributor

@nlharris nlharris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. The only comment I have is regarding

the NOR manager assigns the next available OBO operation member to act as designated NOR Reviewer.

What do you think about adding something about how to determine the "next available OBO operation member"?

Actually, I have one other comment: would it be helpful to add links to info about the automated (Dashboard) review?

docs/SOP.md Outdated Show resolved Hide resolved
Co-authored-by: Nomi Harris <nlharris@users.noreply.github.com>
@nataled nataled merged commit 8590661 into master Feb 28, 2024
5 checks passed
@nataled
Copy link
Contributor Author

nataled commented Feb 28, 2024

Thanks for the suggestions Nomi!

Text on how to determine the "next available OBO operation member" is already provided within the NOR Manager role document, which is cited. I think links to info about the automated (Dashboard) review are in that doc too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document how we should organise community contributions in ontology reviews
2 participants