►
From YouTube: CHAOSS Asia-Pacific Community Call 5/18/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
B
A
A
But
I
would
also
like
to
say
that
you
know
if
we,
if
we're
doing
a
meetup
say
in
asia,
pacific
or
a
chinese
meetup
like
this
would
be
a
good,
a
good
call
to
talk
about
that.
So
if
there
are
logistics,
this
would
also
be
a
fine
time
to
talk
about
that
as
well.
You
know
what
I
mean
so
and
then
I
would
just
like
to
say
I
had
it
on
the
agenda.
I'll
share
my
my
screen
here,
but
I'm
gonna
start
with
it.
A
A
We're
excited
too,
and
it's
great
to
have
you
like,
participating
again
well
sure
you
and
I
can
or
like
you
me,
sean
and
elizabeth.
We
can
just
talk
in
order
to
like
take
care
of
all
the
logistics
and
just
kind
of
what
the
focus
will
be
over
the
course
of
summer.
So
it's
great
to
have
you
back,
even
though
you've
never
left.
A
We
are
too
it's
great
and
then
you
huey,
just
just
let
people
know
too
just
google
summer
of
code
update.
So
we
can't
talk
about
on
this
call
who
we
recommended,
but
the
recommendations
are
in
and
you
I
kind
of
talked
to
you
a
little
bit
like
yeah
yeah
yeah.
So
at
this
point
we're
just
kind
of
waiting
to
see
what
google
does
it's
a
little
bit
different
this
year.
So
in
the
past
we
would
make
some
recommendations
on
the
number
of
slots
that
we
would
like.
A
So
we
would
just
give
them
a
number
like
eight
six
seven
this
year
we
had
to
rank
order
people,
so
we
had
to
say
who
our
top
candidate
was
and
all
the
way
down
through,
say
like
11.,
so
we
we
did.
We
submitted
the
rank
order
last
wednesday,
I
think-
and
so
I
think
we
hear
relatively
soon
but
more
to
come
on
that.
So
we
did
have
some
interest
too
in
the
kind
of
the
work
that
you
were
proposing
yahui
around
the.
A
A
E
A
E
E
Survey
survey
metric
module
about
so
the
last
second
way,
and
we
just
show
how
to
our
solution.
Proposals
about
our
match
model
step
two
and
the
only
difference
about
survey,
metric
module.
It
means
we
have
the
different
original
dates,
because
we
have
the
different
way
to
get
our
original
debt
about
the
survey
data
set.
E
E
E
E
It
means
at
least
we
need
to
get
this
number
of
temples.
Our
survey
debt
is
worse,
otherwise
it
is
otherwise.
It
is
not
correct
surveyed
sets,
it
will
make
make
the
rom
it
will
make
the
wrong
results
about
this
survey.
So
this
is
our
first
step
to
choose
a
sample
size.
We
know
how
many,
how
many,
how
many
number
of
samples
and
the
second
step
is
to
design
a
questionnaire,
so
we
have
to.
E
E
E
A
Yeah,
this
is
great.
No,
this
is
great.
So
thank
you
for
this.
So
the
way
I
understand
it
is
the
yellow,
so
the
the
algorithm
definition,
the
yellow
in
the
algorithm
definition,
is
essentially
mapped
to
the
linear
regression
on
the
left.
It's
the
proposed
technique.
Analysis
techniques
is
that
right.
A
E
F
A
E
B
D
D
A
Okay,
this
this
makes
it
so
I
mean
the
data.
Insight
is
essentially
the
that's
the
narrative
right
that
we
provide
so
like
yahuwah.
You
had
provided
the
data,
the
narrative
about
how
you
as
a
person
or
you
as
an
employee,
would
come
to
understand
the
data.
That's
in
front
of
you
like,
what's
a
sample
way
to
understand
that
that's
the
data
insight,
so
that's
kind
of
the
really
human
component
here,
exactly
okay,.
A
A
D
A
A
We
have
some
different
rules
as
to
what
we
can
provide
and
can't
provide
just
because,
as
a
research
institution,
we
have
some
like
rules
on
how
we
handle
the
data.
But
fundamentally
it's
the
same.
Fundamentally,
it's
the
same
thing.
So
if,
if
there
was
a
fourth
box
below
use
models
for
data
filtering,
I
mean
the
data.
Insights
are
really
the
analysis
of
the
data.
That's
really
what
it
is.
A
A
A
We
redefine
the
code
books,
we
do,
for
example,
frequency
counts
or
we
do
they're
just
a
variety
of
different
ways,
but
in
this
case
I'm
kind
of
okay
with
just
relying
on
like
your
experience,
yuhui
to
provide
insights
or
our
experience
in
the
chaos
project.
To
provide
insights,
I
think
I
think
that's
an
okay
step.
D
D
E
A
A
D
A
A
So
then,
that
kind
of
leads
to
my
one
of
my
questions
here
so
kind
of
based
on
on
where
we're
going
here
so
june.
I
know
that
you
and
other
folks
have
been
doing
a
lot
of
work
around
the
implementations
and
that's
great,
and
I
know
that
shawn
and
ragam
have
been
doing
this
as
well.
I
think
we're
starting
to
kind
of
get
this
down.
A
How
we
think
about
the
structure
of
the
model
repository,
so
this
is
our
current
metrics
model
repository
and
right
now
we
had
initially
focused
on
focus
areas
and
we
have
a
folder
called
toolkits,
but
we've
been
kind
of
focusing
on
implementations,
which
is
great
and
I
think
implementations
folder
should
stay
tool
kits.
I
have
a
pull
request
in
to
remove
this
and
focus
areas
are
aligned
with.
A
A
So,
for
example,
in
the
risk
working
group,
we
have
a
focus
area
called
security.
We
have
a
focus
area
called
business
risk
and
it's
just
a
way
to
kind
of
organize
metrics,
it's
not
perfect,
but
it's
a
way
to
think
about
metrics
kind
of
collectively
we
just
just
because
we
were
doing
this
in
the
metrics
working
groups.
We
just
kind
of
fell
to
that
model
in
metrics
models
that
we
have
a
focus
area
called
development.
We
have
a
focus
area
called
community
engagement
and
so
on
and
so
forth.
A
A
A
D
Actually,
I
have
similar
questions
about
about
the
whole
structures
of
this.
About
about
our
matrix
model.
I
have
one
idea
is
to
to
compose
the
all
the
I
mean:
organized
all
the
matrix
model
in
by
the
way
of
the
ecosystem
current
view,
for
example,
from
ecosystem
from
you.
We
have
a
productive
productivity.
D
D
B
G
D
Three
aspect
to
to
marrying
the
whole
ecosystem,
productivity
and
and
robustness,
and
the
niche
creation,
and
these
three
aspects
also
used
in
the
as
I
saw
some
papers
in
the
open
source
related
area.
They
also
reuse
this
concept
in
the
open
source
ecosystem
to
to
divide
the
whole
marrying
scope
into
two
into
three
aspects.
D
A
D
Yeah,
maybe,
for
example,
not
all
the
open
source
project
could
be
treated
either.
Echo
system,
for
example,
a
plug-in
open
source
software.
It's
only
built,
for
example,
one
plug-in
of
the
vs
code.
This
plugin
is
open
source
button.
It's
and
per
se
it's
it's.
A
it's.
A
independent
cannot
be
treated
as
an
ecosystem.
D
D
D
D
C
I
have
a
comment,
so
are
we
talking
about
using
productivity,
niche
creation
and
robustness
to
categorize
the
matrix
models,
categorize
matrix,
yeah
yeah?
That's
that's
one
of
my
idea,
oh,
that
that
makes
sense.
Well,
while
I
was
looking
at
the
redmi
file
of
the
matrix
model
repository
and
looking
at
the
goal,
the
goal
of
this
is
to
like
to.
C
Combine
different
metrics
together
and
make
a
model
really
can
be
applied
in
practice.
So
how
about
this
is
just
an
initial
idea,
so
I
I
haven't
think
about
an
actual
categorization
yet,
but
maybe
I
was
thinking
to
cut
on,
to
make
the
structure
instead
of
using
fox
areas
like
describing
the
the
area
the
matrix
is
belong
to
like
the
aspect,
this
matrix
or
matrix
model
is
belongs
to.
A
A
A
C
Like
like,
we
can
have
categories
like
if
you
want
like
contributor
growth,
like
if
your
goal,
the
goal
of
your
community
is
to
to
involve
more
contributors.
These
are
the
matrix
models.
You
you
you,
you
can
have
a
look,
but
I
just
realized
that
community
growth
growth
seems
to
be
one
of
the
first
areas
of
chaos.
Metrics.
D
A
D
A
A
D
Yeah,
for
example,
community
activity.
We
would
move
it
to
the
robustness.
Yes,
because
yeah,
because
the
more
active
of
this
community
means
they
can,
you
mean,
difference
some
unexpected
risk
from
outside
of
or
from
inside.
So
that's
what
we
want
want
to
put
this
activity
into
this
robustness,
okay
and
yeah.
D
D
Maybe
later
I
can
share
you
share
with
you
or
all
you
guys
more
papers
related
related
to
the
open
source
ecosystem
papers.
I
read
something
about
it.
There
are
a
lot
of
papers
related
to
this,
and
also
I
I
noticed
that
you
and
shane
read
some
papers
and
quick,
read
written
by
you,
and
they
also
mentioned
this
concept
before
so.
A
A
C
D
C
Yes,
yes,
there
are,
they
they
have,
they
have
the,
but
what
I
was
thinking
is
people
always
come
to
matrix
models
with
certain
certain
amps
and
they
have
their
required
and
if
and
if
we
have
them
structured
with
that
clear
illustr
clear
explained,
go
off
of
those
models,
the
clear
usage
of
those
models
and
they
can
know
exactly
which
are
the
which
area
they
should.
They
should
look
look
at.
A
So
so
I'm
going
to
take
an
action,
I'm
going
to
redesign
this
repository
for
the
next
metrics
model
meeting,
not
I'll,
do
it
as
a
as
a
forked
repository,
but
just
based
on
this
conversation.
I
was
wondering
too
listening
to
yahui
and
choy.
Listening
to
the
two
of
you,
talk
like,
like
renaming
the
implementations
folder
to
something
like
desired
aims
or
desired
goals,
or
hopes
and
dreams
like
something
that
that
would
signal
to
a
person
like
young.
D
Yeah
great,
so
actually
we
we
already
do
something
in
the
matrix
model
I
mean
in
the
definition
part
we
we
either
use
the
stories
and
the
use
cases
to
describe
what
what
kind
of
scenarios
could
adapt
to
this
could
be
adapted
to
this
matrix
model
and
who
can
yeah?
Who
can
use
this
matrix
model?
I
think
we
can.
We
already
add
such
information
into
the
definition
of
the
model.
A
A
This
is
still
not
that
structured,
but
this
structure
still
stays
the
same,
because
I
really
I
do
like
this
structure
a
lot,
but
then
in
here
instead
of
these
at
the
top
level,
it
would
be
whatever
it
was:
not
productivity,
oh
yeah,
productivity,
sorry
it'd,
be
productivity,
robustness
and
niche
creation,
and
then
within
there
we
would
have
the
three
different
metrics
models
or
the
okay.
I
like
that
better
and
then
we
get
away
from
I'll
have
to
update
this
as
well
to
reflect
the
three
and
then
we'd
have
to
move
some.