<aside> ✏️ Scribes TODOs - DELETE AFTER MEETING
This checklist should be completed by the host(s) and scribe(s) of the meeting
A stand-up across D_D Academy sub-teams.
Check-in. 30 seconds each: How are you feeling? What are you grateful for? What are your expectations for the meeting?
Must covers. Anything pressing that needs addressing immediately?
wolovim
: result of coordinape/opening contribution pathways:
piablo
: retro for Q3-Q4 - when, what retro for and who could facilitate?
5 minute floor for Team Stewards to highlight events in their domain:
markkos
making big strides ✊🏾
wolovim
: should we start writing/grooming tickets available to claim, or should we finish up anything before then? markkos
- good to look at the latest and generate new issues.piablo wolovim
: just received a first lesson draft from Raza. A very encouraging kick-off meeting with him on Monday.piablo
: a couple of PRs waiting - everyone is tagged - if you trust me, give them a quick one-over and I can merge them - so we are cleaning the way for v2 content and the new content concepts (e.g. updated structures, SEO, etc) that we’re baking in. (update: markkos
approved one, still SEO one waiting at piablo's
request)wolovim
: create a technical editor role task per lesson - run the code, make small fixes if required. todo: better define this suggestion.markkos
: use the public channels, e.g., #solidity, and generate more public discussion/problem solving. we can jump in and help too. piablo
: don’t want to take the resources away from the dev team. markkos
maybe we just kickstart the conversation and provide the first help, but it generates more activity and help in those channels.5 minute floor for other updates. Add any other topics for discussion as bullet points below.
Check-out. 30 seconds each: How are you feeling? Takeaways from the meeting?
ADD DISCUSSIONS THAT ARE OUTSIDE THE AGENDA