Meeting — January 30, 2019

Attendees: wolftune, msiep, h30, mray

Carry-overs from last meeting

## tracking ops tasks for just server maintenance
- NEXT STEP (chreekat): Review/capture ops priorities [chreekat, in his own list]

## Bryan/Stephen meeting — CI/CD improvements
- NEXT STEP (chreekat): write blog post about this process, document <>

## Tech volunteers and framework etc
- NEXT STEP (chreekat): Decide whether we're open to the option of moving off of haskell for our web framework

## LFNW + beta milestone prioritizing/scheduling
- NEXT STEP (smichel17): Look through issues, tag backend ones <>


Discourse (over past week):

  • Signups: 2 -> 0
  • New Topics: 7 -> 6
  • Posts: 31 -> 23


  • Page 108

design progress, pace

  • NEXT STEP: h30 documents his process of implementing mockups


  • wolftune made forum post: (nevermind though)
  • NEXT STEP: wolftune: better organize those notes and the governance-roles-recruiting milestone

New meeting time?

  • wolftune: mostly about finding a time that works for both mray & Salt
  • mray: Both Tuesday & Thursday can work, but not reliably. Later is better.
  • Decided: New meeting time is Thursday at 2:30 PST
  • NEXT STEP (wolftune): Announce new meeting time


  • wolftune: There’s several options: short talk (45m), long talk (90m), birds of a feather, hacking session
  • wolftune: Salt and I talked about doing a talk about FLO funding, platform cooperativism, bicycling as a metafor for FLOSS
  • NEXT STEP (Salt, wolftune): Submit CFPs by January 31st
  • platform co-op

Use of GitLab kanban boards (+ track civi todos there instead of this pad?)

  • wolftune: Brought this up last time, just wanted to re-iterate, esp. for people who weren’t here last time.
  • NEXT STEP (Salt, msiep, smichel17, h30, all…): Start using the boards to pick your own assignments, mark To Do and Doing appropriately, capture any missing issues