►
From YouTube: CHAOSS.D&I.December.2.2019
Description
CHAOSS.D&I.December.2.2019
A
A
C
A
A
D
C
A
A
The
sponsorship
metric
is
the
one
that
we
worked
on
last
time
and
solid,
just
joined
in
time.
I'm.
Sorry,
I'm,
really,
oh
you're!
Just
on
time.
We
were
just
starting
to
talk
about
the
sponsorship
metric
that
you
created,
pull
request
form
here.
I
can
share
my
screen
and
we
can
walk
through
it
together.
A
A
F
F
F
A
F
All
right
so
I
think
yeah.
So
from
your
end,
I
mean
you've
reviewed
this.
You
should
have
been
able
to
commit
and
I
you
know.
After
all,
I
should
be
the
one
who's
getting
like
an
error
message.
Maybe
we
can
now
switch
back
and
then
you
you
should
see
whether
we
should
land
this
a
long
time.
I'm
sorry
I
came
in
late,
so
I
missed
that
part
of
the
discussion.
A
A
So
what
what
this
changes
is?
One
to
add
the
sponsorship
metric
and
the
question
was
how
effective
are
longtime
members
respond
to
people
in
supporting
diversity,
including
communities,
and
this
is
the
but
just
open
apartment
here.
This
is
the
metric
that
we
worked
on
for
now
over
a
year
and
that
being
reviewed
and
revised
at
the
open-source
summit,
North
America
and
now
we
put
it
into
the
new
template
and
revised
the
last
week
or
last
two
weeks,
I
think
last
week,
and
so
the
proposal
is
to
get
this
merged.
A
A
F
F
It
feels
like
I'm
cheating,
because
everybody
else
did
the
work.
I
just
did
the
sign
you
know,
and
so
I
I
wanted
to
add.
You
know
co-authored
by
and
I
think
it's
a
good
practice
moving
forward
that
if
we're
anything
else
where
we
keep
a
list
of
everyone,
who's
been
editing
that
document,
if
we're
removing
it
to
commit
like
we're,
doing
commit,
we
do
a
co-authored
by
and
we
had
the
github
users
you
know
for
who
are
working
on
the
dock,
and
this
way
everybody's
mentioned
for
traceability,
mm-hmm.
G
F
Categories
like
in
the
released
metric
since
we're
writing
in
Google
Docs
what
will
be
marked
down,
then
we
can
do
like
a
HTML
style
comment
at
the
top
and
anyone
who's
been
editing
with
just
need
to
review
with
that.
We've
had
their
name
and
I
think
the
email
they
use
to
commit
and
so
like
signed
off
by.
B
F
A
G
F
G
F
F
F
So
after
after
you
know
the
first
sheet,
your
fewest
ethics
and
I
did
this
this
not
like
final
or
permanent
or
anything,
but
it's
because,
as
I
went
through
the
other
sheet,
especially
this
one
I
discovered
that
they
kind
of
have
like
more
columns
and
so
I
figured
okay.
We
wanna
we
want
to
have
a
reasonable
amount
of
columns
that
people
don't
need
to
add
new
ones,
and
so
this
column
being
the
template.
If
it's
going
to
be
permanently
there,
then
I
thought
okay.
F
F
Often
it
will
just
say
you
have
to
you
know
it
just
does
that,
but
it
can
allow
you
to
enter
another
value.
It
only
gives
you
a
warning.
Really.
That's
all
me,
you
know
the
title
was
too
large,
so
the
column
was
taking
too
much
space
because
of
the
title
and
then
under
it
was
why
it
was
eating
up
space
for
remarks
and
another
column,
which
is
the
contact
person.
F
So,
if
we're
going
to
harmonize
all
the
columns
across
the
sheets
to
prevent
you
know
the
sheets
from
being
from
being
restrictive
and
to
prevent
them
from
from
being
overly,
you
know,
like
people
just
doing
more
columns,
and
then
you
know
we
run
into
conflicts
of
what
it
was
meant
by
something.
So
anything
that
is
in
contact
implies
get
to
that
person
first,
but
you
want
to
leave
it
as
contact
or
assigned
to
or
point
person
that
I
think
it's
fine.
How
does
this
contact
yeah
and
then
links
and
other
comments?
F
G
I
think
this
is
these
temp.
These
sheets
have
kind
of
reduced
I
mean
what
you
have
here
is
extremely
helpful,
because
they've
kind
of
reduced
down
to
really
that
first
column,
which
is
whether
they're
ready
or
not
to
be
part
of
the
release,
because
that
signals
to
Kevin,
then
obviously
the
metric
name
being
on
the
new
template
is
critical.
G
F
Okay,
Tom
they're,
good,
alright,
cuz
cuz
I
mean
it
doesn't
hurt.
If
we
split
C
into
two
smaller
columns,
there's
width
for
it,
one
of
them
would
be
tempted.
The
other
one
would
be
PR.
It's
also
used
just
to
add
a
link
to
the
PR
when
it's
being
worked
on
or
the
doctor
or
something
not
okay
done.
No
more.
No
more
nagging!
F
C
A
C
F
G
G
F
C
F
G
F
F
G
F
C
F
Template
so
so
everything
that
is
not
pending
in
and
more
is
really
no
template
at
this
point.
That's
correct
good.
That
now
makes
a
lot
more
sense.
Yeah
sure
was
what
it
wasn't
flying,
but
I
just
completely
understood
it
did
good.
Okay,
thank
you
all
right,
so
so
I'm
yeah
I'm
gonna
carry
over
the
format's
I'm,
not
gonna,
replace
the
sheets.
F
F
A
C
A
C
A
G
C
A
G
A
B
B
Know
kind
of
the
question:
do
we
recognize
all
contribution
types
and
equal
proportions
like
the
common
metric,
the
common
working
group,
it
would
be,
you
know
like
what
are
the
contribution
types
and
it
would
be
more
sort
of
more
atomic,
whereas
I
would
see
needing
to
have
a
metric
like
this
in
diversity
and
inclusion,
because
you
know
how
do
we,
how
do
we
recognize
them?
How
do
the
different
types
of
contributions
impact?
How
inclusive
the
project
is?
Does
that
make
sense?
Yep.
B
B
A
A
A
F
B
B
Do
you
feel
like
from
a
data
collection
standpoint?
There
should
be
something
more
than
just
observing
it
from
the
project
webpage,
especially
if
I
think
there.
There
are
loads
of
not
obvious
by
looking
at
people
things
to
think
about
when
it
comes
to
diversity
and
inclusion,
and
it
seems
like
maybe
maybe
something
sorry
I
was
thinking
out
loud.
Maybe
something
around
asking
for
you
know
asking
the
board
chair
for
a
report
of
the
diversity
of
the
to
catch
sort
of
I.
Don't
know,
I,
don't
know
what
you
call
them
invisible,
yep.
G
B
A
A
C
A
G
C
D
A
B
I
don't
know
if
we've
made
much
progress
on
the
documentation
since
we
talked
about
it
at
Kaos,
Khan
and
started
work
through
it
in
the
workshop.
But
this
was
the
group
that
I
was
sitting
in
and
the
challenge
we
kept
having
as
we
were
as
we
were
working
through.
It
is
the
difference
between
what
makes
good
documentation
and
what
makes
your
documentation
help
with
diversity
and
inclusion.
G
G
G
B
F
F
You
know
other
forms
of
communicating
the
same
message
and
so
like
like
for
me,
that's
one
of
my.
My
areas
of
interest,
like
Marquette,
has
been
really
trying
to
eliminate
obstacles
I
personally,
so
I
guess
within
this
room.
Are
we
talking
about
documentation
here
as
the
convention
of
using
markdown?
F
B
A
B
F
B
F
There
is
actually
an
updated
specification
for
accessibility,
I
mean
if
documentation
and
collaboration
tools
are
screen
readable
and
you
can
zoom
in
and
zoom
out
and
make
sure
there's
in
what
color
contrast.
These
are
all
things
that,
if
you
do
proper
web
page
construction
and
proper
document
structures,
these
are
all
things
that
tools.
Do
they
don't
close
the
gap
between
a
person
collaborating
with
another
person
if
they
have
different
conventions
due
to
different
mechanics
of
collaboration,
the
mechanics
are
a
function
of
what
what?
F
So
so,
when
we're
talking
about
the
annoying
and
occupation,
that's
that's
one
of
the
biggest
pain
points.
I
have
personally
I.
Hardly
can
learn
anything
if
I
read
the
documentation.
I
have
to
learn
by
finding
ways
around
documentation,
because
a
lot
of
the
documentation
may
be
visible
to
me.
The
patterns
of
assuming
that
I
use
cognitively
because
of
my
name
is
D
and
because
of
the
difference
in
pace
that
I
have
because
of
other
aspects
like
digital
processing.
F
F
That's
a
mistake,
you
know,
for
me,
a
mistake
has
to
prove
that
it's
a
miss
thing.
I
cannot
just
go
with
the
practice
of
Convention.
You
know
my
practice
is
different
and
and
the
popular
practice
is
only
popular
because
it's
accessible
to
more
people,
but
it's
not
the
only
convention
that
you
know
people
well
drawing
to
and
I
think.
The
word
rhythm
here
is
really
important,
because
it
suggests
that
having
two
rhythms
is
the
nature
of
there's
an
old
white
rhythm
in
wrong
rhythm.
B
C
B
You
can
drop
that
in
the
in
the
references.
That
would
be
awesome,
but
the
other
you
know
the
other
thing
you
recommend.
The
other
thing
that
you
mentioned
was
you
know
like
you're,
a
different
approach
to
it
because
of
because
of
ASD
and
I
was
listening
to
a
presentation
recently
that
was
talking
about
how
it's
basically
talking
about.
B
You
know:
people
who
are
not
neurotypical
and
how
general
improvements
to
the
documentation
help
helped
some
of
them
more
and
there
are
ways
to
improve
documentation
for
people
who
who
are
not
neurotypical
that
also
improve
it
for
everyone
else.
Yeah
and
I
feel
like
we
didn't
we.
We
don't
really
touch
on
that
anywhere
in
this
document,
and
it's
probably
a
good
thing
to
to
address
and
I
wonder
if
there
are
some
I
wonder
if
there
are
some
resources
that
we
can
reference
on
that
as
well.
Yeah.
F
F
F
F
G
So
maybe
the
question
that
I
have
in
the
last
two
minutes
is
what
you've
been
talking
about.
Salah
seems
a
little
bit
different
than
what's
in
the
current
documentation
document,
so
the
question
would
be
is:
is
there
room
for
both
of
these
kind
of
ways
of
thinking
about
documentation,
or
should
we
separate
it
out.
F
That
make
sense
it's
a
journey,
I
think
I
think
you're
going
to
enrich
the
the
because
I
mean
the
pivot
forces
us
to
reconsider
what
we
call,
accessibility
and
I.
Don't
think
it's
an
enhancement
to
the
existing
motion,
but
rather
it
forces
us
to
wander.
You
know,
making
something
bigger
or
more
clear
in
documentation.
F
G
I
think
my
comment
is
that,
like
in
the
documentation
document
like
an
hour
ago,
was
trying
to
capture
the
conversations
from
Kaos
Khan
in
San
Diego,
and
it
looks
like
kind
of
looking
at
that
document.
It
looks
like
it's
a
based
on
how
to
build
documentation
that
is
enabling
a
broad
set
of
people
to
join
the
project.
That
kind
of
looks
like
that's
the
narrative
that
came
out
of
San
Diego
and
what
you're
proposing
is.
G
It's
slightly
different
than
that
which
it
I.
Don't
that's
not
a
bad
thing,
it's
just
different
than
that.
So
the
question
is,
is:
does
this
documentation
document
contain
both
the
ability
of
documentation
to
kind
of
increase
the
size
and
diversity
of
a
community,
as
well
as
being
available
to
people
with
a
variety
of
different
cognitive
approaches?
F
F
Laughs
yeah,
the
first
part
allows
allows
us
to
edit
what
the
definition
of
disability
means
because
I
think
it's
it's
a
faulty
definition
to
say
a
disabled
person
is
disabled
and
using
documents
you
know
an
enabled
or
disabled
person,
that's
irrelevant,
but
disabled,
because
the
document
is
making
me
feel
disabled
unable
to
access
it.
That's
a
general
rule
of
accessible
documentation.
You
make
someone
feel
disabled,
whether
or
not
they
have
a
special
circumstance
or
a
disability
in
their
life.
That's
that's
secondary
from
the
concept
of
inclusion
that
your
document
is
inclusive
and
it
penalizes
someone.