►
From YouTube: CHAOSS DEI Working Group 2/9/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
All
right,
hi,
everybody
welcome
to
the
february
9th
chaos
dei
working
group
meeting
2022.,
it's
great
to
have
you
here.
If
you
could
add
yourself
to
the
agenda,
that
would
be
wonderful.
A
So
elizabeth
just
put
the
minutes
back
in
the
chat,
a
few
things
that
we
need
to
kind
of
address
today.
I
think
today
I
think
our
items
are
the
first
one
is
something
from
dei
badging.
The
second
is
about
taking
retaking
a
look
at
our
metrics
again
and
just
trying
to
get
some
closure
on
some
that
are
moving
forward
and
then
I'll
talk
a
little
bit
about
the
dot
github
stuff,
hey
shoya,.
A
The
reason
I'd
bring
it
up
here
is
because
justin
had
brought
it
up
here
last
time
and
I
think
it
standardizes
a
few
things
from
an
issue
template
and
then
it
also,
I
think
it's
a
way
for
us
to
distribute
the
code
of
conduct
more
evenly
in
the
project
which
is
good
for
us,
so
all
right,
cool
all
right.
So
who
put
this
first
one?
I
can
share
my
screen.
Elizabeth
put
the
first
one
up
here.
You
want
to
go
ahead
and
talk
us
through
that.
A
little
bit
all.
D
Right
it,
so
this
was
there's
an
issue
linked
there
that
was
put
in
the
dei
badging
repo
a
few
months
ago,
and
there
was
some
discussion
and
I
think
matt
cantu
also
had
acknowledged
that
it's
it's
a
gap
in
our
dei
badging
initiative.
Is
this
idea
around
accessibility
at
events-
and
I
know
we've
talked
about
it
a
lot,
but
we
had.
We
really
don't
have
any
metrics
to
for
the
dei
badging
program
to
use
in
the
checks.
So
I
kind
of
bumped
this
up
to
the
queue.
Sorry.
D
D
Yeah
event:
accessibility
right
there
in
progress,
go
on
gotcha,
okay,.
D
I
hope
that's
okay,
but
it's
really
like
empty.
The
metrics
template
only
has
a
few
things.
I've
added
in
so
I'll
continue
to
work
on
that
and
then
I'll
bring
it
back
to
the
group
for
this.
A
A
A
Got
it
that
makes
a
ton
of
sense,
and
I
think
this
is
this
works
well
too,
because
as
we
have
the
metrics
models,
you
know
so
so
we
have
a
working
group
called
metrics
models,
which
is
a
working
group
that
talks
about
how
we
bring
different
individual
metrics
together
in
meaningful
ways
for
people
and
we're
working
on
a
variety
of
different
metrics
models.
We
have
this
tab
here,
so
these
are
the
metrics
models
and
they
bring
together
metrics
in
a
variety
of
different
ways
and
dei
event.
A
Badging
is
one
of
those
metrics
models
because
it
inherently
brings
together
a
collection
of
these
metrics
into
the
badging
program.
So
the
dei
badging
program
is
itself
a
metrics
model,
and
so
we've
we've
kind
of
come
up
with
a
workflow
that
says
if
the
metrics
model
would
like
to
add
a
new
metric
to
the
model,
meaning
that
there's
a
gap
in
the
model,
perhaps
or
there's
just
something
that
could
be
improved
in
the
model
that
they
send
the
request
to
probably
the
most
respective
working
group
that
would
handle
that
additional
metrics.
A
I
think
elizabeth
you're
just
kind
of
following
that
approach.
The
the
dei
badging
group
is
essentially
a
whole
group
dedicated
to
just
that
model,
which
is
interesting
and
then
kind
of
pushing
this
back
to
the
dei
working
group.
D
A
You
know
actually,
before
I
came
to
this
meeting,
I'm
like
like
because
we
have
these
things.
We
have
all
these
workflows,
which
is
like
like
what
you're
talking
about
here.
You
know
what
I
mean
and
another
workflow
is
like
when
we
review
a
metric
and
then
get
it
back
out.
You
know
what
I
mean
and
I'm.
C
D
A
All
right:
do
you
want
to
talk
about
this
at
all
right
now,
elizabeth
or
is
it?
Is
it
just
something
that
not
project
demographics
event?
Accessibility?
Is
it
something
that
you
want
to
talk
about
now
or
do
you
just
want
to
work
on
it
and
then
maybe
bring
it
back
to
the
group.
A
E
D
Since
it
is
so
early,
you
know
I
just
had
some
initial
thoughts
but-
and
we
do
have
other
stuff
to
talk
about,
so
it's
totally
fine.
A
No,
that's!
That's
all
good
all
right
cool
when.
A
D
A
D
D
A
A
Great,
thank
you
all
right.
The
next
thing
I
thought
we
could
maybe
spend
a
little
bit
of
time
today,
kind
of
working
through
project
demographics.
A
So
the
indenting
is
a
little
different
so
event,
so
we
have
event
demographics.
I
was.
A
Demographics
in
there
just
because
it
could
serve
as
an
example
for
project
demographics,
so
we
have
event
demographics
as
a
released
metric,
and
if
you
recall,
as
part
of
this
process,
we
used
to
have
speaker
demographics
and
attendee
demographics
here,
and
we
said
that's
just
too
much
to
it's
silly
to
keep
these
separate.
Why
don't?
We
just
have
something
called
event:
demographics,
which
we
have
at
this
point.
A
So
sometimes
to
the
point
we
were
just
talking
about
it's
it's
kind
of
easy.
Sometimes
if
we
have
metrics
that
are
similar
to
one
another
to
almost
just
copy
and
paste
what
we
have.
I'm
not
saying
just
do
this,
but
like
copy
and
paste
what
we
have
in
event,
demographics
and
put
it
in
project
demographics
and
then
just
find
and
replace
event
with
project.
E
You
know
I'm
looking
at
the
event
demographics
metric
and
it
might
be
worth
it
to
take
event,
demographics
and
kind
of
put
the
project
part
in
there,
but
it
doesn't
seem
like
it's
super
specific
to
events
in
that
metric,
so
it
might
be
worth
it
to
differentiate
them
in
both
directions
like
to
the
event
side
to
the
project
side,
because
this
one
kind
of
is
the
current
event.
Demographics
metric
can
be
generalized
pretty
well.
A
A
All
right
well,
could
we
maybe
without
touching
this
one
first,
could
I
maybe
pause
the
recording
for
a
second
and
then
we
spend
just
a
few
minutes.
A
A
I
yeah,
I
was
wondering
if
we
could
use
as
examples.
We
have
the
open
demographic
questions.
We
have
the
questions
that
were
asked
for
the
lf
dei
survey.
A
So,
if
I
don't
know,
if
anybody
has
that
accessible-
probably
not
immediately
yeah
exactly
so,
I
think
this
one
at
this
moment
is
really
the
only
way
that
we
can
get
this
data.
I
don't
unders.
I
don't
know
if
there's
really
any
other
way,
that
we
can
get
this
data
elizabeth.
Do
you
have
thoughts
on
this.
D
I
know
we've
talked
about
this
before
I
I
mean
you,
you
could
try
to
gather
simple
things
like
location
like
in
the
github
like
if
someone
has
given
you
that
information,
but
it's
you
know
it's,
it's
not
great
data
like
it's,
you
know
totally.
Can
just
people
can
put
earth
you
know
for
their
location.
So
it's
not
super
super
helpful
to
do
that,
but
you
can
do
it
if
you
don't
have
any
other
way
to
do
it.
E
Not
only
that,
but
we're
also
promoting
good
ethics,
and
I
feel
like
consent
is
a
really
big
part
of
data
collection.
So
I
feel
like
surveyed
with
explicit
consent.
Really
is
the
only
thing
I
can.
I
could
think
of.
A
E
A
Think
with
events,
you
have
a
few
opportunities
to
do
that,
perhaps
even
more
so
than
you
do
with
a
project.
To
be
honest
with
you,
because
you
have
to
register
for
an
event,
you
don't
have
to
register
for
a
project,
so
I
might
my
my
thought
was
yeah
that
we
could
just
build
this
out
a
little
bit
and
give
some
real
examples
of
questions
that
could
be
asked
with
respect
to
demographics.
B
Yeah-
and
I
guess
I
was
kind
of
taking
this
a
little
bit-
I
might
have
been
a
bit
a
little
confused
meaning
I
was
taking
this
a
little
bit
differently
when
I
was
going
through
it.
It
was
oh
we're
trying
to.
B
I
don't
know
if
I
was
taking
it
as
demographics
as
much
as
we're
really
trying
to
query
folks
as
to
folks
within
a
given
community
as
to
whether
or
not
they
think
that
particular.
B
Right
like
what
has
been
your
experience
in
xyz
project,
do
you
feel
like
it's?
Has
your
experience
within
a
particular
project
been,
you
know,
adhered
to
the
principles
of
diversity,
equity
and
inclusion.
A
So
at
point
well
taken
we,
I
don't
know
nicole,
if
you
can
see
my
screen
or
not,
but
we
have.
We
have
a
metric
called
inclusive
experience
at
an
event
which
is
kind
of.
I
think
it's
in
line
with
what
you're
talking
about
now.
That's
granted
it's
only
at
an
event,
but
I
mean
we
could
with
respect
to
project
and
community.
B
Oh
that
may
yeah
yeah.
I
I
think
that
probably
just
kind
of
looking
at
it
here
would
would
would
probably
fit
them
the
closest
to.
B
E
So
psychological
safety
is
a
safety
net
in
case,
be
preventative
or
responsive
to
issues
like
a
centered
around
issues.
I
added
a
considering
item
for
project
operation
inclusivity.
That's
just
a
name,
I'm
throwing
out
there
or
like
oh
in
the
spreadsheet,
right
under
project
demographics,
but
I'm
thinking
like
when
I
think
about
this.
This
is
this
is
a
gap
for
sure
and
it
could
be
like
how
do
how
welcoming
is
your
project
as
simple
as
that
I
mean
that
could
be
the
question
even.
D
That's
actually
a
metrics
model
is
welcoming
this
in
a
project
so.
E
Yeah,
that's
why
I
put
operation
too,
because
it
has
to
be
something
specific
like
what?
What
efforts
does
your
project
take
to
ensure
that
it's
welcoming
to
new
community
members?
It
has
to
be
kind
of
specific,
but.
C
I'm
I'm
not
sure
if
I
missed
this
kind
of
discussion,
but
have
we
discussed
the
border
borderline
of
like
what
is
a
project
or
project
community,
because
I
I'm
not
sure
if
this
would
influence
them
the
way
how
we
collect
the
demographic
data
like
we
can
send.
We
can
we
we
can.
C
We
can
proceed
this
by
sending
surveys,
but
if
we
have
a
more
clear
boundary
of
the
or
project
members,
maybe
there
are
some
other
way
like
there
is
a
email
address
of
each
commit
commit
log
and
yeah.
A
C
Yeah,
like
has
it
to
be
a
software,
because
I
know
many
many
open
source
communities
that
does
not
involve
a
software.
So
I'm
not
sure
what
kind
of
project
community
that
we
are
discussing
more.
D
We
might
want
to
leave
that
up
to
the
the
project
and
let
them
decide,
but
we
should
maybe
give
them
guidance
or
like
a
prompt,
because
when
I
think
about
chaos
like
you
can
define
the
chaos
project
in
a
few
different
ways,
you
know
you
could
either
look
at
like
the
auger
community
within
chaos
is
its
own
separate
little
bubble,
and
so
we
would
maybe
you
know,
address
that
differently
than
we
would
like
the
whole
chaos
project.
So
but
that's
specific
to
us.
D
So
I
think
it
would
be
really
hard
to
to
define
a
project
for
everyone,
but
I
think
we
could,
I
think,
you're
totally
right
shoyan,
I
think.
Maybe
we
could
say
a
project
should
be
defined
prior
to
or
your
your
community
should
be
defined
by
you
prior
to
indeed,
in
you
know,
embarking
on
this
journey
or
something
like
that
to
kind
of
give
people
the
heads
up
like
oh
yeah,
I
should
probably
think
about
what
is
what
do?
What
do
I
mean
when
I
say
my
project
community.
C
E
Yeah,
I
think
this.
This
is
definitely
a
great
point.
We
have
we.
We
have
a
certain
idea
of
what
we
think
a
project
is,
and
it's
been
someone
coming
completely
outside
of
the
chaos
project.
Looking
at
this
metric,
it
would
be
like
what
does
that
mean
to
you?
Maybe
we
could
just
add
a
definition
of
what
what
the
the
kind
of
lens
we're
approaching
with
when
we're
talking
about
a
project.
E
A
I
think
yeah,
I
think
that's
the
request,
because
I
listening
to
this
conversation
like
I
was
thinking
when
we
were
in
seattle
right
and
we
had
chaos
con
and
there's
50
people
at
chaos
con
or
is
that
the
community?
I
think
about
the
work
that
shoya
is
doing
in
china
with
the
meetups
and
like
is
that
community
like
to
me
it's
yes
on
on
slack,
we
have
over
200
people
that
are
on
the
slack
in
different
channels
on
on
our
slack
org
like.
Are
they
all
community
members?
A
B
A
A
C
D
In
there
ruth-
and
I
were
just
ruth-
and
I
have
been
working
on
this-
and
we
just
wanted
to
give
you
all
a
quick
update
on
some
feedback
that
we
are
getting
from
doing
the
office
hours,
so
ruth
has
been
working
with
me
and
showing
up
to
the
office
hours
as
well,
which
is
super
super
helpful
to
have
more
than
one
person
there.
So
we
have
had
the
last
few
weeks.
D
We've
had
four
or
five
people
at
each
office
hour
and
we'll
continue
to
do
that,
and
I
know
that
that's
kind
of
kind
of
a
symptom
of
gsoc
starting
up
and
so
a
lot
of
them
are
hopeful
g-sock
students,
but
not
all
of
them.
So
it's
been
really
interesting.
We
had
started
a
doc
which
I
can
drop.
D
I
should
have
opened
this
earlier
sorry
of
what
kind
of
some
themes
that
have
been
coming
up
and
I
just
we
were
going
to
share
them
with
you,
some
quick,
quick
ideas
that
we
had
from
these
office
hours.
Some
of
our
terms
that
we
are
using
internally
are
confusing
to
people.
For
instance,
the
term
working
group
was
a
confusing
term
and
we
don't
define
what
that
means
anywhere.
D
So
we
kind
of
thought
maybe
like
I
know,
we've
had
this
discussion
about
having
a
glossary
and
that's
gone
back
and
forth,
but
I
think
from
a
newcomer
perspective
just
being
able
to
see
or
be
able
to
find
that
what
what
even
is
a
work.
I
don't
even
know
what
a
working
group
means
like
that's.
You
know,
I
think
something
that
we
should
maybe
could
build
out
for
that
purpose.
D
Also,
it
was
not
clear
to
people
what
each
working
group
does.
We
don't
really
have
a
doc.
That
just
says
here
are
our
working
groups
in
like
one
sentence,
we
have
the
participate
page,
which
has
a
little
bit
about
them,
but
it's
not
super
clear
and
it's
kind
of
hidden
at
the
bottom
of
that
page.
So
that
was
something
that
has
been
brought
up
as
something
we
could
do.
D
Some
of
the
the
auger
installation
docs
are
in
need
of
some
help
because
I
think
they're
very
confusing
and
inaccurate
in
a
few
places.
So
I
know
sean
is
super
busy,
but
that
might
be
something
that
he
wants
to
work
on
for
g
stock.
Maybe
an
idea
I
don't
know,
and
then
the
last
one
I'll
just
mention
was
we
we've
had
quite
a
few
people
coming
in
from
ospos
and
I'm
just
wondering
if
there's
something
specific
we
can
do
for
them.
D
I
know,
and
I
always
mention
the
metrics
models
and
that's
where
you
know
kind
of
the
ospo
groups
tends
to
gravitate
toward,
but
that
time
is
not
super
convenient
for
anybody
in
europe
to
join,
and
we
don't
really
have
another
outlet
like
we
don't
have
a
slack
channel.
We
don't
have
any
kind
of
other
way
for
them
to
network
with
each
other,
and
I
think
that
that
would
be
a
really
interesting
thing
for
us
to
provide
is
like
that
hub
for
us
supposed
to
kind
of
connect.
D
Asynchronously
or
you
know,
even
in
another
meeting-
I
don't
I
don't
know
if
we
want
to
do
another
meeting,
because
we
have
plenty
at
chaos,
but
just
wanted
to
bring
that
just
wanted
to
surface
that
up
that
we've
had.
You
know
quite
a
few
people
from
ospos
as
those
kind
of
proliferate
throughout
the
corporate
corporate
world.
So
that's
it.
A
So
I
had
a
few
comments
on
this
one
was,
it
seems
like
we
have
maybe
two
challenges.
As
people
come
to
the
office
hours,
there
are
people
who
want
to
contribute,
but
it's
difficult
to
understand
where
to
contribute.
So
I
think
we
need
to
work
on
like
really
like.
I
know
we
have
the
label
like
good,
first
issue
and
all
that
kind
of
stuff,
but
like
maybe
really
being
specific,
like
hello
to
the
person.
A
D
D
What's
curious
is
that
most
people
are
brand
new
to
chaos,
but
want
to
start
immediately,
and
I
think
that
that's
challenging
because,
like
a
lot
of
our
things,
are
a
little
more
in
depth
like
you
kind
of
have
to
get
to
know
chaos
before
you,
you
can't
just
go
in
and
fix
an
issue.
You
know
you,
it
takes
a
it's
a
little
more
complicated
onboarding.
Then
here's
a
here's,
a
you
know,
list
of
software
issues
you
can
just
go
fix
so.
A
D
That's
our
challenge
is
like
okay,
explaining
kind
of
what
we
do,
because
we're
not
the
typical
software
project-
and
I
think
you
know
especially
some
of
the
students
that
are
coming
in-
are
used
to
seeing
like
oh
kubernetes,
okay,
here
we
go,
you
know,
but
we're
not
like
that
at
all
and
so
differentiating
ourselves
a
little
in
a
good
way,
I
think,
is,
is
going
to
be
challenging
for
us
so
anyway,
when
we
we
have
that
form
and
they
fill
it
out.
I
do
email
or
hit
them
up
on
slack
and
we
chat.
C
D
B
D
Yeah,
I
think
that's
something
ruth
and
I
will
work
on
together.
A
D
We've
had
you
know
quite
a
lot,
and
so
it's
a
little
overwhelming
to
do
that,
but
I
think
that
it
can
be
done
and
I
would
like
to
if
that
makes
sense.
A
Yeah,
okay,
okay
and
then
the
other
thing
that
it
sounds
like
like
with
respect
to
ospos,
like
I
wonder
sometimes
folks
who
are
in
ospos,
are
oftentimes
in
leadership
positions
and
I
feel
like
sometimes
they
they
come
to.
Chaos
like
as
a
potential
resource
to
help
in
their
ospo,
which
is
different
than
contributing
to
chaos,
and
so.
D
D
C
D
I
think
that,
as
we
may
build
those
toolkits
out
that
we're
doing
in
the
in
the
metrics
models
that.
C
D
A
E
B
B
Well,
as
as
elizabeth
as
you
were
talking
through
that,
what
I
was
reminded
of
was
my
my
experience
in
the
openstack
community
and-
and
they
did
a
really
good
job
of,
and
in
fact
they
actually
did
a
session
at
one
point,
I
believe
around
how
many
different
channels
mediums
methods
they
had
for
onboarding,
and
I
wonder
if,
if
it
would
behoove
us,
especially
since
amy
marriage,
is
a
part
of
this
too
and
she's
so
still
still
immersed
deeply
in
that
community.
B
If
we
might
be
able
to
kind
of
leverage
her
experience
as
well,
because
there
were
different
streams
for
you
know,
depending
upon
your,
where
you're
coming
from
what
you're
wanting
that
sort
of
thing
they
kind
of
had
some,
I
felt
like
it.
I
felt
like
they
did
a
great
job
and
were
very
unique
in
having
some
so
many
different
entry
points
to
the
to
that
community
that
we
we
might,
we
might
glean
some
learnings
from
and
and
bkms
or
best
known
methods
from
best
practices.
From
from
from
that
community.
E
All
right,
I
I
wanted
to
mention
a
lot
of
this
information
that
we're
looking
for
is
actually
already
in
the
handbook.
For
some
reason,
we
had
a
glossary.
I
just
realized
this.
Just
now
we
had
a
glossary
already
made
for
a
lot
of
the
terms
in
the
chaos
project,
but
it's
under
a
a
page
called
chaos
committees,
so
it
wasn't
very
easy
to
find
yeah.
So
I
I
have
a
feeling
we
have
more
as
well
that
we
that
we
can
refer
to
out
of
the
handbooks.
E
D
A
Yeah,
maybe
chaos
committees
is
not
the
best
title
for
this.
Okay
right
on
the
very
last
thing
that
I
just
wanted
to
talk
about
in
the
minute
that
we
have.
I
brought
this
up
in
the
community
call
yesterday,
but
it's
about
a
way
to
move
project
badging
forward.
A
A
A
Another
could
be
the
all
in
project
like
all
in
for
maintainers,
as
a
maintainer
wants
to
understand
more
about
improving
their
own
project
like
so,
we
could
have
we
could
partner
with
existing
projects
or
existing
programs
that
are
already
filtering
the
number
of
projects
to
some
degree
in
a
variety
of
different
ways,
that
partnership
would
have
to
come
with.
A
Not
just
this
is
something
we
would
do,
but
we
would
definitely
need
additional
reviewers
and
something
like
this,
and
I
would
probably
I
think
it's
something
that
we
would
ask
that,
like
a
member
from
outreachy
or
all
in
kind
of
participate
in
in
the
project,
badging
side
of
things,
the
way
that
folks
participate
in
event
batching
so
anyway,
I
just
want
to
put
that
out
there.
I
think
it's
a
potential
path
forward
on
project
badging
as
a
way
to
get
our
project
metrics
or
dei
project
metrics
into
practice.
So
that's
it
all
right.