►
From YouTube: CHAOSS.D&I.June.17.2020
Description
CHAOSS.D&I.June.17.2020
A
A
A
A
Okay,
so
the
invitation
is
for
everyone
we'd
like
to
rotate,
who
is
facilitating
this
meeting
so
that
it
is,
you
know,
inclusive
and
we
can
rotate
and
if
one
of
us
leaves
or
cannot
make
it
that
the
meetings
can
continue
and
it's
a
great
way
to
facilitate
and
become
better
at
it.
So
if
anyone
wants
to
step
up,
the
invitation
is
open.
A
Action
items
from
last
week,
we
had
one
for
Matt
and
Elizabeth
to
go
through
the
repository
and
label
all
issues
that
are
metric
ideas
and
to
make
sure
they
are
included
in
our
spreadsheet
of
metrics
and
then
close
the
issues,
because
we
had
a
lot
of
stale
issues
on
a
repository
and
we
just
wanted
to
clean
up
and
keep
the
issue.
Tracker
actionable.
C
A
A
C
A
Thank
you
very
much,
I
also
added
for
the
next
action
item.
I
wanted
to
put
the
documentation
usability
metric
into
our
repository
I've
done
that
there
is
an
issue
created
for
that.
So
that's
all
good
and
then
Matt
Snell
wanted
to
convert
the
items
in
the
inclusive
leadership
metric
into
a
question.
That's
done.
We
also
got
it
already
merged
into
the
repository
and
we
have
a
issue
for
the
comments
in
their
pure
release.
F
A
A
C
A
B
A
A
C
B
C
B
A
A
C
A
C
A
E
Sure
I
can
just
give
some
context
of
why
why
this
is
interesting
to
me,
so
I
saw
the
spreadsheet
just
because
I
really
so
one
of
the
things
that
I'm
doing
in
my
current
role
is
looking
at
open
source
projects
and
trying
to
come
up
with
metrics
that
we
use
internally
for
from
my
organization
at
looking
at
open
source.
So
I
saw
the
spreadsheet
and
I
just
being
able
to
names
of
like
the
categories
that
have
already
been
defined
and
the
names
of
the
metrics
and
use
the
chaos
project
as
a
basic
I
guess.
E
My
concern
with
releasing
this
under
a
Creative
Commons
license
is
really
not
about
me.
Copying
the
spreadsheet
but
say
if
I
wanted
to.
You
know,
write
my
own
metrics
or
extend
some
of
this
work
in
a
way.
That's
in
a
context
of
specific
to
my
organization
and
won't
might
not
be
replicatable
by
other
projects
or
communities.
A
Creative
Commons
license
like
the
Creative
Commons
Attribution
license,
specifically
with
the
the
International
the
4.0
international
license.
E
E
It
would
just
it
would
give
me
more
creative
freedom
to
work
on
these
and
try
to
use
these
in
some
for
something
internally
and
maybe
bring
it
back
upstream,
once
I
get
a
little
bit
of
traction,
so
I
guess
that's
kind
of
the
my
view
on
and
why
I
brought
that
up
on
the
mailing
list,
because
this
is
really
awesome.
Work
and
I
totally
would
rather
build
on
what's
already
out.
There
then
try
to
reinvent
the
wheel
yet
again
with
a
very
similar
challenge.
I
have
in
my
role.
A
Well,
thank
you
very
much
for
your
interest
in
the
chaos
metrics
and
wanting
to
build
off
of
them.
I
I
would
love
to
hear
this
kind
of
feedback
and
future
feedback
that
you
do
have
with
regards
to
the
license
from
the
start
of
the
project,
you
always
wanted
to
build
something
that
you
and
others
can
build
off
of.
So
this
is
very,
very
much
core
of
what
we're
trying
to
do
here
and
as
mere
as
when.
To
give
you
a
little
background
and
we
started
the
chaos
project.
A
Looking
for
that
you
can
use
this.
You
didn't
even
have
to
attribute
the
work
that
we
are
doing.
It
would
be
nice,
but
you
can
use
it
internally
under
the
MIT
license
and
just
to
get
to
the
spreadsheet.
The
spreadsheet
is
just
the
summary
of
what
is
in
the
repositories
and
all
the
repositories
are
under
MIT
license,
and
so
all
the
work
is
free
for
you
to
use.
That's
that's.
How
I
see
it.
E
I
see
I,
guess
I
guess
my
view
at
the
MIT
license
is
it's
kind
of
like
it
works
it's,
but
it's
kind
of
like
using
a
square
peg
in
a
round.
Hole
is
kind
of
the
way.
I
see
it
for
this
type
of
content.
I
just
think
the
creative
commons-licensed
are
more
explicit
about
some
of
the
things.
I
think
the
Creative
Commons
Attribution
license
is
sort
of
an
equivalent
to
the
MIT
license
in
terms
of
how
free
it
is
to
reuse.
E
It's
a
free
culture
license
I
think
the
MIT
license
is
enough
for
now,
but
I
think
Creative
Commons
might
be
a
better
fit
for
some
of
this
content.
I
think
it
might
be
as
something
it's
helpful
to
think
about,
but
at
least
I
guess
in
the
immediate
sense,
I
can
probably
experiment
and
work
around
with
some
of
this
under
the
MIT
license.
I.
C
Have
a
comment
so
I
agree:
Justin
the
I
think
the
optics
that
a
Creative
Commons
license
provides
on
documentation
is
clearer
than
what
the
MIT
license
provides.
I
do
think
that
there's
a
I
mean
Creative
Commons
is
very
explicit.
Around
documentation
and
MIT
is
agreed
with
you
historically
kind
of
around
code
right.
So
so,
while
I
I
do
think,
the
MIT
license
will
enable
you
to
remix
and
simply
provide
attribution.
It.
C
You
to
do
that
and
you
shouldn't
have
any
trouble
with
that.
I
actually
think
this
raises
a
question
that
we
should
talk
about
in
the
chaos
project.
I
do
actually
kind
of
lean
towards
a
Creative
Commons
license
largely
for
the
optics
that
it
provides
around
documentation
that
that's
my
own,
take
I
mean
I,
don't
think
it
would
be
a
huge
lift
I.
C
A
C
E
A
A
A
E
It
it
just
definitely
makes
it
easier
for
me
to
work
with
this
in
the
context
that
I'm
working
in
that
was
why
I
was
interested
in
at
all.
Is
it
just
it's
one
way
that
makes
it
a
little
easier
for
me
to
promote
the
chaos,
work
and
use
it
internally
and
hopefully
get
some
more
folks
who
are
really
already
thinking
about
some
of
these
things
in
my
own
organization,
to
maybe
even
think
about
coming
upstream
and
and
collaborating
with
some
of
the
other,
this
working
group
or
other
working
groups
too?
C
On
the
the
other,
I
did
send
to
an
email
like
one
minute
before
this
project,
and
my
only
other
or
before
this
meeting.
My
only
other
concern,
not
your
irrespective
of
the
license
is
that
the
the
spreadsheet
is
not
one-to-one
with
the
release,
and
so
the
spreadsheet
is
a
working
document
where
we
kind
of
like
I
shop
ideas
like
when
you
heard
Georg
saying
like
we
would
close
issues
and
just
kind
of
drop
them
into
the
spreadsheet.
C
So
we
don't
lose
the
the
ideas
so
the
spreadsheet
tracks,
things
that
have
been
released,
things
that
we're
talking
about
and
things
that
are
just
like
purely
nascent
ideas.
The
the
release
is
just
that
it
is
released
metrics,
and
so
those
two
are
not
equivalent
and
we've
had
this
problem
in
the
chaos
project
where
we
have
the
release,
which
is,
is
the
release
and
we
have
a
github
repository
that
is
not
equivalent
to
that
release,
and
it
does
create
some
confusion
for
newcomers
like.
C
B
E
I
guess
it's
maybe
like
two
really
quick
pulses,
so
I
guess
I
came
in
at
Raul
what
this
I
was
really
interested
in
the
categories
and
the
titles
of
the
metrics,
so
I
think
the
larger
discussion
about
Creative
Commons
is
really
getting
at
the
root
of
what
I
was
interested
in,
but
for
the
spreadsheet
it
wasn't.
That
was
just
the
interface
that
for
me,
that
was
the
first
time
I
saw
and
I
was
like.
Oh
wow,
like
here's,
this
handy
list,
it
was
just
very
quick
and
easy
for
me
to
digest.
E
You
know
it
was
just
that
was
what
kind
of
got
me
to
actually
start
poking
around
at
some
of
this.
That
was
why
I
was
I
was
interested
in
it,
just
as
something
I
could
share
share
around
more
freely,
but
it's
not
really
critical,
like
really
really
the
root
interest
or
concern.
I
have
would
be
around
the
wider.
What
we
were
talked
about
earlier
when
we
already
went
into,
is
just
a
Creative
Commons
license
for
them.
C
C
E
C
A
C
E
A
A
What
are
the
different
demographics
that
we
look
at,
and
we
came
up
with
this
really
nice
list
of
gender
identity,
sexual
orientation,
agent,
everything
and
we
said
that,
instead
of
defining
questions
ourselves,
we
would
built
on
the
work
that
already
exists.
The
open
demographics
initiative
that
has
come
up
with
really
great
questions
that
you
can
just
use
in
your
own
surveys
in
your
own
work.
A
D
C
B
A
E
A
E
C
E
We
try
to
do
a
survey
that
we
were
gonna
send
out
at
the
community,
but
it
just
got
lost
and
legal,
because
all
these
concerns
that
we
as
a
volunteer
community
weren't
ready
to
take
on
there
were
just
all
these
other
legal
considerations
with
gdpr
and
I
was
just
interested.
If
anyone
has
thought
about
that
aspect,
yet
I
haven't
dug
into
these
yet.
But
that's
something
I'm
curious
about
specifically
to
Democrats.
G
Could
it
necessarily
tie
anything
back
to
a
certain
person?
If
that's
your
concern
Justin,
but
the
whole
overall
survey
was
written
in
such
a
way
that
couldn't
be
tied
back
to
anyone
and
at
the
same
time
that
was
kind
of
hurt
us,
because
we
couldn't
ask
follow-up
questions
if
that
makes
sense.
So
we
got
full
honesty
because
we
got
some
nasty
responses.
So
I
know
people
were
being
honest.
They
may
or
may
not
have
actually
been
in
the
community,
but
you
know
when
you
had
something.
G
You
know
that
said
you
know:
I
don't
get
attention
because
I'm
not
as
old
as
other
people.
Again
we
couldn't
follow
up
and
even
see
which
of
the
OpenStack
projects
they
were
talking
about
because
there
was
no
times
so
I
think
the
questions
are
valid
and
usable
in
a
larger
setting
and
the
are
anonymous.
They
are
honestly
anonymous.
You're
not
gonna,
be
able
to
put
things
together,
but
at
the
same
time
you
can't
put
anything
together
to
follow
up
and
Matt
went
through
the
raw
data.
So
he
can
talk
on
that.
H
Sorry
can
I
jump
in
and
just
add
one
special
case
here
that
we
kind
of
forget
about.
Sometimes
you
want
to
anonymously,
just
know
where
it
comes
from,
and
sometimes
that,
together
with
the
demographic,
is
all
you
need
to
know
who
it
is.
That's
just
the
one
edge
case
of
partial
anonymity
and
demographics
just
to
keep
in
mind,
because
getting
that
one
time
is
a
little
too
much
I
think
you
know
Pro
food,
because
the
purpose
is
it
should
help.
C
C
C
Maintaining
the
questions
around
open.
Demographics
is
super
important
for
understanding,
open
source
health,
and
somebody
has
to
do
it
and
I
think.
If
it's
us,
then
it
has
to
be
us.
We
have
to
figure
out
a
way
to
do
that,
because
it's
if
our
goal
is
to
get
a
better
handle
on
on
community
health-
and
we
don't
have
a
good
set
of
demographic
questions
to
offer
to
people
I
think
that's
a
that's
a
detriment
to
open
source
as
a
whole.
H
H
I,
it's
not
a
question,
it's
just
one
thing
that
we
did
think
about
when
we
were
trying
to
do
this
in
no
js'
a
trusted
individual
who
is
the
only
individual
or
two
or
whatever,
who
are
allowed
to
actually
see
the
identifiable
information
of
feedback
that
could
be
I,
guess
causing
contention
or
friction
as
it
goes
up.
Ditching.
E
E
We
had
a
lot
of
support
and
a
lot
of
resources
for
the
questions
and
I
think
while
it
does
help
to
identify
some
of
the
questions,
I
think
the
real
challenge
in
demographic
data
and
what
also
makes
it
I
want
to
say
valuable,
but
more
useful
is
when
you
can
connect
the
ID,
the
anonymous
identity
of
someone
to
to
their
responses
in
a
way
that's
privacy,
respecting
and
and
doesn't
expose
any
personally
identifying
information
like.
That
was
just
something
that
we
tried
to
do
that
in
Fedora,
and
we
had
questions
that
we
had.
E
So
like
to
me,
I
think
of
it,
as
actually
one
of
the
key
things
that
I
think
this
group
could
offer,
is
strategy
on
how
you
collect
that
metrics,
because
I
think
there's
a
lot
of
data
out
there
of
like
good
questions
to
collect
on
demographics
and
even
if
it's
a
little
outdated,
it's
like
the
stuff
doesn't
really
change
that
often
I
mean
it
can
and
it
does.
But
it's
not
something
where
you're
working
on
you
know.
E
It
changes
monthly
kind
of
thing
right
so
that
just
something
that
I
feel
like
I've,
been
on
my
mind
for
a
long
time.
Guess
if
we
went
I
spent
two
years
with
the
Fedora
community
trying
to
launch
a
demographic
survey,
but
we
just
got
so
stuck
up
on
these
GDP
concerns
that
we
just
weren't
equipped
and
didn't
have
the
information
to
know
how
to
handle.
G
So
our
questions
really
did
change
between
the
first
edition
of
our
survey
and
I'll
say
two
years
later,
when
we
did
the
newer
version
and
we
tried
to
keep
some
bounce
peek
to
ask
the
same
questions
so
we
could
correlate.
You
know
how
the
community
was
changing
and
what
we
saw
was
the
mozilla
survey
had
such
better
questions
than
us,
but
some
we're
going
to
do
this.
Some
things
we
kept
running
into
were
the
fact
that
if
you,
google
and
look
for
demographic
type,
questions
are
all
us-based.
G
G
Maybe
we
are
the
place
to
put
them
I
know
we
did
gather
different
demographic
surveys,
maybe
weep
from
there.
We
can
see
the
best
questions
maybe
add
to
them,
but
yeah,
going
back
and
forth
to
try
to
get
the
best
questions
is
what
eats
up
time
and
it
having
same
or
very
similar.
Questions
will
also
allow
us
to
look
at
data
and
be
able
to
compare
apples
to
apples
as
best
as
possible
versus
I
know
between
our
first
survey
and
our
second
survey.
Some
of
the
questions,
especially
gender,
was
apples
and
oranges.
G
A
So
I
fully
agree
with
what
you're
all
saying
that
it's
super
critical
to
have
these
metrics.
These
questions
that
we
need
to
have
a
place
somewhere
where
we
can
make
recommendations
to
others
might
be
that
we
create
them
that
there
are
challenges
around
management
data
collection.
All
that
that
we
should
provide
some
recommendations
for
to
help
communities
and
projects
collect
this
kind
of
data.
So
it
seems
like
just
listening
to
what
you're
all
saying
that
this
is
something
we
can
talk
about
again
next
week
and
maybe
start
thinking
about
how
to
approach
this.
G
C
Can
I
make
one
last
comment,
so
it's
a.
It
was
a
point
that
Justin
was
bringing
up.
So
one
of
the
things
that
we're
finding
in
the
chaos
project
is
the
metrics
that
we
assemble
are
really
like
the
they're,
the
bricks
right,
they're,
the
they're,
the
small
kind
of
localized
pieces
and
a
person
may
not
just
deploy
a
metric
in
a
one-to-one
sense
right.
So
there's
the
we
have
to
think
about
how
the
metrics
can
be
combined
in
meaningful
ways
that
provide
meaningful
insights
to
those
that
are
deploying
them.
C
So
to
your
point,
I
think
we
need
to
provide
not
just
it
in
the
case
of
say,
demographics
like
here,
they
are,
but
also
here's
ways
to
think
about
deploying
those
we're.
Not
we
don't
guarantee
that
this
is
the
perfect
way
for
everybody,
but
here's
just
a
way
to
think
about
the
deployment,
and
so
if
we
looked
at
different
working
groups
like
age
of
issue
like
age
of
issue
might
not
be
the
metric
all
by
itself.
C
B
B
B
B
So
this
is
kind
of
for
anybody
who
doesn't
know.
This
is
the
basic
idea
of
a
submission
for
a
project,
because
we
can
take
projects
or
events
in
our
badging
program
and
us
has
been
working
really
hard
on
getting
these
more
refined.
This
is
a
mock
submission
that
will
have
a
lot
of
different.
It
has
five
different
metrics
from
the
project
and
community
section
of
the
DNI
metrics,
and
each
metric
kind
of
has
its
own
questions.
B
Most
of
this
is
to
figure
out
if
how,
if
they're,
measuring
their,
if
they're,
using
the
chaos
metrics
in
a
certain
way
or
measuring
these
things
in
general,
on
how
they
do
that
it's
it's
kind
of
a
nudge
to
work
on
chaos,
metrics
for
the
project
itself.
With
the
event
the
project
review
checklist
is
the
newer
item
in
which
this
is
what
the
person
who
is
reviewing
the
project
will
fill
out
in
order
to
after
they
review
the
project
for
a
bit
and
everybody.
The
information
that's
provided
from
the
project.
B
This
is
what
they
used
to
fill
out
and
say.
This
project
is
kind
of
is
checking
this
like
measuring
these
metrics,
and
this
is
and
it's
supposed
to
just
check
boxes,
so
it's
easier
on
the
reviewer.
If
the
answer
of
you
a
lot
of
projects,
so
we'd
like
to
get
some
feedback
on
this
as
well,
because
it's
pretty
new
a
pretty
new
process
for
the
review
itself.
So
any
comments
are
welcome.
B
C
They
can
actually
have
an
impact
in
the
world
and
hasta
and
Matt
and
Saleh
and
Tola
have
all
been
working
on
the
DNI
badging
program,
which
would
be
an
opportunity
for
events
and
for
projects
to
earn
diversity
and
inclusion
badges
by
representing
adherence,
isn't
the
right
word,
but
conformance
to
a
select
set
of
Kaos,
DNI,
metrics
and
so
I
think
what
hasta
is
providing
here
is
two
different
ways.
It
looks
like
one
is
via
PR
and
what
does
it
via
gist
as
to
how
to
actually
do
the
review
process?
Is
that
right,
Matt.
B
C
B
B
C
B
Yes,
I
agree
and
our
weekly
minutes
for
anybody
that
is
interested
I'll
put
them
in
the
meeting
minutes
as
well,
but
we
have
weekly
minutes
in
the
documentation
here
that
we
also
have
one-on-one
meetings
and
those
are
those
minutes
are
in
the
weekly
minutes.
So
we
got
all
kinds
of
documentation
that
we're
doing
to
make
sure
that
we
get
this
project.
We
do
we
do
it
in
a
way
that
makes
sense
so
yeah.
That's
all.
We
have
I
think
from
my
site
at
least.
A
All
right,
we
are
technically
out
of
time.
We
always
like
to
end
the
meeting
minutes,
a
couple
minutes
before
the
hour
to
give
and
one
time
for
a
little
break
before
the
next
meeting
starts
and
a
life
full
of
zoom
meetings.
So
thank
you
very
much.
Everyone
will
have
guru
sum
of
code
and
outreach
updates
next
week,
and
then
you
can
talk
about
the
ethics
statement
that
we
talked
about
in
the
weekly
call.
You
see
it
at
the
bottom
of
the
jenefor
today.
You
can
also
talk
about
that
next
week,
thanks
everybody.