►
From YouTube: CHAOSS.D&I.March.25.2020
Description
CHAOSS.D&I.March.25.2020
A
So
what
I
propose
is
that
we
dive
back
into
our
documentation,
accessibility.
We
made
a
lot
of
headway
last
week
and
just
for
the
next,
let's
say:
20
minutes
and
I'm
gonna
cut
it
off
at
the
bottom
of
the
hour,
go
through
resolve
to
the
last
section,
the
data
collection
or
the
implementation
section,
because
we
spend
a
lot
of
time
on
the
description.
A
A
B
B
Sorry
can
we
switch
them
around
because
I
know
matt
has
to
run
to
a
class,
and
then
this
way,
if
you
don't
mind
if
we
can
start
the
bi-weekly
updates
on
the
bi-weekly
week,
and
then
this
way
you
know
we
can
have
myself
and
Matt
give
the
update
to
everyone
with
just
so
I
would
have
missed
some
context
or
or
the
other
way
around.
Can
we
start
with
that?
If
you
don't
mind.
A
A
You
have
full
edit
permissions
if
you
are
unsure
whether
your
edit
is
something
that
will
be
very
good.
You
can
always
suggest,
but
especially
smaller
things
like
typos
cleaning
up
sentences,
just
go
ahead
and
edit
right
away.
Otherwise,
if
you
have
something
you
want
to
discuss
with
us,
first
you're
suggesting-
and
you
can
also
comment
on
sections
and
the
focus
of
today
is
on
implementation
section,
because
we
already
went
over
description
objectives
extensively
before
and
sure
we
can
always
improve.
But
sometimes
it's
just
time
to
move
on.
A
A
A
D
D
E
D
Some
of
them
in
that,
like
there's
a
lot
of
tooling
out
there,
that'll
go
through
and
tell
you
how
accessible
you
are
in
a
bunch
of
different
ways.
Normally
in
regards
to
physical
disabilities.
So,
like
they'll
tell
you
if
you're,
if
you're
doing
correctly
for
this,
for
the
majority
of
screen
readers
they'll
tell
you
a
lot
of
that
and
I
can
go
and
I
got
several
old
friends
of
mine
who
are
accessibility,
experts,
including
the
one
who
does
all
of
PayPal
about
the
tooling,
because
she's
got
a
lot
of
stuff.
D
But
some
of
this
is
also
how
do
we
get
our
numbers
right
because
we're
chaos
and
so
I'm
trying
to
figure
out?
You
know
in
regards
to
the
implementation,
where
we're
going
in
regards
that,
because
you
know,
surveys
are
great,
obviously
in
regards
to
getting
those
numbers,
but
I
know
that
there's
other
ways
where
we
want
to
like
measure
it
and
so
I'm
curious
as
to
what
our
intention
is
for
this
space.
Yeah.
E
No
I
think
that's
a
fair
question,
so
I
comments
on
that
one.
If
you
have
the
link
to
that
the
tools
that
they're
using
your
PayPal
mm-hmm,
that
would
be
super
helpful,
I'm
thinking,
just
in
that
first
bullet
point:
they're,
using
a
tool
that
evaluates
listening
to
talk,
screenreader
friendliness
is
that.
D
E
I
mean
that
would
be
really
helpful
if
we
have.
If
we
have
that
information
and
then
I
think
you
all
raise
another
kind
of
different
point,
which
is
you
know,
kind
of:
where
does
the
chaos
projects
stop
so
how
far
out
do
we
go,
and
this
is
a
common
question
we
have
so,
for
example,
we
say
Survey
first
rate
in
that
that
bullet
point,
but
we
don't
necessarily
provide
a
survey
to
deploy.
We
recommend
running
a
survey.
E
F
Quick
things
on
the
toolings:
if
any
of
them
are
open-source,
it
would
be
good
to
know
so
we
can
promote
other
open-source
projects
and,
as
far
as
the
surveys
I
mean
open,
stakus
we've
shared
ours,
Mozilla
has
shared
ours,
I
mean
just
from
the
fact
that
people
publish
their
surveys.
You
can
base
questions
off
of
other
surveys.
You
know
and
I
do
believe.
We
have
gathered
the
different
surveys.
F
E
E
A
A
E
E
D
So
the
link
that
I
posted
here
they
actually
lists
a
bunch
of
the
standards
that
are
out
there
in
regards
to
specific
documentation,
because
there
are
some
standard
guidelines
that
you
know
already
exist
and
there's
also
if
I
remember
correctly,
there
was
legislation
at
one
point
that
501
C
3
s
and
certain
types
of
businesses
had
to
be
certain
levels
accessible
and
this
team's
going
to
know
what
all
of
those
are,
because
that's
what
they
do.
So
they
throw
a
lot
of
events
on
accessibility
and
how
to
make
a
website
accessible
and
etc.
A
A
E
D
D
A
B
B
A
B
A
B
That
came
to
mind
when
you
were
saying
this
is
I
would
like
to
think
of
each
bullet
point
under
the
data
strategies.
As
relating
to
one
or
more
objective
bullet
points,
it
could
be
a
good
way
to
say
how
many
of
our
objectives
are
covered
by
the
bullet
points.
If
we
can
rank
the
data
collection
strategy
bullet
points
with
what
which
objectives
they
kind
of
address,
that
would
be
a
little
bit
more
objective
to
go
about
this
subjectively,
though
I
mean
you
know,
we're
we're
definitely
making
progress
towards
them.
I.
B
C
I
was
kind
of
thinking
if
I,
if
I
wanted
to
see
how
I
can
measure
these
kinds
of
things
and
look
at
this
many
paragraphs
of
data
collection
strategies,
it's
I,
feel
like
I,
would
get
a
little
overwhelmed
with
like.
Where
do
I
start,
so
there
might
be
a
good,
a
good
way
to
give
some
direction
to
whoever's
reading
it.
That
might
be
helpful,
I'm
not
sure
like
like,
if
I'm
trying
to
do
this
or
measure
this
specific
thing,
like
Saul
had
said.
Where
do
you
go
for
that.
E
B
Exists,
you
know
like
we
could
be
splitting
it
up
like
have
a
a
tally
under
documentation,
accessibility
that
is
broken
into
documentation,
readability,
documentation.
You
know
language
inclusivity
and
diversity
documentation.
You
know,
so
we
can
break
down
the
objectives
into
separate
sub
documents
of
sub
metrics.
But
but
that's
that's
a
future
point.
You.
F
G
I
hadn't
really
thought
about
that,
but
now
that
you
both
mention
it
I
I
would
agree.
This
document
I
think,
has
spiraled
a
little
bit
out
of
control
and
can
may
be
used
by
breaking
down
into
multiple,
multiple
metrics
that
are
under
document.
Accessibility
like
solid
just
mentioned,
I
think
that's
a
good
idea.
H
G
G
Think
if
you,
if
we
broke
this
down
into
into
multiple
metrics
like
Salah,
was
just
sort
of
outlined,
you
can
have
one
that's
you
know
you
could
probably
break
this
down
into
what
like
five
or
six
metrics
that
are
focused
on
specific
aspects,
so
you'd
move
the
objectives
and
the
data
collection
strategies
that
map
together,
because
I
think
the
way
this
is
right
now
the
list
of
objectives
is
so
long
and
the
data
collection
strategies
are
so
long
that
it's
hard
I
think
for
people
to
focus
on
a
particular
area.
I
see.
B
B
E
B
This
format,
though,
that
it
will
likely
be
that
there's
like
like
there's
this
pretest,
you
know,
there's
an
overlap
of
some
of
this
boilerplate.
So
if
you're
going
to
break
this
down
into
five
six
documents,
they're
always
going
to
say
start
with
that
when
you
have
that
other
document,
that
is
the
shared
overlap,
come
here
and
do
this.
So
it's
easy
because
it
seems
that
you
can't
really.
B
I
feel
that
would
be
the
case
because
they're
not
completely
separate,
like
you,
can't
just
put
every
single
data
strategy,
put
a
bullet
point
neatly
under
one
of
the
objectives
or
the
other
on
you
know.
The
overlap
is
basically
like
a
it
kind
of
begs
to
say
that
things
where
there's
overlap,
there's
going
to
be
a
parent
metric
or
a
prep
precursor,
or
something
like
that.
I
don't
know.
E
E
To
take
a
so
based
on
the
objectives
that
we
have
here,
whatever
say,
a
dozen
objectives
take
a
pass
at
trying
to
bring
together
or
I'll
just
make
this
up
three
objectives
that
would
constitute
a
metric
another
three
objectives
that
would
would
constitute
a
metric
number,
two
and
so
on
and
so
forth,
and
just
kind
of
bring
these
forward
next
week
as
possible
ways
to
think
about
this
and
then
further
to
that.
Try
to
map
with
those
say
three
objectives
that
now
constitute
new
metric.
G
And
the
other,
the
other
approach
that
you
might
want
to
take
us
an
input
to
this
is
it
might
be.
It
might
be
interesting
to
look
at
how
documentation
accessibility
asks
experts
break
this
problem
up.
I,
wonder
if
there's
like
some
logical
groupings
that
tend
to
be
used
within
that
industry
that
we
could
just
sort
of
dovetail
onto
I'm.
G
C
C
E
E
B
E
E
So
the
sometimes
the
objective
list
is
a
little
bit
more
definitive
and
comprehensive,
and
the
data
collection
strategies
are
just
kind
of
pointing
people
in
the
right
direction
like
if
you
want
this
data.
Think
about
interviews
or
if
you
want
this
data,
think
about
surveys.
People
have
done
these
in
the
past
or
if
you
want
this
data
think
about
whatever
it
might
be.
So
it's
certainly
not
a
perfect
set
of
data
collection
strategies,
but
it's
just
a
way
to
orient
people
in
the
right
direction.
A
Time
but
I
really
appreciate
the
engaging
discussion
on
where
to
take
this
metric
next
and
I.
Think
that's
a
good
good
plan.
I
try
to
document
this
here
in
the
minutes.
If
you
think
we
discussed
something
that
I
didn't
throw
it
down,
please
do
after
the
meeting
minutes
and
with
that
I
am
moving
us
over
to
the
denied
badging
update.
C
C
C
C
And
it's
on
the
issue.
Okay,
so
this
is
the
DNI
updates.
For
today,
bad
designs
is
the
first
one.
So
if
we
look
at
this
issue
but
weekly
Bajorans,
who
updated
that
to
the
latest
information
and
so
Central
Time,
my
guess,
chaos
time
would
be
10
a.m.
to
12
o'clock
noon.
But
you
don't.
You
can
come
and
go
any
time
and
we
just
kind
of
work
out
some
details.
We
have
a
github
projects
board
that
we
that
we
do
a
lot
of
work
from
and
we
just
go
through
documentation.
C
We
go
through,
what's
kind
of
next,
a
lot
about
even
working
on
these
governance
of
the
badging
as
such
as
like
branding
I,
think
that's
right,
word
for
it,
but
branding
and
how
we
how
we
like
how
we
host
it
was
in
the
chaos
project
or
if
we
really
want
to
have
it
all
within
the
caste
project.
Eventually
office
hours
is
another
thing.
We've
talked
about
so
Matt.
C
B
So
we're
we're
getting
to
a
point
where
we're
designing
these
badges
and
there
are
some
ideas
on
how
we
wanted
to
go
with
it,
and
there
are
some
inputs
from
the
Linux
Foundation
on
different
formats
like
the
kubernetes
5
badges.
There
seems
to
be.
You
know
a
few
I
guess,
workflow
related
things
that
we
would
like
to
put
in
place
to
make
sure
that
branding.
Has
you
know,
branding
assets
that
are
used
in
these
designs
have
the
same
level
of
traceability
that
we
that
we
kind
of
get
used
to
an
open
source.
B
So
so
the
idea
that
we
would
want
to
link
to
a
particular
version
of
the
chaos
logo.
We
want
to
the
Kaos
font
and
other
you
know,
requirements
Doc's
that
say:
you're
allowed
to
print
this
logo
as
small
as
this
or
as
big
as
this.
You
know,
certain
details
have
to
kind
of
be
where
you
would
expect
them
to
be,
and
everything
should
kind
of
flow
very
nicely
to
very
clean
and
transparent
repository
ops
like
the
usual
DevOps,
so
so
at
this
point,
we're
just
looking
to
put
together
some
sort
of
a
structure
there.
B
B
E
C
H
B
B
Process
figuring
out
there
are
so
for
outreach
e.
For
instance,
there
is
I,
think
a
proposal
requirement
I'm,
not
sure
I'm,
maybe
mixing
you
know
the
there
are
certain.
You
know
important
things
we
want
to
put
in
place
to
get
this
and
to
say:
okay,
you
know
we're
set
for
the
summer,
and
so
our
priority
has
really
been
to
learn
how
to
be.
You
know
mentors
so
we're
being
mentored
to
be
mentors
and
for
hasta
and
Tola
I
believe
you
know,
there's
definitely
a
lot
of
excitement.
B
B
B
She
has,
you
know,
created
a
dog
that
tried
to
detail
in
an
amide
map
that
try
to
details
the
longer-term
vision
of
this
workflow,
based
on
the
POC
work
that
we
kind
of
did
very
early
on
and
I
think
we
showed
a
little
bit
of
that
in
Prior
EMI
meetings
yep
but
hasta
you
know
could
chair.
Could
you
share
your
screen
and
show
them
wine
map?
That
would
be
really
cool,
and
you
know
please,
please
feel
free
to
I.
H
B
Yeah
yeah,
so
so
so
you
know
we're
really
trying
to
wrap
our
heads
around
this.
As
you
can
see,
we
you
have
to
know,
though,
that
our
process
we
will
not
on
the
github
structure
yeah
as
much
as
possible-
and
we
addressed
this
yesterday.
So
our
goal
is
to
keep
the
get
lab
chores,
as
you
know,
moving
from
github
to
get
lab
as
a
second
phase,
our
MVP,
hopefully
you
by
the
end
of
the
summer,
will
be
github
centric.
This.
C
C
E
H
They
go
through
it
and
they
tell
the
applicant
that
hey
you
can
make
changes
to
this.
Maybe
you
can
make
changes
to
your
code
of
conduct
or
maybe
you
can
get
like
modify
things
in
a
way
that
refines
the
diversity
and
inclusion
practices
for
your
event
or
your
project,
and
then,
when
that
feedback
is
taken
in
and
it
has
been
applied.
So
when
that
total
feedback
and
application
process
ends,
a
badge
is
assigned
to
them,
depending
on
how
many
deliverables-
or
in
other
words
DNI
metrics,
the
application
stands
up
to.
H
C
C
I
sure
don't
know
girl
ink
of
the
first
edition
first
like
draft
of
the
badge
levels,
and
we
got
some
feedback
on
that
yesterday.
I
just
wanted
to
share
it
again
on
the
different
kinds
of
badges
we
could
have
in
the
different
kinds
of
requirements
that
we
people
would
meet.
We're
also
thinking
of
some
kind
of
ternary
system
of
requirements
where
you
could
be
working
on
it
not
meeting
already,
and
we
don't
know
how
to
factor
that
in
yet,
though
we
haven't
really
talked
about
it.
That
much.
D
E
A
D
Yes,
thanks,
sorry
about
that,
this
needs
to
be
parishes
in
my
neighborhood,
so
it's
the
whole
working
for
home
thing.
So
I
don't
know
the
current
status
of
it.
I
know
that
it
was
up.
It
was
down
and
it's
back
up
again
in
regards
to
Mozilla
working
on
the
open,
badging
program
and
so
I
don't
know
its
current
status.
D
I
have
to
go
check
in
with
my
friends,
but
I
was
there
at
the
beginning
when
they
were
first
starting
it,
and
so
that's
one
reason
why
I
would
like
kind
of
look
to
them,
because
they've
kind
of
had
this
going.
Can
you
know
off
and
on
since
2010
I
want
to
say
so
and
then
I
just
sent
a
message
to
try
to
find
out
what
we're
doing
standards
wise
in
regards
to
this.
So
there
is
some
stuff
going
on,
for
it.
D
D
E
D
Yeah
and
I
think
that's
one
reason
why
it
was
transitioned
over
to
there,
but
I,
don't
know
where
it's
bad
at
at
this
point,
so
I
can
do
a
little
digging
in
regards
to
it.
But
I
know
that
you
know
there's
so
many
different
people
who
want
to
do
badging
at
this
point
that
it
seems
like
it
would
be
useful
to
have
something
to
find
to
go
rally
under.
Do
you
know
what
I
mean
it's
like
too
many
different
things
being
juggled
in
regards
to
badges
yep.
C
D
Yeah
and
it
needs
to
be
more
than
that-
I
mean
you
have
to
take
there's
so
many
other
things
that
you'd
need
to
be
figuring
out
for
it.
You're
like
for
a
while
LinkedIn
was
open
for
badges,
but
I
think
they
turned
some
of
that
off
and
so
yeah.
So
we
have
to
like,
because
those
are
attached
to
individuals-
and
these
might
be
attached
to
the
documents
themselves,
I.