►
From YouTube: CHAOSS.D&I.May.27.2020
Description
CHAOSS.D&I.May.27.2020
C
A
A
D
A
A
A
E
C
A
A
B
A
A
A
A
So
the
way
that
we
work-
and
this
is
for
anyone
who
might
be
new
to
our
working
group-
we
always
have
different
people
proposing
metrics,
and
then
we
discuss
them
here
on
the
call,
and
so
there's
no
right,
there's
no
wrong.
We
just
like
to
hold
it
up
to
the
light
and
get
people's
feedback
and
input.
A
A
B
I
added
a
couple
of
under
the
examples,
I
probably
should
thought
those
the
suggestions
you
could
see,
which
ones
but
I
added
a
note
that
people
with
the
repository
merge
access
or
sometimes
referred
to
as
owners.
So
that's
what
the
kubernetes
community
calls
them,
although
this
may
be.
You
can
argue
that
maybe
those
are
now
but
leave
it
as
well.
Okay,
wait
a
minute,
so
technically,
people
in
the
owners
are
more
like
maintainer
and
people
and
people
that
are
reviewers
all
right.
B
Let
me
think
about
that
one,
a
little
bit
more
and
then
I
also
added
contributors
to
our
organization
members
for
the
repository.
So
this
is
another
kubernetes
distinction
like
the
first
step
on
the
contributor
ladder
is
that
they
make
you
an
org
member,
and
that
gives
you
access
to
people
can
assign
issues
to
you
and
things
like
that.
So
it's
it's
kind
of
the
first
step
in
the
kubernetes
ladder.
Anyways.
A
B
F
A
A
B
So
the
more
I
look
at
this,
the
more
of
a
little
bit
concerned
about
about
how
we're
approaching
this
metric,
so
celui
backups,
like
the
the
chaos
project,
tries
to
you
not
not
have
judgments
about
things
but
is
more
about
how
do
we?
How
do
we
measure
the
thing
and
less
about
how
do
we
judge
whether
it's
successful
or
not,
for
example,
and
if
you
look
at
this
I
think
a
lot
of
this
is
more
prescriptive
about
what
projects
should
or
should
not
do
and
less
about?
How
do
we
measure
this.
A
B
I'm,
realizing
that
my
suggestions
are
even
going
along
those
lines
because
I'm
sort
of
drawing
on
on
what's
already
here
so
let's
I
mean
do
other
people
are
other
people
concerned
about
that.
What
other
people
think-
and
this
is
great
stuff-
and
these
are
great
suggestions,
but
this
feels
less
like
metrics
and
more
about
best
practice.
A
G
A
What
what
you're
seeing
here
is
already
something
that
Emma
had
created
and
I've
put
into
our
template,
and
it
was
very
much
a
guidance
document.
Here's
what
you
should
do
and
I
think
that
still
comes
through.
As
you
note,
I
tried
to
kind
of
address
this
by
saying
we
can
use
these
principles
as
checklists
I
put,
doesn't
understand,
but
the
wording
itself
is
still
very
prescriptive.
I
agree
with
that,
but.
D
B
Eunuchs
I'm
looking
I
was
I
noticed
this
with
the
first
one,
which
is
you
know,
and
then
I
added
one.
That
was
also
judging
and
prescriptive,
but
you
know
if
you
look
at
the
leadership,
should
be
set
up
for
regular
review
and
renewal.
This
is
very
much
a
what
what
people
should
do,
but
I
like
I,
like
the
idea
of
rewording
them
into
questions,
because
maybe
that
would
you
know
is
there?
Is
there
a
period
of
you
know,
renewal
for
for
leadership,
roles
or
a
term
for
leadership
roles?
Something
like
that?
B
B
A
A
E
E
E
H
Think
bandwidth
wise,
it
becomes
very
impossible.
We've
tried
that
in
others
and
calls
with
Tola,
so
what
we
could
do
is
we
sometimes
let
him
request
remote
control?
So
so,
if
you
want
to
open
the
page-
and
you
don't
mind
if
you
control
to
your
mouse,
that
that
can
help
ooh
yeah,
not
nice,
when
the
host
has
to
relaunch
their
zoom.
D
H
H
You
know
so
what
we're
looking
at
is
I
guess
the
page
on
requesting
free
support
for
an
open-source
project
to
use
Crowden.
So
so
we
basically
had
the
proposal
borrow
based
on
on
what
Crowden
has
indicated,
but
then,
as
we
got
into
the
weeds
of
things,
we
came
up
to
a
list
of
kind
of
like
things
that
we
have
to
put
in
motion.
In
order
for
us
to
get
Crowden,
you
know
for
free,
but
I
guess
total.
H
Give
me
one
sec,
I'm
gonna,
take
the
take
that
little
floating
window
that
you
don't
see
out
of
your
way.
So
we
don't
click
on
it
by
mistake,
because
you
were
doing
that
all
right
there
you
go
control
again:
okay,
yeah,
all
right!
Not
now
the
screen
is
free
of
you
know,
magical
buttons
that
you
don't
see.
E
A
H
Can
I
can
I
jump
in
on
that
one,
because
we
are
already
looking
into
how
we're
gonna
manage
the
chaos
community,
/
news
route
and
yes,
the
other
routes
that
have
used
came
up.
I
think
it's
it's
more
just
a
realization.
A
couple
of
weeks
in
that,
if
we're
going
to
have
free
crowd,
then
to
go
ahead
with
that
route
and
yesterday
is
sorry
to
go
ahead
with
this
approach
of
crowd
and
for
internationalization,
which
yesterday's
meeting
at
the
community
meeting
kind
of
said,
we
want
to
do
internationalization
away
from
Crowden.
We.
H
So
bye-bye
you
know
by
by
looking
at
all
of
this
I
guess:
Toula
is
just
recapping
his
first
two
weeks,
but
it's
not
like
we're
likely
going
to
I
had
with
Robin
we're
gonna
have
to
pivot
and
I.
Think
Tolos
work
will
align
well
with
with
the
chaos
white
efforts
that
were
described
discussed
yesterday.
E
H
H
H
Yesterday
we
talked
about
every
horn
could
happen,
I
ate
and
repo
under
it
on
github
or
you
know,
get
lab
or
whatever,
and
it
could
refer
to
the
other
repos
as
sub
modules.
So
so
this
is
just
a
little
mock-up
of
that
example.
Obviously,
and
not
using
sub
modules
at
this
point,
but
you
know
in
every
folder
structure,
we
just
kept
a
bare
minimum
of
markdown
content
to
kind
of
like
test
the
idea
first
with
folders,
but
then
we
would
replace
it
with
sub
modules,
as
our
translation
process
is
in
place.
H
E
H
E
E
H
Yeah,
so
so
just
one
last
point
and
I
think
really
that's
a
recap
of
where
we
are
so
when
we
do
translate,
I
really
do
believe.
We
want
to
explore
the
github
actions
route.
So,
however
process
we
want
to
use.
Oh
you
know,
I
I'm,
still
not
not
sure
what
the
details
were
in
yesterday's
meeting
and
you
know
we're
gonna
catch
off
on
those,
but
I
really
think
that
todos
work.
You
know
from
from
and
github
actions
standpoint.
H
Crowden
is
just
one
variable
and
if
we
are
using
a
different
platform,
if
we're
using
any
form
of
action,
oriented
solution,
then
you
know,
hopefully
that
would
be
an
area
where
we're
told
us
efforts
over
the
summer.
Can
you
know
help
us
deliver
that
and
scale
it
through
chaos,
alright,
so
cola?
If
that's
it
or
do
you
have
any
more
input.
H
H
E
A
Well,
thank
you
very
much
for
investigating
how
we
can
do
translation.
I
know,
there's
an
active
email
threat
on
the
mailing
list.
That
came
out
of
the
conversation
on
the
weekly
meeting
yesterday.
So
if
you
I
think
that's
the
place
where
we
have
the
conversation
right
now,
because
it's
more
than
just
the
DNI
working
group.
So
let's
continue
the
conversation
on
the
mailing
list
and
then
under
weekly
calls.
H
Yeah,
so
what
one
request
I
would
want
to
add
if
possible,
if
internationalization
is
going
to
be,
you
know
an
initiative
within
chaos.
If
we
could
schedule
bi-weekly
or
a
weekly
fall
I,
it
doesn't
matter,
but
I
think
bi-weekly
would
be
a
good
start
for
for
folks
from
the
different
working
groups
to
come
to
a
space
where
it's
just
a
lot
of
to
address
this,
and
you
know
with
that,
without
putting
it
in
the
way
of
everybody
if
they
feel
it's
getting.
You
know
it's
taking
time
out
out
of
their
weekly
hours,
so
yeah.
A
C
G
Summarize
what
this
metric
was
for.
It's
mainly
a
way
of
seeing
looking
at
a
project's
issue
tracker
and
seeing
how
inclusive
it
is,
and
the
ankle
we've
tackled.
This
with
is
mainly
having
the
issue
tracker
being
diverse
in
terms
of
issues
that
are
there
so
having
issues
that
are
documentation,
issues
that
are
code
related
issues
that
require
different
skill
sets
and
issues
that
could
be
like
done
by
either
someone
who's
a
newcomer
or
a
core
member
or
an
occasional
contributor.
C
So
this
is
the
total
number
of
uses
of
this
label
across
13,000
ish
repositories
and
then
the
next
step-
and
you
can
see
that
our
classification
scheme
is
really
focused
on
general
classification,
but
you
may
pass
through
this
list
and
identify
things
that
are
diversity
and
inclusion
related.
So,
for
example,
I
suggested
in
our
last
discussion
and
we
have
an
academic,
yet
the
possibility
of
a
good
first
good,
first
contribution
label
that
a
label
like
that,
if
used
or
f1.
G
C
C
Now
it
is
our
open
coding,
so
in
a
in
a
qualitative
research
setting
or
academic
Serdar
I'm,
an
academic
and
so
Kate
Stewart
from
Linux
Foundation
is
a
academic
minded
person
and
so
open
coding
is
just
we
think
of
words
that
make
sense
and
now
she's
going
through
and
axially
coding
them,
which
means
she
used.
She
came
up
with
a
bunch
of
labels
just
by
looking
at
them,
and
then
she
looked
at
all
of
them
and
normal
them
down
to
a
smaller
set
and
is
going
through
the
top
50
or
200
I.
C
C
G
Yeah
I
think
having
the
frequency
of
that
label
usage
either
between
projects
or
within
a
project
would
be
interesting
with
it
like
within
the
same
project.
They
might
give
us
a
way
of
knowing
how
frequent
a
label
like
good
for
a
newcomer
is
compared
to
other
labels
sure
and
between
projects.
Maybe
it's
a
way
of
like
looking
at
compared
to
other
projects,
how
inclusive
a
project
is
mm-hmm.
C
C
That's
one
of
the
reasons
I'm
starting
to
just
sort
of
lurk
and
diversity.
Inclusion,
because
I've
heard
some
of
the
things
that
we're
doing
in
the
working
groups
are
more
active
and
might
be
helpful
in.
This
is
one
so
I've
made
a
note
to
add
the
number
of
repos
using
an
issue
label
and
also
label
or
a
label
distribution
with
that
within
a
recom
project
or
a
repo.