2019-12-18 Hypha Worker Co-op: Infra & Ops Meeting

from template | Meetings | Calendar | Tasks | Code | Drive

Time: Wed, Dec 18 @ 2-?pm
Location: https://jitsi.hypha.coop/hyphacoop
Attending: patcon, el, yj
Cultivator: …
Notetaker: patcon

Agenda

Item	Time (min)
Personal Checkins	0
Task Board Review	25
Announcements	5
Discussions	20
Process Checkout	2

Notes

Personal Checkins

• … (skipped)

Task Board Review

• Archive Done tasks
• Review HIGH [priority-★★★]
• Triage new tasks
• missing labels wg:NULL | [priority-NULL]
• Not on task board -project:hyphacoop/2 label:wg:infra-ops

Announcements

• … (skipped)

Discussions

• yj: infra feels like a bipolar group. infra + ops.
  • biggest group, if not in membership, then in perceived scope. patcon
• Summary
  • what have we done
    • Task tracker. GitHub.
    • GitHub org setup. Non-profit account.
    • Jitsi instance. (yj)
      • More reliable communication infra via self-hosted Jitsi Meet.
    • Chatbot. (pc)
    • passbolt. (yj)
    • Email server. (el)
    • website (el)
    • Loomio (do)
    • Tested Odoo.
    • Digital Ocean.
    • Inventory doc.
  • Business phone line.
  • Public presence. phone. website.
  • email distrib lists.
  • organizational stuff. Loomio. GitHub. …
  • Cataloging and inventorying the systems that are selected by org.
  • Maybe future things
    • pc: 2FA recommendations.
    • Soft security policies.
  • Initiated alias and email management policies.
  • Shortlink system.
  • Supporting chat needs.
  • Manage riot community for org
  • “how we communicate” doc?
  • thoughts?
    • yj: we’re not as effective as we should have been. not sure what our boundaries. we feel things require lots of input.
    • pc: maybe we should have service-oriented mentality? like checking in with ppl to ask what they need first
      • yj: scope of group makes me wonder if i have time
  • pc: should we be in touch more? is this why we’re bad at acting?
  • yj: revisit mandate of infra. maybe split? fix infra comms?
  • pc: infra as code commitment?
    • yj: worry can lead to vendor lock-in. e.g. terraform config being peppered with digitalocean assumptions.
    • #todo close infra tickets next time

Process Checkout

• pc: we didn’t discuss tasks. if this was a problem, one of us should probably have mentioned it earlier :)

Action Items for Cultivator

• Migrate items with #todo:person to task board
• Publish meeting notes to GitHub
• Publish meeting template for next meeting

_{Edit this page}