►
From YouTube: CHAOSS.D&I.June.10.2020
Description
CHAOSS.D&I.June.10.2020
A
Start
the
recording
so
I
think
I'm,
leading
this
one
today
so
welcome
everybody
to
the
June,
10th
chaos,
diversity
and
inclusion
meeting.
As
all
meetings
right
now,
I'd
like
to
point
out
that
we
are
joined
by
Elizabeth
Barron,
the
new
KS
community
manager,
so
I
will
applaud
all
week
and
wave
and
say
how
thankful
I
am
to
have
Elizabeth
joining
us,
so
welcome
Elizabeth
I
won't.
Have
you
introduce
yourself
in
every
meeting
they
can
watch
the
community
call
video
if
they
want
to
see
your
overview?
A
A
So
a
facilitator
for
next
week,
so
in
the
DNI
working
group
we
like
to
kind
of
rotate
facilitation.
I
am
the
the
default
facilitator,
which
has
become
the
every
other
week,
facilitator
and
gay
organs
so
that
I
actually
mad
Ladd.
We
had
a
lot
of
people.
Do
it
so
we'd
like
to
rotate
facilitation?
Do
we.
A
A
Alright
gave
her
guitars,
alright,
okay,
so
we
we
have
a
number
of
in
the
repository
which
I'll
post
here.
A
A
B
B
So
the
idea
here
was
to
create
resources
for
people
on
how
to
get
started.
We've
given
talks
about
this
and
we've
shared
this,
but
we've
never
actually
created
resource
for
people
on.
If
you
want
to
get
started
with
your
metrics
journey,
here's
what
you
can
do
my
vision
for
this
is
that
it
becomes
part
of
the
metric
release
that
some
section
of
the
metric
released.
B
We
have
a
document
saying
here
are
things
to
consider
choosing
a
data
source
having
your
goal
question
metric
approach,
those
kinds
of
things:
okay,
I
know
we
are
doing
other
things
to
get
metrics
out
there
and,
yes,
that
is
accomplishing
a
lot
of
what
this
was
about.
But
I
still
have
a
bigger
vision
for
this
content.
C
C
The
question
I
think
I
have
sorry
you
do.
One
question
I
had
here
is
what
milestone
would
would
be
more
generic
or
more
generalized?
Sorry
about
you
know,
vision
that
we
want
to
get
to
not
not
just
future
things
to
consider,
but
rather
you
know
vision
that
we're
working
at,
even
if
it's
away
from
the
actual
issue
itself,
but
indirectly,
as
gear
of
mentioned
their
gear
up.
That's
the
vision,
I.
C
So
if
we
look
at
this
screen
right
now
on
the
right
panel,
there's
labels
projects
milestones
milestones
is
the
one
thing
that
you
could
only
assign
one
my
an
issue
to
a
single
milestone,
so
issues
that
are
categorically
nested
under
a
bigger
topic
like
you
know,
I,
guess,
v-0
or
v1
release.
You
know
that
that's
how
they
would
use
milestones
right.
So
so
you
would
create
a
milestone
that
is
very
descriptive
and
named,
and
you
would
slot
those
issues
under
it
and
Jen
yeah.
B
One
of
the
things
that
goes
through
my
mind
is
that
this
is
not
a
DNI
issue
and
maybe
it's
a
bigger
issue,
maybe
something
we
can
ask
in
the
common
group,
because
I
think
this
is
a
general
guideline.
If
you
just
removed
the
DNI
part
of
it,
because
how
to
get
start
with
chaos,
metrics
I
think
we
should
have
something
like
that
in
our
metrics
release
or
on
the
website
or
somewhere.
C
Yeah
so,
but
would
it
move
to
a
repo
where
we
would
close,
or
would
the
minds
stole
an
idea,
be
useful
in
that
repo
as
such,
because,
like
I'm
afraid,
if
we
just
move,
it
will
kind
of
like
perpetuate
like
I'm,
not
talking
about
this
single
issue,
but
rather
about
how
we're
dealing
with
issues
that
are,
you
know,
sailing
away
just
moving
it
to
another?
Repo
doesn't
really
address
the
issue.
I
were
you
know
coming
to
the
decision
to
move
it
so
I,
don't.
D
C
A
B
B
C
I
mean
if
the
issue
is
closed.
It's
always
there
indexable
for
for
traceability.
So
when
we
are
proposing
or
contrasting
how
the
idea
evolved,
there's
input
from
people
on
issues
that
are
closed.
That
basically
kind
of
you
know,
influence
our
process
over
the
years,
so
closing
it
on
the
right
repo,
giving
it
a
label
that
it
relates
to
a
particular
long-term
objective
or
milestone.
I
think
it's
it's
ideal
for
traceability,
so
that
every
comment
related
to
the
thread
that
led
to
a
particular
move
would
kind
of
be
traceable.
But
again
you
know
like
that's.
B
C
A
C
A
Gerd,
do
you
have
thoughts
on
this?
Not
what
to
do
with
this.
At
the
moment,
you
you're
the
owner
of
this.
B
A
A
Dare
I
suggest
we
look
at
another
issue?
This
is
gonna,
be
as
a
slide
right,
or
does
somebody
have
a
better
approach
here
that
we
asked
people
on
this
call
to
take
a
look
at
one
of
the
39
issues
that
are
not
here.
We've
got
a
these
have
to
move
a
little
bit.
A
lot
of
these
have
become
very
stale,
and
so
my
concern
is:
is
that
they're
just
sitting
there
as
placeholders,
with
no
real
action
associated
with
them?
A
A
B
B
Or
we
just
say
if
the
idea
is
not
being
acted
upon
within
two
months
or
one
year,
we
just
closed
it.
That
can
be
a
rule
because
apparently
might
have
been
a
good
idea,
but
we
don't
actually
you
I'm
not
doing
anything
with
it,
so
it
gets
in
the
way.
I
don't
keep
with
having
a
rule
like
that
Mike
Mattek.
If.
A
So
for
those
of
you
that
don't
know
the
metrics
repo
was
a
way
for
us
to
just
capture
all
metric
ideas,
all
of
them,
and
it
became
this
really
unwieldy
kind
of
terrible-looking
repository
that
didn't
do
anything
for
anybody,
and
my
concern
here
is
that
we're
kind
of
running
into
the
same
thing
around
issues
that
it
just
becomes.
We
have
40
or
50
issues
dating
back
two
years
and
posting
an
issue
doesn't
do
anything
for
anybody.
A
A
C
I
think
we
can
also
have
org-wide
project
for
it
and
those
you
could
actually
have
issues
in
hoard
white
repos
belonging
to,
and
but
the
thing
with
project
is
that
you
could
have
an
issue
under
more
than
one
project.
So
it's
not
it's
not
like
canonical
it's.
You
know,
I,
guess
chaotic
that
you
don't
know
exactly
of
this
project
with
that
project
will
close
the
issue
but
yeah.
So.
A
Why
don't
maybe
I'll
propose
this?
That
I'll
take
a
pass
through
the
issues
we
do
have
a
metric
idea
label
and
start
labeling
any
metric
idea
as
such
that
somebody,
okay
and
label
everything
that's
a
metric
idea
as
such
and
simply
close
those
if
they've
haven't
been
acted
on
for
two
months.
Four
gates
come
in
so
then
we
they're
labeled
third
they're
closed
and
we
can
always
filter
back
on
met,
closed
metric
ideas
if
we're
looking
for
inspiration
are
people.
Okay
with
that
and.
B
B
B
B
B
A
C
Yeah
yeah,
no,
no
like
like
definitely
labeling,
closes
ideal
as
long
as
labels
are
visible
for
people
to
know
which
one
they
could
pick
if
they
want
to
look-
and
you
know
you
know,
the
problem
with
labels,
though,
is
that
sometimes
people
ask
for
the
ability
to
label
and
then
they
make
new
labels,
and
then
you
end
up
creating
labels
that
conflict
with
existing
ones.
So
we.
A
C
C
F
C
B
A
The
metrics
toolkit
gives
you
like
deploying
this
metric
should
take
10
minutes,
and
this
is
how
you
would
go
like
the
actual
steps
you
would
go
about
doing
it.
It's
a
really
really
good
idea,
and
it
just
gives
people
kind
of
ways
to
think
about
approaching
metrics
so
like
this
is
like.
If
you
want
to
deploy
speaker,
demographics,
that's
hard
and
it's
gonna
take
a
day.
A
E
A
That
could
very
well
be
yeah
right.
If
you
want
to
deploy
age
of
issues,
here's
kind
of
what
it'll
take
to
get
that
done,
using
the
tools
that
we
have.
It
might
take
one
person
to
actually
set
it
up,
for
example,
Ingram
or
lab
it's
a
half
a
day's.
Hopefully
it's
not
a
half
a
day's
job,
but
it's
a
half
a
day's
job,
but
yeah,
no
I,
agree
and
so
I
part
of
what
is
happening.
A
A
little
bit
in
the
issues
for
me
is
that
the
idea
of
a
metrics
yet
is
being
confounded
with
some
of
the
the
ideas
of
new
metrics
and
I
think
it
would
be
important
to
separate
those
that
here's
a
metric
full
stop,
and
then
we
have
the
metrics
tool
kit
that
can
help
people
approach
the
metrics
in
in
kind
of
these
meaningful
ways.
I,
don't
know
what
people's
thoughts
are
on
that,
but
I
think
you
got
it
right.
Elizabeth,
okay,
you've
been
around
this
for
a
while.
B
F
A
F
A
E
A
A
C
Remove
sorry,
yes,
sir
Arun
I
think
sorry
I,
don't
know
how
to
pronounce
your
name.
He
wrote
in
the
chat,
I
think
very
much
something
a
good
idea
worth
exploring
or
just
least
bringing
up
to
close
the
agenda
item
before
that
that
last
one
had
the
one
about
issues.
I
did,
oh
so
in
the
minutes
and
I
think
so.
I
think
the
idea
is
to
maybe
consider
this
being
a
micro
task
for
a
google
Summer
of
Docs
participants
to
help
label
close
or
move
issues.
A
C
A
All
right,
so
let
me
let
me
move
on
to
a
couple
a
couple
of
the
outstanding
issues
that
we
are
I'm,
sorry
outstanding,
metrics
that
we
have
so
at
the
moment
and
I
think
we're
really
close
on
just
a
couple
here.
So
if
I
show
my
screen
again,
so
we
have
I'm
in
the
minutes
on
the
top
of
page
2,
we
have
issue
inclusivity.
A
C
B
D
D
B
D
A
A
A
F
A
Job
so
he's
very
nice
when
you
answer
your
own
question
so
in
terms
of
auger
providing
tools
providing
the
metric
Sean
had
said
yes,
so
I'm
gonna
resolve
that
his
answer
was
I.
Think
a
little
bit
different,
then
from
an
inclusivity
perspective,
but
I
think
if
I
can
provide
insight
on
labels,
we
can
kind
of
do
the
work
that
Miriam
is
proposing
here.
So
I'm
gonna
resolve
that.
A
A
So
my
proposal-
just
because
this
came
up
on
the
common
call
I-
think
Elizabeth
brought
this
up
yesterday,
because
we're
kind
of
getting
close
to
being
out
a
month
for
release
what
I
suggest
is
we
go
ahead
and
create
the
issue
in
the
PR?
This
one
will
actually
be
available
for
public
comment
for
like
seven
weeks
that
we
don't
do
a
public
comment
period
now
that
closes
during
the
public
comment
period
of
the
next
big
release.
So
that
makes
sense.
A
So
if
we
release
the
metric
right
now,
it
would
be
part
of
the
continuous
release
cycle
and
it
would
go
under
a
four
week
review
process
and
then
that
four
week
review
process
would
close
July
10th,
which
is
fine,
but
that
closing
it
on
July.
10Th
is
right.
In
the
middle
of
the
big
release
review
comment
period,
the
cadence
is
a
little
bit
off
on
these
two
things.
Does
that
make
sense.
A
D
A
B
A
D
D
B
D
A
A
A
A
D
B
B
A
Again,
always
nice,
when
people
can
just
talk
their
way
through
their
own
questions,
they
don't
need
answers
from
anybody,
so
I
I
will
say
one
of
the
things
that
has
been
a
little
complicated
in
this
document.
That
has
three
different
metrics
involved
in.
It
is
the
resources
because
we
so
this
one
is
actually
document
usability
right,
which
I'm
not
asking
that
we
take
a
look
at
it,
but
we
have
different
resources.
B
A
A
List
and
I
don't
propose,
we
need
to
do
it
now,
so
it
makes
sense
to
folks,
yes
and
I.
Think
this
list
is
the
kind
of
the
same
list.
That's
gonna,
be
showing
up
for
document
discoverability,
it's
the
same
list
of
resources,
that's
gonna
be
showing
up
for
accessibility,
and
so,
if
we
could
just
spend
a
little
bit
of
time
in
the
review
period,
just
kind
of
examining
the
resources
and
thinking
about
what
the
best
resources
are
to
share
it
with
people
on
that
metric.
That
would
be
good
all
righty.
A
F
The
programs
they're
using
for
it
are
actually
pretty
slick,
but
it
was
it
was.
It
went
really
well
I
think
so
that's
going
to
be
on
the
29th
that
that
is
shown
and
open
for
questions
and
I'll
be
there.
So
what
time
is
it?
Do
you
remember?
Oh
I'd
have
to
pull
out
the
schedule.
I'll
put
that
in
the
chat
put
it.
A
In
the
minutes,
okay,
so
the
way
that
it
works
for
open
source
in
North
America
is
matt,
has
pre-recorded
the
session
for
DNI
badging
is
probably
20.
Minutes
would
be
my
guess
and
then
there'll
be
30
minutes
for
Q&A,
which
Matt
will
be
at
as
a
live
discussant,
so
I'm
not
gonna,
be
able
to
make
it
on
the
29th,
so
Matt
will
be
doing
it,
which
is
awesome.
So
if
you
could,
please
put
that
on
your
calendar
and
ask
Matt
really
hard
questions
about
the.
A
B
A
The
the
participants
take
a
look
at
those
tasks
and
issue
pull
requests
to
software.
They
issue
pull
requests
or
repositories,
and
we
need
basically
a
couple
people
available
for
the
day
which
I
have
the
dates
in
there.
September
29th
I
think
is
the
day
of
the
open
source
day
to
be
there
to
be
able
to
answer
questions
merge,
pull
requests.
You
know
what
I
mean
to
be
active
in
the
repositories
to
actually
do
the
work,
so
Shawn
had
done
it
in
person
last
year.
B
A
A
B
F
A
A
Anybody
have
any
other
things
to
bring
up
in
the
interest
of
stopping
at
10:51,
which
is
the
time
now
I
say.
Thank
you
so
much
everybody
for
all
of
the
excellent
input.
We
got
two
metrics
under
review
today,
which
is
a
big
thing
and
I.
We
unlocked
it's
just
a
little
bit,
which
is
also
a
really
big
thing.
So
right.