►
From YouTube: CHAOSS.D&I.February.11.2019
Description
CHAOSS.D&I.February.11.2019
A
B
I
think
we
can
get
it
started
so
welcome
everyone
to
our
chaos,
diversity
and
inclusion,
work
meeting
on
February
11.
We
like
to
record
these
and
put
them
on
YouTube,
so
anyone
who
misses
the
reading
can
catch
up
or
if
you
want
to
review
something.
If
you
don't
want
this
to
be
posted
publicly,
please
let
us
know
and
you'll
take
it
down.
B
B
The
second
one
is
the
readme
that
nicole
has
worked
on
I
hope
she
can
point
us,
then
for
releasing
metrics
I
posted
to
the
general
main
list
today
that
we
have
a
proposal
and
we
need
a
sub
domain
for
the
DNI
metrics.
So
we
can
talk
about
this
proposal
there
and
then
I'm
interested
also
in
how
we
can
move
forward
the
metrics
that
were
advanced
during
Cal's
cough
any
other
items.
Anyone
would
like
to
talk
about
today.
B
B
B
B
So
I
don't
know
if
anyone
has
comments,
the
notice
about
the
paid
versus
unpaid
contributors
and,
right
now
it
reads
note
that
hate
versus
unpaid
contributors
can
be
a
problematic
and
nuanced.
From
the
perspective
of
diversity.
Inclusion.
Many
people
who
participate
as
well
in
tears
are
coming
at
it
from
a
position
of
privilege
because
they
can
afford
to
spend
their
free
time
participating
in
an
open-source
project
instead
of
working.
B
A
second
job
to
make
ends
meet
caring
for
family
members
or
spending
time
meeting
basic
survival
needs,
in
other
words,
having
more
volunteer
computers
might
actually
mean
that
the
project
is
less
they
worse
rather
than
more
diverse.
However,
in
a
corporate
sponsored
project
involving
volunteer
contributors
could
be
a
sign
that
the
community's
welcoming
and
inclusive.
B
C
Do
you
people
think
about
that?
I
feel
like
it's
an
enormous
note,
but
we've
had
a
lot
of
discussion
around
this,
because
the
this
particular
dimension
of
diversity
is
a
set
of
the
note,
problematic
and
a
bit
nuanced,
so
we
weren't
quite
sure
what
to
do
with
it.
Does
this
seem
like
a
reasonable,
a
reasonable
solution
to
that?
If
so,
I
can
go
ahead
and
merge
it,
but
I
am
curious.
What
other
people
think.
C
B
C
A
I
do
think
it's
an
important,
distinct
and
one
does
give
you
but
you're
right.
If
there's
sometimes
the
unpaid
actually
means
a
less
diverse
group
cohort
of
people
that
are
volunteering
but
I
think
there's
just
interest
in
curiosity
to
know
what
percent
or
what
portion
of
volunteers
are
paid
versus
unpaid
anyway,
just
for
reasons
of
whether
it's
wanting
to
know
how
corporate
backed
it
is
or
how
I
think.
Sometimes,
there
is
even
the
belief
that
there's
so
much
volunteer
effort
in
open-source,
but
actually
there's
a
lot
of
paid
in
corporate,
backed
activity
and
effort.
B
D
I
have
a
comment:
this
is
Sharon
when
we
did
our
original
diversity.
So
they've
got
a
couple
years
ago.
We
actually
incorporated
something
in
there
around
paid
and
unpaid
just
to
try
and
capture
this.
This
dimension
so
I'm
not
sure
how
well
we
captured
it,
but
we
saw
as
a
distinction.
It
was
something
that
we
thought
would
be
important
to
capture.
So
so
yes,
yeah
yeah,.
C
C
C
B
B
E
A
E
So
for
our
Ricci,
that's
the
program,
I
think
it's
run
through
the
sector,
freedom
Conservancy.
Basically,
you
need
to
bring
I
think
it's
sixty
five
hundred
dollars
forward
as
an
organization
to
actually
fund
the
student
and
so
I
was
I
was
gone
last
week,
kind
of
exploring
a
few
options,
amongst
other
things,
and
one
of
the
groups
that
I
had
talked
to
actually
does
more
direct
funding
to
the
outreach
program,
as
opposed
to
kind
of
the
individual.
A
B
C
F
B
What
we
talked
about
is
that
people
would
like
to
have.
Did
you
involve
someone
who
can
help
us
with
polishing
me?
What
we
have
the
use
cases
that
we
have
need
to
work
on
as
we
are
working
with
more
and
more
projects
to
implement
metrics,
you
can
use
someone
who
can
collect
that
information
and
write
engaging
blog
posts
to
spread
the
news
and
share
what
we
learn.
So
there
are
several
ways
that
I
think
an
outreach.
A
student
could
help
with
advancing
our
mission
and.
A
F
F
B
E
G
F
E
B
B
The
next
action
item
was
to
create
a
pull
request
to
add
contributors
to
our
readme.
We've
done
this
and
it's
already
merged
the
added
Sarah
Conway
as
a
core
contributor,
because
she
has
been
reliably
showing
up
and
contributing
over
the
last
few
months
and
she
added
someone
who
create
a
portrait
of
us
as
a
contributor.
So
thank
you.
Thank
you.
B
H
B
H
So
this
was
so
we
had
a
meeting
in
shop
during
last
week.
Meeting
right
from
hiker
layer
came
to
the
meeting.
It
was
basically
happy
all
participating
and
using
hyper
layer
assets
use
case.
So
I
was
the
one
adding
this
to
the
agenda.
I
think
Sharon,
no
scheming,
I,
don't
know.
If
you
have
some
more
information,
perhaps.
A
Yeah
I
guess
yeah.
That
was
my
colleague,
dry
and
I.
Don't
know
if
he's
on
the
call
this
week,
but
I
guess
I'd,
love
to
know
and
I
can
share
back
with
them
like
what
are
the
first
steps
for
becoming
like
a
use
case
example,
and
is
there
something
that
the
hyper
ledger
project
needs
to
do
or
is
it
something
that
we
need
to
share
with
them?
Sort
of
you
know
how
that
would
start.
H
So
I
would
say
that's
a
good
question,
basically
based
on
to
the
way
we
are
seeing
this
in.
In
other
documents,
we
produce
is
basically
using
the
different
focus
areas
that
are
already
defined.
They
basically
go
through
well
go
through
that
several
questions
on
metrics
define
their
an
example
of
this.
D
H
And
then
go
ahead
with
this
and
I.
Don't
know
what
the
thing
I
mean
you
rest
of
you
here
in
Nicole,
but
to
check
if,
if
this
is,
if
having
the
data
that
we
want
to
have,
for
instance,
for
governments,
what
was
the
purpose
of
having
such
data
a
bubble?
Checklist
is
useful
for
the
board
touring
hands
for
the
community.
People
attend
part
actives
and
see
if
this
is
something
that
helped
the
board
to
make
decisions
basically
or
to
become
more
inclusive
or
to
bring
more
diverse
people
on
board.
G
G
G
H
Yes,
that's
what
I'm
suggesting
Matt
with
a
with
a
main
difference,
which
is
with
solitaire
that
with
OpenStack,
we
have
a
set
of
deadlines.
That
was
more
a
common
interest
in
understanding
diversity,
inclusion,
Nibbana
stack
with,
but
with
some
specific
deadlines
that
we
had
between
what
the
two
companies
and
so
on.
So
we
had
a
self-
let's
say
commercial
branch
here
that
we
have
to
deal
with
if
we
go
with
for
Piper
lay
here.
H
This
is
some
some
work
that
we
have
to
do
all
together,
perhaps
and
having
a
per
layer
as
use
case.
So
then
my
suggestion
was
basically
to
start
small
and
we
understand
with
one
of
the
focus
areas
and
then
check
it.
The
focus
area
is
currently
being
useful
for
the
community
and
for
the
world
and
for
us
as
a
working
group
and
so
on,
but
that
was
basically
my
suggestion
to
basically
is
to
start
small.
G
Yeah
yeah,
so
the
word
yeah,
so
we
did
have
some
deadlines
in
place
for
the
work
that
we
were
doing
in
the
OpenStack
community,
and
this
means
were
around
initially
were
around
the
OpenStack
summits.
That
happened
twice
a
year,
which
also
coincide
with
the
OpenStack
releases
and
and
then
it
also
became
that
because
we
we
were
writing
blogs
and
around
the
work.
G
H
E
G
G
Okay,
I
was
trying
I
was
trying
to
zoom.
I
was
trying
my
computer
this
morning,
rather
than
my
phone
I
may
go
up
back
to
my
phone
yeah
I
I
was
just
saying
that
I
gosh,
let
me
know
if
you
still
have
trouble
if
you
can't
hear
me,
but
I
was
just
saying
that
the
OpenStack
reports
that
we
were
publishing
covered
the
majority
of
the
metrics
or
metric
categories
that
are
included
in
the
chaos,
be
by
work.
H
G
H
E
I,
just
I
think
what
I'm
hearing
I
think
it
makes
a
ton
of
sense
is
I,
don't
know
if
you
saw
in
the
chat.
I
just
picked
out
three
of
the
goals
from
three
of
the
focus
areas
in
DNI
and
so
I
think.
Maybe
just
a
thought
is
trying
to
understand
from
hyper
ledger
what
goals
they're
trying
to
accomplish
and
I
think
really
just
using
the
goals,
as
stated
at
the
work
that
you've
all
done
might
be
a
good
starting
point
see
your
point
Daniel
that
you
can
have
a
kind
of
a
lower.
H
Another
another
way
of
doing
this,
but
with
that
instead
of
being
asked
the
producers
of
the
of
the
report,
we
are
the
ones
kind
of
mentoring
or
helping
to
drive
this,
because
if
there
are
people
already
doing
this
job
in
the
I
perlier
community,
then
we
we
can
be
kind
of
the
icy
drivers
here
right.
We
help
them
to
understand
what
we
are
trying
to
achieve
and
then
be
some
common
goals.
E
H
Yeah,
probably
the
world
is
consultants
like
you.
Let's
imagine.
We
have
a
couple
of
people
interested
in
producing
this
analysis
for
hyper
layer.
Then
we
can
we
we
help
them
to
to
understand.
These
are
the
focus
areas.
These
are
the
questions.
This
is
the
way
we
are
measuring
things.
We
have
a
couple
of
examples
here
then,
how
can
we
do
this
for
hyper
layer?
A
Yeah
I
think
that's
great,
so
I
try
to
work
sort
of,
as
liaison
back
to
the
hyper
ledger
team
and
ask
you
know
of
the
focus
areas
and
the
goals
that
we
put
forward.
You
know
which
ones
are
they
may
be
wanting
to
focus
on
or
maybe
already
investing
energy
into,
and
maybe
to
your
point,
identify
two
or
three
to
start
with
versus.
You
know
the
whole
our
whole
list
that
we've
gone
through
and
work
it
that
way
and
see
where
they
in
their
maybe
hopefully
get
ride
to
a
future
meeting.
A
I
B
A
Can
I
for
that
meeting?
It
sounds
like
the
most.
Some
important
people
to
have
at
that
meeting
would
be
people
from
the
involved
in
the
project
from
the
Linux
Foundation
side
that
are
helping
run
the
project
as
well
as
people
in
the
technical
community
or
at
the
board
level.
Is
that
would
that
be
the
great
group
of
people
to
try
to
connect
Danni
night
I?
Think.
H
D
A
Do
we
have
anything
that
sort
of
summarizes
I
know
it's
not
the
formal
chaos
working
group
I'd,
like
I,
think
the
open
staff
works
sort
of
predates
the
chaos
group
dni
group
existing,
but
things
have
sort
of
now
been
happening
in
parallel.
If
I
understand
it
correctly,
I'm
wondering
do
we
have
a
almost
like
a
little
mini
case,
study
or
use
case
success
around
the
work
we've
done
with
OpenStack.
Would
that
just
be
too
premature
and
the
time
he
doesn't
really
match.
H
Well,
as
nickel
means
can
we
that
that
report
basic
covered
part
of
all
of
the
information
we
want
to
cover
in
care,
so
I
think
it's
a
good
starting
point
and
I
would
say
it's
kind
of
the
he
thinks
we
can
retrieve,
because
we
were
basically
going
to
the
website
or
analyzing
developers
these
things,
while
there
are
other
metrics
that
we
want
to
to
have
in
care
that
are
more
savvy
ways
which
are
typically
more
time
intensive.
Perhaps.
H
G
If
you're
looking
for
one
piece
like
like
I'd,
like
one
case
study,
you
know
I'm,
not
sure
Daniella,
what
do
you
say?
God
I'm
not
sure
that
we
have
that
I
think
I
would
point
to
it.
I
think
I
would
point
to
the
different
logs
that
were
written
about
the
report.
You
know
so
so,
basically,
typically,
the
way
that
it
would
happen
is
that
we
released
a
report
I'm
right
around
the
time
of
this
summit,
and
we
would
yes
exactly
a
superuser.
G
G
A
G
B
B
G
G
G
G
The
the
idea,
then,
would
be
to
to
essentially
say:
okay,
here's
here's.
What
we
agree
on
for
what
our
readme
structure
would
be.
File
structure
would
be
and
I
picked.
It
then
go
in
and
grab
and
I
guess
where
it
doesn't
exist,
but
I
think
most
of
this
exists
in
some
form
or
another,
and
it
basically,
you
put
together
to
read
me
in
the
structure
that
we've.
B
G
B
G
G
Okay,
so
moving
through
this,
then
I
just
wanted
to
get
focused
at
Brennan
for
how
we
came
up
with
the
proposed
structure,
but
I
guess
so
introduction
to
address
New
York's
comment
here
and
then
+1
yeah
include
a
table
of
contents.
Are
we
all
in
agreement
with
that,
then
seems
to
make
sense
yep,
so
I
can
quickly
solve
on
that.
B
G
So
the
the
idea
here,
if
I,
can
kind
of
up
little
bit
conversation
just
a
bit
me.
The
idea
here
was
that
we
wanted
to
quickly
give
good
idea
for
what
did
what
the
group
is
working
on
and
then
get
them
to.
How
do
you
contribute
right?
How
do
to
invite
more
contributors
to
dive
in
so
today?
The
day's
basically
give
them
sufficient
information
to
grok
what
what
we're
focused
on
and
then
how
do
they
get
involved?.
C
Think
the
concern
is
that
for
someone,
that's
completely
new
having
the
metrics
at
the
very
top
of
the
dock
doesn't
provide
any
context
before
they
get
there.
So
it
could
be
confusing.
For
people
who
haven't
had
haven't
spent
the
time
that
we
have
looking
at
looking
at
metrics,
because
they
don't
know
why
they're
looking
at
what
they,
what
they're
looking
at
I,
think
that
was
the
the
argument
for
putting
putting
them
a
little
bit
later.
If
I
remember
correctly,.
E
Yeah,
it
seems
like
there's
two
schools
of
thought
right.
How
do
I
get
involved
and
then,
which
maybe
is
a
use
case?
I'll
just
put
it
that
way:
right,
yeah
I,
don't
how
do
I
connect
and
how
do
I
get
involved,
and
then
the
other
is
folks
that
are
really
not
want
to
know
what
multics
should
I
be
looking
at
for
my
community
I'm,
not
saying
one
is
better
than
the
other.
It
just
appears
to
be
with
the
conversation.
Is
that
that's
all.
C
E
G
B
D
B
G
G
G
G
G
B
C
And
I
think
it
makes
sense,
because
if
people
are,
if
people
are
new
and
they
haven't
contributed
yet
having
all
of
the
information
about
what
the
goals
are
with
the
youths
cases
are
what
the
workflow
looks
like
all
of
that.
Having
all
of
that
above,
the
contributing
section,
I
think,
makes
a
lot
of
sense,
because
then
they
can
make
a
decision
whether
or
not
they're
interested
in
contributing
okay.
G
G
B
G
G
G
You
make
a
statement
about
usage
and
use
cases.
I
can
tell
you
how
just
from
the
contents
in
the
James
eworkgroup
file
how
this
was
being
used
right,
yeah,
it
was
usage.
You
think
how
to
use
this
repository
and
when
to
release
metrics
and
the
write
that
piece
and
so
you
can
use
cases
are
different.
I
think
we
can
resolve
it.
I
think
that
we've
provided
this
clarification.
G
G
The
I
think
we've
done
the
the
structure
revision,
the
the
ones
starting
the
bottom
here
is
the
one
for
the
GMT
workgroup
I
just
carried
it
over
here,
so
that
we
could
see
it
and
the
ones
that
I
put
in
red
were
ones
where
I
was
a
little
confused
cuz.
It
seemed
to
be
redundant,
but
I
was
going
to
go
at
back
to
bend
and
ask
about
those
I.
G
G
G
A
G
B
G
G
B
C
B
Okay,
I'm
fine
with
postpone
a
good,
then
I
do
well.
We
do
have
two
minutes.
I
want
to
talk
about
the
proposal.
Then
the
infrastructure
give
you
an
idea
of
what
this
is
about.
The
so
Toby
Sean,
Matt
and
I
met
to
discuss
how
we
can
release
metrics
in
a
way
that
is
more
appealing
than
markdown
files
in
a
github
repository.
C
B
C
Was
my
question
whether
whether
that
was
just
the
metrics
repository
or
whether
that
also
includes
the
GMD
and
the
mm-hmm,
the
DNI?
So
everything
is
on
the
slash
metrics
page
and
then
we
use
the
subdomains
to
basically
give
us
a
place
to
put
all
of
the
metrics
from
each
of
the
subdomains
before
they're
aggregated
up
unto
the
main
page.
Yes,
okay,
that
seems
reasonable.