►
From YouTube: CHAOSS.Community.September.10.2019
Description
CHAOSS.Community.September.10.2019
A
So
I
am
now
officially
recording
hi
everybody
and
today's
September
10th-
and
this
is
the
KSR
weekly
community
call-
and
this
is
kind
of
open-
must
of
a
less
formal
kind
of
call.
So
if
people
have
things
they
want
to
bring
forward,
now
would
be
a
great
time
to
do
it.
I
guess
one
of
the
things
I
have
a
few
things
as
always,
but
does
anybody
have
anything
on
their
mind
that
they'd
like
to
bring
forward
work
that
they're
doing
whatever
it
might
be?
B
B
Next
week
is
the
inner
source
comment
is
taking
place
in
bulk
in
your
area.
I
could
accept
the
torque
what
we
can
learn
from
chaos
at
the
inner
source
Commons.
So
this
is
the
talk
about.
I
would
like
to
say
that
this
is
happening.
I
still
have
to
work
on
slides,
but
it's
happening.
Can
you
talk
a
little
bit
about
that?
The
idea
is
so
matrix.
Oh,
go
ahead.
Sorry
I
just.
A
B
So
inner
source
just
to
be
sure
that
we
are
all
aligned.
So
this
is
about
bringing
in
open
source
methodologies
or
way
of
working
in
two
large
corporations,
the
graphically
distributed,
etc,
etc.
So
big
company
has
realized
that
well
they
are,
they
have
they
have
similar
structure
as
open
source,
but
they
don't
have
developed,
processing,
age
or
as
happy
as
in
open
source
communities,
and
they
are
not
producing
high
quality
code.
B
So
the
point
is,
it
seems
that
they
can
learn
from
the
open
source
world,
but
then
I've
been
involved
in
the
dinosaurs
comment
for
the
last
three
four
years
right
now
and
one
of
the
hot
topics
once
and
again,
metrics.
The
point
is
that
the
metrics
that
the
north
corporations
are
trying
to
measure
are
kind
of
pretty
similar
I
mean
they
are
using
a
pretty
similar
infrastructure
set
up.
It
had
calm.
It
happened
the
price
in
instead
of
Katella
community
ratio,
and
perhaps
there
isn't
good
luck.
Community
ratio
not
keep
calm
JIRA
at
last.
B
In
a
cycle
of
this
thing,
so
having
basically
the
same
tooling,
you
can
go
and
say
what
I
can
produce
certain
metrics.
The
point
is
that
what
large
corporations
are
now
learning
from
is,
for
instance,
how
to
collaborate,
how
to
produce
code
in
an
open
environment,
how
to
be
transparent,
how
to
build
community,
how
to
do
things
that
we
are
assuming
from
the
open
source
ecosystem
so
and
for
this
to
track
the
success
of
the
river
source
initiative,
one
of
the
things
they
need
about
apart
from
certainty
or
tooling,
or
processes
or
metrics.
B
So
a
way
we
are
working
in
matrix
I
think
is
interesting,
because
it
happens
that
a
lot
of
the
opening
or
most
of
organizations
they
are
trying
to
have
their
own
thing
or
they
are
trying
to
run
their
own
thing
without
having
a
common
B.
You
are
the
matrix
that
they
are
trying
to
retrieve
or
to
achieve
so
having
the
specific
lessons
learned
that
I
think
is
quite
useful.
Is
this
idea
of
having
kind
of
a
release
of
metrics
and
say
hey?
This
is
what
we
have.
B
A
B
So
the
very
first
steps
they
are
using
the
matrix
for
is
to
measure
things
collaboration.
So
you
have
people
from
the
different
business
units
participating
across
the
organization,
so
they
want
to
see
that
collaboration
is
happening,
and
that
means
people
from
different
business
units
cover
it
in
the
same
depository
newcomers
retention
rate,
this
kind
of
things,
things
that
in
open-source
is
kind
of
a.cian
right.
So
this
is
happening.
A
C
B
Today
they
don't
realize
in
some
cases,
unless
you
open
the
discussion
that
when
you
are
measuring
a
commit,
it's
not
the
same
coming
if
this
is
done
by
a
bot
or
if
this
is
done
in
a
branch
or
if
this
is
done
in
master
or
if
this
is
done
in
a
peer
review
process
and
on
how
to
count
all
of
these
comets.
It's
something
that
you
need
to
be
aware
of
and
documented
somehow.
So
this
is
the
way
I
am
trying
to
bring
into
the
discussion
of
the
inner
source
commands.
B
A
I,
do
you
think
there's
anything?
This
is
all
super
interesting.
Do
you
think,
there's
anything
from
the
inner
source
common
side
of
things
that
would
inform
chaos.
So
a
lot
of
what
you've
been
talking
about
this,
bringing
maybe
a
more
refined
way
of
thinking
about
metrics
and
what
those
metrics
can
mean
from
the
work
that
obviously
is
being
done
in
Chrome
or
lab
and
chaos
to
the
audience
at
dinner
source.
Do
you
think
it
goes
the
other
way
as
well.
B
Definitely
because
one
of
the
things
at
least
I'm
learning
from
large
corporations
is
how
to
have
metrics
that
are
related
to
money
to
budget,
and
this
is
kind
of
the
world.
We
are
developing
in
chaos
in
some
of
the
working
groups,
so
bringing
this
conversation
into
chaos
is
definitely
worth
and
some
others
that
again
I
say,
as
I
mentioned
before,
we
assume
in
the
in
the
open
source
world
that,
but
perhaps
we
can
help
with
us
this
concept
of
collaboration
or
some
other
things
or
transparency.
How
do
you
measure
transparency?
D
What
I,
what
I
want
to
say
is
one
of
the
discussions
that
we
have
quite
lot
really
centers
around
the
idea
of
consortium
and
partnerships,
that
is,
corporate
development
activities
that
are
done.
You
know
with
it
with
a
group
of
partners
and
and
how
do
you
ensure
sort
of
equitable?
You
know
distribution
of
contributions
and
value,
so
I'll
just
bring
that
up
as
maybe
something
to
something
to
look
for
in
your
discussions
at
that
conference.
I.
D
D
Economic
professors,
industry,
analysts,
people
of
that
profile
and
I've
actually
made
started
making
some
progress.
I've
got
a
stock
analyst
that
I've
been
talking
to
I
want
to
reach
out
to
Yana
when
the
time
is
right,
it
might
be
Daniel
that
there
are
people
at
this
inner
source
conference
who
fit
that
profile,
and
if
so,
we
want
to
chat
with
him.
A
One
of
the
working
group
meetings
Andy,
you
can
totally
correct
me
if
I'm
wrong,
but
that
would
attend
the
working
group
meetings
twice
a
year
just
to
kind
of
get
a
sense
of
what
the
metrics
are
that
are
being
deployed,
how
those
metrics
are
being
deployed
in
tooling
and
just
give
their
feedback
on
and
what
they
think.
The
direction
of
the
working
group
is
just
advisory,
not
certainly
not
steering
the
the
work
officially
by
any
means
said
about
right.
Andy,.
D
That's
what
I
have
in
mind
the
involvement
would
be
very
lightweight
and
as
much
as
anything,
it
would
be
a
way
for
us
to
get
some
validation
that
the
things
that
we
are
talking
about
here
matter
to
you
know
folks,
in
the
field,
it
would
be
an
opportunity
for
networking,
perhaps
and
and
just
to
almost
like
a
kind
of
like
a
sensory
organ
to
you
know,
to
ask
for
some
feedback
beyond
you
know,
beyond
our
own
expertise,.
E
B
D
I'll
Daniel,
if
you
could
please
post
your
email
on
the
chat
and
then
I'll,
send
you
an
email
and
actually
I'll
copy
everybody,
yes
with
a
one
pager
with
with
the
profile
of
what
we're
looking
for
and,
and
maybe
some
some
notes
on.
You
know
what
this
group
is
intended
to
do,
what
the
intended
involvement
is
and
what
the
benefits
would
be
for.
Participants
can.
D
A
D
And,
and
by
the
way,
this
is
on
my
to-do
list
anyway,
because
because
other
people
have
been
asking
me
for
it,
so
yes
I
will
absolutely
do
that.
I
know
one
pager
be
perfect.
Yeah.
B
Another
way
of
doing
these
I
mean
not
for
this
time,
but
for
the
next
one
is
to
the
to
come.
If
that's
possible
to
the
in
interest
comment
or
or
it
can
be
kind
of
the
bridge
between
both
communities
in
some
house
or
anything.
You
have
questions.
I
brought
those
questions
there
and
then
the
other
way
around
I
bring
questions
here,
at
least
if.
A
A
A
Very
much
okay,
so
I
had
a
I
had
one
I'll
say
it.
I
am
a
lot
of.
You
know
that
I'm
always
very
interested
in
making
sure
that
the
work
that's
being
done
in
the
metrics
working
groups
is
finding
a
home
whether
it's
in
in
software,
so
whether
it's
in
the
work
that
is
being
done
around
grimore
lab
or
the
work
that's
being
done
around
a
ger,
so
I
think
continuing
to
work
to
map.
The
metrics
that
were
part
of
the
release
to
the
software
is
something
that
I
I
would
love
to
see.
A
We
can
actually
just
articulate
things
that
already
exist.
It
should
be
big,
I.
Think
in
the
first
release
we
were
articulating
things
that
didn't
exist
in
software
it
at
certain
times
it
made
the
work
a
little
bit
a
little
bit
long,
sometimes
but
I
think
if
we
can
rely
on
what's
already
deployed
in
software
that
might
speed
the
process
up
a
little
bit.
Sean
I
know
you're
doing
this
with
risk
mm-hmm
that
there
are
things
that
are
currently
in
augur.
That
would
be
contributions
to
the
risk
working
group.
A
A
C
Right
and
then
yeah
I
mean
I
think
it's
likely
that
Remora
an
augur
have
similar
metrics
defined
in
this.
So
then
that
can
become
a
really
good
conversation
on
that
group
about
what
what
are
the
parameters
and
filters
and
what
are
the
core
parts
of
the
metric
yeah
I
think
those
are
all
great
I
think
this
is
a
good
path
go
down
so
that
it
becomes
more
concrete
to
the
consumers
of
chaos.
Metrics.
A
A
Okay,
any
comments
on
that
I'll
talk
with
the
working
groups
on
these
things
too,
but
I
just
want
to
put
this
out
here
in
the
community
call
okay,
so
yesterday,
I
remember
which
call
it
was,
but
I
have
a
so.
The
other
part
of
part
of
this
is
I
would
really
love
to
see
the
metrics
and
software
kind
of
this
combination
of
both
of
them
being
deployed
in
in
white
papers
or
deployed
in
reports
quite
similar
to
the
work
that
grimore
lab
has
done
with
OpenStack
around
the
gender
report.
Is
it's
fantastic
right?
A
A
So
it's
nice
because
it
at
this
point
now.
The
report
has
some
history
and
you
know
the
first
report
doesn't
have
a
lot
of
contextual
meaning,
but
over
the
course
of
several
years
it
starts
to
mean
something
for
OpenStack,
which
is
really
great.
I
would
like
to
propose
that
we
identify
an
open
source
community
and
prefer
to
create
a
report
based
on
the
chaos
metrics
that
we
have
released
and
I
would
actually
work
to
shepherd
that
so
what
came
up
was
I.
Don't.
B
A
Kate's
on
the
call
right
now,
but
what
came
up
was
like
the
Zephyr
community
and
I
only
mentioned
that,
because
Kate's
on
the
board
mm
Kate
is
involved
in
the
Zephyr
project
but,
for
example,
reaching
out
to
the
Zephyr
community
and
seeing
if
they
would
like
a
yearly
report
built
on
on
the
chaos
metrics.
Using
the
chaos
metrics
across
all
working
groups
to
provide
insight
on
the
community.
And
it's
something
that
we
would
do
as
a
community
and
again.
I
would
take
that
on.
A
C
A
A
F
F
B
B
B
A
Think
that's
really
smart
and
I
think
we're
gonna
have
to
do
the
work.
Meaning
me
I'll
tell
take
this
on
as
one
of
my
action
items
for
the
year
and
it
would
be.
The
hope
would
be
is
that
it
would
be
kind
of
a
chaos,
slash
community
branded,
whatever
that
community
might
be
flyer
or
a
report
on
the
brings
a
sales
for
it
and
I
really
honestly
like
to
stick
with
the
chaos
metrics
that
were
part
of
the
release.
C
C
They
we
pick
a
few
communities.
One
of
the
things
that
that
we
can
do
that
will
be
helpful,
is
to
talk
to
that
community
first
about
what
what
is
the
context
of
the
things
that
they're
interested
in.
So
we
have
a
number
of
chaos,
metrics
that
are
released,
the
number
that
will
be
released
again
here
in
a
few
months,
yeah.
B
C
Subject
so
doing
reports
for
say
three
communities
gives
us
an
opportunity
to
think
about.
Okay.
How
do
we
put
all
of
these
metrics
in
context
for
specific
mm-hmm
communities
so
that
it's
you
know,
here's
your
metrics
boom?
It's
not
that
it's
more
of
a
discussion
and
a
refinement
of
what
the
report
looks
like
based
on
the
questions
that
are
most
salient
to
that
community
at
that
time.
Okay,
so
then
it
then
there's
kind
of
a
context
around
other
metrics
yep.
A
So
the
idea
would
be
as
saying
just
hear
me
out
as
I
walk
through
this,
but
here
are
all
the
chaos
metrics.
They
all
may
not
be
selling
salient
to
your
project.
So
why
don't
we
talk
through
the
ones
that
are
most
meaningful
to
you
with
evolution
or
risk
or
value
or
whatever,
that
might
be,
and
producing
a
smaller
subset
of
the
results
from
those
metrics,
because
those
are
the
ones
that
are
insightful
for
that
particular
project.
Is
that
right.
C
E
B
B
G
E
A
E
D
D
D
It
would
be
a
way
to
generate
awareness
and-
and
maybe
it
would
be
a
way
for
people
to
discover
you
know
the
chaos
community,
so
it
could
be
like
the
most
effective,
the
most
effective
open-source
project
or
the
open-source
project
that
has
most
contributors
or
the
fastest
growing
open-source
project
or
or
something
like
that,
just
one
or
two
metrics,
very
simple
that
anybody
could
understand
like
in
ten
seconds.
Is
it
like
the
velocity
stuff
could
be
the
project
velocity
it
could
be,
it
could
be.
You
know
it
would
just
be
a
metric.
D
You
know
like,
for
example,
there's
a
lot
of
surveys
around
the
the
most
popular
programming
language,
and
you
know
it's
something
that
that's
easy
for
people
to
understand.
There's
there's
like
people
pay
attention
to.
You
know
every
year
when
the
survey
comes
out
which
languages
go
up
in
the
stack
in
which
languages
go
down
in
the
stack
and
they
have
debate
about
it
and
it's
it's
a
way
for
you
know
it's
it's
it's
kind
of
this,
this
widespread
thing
that
goes
out
and
I
think
in
a
similar
way.
D
You
know
we
might
be
able
to
brainstorm
a
a
single
chaos
metric.
You
know
we
would
call
it
like
the
best
open-source
project
in
the
world,
there's
something
like
that.
It
could
even
be
a
little
bit
controversial
that
might
be
okay,
like
click
bTW,
it
could
be
a
little
bit,
click
baby
or
a
little
bit
controversial,
and
we
could
just
say:
hey.
D
You
know
we're
the
worldwide
experts
and
measuring
open-source
we're
telling
you
this
is
the
best
open-source
project
in
the
world,
or
this
is
the
one
that
is,
you
know
the
best
and
let
people
debate
it
and
let
people
discuss
it
and
and
and
that
would
be
a
way
I,
think
of
generating
attention
and
and
so
on.
So
just
an
idea,
sure
thing:
I'll.
B
Being
shy
so
even
involved
well,
I
was
involved
a
lot
of
years
ago
in
some
European
research
and
development
projects,
and
one
of
them
were
related
to
quality
models.
So
we
can
need
to
use
the
very
gain
in
the
world
good
or
bad.
But
the
point
is
that,
after
measuring
hundreds
of
prey
at
that
point
in
time,
we
realized
that
there
were
brilliant
that
were
far
from
the
average,
and
this
is
what
we
were
using.
B
So
you
have
some
a
big
amount
of
projects
kind
of
an
average
around
certain
metrics,
and
then
they
were
riots
that
were
far
from
that
average
right
to
left
to
them.
We
can
say
that
you
are
far
from
the
average
of
the
brigade's,
and
then
we
are
not
saying
this
is
good
or
bad
that
you
are
far.
It
is
a
bit
different,
more
diplomatic
way.
A
H
H
H
A
A
C
A
A
little
bit
easier
and
things
like
kubernetes
or
or
hyper
ledger,
they're,
just
or
the
kernel,
or
something
like
that
they're.
Just
so
big
that
we
may
end
up
I,
don't
know
it
may
just
be
really
really
hard,
at
least
at
least
as
a
first
pilot
past.
That
was
the
thought.
I
don't
know.
People
have
thoughts
on
that
as
well.
A
Are
this
was
based
on
the
conversation
about
that
we
had
that
kind
of
sprung
up
in
DNI
about
trying
to
identify
an
organization
or
a
project
that
we
could
do
a
health
report
for
our
health
fire.
For
so
that's
what
this
was
so
all
right.
This
is
good.
Any
other
thoughts
on
Matt
for
the
annual
report.
Flyer
like
I,
said
I'll,
take
the
lead
on
that
trying
to
identify
projects
and
trying
to
coordinate
that
I
personally
is
very
interesting
to
me.
A
A
G
I
want
to
highlight
one
one
thing
that
we
are
doing
with
the
DNI
group
and
that
is
related
to
and
you
everyone
who
was
at
Kaos
con
saw
gris-gris
of
us
from
the
Patchi
Software
Foundation
talk
about
the
the
work
that
she's
doing
with
regards
to
diversity
and
inclusion
in
the
Apache
Software
Foundation,
and
she
wants
to
get
a
overview
of
what
is
happening
right
now,
where
I'll
be
right
now,
with
in
terms
of
diversity,
inclusion
and
weirdo
figuring.
That
out
is
doing
a
survey.
G
The
last
survey,
the
Apache
Software
Foundation,
did
was
in
2016,
so
three
years
later,
now
is
time
to
redo
that
again
and
in
the
conversations
we
have
been
having,
she
is
very
interested
in
leveraging
the
work
that
the
chaos,
diversity
and
inclusion
working
group
has
had,
and
we
in
using
the
the
questions,
the
survey
items.
So
not
the
questions
that
we
think
of
in
chaos
terms,
but
the
questions
inside
of
the
metric
and
for
helping
that
I
post
a
link
here
in
the
Google
Doc.
G
G
The
next
step
is
once
the
ASF
develops
its
survey
tool
and
collects
the
data
and
has
insight
the
goal
is
to
feed
that
back
into
the
diversity
inclusion
working
group
as
well,
so
that
that's
my
my
view
of
things,
I
hope
you
can
help
me
ace
up
here
as
chaos
and
I
hope
that
putting
pressure
on
the
metrics,
as
you
always
call
it
Matt,
we
can
improve
what
we
currently
have
in
the
DNI
work
cool.
Thank.
A
You
Bert
thank
you
for
doing
that.
I
had
also
thought
about,
possibly
when
the
survey
is
completed,
reaching
out
to
folks
at
the
LF
to
potentially
run
the
survey
Linux
Foundation
projects
I
haven't
done
anything
on
that.
Yet
I
don't
know
what
that
would
look
like
and
I.
Don't
know
if,
if
BASF
I
don't
know,
I,
don't
I,
don't
know
if
there's
a
problem
to
do
that
or
if
you
have
thoughts
on
that
anybody,
Georg
I.
G
G
G
G
C
C
We
got
a
paper
out
to
more
edited,
so
I
haven't
gotten
to
that
and
I
don't
know
if
it's
useful
at
this
point
to
get
to
it.
We
have
an
infinitely
easier
version
of
auger
to
build,
as
we
did
in
RF.
We
showed
in
our
weekly
chat
last
week,
so
I
think
it's
still
valuable
if
I
get
either
one
pager
or
is.
Is
that
train
kind
of
out
of
the
station?
The.
C
G
A
F
G
On
thank
fliers
yeah,
so
the
one
pager
is
given
to
the
participant
at
the
start
of
the
hackathon.
Look
at
it
say.
Yes,
this
is
project
I
want
to
work
with
for
the
next
and
27
hours
so
how
to
mark,
and
then
it
would
be
good
to
have
people
on
our
smack
channel.
Irc
I,
don't
actually
know
where
we
will
meet
with
these
students
to
answer
questions
and
provide
help
throughout
the
whole
hackathon.
Thank.
C
You
do
they
have
a
slight
channel
that
they're
using
that
they'll
create
channels
within
for
us
I.
Don't
work
because
I
have
public
support
slack
for
augur,
but
if
they
have
a
they
have
a
channel
focused
on
the
event,
then
that
might
be
easier
for
the
participants.
I,
don't
I
think
we
just
need
to
know.
If
we're
listening
to
our
channel
or
there's
another
slack
or
we
should
be.
You
know,
I.