►
From YouTube: CHAOSS DEI Working Group 2/16/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
Boo
on
the
trends,
bad
update,
all
right
anyway,
I'm
gonna
share
my
screen
brain
all
right,
so
welcome
everybody.
A
You
can
add
yourself
that
would
be
most
excellent,
I'll
go
ahead
and
facilitate
today,
I
kind
of
put
together
the
agenda.
Would
somebody
like
to
take
on
facilitating
in
on
the
23rd.
B
A
That's
all
right,
facilitation
is
just
kind
of
you
know.
It's
just
moving
us
through
the
agenda.
You
know
what
I
mean:
it's
mostly
just
setting
the
agenda
and
then
just
moving
us
through
the
agenda.
So
all
right,
so
I
thought
we'd
start
today
by
taking
a
look
at
our
project
overview.
A
So
this
is
the
work
that
justin
had
done
with
the
project,
and
I
really
liked
the
looks
of
this.
A
So
this
is
a
way
for
us
to
kind
of
take
a
look
at
any
metric
ideas
that
we
have,
which
I
don't
think
we're
gonna
touch
too
much
today
any
to
do's
and
then
things
that
we've
completed.
So
I
think
we're
looking
pretty
good
in
terms
of
in
progress.
There
are
a
few
that
we
could
take
a
look
at
and
we
don't
have
to
follow
through
on
them
necessarily.
A
C
I
think
it's
an
awesome
idea
and
I
think
it
stemmed
from
the
fact
that
we
wanted
to
broaden
the
metrics
that
we
were
looking
at.
So.
D
C
Wouldn't
just
be
focusing
on
metrics
that,
were
you
know,
applicable
to
this
group
or
that
this
group,
that
being
said,
we
we
do
have
a
quite
a
bit
of
a
backlog.
So
I
think
that
that
is
a
great
thing
to
do.
A
little
later
in
the
year.
Okay,
make
sure
that
you
know
the
the
people
who
are
working
on
these
metrics
and
bringing
these
ideas.
That
group
is
also
diverse
as
possible.
A
You
know
what
I
mean
like
add
to
that
issue.
I
can
go
to
the
full
issue.
Elizabeth.
Maybe
could
you
add
that
small
comment
to
the
issue
just
so
we
know
that
it's
we're
looking
at
it
and
that
maybe
just
to
address
we
want
to
address,
maybe
the
backlog
of
metric
ideas.
First,
I
think
that's
what
you're,
referring
to
kind
of
this
list
over
here.
C
A
A
Okay,
thank
you.
Look
at
how
awesome
this
project
board
is
to
be
honest
with
you
like.
I,
don't.
We've
never
really
been
able
to
work
through
things
quite
like
this,
so
this
is
great,
so
justin
you're
not
on,
but
thank
you
release
notes.
This
is
just
kind
of
our
ongoing
notes
that
we
have
as
we're
releasing
things.
So
that's
not.
Okay,.
E
We're
reporting
but
number
three:
we
that's
a
released
metric
at
this
point.
You
can
close
that
issue.
It
was
just
tracking
the
beginning
of
that
process.
A
A
So
inclusive
naming.
E
Matt
yeah,
we
talked
about
this
for
a
while.
I
I
just
put
together
the
list
of
things
that
we
need
to
look
for
and
change.
That's
that's
all
that
is.
A
A
E
C
This
might
be
a
good
google
summer
of
code
project
because
I
think
I
could
be
wrong,
but
I
think
the
ini,
inclusive
naming
initiative
has
a
tool
that
will
scan
through
and
grab
them
for
you.
But
we
would
need
someone
to
kind
of
manage
that
and
do
that,
so
it
wouldn't
be
like
manually
someone
going
through
and
but
it
would
set
that
process
in
place
for
it
to
like
be
part
of
mars,
for
instance,
or
part
of
the
check
or
something
I
don't
know,
just
an
idea.
There
might.
A
A
D
A
E
E
A
All
right
all
right,
and
then
this
is
just
some
tracking
work.
So
honestly,
this
is
that
was
it
for
our
tasks.
So
thank
you,
everybody
for
that,
and
I
the
reason
I
kind
of
like
this
too,
is
that,
instead
of
just
going
through
our
pull
requests
and
our
issues,
this
kind
of
locates
us
a
little
bit
faster,
the
things
that
need
attention
so
again
huge
kudos
to
to
justin
all
right.
So
we,
the
second
thing
we
have
here,
did
anybody
have
any
other
comments
on
the
project
board
for
dei.
D
So
I
have
something
if
you
want
match,
I
can
help
you
out
with
that.
Do
you
like
to
do
together
the
proposal?
I
have
a
bit
of
experience
with
that,
so
maybe
we
can
work
on
it.
It's
fine
for
you,
yeah.
E
That
sounds
great.
I'm
gonna
put
it
in
a
google
doc
and
I'll.
Send
it
I'll.
Send
you
a
link
to
that
I'll
also
send
it
to
the.
A
So
christy
just
from
a
process
perspective,
so
we
the
way
that
we
do
it
and
it
may
be
a
different
as
to
how
you've
done
it.
But
we
so
we
went
ahead
and
did
the
organizational
proposal
for
g-sock.
So
that's
already
in
and
then
we
just
we
collect
ideas
from
different
potential
mentors
across
the
chaos
project,
so
like
matt
or
sean
elizabeth,
and
then
we
have
so
we
just
kind
of
describe
what
that
task
would
be
on
a
in
a
markdown
file.
A
And
then
we
have
like
a
micro
task
that
we
ask
the
potential
applicants
to
do
associated
with
one
particular
topic
that
they're
interested
in
just
to
kind
of
see.
If
they
you
know,
are
in
a
good
place
to
work
with
us
over
a
course
of
summer
and
then
we
go
ahead
and
we
have
them
submit
their
microtask
work.
And
then
that
gives
us
something
to
review
when
we're
reviewing
applicants
for
google
summer
of
code.
So
that
may
be
the
process
similar
to
what
you
had
done
in
the
past.
A
A
Good,
could
somebody
drop
the
minutes
in
for
justin
if
they
haven't.
A
Awesome,
we
must
do
this
in
the
other
working
groups
too.
It
really
helped
us
kind
of
focus
on
these
tasks
and
to
do's
quite
well
all
right.
So
the
metric
idea,
elizabeth-
this
was
yours
event,
accessibility.
I
don't
know
if
you
have
any
departments
on
this
or.
C
Yeah
I
did
start
building
it
out.
I
saw
christy
was
in
there
also
adding
some
comments
and
I
did
bring
it
up
in
the
dei.
Badging
weekly
call
as
well
in
case
since
this
is
kind
of
was
the
inspiration
for
this
was
the
dei
badging
initiative.
So
I'm
not
sure
we
might
have
some
of
those
individuals
contributing
as
well,
but
I
mean
it's
it's
getting
there
like.
I
don't
know
if
we
want
to
work
on
it
if
we
have
time
or
what,
whatever
you
want
to
do.
A
A
Okay,
why
don't.
F
C
A
C
I
also
would
really
love
input
on
actually
how
to
measure
this,
because
I
don't
like
it's
not
something
that
we
would
like
survey
people.
I
think
it's
it's,
that
it
would
be
the
organizer
just
keeping
track
of
what
measures
they're
doing
and
like
that's
their
metric.
C
A
Yeah,
I
mean
maybe
it's
to
me.
It
feels
a
little
like
like
honestly,
like
code
of
conduct
like
we
just
asked
to
see
it
yeah.
C
A
A
Rain
all
right,
so
I
just
this
is
an
update.
I
really
honestly
think
that
maybe
elizabeth
will
work
on
when
you
bring
this
one
back
next
week.
Event:
accessibility,
I'll
talk
about
project
demographics,
like
the
the
short
comment
here
is,
I
think
it's
largely
done,
but
there's
something
else.
I
kind
of
want
to
talk
about
a
little
bit
today.
A
A
And
so
really
at
this
point,
it's
just
adding
yourself
as
a
contributor,
if
you
feel
like
you,
have
contributed
to
this
metric.
But
overall,
I
think
it's
it's
coming
along
pretty
well
and
based
on.
I
think
we
worked
on
this
a
week
ago
as
a
group,
and
so
I
just
cleaned
everything
up.
So
maybe
we
can
just
finalize
this
next
week
when
we
finalize
the
event
accessibility,
because
maybe
that
shouldn't
take
too
long,
okay,
all
right.
So
I
I
wanted
to
talk
just
a
little
bit
about
our
privacy
and
ethics
documents.
A
A
No,
for
some
reason
I
was
just
signed
out
as
chaos
community,
because
somebody
else
signed
in
maybe
there's
another
meeting
going
on
somewhere
or.
A
So
I
don't
know
if
this
fits
in
dei.
I
don't
want
to
overload
common
all
the
time,
but
we
just
need
some
place
where
we
need
to
sort
this
out,
and
this
is
to
some
degree
driving
me
crazy,
because
I
feel
like
we
have
these
things
all
over
the
place.
A
So
right
now
we
have
a
data
policy
document
that
is
posted
here
all
right
and
this
talks
about
how
we
as
a
community,
handle
data
with
respect
to
privacy
for
things
that
we
collect
like
the
the
stuff
that
happens
within
the
chaos
project
or
at
our
events
like
so
that's.
This
is
one
data
project
policy
and
I'm
okay
with
this,
and
I
think
it's
a
little
bit
different
than
the
rest.
So
so
far
so
good.
A
We
have
this
statement
in
the
metrics
template
that,
if
you
didn't
notice
is
somewhere
in
here
it's
here,
so
we
now
have
this
statement
in
the
metrics
template
that
says
the
use.
It's
basically
saying
you
know
if
you're
going
to
use
this
metric,
this
may
come
with
data
collection
associated
with
it.
You
being
the
user
of
the
metric,
not
you
being
a
chaos
community
member.
You
need
to
think
about
so.
A
B
So
having
individual
metrics
have
a
pointer
to
a
standard
data
use
document
that
makes
sense
to
me
and
the
state
the
the
statement.
The
brief
statement
also
makes
sense
because
it
puts
it
in
the
context
of
hey
you're
using
a
metric,
and
these
are
the
things
that
get
consumed
or
collected
and
be
careful
and
here's
the
details
on
being
careful,
but
I
suspect
it
gets
more
complex
from
here,
so
we
we
also
then
have
this.
A
B
A
So
are
you
following
so
far
we
have
like?
We
have
our
own
privacy
statement,
which
I
think
is
separate
from
this,
and
then
we
have
a
disclaimer,
that's
in
the
metrics
template
and
we
have
a
disclaimer,
that's
at
the
top
of
the
metrics
page,
all
right.
So
to
me
this
is,
and
then
we
have
it.
So
this
is
the
disclaimer
at
the
top
of
the
metrics
page.
A
A
All
right,
so
this
is
the
one
that
I've
been
working
on.
This
is
the
one
that
lucas
has
been
working
on.
This
is
the
one
that
sophia's
been
working
on
elizabeth.
You
had
put
a
bunch
of
comments
in
here
as
well.
That's
this
document
all
right,
I'm
not
asking
you
to
go
through
this
document
at
this
point,
but
this
is
just
things
to
consider
and
then
here's
some
existing
kind
of
a
list
of
existing
regulation
around
privacy
all
right.
A
A
So
like
when
we
are
in
you
know,
when
we
have
this
implementation
statement,
which
is,
I
showed
you
on
that
last
page,
when
we
say,
please
see
the
chaos
data
ethics
document,
it
links
to
what's
what's
currently
called
privacy
regulation
relevant
to
the
use
of
open
source
software
metrics
are
any
people.
Are
your?
Are
your
brains
doing
with
all
of
this,
because
there's
a
lot
of
documents
I'm
trying
to
like
I've
got
to
unravel.
This
is
silly
that
we
have
so
many
documents
right
now.
A
A
A
Looks
like
an
old
version
of
no
of
this,
like
we
have
like
these
three
documents,
this
one
that
is
appears
to
be
the
most
recent.
This
is
the
one
that
christy
was
like.
What's
that
and
I
couldn't
answer,
and
then
we
have
this
one
which
sophia
had
was
working
on
a
little
bit,
and
this
is
what
kind
of
prompted
all
of
this
so
thoughts
on
this
one.
A
C
A
A
A
Then
I
kept
wondering
I'm
like:
why
am
I
so
confused
on
this
issue
like
why?
Why
can't
I
seem
to
track
what's
going
on
here
and
I
figured
out
why
all
right
so
I'll
take
an
action
item
to
merge
these
three
and
we
would
just
have
one,
and
I
think
it
would
show
up
elizabeth
in
the
community
repository.
A
C
A
A
So
should
we
keep
both,
they
should
probably
say
the
exact
same
thing
if
we
keep
both
and
they
don't
currently
say
the
exact
same
thing
and
the
only
reason
that
it
might
be
useful
to
keep
it
here
is
not
all
of
our
older
released.
Metrics
necessarily
have
that
disclaimer
in
there,
because
this
disclaimer
is
a
relatively
new
addition
to
the
metrics
template.
A
A
Okay,
cool
justin
you're
putting
some
comments
in
there.
I
don't
know
if
you
are
able
to
unmute
and
tell
us
what
you're
talking.
A
That
I
so.
D
F
Week
I
attended,
I
was
attending
an
ieee
standards.
Association
was
like
making
a
working
group
and
it
was
like
understanding
that
whole
process
for
the
first
time-
and
one
thing
I
thought
was
neat-
is
how
they
classify
things
like
things
across
like
standards,
recommended
practices
and
guides,
and
they
the
main
there's
a
couple
of
things
that
are
different,
but
they
use
different
verbs
to
kind
of
classify
those
different
documents
where,
like
a
standard,
uses
shell,
because
that's
something
you
have
to
do
to
comply.
So
it's
a
must.
F
Whereas,
like
a
recommended
practice
this
should
they
recommend
that
you
do
these
things
and
then
for
guides
they
use
like
the
word.
May
you
may
do
this
to
be
kind
of
more
flexible
or
permissible
of
how
people
are
supposed
to
take
away
what
their
interpretation
should
be.
So
I
was
thinking
of
these
documents,
like
maybe
there's
a
way
of
like
like
separating
this
out,
and
maybe,
if
we're
combining
documents
down
into
one
thing,
just
being
really
consistent
on
the
language.
A
Yeah,
I
think,
in
this
case
I
put
in
the
comments
I
think
we're
should,
in
this
case
we're
kind
of
handing
these
over.
I
really
think
you
should
think
about
these
things.
You
don't
have
to
if
you
don't
want
to,
but
you
really
should
do
that.
So
I
like
the
way
you
put
it
all
right,
cool
all
right
great.
Thank
you
everybody.
A
I
guess
in
the
last
few
minutes
elizabeth
did
you
have
anything
you
want
to
talk
about
with
onboarding
specific
to
this
group.
I
know
you
talked
about
it.
A
little
bit
yesterday
in
the
community
call
the
things
you
want
to
bring
forward
here.
A
C
So
the
the
question
remains
of
being
a
mentor
for
someone
to
write
the
slack
bot
ruth
didn't
feel
comfortable.
Doing
that
I
could.
But
it's
been
like
five
years
since
I
wrote
a
slack
bot,
so
I
don't
know
if
I
would
be
a
very
good
mentor.
So
we
would
just
need
to
find
someone
willing
to
mentor
that,
but
then
it
flips-
because
I
you
know
ruth-
was
very
interested
in
mentoring
since
she
had
already
gone
through
that
project
or
that
cohort.
C
A
Okay,
it
would
be
possible,
maybe
for
if
ruth
wanted
to
be.
D
You
ever
comment,
sorry,
just
a
big
question.
Yes,
can
you
please
give
me
a
little
bit
of
context?
What
is
she
called
africa?
C
An
event
or
yeah,
it's
like
a
mentorship
program,
very
similar
to
google
summer
of
code,
but
it's
geared
towards
bringing
women
in
africa
into
coding.
So
it's
specifically
for
women
in
africa.
It's
a
two
month,
cohort
ruth
ikega,
who
is
usually
on
this
in
this
group.
She,
oh
you
know
ruth
oh
yeah.
She
had
gone
through
that,
and
so
it's
like
a
two
month
did
I
say
that
already
two
month
cohort,
the
deadline
to
apply
is
february.
C
28Th,
though,
so
it's
coming
up
very
soon
and
we
would
have
to
have
all
our
tasks
subtasks
and
everything
already
set.
I
think
when
we
apply
so
does
that
give
you
a
little
more
context.
D
Yes,
so
if
I
would
like,
for
example,
to
have
to
help
ruth
or
probably
to
participate
as
a
mentor,
I
don't
know,
I
guess
that
one
requirement
should
be
to
code.
C
D
A
My
my
thought
is
through
people
in
the
chaos
project
who
have
worked
in
slack
and
have
created
slack
bots.
I
mean
we
have
an
availability
of
enough
people
who
have
kind
of
been
through
this
before
and
mentorship
is
so
many
things
more
than
just
writing
code,
and
so
I
I'm
I'm,
I'm
actually
really
inclined
to
to
do
this
and
we
can
figure
out
the
technical
support
just
as
we
move
forward.
That's
that's
my
inclination.