Meeting — December 9, 2019

Attendees: smichel, Salt, wolftune, alignwaivers, msiep, ikomi


Discourse (over past week):

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

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:
    • Objections vs concerns
    • Example of proposal phase:

Use of GitLab kanban boards

  • Use the boards to pick your tasks, dragging or marking To Do and Doing appropriately
  • e.g. wolftune’s:

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.
  • three discussion mechanisms: hand symbol, round, open discussion

Review previous meeting feedback

  • Salt: great to have all the attendees, still have tention of not starting on time
  • smichel: handraising worked surprising well
  • wolftune: handraising worked well, personally felt less like interrupting, we seem to be engaging with issues rather than just noting them
  • iko: miss older format, this is a bit more rigid, but if people are happy I don’t mind (understandable people might prefer it overall to reduce mic collision)
  • MSiep: happy to keep trying to format
  • mray: willing to keep testing, why don’t we use Matrix for more things that integrate this
  • alignwaivers: thing hand raising good idea, but want way to say two words without having mics fighting, type more things out, esp simple yes/no questions


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

## Volunteer / role recruiting etc
- SeaGL volunteers, Civi status, board recruiting etc, follow up by mid-Dec with or without Civi

## Volunteer recruiting application
- NEXT STEP (msiep): Wireframe of (or wherever the form will live), potentially with second stage "fill out profile" option (see meeting notes )

## Advanced agenda planning for meetings
- secretary role, reminders about this etc.
- NEXT STEP (wolftune): create a thread to discuss how to resolve this tension <>

## Issue grooming / dumping etc
- NEXT STEP (align_waivers): compile a list of references or links that explore the issue of grooming-guide
- NEXT STEP (smichel17): Delete or close the LFNW 2019 milestone <>
- NEXT STEP (smichel + wolftune + alignwaivers + msiep): schedule grooming session
- NEXT STEP (msiep): groom design repo issues

## Code development progress / site building
- NEXT STEP (chreekat): run the backlog of crowdmatches (blocked by needing to build and deploy updated site)
- NEXT STEP (wolftune): contact people, chreekat and/or others, verify how to build and send build to the server; also add mention of this in

## Engagement / "Community member" recruiting
- NEXT STEP (Salt): create a driver statement for an active community voice role

Marking prominently that we’re under-construction

  • msiep: I looked at what Robert sent, one existing issue is what the “under construction” flag looks like on mobile, but otherwise looks good to go
  • misep: Looks like it will be straightforward, would be nice to have but maybe not necessary to proceed.

  • Salt: Next step is “implementation” — what does that look like today?
  • wolftune: Note, updating live site is independent of whether we get the development done locally
  • Salt: I mean the local development
  • wolftune: Henri (h30) is the one doing this, was working on documenting the contribution process.
  • wolftune: I recently saw a long-term friend/contributor who could do frontend dev, maybe.
  • Salt: Is h30 still in the irc channel? I can reach out to him
  • smichel17: I can reach out.
  • wolftune: We also have a bunch of people who have been interested that we could reach out to about this specific task.

  • NEXT STEP (smichel17): Privately reach out to h30, make sure to mention the ‘under construction’ site banner issue
  • NEXT STEP (mray): finish mockup & get feedback

Blog post spam?

  • Salt: We’ve been recieving “Do you want to do mutual blogspam posts?” type emails recently. Do you think they’ve been handled well?
  • wolftune: I think so. A few of them have been people who clearly didn’t actually read our wiki, just based on keywords. I think these are fine to ignore.
  • wolftune: A few others have been more involved, we can write back to those people explaining why we don’t do it or consider it if they’re really aligned.

meeting evaluation / feedback / suggestions round

  • smichel: could have been faster with amount covered, liked starting on time
  • Salt: sloppier with the hand-raise, maybe some flexibility is fine
  • wolftune: feedback for Salt, say “acknowledged” or “thanks for update” rather than “no problem” when there’s no progress or otherwise there are problems
  • align: I think it’s easier to get sloppy when we have less on the agenda
  • msiep, iko: nothing to add :)