Update "Membership" page

[cmungall]

This page has a URL and title that suggests membership of OBO in a broad sense: https://obofoundry.org/docs/Membership.html

But the content is just about membership of the OC

The OBO governance recommendations state:

The current membership page erroneously suggests that the OBOF membership solely includes members of the Operations Committee and working groups

@nataled suggests The page states that those listed are Ops, not Foundry as a whole, so there's no error per se. However, to avoid misinterpretation, there's a possible fix: Retitle the page “Operations Committee Members”

We should do this. A separate question is whether to change the URL. I am not sure what support we have for redirects, but for maximum clarity I suggest the following:

1. We move Membership.md to OperationsCommitteeMembership.md
2. We have a new page Membership.md, that is mostly links
   • link to OperationsCommitteeMembership
   • Links from the "participate" navbar

In time we could flesh out the membership page more and have more robust inclusive language that clarifies the different roles community members can have in relation to OBO, following the governance recommendations. However, getting this right will take time, so I suggest my incremental steps above while we work this out

[nlharris]

This sounds reasonable to me, and I would be happy to carry it out. Do we need to get approval during an OBO Ops meeting?

There's an even more incremental approach we could follow: we could change the title of the Membership page right now and hold off changing the URL until we have a new Membership.md page. I think the URL is less important than the title of the page and the text used for hyperlinking to it.

[addiehl]

Also, some affiliations have changes since this page was made (at least 4 people). Might be good for everyone to review their affiliations and offer updated information if needed.

[matentzn]

Its totally fine to do all the edits suggested here IMO, there is no "significant change" which needs Ops approval, but when the PR is done I would suggest to have @nataled review it has a member of EWG.