generate officers page on mkdocs

[sophiebsw]

currently the officers page on mkdocs is a mess and very outdated. it should be updated to work similarly to the old page, being generated through ldap information. ideally it could be a static page that is generated/built by a CI job

[vqbc]

theoretically if we use a macros plugin we can do the same thing as the old officers page and also add hours to the mkdocs lab page... it'd probably add too much complexity though

[iancheung0202]

@sophiebsw ive been wanting to contribute for a while now and i just dug into this and i dont think officer/committee data isn't actually in ldap anywhere (opstaff, ocfadmin these just manage sudo perms and not manager roles). i think the real source of truth is the _bod_terms() list hardcoded in ocfweb docs/views/officers.py, and mkdocs officers.md is basically a duplicate handwritten copy of the same thing

i was thinking instead of just generating officers.md from a json dump coming from docs/views/officers.py, i think it might make more sense to pull this data model (officer/term/committee stuff) out of ocfweb and into ocflib, so both ocfweb and mkdocs import it directly instead of duplicating handwritten stuff. mkdocs already builds w/ nix + python so it could just import ocflib at build time, no api needed.

would this be an overkill for this? i dont really have the context of how it used to work in the past and would appreciate any insights you have on this.

[iancheung0202]

update:
followed up with ocf/ocfweb#907 and #80
the single source of truth currently is located at https://github.com/ocf/ocfweb/blob/master/ocfweb/about/officers.py

next steps:
phase out the hardcoded python file of officer info and implement a system in ldap (add new roles, terms info) in ocflib.account.utils.