Toronto Workers Co-op Meeting 23 Jan 2019

🗓 Calendar
Time: 23 Jan 2019 5:00 PM ET
Location: https://appear.in/offline
Attending: ben, udit, yurko, elon, garry, patcon, dc

[TOC]

Agenda

• Go thru previous business
• IPFS grant status
• Status update from each working group
• New Business
  • Name, M/V
  • Meeting schedules for 2019

Notes

• Previous Business

  • udit: Move results of our Retreat to GitHub
  • all: Contribute to Org Name and M/V, have finalized Name and M/V by Jan 18
    • all: add further proposals by weekend
    • dc: Mon Jan 14 – set up polls on Name and M/V
  • patcon: Reach out to OCA about non-profit coop
  • all: 5-6 pm for next meeting and one more in Jan, monthly “all hands” after
    • set up in calendar
  • udit, patcon, ben: Discuss business planning tomorrow in person
  • ??: Jan 20 ping PL if haven’t heard anything

• IPFS grant status

  • reached out, we should get a decision by end of this month, Jan 28
  • Timelines to be adjusted based on new start date

• Working Group Updates

  • Business Planning
    • Meeting plan, Feb 8 in person
    • Co-work, in person
    • Sorta agreed on format
  • Governance
    • Async so far!
    • Milestone for Q1 for draft
    • “Living Documents” in our ecosystem?
      • Bylaws as “official”
      • Keeping our operating procedures more living/manage in a different process
      • Seems like making the bylaws work for us is exciting! (e.g. all-board membership)
  • Finance
    • Notes from visit to DUCA: https://hackmd.io/JCKRSvcTQ12EP-O_nzd-mQ?edit
    • Things more difficult with multi-sig
    • Some question over wires that Yurko wants to confirm
    • patcon: ability to waive fees?
    • patcon: is there a way to think about non-multisig
      • e.g. expenses versus paying from bank account -dawn: Keep small cash pool for day-to-day with shared password to avoid multi-sig burden on everything (e.g. OpenCollective, PayPal, recurring costs not paid out of pocket by members), but also understand the cases we want multisig (paying out major expenses?)
  • Infra and Ops
    • Laundry list of tools, potentially out of scope? Needs versus project “wants”?
    • benhylau: make tools on as-needed basis
    • yurko: prioritize password management (benhylau +1)
      • thinking about project and task management
      • knowledge management
    • Milestones for this group needs to be clarified, this should move forward!
    • Infrastructure as code
      • dcwalk: over-automating infra may be harmful to the org (e.g., 100% reproducible deployment vs. exceptions)
      • dcwalk: let’s not die on the infra hill…?

• Mission, Vision, Short list of 10 names: And finally, with 6/7 weighing in, we have a top ranks mission statement:

  Worker Co-operative cultivates collective growth and meaningful livelihoods through learning and building technologies together.

  With 5/7 people weighing in, the clear leader for a Vision is:

  Working in solidarity with our neighbours, we support each other and provide safe harbour to imagine and create alternative futures.

  With 6/7 people weighing in the top-half of our ranked names are (in order):

    Radicle
    Hypha
        - pronounciation
    Dripline
    Random Assembly
        - a joke?
    Intercrop
        - sounds kinda nice
        - sounds too agricultural
    ~~Filamentel/Filamental~~
    ~~Patch Dynamics~~
        - vibe (systems thinking)
    ~~Dripline Systems~~
    ~~Hyphae~~
        - pronounciation
    ~~Treefall Gap~~
  

  • Not ready to decide name today
  • Get feedback from friends on top five and share notes
    • potential pitfalls and how it resonates with friends
  • DC: thinks that like all of the words need some explanation to be understood in the way we intend them

Actionable Items

• patcon: Reach out to OCA about non-profit coop
• In a week, add name feeling out on loomio
  • dawn update loomio thread

_{Edit this page}