►
From YouTube: CHAOSS Asia Pacific Community Call 8-25-21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
A
The
asia
pacific
chaos
community
call
meeting,
you
could
add
yourself.
That
would
be
wonderful.
A
A
A
That's
funny
all
right,
so,
let's
see
we
have
something
here
at
the
top
I'll
share.
My
screen.
A
So
we
have
different
levels
of
developers
corresponding
to
different
operating
strategies.
I
did
not
put
this
in
there.
Do
you
does
anybody
know?
I
think
that
you
enjoy.
D
A
D
D
So
we
try
to
define
we
try
to
define
a
developer's
role,
so
you
can
see
this
this
from
bitter
bitterge,
so
they
define
the
three
levels
of
the
developer
developer
developers
about
core
regular
and
choreo.
So
we
also
have
a
in
our
open
unit
community.
D
We
have
our
own
defined
about
the
deployer,
so
we
define
its
d
0
d,
1
d
2,
and
we
try
to
define,
define
this
deployer
to
find
out
which
people
do
which
scenes.
So
we
can
and
we
can
figure
out.
So
what
is
the
conversion
conversion
rate
from
such
as
conversion
rate
from
d0
to
d1
or
d1
to
d2
like
this?
So
this
is
our
defended.
D
Maybe
it
is
an
example
or
something
else
like
like
a
video.
They
also
have
their
defendant.
So
the
question
is:
is
this
suitable
for
putting
on
kills
as
an
example
or
the
second?
The
question
is:
is
it
correct
or
it
is
and
to
defend
this
like
this,
so
that
I
have
two
questions
about
about
this.
A
So
first,
thank
you
for
sharing.
This
is
really
great,
so
the
first
question
with
respect
to
how
could
we
bring
this
forward
in
the
chaos
community?
Well,
yes
or
no.
The
answer
is,
of
course,.
D
A
The
second
is
with
respect
to
a
metric.
I
think
you
had
mentioned
conversion
rate
between
contributors.
Is
that
right,
so
you're
interested
in
how
developers
move
between
d0,
d1
and
d2
is
that
right.
A
You
know,
we'd
have
to
kind
of
identify
a
few
things
like
what
the
the
objective
of
the
metric
is
like.
Why
you
would
want
to
care
about
something
like
this.
You
know
what
I
mean,
so
we
could
easily
do
that
and
it
sounds
like
you
have
deployed
this
in
grammar
lab
through
a
dashboard.
A
A
A
So
basically,
our
ranking
art
isn't
working
right
now,
but
we
have
different
focus
areas
within
the
chaos
project,
so
common
metrics
diversity,
equity
and
inclusion,
metrics
evolution,
risk
and
value.
So
we
can
we
kind
of
categorize
our
metrics
at
the
highest
level
around
these
different
focus
areas
or
within
these
different
areas,
and
then
within
each
one.
A
We
have
particular
focus
areas
so
I'll
go
down
to
evolution.
We
have
a
focus
area
around
code
development
activity
and
then
we
have
specific
metrics
that
help
understand
code,
development
activity,
and
so
what
you
were
talking
about
I
had
put
as
like
the
metric,
I
think,
would
be
called
conversion
rate
that.
A
And
I'm
not
quite
sure
where
it
would
fit
code
development
process
issue
resolution,
maybe
community
growth,
because
this
is
kind
of
about
the
people.
So
this
is
kind
of
a
community
related
metric
and
so
like,
we
have
a
metric
called
inactive
contributors,
and
we
just
we
follow
a
template
like
this,
so
a
description.
What
is
it?
What
is
this
metric,
so
we're
interested
in
how
people
move
between
different
development
roles
or
profiles,
the
objective,
whatever
the
objective,
might
be
for
wanting
to
see
this
like?
Why
do
you
care
about
people
moving
between
roles?
A
How
you
would
go
about
implementing
such
a
metric,
which
I
think
you
talk
about?
You
know
when
you
talked
about
those
roles,
the
different
things
that
you're
looking
at
for
the
different
types
of
roles.
So
this
is
how
you
kind
of
implement
this
and.
D
A
The
different
this
is
fairly
short
metric,
but
the
different
data
collection
strategies
that
you
would
use
to
capture
that
data,
and
so
it's
just
just
really
a
way
to
help
people
who
aren't
familiar
with
the
metric
that
you're
talking
about
just
understand
kind
of
the
definition
of
that
metric.
C
Matt,
while
you're
doing
that,
I
just
wanted
to
make
a
quick
comment:
the
drupal
community
drupal
d-r-u-p-a-l.
They
had
developed
a
pretty
detailed
list
of
potential
roles
within
their
project.
C
I
mean
they
went
even
so
far
as
to
say
you
know
this
person
works
on
like
the
social
media
team
for
the
project
you
know,
so
they
have
a
very,
very
detailed
list,
and
this
would
fit
in
great
with
that
with
this
metric
that
we're
talking
about-
and
I
think
it
also
kind
of
touches
on
what
we
were
talking
about
yesterday
in
the
metrics
model
group,
about
the
the
events
tracking,
even
someone
that
just
attends
an
event
that
your
project
is
about
and
then
like
watching
their
journey
across
to
make
them
a
contributor
like
how
does
that
journey
go
from
even
just
you
know,
starting
out
as
an
attendee
in
an
event
and
like
bringing
them
forward
all
the
way
across.
C
A
F
A
A
You
know
what
I
mean
if,
if
june
has
an
interest
because
oftentimes
you
just
spend
a
little
bit
of
time
as
a
group
of
people
just
working
in
the
document
collaboratively
so
that
you
don't
have
to
do
all
the
work
by
yourself,
we
can
do
it
as
a
group
and
then,
as
it
kind
of
kind
of
formalizes,
we
could
bring
it
to
the
evolution
working
group
and
just
because
I
think
the
timing
of
that
working
group
is
even
later
for
you
all
right
now
in
the
day.
A
A
D
A
D
A
Yeah
so
just
start
some
document
that
we
could
all
work
on
next
week
so
like
whether
it's
sharepoint
I
could
set
one
up
the
sharepoint.
This
seems
to
work
for
everybody
on
this
call.
A
C
A
D
Okay,
oh
I
I
I
remember
what
I
second
the
question.
The
second
question
is:
is
it
correct,
do
you
think
my
defined
it
is
it.
A
Yeah
and
I
think
in
terms
of
like
defining
the
the
people,
I
think
elizabeth's
point
was
really
good-
that
the
drupal
community
can
help
in
that
regard
too.
Personally,
I
so
a
lot
of
these
metrics
are
just
to
kind
of
help
like
locate
people
in
a
particular
way
of
thinking
about
their
communities
and
the
way
that
dawn
may
think
about
her
communities
and
the
way
that
who.
A
Think
about
his
communities,
they're-
probably
going
to
be
a
little
bit
different.
So
there
is
no
like
universal
truth
or
correct
way
of
thinking
about
it,
but
a
metric
like
what
was
it
called
again
conversion
rate
for
contributors
like
that
might
be
something
that
that
folks
at
vmware
might
care
about
in
a
particular
way
and
they
might
define
the
parameters
a
little
bit
different
than
the
way
that
say
folks
at
huawei
may
think
about
it
and
define
the
parameters
a
little
bit
different
and
so
we're.
Okay
with
that.
A
A
Let's
see
I
just
kevin,
I'm
so
glad
you
joined
our
resident
metrics
release
person
hi,
so
I
just
want
to
make
a
note
that
the
metrics
released
the
the
freeze
for
the
metrics
for
this
next
round
is
going
to
be
at
the
end
of
this
month
so
kevin.
Do
you
have
any
comments
that
you
just
want
to
say
on
on
that
at
all.
B
B
So
we've
we've
just
we've
just
kind
of
ironed
out
some
of
the
the
work
group
checklist.
So
this
week
we
are
going
through
and
we
are
pardon
me
we're
adding
a
a
checklist
document
to
each
working
group
and
following
that,
we
we're
going
to
go
through
and
we're
going
to
make
sure
that
all
of
the
newly
released
metrics
have
an
issue
created
for
them
in
the
translations
repo.
B
A
E
B
So
we
do
have
a
right
now
we
have
a
total
of
eight
metrics
that
have
been
released
by
the
working
groups
and
I
think
we
have.
I
think,
four
of
those
have
issues.
E
B
Yeah,
that's
what
I
that's
what
I
was
just
saying
so,
the
on
our
on
our
side.
The
working
groups
have
released
eight
metrics.
However,
we
have
only
created
four
four
issues,
so
you
have.
There
are
four
more
that
we
need
to
create
right
now
and
then
I
can
tell
you.
I
can
tell
you
also
that
the
a
few
of
the
working
groups
are
going
to
be
pushing
some
metrics
out
at
the
last
moment.
B
Okay,
so
we
can
probably
expect
two
to
four
new
metrics
before
the
release
freeze.
So
this
this
release
will
probably
release
a
total
of
around
12
metrics.
B
Okay,
so-
and
I
will
I
will
do
my
best
to
get
those
issues
created
for
you
as
soon
as
possible,
so
you
have
a
little
more
time
to
to
peek
at
them.
Yeah
yeah,
yeah,.
B
And
then
I
know,
risk
risk
will
end
up
having
a
couple
as
well.
E
E
B
Excellent
well,
thank
you
thank
you
for
that,
so
we
we
all
really
appreciate
the
work
you're
doing
on
the
translations.
A
D
A
A
D
A
Yep,
I
see
people
in
there,
so
good
yay
great,
let's
see
a
few
other
things
just
to
just
as
a
note.
We
have
a
new
chaos
privacy
policy,
so
we've
been
working
like
we
started
the
work.
A
year
ago
I
was
gonna
say:
we've
been
working
on
this
for
a
year,
but
that's
not
true.
We
started
the
work
a
year
ago
and
recently,
steve
winslow,
with
linux
foundation,
kind
of
gave
it
a
review
and
added
a
few
comments
that
are
in
line
with
the
lf
policy,
and
so
it's
it
was
approved.
A
You
thought
it
looked
good
and
we
now
and
so
this
policy
is,
it
describes
what
we
as
the
chaos
project,
do
with
the
data
that
we
collect
and
steve
thought
it
was
appropriate
that
the
chaos
project
has
its
own
data
policy.
That's
somewhat
independent
from
the
linux
foundation,
just
because
we're
kind
of
in
this
world
of
collecting
data
and
thinking
about
so
we
thought
it
was
a
good,
a
good
good
way
to
think
about
things.
A
We
can't
have
a
policy
clearly,
but
we
can
at
least
have
guidance
like
as
you're
collecting
this
data.
Here
are
the
bounds
that
you
probably
want
to
think
about
as
you're
collecting
that
data,
particularly
with
with
laws
both
here
domestically
in
the
united
states
and
internationally,
having
a
pretty
big
impact,
not.
E
Data,
I
have
a
question
match,
so
this
power
say
policy.
This
means
like
say
the
augur
and
chaos
the
service
provided
by
those
tools
they
have
to.
They
have
to
follow
this
policy
and
in
some
scenario
like
some
some
community,
they
they
download
and
they
deploy
their
own
auger
and
grip
lab
in
their
own
community.
A
No,
it's
just
it's
just
only
for
our
community,
but
then
the
second
document
would
be
for
the
people
who
are
installing
their
own
version
of
grimoire,
lab
or
auger.
It
would
be
guidance
we
would
say
here
are
things
that
as
you're
deploying
these,
you
might
want
to
think
about
like
how
you
store
the
data,
how
you
represent
the
data,
how
you
think
about
personal
identifiable
information,
just
those
kind
of
things,
but
it's
more
just
to
help
people
along.
G
I
know
I
notice
at
the
bottom
that
the
contact
person
is
is
elizabeth,
which
is
great,
but
so
I'll
be
honest.
Like
at
vmware,
we
had
a
key
person
who
was
the
contact
person
for
everything,
leave
a
group
and
go
to
another
group,
and
it
has
been
painful
to
kind
of
scrub
that
I
wonder
if
there's
like
a,
we
could
create
like
a
community
contact,
alias
like
an
alias
email
that
goes
to
elizabeth,
but
I'm
just
I'm
just
thinking
long
term.
It's
better
to
have
some
aliases
for
things
like
that
than.
A
A
A
We
have
like
we
have
such
an
alias
for
code
of
conduct
violations
and
then
we
just
manage
the
people
that
receive
that.
So.
A
G
G
A
G
C
A
A
B
We
will
be
live
streaming
that
event,
however,
we're
also
going
to
be
having
a
a
follow-up
kind
of
virtual
event,
that'll
that
we
don't
have
the
details
of
that.
Yet.
A
Recorded
videos
for
some
of
the
present
we
record
everything
it'll
be
live,
streamed
and
fully
recorded,
but
then
we
would
also
have
sessions
where,
like.
If
I
recorded
a
presentation,
I
would
be
available
to
answer
questions
at
a
particular
time
when
the
presentation
airs
is
that
right,
kevin.
B
Yes,
yes,
so
the
the
virtual
event
would
be
would
be
disconnected
from
the
in-person
event
and
we
would.
We
would
spread
it
out
over
possibly
a
week
or
two
and
have
yeah
basically
question
and
answer
sessions,
and
maybe
some
panel
discussions
that
could
kind
of
happen
live.
B
But
those
the
virtual
event
has
not
been
planned,
yet
we
just
know
that
we
need
to
collect.
We
know
that
we
need
to
record
all
of
the
presentations
for
the
in-person
event,
and
then
we
also
know
that
any
anyone
who
has
submitted
a
a
presentation
and
if
they
won't
be
able
to
be
there
in
person
we're
asking
them
to
record
their
presentation
so
that
we
can
show
it
at
the
virtual
event.
E
We
have
already
some
schedule
on
to
say
the
topics
and
how
it
what
the
content
and
of
those
publicly
presented
in
the
in
the
chaos.
A
The
the
last
thing
that
I
have
did
anybody
else
have
anything
on
events
or
anything
like
that.
Okay,
the
last
thing
is,
I
just
wanted
to
to
briefly
relive
the
metrics
model
discussion,
because
my
brain
is
still
reassembling
from
our
discussion
of
personas
use
cases,
metrics
models,
metrics
and
I
know
so
so
we
were.
A
I
know
a
number
of
us
were
on
the
call,
but
we
were
thinking
about
right
how
to
bring
metrics
forward
in
in
models
that
could
be
useful
to
individuals.
Not
just
kind
of
the
individual
metric.
You
know,
like
age
of
issue
could
be
useful,
sure,
but
kind
of
how
a
collection
of
metrics
might
be
useful
for
a
community
manager.
A
It
could
be
useful,
for
you
know,
an
organization
that
is
releasing
open
sources
or
ips
open
source,
or
something
like
that,
some,
whatever
the
scenarios
might
be,
and
the
app
ecosystem
we
were
kind
of
trying
to
connect
with
the
app
ecosystem
work.
Their
work
is
considerably
more
top-down,
so
they
kind
of
think
of
the
goals
that
they
may
want
to
accomplish,
safe
for
an
event
like
thinking
about
metrics
associated
with
an
event
and
as
a
result,
they
to
adjust
their
goal.
A
They
kind
of
come
up
with
metrics
that
may
or
may
not
exist
in
the
chaos
project.
So
the
metrics
in
in
their
scenario,
are
a
bit
more
hypothetical
than
I
think
what
we
were
thinking
about.
So
from
the
metrics
model
discussion.
We
were
basically
saying
of
this:
whatever
50
or
60
metrics.
We
have
in
chaos
that
currently
exist
and
are
hopefully
deployable
in
some
way.
How
do
we
bring
those
together
in
ways
that
are
meaningful,
so
we
could
actually
tool?
A
You
know,
use
auger
or
grimore
lab
to
actually
show
these
metrics
models.
So
again,
the
app
ecosystem
is
a
little
bit
different
because
a
lot
of
the
metrics
that
they
talk
about
don't
exist
yet
there's
they
don't
we
don't
have
metrics
for
them.
We
haven't
written
the
markdown
for
them.
They
were
just
kind
of
thinking
about
the
goal
and
imagining
metrics
that
could
help
inform
that
goal,
which
is
actually
kind
of
how
we
build
metrics
anyway.
A
So
this
is
kind
of
the
opposite,
so
we
I'll
pull
up
the
metric
spreadsheet.
A
B
A
You
can,
if
it's
yes,
it
is
like
super
clear.
B
I
would,
I
would
just
say
that
I
think
we're
on
the
right
track
here
and
I
I
think,
the
how
we,
how
we
structure
the
the
models
in
relationship
to
each
other
is
going
to
emerge
as
we
continue,
but
I
think
I
think
we're
on
the
right
track
with
starting
with
the
the
the
way
we
are
developing
these
models
now
or
the
way
we're
thinking
about
these
models
now.
Okay,
so
I
think
the
the
one
thing
we
need
to
probably
resolve
at
this
point
is
a
kind
of
a
common,
simple
structure.
A
To
present
these
existing
models,
I
agree.
I
agree
with
that.
We
didn't
really
get
to
that
yesterday,
yeah.
That
was
like,
because
the
app
ecosystem
uses
text-
and
I
like
the
the
one
that
I
think
I
do
think
it
was
brought
forward-
was
a
visual
and
I
I
connected
with
the
visual
that
powerpoint
one
that
developed.
It
was
more
of
a
flowchart,
but,
like
I
really
connected
with
that
really
well,
and
so
I
prefer
kind
of
a
visual
model.
B
But
the
part
of
the
problem
is
the
is
the
complexity
of
using
a
bunch
of
different
types
of
models
right
now,
and
I
think
that's,
I
think,
that's
where
we're
kind
of
getting
hung
up
in
our
discussion,
so
it
might
be
best
to
just
start
with
a
very
plain,
simple
text-based
model
and
then
move
and
then
move
on
from
that
text-based
model
to
to
more
complex
visual
representations
of
the
model.
A
Okay,
so
the
what
we're
doing,
at
least
in
terms
of
from
what
I
understand
is
the
next
steps
forward
for
the
metrics
model
working
group.
Is
I
trying
to
identify
existing
models
so
things
that
may
already
be
in
practice?
A
Sean
has
mentioned
this
in
his
work
with
auger
that
there
are
already
models
where
metrics
are
being
drawn
together,
and
if
we
can
capture
that,
that's
probably
the
best
way
to
start.
I
think
you're,
alluding
to
this
kevin,
and
then
we
worry
about
like
is
this
an
issue
of
governance?
Is
this
an
issue
of
operations?
Is
this
an
issue
of
development
like
where
does
it
fit?
So
it's
a
little
bit
different?
A
Actually,
it's
not.
Actually
it's
not
actually
not
that
different
from
how
we
develop
metrics,
we
kind
of
develop
a
metric
and
then
we're
like
all
right.
Where
does
that,
because
we
just
did
that
here
today,
we're
like
this
seems
like
it
fits
in
evolution.
You
know
what
I
mean
like.
We
had
a
metric
and
it
seemed
like
we
found
a
home
for
it.
E
A
Models
and
then
kind
of
like
working
them
into
a
structure.
I'll
just
say
again.
Like
I
said
yesterday,
we
have
to
err
on
the
side
of
simplicity,
because
if
we
want
people
to
to
be
able
to
look
at
these
and
understand
where
they
are
locate
themselves
in
relation
to
a
metrics
model,
it
has
to
be
very,
very
simple.
G
As
someone
who's
tried
to
roll
out
the
grammar
labs
dashboards
to
lots
of
people,
complexity
is
not
your
friend
people,
just
people
don't
understand
that
they
won't
use
it.
A
E
Cool,
so
we
are
gonna.
We
are
gonna,
have
a
next
metric
smaller
meeting
two
weeks
later
right,
no.
A
A
And
then
it'll
move
to
two
weeks,
just
so
it'll
be
off
it'll,
be
asia-pacific,
call
will
be
one
week
and
then
the
metrics
model
meeting
will
be
the
next
week
and
so
we'll
just
kind
of
those
will
be
off
cadence
with
each
other
cool.
All
right,
I
am
done
with
content
everybody.
This
is
good.
Does
anybody
have
anything
else
they'd
like
to
bring
forward
today
or
share,
or
anything
like
that
or
questions
that
you
might
have
all
right?