How This Works: We look at past #action items
from the last meeting for quick follow-up. If a task is completed,
we move on to the next one. If it isn't, we get an update and
re-action if needed. If no status, we'll try to get a quick update
and move forward.(jwf,
15:12:43)
=== [COMPLETE] "jwf Follow up with pyadav on
mailing list about FWD CFP article after meeting" ===(jwf,
15:13:05)
=== [COMPLETE] "tatica Open a new D&I team
Pagure ticket to discuss a new "I am Fedora" community video to
start working on at Flock (cc: @x3mboy / @bt0dotninja over on Fedora
Marketing)" ===(jwf,
15:17:13)
#104 has no updates; reminder to follow-up with
discussion for D&I hackfest, 1x1 coffee interviews, and speak a
non-English language in their respective sub-tickets(jwf,
15:26:42)
Ticket #94: "Fedora Women's Day 2019"(jwf, 15:28:14)
ACTION: nkathole
pyadav Collaborate on draft of suggested improvements / additions to
FWD organizer resource pack in a Google Doc by Monday, 29
July(jwf,
15:42:20)
IDEA: Organize content
by audiences (e.g. resources for university FWDs, resources for
office FWDs, etc.)(jwf,
15:42:45)
IDEA: Divided in two
types of resources: actual organizer resources (e.g. promoting your
FWD, where to find flyers / graphics from D&I team) and content
resources (what cool things are happening in Fedora community? How
to get involved in Fedora community? etc.)(jwf,
15:43:28)
Ticket #54: "Create event organization best practices guide for D&I at Fedora events"(jwf, 15:44:47)
ACTION: bee2502 Add
comment to Ticket #54 about splitting up NumFOCUS chapters and
asking for help with summarizing each of the ten chapters with rest
of team(jwf,
16:02:02)