-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undraft the bylaws: CF Council [due: 7 May] #149
Conversation
✅ 9 of 9 members of @commonhaus/cf-egc have voted (reaction or review).
The following votes were not counted (duplicates): |
70766f0
to
26bdae2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-reviewed after updates.
Agree with all the changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm approving, but it seems to me there's a real problem with the structure of this document: IMO it fails to sufficiently-clearly separate the roles of and processes followed by the CFC vs the EGC.
Open a discussion so we can chase what should be clarified? What I will add:
|
sure, we can figure it out next week. no need to block this PR. |
Just the CF Council (and Extended Governance Committee) bylaws this time.
I know I have a concern about electronic/digital participation in lieu of meetings. At the moment (as written) our electronic participation threshold (quorum) is everyone. Not sure how that will scale as we add more projects.
I think Gavin also noticed that it wasn't necessarily clear if procedures were the same or different for bylaws vs. policies.
voting group: @commonhaus/cf-egc
Do one of the following: