►
From YouTube: CHAOSS.Diversity&Inclusion.August.12.2020
Description
CHAOSS.Diversity&Inclusion.August.12.2020
A
Could
somebody
gaylord
or
kevin
or
gabriel
kevin?
Can
you
kind
of
watch
the
admit
list
yeah
if
I'm
kind
of
all
right?
So
if
you
could
add
yourself
to
the
list
today
on
the
minutes
that
I
put
in
there
and
I'll
post
them
again,.
A
A
Okay,
so
you'll
see
in
the
minutes.
I
have
kind
of
a
few
things
that
I'd
like
to
get
through
today.
The
first
is:
do
we
have
any
volunteers
to
be
a
facilitator
next
week,
always
happy
to
help
out.
A
I
would
imagine
you
do
so
the
list
today
and
I'm
going
to
kind
of
look
at
you
for
just
a
second
dawn
if
there
was
anything
that
jumped
out
to
you
for
those
first
30
minutes,
so
we
had
dna
issues
meeting
the
issues
on
github.
I
wanted
to
go
through
those
a
little
bit
because
we
have
some
pretty
old
lingering
issues
and
I've
been
trying
to
clean
those
up
just
a
little
bit
today.
A
As
we
had
documentation
usability
as
part
of
the
last
release,
and
then
we
have
a
couple
other
documentation
metrics
that
I
think
we
can
aim
for
for
the
for
six
months.
From
now,
matt
and
asta
have
some
updates
to
the
badging
program,
just
in
terms
of
the
logistics,
and
then
we
have
a
new
metric
candidate
for
burnout.
A
I
think
that
was
from
ruth
is
that
right,
but
I
don't
see
her
on
so
we
can
just
wait
for
that
and
then
I
would
also
like
to
start
kind
of
talking
about
dna
in
the
chaos
project
itself,
so
kind
of
what
this
might
start
to
look
like,
and
if
we
have
thoughts
in
this
group,
so
don
was
there
anything
that
you
wanted
to
hit
earlier.
Just
go
ahead
and.
A
Okay
right
on
all
right,
so
maybe
I
thought
we
could
spend.
Maybe
just
a
few
minutes
and
I'll
get
the
minutes
back
in
here
again
for
folks
that
are
joining.
A
So
I
thought
I'd
like
to
spend
just
a
few
minutes.
We
certainly
don't
just
spend
a
long
time,
but
I'd
like
to
start
getting
our
our
weekly
addressing
of
issues
and
or
pull
requests
in
the
dna
working
group
a
little
bit
more,
something
we
do
a
little
bit
more
regularly.
They
seem
to
be
posted
and
they
don't
seem
to
be
attended
to
for
long
long
periods
of
time.
So
I'd
love
to
start
kind
of
taking
a
look
at
those.
A
A
A
A
At
the
same
time,
so
we
have
a
discussion
on
adding
extra
section
to
the
demographics
here,
so
this
was
brought
up
by
daniel
and
alexander
quite
some
time
ago
and
to
me
when
I
was
taking
a
look
at
this
metric
or
I'm
sorry
when
I
was
taking
a
look
at
this
issue,
we
had
also
talked
about.
A
Where
sorry
gary,
do
you
remember
when
we
were
talking
about
kind
of
offering
to
take
ownership
of
the
the
demographics
work?
Do
you
remember.
B
That
yeah,
I
remember
the
conversation.
I
don't
think
we
opened
an
issue
on
our
own
repository
it
pinged
nikki,
but
I've
never
heard
back.
A
Open
demographics
here
it
is
right
here,
isn't
this
it
okay,
so
for
those
of
you
that
that
are
kind
of
new
to
this
nikki
stevens
is
that
her
name
has
been
running
an
open
demographics.
A
A
Okay-
and
so
I
I
think,
that's
this
issue-
isn't
that
this
about
potentially
forking
that
and
then
maintaining
it
in
the
chaos
project,
and
then
I
think
this
is.
This
would
ultimately
be
related
to
that
as
well,
which
is
about
how
we
would
think
about
the
demographic
questions
in
terms
of
basically
contributing
to
that
work
that
you
had
just
talked
about.
A
So
do
we
want
to
simply
move
forward
and
and
fork
this
and
try
to
maintain
it?
That
seems
not
quite
right.
Do
we
want
to
reach
out
to
to
the
project
again
and
see
in
terms
of
what
you
had
done
earlier,
georg
and
see
how
that
works?
Do
you
have
thoughts.
B
D
A
C
B
The
pull
request
is
three
one.
Two.
B
Yeah
I'll
change
the
pull
request.
I
don't
like
how
it
because
I
changed
the
numbering.
I
had
to
change
all
of
the
lines,
I'll
change
them
all.
So
it's
easier.
A
A
Okay,
so
this
is
this-
is
about
metrics
that
are
part
of
a
focus
area
called
project
places.
We
no
longer
have
this
focus
area.
I
think
it's
called
project
and
community.
A
A
A
A
A
B
A
A
So
all
of
I
see
the
kind
of
so
none
of
these
links
exist
anymore.
Sadly,
because
this
doesn't
exist
anymore
either
the
focus
area
of
project
places
so.
B
Okay,
sorry,
but
it's
a
good
idea,
but
we
would
need
anita
to
push
this
forward
because
she's
the
expert
on
the
gender
mac.
A
Would
you
could
you
maybe
ping
her
on
closing
it
just
say:
hey
we're
gonna
close
this
issue
until
it
moves
forward.
A
Okay,
thank
you
develop
project,
okay,
so.
B
I'm
I'm
pinging
anita
right
now.
A
And
we'll
be
done
so
this
one,
this
one
is
about
documentation.
A
So
for
a
lot
of
people,
we
had
talked
about
documentation
kind
of
at
this
highest
level
as
a
metric,
and
what
we
realized
when
we
started
talking
about
documentation
was
that
there
are
a
whole
variety
of
different
ways
that
we
need
to
think
about
documentation.
A
A
I
think
it
might
have
been
errol
who
had
brought
up
documentation
like
timeliness.
Do
you
remember
this?
When
you
had
talked
about
the
just
the
how
long
it
takes
to
read,
which
I
think
would
probably
fit
it
kind
of
in
this
world
that
we're
talking
about
as
well?
So
I
would
probably
want
to
add
that
so
the
issue
that
george
would
had
brought
up
was
about
documentation,
and
I
was
wondering
if
we
could
close
this
issue
because
we're,
I
think
we
are
addressing
this
in
the
project
right.
D
B
A
I
would
probably
rather
do
the
latter,
and
then
we
can
take
care
of.
We
can
also
add
an
issue
for
what
errol
was
talking
about.
I
don't
remember
what
you
called
it
documentation,
something.
A
B
B
A
A
Well,
yeah,
I
was
gonna,
ask
errol
to
open
one
on
okay
on
time,
diversity,
documentation,
time
diversity,
and
then
we
can.
A
I'll
take
solace
and
we're
in
fact,
that
we're
down
to
20
issues
for
the
moment
and
all
right.
Well,
thank
you.
That
was
great.
If
we
could
do
this
every
week,
that
would
be
really
great
that
we
can
kind
of
start
kind
of
winnowing
this
down
and
to
your
point,
georg.
F
A
Into
a
more
modern
date
should
be
great
all
right,
thanks
justin
for
adding
that.
So
could
we?
Oh
I'm
sorry.
A
Yeah,
you
bet
so
hello,
ruth
so
I'll
put
the
minutes.
A
I'm
gonna
stop
my
share
for
a
second
and
where
oh
somebody
gave
it
to
roos
thanks
justin,
so
ruth
one
of
the
things
that
we
were
talking
about
in
the
minutes
today,
which
was
yep
so
the
it
just
went
away.
Where'd
it
go
there,
we
go
burnout
as
a
new
metric
candidate
for
dni.
A
G
Yeah,
okay,
so
I
talked
about
it
yesterday
in
the
weekly
meeting,
so
the
idea
was
okay.
We
have
some,
although
I'm
new,
to
tech,
but
I
know
there's
a
point
in
I
volunteer
a
lot
before
I
start
tech.
I
do
volunteering
so
there's
a
point
where
people
are
walked
out,
even
when,
like
for
a
people's
person,
a
person
that
is
so
nice
to
always
give
out
their
time.
G
So
there's
that
point
where
the
person
is
worked
out
that
there's
no
one
to
reach
out
to,
because
I
am
nice
I
don't
want
to
make.
It
seem
like
I'm
being
I'm
drawing
away
from
activity
so
for
for
project
and
okay.
This.
This
should
be
specific
to
projects,
not
events
so
for
projects
that
the
contributors
should
the
project
should
have.
The
community
should
have
a
way
to
reach
out
to
the
contributors
for
in
that
regards
burnout.
G
So
because,
if
if
someone
is
born
now
like
for
a
nice
person,
you
wouldn't
they
will
just
start
drifting
away
and
stop
contributing
at
the
point,
maybe
because
they
don't
know
who
to
reach
out
to
or
talk
to
about
how
they
feel
or
how
they
are
under
presented
in
that
community
or
nobody's
listening
to
them.
So
I
I
feel
I
I've
not
really
really
thought
about
the
idea
so
well,
but
I
think
this,
like
the
the
scratch
of
the
idea
I
have
concerning.
A
So
that's
super
helpful.
Thank
you.
I
I
do
have
a
question
in
terms
of
burnout.
Ruth,
do
you
think
it's
about
if
the
metric
was
regarding
burnout?
Is
it
about
how
we
would
observe
burnout
occurring
within
a
community,
or
is
it
a
metric
that
we
observe
that
the
community
is
attentive
to
help
people
who
are
feeling
burnt
out?
G
A
H
C
D
All
right,
sorry,
I
right
glued
in
my
hand,
but
yeah.
So
so
I
have
a
new
os
and
the
icons
are
not
showing
up.
So
I
guess
my
hand
is
raised.
I'm
sorry
to
jump
in
so
burnouts
are
very,
very
tricky
because
sometimes
a
person
isn't
burnout
and
they
don't
take
a
back
seat
and
they
don't
necessarily
realize
they're,
not
being
nice
anymore.
D
So
so
I
think
if,
if
we're
gonna
start
taking
the
angle
of
the
word,
I
like
to
use
this
mental
hygiene,
then
then
I
think
it
helps
to
also
consider.
Are
there
certain
questions
that
could
be
made
available
to
allow
people
to
identify
if
they
are
in
burnout?
D
He
gives
me
this
questionnaire
to
tell
me
if
I
have
depression,
for
instance,
so
we
don't
need
something
that
is
like
what
mental
health
related
things
you
need
to
explore,
but
rather,
if,
if
you
are
in
your
usual
or
if
you're
or
if
you've
been
under
stress
for
too
long
and
you're,
not
able
to
step
back
because
stepping
back
is
a
community
priority,
if,
if
you're
not
in
the
right
head
space
and
a
person
of
course,
person,
one
two
so
yeah,
I'm
gonna
step
back.
A
F
Yeah,
I
could
probably
chat
a
little
bit
on
at
least
what
I'm
thinking
about
when
I
think
of
burnout.
So
from
some
of
my
experience
working
in
what
I
would
call
non-software
parts
of
open
source
communities.
F
F
But
it
just
invites
all
these
interesting
questions
and
to
me
I
see
it
in
those
non-non-engineering
non-software
teams,
usually
because
they're
volunteer
teams
where
people
are
actually
doing
a
huge
amount
of
work,
but
that
work
is
poorly
understood
or
not
very
visible
in
the
upper
part
like
in
the
upper
parts
of
the
project.
Usually
community
management
work
in
my
experience,
but
it
can
also
be
it
can
also
be
technical
things.
It's
not
exclusively
community
work.
F
So,
for
me,
I
always
think
like
one
of
the
things
about
measuring
burnout
is
usually,
if
there's
a
feeling
of
burnout
in
a
community,
I
can
usually
hypothesize
that
there's
some
aspect
of
work:
that's
either
poorly
documented
or
poorly
understood
by
the
rest
of
the
community.
So
I
think
in
some
way
you
can
measure
it,
but
in
order
to
measure
it,
you
have
to
measure
what
you're
not
measuring
yet.
So
I
guess
it's
kind
of.
D
E
E
It
sounded
super
icky
and
gross
in
my
head
when
I
wanted
it,
but
I
do
want
it
and
I
would
love
to
try
and
unpick
that
for
myself,
but
I
would
be
really
interested
in
projects
if
they
manage
if
they
know
that
they've
had
cases
of
burnout
if
they
indicate
that
people
have
burned
out
and
that
they
were
kind
of
like
up
front
about
that
number,
it
kind
of
would
not.
I
was
kind
of
thinking.
E
Maybe
that
would
help
me
understand
whether
or
not
I
wanted
to
contribute
to
the
project
or
not,
but
also
it
kind
of
gives
a
signal
of
like
that.
They
are
willing
to
have
the
conversation
and,
at
the
very
least,
doing
something
about
it.
Yeah
yeah,
it's
kind
of
a
a
weird
request
for
a
metric,
because
you're
in
you'd
want
to
the
instinct
is
to
hide
that
kind
of
stuff.
I
think,
maybe
anyway,.
A
So
it's
it
sounds.
It
sounds
like
a
lot
of
these
comments
are
about
kind
of
observing
the
project
itself
and
asking
how
the
project
is
helping
the
community
members
with
burnout,
how
they're,
looking
across
the
entirety
of
the
project,
not
just
technical
spaces
that
may
be
resulting
in
burnout.
A
A
For
me,
I'm
going
to
propose
that
I
could
work
with
ruth
and
we
could
maybe,
over
the
next
week,
come
up
with
a
super
rough
draft
of
a
metric
that
we
could
speak
to
a
little
bit
and
you
can
all
say
it's
great
or
it's
terrible
or
whatever
it
doesn't
matter,
but
it
would
try
to
be
capturing
all
of
these
these
nodes
and
and
bring
it
forward.
If
that
would
be
all
right
with
everybody
has
any
I'm
curious?
Has
anybody
ever
seen
a
project
that
talks
about
burnout?
A
F
A
Okay,
okay,
okay,
so
I'm
gonna
add.
A
Yeah,
I
have
one
one
other
ruth
is
it?
Is
it
okay
to
work
in
google
docs
to
start
this
with
you.
A
Okay,
I'll
create
the
link.
Can
you
either
privately
send
me
your
email
address.
A
A
All
right
great,
thank
you.
H
By
the
way,
yeah,
I
feel,
like
I've
become
the
the
guy
who
just
talks
about
badging,
but
here
I'm
here
to
talk
about
badging
for
a
little
bit,
so
we
one
quick.
H
I
guess
we
have
changed
a
lot
of
things
with
the
workflow
asta
and
I
have
been
working
on
this
workflow
pretty
much
non-stop
for
a
while
and
we've
got
kind
of
some
changes
to
the
workflow
that
you'll
see
in
the
second
pod
testing,
probably
in
launch
one
of
them
is
that
the
pull
request
idea
that
you
create
a
pull
request
with
information.
H
You
have
to
edit
a
line
in
the
table.
Things
like
that
is
now
on
the
chaos
website,
and
it
is
automated
for
the
most
part
I
was
going
to
do
I'm
going
to
do
a
demo
of
the
web
form
real
quick.
Can
I
share
with.
I
need
a
google.
H
H
And
we
we've
been
putting
together
a
a
forum
that
you
can
kind
of
fill
out.
I've
got
it
pre-filled
out
here.
Can
you
make
him
co-host.
H
H
H
That
would
probably
help
so.
Basically,
it's
the
same
thing
as
if
you
created
a
pull
request,
but
it
goes
to
an
issue
instead
and
it
has
like
you,
put
the
event
name
link
to
the
website
and
then
all
of
the
metrics
information
you
kind
of
fill
out
with
some
testaments
to
how
you
commit
or
don't
commit
to
the
diversity
and
inclusion.
In
your
event,
so
we've
got
all
these.
I
got
all
these
filled
out
already,
with
kind
of
a
mock
event.
So
if
you
click
submit
it
will
take
you
to
an
issue.
D
H
Again,
yeah
yeah,
I
can
zoom
in
so.
H
An
issue:
that's
got
this
information
in
it
and
then
you
you
just
submit
a
new
issue,
looks
like
we
had
a
formatting
error
on
this
one,
but
generally
it
creates
the
entire.
The
entire.
H
So
I
I
it
looks
like
there's
a
spacing
issue,
but
we
have
a
system
that
we
created
an
issue
with
we
plan
to
have
some
bots
that
kind
of
assign
a
pending
badge.
H
The
the
the
workflow
is
the
fine
details
are
still
being
worked
out,
but
the
bot
is
going
to
be
put
together
in
that
in
that
space,
where
it
will
reply
to
you
and
it
will
regenerate
checklists
for
the
reviewers.
H
I'm
also
glad
to
take
questions
about
this
as
well,
and
the
review
checklist
is
going
to
be
provided
automatically
you
they
fill
it
out
and
then
it
creates
a
percentage
which
is
also
a
new
feature
that
you
have
to
have
a
certain
percentage
of
these
metrics
with
a
positive
review,
and
then
it
will
come
back
and
give
you
a
badge
but
based
on
that
and
our
new
percentage
rating
is
40
for
pending.
A
So
the
so
right
now
somebody
the
process
would
be.
Somebody
comes
to
the
form
that
you
had
just
showed
to
request
a
badge.
A
It
shows
up
in
it
as
an
issue
in
badging
in
the
badging
repo
yeah,
a
person
will
assign
reviewers
to
that
is
it?
Would
that
be
like
you
and
hosta
or
who
would
assign
reviewers
to
that
issue?
Also.
H
I
Right
now,
like
it's
more
likely
that
the
issue
assignments
would
be
done
manually,
I'm
working
on
something
which
could
make
that
more
unbiased.
But
since
we
will
be
like
randomly
assigning
the
viewers,
so.
H
Okay,
yeah
and
we've
got
the
bot
we
got
built
right
now
is
to
probot,
and
I
believe
it
uses
the
github
api
for
a
lot
of
its
information
exchange
too.
We've
got
a
lot
of
a
lot
of
things
built
up
at
this
or
I'll
mostly
ask
that
it's
got
a
lot
of
things
built
up
at
this
point
that
are
really
going
to
be
really
cool
for
that
second
pilot
test.
I
think
cool.
F
Yeah
not
to
nerd
out
too
much,
but
just
curious
like
how
did
you
what's
what's
behind
the
scenes
to
make
that
happen?
Like?
Are
you
running
a
server
app
to
like
open
to
send
send
a
request
to
the
github
api?
I'm
just
curious,
because
I
was
having
the
same
conversation
this
week
about
something
very
similar,
so
I'm
just
interested.
H
I'll,
definitely,
if
you
want,
I
can
share
the
code
with
you
for
because
it's
just
you
can
it's
all
client-side
javascript
and
it
it
basically
just
you
can
use
url
parameters
to
create
an
it
to
go
to
that
create
issue
screen
and
you
you,
you
use
a
login
parameter
so
that
they
have
to
log
in
and
get
to
that
to
get
to
that
page
with
their
account.
H
And
then
you
you,
you
basically
just
encode
the
entire
body
of
the
issue
with
encode
uri
component
and
then
and
then
just
put
it
into
the
url.
I
can.
I
can
definitely
show
you
how
to
do
that,
because
it
was
kind
of
a
secret
that
I
found.
H
D
And
I
think
it
also
ensures
that,
like
once,
you
trigger
the
process
external
from
what
the
github
interface
itself,
like
that
the
person
has
to
use
the
github
interface
so
that
it's
the
familiar
process
and
if
you're
gonna
make
it
on
their
behalf.
Somehow
then
you're
you're
diverting
from
the
familiar
process-
and
you
know
you
have
to
start
to
actually
provide
troubleshooting
and
stuff
like
that.
So
so
it
just
helps
that
that
it
relies
on
github.
D
If
the
front
end
is
not
running,
all
you
tell
them
is
just
take
this
mark
down
file,
fill
it
up
and
open
an
issue
that
says
you
know
as
far
as
you
have
to
go.
If
you
have
to
troubleshoot,
if
you
know
your
site
is
offline
whatever,
so
so
it's
a
very,
very
simple
process.
If
you
have
to
do
it
manually,
it
doesn't
require
you
to
need
the
website.
At
that
point,.
A
Cool
and.
I
A
H
Yeah
something
to
edit
that
dot
that
read
me
document
at
the
beginning
of
the
event:
diversity
and
inclusion,
repository
and
add
a
line
item
that
shows
that
when
it
was
bashed
when
it
expires,
things
like
and
the
badge
itself
in
the
project
or
the
event.
So
we
have
that
I've
got
kind
of
some
of
the
code
for
that.
But
I
don't
think
it's
going
to
be
ready
by
the
second
pilot
testing,
because
there's
several
steps
involved
and
you're
handing
off
from
one
api
call
to
another.
A
H
That
asta
had
was
that
we
should
probably
have
a
human
merge
it,
but
other
than
that
it
would
create
the
pull
requests
and-
and
we
would-
we
would
have
that
ready
for
merge
at
that
point.
A
H
There's
a
there's,
a
there's
like
a
generate
command
that
you
had
made
hosta
that
assigns
a
badge
based
on
a
percentage,
and
then
you
don't
close
the
issue
at
that
point.
You
kind
of
can
keep
going
yeah.
I
Like
I
haven't
associated
open,
close
state
for
the
issue
with
that,
but
yeah.
A
Lot
of
effort
that's
being
put
into
the
reviewer
to
kind
of
confirm
or
deny
an
event's
claim
to
a
particular
metric,
so
there's
work
right
tracking
down
how
attentive
they
are
to
say
speaker,
demographics
or
how
attentive
they
are
to
their
code
of
conduct,
and
so
I
think
when,
from
a
review
perspective,
that's
the
the
the
most
effort
is
being
put
on
that
review
process
and
the
the
less
effort
we
can
have
at
the
end
of
the
process
for
a
reviewer,
the
better
right.
They
they,
the
reviewers,
done
their
job.
A
They've
worked
with
the
event
to
think
through
critical
metrics
with
respect
to
dni
for
their
event,
awesome
close
issue,
the
badge
closed,
the
issue
and
the
reviewer
is
essentially
done
so
yeah
it'd
be
great.
If
there's
not
a
lot
of
lingering
things
at
the
end,
so
sorry
somebody
was
going
to
talk.
I'm
sorry.
I
I
A
H
Oh
sorry,
I
didn't
know
I
was
muted,
still
yeah,
I'm
here
at
the
beginning,
so
this
is
this
is
aussie.
Do
you
want
to
talk
about
this
as
I
go
through
it.
H
I
Like
this,
one
works
over
the
pull
request,
but
it
will
work
over
issues
as
well,
so
what
the
bot
does
it
is
that
it
picks
out
the
checklist
from
the
issue
or
pull
request.
The
slash
command
is
commented
at
and
then
it
removes
the
initial
checks
from
the
checklist
and
calculates
the
percentage
otherwise.
H
A
Okay:
okay,
we
have
a
minute
left,
so
I'm
going
to
ask
a
question:
we're
not
going
to
get
to
everything
on
the
list.
What
are
people's
thoughts
on
as
a
as
an
event
as
making
a
request
for
a
badge,
the
number
of
reviewers
that
we
should
have
to
review
that
event.
A
A
D
A
That
justin
just
provided
all
right
folks,
well
we're
not
going
to
make
it
through
everything
we're
one
minute
over.
I
will
see
you
next
week
and
we'll
have
some
other
things
to
bring
and
talk
about
next
week.
I
really
appreciate
everybody's
time
and
feedback.
It's
very,
very
helpful.
Thank
you.