►
From YouTube: CHAOSS D&I Working Group 12-2-20
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
So
this
is
the
diversity
and
inclusion
working
group.
I
do
appreciate
anyone
with
the
willingness
to
volunteer
to
keep
track
of
the
minutes.
Nobody
else
volunteered
to
coordinate
this
meeting
after
the
last
one.
So
I
am
keen
to
see
if
there's
anyone
that
is
willing
to
coordinate
the
meeting
after
this
one
I
can
do
that
is
that
matt
snell
yeah
all
right.
A
A
C
Oh
no,
what
kind
of
superhero
has
the
most
home
runs.
C
Yeah,
it's
batman.
A
That's
good.
That
was
good
thanks,
matt
all
right
yeah.
I
appreciate
that.
That's
that's
great!
So
we
do
have
a
one
action
item
that's
been
added
and
then
we
should
probably
review
the
metrics
that
we
have
set
set
for
release.
A
But,
let's
start
with,
I
don't
know
the
topic
for
the
reply
to
angel
angela
brown
from
lf
events
to
our
recommendation
on
the
disability
question
on
the
registration
forms.
Is
this
a
quote
of
the
I
don't
know
who
puts
this
there?
Is
this
a
quote
of
what
her
response
was.
A
Thank
you
to
thank
you
to
you
and
the
cast
diversity,
inclusion,
working
group
members
for
your
efforts
here,
which
are
much
appreciated.
We
will
put
all
your
recommendations
in
place
and
the
latter
two
will
be
reflected
on
all
future.
Registration
forms,
that's
fantastic
if
somebody
could
copy
what
those
two
questions
that
will
be
included
and
all
the
registration
forms
are
when
you
have
a
chance,
I
think
that
will
be
helpful.
I
I
don't
know.
A
Really
fantastic
news
that
that
we-
actually-
I
bet
you
know
the
alex-
is
doing
that
work
and
that's
that's
fantastic
for
the
existing
pull
requests.
A
Is
it?
Let
me
ask
before
I
start:
are
there
topics
other
than
sort
of
the
business
of
reviewing
pull
requests
and
other
types
of
things
that
we
want
to
address
during
this
meeting
today
it's
been
a
it's
been
a
couple
weeks
since
we
met,
and
if
there,
if
there
are
specific
topics
on
folks
minds,
I
want
to
make
sure
those
are
reflected
in
the
agenda
before
we
get
rolling.
F
I
think
if
I
remember
right,
we
can
look
at
the
public
chat
channels
metric
again,
yeah.
A
A
Listening
speaking,
so
there
are
some
other
metrics
that
we've
listed
as
in
progress
and
of
those
are
there
any
that
we
intend
to
pursue
the
release
of
during
the
next
metrics
release
cycle,
which
I
believe
our
metrics
go
under
review
at
the
end
of
january.
D
They
go
under
review
once
we
flag
them
ready
unless
there
is
a
public
review
one
month,
metric
freeze
where
we
don't
add
new
metrics
to
the
review,
and
we
focus
on
reviewing
what
we
have.
A
Yeah
so
like,
for
example,
demographic
deserve
diversity.
Listening
and
speaking,
we
do
list
that
in
progress,
but
we
haven't
started
work
on
those
yet
and
also
code
of
conduct
these
these
three
here
under
governance,
we
do
list
as
in
progress
and
we
haven't
started
the
template
on
those
for
discoverability
and
communication
channels.
The
templates
have
been
started,
and
I
think
I
think
those
are
on
the
list
of
ones
to
discuss
today.
A
A
A
We're
working
on
these
metrics
and
we
have
these
metrics
under
review,
so
both
of
these,
I,
I
think,
required
a
good
deal
of
discussion
last
time
that
we
didn't
conclude.
So
I
might
suggest
that
we
begin
a
discussion
about
public
chat
channels
and
maybe
review
that
metric
and
then
maybe
give
that
give
that
15
minutes
give
or
take
and
then
look
again
at
document
discoverability.
A
D
A
A
So
there
are
accepted
so
we've
got
the
changes
from
the
last
time
accepted
in
a
lot
of
comments.
My
first
question
here
is:
do
we
want
to
take
a
minute
to
read
this
metric
and
then
before
we
edit
it
or
do
we
do?
What
do
we
want
to
just
initiate
collective
editing.
F
Yeah,
so
for
as
far
as
changes
since
the
last
time
we
talked
about
it,
I
was
I
integrated
most
of
the
feedback
that
we
had
from
the
last
live
editing.
Mostly
things
got
moved
around
or
changing
a
few
nitpicks
did
find
out
that
there
actually
is
getter
support
in
percival.
It's
just
not
documented,
but
there
is
actually
a
plug-in
already
written
for
it
that
integrates
with
it.
So
that's
that's
a
plus,
but
all
of
hogger's
features.
H
F
F
Is
almost
finished,
maybe
just
looking
at
any
final
final,
nitpicks
or
or
suggestions.
I
know
the
biggest
feedback
that
I've
had
so
far
is
just
maybe
being
more
clear
that
we
mean,
like
the
chat
platform
itself
versus
communication
and
moderation
strategies,
but
sometimes
that
also
influences
the
tool
like.
I
guess
that
might
be
the
detail
to
kind
of
keep
in
mind
while
going
through
this.
F
A
F
F
Me,
I
think,
maybe
just
like
a
10
or
15
minute
pass
just
to
do
a
maybe
one
last
review
and
then
see
where
we
want
to
take
this
next,
because
I'm
not
sure
what
else.
Maybe
we
can
you
know
polish
it
up
a
little
bit,
but
I
think
it's
almost.
I
think
it's
almost
done.
A
Yeah,
I
think,
let's
take
let's
take
that
10
minutes
and
collectively
review
it.
One
one
question
that
we
should
ask
ourselves:
maybe
after
we've
edited
and
reviewed
it
is
as
a
general
pattern.
We
haven't
valenced
the
metric
itself
and
in
general
I
don't
think
we
are.
We
are
classifying
tools
that
we
want
to
draw
trace
data
from
as
being
open
or
not.
A
A
However,
we
may
want
to
discuss
that
after
we
spend
the
time
time
editing,
because
I'm
sure
that
will
come
up
in
the
review
period
and
as
I
learned
in
my
last
meeting,
we
actually
typically
don't
record
during
the
editing
session.
So,
if
we're
ready
to
start
like
reviewing
and
editing,
I
will
pause
the
recording
and,
if
that
works,
for
people.
A
All
right,
okay,
so
we've
spent
10
minutes
or
so
reviewing
and
editing
this
document
and
making
some
changes
justin.
I
think
you
had
a
comment.
F
I
mean,
I
guess
for
me,
I'd
just
be
wondering
if
anyone
has
specific
feedback,
I
guess
maybe
the
thing
that
we
could
talk
about
would
just
be
the
the
name,
because
that's
just
kind
of
like
the
probably
the
most
the
most
pressing
thing,
maybe
just
to
make
sure
that
we're
clear
on
the
name,
but
there's
a
couple
of
comments,
this
one
anyone
wanted
to
highlight
or
call
out
any
of
their
their
edits
for
the
most
part.
F
I
think
I've
accepted
most
of
them,
but
not
sure
if
anyone
wants
to
like
bring
any
up
for
discussion
or
or
raise
any
group
questions
before,
maybe
looking
at
another
one.
A
A
Okay,
yeah,
so
don
had
asked
a
question
about
something
about
diversity
and
inclusion
in
the
title,
and
you
and
don
had
a
conversation
about
it
over
the
last
few
weeks,
and
I
had
a
few
suggestions,
I
I
do
think
dawn's
point
is
important
be
in
and
because
there
are
other
things
like
just
gross
activity,
participants,
messages
that
are
of
interest
in
other
working
groups,
but
I
I
do
think
our
interest
in
this
is
making
some
measurements
of
inclusivity
or
transparency.
A
And
then
those
are
the
two
words
I
suggested
only
because
well,
there's
even
like
obvious
words
to
consider
I'm
unsure
about
the
removal
of
public,
because
I
think
I
guess
it
so.
On
the
one
hand,
public,
I
think,
is
good,
although
we're
not
trying
to
make
value
judgments,
but
it's
hard
for
us
to
measure
or
know
about
private
chat
channels.
A
D
My
thinking
here
is
that
we
used
public
only
in
three
instances
throughout
the
entire
document.
One
of
them
was
the
title,
and
so
it
didn't
seem
to
be
reflected
in
the
rest
of
the
document
and
then
to
your
point.
Sean
opens.
Those
projects
might
not
make
all
of
their
synchronous
communication
public
where
anyone
can
join.
They
might
have
some
that
are
only
for
project
members
or
community
members,
and
they
might
still
have
access
to
the
data
and
api
and
can
apply
these
principles
or
metrics
as
well.
Right.
A
So
as
a
project
owner
I'm
interested
in
the
metrics,
even
though
my
channel
is
not
public,
in
fact,
I
mean
augur,
has
private
chat
channels
that
we
use
for
like
low-level
coordination,
that
we
would
be
interested
in
in
this
metric,
for
so
that
makes
that
makes
sense.
That
makes
a
good
deal
of
sense
to
me
that
me
too,.
F
I,
like
the
idea
of
chat,
channel
inclusivity.
I
think
that's
when
I
can.
We
can
sit
with
that
one
for
a
week
and
then
see
if
we
we
feel
differently
next
week.
A
I
mean
the
other
thing
we
can
do.
Is
I
think
that
this
this
work
has
become
mature
and
one
question
I
would
throw
the
group
is:
is
the
metric
mature
enough
to
put
under
review
or
up?
Is
there
more
work?
I
think
the
one
other
thing
that
we
need
to
discuss
is
under
the
the
listing
of
the
platforms
and
what
to
do
about
that
before
we
release
it.
A
F
Yeah,
I
guess
I
guess
the
the
summary
that
I
was
thinking
of
for
the
the
platforms
is,
I
would
agree,
I
don't
think
we
have
to
list
the
poop
emoji
platforms
here.
F
I
think
what
we
could
do
instead
is
just
list
platforms
that
are
currently
supported
in
grimoire
or
maybe
just
link
out
to
percival
c
percival
for
supported
platforms.
So
that
way
we
don't
have
to
keep
up
that
list
if
personal
ads
or
drop
support
for
others.
So
maybe
we
could
just
link
out
to
that
just
be
like
see,
percival
for
information
on
supported
platforms
with
grimore
I'd
be
okay
with
that
and
non-listing
specific
platforms.
I.
A
Would
say
in
addition
to
that,
I'm
interested
in
knowing
whether
or
not
the
platform
is
open
source,
because
if
I'm
looking
at
like
as
a
project
maintainer,
I
kind
of
want
to
know
if
I've
like
I'm
using
slack.
I
know
it's
not
open.
I
don't.
I
did
not
have
awareness
of
several
of
these
open
source
chat
channels
that
are
available,
and
this
is
the
so
this
is
a
place.
I
could
get
that
information
and
I
don't
know
where
else
I
would
look
for
it.
A
So
I
think
I
think
it's
helpful
to
indicate
whether
it's
open
source
or
not,
and
I
don't
think
it's
a
value
judgment.
I
think
it's
a
fact.
So
I
guess
I
would
advocate
for
in
some
indication
of
whether
or
not
the
platform
is,
is
open
source
in
addition
to
its
availability
on,
and
I
I
don't
have
any
issue
listing
its
availability
in
percival
right
now.
Percival
is
in
fact
the
only
tool
that
incorporates
these
chats
into
their
their
metrics,
but
at
some
point
in
the
future,
I'm
sure
auger
will
get
there.
D
So
I
understand
the
value
of
knowing
whether
tool
is
open
source
or
not.
My
concern
with
including
the
list
in
the
metric
is
that
this
list
becomes
outdated.
Slack
was
just
bought
by
salesforce,
we
don't
know,
what's
going
to
happen
there,
and
I
would
like
to
keep
this
technology
detail
out
of
the
metric.
D
When
you
redesigned
the
metric
template
about
a
year
ago,
we
removed
a
lot
of
the
low-level
technical
details
to
keep
the
metrics
more
inspirational
and
focused
on
what
you
could
do
with
a
metric
like
this,
without
going
in
the
detail
on
how
you
would
actually
implement
it.
So
that's
why
I
think
it's
too
much
information
in
a
chaos
metric.
D
A
Okay,
perfect:
I'm
gonna
leave
the
crossouts
in
there
now
so
that
you
don't
lose
the
list
and
when
I
guess
we
could
just
I
copied
it
out
all
right.
We
can
accept
that
then.
G
I
do
also
see
some
benefit
to
linking
that
blog
to
the
metric,
if
that's
possible,
just
so
that
people
can
can
have
that
awareness
of
the
of
that
list.
I
know
it
will
change
and
that
can
happen
in
git,
but
knowing
what's
open
and
not
is
really
beneficial
as
well.
I
understand
why
you
don't
want
it
in
the
metric,
though.
A
I
I
I
like
that
idea
as
well,
so
maybe
we
had
see
chaos
blog
post
on
open
source
platform
status
here
and
we
can.
We
can
leave
that
blank
to
be
written.
Then
I
like
that
idea.
I
think,
because
when
I
come
to
this
metric,
that
really
is
one
of
the.
This
is
that'll,
be
a
very
important
question
for
me.
As
a
newcomer,
I
don't
know
that
I
put
a.
I
didn't
put
a
great
deal
of
thought
into
choosing
slack.
A
Metric,
oh,
I
let
me
undo
that
I
can.
I
guess,
control
justin
put
a
great
justin
suggested
linking
the
blog
post
at
the
bottom
under
resources
yeah,
and
I
think
that's
a
good
idea
as
well.
F
So
maybe
the
one
thing
that
would
be
helpful
for
me
just
to
think
about
is
they're
getting
a
temperature
check.
If
folks
think
we
could
try
to.
Is
this
something
we'd
want
to
try
to
close
out
by
the
end
of
the
year
to
put
into
a
proposal
metric?
Do
we
want
to
take
a
couple
more?
Do
we
want
to
wait
until
after
the
holidays
period
for
december?
Before
pitching
it?
A
My
view
is
it's:
if
we
accept
the
changes
and
that
we've
made
and
the
discussion
that
we've
had,
I
don't,
I
think,
broader
review
by
the
community.
I
think
it's
time
for
that.
I
don't
think
there's
anything
in
here,
that's
like
unfinished
or
ill-considered,
and
I
this
is
my
opinion
but
I'll.
Let
others
state.
A
B
A
Amy
you
broke
up
there.
Can
you
say
that
again.
B
Oh
yeah,
sorry,
I
finally
went
mobile.
I
think
we
have
a
lot
of
comments
in
the
doc
that
we
need
to
resolve.
I
mean
I
think
they
were
mainly
wording
type
things,
but
if
we
don't
get
that
resolved
by
next
week
and
then
finalize
things
in
the
for
the
following
week,
we're
going
to
lose
people
to
the
holidays.
B
So
resolve
everything
and
go
through
it
for
next
week's
meeting
and
then,
if
there's
any
other
comments
next
week,
that
gives
us
another
safe
week.
But
if
we
get
everything
and
everyone's
happy
next
week,
I
think
we're
good.
A
Me:
okay:
let's
leave
that
note
document
discoverability
is
the
other
one
and
we
have
seven
minutes
left.
Do
we
want
to
do
some
work
on
document
discoverability?
While
we
have
time
or
do
we
want
to?
F
Maybe
we
can
talk
about
this
know
if
there
was
anything
else
with
burnout
or
if
this
is
the
only
thing
left.
If
this
is
the
only
thing
left,
I'm
happy
to
just
edit
this
for
a
little
bit,
but
I
just
want
to
make
sure
we
don't.
I
don't
know
if
there's
anything
else
to
add
on
the
other
metrics.
A
Well,
this
was,
I
think
this
is
this
metric
we
discussed
last
time,
and
I
think
you
did
a
good
job
of
explaining
how
this
metric
emerged
as
sort
of
the
diversion
of
two
metrics
or
even
three,
and
it's
the
third
of
it's,
the
third
of
the
three
metrics.
Am
I
recalling
that
correctly
york.
A
So
there
was,
I
think,
there's
a
lot
of
editing
work
to
do.
If
I'm
remembering,
I
don't
know
how
much
we
finished
last
week
to
make
this
uniquely
discovery
and
remove
the
parts
that
are
are
part
of
the
other
metric,
the
other
two
metrics,
and
that's
my
recollection
of
where
this
is
at
so
georg.
What
are
your
we?
We
did
do
some
crossing
out.
D
Working
on
the
blog
post
to
preserve
our
work
on
the
list
of
chat
platforms,
I
just
yeah
in
the
chat.
If
you
can
look
at
it,
if
you
don't
mind
going
on
that
roll
hole,
because
in
five
minutes
I
don't
think
we
have
time
to
dive
into
this
new
metric.
A
Yeah,
I
think,
let's,
let's
save
this
for
next
time,
just
I'll
make
a
okay.
H
Yeah
and
sean,
were
you
saying
that
the
idea
was
that
we
move
what's
here
into
other
other
metrics
just
so
I'm
underst
am
I
understanding.
D
Yeah
one
of
them
we
released
last
time
there
was
the
documentation
accessibility
and
we
also
worked
on
the
documentation
usability.
I
think
which
we
have
under
review
right
now
and
discoverability
is
the
third.
So
the
problem
we
ran
into
when
we
had
just
documentation
was
that
we
had
many
different
things
going
on
and
it
became
this
gigantic
document,
and
you
still
see
this
in
this
version
of
the
document,
because
there
are
things
that
are
not
directly
related
to
discoverability,
but
more
about
accessibility
and
usability,
which
we
would
have
to
look
at
the
metrics.
A
Okay,
so
there
yeah
there's
there's
that's
that's
the
work
I
think
and-
and
I
think,
let's
set
aside
some
time
to
do
that,
work
in
the
next
meeting.
Okay,
did
that
answer
your
question
nicole,.
A
I
figured
gear
is
really
good
at
answering
those
kinds
of
questions
so
well.
Thank
you.
We
have.
We
have
three
three
minutes
left
and
I
think
nothing
that
we
can
actually
productively
accomplish
in
those
three
minutes.
So
I
might
suggest
this
is
a
good
time
to
say
thank
you
and
we'll
see
y'all
next
year
or
whatever.
D
A
I
think
I
think
the
left
emoji
is
inten
well.
A
A
A
D
F
A
And
once
like,
what
again
were
the
two
categories
that
you
mentioned
for
the
two
different
emojis.
F
F
A
And
I
think
I
think
that
there
is
this
this
I
guess
if
we
leave
full
open
partial,
I
guess
that's
quite
descriptive.
D
A
D
A
I
think
it's
something
the
community
would
be
interested
in,
though,
and
I
think
keeping
percival
support
is
is
helpful
because
people
know,
then
they
have
a
tool.
They
can
use
to
gather
the
data
from
that
platform,
and
I
think
that
that
would
influence
me
about
what
platform
I
chose.
So
you
know
knowing
that
percival
doesn't
currently
support.
Zulip-
and
this
is
you
know,
blog
posts
can
be
updated
and
when
augur
supports
things
like
this,
it
can
be
updated
with
that
information
as
well,
but
I
I
do
think
it's
helpful
to
to
have
that
indicated.
A
A
And
now
we're
a
minute
and
a
half
over
and
so
georg,
I
trust
you
to
complete
this
blog
post.
It
looks
really
good.
Thank
you
very
much
for
pulling
it
together
during
the
meeting.
That's
amazing
and
we
will
see
everyone
next
week
when
matt
is
our
noble
coordinator.