Meeting — January 2, 2019

Attendees: wolftune, salt, msiep, smichel17, align_waivers

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

## Board stuff, Governance overhaul / Volunteer recruitment
- NEXT STEP (wolftune): posts on discourse about things he has personal notes on governance roles.
- NEXT STEP (wolftune): co-working to create a more complete list of roles/titles we want (capture wolftune's notes in better form)
- NEXT STEP: (wolftune) create organized milestone and tasks in governance repo for Board-related and other stuff…
- NEXT STEP (wolftune): Follow up with canawen (explain current status, ask about his coding experience)

## Project outreach, Kodi etc
- NEXT STEP (Salt): Set up an hour to co-work with Michael
- NEXT STEP (msiep): work on feedback form <>

## LFNW + beta milestone prioritizing/scheduling
- NEXT STEP (Salt, wolftune): Submit CFPs by January 31st <>
- NEXT STEP (smichel17): organize the above tasks on to gitlab in some way <>

## Knocking out code issues etc.
- NEXT STEP (smichel17): Look through issues, tag backend ones
- NEXT STEP (smichel17): announce alpha-visual-design milestone on forum (to other volunteer devs) <>

## Peertube video?
- NEXT STEP (mray): Keep experimenting with peertube <>


Discourse (over past week):

  • Signups: 1 -> 2
  • New Topics: 7 -> 2
  • Posts: 39 -> 11


  • Page 108

Design and planning around blocking duplicate patron accounts, issue tracking

  • now closed
  • where do we capture anything about this in our backlog etc.
  • we’ll just drop this concern for now
  • we use top, high, med, low priority tags now and that’s good enough

Volunteer form, civi

  • NEXT STEP: wolftune opens issue in outreach repo tagged with Civi and with details from old discussion, assign to Michael

Civi, ops

  • Salt: we need to decide where Civi lives: suggest move everything but mail off of mx1, get new server for accessory apps including Civi, Ghost, Gitit… (all currently in docker)
  • whatever Aryeah wants since he’ll help maintain, but potentially just new server with all the needed normal stuff, Nginx (or Apache if he prefers) etc.
  • NEXT STEP: get server set up by Aryeah by his prefs, up to the point of Drupal + latest Civi installed (Salt owns Civi config and would like nothing more)