resources/meetings/2020/

resources/meetings/2020/2020-05-08-meeting

Meeting — May 8, 2020

  • Attendees from last week: Salt, alignwaivers, iko, Adroit, wolftune, smichel17

  • Attendees (current): Salt, alignwaivers, wolftune, smichel, iko, MSiep, Adroit

Metrics

Discourse (over past week):

  • Signups: 0 -> 0

  • New Topics: 9 -> 8

  • Posts: 105 -> 60

  • DAU/MAU: 49% -> 50%

Snowdrift patrons: 119

Reminders on best-practice meeting habits

  • Review previous meeting notes especially when absent!

  • “NEXT STEPS” should be clear and actionable for assignee (who should double-check this for themselves)

  • Use chat in etherpad (and add your name)

Discussion mechanisms

  • open discussion

  • call for a round (“pass the mic” style, facilitator makes sure no one is skipped)

  • hand symbols

    • “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

Facilitation by topic

  • There is a leader for each topic (generally the person who raised the topic), and the facilitator will assist the topic leader in the discussion via the etherpad chat

Notetaking

  • “???” in notes means something missed, please help capturing what was said

  • aim for shorthand / summary / key points (not transcript)

Review previous meeting feedback

  • adroit: I didn’t care for the timeboxing, can’t account for how much other people talk. On baton passing, it does show when done talking, but maybe something like “over” works too

  • smichel: terrible, had connection issues the whole time. first half was fine. I think baton passing just takes getting used to and we should stick with it for while.

  • alignwaivers: it would be helpful for people to note in chat if they previously dropped out

  • wolftune: We’re not doing that well with baton-passing, would suggest going back to a faciltator and varying the order. Timeboxing was helpful to stay focused

  • Salt: shared facilitation will hopefully improve as everyone gets better at facilitation, also anyone can ask for the main facilitator to facilitate. Time boxing is a good idea but was a bit wishful, needs to be more realistic. We need to get better at starting right on time. Having video was nice. I need to figure out a way to eat or get up, but this was my only hole in the schedule for a very long block. I really like the talkingstick passing for rounds.

Last meeting next-steps review

Top-level prioritised wishlist (chreekat/iko)

  • NEXT STEP (smichel): groom via forum or have a working session, identify tensions, driver, proposal through sociocracy process

  • NEXT STEP (smichel, alignwaivers, wolftune and anyone else from team): meet on May 9 or within the week to prioritise items?

  • NEXT STEP (smichel): Announce board meeting when it is decided [DONE]

Backend dev for cross-functional ux team (iko)

  • NEXT STEPS (wolftune): define new role, then recruit for it

Update on Board progress (wolftune)

  • NEXT STEP (team): engage with board members via intro posts in welcome category on discourse https://community.snowdrift.coop/t/about-the-welcome-category/527

Posting team meeting times (wolftune)

  • NEXT STEP (smichel): consolidate all the meeting times posting locations

Sociocracy processes via the forum (wolftune)

  • NEXT STEP (wolftune): discuss on forum delay between finishing draft of driver or proposal and the formal consent decision [done]

Team Agreements Follow up (alignwaivers)

  • NEXT STEP (alignwaivers): update team agreement document (as accepted proposal) on the forum and on git as an official document [DONE]

Current Agenda

Roadmap planning (smichel)

  • smichel: Board gave advice on structure of usable roadmap

  • wolftune: Board’s advice and insight is about structure/ format that is now online/discourse https://community.snowdrift.coop/t/planning-roadmap-design-and-link/1528

  • wolftune: happy to fill in the blanks and ping people as we go for needs to be met on roadmap

  • wolftune: what was orig random set of bulletpoints, now is semi-organized on the wiki https://wiki.snowdrift.coop/planning

  • wolftune: glad for input on the discourse post from people

  • wolftune: possible UI implementations with wireframe for the wiki contents

  • wolftune: wiki not currently broken up into phases

  • adroit: https://safenetwork.tech/roadmap/ might be good roadmap example

  • NEXT STEP (wolftune, MSiep): Monday coworking on roadmap

Design implementation documentation (wolftune/iko)

  • https://snowdrift.sylphs.net/pad/p/design-implementation

  • wolftune: iko put together first draft of design implementation documentation, I’d like to get feedback on this (especially from adroit) so could be handed to newcomers easily

  • adroit: was pretty obvious (in a way that is helpful to have it spelled out)

  • wolftune: having it documented is good for finding tensions (improvements) in the futures

  • NEXT STEP (smichel and others): Review this doc, annotate with current pain points

  • NEXT STEP (adroit): capture this and put it into ???git

Role clarifications, updates, documention (wolftune)

  • note from wolftune: this includes Backend dev for cross-functional ux team

  • iko: role description draft for backend dev: https://snowdrift.sylphs.net/pad/p/role-development

  • wolftune:would like to invite others to cowork. Roles from S3 such as delegator seem good to review]. All roles need clearer structure and driver statements, including need for broader structure necessary to guide fromtop-down

  • https://gitlab.com/snowdrift/governance/-/issues/53

  • NEXT STEPS (alignwaivers, wolftune): schedule coworking session

Carryovers for smichel from past meeting (smichel)

  • smichel: I have been busy; wasn’t able to do or capture these mostly; will be able to later, would like to keep these in the pad for now

  • NEXT STEP (smichel): groom via forum or have a working session, identify tensions, driver, proposal through sociocracy process

  • NEXT STEP (smichel, alignwaivers, wolftune and anyone else from team): meet on May 9 or within the week to prioritise items?

  • NEXT STEP (smichel): consolidate all the meeting times posting locations

  • wolftune: has been much discussion on forums about how to come to consensus outside of meetings

  • smichel: I’d like to see meetings here engage with things we’re all prepped on from forum etc, but now we can more immediately hash out concerns

  • wolftune: implementing gtd and compartmentalizing all this is relevant, personal organization etc

  • salt: did a big dump of tasks into gitlab, but need to utilize git more. Is it okay to put some stuff in there with ‘needs grooming’ tag

  • wolftune: git has (ee?) feature: status tag

  • wolftune: note of feature on discourse: time set bookmark


meeting evaluation / feedback / suggestions / appreciations round

  • iko: thanks

  • alignwaivers: figuring out some of this streamlining stuff will be good in long run

  • adroit: got a lot of things to read

  • smichel: didn’t feel as effective, but bc distracted. Example that meetings best when everything is thought about in advance, in reverse (no prep this time)!

  • msiep: good meeting, distracted myself, but thanks everybody

  • Salt: meeting went well, nice to have end early - using feedback. Happy with softer timeboxing and baton-passing

  • wolftune: I really liked that we got to the open chat, was a bit awkward that I brought up topics that wasn’t sure how to move forward exactly, need to figure out better ways to ping people to be aware of agenda items in advance