Meeting — February 24, 2020

Attendees from last week: Salt, mray, MSiep, smichel, Alignwaivers Attendees (current): alignwaivers, mray, MSiep, Salt, smichel17, wolftune


Discourse (over past week):

  • Signups: 0 -> 0
  • New Topics: 1 -> 1
  • Posts: 4 -> 13

Snowdrift patrons: 118

Reminders on best-practice meeting habits

  • Review previous meeting notes especially when absent!
  • Audio notifications for etherpad chat available on firefox via

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

  • mray: please get audio set up well in advance

Last meeting next-steps review

Interested project (Salt)

  • NEXT STEPS (salt): Send incoming project sample documentation to them, request feedback
  • NEXT STEP (smichel17): email OSUOSL about email forwarding community@ not working.

Current Agenda

Team Agreements (via formal Proposal method) - vote on consent/concern/objections (alignwaivers)

  • alignwaivers: people who haven’t done it, do it!

Recruiting (wolftune)

  • wolftune: been some tension around this for awhile : one aspect of the ‘implementation of the site’ as the larger topic. want to open up for discuss
  • salt: have this on my list, depends on where it fits as a priority
  • wolftune: open to feedback on this. I welcome pings in regards to higher priorities
  • smichel17: I have a couple thoughts and a tab open to wolftune’s forum post about it to chime in when I get to it

Issue grooming (wolftune)

  • also related to prioritizing, signal vs noise ratio, would like to make progress here and do more on issue grooming, schedule coworking time if anyones open
  • NEXT STEPS (alignwaivers, wolftune, smichel) schedule / meeting

Libreplanet (wolftune for salt & smichel)

  • salt will arrive Thursday, volunteer training Friday, conference Sat/Sun March 14/15, return monday morning
  • wolftune: would be nice to keep in mind for everyone, things that would be nice to have done by then
  • salt: also birds of a feather options then, throw together a snowdrift discussion/talk
  • smichel: will be there on some overlapping days, still figuring out accomodations, but flexible enough to do dinner or something like that, considering volunteering if still an option
  • wolftune: would like to focus on what’s the angle/pitch for connecting with people -
  • salt: think about the focus pitch/angle (in context) for the event is: FSF - tech heavy but not just dev, political, free software movement etc. 10+ years old
  • msiep: primarily recruiting volunteers, 2ndarily projects, also getting across snowdrift status
  • mray: agreed with what msiep said, and specifically recruiting devs who can accomplish what chreekat
  • alignwaivers: agreed about devs as priority
  • wolftune: basic gist is clear, my vision is twofold: 1: inspire those who are going to make the pitch that if SD can get funding it supports lots of the things that people will be working on there (economics angle).
  • wolftune: 2: SD is really important, we need dev help, not wishy washy pitch
  • smichel: in past, found that SD is pretty easy sell because ppl more ethically/morally aligned (for the most part). The bigger thing is communicating the scope of our ambition: many people feel we’ll always be the underdog, envision that our goal is eg, doubling funding for FLO, when really we want to expand by orders of magnitude.
  • salt: hearing that we need to recruit - want to get a sign like what people who hold up at the airport “do you know haskell?” or sign with tearaways. Most people very pro what we are doing. there’s a degree of easy / newcomer tasks, have examples (front end, making sure org for the wiki is right)
  • wolftune: clarifying points: I think front end is key: clarity for people and UX will make people feel like they want to be involved. Don’t want to make it ‘you know haskell come up help us’. Better to say “you know web dev, come help us (and haskell 2ndarily).better to ask”are you too busy to help?" instead of “do you have time to help?”
  • mray: not just about the front end developer - it’s a blocking issue. Can be reflected with priority, I think it’s holding the entire project back
  • salt: sounds like recruiting and updates are the desired focus
  • smichel: do we announce we are live?
  • wolftune: feel free to say “we are accepting initial first pledges, you can pledge to snowdrift itself”. Irony is that’s what we need a front end dev for, the pledge pages aren’t updated
  • salt: the idea of ‘what is our status’ - we are to some extent out of alpha
  • smichel: pitch in my head: first is the usual. We are live with our own project, pledge with CC. Caveat is front end dev needs, help us get to a point where we can announce
  • mray: not sure that’s how we should approach people directly. For me, it’s more of look at where we are now and see how they can contribute, make a better back & front end. Being vague about it may elicit unfortunate surprise
  • wolftune: want to emphasize, when we talk about dev - it’s great to say we already have the design for what this page should look like, much better than seeing we need someone to do front end dev.
  • another specific pitch would be getting people on the forum,
  • smichel :(1) get them on board, (2) We’re very close to live, you can actually pledge with real money but the UX is not great yet. (3) We have a new design with better UX, the only thing we’re waiting on to annouce widely is implementing the design, so (4) If you are a frontend dev, please come help!
  • salt: two types of volunteers: team members, not just contributers. but here we are mostly talking about contributers here. So making it clear we do want team members, but also invite to community, and to contribute.
  • wolftune: emphasizing we DO have a team showing up weekly, if they are showing up to help there’s a lot of support (they would be joining an already strong/supportive team)
  • NEXT STEPS (alignwaivers): summarizing this thread and putting it on discourse

CiviCRM (salt)

  • salt: news: civi testing and such is done, just waiting on domain name to be moved over (supposed to happen last week). Iko switched over domain name for the old site, hopefully will be able to access the old & new one
  • extreme hope: new civi is set up in time for libreplanet

Forum post timing (smichel)

  • smichel: this prompted by wolftune post 3 hrs ago. If that was posted by friday, would have been able to check over the weekend. For the record, ideally things get posted before weekends so I can put SD work in over the weekend
  • wolftune: possibly via forum, (or probably irc / signal might be best) checkins might make sense: “hey howd the week go, whats the weekend looking like)
  • salt: pinned topic for timing / availability to remind people
  • smichel: Maybe whenever we do coworking we could announce it in IRC or forum?

IRC/Matrix bot noise (salt)

  • salt: when a lot of people making git contributions, hard to see the conversations, would
  • NEXT STEPS: Generally prompt people while available to cowork more often

OSI incubation (wolftune)

  • wolftune: the issue (posted to the Board of Directors) - contacted by new sponsor person at OSI - we should figure out what it means to graduate from incubation period - in summary, when “we have our first project” will be graduating from OSI incubation
  • wolftune: nice that we’ve been making progress of gov things, reliability and communication
  • smichel: do like the proposals popping up, I can read it and vote (without too much investment of time/energy, depending)
  • wolftune: if we had 2 or 3 people with extra time, we are on the threshold of breaking through / momentum of activity, decent enough holding pattern

meeting evaluation / feedback / suggestions round

  • salt: applaud everyone, covered a lot, glad to be less strict about rules in a beneficial way
  • smichel: also happy getting through it in amount of time, good topics that needed be discussed in sync
  • wolftune: didn’t hear even engagement with everyone, still not the same as being in the same room
  • alignwaivers: I appreciate the posts on the side sometimes, but longer thoughts could be directly added to the meeting notes in the main pad
  • mray: thanks to all, esp. salt as facilitator
  • mray: one thing thats important to me is to try to have good audio quality. If software can’t do much, but if hardware maybe we could afford decent headphones
  • msiep: glad to meet, but progress on front-end will help motivation