Hi Bill,
What do you think are the high priority items to tackle? Is this to work through outstanding issues on the tracker? Or just to meet for the sake of meeting?
I think part of the challenge here stems from the early decision to include lots of highly domain specific relations in one ontology; see:
While practical in some ways, this leads to issues with meetings. In the past, when I attended RO meetings, it is mostly generalist ontologists discussing an issue in a specific domain without the experts present. This leads to frustration with PRs not being merged etc.
Here is what I have always advocated for, but I don't see it reflected in the online docs. Insofar as RO is cross-domain and deep, there needs to be governance mechanisms set up such that certain branches of the ontology are governed by a particular specialist group. That group should have their own rules for who merges PRs, etc, so long as the change localized to their branch. That group can and should decide when to have regular or ad-hoc meetings, no need to bring in the wider group. These groups would be welcome to use to RO time slot for convenience, but it would be clear who needs to attend each meeting.
The core RO group would meet to discuss pan-domain relations, anything to do with COB (though this might be better done on COB calls), and would be available to answer technical questions from the domain groups.
I would be happy to join a one time call to finalize and document these governance procedures. I'm also happy to join to discuss technical questions.
I people do have immediate technical questions or ad-hoc things to discuss, we also have the slack channel, this can be much better if people need immediate responses.
Another potential topic is the long abandoned RO paper. Having some targeted calls to finish this up might be productive.