►
From YouTube: CHAOSS.Diversity&Inclusion.Sept.2.2020
Description
CHAOSS.Diversity&Inclusion.Sept.2.2020
B
So
the
agenda
that
I
looked
at
for
covering
this
week
was
just
a
follow-up
on
the
burnout.
Metrics
conversation
with
ruth
and
matt
g,
so
one
or
both
of
y'all
could
give
an
update
on
that.
Then
looking
at
the
badging
projects
with
the
upcoming
launch
on
september
14th,
so
it's
just
about
two
weeks
away,
so
figured
matt
snell
can
give
us
an
update
on
that
side.
B
And
then
we
have
a
couple
highlights
from
state
of
the
source
which
will
be
good
to
talk
about
and
then
we'll
talk
about
facilitating
for
next
week.
So
maybe
before
we
jump
into
the
agenda,
would
it
help
if
we
just
did
like
introductions
of
everyone
for
for
nikki
since
she's
new
to
the
the
call?
Let
me
just
do
like
one
sentence,
so
I'm
sorry
thank
you
yeah
they
so
we'll
just
do
quick.
Would
quick
introductions
be
helpful.
B
Sure
so
I'll
just
we
can
just
go
in
and
quit
the
order
from
top
to
down
on
the
participants
list,
all
I'll
I'll
call
it
out.
Just
so
do
name
pronouns!
Well,
if
your
interest
in
dni
metrics
and
maybe
a
little
bit
just
a
sentence
about
what
you
do
so
I'll
start,
my
name
is
justin.
I'm
the
open
source
technical
advisor
at
the
unicef
innovation
office,
my
pronouns!
A
Hi,
I'm
matt
german
prey
if
you
care
how
to
say
the
last
name,
he
him
I've
been
involved
in
this
working
group,
the
dni
working
group
for
a
long
time
and
I've
I've
learned
a
lot.
So
it's
it's
great
just
to
continue
to
learn,
and
I
think
a
lot
of
my
hopes
are
to
really
bring
a
lot
of
the
dna
efforts
that
occur
in
this
group
and
other
groups
into
practice
and
help
people
improve
the
way
that
they
work
in
communities.
D
F
E
G
Hello,
everyone,
I
am
astra
best
pronouns,
are
she
and
her,
and
I
am
a
contributor
to
the
dna
badging
project.
So
my
interest
and
bni
metrics
are
like
are
a
product
of
working
on
that
project.
So
I
like
to
see
how
they
can
be
implemented
and
like
how
people
respond
to
analyzing
things
which
are
related
to
them.
F
F
H
Since
the
beginning,
I've
been
really
passionate
about
that.
So
that's
that's
one
reason
why
I'm
I'm
especially
interested
in
this
working
group,
not
that
I
have
favorites,
because
I
don't
I'm
the
community
manager.
I
love
all
the
children
the
same,
but
I
don't
know
this
one's
got
my
heart
and
I'll.
Also.
I
am
I
do
this
part
time
and
then
I'm
also
a
nature
photographer
as
my
other
half,
so
something
not
tech,
that's
it!
Oh!
I
am
awesome
thanks.
I
I
The
reason
that
I'm
interested
in
what's
going
on
here
is
I'm
really
interested
in
diversity,
inclusion,
stuff
in
general
and
less
good
at
the
metrics
side
of
things.
So
actually
I'm
learning
lots
by
being
part
of
this
working
group.
So
I'm
taking
a
lot
of
information,
but
I
hope
to
and
have
contributed
in
the
ways
in
which
I
am
able
to
my
pronouns:
are
they
them,
but
I'm
also
pronoun
agnostic,
so
I'm
happy
with
she
her
or
he
him
as
well.
B
J
Go
ahead,
that's
what
I
remember,
but
hi,
I'm
matt
snell
my
point
answer:
he
him
his
and
I
my
I
mean
graduate
assistant
at
the
university
of
nebraska
at
omaha.
I
want
to
say
that,
because
I
look
very
nebraska
today
and
I
just
I
have
a-
I
have
a
passion
for
diversity
and
inclusion,
but
I'm
still
pretty
new
to
it.
J
J
K
Thanks
justin,
so
my
name
is
nicole
huseman,
a
pronoun
she
or
her
and
gosh.
I've
been
involved
in
open
source
for
a
little
over
10
years
and
involved
in
the
chaos
project
on
for
my
gosh
gosh
at
least
a
few
years
now,
and
always
very
deeply
interested
in
diversity
and
inclusion
in
the
tech
industry
and
in
the
open
source
community.
C
C
C
I
had
a
great
call
with
matt
and
gaywork
about
open
demographics,
and
I
don't
know
how
I
feel
about
metrics
per
se,
but
I
also
know
that
we
live
in
a
datified
society
and
so
I'm
sort
of
navigating
that
tension
between
like
data
and
surveillance,
but
also
like
making
communities
warm
and
welcoming
and
how
to
do
that
at
scale.
And
so
that's
sort
of
where
I'm
at
thanks
for
having
me.
L
Everyone
yeah,
okay,
I'm
ruth
ikeda
from
nigeria,
pronounced
she
her.
Then
I
decided
to
join
the
dni
working
group
because
I'm
from
I'm
a
black-
and
I
want
to
be
part
of
the
working
group
that
defines
metrics
for
being
diverse
and
inclusive,
so
I
want
to
be
part
of
that
goal
and
see
that
it
pushes
forward.
So
that's
why
I
joined
td
and
I
work
and
group
yeah.
B
And
then
so
next,
so
I
see
it,
gotta
keep
a
couple.
More
people
also
joined
us,
hey
sean,
so
we
have
anita
and
sean
we're
just
doing
a
quick
introduction,
since
we
had
some
new
folks
join
the
call
for
the
first
time
so
just
name
pronouns
affiliation
role
and
just
a
sentence
or
two
or
why
you're
interested
in
dni
metrics,
while
you're
here
so
anita.
M
M
M
Being
my
commitment
to
the
dni
working
group
is
really
just
part
of
what
comes
out
of
being
in
one
of
the
more
balanced
communities
in
computer
science,
which
is
the
social
computing
research
community,
as
well
as
the
one
of
the
more
unbalanced
computer
science
departments
in
the
country
where
we
have
93
male
white
people
that
compose
our
population.
So
my
commitment
to
diversity
and
inclusion
and
open
source
stems
from
my
desire
to
make
a
difference
in
the
world.
B
N
I
have
been
into
open
source
for
a
couple
of
just
to
know,
but
I
have
I
actually
found
it
very,
very
interesting
and
I
want
to
get
involved
later
the
unborn
process,
because
a
lot
of
persons
have
issues
with
it,
including
myself.
I
had
a
lot
of
issues
getting
into
it,
so
the
onboarding
process
would
be
like
the
right
spot
for
me
to
start,
and
then
you
got
the
guy
here
and
I
metrics
is,
and
I'd
like
to
get
involved
with
over
time.
I
hope
I
learn
more
from
this
place,
though.
B
Great
thanks,
so
I
think
that
was
was
everyone.
I
don't
think
I
I
missed
anyone
there.
So
I
know
most
of
us
were
already
probably
pretty
familiar
with
each
other,
but
I
appreciate
just
helps
to
build
some
context.
I
think
so
going
back
and
looking
at
the
agenda
doc.
If
you
need
a
link
to
that,
it's
in
the
zoom
chat,
I
figure
we
can
go
ahead
and
start
really
quick
on
an
update
with
the
project
burnout
metrics,
which
I
didn't
have
any
notes
for
that.
But
I
figured
ruth
or
matt
g.
L
Okay,
so
sorry
I
wasn't
in
the
last
meeting,
I
had
some
network
issues.
Well,
I
looked
at
the
google
docs,
so
I
made
some
for
the
comments
that
I
made.
I
added
them
up
yeah.
So
then
there's
something
else.
I
wanted
to
add
on
the
project
burnout.
So
in
guinon,
there's
this
project
ongoing
schedule
mentors.
L
L
So,
while
in
that
project
we
we
try
to
see
how
the
the
different
challenges
newcomers
encounter
when
they
come
into
an
open
source
project,
so
we
had
another
subgroup
for
the
project
schedule
mentos,
so
why
I
mentioned
it
now
for
project
burnout
is
mentors
in
from
from
what
we've
gathered
so
far.
Mentors
in
open
source
project
also
experience
burnout,
because
you're
getting
contributors
from
all
over
the
world
with
different
skill
sets
with
different
cultural
backgrounds.
L
So
when
assigned
to
a
mentor,
sometimes
the
the
questions
or
the
handholding
parts
for
that
contributor
is
usually
very
stressful
and
they
can
experience
burnout.
So
that's
one
one
thing
I
want
to
fix
in
in
this
burnout:
where
do
we
fit
in
mentors
that
are
experiencing
burnouts
in
open
source
projects
because
they
are
also,
they
are
also
to
be
taken
care
of?
They
are
also
to
be
taken
care
of
on
that
as
relating
burnout
metrics.
So
we
shouldn't
also
leave
them
out
because
mentors
actually
do
a
lot
yeah.
L
So
that's
one
thing
I
wanted
to
chip
in
or
yeah,
and
I
think
I
went
there
are
some
comments
that
were
unresolved.
I
couldn't
resolve
them,
I
think
one
from
errol
about
if
the
terms
were
used
globally,
so
yeah-
I
I
didn't
quite
understand
that
part.
So
I
just
left
the
comments
unresolved.
So
if
we
could,
if
errors,
could
please
expand
on
that.
B
B
Oh,
no,
it's
already
there
thanks
george,
so
it's
the
qualitative
questions
with
their
own
interpretation
of
terms
and
just
looking
at
those
three
questions
just
to
get
like
a
more
global
context.
If
these
are
things
that
people
will
understand
in
the
same
way
or
if
they'll
be
perceived
differently,
is
there
a
way
you
want
to
try
to
guide
the
discussion
on
that
or
just
do
we
want
to
do
some
silent
editing
and
do
some
like
silent
notes
in
the
doc?
What
would
be
more
helpful.
E
I
But
it
is
not
something
which
I
heard
a
lot
like
used
a
lot
in
when
I
was
doing
some
stuff
in
east
asia
and
some
other
places.
So
I
just
just
suggesting
that
if
we
are
using
the
term
burnout
and
self-care
in
questions
that
maybe
there
needs
to
be
a
little
place
where
that
is
explained
or
like
that,
we,
if
we
know
of
any
other
words
that
other
kind
of
cultures
use
to
describe
this,
that
we
could
use
multiple
different
words
that
describe
this.
F
I
think
the
term
is
more
universal
now
than
it
may
have
been
in
past,
and
we
might
just
be
seeing
it
that
way.
Internally,
because
again,
a
u.s
company
sending
out
emails
on
how
to
prevent
burnout
and
stuff,
but
we're
seeing
a
lot
of
replies
from
all
over
the
world
and
they're
okay
and
they
are
using
that
terminology.
F
A
A
Yeah,
I
was
gonna
say
in
the
description
like
all
the
way
at
the
top,
it
maybe
a
little
bit
more
effort.
We
should
put
a
little
bit
more
effort
in
describing
what
it
is,
so
we're
going
to
just
say:
listen
we're
going
to
be
using
this
term
and
here's
here's
what
we
mean
by
this
to
just
give
it
a
little
bit
more
context.
B
B
So
I
I
just
wonder
if
it'd
be
a
helpful
way
to
give
people
a
really
clear
way
so
like
for
me.
I
see
this
like
in
my
my
default
reaction
is
kind
of
like
the
wall
of
text
can
be
a
little
intimidating,
especially
if
I
imagine,
if
you're,
not
a
native
english
speaker,
it
might
be
a
little
more
challenging
and
if
we
want
to
have
a
more
global,
I
don't
know,
maybe
there'd
be
a
way.
B
E
J
I'd
I'd
recommend
not
using
the
term
burnout
at
all
when
it
comes
to
asking
people
questions
that
they
might
not
know
what
bernard
is
having
situations.
We
could
ask
questions
like
tired
or
kind
of
kind
of
words
that
describe
burnout
without
having
to
talk
about
the
term
itself,
because
that
I
think
the
problem
isn't
so
much
that
it's
not
defined
as
it
is
that
it's
not
universally
it
might.
It
may
or
may
not
be
universally
used
as
something
that
people
understand
is
burnout.
B
Cool,
so
I
think,
maybe
just
with
respect
to
time.
I
think
this
is
I'll.
Try
to
get
some
of
this
down
in
the
notes,
too.
Maybe
a
good
way
to
have
a
follow-up
on
this
discussion
is
to
open
a
new
conversation
on
the
dni
mailing
list
just
to
have
a
just,
because
I
know
there's
also
folks
who
can't
make
it
to
the
call
for
whatever
reason
so
it'd
be
good
to
try
to
pull
in
their
perspectives
too.
If
this
is
something
that's
interesting
to
them,.
F
The
link
in
chat-
it's
not
really
burnout
but
stress
anxiety,
but
to
be
honest
with
you
the
way
they
do
it
is
what
you
see
and
what
I
feel.
Maybe
we
could
do
something
similar
to
that.
I
thought
that
was
really
well
organized
and
very
clear.
So
if
we
do
want
to
go
something
with,
you
know
pointing
out
what
are
parts
of
burnout,
we
could
do
something
very
similar,
so
I
think
it
makes
sense
to
people.
B
I
think
that
would
be.
I
really
like
the
idea
of
trying
to
open
this
discussion
up
too,
to
get
more
feedback
on
that
in
ways
that
we
could
be
maybe
more
inclusive
or
be
be
clear
in
what
we
mean,
especially
when
we're
talking
about
these
really
broad
topics
that
can
sometimes
be
hard
to
put
into
a
metric.
A
A
So
the
way
that
we
write
them
and
try
to
talk
about
them
in
all
working
groups
is
as
a
project,
for
example,
with
project
bernard.
Are
you
thinking
about
project
burnout
within
your
project
and
how
are
you
doing
that
so
we
never
add
value
or
like
we
never
make
value
judgments
on
any
of
our
metrics
just
trying
to
indicate
that
these
are
probably
things
that
you
want
to
think
about
when
it
comes
in
this
case
with
respect
to
dni
and
what
the
results
that
come
from
this
metric.
A
B
Great
thanks
so
we'll
we
can
do
a
follow-up
next
week
on
on
the
burnout,
metrics
and
I'll
take.
I
have
the
action
noted
that
I'll
start
a
throw
on
the
mailing
list
about
how
to
talk
about
burnout,
just
because
I
want
to
with
respect
to
time-
and
I
don't
know
if
nikki
has
to
jump
off
soon.
I
just
want
to
go
straight
into
the
just:
do
the
open
demographics
follow
up?
Just
maybe
just
any
updates
from
that
meeting?
A
The
repository
will
will
stay
where
it's
at
and
in
the
chaos
project,
as
we
refer
to
we'll
just
continue
to
refer
to
to
the
open
demographics
work
in
the.
I
think
it's
dr
nikki
repository,
I
kind
of
forget
the
org,
but
I
think
that's
it,
and
then
the
meeting
too
was
just
to
make
sure
that
when
we
add
maintainers
that
are
coming
from
the
chaos
project
to
this
repository,
that
we
don't
change
the
directions,
not
quite
the
right
word,
but
is
philosophy.
The
right
word
change
the
the
nature.
L
I
A
C
I
C
I
just
want
to
make
super
clear
sorry,
my
someone
is
banging
on
my
door.
One
of
the
things
I
just
want
to
make
clear
is
that,
like
I'm
super
not
trying
to
like
maintain
control
over
it
but
trying
to
just
keep
it
organization
agnostic?
So
it's
not
that
I
want
to
keep
it
mine,
it's
just
that
like
there's
a
reason
it
didn't
become
drupals,
even
though
I
was
deeply
embedded
in
the
drupal
community
at
the
time.
C
C
So
for
all
I
care
we
could
move
it
into
the
it
could
move
out
of
my
own
github
profile
and
into
an
one
just
called
open
demographics
and
be
itself
there.
I'm
fine
with
that
being
the
case
too.
So
it's
not
that
I
needed
to
stay
associated
with
me
per
se,
as
it
is
just
trying
to
keep
it
away
from
the
big
corporate
overlords.
B
Awesome
so
maybe
one
of
the
open
questions
might
be.
If
we
want
to
talk
about
that
now
or
we
can,
we
can
push,
but
maybe
just
about
how
what
those
logistics
would
look
like,
or
we
want
to
start
thinking
about.
How
can
we
bring
people
from
the
chaos
side
of
things
to
participate
in?
That?
Is
there
like
a
call
to
action
that
we
could
try
to
take
from
this.
C
I
think
one
of
the
things
that
I'd
be
happy
to
think
with
think
about
with
you,
either
now
or
next
meeting.
I
don't
know
what
else
is
on
the
agenda
is
maybe
making
a
list
of
action
items
for
folks
to
jump
in
on
rather
than
saying
like,
let's
all
start
from
a
blank
slate
and
try
and
invent
the
wheel.
We
have
a
bunch
of
stuff
that
matt
and
gary-
and
I
talked
about
just
need
to
happen,
no
matter
what
right
the
docs
need
to
be
cleaned
up.
We
need
a
better
onboarding
process.
C
We
need
ways
to
contribute
that
aren't
so
great,
like
good,
first
issue,
labels
that
aren't
so
so
tech
and
so
require
so
much
social
technical
capital.
So
we
can
I'm
happy
to
go
through
and
like
collaborate
on
making
a
list
of
those
and
getting
even
getting
like
a
good
issue.
Template
put
together,
so
things
like
that
that
just
are
ready
to
go
and
then
maybe
from
there
and
that'll
buy
us
a
couple
months
anyway
and
then
from
there
figure
out
what
the
next
best
steps
seem
like.
B
C
That's
a
great
idea,
and
the
other
thing
that
I
want
to
float
now
that
I'm
thinking
about
october
and
opening
it
up
to
general
contributions
is
getting
taking
another
look
at
the
contributor
agreements
and
repo
codes
of
conduct,
I'm
in
my
memory
they're
in
there,
but
I
think
it's
always
worth
taking
another
look
at
them.
As
types
change.
B
Definitely
cool
so
I
think
then
we
can
we'll
go
with
the
issue
then,
to
push
the
conversation
forward
there.
So
I
think
matt,
matt
g.
Are
you
going
to
take
that
one
cool
so
with
that?
I
think
we
can
jump
to
the
bat.
I
think
it's
badging
I'm
trying
to
find
the
tab
now,
where
is
it
yeah
with
badging,
so
matt
matt
snell?
Do
you
want
to
give
a
quick
update
there
anything
that
we
can
help
out
with
on
the
badging
front
yeah
so.
J
Our
launch
is
coming
up
september
14th
and
we're
always
looking,
I'm
actually
actually
going
to
ask
for
two
things
today:
we're
looking
for
people
to
scrutinize
our
organization
and
find
anything
that
might
be
wrong
or
dead
links,
or
anything
like
that.
If
you
ever
want
to
that's
always
kind
of
an
open
thing
that
you
can
always
do
and
the
other
one
is
we're
looking
for
badging
reviewers.
J
J
We
have
some
emails
up
there
and
we
also
have
a
repository
that
you're
free
to
open
an
issue
on
as
well.
We'll
also
be
sending
out
some
messages
to
try
to
get
more
viewers
as
well.
But,
oh,
it's
glad
to
have
you
in
there
too,
and
you
probably
get
a
head
start
on
getting
that
application
anyway
to
become
a
reviewer.
B
A
B
A
A
The
idea
is,
is
that
as
the
dni
metrics
are
being
put
forward,
so
things
about
like
event,
code
of
conduct
event,
family
friendliness,
attention
to
speaker,
demographics,
attention
to
attendee
demographics,
diversity,
access
tickets,
the
idea
is
that
we're
just
simply
asking
events.
Are
you
attending
to
these
things?
When
you
are
putting
together
an
event?
Are
you
attending
to
family
friendliness?
Are
you
attending
to
diversity,
access
tickets?
A
A
Not
I'm
saying
good
or
bad,
and
the
review
process
is
just
kind
of
it's:
an
open
and
transparent
review
process
where
an
event
says
that
they
have
a
code
of
conduct
and
they
have
a
way
to
to
report
issues
and
there's
an
enforcement
policy
with
the
code
of
conduct,
the
review,
the
reviewer
simply
tries
to
ensure
that
that
is
the
case
and
it's
and
it's
publicly
available
for
attendees
and
so
as
part
of
the
badging
process.
It's
that
an
event
demonstrates
that
they
are
being
attentive
to
these
particular
issues,
and
so
from
a
review
perspective.
B
And
I
see
I
just
dropped
in
the
zoom
chat
too.
If
you
want
to
ask
some
questions
or
get
involved,
there's
you
can
email,
astha
and
matt.
Their
emails
are
in
the
chat
also
in
the
meeting
minutes,
and
you
can
also
find
the
github
repository
where
all
the
action
is
happening
in
the
chat
as
well.
So
anything
else
we
want
to
cover
on
badging
before
we
jump
to
last
couple
topics.
I
had
one
last
thing
to
say.
A
It's
part
of
the
review
process
too.
The
intention
is
to
to
help
events,
so
if
they
haven't
thought
about,
say,
diversity,
access
tickets,
it's
part
of
the
review
process
to
maybe
point
them
to
other
events
that
that
that
attend
to
diversity,
access
tickets
and
talk
through
ways
that
that
the
event
could
provide
them
for
attendees.
So
it's
meant
to
be.
The
review
is
also
meant
to
be
a
constructive
process
so
that
events
are
improving
the
the
ways
that
they
attend
to
dni.
J
B
D
Itself
is
about
metrics,
with
metrics
about
in
open
source
and
what
we've
learned
from
the
chaos
project,
so
I'll
talk
about
what
is
community
health,
and
why
do
we
all
care
about
this?
What
do
we?
If,
if
we
want
to
understand
community
health
more,
you
know
practically
not
just
indeed
doing
some
crystal
ball
looking,
then
we
need
metrics
and
the
metrics
that
we're
developing
in
chaos.
This
is
where
we
all
build
out
the
language
together
and
that,
well,
we
are
building
out
the
metrics
for
one
have
a
shared
language.
D
D
I
D
Collecting
everything
to
you
need
a
strategy,
there's
so
much
data
about
open
source
communities.
It's
opening
a
fire
hose
of
data,
so
you
need
to
have
a
good
strategy
and
how
to
go
about
doing
that
so
yeah
yeah.
Unfortunately,
I
don't
have
a
link
to
the
specific
talk.
I
just
have
that
link
to
the
schedule.
D
B
B
L
L
L
H
B
D
B
B
D
B
Here
could
follow
up
with
matt
g
if,
if
there's
not
any
takers
right
now
or
we
could
put
it
out
actually,
I
could
also,
since
I'm
already
gonna
post
a
mailing
list
thread.
I
could
make
an
open
call
on
the
mailing
list
if
anyone
wants
to
volunteer
and
facilitate
so
no
one
has
to
be
on
the
spot
right
now.
Take
that
commitment
too
so
I'll
just.
D
B
I
haven't
looked
at
the
state
of
the
source
schedule,
but
I
know
I'm
probably
going
to
be
tied
up
with
that
too.
So,
that's
probably
where
I'll
be
next
week,
cancel
okay.
So
in
that
case
then
we'll
push
to
another
two
weeks
and
then
I'll
still
I'll
still
open
a
thread
to
see
if
anyone
wants
to
volunteer
to
facilitate
and
we'll
go
from
there
cool.