Meeting — November 4, 2019

Attendees: msiep, wolftune, salt, alignwaivers, photm, smichel


Discourse (over past week):

  • Signups: 0 -> 1
  • New Topics: 1 -> 2
  • Posts: 11 -> 16

Reminders on building new best-practice habits

Sociocracy stuff

  • Drivers, describing driver statements:
    • Current situation + effect + what’s needed + impact of doing it
    • forum discussion of our use:

Use of GitLab kanban boards

  • Use the boards to pick your tasks, dragging or marking To Do and Doing appropriately


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

## Issue grooming / dumping etc
- <>
- NEXT STEP (smchel17): Delete or close the LFNW 2019 milestone
- NEXT STEP (smichel + wolftune + alignwaivers): schedule grooming session
- NEXT STEP (msiep): groom design repo issues

## Team communication commitments etc
- NEXT STEPS (wolftune + alignwaivers): keep studying Sociocracy ideas around this, find current stuff we have, organize our statements

## Marking prominently that we're under-construction
- NEXT STEP (mray): respond to proposal

## Nathan Schneider as Board recruit?
- Michael went on System 76 tour with him, welcome to use that reference as a prompt
- NEXT STEP (wolftune): reach out to Nathan


  • NEXT STEP (athan + wolftune): get accommodations planned, see if anyone wants to come up with us
  • we’ll have a table
  • Aryeah will be there and can help at the table
  • Things to focus on: we are going through long transition to OSU, lots of volunteer opportunities
  • Also discuss Sociocracy, things to get help with? Meeting note taker
  • Display, demonstrate, and maybe collect, project interest forms
  • Collect emails for mailinglist, signups, somehow to display current match for us
  • Priority is on team building
  • form for projects interested! Get some involved as much as we can
  • has a good next-steps
  • putting reference in our separate talks etc
  • wolftune: my talk is about Transformative Justice etc. will reference our CoC and values


  • OSUOSL is going forward with clean install of Drupal and CiviCRM
  • after install, we’ll have to do configuring
  • then import of data
  • after CiviCRM is working, various design tasks for survey forms / volunteer intake forms…

Donation CRM, follow-up

  • NEXT STEP (wolftune): make a spreadsheet for stuff-to-go-in-Civi as in the recent donation
  • Use thoughts here:

Code development progress

  • NEXT STEP (chreekat): run the backlog of crowdmatches (blocked by needing to build and deploy updated site)
  • chreekat made progress on CI with GitLab, but got stuck on something with postgres
  • once CI/CD is working, we just also need OSUOSL to run the main site server, then we can get everything updated
  • photm: more clarity about the priorities and why they are (and whether they are valid) would be helpful
  • photm: reading a few issues marked high priority, I had the feeling that they were not actually high priority. For example, upstreaming our postgresql fork
  • wolftune: the broader issue seems to be issue grooming — everything should have driver statements in addition to just what needs doing. & we want to do more regular grooming.
  • NEXT STEP (photm): ping chreekat (and others) at to check what the priority was, why was this a blocker? Was it related to getting the codebase updated to upstream dependencies?

Athan met industry person, wastewater management FLO software something

  • Ask about using mechanism at institutional level
  • Encouraged forum participation
  • Short answer, idea of different level of patronage for instutitions

meeting evaluation / feedback / suggestions round

  • need note taker
  • consent to the agenda would have been good
  • people who have to leave early could then make sure the order will fit them
  • maybe more clear rounds, discuss tensions, have more explicit proposals and objections/concerns