►
From YouTube: CHAOSS DEI Working Group 5-12-21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
All
right,
hi,
everybody
welcome
to
the
may
12th,
I
think
for
everybody
on
the
call.
May
12th
version
of
the
dei
ksdei
working
group
meeting
kind
of
a
light
agenda
today.
This
seems
to
happen.
Sometimes
I
think
in
in
may
I
don't
know
we
all
have
emerged,
at
least
in
the
northern
hemisphere.
We've
emerged
through
winter.
A
You
know
kind
of
finding
other
things
that
are
out
yeah,
which
is
cool,
so
I
think
a
few
things
today
we
have
a
couple
of
metrics
that
it
looks
like
we're
going
to
be
returning
to
one
is
documentation
discoverability,
and
this
was
in
the
minutes
before
I
took
a
look
at
the
minutes.
So
oh
it.
B
Basically,
I
took
the
shell
that
we
had.
We
had
some
work
done
in
this
already.
I
was
not
the
original
author,
however,
so
I
tried
to
keep
as
much
of
the
original
as
possible
and
have
it
still
make
sense.
So
if
any
of
you
are
on
the
call
that
were
part
of
that
original
discussion
and
can
provide
additional
context,
that
would
be
super
helpful.
I
hope
I
didn't
delete
anything
that
it
was
important
to
you.
B
If
I
did
then
feel
free
to
you
know,
return
the
version
or
reverse
go
back
whatever
whatever
that
word
is
that
I
want
revert.
Thank
you
yes,
thank
you.
I
need
more
coffee,
yes,
so
yeah,
I
don't
know
if
we
want
to
take
a
few
minutes
and
look
through
it
or
work
on
it
or
whatever
you
all
want
to
do
it.
That
is
completely
fine
with
me.
A
Yeah
so
at
least
I
I
think
this
was
part
of
the.
A
Split
of
the
documentation
metric
from
ages
ago,
and
then
it
became
a
couple
other
metrics
just
in
terms
of
what
the
concerns
around
documentation
can
be,
and
so
this
is
one
of
them,
and
maybe
I
have
a
question
for
you.
Elizabeth
just
was
there
anything
in
here
that
seemed
complex
or
problematic
that
when
you
were
doing
the
revisions.
B
B
So
some
of
I
think
that
was
in
here
were
remnants
from
when
we
split
them
out,
so
I
just
wanted
to
kind
of
get
other
people's
opinions
on
whether
or
not
things
should
stay
or
go
and
go
somewhere
else
or
even
in
another
metric
or
you
know,
whatever
we
want
to
do
with
it,
with
particular
attention
to
the
geographic
access
and
the
mobile
access.
I
feel
like
those
could
have
gone
into
documentation,
accessibility,
but
maybe
there's
something
else
as
well.
Okay,.
B
The
other
thing
I
was
I
was
wondering
about
was
back
when
you
up
at
the
top,
it
says
editability,
I
didn't
know.
If
we
wanted
to
make
accuracy
a
piece
of
this,
it
doesn't
seem
like
it
really
fits
here,
but
it
kind
of.
Does
I
don't?
B
I
don't
know
whatever
you
all
think,
but
I
feel
like
accuracy
is
a
is
a
piece
of
this
that
has
not
been
represented
before,
unless
we
want
to
put
it
in
usability,
I'm
not
sure,
I'm
not
sure
what
you
all
think,
but
I
think
that
it
is
an
important
piece,
because
inaccurate
documentation
is
extremely
frustrating
and
should
be.
You
know,
paid
attention
to
that.
The
documentation
is
is
kept
up
to
date.
B
C
B
Yeah
so
yeah
yeah
editability,
I
think
maybe
its
own
metric.
A
A
So
I
could
maybe
see
ability
in
there
as
well
portability.
B
B
Confusing
to
me,
because
are
we
moving
then
like
we're
not
really
moving
the
documentation,
so
I
wasn't
sure
what
that
meant
or
who
the
original
author
was
to
put
that
in
there
thought.
Maybe
if
they
were
here,
they
could
provide
some
additional
context.
D
E
All
right,
yeah
we'll
make
it
into
what
we
think
it
is.
A
And
then
geographic
access,
I'm
trying
to
think
through
that
a
little
bit
too
be
accessed
by
users
who
may
be
subject
to
very
various
internet
restrictions.
That
makes
a
little
sense
to
me.
B
A
I
think
what
you
were
just
talking
about
would
fit
for
me.
So
if
there
are,
this
is
limitation
based
on.
G
C
B
B
E
B
It
you
know
it
might
even
fit
in
something
with
you
know,
like
code
quality
or
something
like
that-
maybe
not
necessarily
here
in
dei,
but
I
don't
know.
B
B
Well,
we
do
have
documentation
usability
which
includes
like
readability,
and
things
like
that.
So
I
mean.
Maybe
it
fits
under
that
as
just
another
thing
to
check,
because
if
it's
inaccurate,
then
it's
not
really
usable,
but
I
don't
know.
A
A
A
So
we're
just
kind
of
doing
this
as
a
team
right
now.
So
then
does
that
fit
with
the
description
too.
I.
H
B
A
lot
of
these
were
here
already.
It
feels
like
someone
put
a
whole
lot
of
work
into
them,
so
I
didn't
want
to
just
you
know,
delete
them
and
I
feel
like
they're,
pretty
good,
except
for
there's
a
few.
Actually
readability
and
scannability
can
probably
take
out
because
that's
probably
taken
somewhere
else.
B
I
just
wasn't
sure
if
there
was
any
other
way
to
really
capture
this
data
aside
from
a
survey,
unless
there's
you
know,
like
google
stats
or
something
on
how
many
times
people
hit
you
hit
the
pages
and
like
what
their
search
terms
are,
and
things
like
that,
like
I
didn't
know
how
deep
we
wanted
to
get
with
this.
So.
B
A
B
E
We've
I've
certainly
looked
at
what
search
terms.
Take
people
to
my
site
from
my
google
analytics.
E
B
Maybe
we
could
add
it
as
a
just
an
idea,
and
if
somebody
wants
to
kind
of
go
down
that
rabbit
hole
they
can
like.
I
don't
know
how
far
we
want
to
hold
their
hand
down
that
road
down
that
road,
because
I
feel,
like
that's
a
whole
science
in
and
of
itself-
and
I
don't
know
I
don't
know
you
know.
A
D
A
A
A
B
Again
this
was
you
know,
not
my
original
stuff.
I
tweaked
it
a
little.
I
don't
know
how
you
all
feel
about
the
complexity
of
the
way
this
is
presented.
G
A
B
Also
felt
like
they
were
kind
of
mixing
like
I
wasn't
sure
when
they
said
mailing
list
communication,
if
if
they
meant
like
the
mailing
list
itself,
was
easy
to
find
and
or
an
answer
within,
the
mailing
list
was
easy
to
find.
So
it
was
a
little
bit
confusing
to
me
what
okay,
yes,
because
it
was
very
general
like
just
describe
your
experience
so,
like
I
don't
know
like
performing
code,
reviews
are
easy
to
find
like
I,
I
wasn't
quite
sure
what
that
meant.
B
I
It's
apache
term
for
okay,
the
basically
maintainers
steering
committee
kind
of
thing,
yeah,
it's
kind
of
below
a
steering
committee.
So
it's
more!
It's
more
like
a
committee
of
maintainers.
B
A
A
B
C
But
one
thing
I
felt
missing
in
this
in
this
list
is
like
the
website.
People
always
first
think
they
always
go.
Is
the
website.
C
So
what's
missing
here?
Yes,
so
I
in
the
example
list
we
have
this
like
mailing
list
or
communication
archive
the
first
thing.
Always
anyone
go
for
looking
for
a
documentation
or
anything
is
the
website
of
the
project
or
a
community,
or
so
the
website
like
itself
is
not
in
the
list
is
what
I'm
trying
to
say.
A
It
I'm
gonna
make
a
mistake:
how
easy
is
it
for
an
individual
I'll,
just
point
out
code
of
conduct
and
they
may
go
to
the
website
to
find
it,
and
it's
probably
pretty
straightforward
to
find
on
the
website
if
we
didn't
have
it
on
the
website,
and
it
was
only
available
say
through
the
governance
repo
in
the
chaos
project.
B
A
F
Trying
to
understand
is
this
about
the
chaos
project.
Specifically.
Are
we
just
talking
generally
with
this
metric
generally?
Okay,
I
actually
think
website.
I
think
the
point
finance
making
is
actually
really
key,
because
I've
seen
so
many
open
source
projects
that
have
documentation
and
have
these
things
done
and
then
they
don't
have
any
way
to
find
it
on
their
main
website
and
a
lot
of
times
as
a
project.
You
really
need
to
put
that
stuff
out
there.
F
People
aren't
just
going
to
come
across
it
right
and
websites
are
a
huge
oftentimes,
that's
the
front
door
for
many
many
projects
or
organizations.
So
I
really
think
that
one
makes
a
lot
of
sense
from
my
perspective,
because
I
see
it
not
done
all
the
time
and
there's
definitely
a
web
development
piece
that
you
need
to
account
for
that.
I
see
over
so
okay.
B
A
Would
you
want
to
put
website
in
this
list
because
to
me
this
list
is
like
it's
not
about.
If
I
put
to
me
if
I
put
website
in
this
or
if
we
put
website
in
this
list,
the
question
is:
how
easy
is
it
to
find
the.
A
I
understand
the
point
that,
like
not
having
this
on,
the
website
makes
it
difficult
to
find
this
documentation,
and
so,
if,
if
these
things
aren't
on
the
website,
you
know
like
accessible
through
the
website
or
discoverable
through
the
website,
then
the
answer
is
always
going
to
be
quite
difficult
to
find.
Like.
F
Different
way
to
this
that
website,
because
I'm
seeing
that
those
all
these
items
are
like
specific
individual
places
and
a
website
can
be
more
of
a
catch-all,
maybe
there's
a
different
question
here
of
where
do
you
go
to
discover
a
project's
processes?
Is
it
a
website?
Is
it
documentation
site?
Maybe
that's
a
better
approach.
Gotcha.
A
F
A
A
F
This
is
one
it
can
all
depend
on
the
software
because,
like
if
you're
in
a
linux
community,
then
it
could
be
a
downstream
packaging
user,
but
if
you're
a
javascript
person,
maybe
it's
like
the
package
registry.
What
are
those
called
like
npm
and
pi
pi
for
python
and
yeah
is
packing
registries
package
package.
I
F
Sometimes
yeah
like
for
one
tool
that
might
be
true,
but
if
I'm
building
like
a
like
well
I
don't
know
I
I'm
just
thinking
out
loud.
I
guess
it
can
be
a
very
contextual
question.
I
guess
it
just
depends
on
the
project.
I
don't
know.
If
there's
a
lot
of
things,
we
could
abstract
out
like
universal
for
open
source,
but.
I
I
Well,
that's
a
good
point.
That's
a
good
way
to
phrase
that
I
actually
still
have
a
question
about
the
previous
previous
section,
the
matrix.
I
actually
don't
think
this
is
a
matrix
item,
because
I
think
it's
there
are
a
bunch
of
questions.
I
think
these
are
just
questions
that
would
be
on
a
library.
G
I
A
G
B
B
A
A
A
Okay,
not
what
is
this
open-ended
follow-up
question
if
the
answer
is
not
no
challenges.
A
C
Yeah,
because,
like
the
survey
project
members,
it
is
saying
that's
where
I
was
is
it
like,
though,
the
contributing
members
already
are
aware
of
where
the
documentation
is
or
where
the
work
is
thing,
but
it's
more
of
a.
If
I'm
a
newcomer
and
I
want
to
see
the
documentation,
am
I
able
to
locate
it?
That
survey
should
be
focused
to
that
audience.
I
guess.
B
The
the
question
actually
addresses
both
of
those
things:
those
people,
those
things
users
and
contributors,
so
I
think
it
can
encompass
both
unless
we
think
it
shouldn't.
E
A
B
A
A
Yep,
okay,
should
we
possibly.
G
B
Yes,
yes,
scanability
and
readability.
Yes,
is
usability.
B
B
A
B
C
B
B
B
I
also
think
like
it's,
it's
challenging
to
make
videos
searchable,
and
I
know
that
there
are
companies
that
do
that,
and
you
know
you
can
provide
transcripts
and
everything.
But
I
don't
know
I
don't
know
if
we
want
to
put
this
in
here
or
not.
B
D
B
A
C
B
C
C
Cool
one
point:
I'm
not
sure
whether
it
fits
here
or
somewhere
else
like
is
documentation
available
in
different
languages,
because
that
also
helps
people
to
look
for
the
documentation
in
their
own
local
language
or
some
other
language.
You
have
a
pointer
for
that,
but
not
at
all
or.
B
A
All
right
so,
let's
see
oh,
nobody
was
supposed
to
change
anything.
A
A
That's
awesome,
so
maybe
for
the
next
next
week
we
can
just
finalize
this
like
clean
it
up
in
the
spreadsheet
and
kind
of
start
doing
the
whole
ready
for
release
kind
of
thing.
If
that
works
for
folks
and
then
yeah
this.
A
A
A
This
is
so
we
have.
We
have
plenty
of
time.
The
next
release
cycle
isn't
for
a
long
time.
It's
like
two
months,
it's
forever
forever
away.
So
I
think
it's
all
good
and
again
this
will
just
remove
speaker.
Demographic
especially
lose
two
metrics
in
the
next
release,
but
kind
of
combining
them
into
just
a
single
metric
and
then
community
survey.
Coming
soon
did
somebody
want
to
talk
about
that
ever
put
that
in
there.
A
B
I
don't
think
I
think
justin
had
to
drop,
but
I
think
justin
probably
put
this
in
there
just
to
give
people
oh
yeah.
He
did
put
it
in
chat
that
he
had
to
go
but
yeah.
So
that's
just
a
really
kind
of
a
heads
up
that
we
are
going
to
be
doing
a
survey
or
the
the
independent
team
is
going
to
be
doing
a
survey
whenever
it's
ready
to
go
so
just
kind
of
keep
an
eye
out.
For
that.
That's
pretty
much.
It.
B
And
also
maybe
some
other
areas,
but
that's
part
of
the
thing
that
is
being
sorted
out
right
now.
I
think.