►
From YouTube: CHAOSS.Community.September.1.2020
Description
CHAOSS.Community.September.1.2020
A
Hi,
welcome
to
the
september
1st
super
special
monthly
edition
of
our
community
call.
I
know
you're
all
super
excited
because
I
am
as
well.
So
I'm
really
glad
to
see
everyone
here
welcome
welcome
if
you
have
not
done
so.
Please
put
your
name
on
the
attendees
list
in
the
meeting
minutes,
which
I
can
plop
in
here
again.
B
We've
got
him
in
quarantine
right
now,
because
he
was
swiping
at
our
dogging
cat
that
we
have
right
now.
So
he's
he's
alone
for
a
bit.
A
Kids,
don't
behave
sometimes
I
know.
Well,
we
fully
expect
to
see
an
appearance,
maybe
next
time.
That
would
be
really
great
all
right.
So,
let's
move
right
on
along
to
the
agenda.
We
have
a
few
items
from
last
week.
We
need
to
take
care
of.
It
looks
like
we
have
a
lot
of
items
from
last
week.
We
have
to
take
care
of
that's
totally
fine
and
also
new
items
totally
fine.
That's
the
whole
purpose
of
these
meetings
anyway.
A
So
yeah,
let's
jump
right
in
the
first
item
on
the
agenda,
is
to
discuss
what's
been
brought
up,
as
called
shared
focus
areas
across
the
group
on
dependencies.
So
I
will
let
sean
or
kevin
talk
about
that
if
they
would
like,
if
they
are
here.
A
A
D
This
dependency
issue
is
being
highlighted
a
lot
in
different
meetings
that
people
want
to
look
at
the
dependencies,
not
only
in
terms
of
library
dependency
in
terms
of
people
dependency
projects
dependency,
so
dependencies
can
be
looked
in
the
different
ways
from
the
business
perspective
from
the
value
perspective.
D
So
from
all
these
different
dependencies,
we
observe
that
dependencies
is
highly
important
and
each
working
group
is
looking
at
it
in
a
different
angle
from
the
dependency
perspective,
so
the
discussion
was
like.
Should
we
have
a
common
area
where
all
group
members
from
the
different
group
can
come
together,
chime
in
and
discuss
on
the
dependencies
to
grow
it
along
with
the
dependencies?
Also,
some
of
the
metrics
come
arises
where
multiple
groups
are
using
it.
D
So
the
the
theme
was
like
we
can
have
a
shared
focus
area
where
people
from
the
different
working
groups
can
come
in
and
discuss.
Okay.
These
are
the
metrics
which
are
used
by
the
different
groups
so
that
we
can
jointly
develop
them
and
use
them.
D
So
that's
where
this
topic
brought
here
in
the
common
like
that,
we
need
to
have
a
shared
focus
group,
our
focus
area
whereby
members
of
each
group
can
come
and
develop
the
metrics
which
are
aligned
with
all
the
groups.
E
So
we
so
we
we
did
talk
a
little
bit
about
having
a
a
separate
group
to
to
deal
with
this
issue.
That
is,
that
is
common
to
the
working
groups.
But
I
think
the
the
key
point
here
is
actually
the
the
idea
that
a
focus
area
can
exist
in
in
multiple
different
working
groups,
and
they
can
work
on
that
focus
area
independently
in
whatever
way
that
they
would
want.
E
So
the
the
focus
area
could
be
if
it's
dependencies
that
focus
area
would
exist
within
evolution,
it
could
exist
within
common
and
it
could
exist
within
risk
and
those
working
groups
could
independently
work
on
that
focus
area
in
the
way
that
they
see
fit.
So
it's
not
necessarily
coming
together
to
collaborate
on
dependencies.
It's
the
it's.
The
understanding
that
this
focus
area
can
exist
in
each
of
these
working
groups.
C
I
have
a
question,
so
what
would
the
and
you
may
not
have
the
answers,
but
what
would
the
focus
area
be
and
why
would
there
one
be
need?
Why
would
there
need
to
be
one
shared
across
working
groups.
F
E
E
E
C
D
G
G
Fun
yeah
these
things
happen
yeah,
so
that
that's
a
really
interesting
point
as
well.
C
C
I
So
is
this
so
I
understand
libraries
are
all
provided
the
data
set
and
tools
to
create
a
data
set,
but
from
a
chaos
and
metrics
perspective.
I
I
think
we
can
maybe
even
start
work
on
defining
what
we
could
be
doing
if
we
had
to
make
the
data
and
to
capture
some
of
the
work
that
we
did
in
the
early
days
with
the
library
zero
project.
And
then
I
don't
know
if
anyone
is
working
on
new
tooling,
but
that
would
then
complete
that
circle
at
some
point
that
we
have
for
chaos.
C
I
H
C
H
A
A
I
know
kevin
had
also
brought
up
when
we
get
to
the
point
where
we're
tagging
different
metrics
and
allowing
people
to
sort
on
them
in
different
ways
as
more
of
a
matrix,
not
just
like
a
linear
thing.
Having
that
shared
kind
of
focus
area
fits
very
nicely
into
that
and
and
kind
of
setting
up
a
framework
for
that
to
happen
in
other
ways.
C
Dog
was
freaking
out.
Sorry,
I
missed
it.
So
each
of
the
working
groups
could
kind
of
define
their
own
set
of
questions
that
are
relevant
like.
Why
are
dependencies
important
for
risk
and
what
are
the
questions
that
would
be
kind
of
risk
associated
questions
and
then
what
are
the
dependencies
that
are
from
a
value
perspective,
or
what
does
dependencies
mean
from
a
value
perspective
is
how
I
should
say
that,
and
what
are
the
questions
that
help
reveal.
E
Reside,
I
think
the
the
point
is
that
it
would.
It
would
continue
to
reside
in
in
each
of
the
individual
working
groups.
Okay,
so.
H
H
H
C
A
C
So
we
had
talked
about
remind
me
if
I'm
wrong
with
dev
stats
that
they
were
taking
a
look
at
so
dev
stats
is
the
tooling
that
cncf
has
put
together
to
get
health
understanding
of
the
cncf
related
projects.
C
Let
me
just
put
a
phone
number
in
the
chat,
I'm
tempted
to
call
it
from
what
I
understand
in
the
prior
conversation.
Dev
stats
was
kind
of
reflecting
on
on
how
they
represent
their
own
metrics
and
that
maybe.
D
H
C
C
A
Okay,
I'm
very
sorry
for
the
dogs,
they're
saving
us
from
the
terrible
amazon
driver
or
it
might
be
a
chihuahua
walking
by
I'm
really
sorry.
So,
let's
move
on
to
zoom
link
update.
Do
we
have
enough.
C
C
To
get
off
uno
and
from
a
pay
perspective,
I
think
we've
been
trying
to
figure
out
how
to
pay
out
of
community
bridge
they're.
Basically.
H
C
The
charge
is
going
to
be
to
we
just
have
to
pay
for
whatever
it
is
a
sitting
at
site,
a
project
whatever,
where
we
get
some
allocation
of
links,
yeah,
yeah,
yeah,
and
so
we
have
to.
I
think
it's
like
30
a
month
that
we're
gonna
end
up
paying,
and
so
we've
just
had
to
figure
out
a
little
bit
of
the
logistics
on
how
to
get
that
money
out
of
community
bridge
and
back
to
the
linux
foundation.
So
that's
it.
C
It
should
come
shortly
and
then
maybe
we
don't
have
to
do
all
this
admitting
like
how
I
have
to
how
we
all
have
to
admit
everybody-
and
we
can
also
right
now,
because
uno
is
a
little
problematic,
because
it's
university,
and
so
you
have
to
be
affiliated
with
the
university
to
actually
kind
of
be
on
the
account
which
I
think
we
need
to
not
have.
That
anymore
makes
life
a
little
harder
for
some
reason.
A
Okay,
thank
you
matt.
We
appreciate
that
all
right,
so
the
next
one
on
sorry,
the
next
one
on
the
agenda
is
the
community
reports.
C
So
I
just
an
update
there,
we're
really
getting
close.
I
was
going
to
show
some
of
the
reports
too,
but
we're
getting
pretty
close.
We
just
had
some
final
details
to
work
out
between
us
and
again
the
linux
foundation
as
because
they're
going
to
be
responsible
for
the
actual
process
by
which
a
request
is
made.
C
H
C
What's
going
to
be
produced,
I
am
co-host
so
I'm
going
to
share
my
screen
for
just
a
second.
C
Sake,
so
just
so,
you
all
see
the
this
is
the
one
of
the
versions
of
the
community
reports.
C
The
reports
are
going
to
be
12
months
prior,
so
they're
going
to
be
the
12
full
months
prior
to
the
date
of
request,
so
right
now
it
would
stop
at
the
end
of
august
of
this
year.
Right
now
the
reports
are
only
going
to
be
for
a
single
repository.
C
You
can
see
that
the
reports
are
generated
by
auger
cauldron,
which
is
underneath
auger
again
and
then
cauldron
with
some
links
to
the
software
as
well
as
links
to
the
metrics,
and
so
the
idea
behind
these
community
reports
is
to
really
just
kind
of
get
people
into
the
space
as
to
what
metrics
can
can
show
and
how
they
could
be
meaningful
for
their
community,
even
if
it's
just
one
repository
or
even
if
it's
just
four
different
kind
of
comp,
these
composite
metrics
and
really
to
demonstrate
the
work
that
has
happened
in
the
chaos
project.
C
So
if
a
community
wants
to
know
more,
that's
great
we'd
encourage
them
to
participate
in
the
respective
working
groups
or
in
the
community
call
or
to
reach
out
to
us
on
the
mail
list
whatever.
But
this
is
meant
to
kind
of
show
people
the
work
that
we're
doing,
provide
insights
for
folks
and
get
them
to
want
to
ask
additional
set
of
questions,
sean
or
georg
or
elizabeth
or
anybody.
You
want
to
add
or
subtract
from
what
I
said.
I
C
H
No,
I
think
I'm
keen
to
get
some
we're
gonna
try,
we've
asked
don's
today.
I
think
he's
gonna
help
get
us
a
little
bit
of
feedback
on
a
couple
of
different
versions
of
the
report,
just
as
a
very
lightweight
market
research,
but
we're
ready
to
start
rolling
as
soon
as
the
item
is
on
the
on
the
website.
G
G
It's
awesome,
have
you
as
anyone
that's
requested
something
like
this
seen
it.
C
C
C
That
and
I'm
guessing
in
the
next
week
or
two
we'll
actually
have
this
up
on
the
web
page
by
which
people
can
request
reports
very
cool.
A
D
H
C
I
K
D
D
C
Agree,
I
mean
maybe
that's
something
we
should
put
to.
You
know
how
we
have
some
on
the
web
page.
We
have
some
room
to
say
you
know
this
is
going
to
be
12
months.
Maybe
that's
something
that
we
could
say
that
our
goal
is
to
get
these
back
to
you
within
three
to
five
days.
Something
like
that.
E
If
you,
if
you
want
feedback
on
this
document,
could
you
share
the
pdf
with
us.
C
G
It
might
be
cool
to
get
it
on
a
in
a
public
place
to
do
so
as
well.
Maybe
you
can
make
a
public
link
to
the
pdf
and
github
issue
and
we
can
socialize
it
a
little
bit.
G
You
know,
or
you
know,
one
of
the
call
to
actions
of
people
who
are
interested
like
hey.
Look
at
our
draft
of
what
that
report
is
going
to
be
and
add
your
thoughts
on
it.
Just
trying
to
think
of
the
feedback
loops
for
people
to
weigh
in
beforehand
yeah.
C
C
G
C
G
G
C
H
Still
want
to
do
that
eric
and
sean
we
we
can.
I
think
we
need
to
go
back
and
add
that
to
the
report
that
we've
drafted,
obviously
because
we
did
not
do
that
in
the
in
the
original
graph,
but
I
think
it's
a
good
idea,
because
it
helps
people
map
atomic
metrics,
that
we
create
and
define
to
sort
of
the
synthesis
of
those
that
are
that.
I
think
atomic
metrics
are
often
as
actionable
as
a
combination
of
them.
I
E
From
so
I'm
not
from
looking
at
this,
I'm
not
it's
not
clear
to
me
what
the
definition
of
a
contributor
is,
for
example,
things
like
that.
So
if
we,
if
we
mapped
it
to
the
chaos
definition
of
what
a
contributor
is
or
or
metrics,
that
would
tell
me
what
you're
actually
measuring
that
might
be
helpful.
G
I'm
with
kevin
on
this
that,
like
connecting
it
back
to
what
we
do,
and
maybe
that
would
we'll
take
a
couple
iterations
before
we
get
there
smoothly
of
like
knowing
what
layer
of
expertise
or
are,
is
this
person
like?
Do
we
need
to
define
our
terms
really
thoroughly
or
do?
G
Can
they
be
assumed,
and
we
know
that
they're
contributors
to
chaos,
and
they
just
want
to
get
us
to
make
some
pretty
graphs
but
yeah,
connecting
it
all
the
way
through
to
like
making
sure
we're
reinforcing
what
the
terms
mean
in
a
clear
way.
Even
if
there's
like
a
summary
faq
after
this,
if
we
need
to
but
yeah,
there's
definitely
some
context.
There.
C
J
A
Awesome
all
right,
matt.
I
gave
you
an
action
item
for
that
too,
just
fyi
so
and
we
called
the
repo
health
reports.
So
I
guess
we
can
probably
change
that
if
you
would
rather
have
it
say,
community
reports
or
whatever
you
want.
A
We're
having
a
booth
at
all
things
open,
which
is
a
great
conference
they're,
doing
it
all
virtual,
of
course,
this
year
and
it's
october,
19th
and
20th,
and
because
of
the
wonderful
folks
at
patersia
they
have
offered
through
that,
I
believe
through
their
sponsorship
they
would
get
a
free
kind
of
add-on
booth,
so
they
have
donated
that
to
chaos
and
matt
and
georg
and
myself
will
be
staffing
that
booth
virtually.
A
A
H
I
B
So
I'm
I'm
like
I'm
glad
to
help.
I
just
I
just
want
to
make
sure
it
works
around
my
classes
and
things
like
that.
A
Yeah,
I
will
put
something
together
and
I'll
send
it
to
should
I
just
send
it
to
the
regular
chaos
mailing
list
or
yeah.
Okay,
I
will
do
that.
A
Not
sure
at
all
we
have
very
little
details
so
far.
E
G
Cool
yeah,
it
should
be
fun.
It
could
even
turn
into
an
opportunity
if
it
is
the
same
software
there's
basically
a
dedicated
chat,
room
per
booth
and
then
a
video
like
optional
video
component,
where
people
can
jump
into
a
shared
video
channel,
and
you
can
even
invite
people
that
are
in
the
channel
chatting
to
have
a
conversation
at
the
booth.
So
it
turns
into
like
your
own
sort
of
twitch
meets
podcast
meets
something
that
could
be
pretty
fun.
G
A
A
Cool-
let's
just
put
a
note
here
that
we're
doing
that
and
then
what
about
inner
sourcing.
C
You
put
that
there
too,
so
I
just
want
you
to
know
daniel.
Are
you
on
the
call
right
now?
The
hope
is.
Is
that.
C
I
do
see
him
still
on
the
list.
Hello.
Are
you
still
planning
on
coming
to
the
asia
pacific
meeting
next
week
about
intersourcing,
so
daniel's
going
to
talk
about
intersourcing
at
the
asia
pacific
call
next
week,
it'll
be
recorded
in
intersourcing.
It's
coming
up
quite
a
bit,
at
least
I'm
sure.
It's
very
high
on
the
thing
high
on
the
list
for
maybe
folks
at
patersia,
but
I'm
hearing
about
it
a
lot
too
and
requests
for
intersourcing
and
maybe
something
we
want
to
put
on
the
chaos
radar
too
so
daniel.
F
Oh
yeah
yeah,
so
it's
it's
on
wednesday.
F
9Th
yeah
that
one,
oh,
I
was
looking
for
that
yeah.
I
found
this
yeah
3
p.m.
Here
so
yeah
yeah,
I
I
we
were
discussing
about
this
beginning
of
august,
maybe
or
mid
hours
or
so.
What
am
I
gonna
discuss
in
in
this?
I
don't
know
so
this
is.
This
is
mostly
about
your
specific
needs.
So
we
have
we
kind
of
have
standard
topics
or
a
bit
of
discussion
about
the
inner
source
common.
F
F
H
H
They're
very,
it
seems
to
me
they're
in
a
very
beginning
place
and
so
getting
them
to
understand
key
concepts.
I
think
will
be
very
helpful.
Okay,.
K
C
A
A
A
A
H
Evolution
is
focused
on
developing
basically
deciding
what
metrics
we're
going
to
build
out
for
the
next
set
of
releases.
We
have
a
few
that
didn't
make
it
into
this
release
that
we're
likely
to
introduce
as
interim
releases.
We
do
have
a
larger
discussion.
I
don't
know
if
it
happened
before
I
got
here
about
the
review
versus
pull
request,
merge,
request
software
change.
That
might
be
something
that
needs
to.
I
don't
know.
If
did
we
talk
about
that,
while
I
was
taking
care
of
my
dog?
H
No
okay.
So
that's
a
that's
a
big
item
and
we
don't
have
time
for
that.
So
we'll
just
keep
discuss
we'll
bring
it
up
at
the
next
meeting
and
go
slow
on
making
any
changes.
H
Oh
okay,
we're
focused
on
tagging
and
understanding
how
so,
for
example,
the
linux
kernel
report
was
just
released,
showing
how
review
tags
are
significantly
more
used
now
than
they
were
early
on
in
the
kernel
and
kate.
Stewart
and
other
people
in
the
risk
group,
including
sophia,
are
looking
at
what
these
tags
mean.
A
B
If
you
want
to
be
a
reviewer
for
this
project,
it's
not
nearly
as
involved
as
it
used
to
be,
and
it
will
be
something
that
will
help
the
community
quite
a
bit
in
dni,
and
if
you
want
to
be
a
reviewer
or
don't
know
if
you're
a
viewer
or
anything
like
that
and
then
just
feel
free
to
email
me,
I've
got
my
email
there.
We've
got
a
new
burnout
metric.
B
That
looks
really
interesting
and
I'm
really
excited
to
see
what
comes
out
of
that,
and
I
am
not
so
sure
about
the
open
demographics
part
of
it.
I
A
Fantastic
value,
matt
b.
G
Yes,
we're
doing
some
fun
stuff
around
social
value
got
to
a
more
specific
definition
and
are
working
with
to
get
some
metrics
in
there
going
forward.
If
that
interests
you
jump
in
we've
got
some
others
in
progress
that
we're
working
through
like
project
popularity,
has
been
floating
around
for
a
while
and
needs
some
specificity
and
scms
is
evolving
into
a
project
similar
to
dna,
badging
and
community
reports,
and
then
there's
an
outstanding
request.
That
just
came
in
that.
G
I
want
to
take
the
30
seconds
of
this
and
ask
about
which
is
like
a
public
calendar
link
to
when
our
meetings
are.
Do
we
have
any
sort
of
chaos
wide
calendar,
that's
being
managed
that
I've
lost
track
of?
I
see
a
head
nod,
so
I
was
under
it's
under
slash
participate.
E
And
as
a
note,
if
you
need
to
add
things
to
that
calendar
or
or
edit
existing
things,
you
can
post
an
issue
on
the
website
repo
or
reach
out
to
myself.
A
K
Hi
so
yeah,
so
I
had,
I
have
an
update
on
g
was
seasonal
talk,
so
I
worked
on
the
working
group
section
for
the
cognitive
white
handbook,
which
I
put
up
the
link
within
in
the
meeting
notes
itself.
I
also
created
a
repository
for
tracking
up
my
progress.
The
link
can
be
in
the
same
meeting
notes
and
currently,
I'm
done
with
the
path
to
leadership
section
two
within
the
community
handbook.
I
also
shared
this
on
the
mailing
list
too,
and
feedbacks
are
appreciable
on
this.
K
So
I'm
like,
I
would
be
working
on
the
terminology
part
for
the
coming
days,
which
would
describes
the
terms
that
are
being
used
frequently
within
the
kiosk
community
and
how
to
use
the
terminology,
like
you,
usage
guidelines
like
capitalization
abbreviations
and
the
words
to
avoid,
with
some
reasons.
So
this
is
going
to
be
my
work
in
the
for
the
coming
days,
so
I
have
updated
the
with
my,
like,
I
updated
my
progress
on
the
mailing
list
with
my
blog
post,
as
well
as
the
weekly
report
yeah.
That's
it.