2020-01-08 Hypha Worker Co-op: Governance

Time: Wednesday, Jan 08, 2020 @ 3-4.30pm
Location: https://jitsi.hypha.coop/hyphacoop
Attending: pc, dw
Cultivator: dw
Notetaker: dw

Agenda

✅ Select mailing address (in convo with other WGs)
✅ Select “incorporators”
✅ Draft articles of incorporation
✅ Submit articles of incorporation 2019 Q1
Draft early/initial core bylaws
Consult a lawyer over by-laws (“Confirmation of legal standing”)
Finalize bylaws
[Plan for] the initial General Meeting 2020 Q1, by-laws adopted, director/board for upcoming year set)
Notes:
- dc: thinks “Finalize bylaws” means formally adopt

Prepare for first AGM
- Implement peer interviewing
- Determine first training
- Build to consensus on Bylaws
- Operations implementation report
- Y2 Financial Plan
- Milestones
  - Pick date
  - Draft bylaws
  - First directors selected
Implement Engagement Strategy
- Develop initial brand
- Build relationships
- Milestones
  - Develop brand lookbook
  - Re-launch website
  - Defined “Local Solidarity and Decentralized Neighbours”
Notes:
- dc: “First directors selected” an outcome, not milestone?
- pc: “first training”? –> aspirational from using our development fund!
- pc: “operations implementation report”? dc: think this was a status update
- dc: is engagement strategy mostly business development?

From 2019-12-18 all hands:

✅ Tracked organizational actions via task tracker
✅ Conducted “informational interviews” with other co-operatives
✅ Drafted and submitted articles of incorporation
- ✅ Determined head office
- ✅ Determined “incorporators” and “directors”
✅ Submitted initial return
✅ Developed co-operative resolution and signing process
✅ Ensured compliance with WSIB expectations
✅ Set up time for 2020 Q1 regular meetings and co-work session to work on:
- Draft initial bylaws
- Plan for initial General Meeting 2020 Q1

Governance wg:governance
- Archive Done tasks
- Review HIGH [priority-★★★]
- Triage new tasks
- missing labels wg:NULL | [priority-NULL]
Did triage in order except for looking at missing labels

Governance and Operations boundary?
- dc: concern over just bolting Ops on, should be its own thing (even if it meets together/has same people for now)
  - very different scale of action
  - worried if/how operations gets “ghettoized” as the no one wants to do tasks if they are left by themselves
- pc: importance of defining roles
What makes a successful AGM? What is it not?
- pc: Should feel celebratory. Assuming bare minimum requirements are already done. Shouldn’t feel rote/procedural (despite things being stacked in favour of that happening)
- dc: Alleviates tensions from previous year and sets a course for upcoming year in a motivating way. Ideally, not a place to initiate controversial convos. If challenging topics, should have prep. No surprises to most people there.
Proposal for Operations:
- New tag for “in between” tasks (e.g., could be needs-review, ownership-issue, boundary-object)
- wg:ops as new tag, rename existing to wg:infra
- “Ops” work (potentially) addressed at Governance WG for now.
Things to take to meeting today:
- Question:
  - Are there roles that you think we need to be successful? Which ones do you think are most important?
  - What makes a successful AGM? What is it not?
- Proposal for Operations

_{Edit this page}