Documentation request: How to review an Uberon pull request

[matentzn]

We need to break our reliance on @cmungall and @dosumis for reviewing Uberon pull requests. Can we develop a definite recipe that we can follow that allow us to spread the load a bit to create more "experienced" Uberon editors, perhaps coupled with an intensive training for the entire editorial team?

[matentzn]

@cmungall can you hammer out a step by step guide on how to review an Uberon pull request reliably, with a few notes on warnings and pitfalls?

[github-actions[bot]]

This issue has not seen any activity in the past 6 months; it will be closed automatically one year from now if no action is taken.