►
From YouTube: CHAOSS DEI Working Group Feb 22 2023
Description
Minutes from this meeting can be found here: https://docs.google.com/document/d/1MzDk84BL7FfHDxbFxJz39M72V2Hfc5Y6oCPhOl6woxo/edit#heading=h.n3rh3l1y6dv7
A
Just
a
quick
reminder:
we
try
to
do
this
every
meeting
this
meeting
is
under
the
chaos
code
of
conduct.
So
just
keep
that
in
mind
and
use
your
best
self
here
and
also
this
meeting
is
to
talk
about
diversity,
equity
and
inclusion
in
in
chaos
in
metrics,
whatever
kind
of
pops
up
around
those
topics,
the
agenda's
in
the
minutes,
but
if,
in
terms
of
the
minutes
agenda's
in
the
chat,
I
got
it
I'm
one
here,
I'm
with
it,
it.
B
A
And
if
you
don't
mind
to
put
your
name
in
the
in
the
agenda
here
under
attendees,
that
would
be
great.
If
you
don't
want
to
that's.
Also
fine
and
just
also
a
reminder,
you
can
keep
your
cameras
off
here
at
chaos.
We
we
really
don't
mind
at
all
and
you're
welcome
to
just
chat
in
the
chat
window.
If
you
don't
even
feel
like
turning
your
mic
on
that's
also
totally
fine.
A
A
A
The
purpose
of
this
tour
guide
group
would
be
to
be
able
to
provide
a
little
one-on-one
assistance
for
folks
who
are
new
to
chaos
and
kind
of
struggling
trying
to
find
their
way,
because,
right
now,
mostly
it's
myself
and
Ruth,
and
maybe
a
few
others,
maybe
one
or
two
others-
that
kind
of
field
a
lot
of
those
requests
and
a
lot
of
that
that
traffic.
So
we
were
trying
to
help
spread
the
spread,
the
love
a
little
and
then
like
Build
A
team
out.
A
That
can
help
with
that
and
we
decided
to
call
ourselves
tour
guides
because
we're
going
to
help
folks
find
their
way.
Mary
blessing
has
been
kind
enough
to
agree
to
to
lead
this
team
and
really
kind
of
build.
This
out.
She
has
been
such
a
great
asset
in
in
chaos,
extremely
welcoming
and
helpful
to
newcomers
already,
and
she
does
have
a
Community
Management
background.
So
I'm
super
happy
to
be
kind
of
handing
this
off
to
her
to
kind
of
run.
A
There
is
a
slack
Channel,
I
think
I'm
just
going
to
scroll
down
here
for
a
minute,
I,
don't
know
if
it's
in
here
or
maybe
from
before.
Here
we
go
there's
a
dock
here,
yep
see
here's
Mary
already
commenting.
We
have
a
doc
here
that
we
had
just
been
dumping.
Some
ideas
in
here
were
the
folks
that
had
originally
stepped
up
to
be
a
part
of
that.
If
you
are
interested
in
participating
just
reach
out
to
Mary
blessing
she'll,
add
you
to.
A
I
know,
there's
been
concern
too
I'll
just
say
real
quickly.
I
know
there's
been
concern
about
the
volume
of
requests,
because
we
do
have
quite
a
few
newcomers,
too
chaos
pretty
consistently.
We
pretty
much
have
two
to
three
new
members
every
day
that
come
to
chaos,
not
everybody
sticks
around,
of
course,
but
we
do
have.
You
know
a
pretty
fair,
consistent
flow,
and
so
there
is
a
potential
for
that
group
to
be
kind
of
overwhelmed
with
requests
for
help.
A
So
what
we
decided
in
the
last
meet
well
Ruth
and
Mary
blessing
and
I
met
to
talk
kind
of
talk,
things
out
a
little
bit
as
far
as
implementation
goes
and
we're
going
to
start
with
mentioning
at
the
end
of
our
onboarding
calls
which
happen
once
a
month,
because
we
kind
of
that
way.
We
know
that
it's
someone,
that's
super
interested
in
being
part
of
the
community
they've
they've,
taken
that
step
to
join
the
call
or
watch
the
video
they've
they've
gone
through
that
quick
start
for
newcomers.
A
So
there's
a
little
bit
of
a
barrier
to
still
just
enough
just
enough
to
kind
of
help
us
sort
things
out
first
and
then
eventually
we
will
add
that
to
the
slack
bot.
That's
that's
kind
of
our
next
step.
If,
if
this
works
the
way
it
should
and
we
feel
like,
we
can
handle
a
larger
load,
We'll
add
it
to
that
newbie
slack
bot
and,
as
a
matter
of
fact,
precious
a
has
already
written
or
not
precious.
Someone,
oh
I,
forget
who
someone
already
wrote
the
code
precious
a
already
looked
at
it
and.
A
A
C
A
A
B
A
A
A
B
B
D
B
C
B
C
A
A
C
D
B
B
A
B
B
C
E
I
think
we've
had
like
so
many
contributors
like
recently
and
to
make
this
more
like
accommodates
more
room.
We
could
try
to
use
so
there's
this
software
I
be
like
yeah.
It's
like
a
software
that
at
least
out
odd
people
to
have
made
like
contributions
to
the
particular
repository
like
brings
out
the
picture
of
their
of
their
GitHub
profile,
image
and
I.
Think
you
can
find
it
on
this
repository
here
so
like
that
will
cover
more
persons,
because
we've
had
like
more
persons
within
the
community
of
late
I.
C
F
Yeah
I,
actually
I
was
gonna
speak
to
what
matters
raised.
I
think
if
there's
a
way
to
do
this,
that
captures
folks
who
have
contributed
but
not
made
commits
to
the
repo,
because
I
think
that's
how
it's
identifying
contributors
and
I
know
GitHub
does
have
some
fancy
ways
to
attribute
things.
Call
people
contributors
who
haven't
made
commits
so
maybe
there's
a
little
bit
of
workaround
needed
to
make
that
a
fit,
but
it
I
do
love.
D
D
B
B
C
B
B
B
A
Like
I
think,
the
only
thing
that
we
have
and
that
we're
working
on
is
that
path
to
contribution
which
is
like
the
quick
start
and
then
there's
a
page
for
participating
and
then
there's
another
step,
another
page
or
contributing.
But
that's
not
the
same
as
a
core
contributor
versus
the
maintainer.
So.
G
B
B
C
A
C
G
G
D
A
B
D
E
D
C
C
A
About
adding
these
metrics
to
the
bot
and
so
I'm
gonna
make
the
changes.
I
started,
making
the
changes,
but
I'm
gonna
make
them
in
a
different
way
now.
So
it
was
good
that
I
had
a
good
chat
with
him
about
that
before
I.
Just
did
it.
So
yes,
so
hopefully,
by
the
end.
Well,
I,
don't
know
I
want
to
say
by
the
end
of
the
week,
but
it's
really
close,
maybe
middle
of
next
week,
we'll
have
those
added.
A
So
I'm
a
little
stuck
but
yeah
we
we
talked
Enoch
and
I,
talked
about
too
something
that
we
need
to
solve
and
we
don't
know
how
to
solve
this.
Yet
is
collecting
direct
emails
from
folks
who
submit
applications,
because
we
don't
do
that
right
now
we
don't,
we
don't
collect
their
name
or
their
information.
Their
email
address.
E
A
And
the
reason
is
because
we
didn't
want
to
put
that
in
a
public
issue
that
everybody
can
see
like
they're.
You
know
what
I
mean
yeah,
so
we're
trying
to
figure
out
a
way
that
we
can
collect
that
information
without
posting
it
publicly
but
store
it
someplace
securely
for
us
to
use
in
case.
We
need
to
reach
out
directly
to
the
event
organizers,
so
yeah.
B
G
A
G
A
A
A
Yeah
because
there
have
been
times
even
before
we
wanted
to
start
this
event.
Organizer
group,
that,
like
the
event,
organizer
hasn't,
responded
and
I,
think
it's
just
because
they're
not
getting
the
GitHub
notifications
so
like
we
just
need
a
secondary
way
to
you,
know,
reach
out
to
them
and
and
have
them
have
that
that
connection
so
yeah.
That
would
be
good,
we'll
think
about
that.
A
little
bit.
A
B
A
A
B
A
Delight
is
also
reminding
me
that
we
have
a
design
for
a
hundred
badges,
which
I
think
we
have
met.
That
I
should
have
I
should
have
said
that
earlier
I
think
we've
met
our
100
badge,
a
hundredth
badged
event.
So
maybe
we
should
work
with
the
communications
working
group
to
figure
out
like
what
how
we
want
to
announce
that
and
make
a
big
deal
about
it,
because
it's
kind
of
cool
Delight.
Would
you
mind
putting
a
link
in
here
in
the
chat
to
that
badge
design
or
to
that
award.
B
B
B
C
A
A
Kingsley
was
involved
too
yeah.
Congratulations
to
both
of
you
for
doing
that.
We
really
appreciate
that
and
we
will
definitely
use
that
in
our
social
media
campaign
love
it
I'm
gonna
put
this
link
here
in
a
minute,
so
you
don't
forget,
and
then
we
have
our
Communications
meeting
tomorrow,
so
we'll
bring
this
up
and
figure
out
how
to
how
to
spread.
The
word.