Skip to content
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

Proposed amendment to Member Section for 2024 Annual Meeting #10

Closed
wants to merge 1 commit into from

Conversation

galanadra
Copy link
Contributor

These lines address the member responsibilities to keep the space clean, to report damages and dangers, and outline consequences of failing to fulfill member responsibilities.

Copy link
Contributor

@templela templela left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comments are typos, but more importantly, I have 3 main issues:

  1. The only responsibility that can realistically be broken is the cleanliness one. So calling the consequences a result of not following the responsibilities is incongruous.

  2. Members will receive written warnings from who? Presumably the board. Who determines if the responsibility has or hasn't been met? Is this a formal member escalation policy, or just power being given to the board?

  3. The board already has a formal mechanism to address any general complaints about a member. I am in general for having a set of expectations for members, but I do not think that having a specific playbook for these scenarios tied to the bylaws is necessary. The bylaws at the moment are lean and we haven't run into (or close to) a scenario that begs this change.

Basically I'm for setting out the cleanliness as a responsibility but have specific punishment tied to it.

Bylaws.mediawiki Show resolved Hide resolved
Bylaws.mediawiki Show resolved Hide resolved

# Members may resign by written notice to memberadmin@hacklab.to
## leaving the space as clean as or better than the member finds it after each visit.
## reporting damage or problems with the equipment or space to the area steward, or the Board if no steward is available, as soon as possible.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should "don't break the anti-harassment policy" be added to member responsibilities?

https://github.com/hacklabto/hacklab-bylaws/blob/7fb44162ac3b9b424134997d64e11c5c55a3147c/Anti-Harassment_Policy.mediawiki

@glowmouse
Copy link
Member

I think the by-laws with this change are less authoritarian than the current bylaws. Specifically, after the change three warnings are needed for the board to remove a member. My understanding is that the board can now remove members at will.

I don't think explicitly saying that cleaning is a member responsibility is overly onerous.

@templela
Copy link
Contributor

templela commented Sep 28, 2024

I think the by-laws with this change are less authoritarian than the current bylaws. Specifically, after the change three warnings are needed for the board to remove a member. My understanding is that the board can now remove members at will.

That would be nice but this line is still in the bylaws.

Edit: To be clear; this change only increases ways that members can be removed.

@galanadra
Copy link
Contributor Author

  1. The only responsibility that can realistically be broken is the cleanliness one. So calling the consequences a result of not following the responsibilities is incongruous.

Members can fail to rectify an invalid email, pay dues, sign the current waiver, or report damage.

  1. Members will receive written warnings from who? Presumably the board. Who determines if the responsibility has or hasn't been met? Is this a formal member escalation policy, or just power being given to the board?

Other members can call members out in writing. Maybe an addition to copy the board to make sure it doesn't turn into harassment, but we all are supposed to help keep each other accountable, no? It's just the board that gets to deal with the consequences.

@galanadra
Copy link
Contributor Author

galanadra commented Sep 29, 2024

  1. The board already has a formal mechanism to address any general complaints about a member. I am in general for having a set of expectations for members, but I do not think that having a specific playbook for these scenarios tied to the bylaws is necessary. The bylaws at the moment are lean and we haven't run into (or close to) a scenario that begs this change.

"Discipline of a member and terminating a membership
The articles or by-laws may give the directors or members the power to discipline a member for cause (for example, suspension, fine, expulsion or refusal to re-admit as a member), or their membership can be terminated. The articles or by-laws must set out the circumstances and the steps to be followed. Any discipline or termination must be done in good faith and in a fair and reasonable way.

A member must be given at least 15 days’ notice of a disciplinary action or termination. The notice must give reasons and must explain that the member has the right to be heard orally, in writing or in another format allowed by the articles or by-laws. Refer to section 51 of ONCA." - Guide to ONCA

If you want the only consequence for violating responsibilities to be revocation, then we don't have to add anything. I'm trying to add more intermediate steps, so we don't just have to rely on nothing or get out.

@templela
Copy link
Contributor

Alright I think I see the importance of offering intermediate steps or guidance for escalation. The formality of the 3 strikes rule is what makes me uncomfortable, its pressure to act a way in a situation, regardless of the circumstances of the situation.

pt by pt:

Members can fail to rectify an invalid email, pay dues, sign the current waiver, or report damage.

Invalid email is unenforceable without spot checks, paying dues is already dealt with, signing the waiver is unenforceable too given our current filing method. Leaving only the cleanliness/damage (lab etiquette).

Other members can call members out in writing. Maybe an addition to copy the board to make sure it doesn't turn into harassment, but we all are supposed to help keep each other accountable, no? It's just the board that gets to deal with the consequences.

I've told other members who I believe are quite good lab stewards to clean up their shit more than 3 times 😁. All before joining the board. Either way I think it should be spelled out more explicitly if we keep the strike system.

If you want the only consequence for violating responsibilities to be revocation, then we don't have to add anything. I'm trying to add more intermediate steps, so we don't just have to rely on nothing or get out.

This is the specific word of the act, not a paraphrase from s51:
Screenshot 2024-09-28 at 10 18 18 PM

Maybe something along the lines of:

# Members who fail to meet their responsibilities as laid out in the by-laws are encouraged to be guided or corrected by other members. In the case where they repeatedly fail to meet these responsibilities the matter should be brought before the board. There the board may choose to suspend, fine, expel or refuse to re-admit the offending member, by a majority vote. Action will never be taken without the opportunity for the offending member to present themselves on the issue.

Interestingly we don't have anything in the bylaws about fining or suspending a member.

### Revocation of membership.

# Members must resign by written notice to memberadmin@hacklab.to
## Members are responsible for paying dues until the date a written request to resign is received.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this line be done as a separate PR. I think it's less controversial than the other changes, and it still seems positive to me.

@glowmouse
Copy link
Member

I think the by-laws with this change are less authoritarian than the current bylaws. Specifically, after the change three warnings are needed for the board to remove a member. My understanding is that the board can now remove members at will.

That would be nice but this line is still in the bylaws.

Edit: To be clear; this change only increases ways that members can be removed.

You're right. Also, I do think the board needs the power to quickly remove a member for something that's not codified in the by-laws. For example, a member gets into a heated discussion with somebody in the lab and throws a punch.

I'd upvote a PR that just added a clause to the effect that members are responsible for cleaning up after themselves, given we've had problems.
I'd also upvote a PR that just added a clause to the effect that members are responsible for following the anti-harassment policy.

That would leave enforcement completely up to the board.

@templela
Copy link
Contributor

This PR has been reopened fyi
#12

@galanadra galanadra closed this Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants