PR #10 - Recomendations for Responsibilities PR #12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Not formally part of the AGM 2024. |
|
motion tabled so this is back as my recommendation. |
templela
changed the title
zach-c-d
reviewed
Feb 7, 2025
| ## Former members will have three months to remove their belongings from the premises. If, after three months, the belongings have not been removed, the belongings shall become property of the organization. | ||
|
|
||
| # A majority of the board can vote to revoke the membership of a member. | ||
| # Members who fail to meet their responsibilities as laid out in the by-laws are encouraged to be guided or corrected by other members. |
There was a problem hiding this comment.
I like this wording.
- It represents how things are handled in practice at hacklab
- It's written in a way that makes clear this should be the first response used for misbehavior
- It's language is soft enough that it won't be used against members that fail to correct a misbehaving member.
zach-c-d
reviewed
Feb 7, 2025
zach-c-d
reviewed
Feb 7, 2025
| ## A member who has had their membership revoked can only reapply at the board’s discretion. The period for which they are barred from reapplication will be defined in the letter from the board to the member upon revocation of membership. | ||
| ## The board is responsible for informing the active members about those persons who have had their membership revoked, including communicating the length of time that they have been barred from reapplying. | ||
| ## The board is responsible for informing the active members about those persons who have had their membership revoked, including communicating the length of time that they have been barred from reapplying. |
There was a problem hiding this comment.
This seems unnecessary beyond the usual "this member has been de-memberized" email that goes out. Unless it's a safety matter, or the board has barred someone from reapplying.
There was a problem hiding this comment.
My concern here is that getting expelled from hacklab by the board could be embarrassing. Unless it's necessary, I wouldn't want to make it clear why someone dememberized in a broadcast to the entire membership.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@galanadra - here's what I reccomend the changes are specifically.
I've removed the 3 notices, as that can still apply outside of the bylaws.
And most importantly I've removed the board's unilateral decision making. Now the offending member must break a bylaw.