resources/meetings/2019/

resources/meetings/2019/2019-09-04-meeting

Meeting — September 4, 2019

Attendees: wolftune, MSiep, alignwaivers, smichel17, Salt, mray

Metrics

Discourse (over past week):

  • Signups: 0 -> 1
  • New Topics: 1 -> 1
  • Posts: 10 -> 12

Sociocracy 3.0, wolftune @ page: 11 of 37

Reminders on building new best-practice habits

Sociocracy 3.0 stuff

  • Drivers, describing driver statements: https://patterns.sociocracy30.org/describe-organizational-drivers.html
    • Current situation + effect + what’s needed + impact of doing it
    • forum discussion of our use: https://community.snowdrift.coop/t/sociocracy-3-0-drivers/1309

Use of GitLab kanban boards

  • Use the boards to pick your tasks, dragging or marking To Do and Doing appropriately
  • https://community.snowdrift.coop/t/using-the-kanban-boards-in-gitlab-plus-wolftune-check-in/1263

Carry-overs

## New Project Forms
- NEXT STEP: (salt) discussing LibreOffice draft with Kodi and/or other closer project contacts

## LFNW + beta milestone prioritizing/scheduling
- <https://gitlab.com/groups/snowdrift/-/issues?milestone_title=LFNW+2019>
- NEXT STEP (smchel17): Delete or close the LFNW 2019 milestone

## Salt met author of unfinished book on patronage funding at Communications conference
- NEXT STEP (salt): follow up with conference contacts

## design progress, pace / how's h30
- NEXT STEP (wolftune): bug h30 (Henri) about documenting process of implementing mockups <https://gitlab.com/snowdrift/snowdrift/issues/158>
- NEXT STEP (all): recruiting front-end (haskell?) developers

## IRC / forum activity
- need more activity, prompting etc. etc.
- mray: [longer, clear, well-said discussion about the need to just move forward in desperation toward whatever we can do, can't be perfect or always wait for someone else to do the right things etc]
- NEXT STEP (mray): post this and other questions on the forum

Issue grooming / dumping etc

  • NEXT STEP (smichel + wolftune): schedule grooming session

Comparison page

  • wolftune: emphasizing that a term like “mutual assurance” or reference to the “coordination problem” could be an important distinction, as in Snowdrift.coop and Kickstarter both check that while Patreon does not. current status: https://gitlab.com/snowdrift/design/issues/110#note_206499815
  • NEXT STEPS (mray + msiep + ): continue work on this page, consider sharing with Kodi soon etc.

Finding next “detail” page (“For public goods”, “Ongoing Funding”, “No fees”, “Non-Profit”?)

  • mray: public goods is very broad
  • wolftune: https://wiki.snowdrift.coop/about/economics
  • wolftune: one image is bike path to be more specific, but snow-clearing service is a public good overall
  • mray:
  • NEXT STEPS (mray + msiep + wolftune): discuss priorities among these

Updates from OSU

  • They did not open port 465, took some troubleshooting, config may be updated but not deployed yet, hopefully soon
  • Will need to update snowdrift.coop IP, amazon uses a dynamic IP and if they switch it then the site breaks; all we can do until we move the main site to OSU is ask OSU to update to the IP address.
  • NEXT STEPS (wolftune): Find IP on AWS and send it to OSU

Marking prominently that we’re under-construction

  • NEXT STEP (msiep): move forward the idea of marking some state-of-the-platform expressed more clearly (issue or forum post etc)

Percentage Funding

  • Salt: ask the early adopters to consider explicitly offering a percentage to us
  • mray: we should wait maybe and see how things go
  • more discussion about the topic, but ran out of time to go into much

Better meeting tech (Jitsi failed us today)

  • NEXT STEP (alignwaivers): post discussion of this to forum