Regardless of who the person is doing the community management and architect work for the CentOS community, that person should have an ex-officio role and participation in Board business. This allows for the direct involvement of a community voice in all deliberations, public and private.
Look at how this can work and be writ into the governance.
As Community Architect, I'm of course +1 to having a permanent seat for the community to have a voice, and an ear, on the Board deliberations.
Please see details at https://blog.centos.org/2020/06/minutes-for-centos-board-of-directors-for-2020-06-10/
Pending ACTION : Karsten and Rich need to coordinate and make changes to add to governance.
Revisiting: Unclear exactly what remains undone here. Is this just the step of documenting this on the website?
Metadata Update from @quaid:
- Issue assigned to quaid
- Issue marked as blocking: #22
Yes, I need to get this documented; if it's OK (since we're not measuring time to close on these issues, RIGHT?!?) I created a tracker issue that this and a few others will block until completed. When I have this item in the draft and/or draft accepted, I'll close this issue.
This is documented on https://www.centos.org/about/governance/ and in my (still in process) Governance documentation.
Metadata Update from @rbowen:
- Issue status updated to: Closed (was: Open)
to comment on this ticket.
SSH Hostkey/Fingerprint | Documentation