Meeting — February 10, 2020

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


Discourse (over past week):

  • Signups: 0 -> 0
  • New Topics: 4 -> 2
  • Posts: 28 -> 13

Snowdrift patrons: 117

Reminders on best-practice meeting habits

Use chat in etherpad (and add your name)

Conversation queuing

  • “o/” or “/” means that you have something to say and want to be put in the queue
  • “c/” or “?” means that you have a clarifying question and want to jump to the top of the queue
  • “d” means thumbs up, encouragement, agreement, etc.
  • “>” as an indicator of understanding someone and the point can be concluded, please move on
  • three discussion mechanisms: hand symbols (above), call for a round (and vary the order), open discussion


  • “???” on the etherpad means the notetaker missed something and needs assistance capturing what was said
  • aim for shorthand / summary / key points (not transcript)

Review previous meeting feedback

  • wolftune: happy we have an effective meeting, low stress, etc
  • msiep: did seem quite efficient
  • smiche17: thought we even could have been a little shorter, given little to talk about (nothing to add from anyone else)

Last meeting next-steps review

Team Agreements (alignwaivers) [captured]

  • NEXT STEPS(alignwaivers): use the proposal mechanism to implement ### Snowdrift-dev Channel, move GL announcements there (Salt)

  • NEXT STEPS (smichel17): setup snowdrift-dev channel [captured] smichel: good for notification management - can have separate channels/notifications based on which channel

Current Agenda

Audio Notifications for that works for firefox available via (alignwaivers) - thanks to Iko for the suggestion

  • NEXT STEPS (alignwaivers) incorporate into pad

Meeting queuing system (Salt)

  • some people (mray) felt discouraged in participation, wanting to improve and get feedback ROUND:
  • wolftune: queing system nice for lack of face to face though not as great. Good to continue but don’t be pedantic about it
  • smichel: good to treat it like raising a hand, dont need to use as exclusive way to order conversation, find a reasonable comprimise, people who have a tendency to butt in or talk too much can restrict themselves to handraise only
  • salt: queuing system seems on a whole to be a benefit but good to be aware of the issue, good to compromise
  • msiep: generally agree with the idea of not being too absolutist about
  • mray: works for what it does, felt not totally part of an open discussion
  • align: I like the idea of defaulting to open discussion but switching to queue if there’s too many people (or if lack of good turn taking) [trying to talk]

  • wolftune: useful to be able to signal I have something to say, and can convey something to say without breaking the flow or interrupting someone. Give tool facilitator freedom and feedback in order find the balance
  • Salt: Mostly agreed. has been an issue in the past, this seemed to be an improvement. good to continue to some degree
  • wolftune: [in chat] I also personally have the issue of previously (and still now) wanting facilitation and cut-off if I ramble or interrupt; so there’s other ways than this to facilitate
  • wolftune: typed some stuff, nicely facilitated conversation goes better. The question is how much to credit this vs. facilitation
  • align: liked the way we can have side-comments quickly in chat instead of having to say everything
  • mray: this structure tries to streamline, but with side effects - an emotional thing but not that much of a problem. Seems like the meeting is less approaching between one another
  • wolftune: question of how to use the tool. If the facilitator conveys ‘we are here as people and want to implement this tool to help make progress in meeting’, etc
  • smichel: some amount of back and forth that gets lost in the discussion which is useful, but perhaps an alternative folks that need to go back and forth could discuss after the meeting
  • salt: thought this was worth meeting up
  • NEXT STEPS: keep in mind for facilitating in the future

LFNW Assembly proposal about Sustainable funding for hardware accepted (alignwaivers)

  • align: this talk, most relevant to snowdrift, got accepted later. I put it down as an assembly format which is more of a discussion (??? - what is that).
  • might be useful to have Salt or someone else on the panel. Would anyone want to?
  • wolftune: a lot of the work of hardware which is on research and development. Production is a different matter (funded by hardware purchases)
  • NEXT STEPS (alignwaivers) watch for schedule release (potentially notify LFNW of other’s schedules who may be on the panel)

CiviCRM updates (Salt)

  • Salt: got the word that we’re basically ready, will hopefully hear more today.
  • Salt: Qs: What kind of specs do we have? What vhosts are we going to use – Should we link Or have
  • NEXT STEP (salt): ping OSUOSL again

Reviewing previous meeting notes when you miss

  • (came up regarding Salt missing the previous, previous meeting feedback)
  • salt: don’t know the best way of doing this
  • wolftune: we do capture the notes on the wiki, maybe reading the notes would be all that’s necessary
  • salt: just wanted to put it out there, and see if any other alternatives
  • salt: maybe have a line in the pad to reminder
  • wolftune: will help if we identify who was or wasn’t here last time.
  • NEXT STEPS (alignwaivers): incorporate both metrics of attendance and reminder to review previous meeting

- wolftune: had some people like photm that are actually reading the meetingnotes and giving feedback which is nice - smichel: have an idea from when I was on Board meeting entirely over irc, a bot that the debian group uses that documents - alignwaivers: feels more human to hear peoples voices but can see potential - alignwaivers: things can be copied from text to the pad when desired - smichel: If we go that way, it’d be important to capture text in the meeting notes

meeting evaluation / feedback / suggestions round

  • smichel: spent a lot of time discussing meeting process, felt alright and didn’t have much else to discuss, good to keep evolving, still out by the top of the hour
  • alignwaivers was some disconnection issues with etherpad, anyone have connection issues since iko managed in the past week (msiep had an issue but was with mumble too could have been internet connectivity)
  • mray: went well
  • msiep: +1
  • Salt: +++ glad we were able to spend some time on meeting logistics around mrays concerns on the hand raising implementation
  • wolftune: I noticed that there is a difference between raising a hand and then speaking, vs waiting to be called on. If everyone can see the speaking queue, we could just do it, compared to waiting until called on