►
From YouTube: CHAOSS Monthly Call August 7 2018
Description
Monthly CHAOSS Meeting for August 2018
A
Right,
why
don't
we
go
ahead
and
get
started
couple
agenda
item
today,
I
think
we'd
like
to
start
out
with
working
groups.
As
you
know,
today's
are
a
bit
of
a
more
formal
meeting,
so
what
we
get
some
updates
as
to
what's
going
on
with
diversity
and
inclusion,
as
well
as
with
maturity
and
decline,
never
would
like
to
chime
in
on.
C
Growth
maturity
decline,
we
moved
our
days
and
we
are
gonna,
do
a
better
job.
Promoting
the
new
day
for
the
next
meeting.
The
last
meeting
had
a
very
small
turnout
and
we
didn't
decide
anything
because
I
didn't
think
we
had
enough
representation.
I
do
believe
we
are
getting
a
growing
amount
of
engagement
from
various
community
manager
types
and
we
are
gonna,
have
a
lot
of
a
lot
of
new
instrumentation
to
share
with
people
at
KS
comm,
including
a
Status
page,
that
we
reviewed
on
the
last
regular
ngon
monthly
call.
C
D
C
Page,
what
is
this?
That's
the
the
page
or
we
can
see
a
breakdown
of
which
of
the
metrics
are
implemented
in
order
and
in
a
description
of
those
metrics
and
I.
Think
I
think
our
working
group
is
in
the
process
of
defining
really
two
dimensions.
One
is
the
metadata
that
needs
to
be
captured
with
relation
to
each
metric,
so
commits,
for
example,
can
include.
C
There
are
number
of
ways
of
counting
them.
Sometimes
whitespace
is
removed.
Sometimes
it's
not
sometimes
squash.
It
sorry
counting
for
sometimes
they
aren't
so
to
the
extent
that
there
are
these
variations
every
time
a
metric
is
presented,
we're
trying
to
describe
the
families
of
variations
and
we're
calling
that
metadata
and
then
also
we're
in
the
process
of
defining
individual
metrics,
with
more
clarity
and
growling
them
a
little
bit
more
in
published
research
about
the
metrics
themselves.
A
A
A
C
A
C
We
do
have
a
format.
We
do
have
a
working
repository
that
is
not
in
the
main
metrics
repository,
but,
unlike
the
I,
think
I
think
there's
two
fundamentally
different
problem
spaces
here
that
diversity
and
inclusion.
That
group
has
really
started
from
the
ground
up
and
tried
to
understand
what
are
the
potential
useful
metrics
in
that
space
because
they
have
not
existed
for
long
or
been
deployed
that
often,
in
the
case
of
growth,
maturity
and
decline.
C
The
metrics
that
are
outlined
in
the
main
metrics
repository
have
been
defined
before
people
are
generally
familiar
with
many
of
them,
so
the
fork
repository
or
the
version
of
a
growth
maturity
decline
of
working
group
repository
that
we
have
is
not
substantially
different
than
what
is
currently
in
the
metrics
repository,
and
that
is
that
is
the
difference
between
this
working
group
and
diversity
and
inclusion.
I.
Think
ok,.
G
I
do
have
a
I
do
have
a
pull
request
into
the
GMD
work
group
to
try
to
align
the
structure
more
with
the
diversity
and
inclusion
work
group
structure
structure
to
kind
of
a-line
our
processes
a
little
bit
well.
I
put
that
in
last
week,
I
missed
the
meeting
last
week,
because
I
was
in
an
interview.
So
if
someone
was
taking
up
in
the
next
meeting,
then.
A
A
Okay,
that'd
be
good
cool
and
then
Sean.
There
was
also
some
discussion.
I
think
the
way
that
diversity
and
inclusion
is
kind
of
going
and
Georg
you
can
chime
in
on
this,
but
the
way
that
they're
kind
of
presenting
the
structures
is
a
bit
higher
level
than
these.
The
low
level
metrics
is
that
right,
Georg
I'm,
trying
to
get
this
all
straight,
so
the
DNI
group
is,
is
presenting
their
work
in
a
particular
way
and
kind
of
thinking
through
how
they
consider
their
own
metrics.
Yes,.
A
B
That
layer
sits
above
the
individual
metrics
but
below
the
categories
and
high-level
metrics,
where
we,
where
we
outline
what
are
the
goals
and
for
a
specific
metric
or
why
do
we
want
to
look
at
it
and
what
are
all
the
different
ways
of
looking
at
it
and
then,
within
that
layer
we
describe
what
are
the
tools?
What
metrics
can
they
provide?
How
do
we
interpret
those
metrics?
It's
the
handbook
approach,
it's
the
recipe
approach
that
we
inserted
at
that
level.
Okay,.
A
E
C
I
think
and
I
think
that's
that
pull
request
is
certainly
something
that
we
will
consider
in
the
next
meeting.
The
certainly
the
rhythm
of
this
working
group
is
slightly
different
than
the
rhythm
of
the
diversity
inclusion
group
and
we'll
have
to
sort
of
as
a
group
determine
it.
The
process
that
DNI
wants
to
align
us
with
is
a
process
that
works
for
this
group
and
and
I
can't
I
can't
really
speak
to
whether
it
is
or
it
isn't,
because
I
haven't
looked
at
Kevin's
pull
request.
Yet.
Okay,.
A
C
H
C
Think
that
resolving
that
through
some
of
the
metadata
and
other
discussions
is
our
principal
objective
before
chaos
counts,
so
that
we
go
into
chaos
con
with
some
degree
of
sort
of
common
ground
that
the
group
is
working
from.
I
would
say
that
thus
far,
hey,
sis
and
I
are
providing
the
cohesion
and
we're
working
to
integrate
the
work
of
Daniel
German
and
a
lot
of
other
really
insightful
contributors
in
that
in
that
flow,
okay,
I
think
it's.
It's
really
kind
of
a
group
formation
process
formation,
okay,.
A
Cool
great,
so
I
think
that
one
thing
that
I'll
I
kind
of
asked
both
the
DNI
and
GMB
work
groups
to
think
about
is,
as
you
have
forked,
the
metrics
repository
to
think
about
the
growth
maturity
and
decline.
Metrics
I
think
those
metrics
are
sitting
duplicate
now
inside
of
the
work
group.
Is
that
correct?
C
So
what
we
actually
what's
actually
been
there's
a
little
bit
of
so
I.
The
way
that
the
working
groups
are
operating
right
now
is
I,
don't
think
they
really
created
Forks
I
think
what
they've
done
is
taken
the
content
of
the
metrics
repository
and
put
an
initial
version
of
that
content
into
a
completely
separate
repository
that
then
will
need
to
be
I
think
manually
integrated
back
into
the
main
metrics
repository.
C
I
I
B
A
So,
okay,
so
maybe
we
won't
solve
this
problem
now,
yeah,
no,
not
today
and
brings
up
a
no
I
think
you
bring
up
a
really
good
point,
then
I
think
maybe
the
takeaway
would
be
for
the
working
groups
just
to
be
very
mindful
of
of
this,
so
that
we
don't
have
a
lot
of
duplicate
work
occurring
across
the
chaos
organization
and
so
that
you
can
help
reduce
the
manual
effort
that
may
come
later
pushing
a
button.
That's
way
better
than
doing
a
lot
of
manual
copy
and
pasting.
So.
A
F
Well,
hello,
everyone
I
don't
so
our
initial
approach
was
as
the
diversity
inclusion
working
group
was
that
it
burned
from
the
initial
set
of
metrics
that
we
had
in
the
diversity
branch
of
the
metrics.
It
was
quite
easy
to
start
from
scratch.
Let's
say:
I'm
the
scratch
we
have
was
the
panel
stacked
in
the
report,
so
how
I
saw
all
of
these
well,
my
idea
was:
we
have
a
set
of
gold
questionnaire,
metrics
that
we
have
in
the
main
repository,
and
then
it
happens
that
we
are
producing
some
more
in
the
in
the
working
group.
F
So
the
idea
is
once
we
feel
comfortable
about
the
metrics
that
we
have
in
the
working
group.
Then
we
start
moving
things
to
the
main
repository.
So
that's
basically
the
idea,
but
at
least
I
have-
and
that
was
my
my
my
first
idea-
I
wasn't
having
this
these
working
groups
and
the
and
the
main
repository
said
this.
We
we
haven't.
We
have
not
moved
any
metric
to
the
main
repository
reason
for
this,
because
you
still
don't
have
don't
feel
comfortable
with
the
metrics
that
we
have.
So
we
feel
comfortable
with
the
goals
that
we
have.
F
We
have
defined,
I
would
say,
and
please
care
correct
me
and
wrong
and
Prime
another
sniper
around.
But
I
would
say:
that's
that's
the
status
right
now,
so
we
have
to
find
a
set
of
goals
that
we
all
feel
comfortable
with.
Now
we
have
to
work
a
bit
more
on
the
questions
and
images
and
then
once
we
have
those
metrics
and
questions,
the
idea
is
to
start
moving
things
to
the
main
repository.
So
then
we
have
rather,
let's
a
discussion
with
all
of
the
people
in
the
main
repository.
B
After
that,
during
the
last
workgroup
meeting
last
week,
which
I
know
you
couldn't
make
Daniel,
there
was
confusion
about
the
goals
actually,
okay,
so
we
need
this
something
the
workgroup
has
to
do
is
document
the
Gould's
better
and
write
down
what
they
are,
how
they're
structured,
why
we
chose
these
goals
because
it's
not
not
apparent
Chapman
and
we
had
people
join
from
the
open
source
leadership
summit.
That
was
what
two
three
weeks
ago.
So
they
had
come
because
they
had
heard
of
our
work
and
there
was
a
little
confusion.
F
Then
they
were
strong,
my
perception
that
I
felt
that
we
have
a
listicle,
so
we
have
we
need
to
keep
working
there.
The
problem
made
my
main
concern,
but
the
problem
is
that
we
can
keep
this
cuts
in
about
this
forever.
So
I
didn't
know
when
to
have
the
Tate
releases
or
to
deliver
thing
and
perhaps
would
be
good
well
something
that
we
already
tried
in
some
other
areas.
Try
to
have
some
releases
of
matrix
I
know
we.
E
C
Right
so
I
think
any
Ben's
point
about
really
trying
to
keep
keep
these
in
the
same
repository
is
probably
the
most
that's
practical
and
I
think
a
real
important
thing
to
think
about
and
then
separate
from
that
I
think
the
working
groups
need
to
probably
maintain
you
know
their
own
processes
to
solve
the
problems.
If
they're
trying
to
solve.
C
A
Agree,
I
think
maybe
the
two
takeaways
I
would
have
is
that
how
the
working
groups
represent
their
relevant
metrics
kind
of
this
layered
approach.
That
Gary
was
talking
about.
I
think
it
would
be
nice
if
we
could
get
consistency
in
that
regard
at
least
structures
and
how
these
things
are
represented.
Oh
I,
don't
want
I,
don't
think
it's
a
good
idea
to
have
one
workgroup
kind
of
representing
things
in
one
way
and
then
a
different
work
group
representing
things
in
two
different
way.
C
Heard
you
conceptually
and
I
think
yeah
I
do
agree
and
it
would
be
good
at.
Maybe
there
was
a
little
bit
of
all
I
think
that
I'd
look
briefly
at
the
pull
request
that
Kevin
made,
while
talking
here
and
I,
think
it
looks
helpful
and
like
it
ants
the
growth
maturity
decline,
working
group
and
if
it's
consistent
with
D&I
and
I
think
we're
getting
where
I
think
I
don't
see
anybody
objecting
to
that.
Okay,.
F
A
A
F
A
J
H
A
J
Yeah
this
morning,
where
we're
starting
to
work
on
and
then
you'll
keep
me
honest
here
and
in
New,
York
and
others
we're
starting
to
work
on
the
next
level.
I
think
Emma
worked
on
one
of
them
right
and
in
terms
of
the
metric
categories
and
then
drilling
those
down
into
what
what
we
intend
or
what
we
mean
by
those
different
categories.
So
that's
one
of
the
things
that
we're
working
on
is
I
think
fairly
quickly.
J
Here,
when
you
start
to
each
of
us
and
I
think
we
left
our
last
call
actually
where
we
talked
about
maybe
finding
different
folks
or
different
folks,
stepping
up
to
em
to
take
each
one
of
those
on
and
and
work
through
them
and
put
some
detail
underneath
them
and
I,
and
then
too
I
come
back
together
and
discuss
those
the
details
underneath
each
of
the
categories.
Well,.
J
We
actually
in
if
I'm,
remembering
quickly.
We
in
our
last
call
brought
into
there
seem
to
be
some
overlap
between
the
different
categories,
so
you've
got
sort
of
a
main
categories
event
and
then-
and
then
you
may
have
some
but
I
almost
would
almost
call
mid-level
where
you've
got
a
little
bit
of
dimension
underneath
that
category.
But
we
really
haven't
detailed
it
out
too
much
at
this
point.
Okay,.
B
B
E
B
A
J
B
We
had
within
was
it
events,
no
project
places
within
project
places,
we
have
actual
places
like
documentation
and
then
we
have
sentiment
which
is
not
a
place
itself,
which
is
a
way
to
understand
places
and
we
can
apply
sentiment
to
all
other
places
as
well.
This
is
where
the
vertical
and
horizontal
idea
comes
from.
K
A
B
A
H
E
A
F
G
B
C
C
A
C
A
C
A
B
Since
we
was
it
since
we
last
met,
we
submitted
proposal
or
mo
submitted
a
proposal
to
mas
fast,
we
have
a
proposal
or
two
at
the
open
source
summit
Europe
that
we're
waiting
on.
We
are
looking
forward
to
the
chaos
con
and
started
working
on
and
he
called
you.
You
started
working
on
the
panel
discussion.
Getting
that.
F
A
A
J
Yeah
yeah,
so
we
had
we're
working
on
the
the
next
release
of
the
OpenStack
diversity
report
would
be
with
OpenStack
summit
in
Berlin,
okay,
I
believe
that's
November
I'd
have
to
look
at
that
again
yeah.
If
anyone,
if
any
of
you
are
interested
in
working
on
that
it
would
be
great
to
have
your
input
on
that.
J
We
had
talked
about
this
next
report,
and-
and
this
is
just
in
shock
right
now
and
but
if
any
of
you
have
any
input
and
would
like
to
see
something
in
the
report,
let
us
know
the
what
we
had
talked
about
was
taking
the
top
five
projects,
where
diversity
shines
brightly.
Where
things
are
going
well
and
the
equally
important
the
bottom,
five
and
I
don't
know
I'd
just
I,
don't
know
how
we
got
to
five,
but
it's
pretty
flies
without
you,
but
essentially
digging
into
those
communities
or
sub
communities
and.
J
F
In
just
to
let
something
else
here
in
terms
of
having
a
process
to
retrieve
feedback,
we
don't
have
that
process
and
if
an
official
process,
the
idea
is
that
we
go
through
either
the
working
group
or
basically
you
Nicole
and
others
talking
about
the
report
and
then
bring
in
feedback
from
the
community.
So
it's
time
we
go
to
openness,
tax
time,
it's
basically
we
we
talk
to
people,
we
try
to
retrieve
feedback
and
say
hey.
This
is
what
we
have.
F
So
we
try
to
have
the
community
on
board
in
somehow
and
then
trying
to
focus
on
some
specific
people
that
have
helped
after
a
while.
So
as
Nicole
mentioned,
so
we
have
Victoria
Allison
and
some
others,
so
they
are
bringing
some
really
good
feedback
in
terms
of
the
quality
of
the
data
that
we
are
producing
and
the
area
that
we
should
be
looking
at.
So
this
is
the
process
we
have
right
now.
A
Question
and
the
on
the
with
respect
to
the
report.
Are
you
also
publishing
ways
that
other
projects
could
produce
a
similar
report?
I
mean
this
is
one
of
the
kind
of
the
key
things
we're
gonna
need
to
think
about
longer
term
with
the
Kaos
project.
Maybe
at
the
highest
level,
is
not
just
thinking
through
what
the
metrics
are
and
how
to
categorize
them,
but
how
to
assist
people
in
producing
this
relevant
information
and
then
kind
of
what
Nicole
was
pointing
to
maybe
how
to
start
putting
that
data
as
well.
D
F
We
were
discussion
about
that
in
in
the
group
how
to
help
third
parties
to
reproduce
or
produce
any
analysis
for
their
communities.
The
point
so
far,
I
would
say
that
we
don't
have
an
answer.
Okay,
we
are
still
guessing
if
we
should
go
for
some
template
or
some
specific
software
or
just
focus
on
each
of
the
categories
has
Nicole
mentioned
that
the
goals
that
we
have
defined
and
say:
okay,
you
want
analyze
this
goal.
You
have
to
follow
this
process
and
then.
D
F
H
F
J
G
J
A
It's
actually,
you
have
a
method,
so
say:
OpenStack
produces
this
report,
and
it's
read
by
people
in
kubernetes,
community
or
hyper
ledger,
and
they're
like
this
is
great.
I
would
love
to
be
able
to
produce
a
DNA
report
for
our
project
as
well,
but
then
I
think
that
the
next
questions
are
going
to
be.
How
do
I
go
about
doing
this?
How
do
I
actually
generate
this
data,
not
the
metrics
themselves,
as
you
pointed
out,
but
the
actual
methods
or
processes
by
which
to
capture
and
analyze
this
data
and
make
sense
of
it.
F
J
I,
you
know:
we've
we've
come
this
far.
We've
learned
these
things.
We
think
we
now
need
to
do
this
right,
but
even
getting
to
the
quantitative
person
qualitative.
And
how
do
we
do
that?
I
think
we
haven't
figured
that
piece
out
yet
like
how
do
we
go
and
dive
into
these
the
top
five
and
the
bottom
side?
We
think
that
would
be
a
valuable
exercise.
We
think
we
would
learn
from
that
and
we
think
that
what
we
learn
could
be
applied.
J
A
H
F
So
in
the
in
the
in
the
so
the
whole
story
here
is
okay.
We
are
producing
this
open
a
stock
in
the
report
and
then
at
Kaos,
let's
say
appeared,
and
we
said,
maybe
it
makes
sense
to
have
this
in
in
the
communities
of
other
communities
can
reproduce
analysis
so
astray
I
mentioned
yeah.
Part
of
the
method
is
in
the
document.
Part
of
the
matrix
discussion
and
definition
is
in
the
document,
and
the
software
is
in
is
publicly
available
in
in
in
your
personal
repository.
But
then
I
move
this
to
chaos.
F
So
then
it
happened
that
when
we
have
started
to
work
on
this,
we
are
started
to
attract
people
to
the
working
group
and
then
basically,
the
four
main
areas
that
we
were
defined
in
OpenStack
were
not
enough.
So
we
said
okay,
then
we
need
to
start
a
discussion
about
the
codes
and
then
this
is
what
we
are
basically.
So
we
are
now
defining
the
goals
because
it
seems
that
we
still
have
to.
A
A
F
But
a
question
here
and
perhaps
for
the
world
for
your
next
meeting
would
be,
if
you
think,
from
the
board
that
we
need
to
deliver
things.
Perhaps
one
of
the
things
that
you
you
may
you
may
foster
is
to
have
this
kind
of
deliverables
after
six
months
or
a
year,
so
others
can
use
things
whatever
the
stage
of
the
different
working
groups
is,
but
they
can
use
and
reuse
the
the
things
we
are
pretty
using,
but
that
may
help
to
to
have
system.
J
B
A
A
A
B
This
would
be
a
good
starting
point
for
our
next
DNA
group
meeting,
where
we
can
then
discuss
how
we
get
the
method
from
the
OpenStack
report
into
our
structure
and
into
our
repository.
How
we
can
capture
that
I
think
that's
a
good
starting
point,
and
we
can.
We
cannot
worry
about
the
other
subcategories
quite
yet
and
just
sort
of.
But
what
we
have
here
I
think
that's
a
good
way
to
move
forward.
That.
F
D
F
Having
specifically
the
metrics
or
the
methods
or
them
or
the
things
that
we
are
using
just
there,
but
what
means
this
is.
This
is
what
we
think
this
is
what
with
is,
and
then
this
is
what
we
do
in
develop
and
in
the
repository-
and
this
is,
this
is
probably
not
the
way
to
proceed
so
mr.
West,
what
was
the
problem?
Oh,
let's
say
that
I
I
didn't
want
at
least
personally
and
just
my
my
opinion.
I
didn't
want
to
put
everything
from
the
open
extract
in
the
report.
F
F
A
J
A
C
C
A
C
A
It
for
me
is
easier
for
everybody
very
hopeful,
so
I.
This
is
really
helpful.
Everybody
thank
you.
So
much
for
the
work
group
updates
and
thinking
through
kind
of
these
process
issues
I
think
it's
important
that
we
continue
to
talk
through
these
a
lot
of
moving
parts
in
this
project.
So
in
the
remaining
ten
minutes
we
have
the
chaos.
A
A
A
Patient
very
exciting,
so
we're
putting
together
I
got
in
touch
with
University
Communications
here
at
the
UN,
oh
and
they're
doing
a
professional
video
on
they're
gonna,
put
together
a
professional
video
on
chaos
like
a
two
minute
overview
of
the
project,
and
so
some
of
you
might
be
asked
for
quotes
or
there
might
be
pictures
taken,
tear
it
out
with
everybody
before
we
go
public.
But
yes,
we're
doing
some.
A
D
K
Yeah,
we
should
probably
sync
up
as
a
team
because
we
haven't,
we
haven't
really
done
that
in
a
while,
once
we
selected
the
talks,
so
we
haven't
went
talked
about
things
like
who's
gonna,
be
there
when
we
open
up
registration
who's
going
to
out
the
list
of
people
and
I
think
there
are
a
lot
of
little
logistical
details
that
we
haven't
really
talked
about.
Yeah.
K
D
D
D
I
I
A
I
D
I'm
tied
to
a
members
area
mint
regional
agreement
in
this
and
I
remember,
the
idea
was
that
we
were
I
mean
calcium
was
free.
We
were
going
to
be
included,
I'm
interpreting.
The
message
were
with
the
climate
that
about
this
month
ago
we
were
going
to
be
included
into
the
registration
for
OSS,
so
that
cows
con
is
there.
But
there
is
nothing
about
the
speakers
so,
but
maybe
we
can
ask
anyway,
so
I
agree
with
you
Matt.
Let's
ask
yes,
my.
A
A
C
E
E
H
D
Like
that
yeah
we
can,
we
can
try
to
get
to
rely
on
the
same
hotel
that
other
years,
if
we
find
on
the
spot
great
and
the
problem
is
that
find
in
a
space
in
the
university
is
very,
very
difficult
and
on
a
Friday
is
more
even
more
difficult
because
there
are
classes
or
basically,
we
need
to
rent
a
space,
some
work
and
we
can
rely
on
the
holder.
Look,
we
have
a
sponsor
in
a
again
I
can
talk
to
Peter
yeah.
We
can
see
whether
there
is
some
more
money
you.
K
D
A
A
D
F
D
K
A
K
H
K
A
A
H
A
A
H
A
A
A
But
we
do
have,
we
do
have
a
new
email
that
is
just
chaos
at
lists
and
right
now,
all
of
our
conversations
occur
through
this.
The
email
which
is
OSS
Health
metrics
at
lists,
which
is
not
the
best
name.
So
we
have
a
better
name.
The
it
gives
me
a
headache
to
think
about
moving
an
email
list
from
one
location
to
another.
So
and
there's
like
a
hundred
there's
like
so
many
BOTS
in
the
list
that
I
can't
manually
go
through
the
current
OSS
Health
metrics
list
and
manually
move
people
over.