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,
13:09:19)
=== [COMPLETE] "jwf Update tickets #25, #46
with meeting discussion about Diversity Representative, open new
ticket for call for nominations" ===(jwf,
13:09:24)
We decided on Fedora Council seat, are in the
process of filling the seat (ticket #46 is on meeting agenda)(jwf,
13:09:33)
=== [COMPLETE] "jwf Put updates into #43 about
FAS group application template, close ticket as complete" ===(jwf,
13:09:39)
=== "chhavi will work on the article for the
two Outreachy Interns we have for Fedora" ===(jwf,
13:09:48)
chhavi_ collected replies from Outreachy
interns, in the process of compiling replies into an article over
the weekend(jwf,
13:10:44)
ACTION: chhavi_ Write
Outreachy intern article from collected replies, to be completed by
next Diversity meeting(jwf,
13:11:49)
=== "jonatoni Complete a first draft of the
article for FWD (jwf to help with review)" ===(jwf,
13:11:58)
Draft is almost finished, jonatoni will add it
to CommBlog drafts over this weekend; to be completed entirely by
next Diversity meeting(jwf,
13:13:59)
ACTION: jonatoni Add
first draft of the article for FWD to CommBlog (jwf to help with
review); publish by the next meeting(jwf,
13:14:42)
=== "jonatoni will open a design ticket for the
Diversity Team t-shirts" ===(jwf,
13:14:50)
ACTION: Amita Open
new Design Team ticket for creating Diversity Team t-shirt design,
refer to FWD ticket as a reference in new ticket(jwf,
13:21:24)
=== "Amita will update the tshirts ticket, with
the criteria we discussed during the meeting" ===(jwf,
13:21:35)
We will close the old FWD ticket since it is a
completed design and the Design Team prefers new tickets for new
tasks, to help their team stay organized(jwf,
13:22:02)
chhavi_, bee2502, and jwf synced up on sharing
the videos and transcripts, but the videos are huge and take some
time to download. Fortunately, we have text transcripts that we can
use to get a sense of direction without waiting for downloads(jwf,
13:32:09)
HELP: Diversity Team
members, please review the transcripts in any free time to find
content that might be helpful for us to highlight! Please note the
transcript number / person if you find good ones.(jwf,
13:34:40)
ACTION: chhavi_ Come
up with ideas for a theme for Flock 2017 video based on transcripts
by next meeting, other team members to help and give feedback(jwf,
13:35:36)
=== Ticket #28: "Diversity Team Goals - From
June, 2016 to Jan, 2017" ===(jwf,
13:36:41)