-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Bylaws clarifications #28
Comments
jfyi for the member thing: the intent is that all staff are invited, and encouraged but not required, to become members of the nonprofit. The idea is that we primarily operate on the basis of staff consensus, rather than explicit voting; the voting members are there to ensure that formal decisions reflect that consensus and that there's no individual or small group of leaders that can subvert things. |
If the members are supposed to (usually) be people who volunteer to the operation of the association's services, that's something worth mentioning explicitly. |
I believe https://libera.chat/about now clarifies point 1 and 4. The criteria for membership right now is "becoming staff" but I believe we'll want to consider refining it later, in fact there are already proposals being drafted for consideration. I've tracked point 2 and 4 for internal discussion on upcoming Monthly General Meetings, does that qualify as handled/answered making this issue closeable? I don't see any more immediately actionable items |
Thanks.
Do you mean 1 and 3?
Let's keep it open until the changes are "released", even if there's nothing to be done right now? But feel free to close it if you want to. Thanks again. |
1 and 2 are answered in: https://libera.chat/bylaws#membership 3 and 4 are answered in: https://libera.chat/bylaws#monthly-general-meeting (item 10) |
Excellent, thanks! |
Hi,
First, thanks a lot for https://libera.chat/bylaws
I am told you have a general meeting tomorrow to clarify/improve them, so here is a list of suggestions that you may or may not want to take into account:
Thanks!
The text was updated successfully, but these errors were encountered: