►
From YouTube: CHAOSS DEI Working Group 2/23/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
A
Here
that
would've
been
bad
okay,
I
hope
everybody's
doing
good.
If
you
did
not
add
your
name
to
the
agenda
yet,
and
you
would
like
to
do
that.
That
would
be
awesome,
as
always,
with
every
chaos
meeting
you
do
not
have
to
turn
your
camera
on.
We
do
not
care
either
way,
so
yeah
leave
it
off
if
you
want
or
turn
it
on.
It's
totally
fine
first
item
on
the
agenda
is
to
pick
a
facilitator
for
next
week.
Do
we
have
any
takers.
C
I
can
try
for
the
next
week.
I'm
not
sure
if
I
will
do
a
great
job,
but
I
can
give
it
a
try.
Awesome.
D
But
I
think
least
that's
where
that
dog
comes
in
the
one
that
we
were
sharing
in
the
previous
night.
A
Yeah
enoch
knows
what's
coming
kristy
we
will
get
to
this
later
in
the
agenda,
but
I
have
written
a
little
doc
on
like
how
to
facilitate
our
meetings.
So
hopefully
that
will
help
you
perfect.
Thank
you.
B
A
Okay,
nice,
then,
you
do
not
have
to
know
like
what
the
deal
is
with
that
item
you
just
be
like
who
added
this?
Who
wants
to
talk
about
this
thing
that
they
added
so
it's
pretty
it's
pretty
informal,
pretty
casual,
as
you
can
probably
tell
all
right,
oh
and
matt
put
the
the
meme
in
there.
Thank
you,
matt.
E
Oh,
I
put
the
meme
in
the
chat.
I
also
put
that
facilitation
doc
you've
been
working
on
in
the
first
and
then.
A
Oh
perfect
awesome
then
we'll
just
talk
about
that
now.
I'm
gonna
move
number
six
up
to
number
one,
so
I
wrote
this
little
doc.
It's
a
one-page
thing
for
anybody
who
wants
to
facilitate
a
chaos
meeting.
It's
pretty
generic.
I
probably
left
stuff
out
so
feel
free
to
add
something
if
I
missed
messed
it
up
or
whatever
before
the
meeting.
Here's
some
things
to
do
during
the
meeting
and
then
after
the
fact
you
don't
have
to
do
anything
like
we'll
upload
it
to
youtube
and
all
of
that
good
stuff.
A
So
it's
pretty
straightforward.
But
if
you
have
any
questions
on
that
christy,
let
me
know
for
sure.
Let
me
know
not
a
big
deal
at
all,
and
I
didn't
know
where
to
put
this
because
I
feel
like
it
should
go
in
the
handbook,
but
in.
A
E
A
I
will
do
that
and
I'm
gonna
as
a
as
a
side
point.
I
think
I
had
another
one
or
two
pr's
out
there
for
the
community
book.
I'm
just
gonna
merge
them
is
that
cool.
A
A
All
right,
so
any
any
other
comments,
questions
anything
I
see,
there's
another
okay,
so
that
that
brings
up
a
good
point.
Actually
matt
matt
snell
pointed
to
this
repo,
but
that's
not
actually
the
repo
where
getbook
pulls
it
from.
A
There's
another
yeah
there's
a
different
one,
which
I
found
and
now
I've
lost.
I
think
it's.
A
E
It
looks
like
just
a
laundry
list
thing.
The
the
the
references
in
the
readme
on
the
actual
repo
are
all
broken.
E
Okay,
the
syntax
must
have
changed
or
something.
D
B
A
A
A
A
A
It's
terrible,
okay,
all
right,
so
anything
else
with
the
handbook,
stuff
facilitation
guide.
Anything
else.
A
B
Lot
for
enoch,
so
right
now
it
looks.
E
B
As
we
do,
the
website
redesign
you
know
in
the
spring
and
in
the
summer
we're
going
to
build
a
knowledge
base
on
the
site
and
the
knowledge
base
is
going
to
be
really
two
things.
One
is
it's
going
to
be
metrics
and
metrics
models
like
the
things
that
we
produce
and
the
other
is
really
going
to
be
the
handbook.
C
C
D
B
D
B
B
D
Yeah,
I
guess
that's
my
I
just
thought.
Maybe
somebody
or
a
group
should
take
it
up
so
that
just
stops
floating
all
over
the
community.
B
D
Go
ahead
and
to
I
just
asking
please
elizabeth
whether
there
is
actually
a
place
where
all
this
metric
documentation
is
pressed
apart
from
github.
Someone
can
just
guide
you
through
the
descriptions
apart
from
github
and
the
docs
that
we
use
for
editing.
E
D
Oh
yeah
sure,
okay,
we
can
go.
I
was
just
some
quick
questions.
E
This,
this
does
kind
of
make
me
think
about.
Maybe
information
management
should
be
more
of
a
focus.
That
might
be
something
to
say
here
of
the
chaos
community,
mostly
in
like
making
sure
it's
centralized
and
easy
to
access
that
might
go
in
with
onboarding.
You
might
go
in
with
the
web
server
designer
it
might
be
printing
it
in
both.
B
B
And
so
I
just
I
and
I
don't
think
it's
been
a
terrible
problem
for
the
chaos
project
and
I
still
don't
think
it's
terrible
yet.
So
I
think
it's
great
that
we're
taking
a
look
at
it
now
and
honestly.
Maybe
it's
something
that
we
kind
of
document
our
process
on
elizabeth
to
help.
Others,
like
you
know,
as
you
have
people
working.
A
Yeah
I
mean,
I
completely
agree.
I
think
it's
it's
an
interesting
part
of
chaos's
journey,
a
growing
pain
for
sure,
and
maybe
it
maybe.
This
is
something
for
the
common
working
group,
but
it
might
make
sense
to
have,
I
think,
as
enoch
was
suggesting
like
one
or
two
people,
a
small
team
of
people
that
are
like
our
documentation
team.
D
A
All
right
any
final
thoughts
on
this
before
we
move
on.
D
Okay
and
also
that,
but
but
I
think
I
don't
know
whether
much
you're
okay
with
us,
maybe
suggesting
the
community,
so
that
someone
owns
this
app.
B
Yeah,
I
think
we,
let's
start
with
that.
I
I
would
also
like
to
get
input
from
other
chaos-
community
members
who
may
have
been
through
this
process
before,
because
there
are
a
lot
of
people
in
the
community
who
are
very
experienced
open
source
community
members
and
managers,
and
they
may
have
some
insight
as
well
just
to
good
steps
forward
here.
A
All
right,
let's
go
ahead
and
move
on,
because
we
do
have
some
other
things
to
talk
about,
and
we
have
to
do
that
this
week
because
it's
our
last
week
so
we
are,
we
have
two
metrics
in
progress
that
I
think
are
going
to
be
candidates
for
our
metrics
freeze
or
metrics
release
coming
up.
Oh
wait
is
this:
something
different
project
overview
is
different.
A
E
A
Okay,
so
we'll
go
ahead
and
skip
ahead
then,
and
talk
about
our
metrics.
So
I
think
these
two
project,
demographics
and
event-
accessibility-
are
our
two
did.
We
have
any
others
that
I'm
missing.
A
Okay,
so
our
metrics
freeze
is
on
march
1,
which
is
next
week,
so
this
is
our
last
meeting
before
that.
Do
we
want
to
look
at
this
real,
quick
or
no
matt.
B
A
A
Yeah,
so
when
we
release
the
metric,
we've
worked
on
it
in
the
google
doc
and
we
say:
okay,
this
is
ready.
We
think
it's
pretty
good
as
it
is
so
we
have
a
a
metric
quality
checklist
here.
We
open
an
issue
in
the
repo
and
this
kind
of
helps
us
make
sure
we've
ticked
all
the
boxes
with
regard
to
what
needs
to
happen,
because
the
metrics
get
put
into
a
pdf
automatically.
A
So
the
formatting
is
a
big
deal.
We
want
to
make
sure
translations
are
included
and
that
the
metric
gets
translated.
We
make
sure
we
upgrade
our
spreadsheet
and
do
all
of
the
things
put
it
on
the
website.
All
of
the
things
that
we
need
to
do
to
make
sure
that
that
metric
fits
in
everybody's
requirements
of
all
the
moving
parts
of
this
machine.
A
So
we
had
worked
on
this
one
last
week:
project
demographics,
so
basically
matt,
took
that
google
doc
put
it
into
a
pr
over
here,
which
will
then
essentially
add
that
to
the
website,
and
that
will
be
the
official
version
of
that
and
that's
what
that
looks
like
it's
for
the
spring
2022
release.
A
So
that's
what
that
process
looks
like.
I
did
the
issue
for
event,
accessibility,
but
I
didn't
check
any
boxes
yet
so
matt's
ahead
of
me.
It's
a
race
and
he's
gonna
win.
A
But
since
we
already
kind
of
finished
that
one
up
last
week
that
one's
pretty
much
ready
event
accessibility,
we
worked
on
it
a
lot
last
week,
but
I
wanted
to
make
sure
that
everybody
had
one
more
chance
to
kind
of
look
at
it.
Really
quick.
So
do
we
mind
if
we
take
five
minutes,
not
even
three
minutes
and
just
read
through
this
and
just
add
any
any
final
thoughts
on
it.
D
F
A
B
A
Okay,
I
also
just
as
a
point
of
note,
I
went
through
the
issues
in
the
dei
working
group
repo,
because
several
people
had
opened
issues
mentioning
different
ideas
around
this
metric
that
we
captured
here.
So
I
anything
that
we
missed.
We
I
put
in
and
closed
those
issues,
so
I
think
there
were
like
two
or
three
cool.
A
One
issue
I
actually
while
we're
talking
about
this
was:
where
was
this
nico
had
opened
something
about
colorblindness,
and
I
we
did
include
that
in
our
event
metric.
But
I
don't
know
if
we
want
to
leave
this
issue
open
for
other
kinds
of
documentation
within
a
project.
A
A
Okay,
perfect,
then
we'll
leave
it
open
and
just
that's
the
point
of
reference
then.
E
So
I've
got
something
to
propose
here.
I
just
linked
a
document
in
the
main
minutes,
I'm
not
sure
how
far
along
this
is
for
attention
to
colorblindness.
E
But
it
looks
like
we
have
a
pretty
pretty
full,
like
not
complete,
but
pretty
full
document
for
that
metric
on
its
own
as
well.
It
was
kind
of
just
floating,
it
wasn't
in
the
spreadsheet,
but
I'm
wondering
if
we
could
just
before.
E
I
guess
it
would
have
to
go
on
the
next
release,
but
maybe
at
that
time
we
could
pick
the
colorblindness
part
out
of
the
accessibility
and,
as
we
find
different
aspects
of
accessibility,
we
could
just
take
them
out
of
the
broad
accessibility
metric
and
it
would
just
be
the
kind
of
the
placeholder
for
the
things
we
don't
have
in
place
as
a
metric.
Yet.
E
It
happened
like
before
this
year
started
so.
E
Yeah
yeah,
that's
just
an
idea
like
the
the
accessibility
metric
would
be
a
kind
of
a
catch-all,
but
as
we
wanted
to
add
more
details
to
certain
aspects
of
accessibility,
we
would
put
them
in
the
project
and
community
section.
A
Okay,
so
in
the
meantime,
how,
since
we
don't
have
that
metric
developed
quite
yet,
how
do
we
do
we
want
to.
B
B
A
You're
awesome:
let's
go
ahead
and
move
on,
so
we
have
about
20
minutes
left
just
in
case
we
have
other
stuff,
so
privacy
ethics
docs.
I
know
last
week
we
talked
quite
a
lot
about
that
matt.
It's
totally
fine.
If
there
is
no
update,
because
there's
a
lot
of
work
to
be
done.
B
B
And
so
we've
combined
them
into
a
single
document
which
seems
to
work
pretty
well
so
right
now,
I'm
in
the
I
think,
I'm
in
the
ethics
section,
and
we
have
a
bunch
of
listed
points
in
the
estate
ethics
section
that
need
to
be
put
into
more
of
a
narrative
form.
A
Where,
where
do
we
want
to
do
that,
work
like
I
don't,
I
feel
bad,
like
that's
all,
just
kind
of
falling
on
your
shoulders?
Is
that
a
common
would
that
be
common?
What.
A
B
This
up,
no,
we
have
all
the
content.
It's
really
honestly.
It's
just
a
formatting
issue
at
this
point.
Okay
and
trying
to
do
things
like
making
sure
the
section
sizes
are
somewhat
consistent
with
each
other
that,
like
the
privacy
section,
is
two
pages
and
that
the
ethics
section
isn't
like
17
pages.
You
know
what
I
mean
we're
just
we're
just
trying
to
get
the
point
across
that
these
are
things
that
you
might
want
to
think
about,
and
here's
how
you
can
move
forward
you
as
a
consumer
of
these
metrics,
can
move
forward.
A
B
A
If
you
want
a
little
more
context-
and
you
aren't
sure,
there's
a
bunch
of
context
down
here
from
last
week-
so
like
all
the
docs,
essentially,
if
you
want
to
go
and
read
them
all,
you
can
it's
your
prerogative
to
do
that
if
you'd
like
to
take
you
about
an
hour,
but
that's
okay,
all
right!
So
let's
go
ahead
and
move
on.
Then
we
don't
have
anything
we
wanted
to
share
from
dei
badging.
A
We
wanted
to
share
this
doodle,
so
please
fill
it
out
we're
trying
to
land
on
a
date
to
have
a
virtual
badging
celebration,
slash
reviewer,
appreciation
event
that
will
be
it's
being
handled
in
the
dei
badging.
A
G
There
you
go,
I
guess
just
if
people
can
get
the
doodle
done
and
we
don't
have
a
restriction
on
the
number
of
people
that
can
attend.
There
aren't.
G
I
do
we
have
a
decision
on
who
we
wanted
to
invite
outside
of
the
meetings.
Elizabeth
did
we
want
to
invite
the
people
who
had
submitted
to
the
badging.
A
Yeah
yeah
we're
going
to
invite
them
we're
going
to
invite
the
reviewers,
of
course,
we're
going
to
put
the
doodle
out
with
the
chaos
the
bigger
chaos
community
as
well
so
yeah
we'll
try
to
get
at
least
try
to
get
them
to
fill
the
doodle
out.
If
they
don't,
then
we
can
at
least
invite
them
when
we
have
a
final
date
and
that
will
be
held
on
big
blue
button.
A
A
The
leading
bit
software,
the
big
blue
button-
they
have
donated
the
space
and
that
way,
there's
no
restrictions
on
number
of
people
who
can
participate
and
the
agenda
is
tbd
right.
Now
it's
going
to
be
pretty
loose
just
kind
of
hanging
out
and
we'll
probably
have
like
a
like
a
rough
schedule
of
you
know
how
the
event
will
go,
but
it's
just
meant
to
be
a
fun
thing.
So.
G
I'm
wondering
one
a
thought
that
I've,
I
guess
just
came
up
and
it
might
be
more.
We
talk
about
it
in
badging,
who
is
maybe
a
highlight
reel
of
some
of
the
things
that
accomplishments
over
the
last
year
from
our
reviewers
so
and
other
like
metrics
accomplishments.
That
have
happened
because
of
our
like,
because
of
people
applying
for
badges
and
the
reviewers.
A
E
So
worth
mentioning
here,
it
would
be,
I
think,
a
two-year
anniversary
timeish
around
the
two-year
anniversary,
as
well,
of
the
like
the
initiation
of
the
summer
of
code
projects
and
kind
of
the
beginning
of
the
badging
initiative
too.
It
started
in
2020
so
yeah
two
years,
if
you
wanted
to
give
it
a
tagline
and
something
remarkable
about
it.
So.
G
A
A
All
right,
the
next
one
is,
I
just
wanted
to
let
matt
and
or
enoch
talk
about
the
badging
bot,
because
there's
they
have
some
amazing
things
in
store.
I'm
super
excited
about
this
work
like
really
excited,
because
I
think
it
has
bigger
implications
too,
for
the
whole
chaos
project
on
just
how
we
onboard
people,
especially
code
contributors,
so
enoch
or
matt.
Do
you
want
to
just
kind
of
give
a
quick
update
on
or
like
a
quick
overview
on
what
you
all
have
been
talking
about.
D
All
right
yep,
so
we
were
sharing
with
the
badging
in
the
weekly
badging
meeting
the
time
while
I
was
going
through
the
badging
boat
realized.
There
could
be
some
issues
that
we
can
take
care
of,
since
the
maintenance
has
been
really
on
a
low
scale,
and
yet
this
boat
is
in
use.
So
I
was
talking
to
matt
and
I
was
telling
him
we
could
actually
come
up
with
some
some
some
program
to
see
that
we
can
maintain
this
boat
slowly
as
we
wait
for
maybe
better
maintenance.
D
So
all
the
ideas
that
were
there
were
brought
up.
I
brought
them
up
and
then
me
and
matt
looked
through
them
and
added
some
details
to
them
so
that
we
can
see
how
we
better
address
them.
So
I
thought
that
we
could
bring
it
up
in
the
working
groups
so
that
they
know
that
we
are
up
to
something
and
so
that
the
whole
community
knows
who's
responsible
for
it
too.
So
we
arrange
them
in
the
in
their
priority
order
from
up
there
to
down
here.
So
we
thought
it's
good.
D
We
first
do
a
documentation,
because
previously,
whoever
came
up
with
that,
didn't
actually
put
a
documentation
that
was
really
welcoming
to
the
it
was
informative.
If
you
look
in
the
handbook
but
guiding
through
how
to
get
started,
how
to
contribute
stuff
like
that,
then
also
much
was.
I
brought
up
the
idea
of
configuration
and
cloning,
I
might
add,
the
dawn
hosting
the
boat
to
another
platform,
so
that
would
make
it
robust,
yeah
and
also
making
tests.
D
I
realized
that
there
are
some
scripts
that
are
actually
for
testing,
but
they're
broken
and
they
don't
work
so
much.
I
was
telling
that
that
we
need
to
take
care
of
testing
the
bots
and
all
the
code
that
goes
in
the
so
that
in
the
future
we
actually
have
few
things
breaking.
If
we
have
to
actually
make
this
so
robust
yeah,
then
the
two
last
things
that
were
very
important.
D
We
were
seeing
a
world
over
actually
converting
and
uploading
reviews
automatically
to
the
bot
without
first
having
to
generate
a
template.
So
someone
just
goes
the
website
and
just
fills
in
a
certain
form
or
a
certain
second
okay
and
automatically
when
they
quick
review,
and
they
don't
need
to
go
to
g
time
or
even
edit,
a
markdown
template
yeah
and
the
last
one
was
automatically
adding
reviewers.
D
So
if
reviewers
here
in
the
dei
are
interested
in
participating
in
making
reviews
automatically
when
they
sign
up
somewhere,
the
bot
picks
it
up
and
adds
them
to
the
list,
and
then
we
can
assign
them
according
to
how
many
reviews
they're
making
according
to
how
many
reviews
they
have
completed
and
according
to
their
availability,
so
stuff
like
that,
so
matt
was
actually
suggesting
most
of
the
algorithm
work
of
how
the
reviewers
will
be
managed
by
the
board.
So
that's
in
brief
about
all
of
the
ideas
there
we
were
thinking.
D
D
We
can
work
collaboratively
on
to
seeing
what
parts
of
the
documentation
software
need
to
be
added
onto
the
onto
the
documentation
that
we
may
come
up
with.
Then
we
can
go,
that's
what
they're
actually
down
there.
So
that's
briefly
about
the
budget
improvements
that
I
was
the
chat
I
was
having
with
matt.
E
Yeah,
I'd
only
add
that
that
the
link
to
the
very
basic
algorithm
idea,
it's
a
very
complicated,
complicated
setup
that
we're
working
on
for
the
algorithm.
If
you
click
on
the
picture
there,
it's
it's
about
as
complicated
as
it
gets.
E
We
have
four
things
we're
going
to
use
to
to
assign
reviewers
based
on
their
preference
and
all
this
stuff,
but
it
will
we'll
give
you
more
updates,
as
we
go,
we're
probably
going
to
have
a
doc
for
each
of
these
items
and
and
just
have
it
just
have
a
kind
of
a
branch
of
documentation.
That's
focused
on
the
badging
bot
as
well.
D
Sure
and
matt
was
like:
oh,
the
algorithm
is
really
something
that
is
kind
of
tricky
and
also
the
converting
of
the
docs
automatically
over
the
forms
automatically
so
that
the
board
picks
them
up,
and
someone
just
receives
all
results
from
one
place
is
also
some
other
tricky
thing.
So
that's
why
they're
actually
down
there
at
the
end
yeah,
so
that's
it.
B
Yes,
thanks
for
thinking
through
this
does
does
any
of
this
change
the
scope
of
what
the
bot
is
intended
to
do
or
what
it
is
currently
doing.
Right
now,
I
see
like
there's
the
ad
reviewers
yeah
that
makes
the
pot
a
little
bigger.
It
seems
like
okay,
it.
E
Might
be
worth
explaining
the
the
kind
of
the
pain
points
that
we
that
I've
experienced
in
managing
the
body
and
how
other
people
have
experienced
too?
I
can.
I
can
quickly
list
them
off.
It's
just
that,
like
manually
having
to
manually,
assign
reviewers,
because
we
didn't
have
the
time
or
the
effort
to
put
into
an
algorithm
that
assigns
them
is
something
we're
going
to
take
care
of,
and
then
also
we
have.
We
might
need
to
move
out
of
the
glitch
platform
to
have
a
little
more
control
over
the
instance.
E
The
badging
bot
instance
itself,
and
the
last
one
would
just
be
the
the
the
documentation
and
getting
people
on
board
into
the
badging
bot.
I've
tried
it
before
and
it
hasn't
been
good
so
like
making
sure
that
people
understand
it
a
little
better
if
they
want
to
read
it
on
their
own.
B
Okay,
one
thought
on
the
reviewers:
would
it
be
possible
to
include
the
inability
for
the
bot
to
ping
reviewers
if
a
review
seems
to
have
stopped
or
something
like
that.
E
The
github,
the
github
platform,
has
done
a
good
job
of
pinging
people
when
they,
when
they
get
assigned,
and
that's
really
the
focus
of
that
it
would
be
if
we
could
also
add
an
email
kind
of
hook
as
well.
But
I'm
not
sure
it
would.
I
mean
no
about
nine
times
out
of
ten.
A
reviewer
will
get
there
within
the
day
if
they
get
assigned.
So
it's
been
great
so
far,
but
yeah.
Looking
looking
forward
to
more
improvement.
B
A
A
So
this
is
super
helpful
to
help
it
be
a
little
more
scalable
in
the
future
and
rely
less
on
manual
intervention
and
also
makes
it
better
for
people
who
are
applying
for
a
badge
and
better
for
newcomers
to
the
chaos
project
who
are
looking
for
something
to
do
looking
for
a
way
to
contribute.
Having
that
documentation,
there
is
a
great
a
great
introduction
onto
you
know:
here's
how
chaos
works,
because
I
think
that
this,
the
dei
badging
is
like
so
compartmentalized
and
it's
easy
to
understand
what
it
is
and
what
it
does.
A
A
We
added
a
super
secret
meeting
to
the
cast
calendar,
we'll
we'll
we'll
add
for
people
who
are
working
on
this
bot
so
right
now
it's
just
matt
and
enoch,
but
eventually
that
placeholder
will
be
open
to
more
people
as
soon
as
like
things
get
off
the
ground
a
little
more
so
yeah.
A
All
right,
we
have
only
three
minutes
left.
Thank
you,
enoch
and
matt
you're
awesome.
We
heart
you
you're
great,
but
we
have
three
minutes
left
and
I
see
there
is
a
couple
more
things
to
talk
about.
Matt
did
you
want
to
bring
some
updates
from
the
agency?
We.
A
And
then
real
quick,
the
call
for
participation
in
she
code,
africa.
We
do
need
a
mentor
who
can
code
kind
of
struggling
with
that
application,
because
you
do,
we
do
have
to
list
out
the
tasks
for
a
slack
bot.
I
don't
know
if
anybody
would
be
interested
in
helping
ruth
and
I
mentor
this
person,
or
maybe
we
can
mention
it
also
in
the
community
call
next
week.
C
Hi
so
elizabeth,
if
so,
it's
required
to
have
technical
skills
right,
okay,
yeah!
I
I
wanted
to
help,
but
I
don't
have
no,
I
think
so.
Yeah
yeah.
E
It
might
be
worth
I
I
believe
I
believe
among
like
you
and
ruth
there.
There
would
be
enough
there
that
we
could
work
out
the
technical
part
of
it
or
we
could
find
someone
closer
to
the
time
as
long
as
we
have
at
least
one
or
two
people
to
commit
to
the
role
we
can
have.
I
think
we
can
have
more
than
two
mentors.
A
Okay,
that
would
be
perfect,
because
you
know
ruth
and
I
are
gonna
co-mentor,
I
think
also,
so
it
would
not
be
like
a
full-time
mentorship.
It
would
just
be
you
know
if
this
person
gets
stuck
on
the
code
and
needs
some
technical
guidance
like
I
don't
know
that
I'm
the
best
person,
because
I
haven't
written
a
slack
button
in
literally
10
years,
so.
E
Yeah,
what's
what's
the
period
for
that
for
that
she
called
africa
mentorship.
A
Okay,
well,
we'll
sort
it
out
we'll
we'll
figure
that
out
I'm
meeting
with
ruth
tomorrow.
So
we'll
talk
about
it,
we'll
we'll
get
it
all
sorted
out.
A
A
You
know
I
wanted
to
maybe
provide
a
little
more
but
yeah
ruth,
and
I
will
talk
about
it
tomorrow,
too,
and
kind
of
where,
where
we
are,
maybe
it's
fine
she's
been
through
the
project
or
the
program
before
so
maybe
it's
fine
to
leave
it
a
little
more
ambiguous
and
not
have
to
have
everything
immediately
sorted,
but.
F
A
We'll
holler
at
you
all
if
we
need
some
help
for
sure
and
then
we're
out
of
time.
But
I
see
this
badging
bot
google
summer
of
code
link
real
quick
here's
where
we're
dropping
the
ideas
for
our
google
summer
of
code
projects.
So
if
I'm,
assuming
somebody
put
this
on
here,
to
look
for
more
dei
ideas.
E
Either
more
ideas
or
more,
we
also
need
mentors
for
the
for
the
badging
about
stuff.
So
we'll
we'll
be
I'll
talk
about
that
more
next
time.