►
From YouTube: CHAOSS.D&I.May.20.2020
Description
CHAOSS.D&I.May.20.2020
C
B
A
B
A
A
D
E
D
A
B
D
F
F
B
B
A
B
Okay,
so
I
try
to
put
in
a
statement
from
the
part
of
the
applicant
and
part
of
the
reviewer,
the
review
statement
and
the
points
following
it
are
actually
similar.
Ups,
all
both
event
and
project
cases.
So
the
point
under
the
quotation
mark
is
actually
something
from
their
perspective
and
the
bullet
points
following
are
actually
something
like
and
like
what
we
would
like
to
do
in
badging
to
just
make
use
of
how
an
applicant
things
and
we
make
it
according
to
them.
E
A
Right,
the
eight
this
makes
sense
so
that
I
have
low
overhead
or
low
effort
to
request
a
badge
that,
once
the
process
is
complete,
the
badge
is
provided
to
me
simply
in
a
suitable
format.
That
makes
a
good
sense
from
our
respective
I'm
just
kind
of
telling
you
how
I
read
this
from
a
reviewers
perspective,
there's
a
an
efficient
way
for
the
reviewers
and
the
applicants
to
talk
to
one
another
to
provide,
as
you
say,
feedback
well
as
the
divine
define
responsibilities
and
guidelines.
It's
also
fair.
The
reviewer
checklist
review
checklist
implementation.
B
Okay,
so
the
first
thing
imagine
is
that
applicant
gives
them
the
details
like
right
now
we
have
PR
templates
so
which
have
questions
related
to
badging
like
different
metrics,
and
the
applicant
answers
that
so
review
checklist
would
be
a
more
condensed
form
of
how
those
metrics
actually
do
match
up
like.
If
we
are
evaluating
something
like
code
of
conduct.
B
So
right,
then
we
will
actually
would
have
to
go
in
and
evaluate
how
the
code
of
conduct
of
a
certain
project
or
an
event
works
out,
and
then
the
review
sheet
list,
which
will
exist
as
a
markdown
comment
on
the
pull
request,
which
is
being
used
for
the
badging
application
and
the
review
will
have
edit
access
to
it.
So
it
would
be
like
something
like
a
grocery
list
where
you
are
taking
component
when
you
have
them.
Does
that
make
sense,
yeah.
A
So
then
I'll
do
a
follow
that
doesn't
make
sense.
So
follow-up
question
would
be
if,
for
example,
there's
a
need
to
review
the
code
of
conduct
for
an
event.
The
reviewer
checklist
would
would
be
here's
how
you
go
view
the
code
of
conduct
or
that
you
need
to
look
on
the
website
to
observe
the
code
of
conduct
and
the
checklist
might
contain
a
different
statement
for
identifying
how
the
event
captures
attending
different
demographics
and
the
reviewer
checklist
might
have
different
ways
for
capturing
your.
B
Okay,
I'm
not
exactly
sure
how
I
am
going
to
go
ahead
with
the
review
checklist,
but
that's
a
good
perspective.
You
give
and
I
was
not
thinking
like
that.
So
for
me
a
review
checklist
was
more
like
if
something
is
up
to
the
standard
or
not,
rather
than
rather
than
the
reviewer
going
through
the
steps
to
evaluate
that.
But
maybe
those
lists
can
work
like
that.
A
F
B
A
B
A
B
D
I
hear
you
darling
again:
I
found
what
people,
what
people
found
useful
is
that
they
use
their
headset
like
if
you
know,
if
you
have
a
Bluetooth,
headset
or
something
so
on
the
phone
with
zoom,
it's
generally
more
marketed
with
that,
sometimes
than
the
actual
owns
microphone.
If
you're
using
yourself,
I.
D
Doodles,
if
it's,
if
it's
dangling
headset,
then
that's
what
the
noise
were
hearing.
But
if
you
use
a
Bluetooth
in-ear
and
it
doesn't
have
like
it's
not
dangling,
the
microphone
is
not
dangling,
then
that
that
that's
when
you
get
less
yeah
less
the
money
doesn't
brush
against
your
clothes
right.
But
that's
what
we're
hearing.
B
A
B
B
A
B
Okay,
dinners
are
people
who
would
actually
go
in
give
it
give
some
final
checks
to
the
application
see
if
everything
is
an
order
if
the
badges
have
been
saying
assigned
and
stuff
and
then
when
the
application
has
to
be
closed,
the
most
public
west,
or
whatever
else
needs
to
be
done
to
make
that
assignment.
Finally,.
D
Okay,
I
think
I
think
is
related.
We
related
more
to
being
a
triage
oriented
as
opposed
to
application
oriented.
So
you
know
what
process
applications
take
and
you
make
sure
that
everything
about
the
batching
repo
in
question.
You
know
the
PR
is
the
files,
so
you're
kind
of
doing
that
support,
work
that
is
github
or
get
lab
oriented.
You
know
on
how
to
make
sure
everybody's
efforts.
Are.
D
A
D
B
B
B
When
the
reviewers
and
the
applicants
think
that
the
review
is
complete
and
the
moderator
comes
in
when
the
review
seems
to
be
stuck
somewhere
in
between
so
take
moderator
could
actually
be
a
reviewer
who's,
not
actually
reviewing
that
particular
application,
auto
maintainer
themselves,
so
I
don't
know,
I
just
feel
it
to
me
too.
So.
D
D
A
A
Would
one
maintainer
suffice
and
would
one
or
not
one
reviewer,
but
you
know
with
ten
reviewers,
so
we
may
want
to
start
thinking
a
little
bit
about
number
of
people,
the
weekends
as
well,
just
because
we're
trying
to
balance
an
effective
program
with
human
capital,
yeah
Ezra
program.
That's
all
so.
D
B
D
Moderating
on
this,
and
not
not
in
the
reviewer
capacity,
that's
fair,
yep,
that's
good!
Yeah!
A
maintainer
can
be
any
ID
above
as
long
as
they
are
not
the
reviewer
of
that
particular
application
itself,
or
they
could
be
if
you
know
if
they
are
comfortable.
That
way.
The
state
here
that
the
challenge
here
is
not
moral,
it's
more
like.
If
you
have
to
do
two
two
jobs,
you
might
skip
a
beat
on
either
side.
So
the.
A
A
A
D
D
The
reason
why
we
want
to
use
BOTS
is
to
try
to
facilitate
the
process
to
close
to
close
gaps
that
basically,
instead
of
there's
someone
waiting
until
someone
is
available
to
help
them.
You
know
to
the
next
step,
if
that
God
can
do
that,
then
yes,
I
think
people
sadly
use
BOTS
and
other
repos
kind
of
say
like
nobody's
looking
and-
and
this
has
been
open
for
a
while,
we'll
just
close
it
if
important,
they
will,
they
would
have
looked
at.
You
know
like
bots,
should
not
show
you
to
the
door
kind
of
thing.
A
D
A
D
I
think
I
think
it's
a
some
update
of
the
DNI
badging
I
guess
I
can
give
a
very,
very
quick
just
recap.
So
so
obviously
it's
the
first
time
we're
starting
this
process
where
we're
working
with
you
know,
Austin,
Tola
and
we're
gonna
have
to
you
know,
hopefully
a
more
structured
process
to
go
about
internships
and
to
go
about.
You
know,
folks,
who
want
to
be
mentored.
D
You
know
in
badging
or
in
other
venues,
so
so
we're
gonna
we're
gonna
want
to
put
together
kind
of
a
a
guide
or
a
you
know,
a
process
that
will
document
by
the
end
of
the
first
round
of
internships.
But
you
know
so.
For
the
first
two
weeks
we
were
just
trying
to
figure
out
the
comfort
zone
for
everyone.
You
know
where,
where
there's
overload-
and
it
has
been
really
great-
you
know-
and
you
you
know
hopefully
will
love
I
guess,
give
them
a
good
experience
as
well.
D
A
That's
great,
thank
you
and
I
guess:
I'll
say
to
hasta
EMTALA,
who
just
dropped
off
we're
I've
reached
out
to
the
Linux
Foundation
auste
to
try
to
get
you
a
pass
to
open-source
summit.
North
America
I
mean
the
chaos
project
is
willing
to
pay
for
it.
So
if
you
have
an
interest,
let
me
know
it's
gonna
be
a
virtual
event
in
June
and
the
open
sort
of
summit
North
America
is
probably
the
one
of,
if
not
the
largest
Linux
Foundation
events,
let's
run
every
year,
and
they
just
have
great
tracks
on
issues
around
diversity.
A
A
Okay
and
then
I'll
just
be
in
touch
and
I'm
guessing,
it's
gonna
be
just
a
registration
code,
that's
what
I'm
hoping
to
get
and
then
I
can
give
you
that
registration
code
and
you
can
just
register
for
the
event
and
then
participate.
However,
you'd
like
to
participate,
there's
no
applications
on
our
part.
You
have
not
it's
really
just
for
you
to
participate
in
the
event.
A
A
B
A
So
it's
the
issue
tracker
inclusivity
metric.
We
obviously
have
the
documentation,
discoverability
and
accessibility
metric.
We
don't
have
time
to
take
that
on
today,
but
I'd
like
to
just
ask
you
to
go.
Take
a
look
at
the
metric
that
I
just
put
in
the
chat
I've
been
working
on
this
a
little
bit
of
to
kind
of
help,
get
it
into
a
state
that
I
think
we
could
consider
I,
don't
think
it's
ready
yet,
but
a
state
where
I
think
we
can
consider
really
thinking,
as
it
is
part
of
the
continuous
metric
release.
A
A
A
You
can
see
the
one
I
had
never
seen
that
one
before,
but
around
mentor
like
there's
a
mentor
available
for
this
issue,
so
trying
to
mark
issues
as
a
way
to
it's
a
great
idea
as
a
way
to
encourage
participation
in
a
project,
so
I've
been
working
kind
of
through
right,
where
the
description
thank
you
description
and
objectives,
I
was
I
was
hoping
she
would
be
here.
The
where
I'm
stuck
a
little
bit
right
now
is
around
data
collection
strategies.
A
E
E
E
E
E
E
E
E
E
C
E
D
I
could
I
if,
in
fact,
that
screenshot,
where
it
said
six
count
if
there
could
be
like
a
like
a
little
summary
line
after
account,
you
know
where
would
use
the
query
to
try
to
somehow
form
a
natural
language
sounding
phrase
based
on
the
filters,
and
then
you
know
so
it
would
be
six
issues
open.
You
know
like
something
like
that
based
on
the
query
and
then
that
would
make
it
a
good
visual.
That
is
just
you
know.
It's
a
natural
language
description.
D
Sometimes
they
do
those
like
numbers
and
then
they
just
say
a
data
summary
and
natural
language.
Are
you
hoping
to
describe
what's
in
the
issue?
So
no?
No,
no,
like
we
use
the
filter.
That
set
github
issue
is
and
and
then
good
first
issue.
So
if
we
find
a
way
to
use
the
filter
parameters
to
translate
that
to
a
natural
language
sounding
you
know
six
github
issues
that
are.
That
is
a
good
first
issue.
D
A
E
E
E
D
I
guess
between
those
two
plots,
you're
able
to
say:
listen,
you
go
from
this
to
this,
and
now
you
know
exactly
what
goes
on
right.
You
know
like
like
not
not
too
much
noise.
You
actually
pinpoint
with
between
between
the
two
views.
One
is
the
big
picture,
one
of
detail:
you're,
more
refined,
yeah,
yeah,.
A
D
E
A
So
then,
this
is
great.
So
then
I
think
this
will
help
all
to
continue
to
work
on
the
data
collection
strategies
actually
watching
you
helped
with
the
big
big
question
strategies,
so
that
was
thank
you.
I
can
write
that
up
a
little
bit
better.
Now,
oh
and
then
the
hope
is,
is
the
weekend
that
maybe
Miriam
I'll
moving
on
the
call
next
week
and
we
can
or
when
I
see
your
arm.
I'll
say
that
this
is
moving
forward
or
all
even
finger
on
this
one.
So
thank
you,
okay,
yeah
and
then
Eric
next
week.
A
A
D
Are
we
talking
about
documentation,
the
documentation,
accessibility
that
please
so
so
so?
Was
it
last
week
that
we
kind
of
said
we
try
to
you
know
PR
the
first
bit
I
came
up
here
last
week
right
it
was
last
week.
Yes,
yes
and
I.
Guess
just
just
to
see
how
everybody
here
is.
You
know
feeling
that
that
direction
that
you
know
since
so
the
way
I
kind
of
looked
at
it
is
maybe
before
we
seek
clarity
in
all
things,
we
want
to
anchor
some
clarity
and
then
all
things
can
find
their
clarity
around
that.
D
So,
if
we
PR
the
first
part,
then
we
will
know
whether
or
not
two
more
parts,
one
look
a
certain
way.
It
would
allow
the
open
source
process.
You
know
the
transparency
aspect
of
it
to
refine
what
we're
anchoring
as
the
first
part,
and
it
could
even
drive
interest
for
people
who
want
to
work
on
the
two
other
parts
of
this
write,
two
or
more.
A
D
So
maybe
I
don't
know
if
we
want
to
I,
don't
know
how
stead
do
you
want
to?
Maybe
you
know
not
just
a
stew,
but
you
know
if
anybody
here
would
like
to
PR
that
part
you
know
from
from
the
newcomers.
You
know
just
give
them.
It's
not
a
big
deal.
Oh,
but
yeah
he'll
new
comer.
To
do
it.
That's
great!
This
way
they
kind
of
like
get
right
into
it.
It's
a
good
first
issue
right,
oh
no,
mentorship
right!
This
is
a
man,
the
mentor
PR,
so.