2021-09-30 Hypha Worker Co-op: Dripline

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

Time: 11:00-12:00pm ET
Location: https://link.hypha.coop/calls
Attending: uv, el, dc
Cultivator: dc
Notetaker: el

Agenda

Item	Time (min)
Personal Checkins	5
Announcements	5
Task Board Review	15
Discussions	30
Process Checkout	5

Notes

Discussions

• Troubleshooting Staging + co-work on reviewing
  • New link failing!
  • Udit nother small commit
• Launching guest post
  • tweet about it? might want to change the date
    • todo: udit to change the date to sep 30
    • todo: dc to tweet out
• Dicussing Future posts
  • Fits into large new inivitative convo?
    • Reflections vs takes?
      • reflections might also be content mills
    • takes time to develop
    • how we co-operate was kind of a take
  • Hopper: https://docs.google.com/document/d/1Otvfq0VIJfqevsq5SisB7-uovEDL18CXLwXrzqggl7k/edit
    • Define new post(s) that are more on the take-like side (less minimal reflection) that builds on work/spaces we are in
  • uv: doing co-operative governance in blog post
    • cosmos doing governanace things
    • have perspectives from our own coop
    • have perspectives from COMPOST work we’ve done
    • should have a good sense of governance and should be a good thing to write about
  • el: no thoughts
  • dc:
    • thinking more about social spaces
    • November is worker coop conference
    • can attend if no one can
    • Relates to initatives
    • Helpful for social spaces for campaigns
    • Exit2DWeb
  • another idea:
    • thinking accross initiatives
    • healing DWeb
  • other one: healing data loss matrix
    • techical writing
    • who will write this?
      • el: maybe yj could help write it?
      • uv: better editor
      • eli: willing to write first draft, the edit
  • outline
    • Where is this written about?
      • https://github.com/hyphacoop/organizing-private/blob/master/documents/infrastructure/incidents/2021-06-06-matrix-data-loss.md
    • Outline
      • Length: 500-900 wds
      • Key Takeaway(s):

Introduction:

• thesis statement:

  • distributed systems are more resilient but confusing to debug

• Key points:

  • surprising that is restored by itself from other messages
  • recreating acounts auto-restored for people

1. What happened? 5Ws: What, what, where, when, why? (can re-use a lot from the incident report) [If you want a description about how to write this: “Write a blog post using the 5Ws” https://kathrynaragon.com/blog/write-blog-post-simple-5-ws/]

2. What was surprising was that even though … accounts were lost …. recovered by… This was because …

3. Why is this different from if we were using slack?

   • could this type of problem even happen if we were using slack?

Conclusion

• Month to write it, then a month to review and publish
• TODO Elon will give us a draft 4 weeks from today, i.e., Oct 28
• TODO Dawn to share outline of pt. 2 of cooperating series: radical coops / solidarity economy thing? -> Async by Oct 14

Task Board Review

• Review DONE tasks
  • …
• Review [priority-★★★] [priority-★★☆] [priority-★☆☆] [priority-none]
  • …

Process Checkout

• …

Action Items for Cultivator

• Migrate items with #todo:person to task board
• Publish meeting notes as
  • initiative: open access, or publicly indexed with restricted access
  • finance: open access, or publicly indexed with restricted access
  • operations: open access, or publicly indexed with restricted access
• Reset meeting pad for next meeting

_{Edit this page}