►
From YouTube: CHAOSS Asia-Pacific Community Call 7-14-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).
A
B
A
Yeah
something
like
that,
so
the
believing
space
is
where
we're
gonna
have
videos
and
online
keynote
is
entirely
possible.
There's
a
guidelines
for
metrics
translation.
A
D
D
A
A
I'm
not
sure
who
brought
it
up,
but
somebody
mentioned
that
some
some
words
in
the
metrics
do
not
have
a
strong
map
to
english
or
between
chinese
and
english,
and
so
some
of
the
language
that
we
use,
I
think
maybe
proxy,
was
one
of
the
words.
But
there
are.
There
are
words
that
are
in
some
of
the
books.
E
A
Is
there
is
anyone
who
would
be
willing
to
do?
We
have
the
translations
available
right
now,
yash.
D
D
F
F
The
the
chinese
translations
that
we
have
were
were
translated
almost
a
year
ago,
and
then
I
know
that
the
the
translation
team
has
been
working
on
updating
them,
based
on
the
the
new
metrics
and
the
the
changes
to
metrics
that
have
occurred.
F
E
Yeah,
it's
not
the
same,
and
we
were
translating
is
especially
hue
and
clement.
They
are
translating
the
new
released
new
release
matrix
which
from
the
version
of
this
march-
and
we
will
try
to
release
oh.
G
E
G
Actually,
we
have
to
translate
the
latest
version
on
the
master
branch
following
the
the
english
branch
in
english
version,
and
we
have
finished
the
coleman
working
group,
common
and
risk
and
and
evolution.
These
three
working
groups
and
they've
been
still
working
on
the
rest
of
the
two
working
groups
like
value
and
and
what's
the
last
thing.
G
Yeah
yeah,
that
was
the
inclusion,
and
we
think
that
we
are
gonna
finish
that
by
the
end
of
this
month,.
F
E
F
H
F
When
how
can
you
tell
us
when,
when
everything's
ready
for
the
release
in
comparison
to
unstable,
I
saw
that
you
have
finished.
G
Your
introduction
right-
and
I
just
want
a
mission
to
answer
your
question-
that
actually
we
have
planned
to
get
to
catch
up
the
the
next
official
release
of
the
english
version,
which
would
be
the
on
the
november.
I
think-
and
I
think
before
we
want
to
think
up
the
progress
of
that
next
english
version
release
together
with
the
chinese
release.
We
think
because
we
we
want
to
match
up
all
the
metrics
between
the
chinese,
washing
and
english
worship.
A
G
G
Okay,
so
when
I'm
sorry,
what
was
the
question?
Would
it
be
a
simultaneous.
A
F
English
language
release
happens
twice
a
year
so
about
six
months
apart,
so
that
happens
in
october,
and
it
also
happens
in
march.
A
A
D
Further
yeah
we
have
a
section
for
translations
released.
Oh,
these
are
translated.
Oh
yeah,
wow
handbook
is
total.
Actually
I,
after
two
months
of
period
like
I,
was
actually
thinking
like
once
we
have
the
english
release.
Then
we
could
give
the
translations
team
some
time.
So
they
could.
You
know,
review
the
pdf
and
incorporate
those
changes
and
they
could
have
a
two
months
of
time,
so
the
translations
release
would
be
delayed
by
two
months,
an
englishman,
but
if
the
team
feels
that
they
can
do
a
release,
I
think
that's
better.
A
So
there's
two
questions
here:
one
is:
how
do
we
signal
that
those
translations
are
ready
and
the
second
is
timing?
Can
I
suggest
first,
the
signaling
of
readiness?
Maybe
we
enable
whomever
is
doing
the
translations
or
working
on
the
translations
to
have
a
separate
branch
in
the
repository
for
translations
that
they
could
edit
and
then,
when
the
asia-pacific
team
community
thinks
that
the
translations
are
ready
in
chinese,
they
would
do
a
pull
request
into
the
main
repository.
F
However,
okay,
usually
at
least
I
would
one
metric
probably
gets
edited
a
lot
a
lot,
so
most
of
the
metrics
make
it
through
and
it's
usually
one
metric
will
get
get
a
fair
amount
of
edits.
So
the
when
the
metrics
are
going
through
the
review
period,
you
they're
not
they're,
not
considered
stable,
so
the
the
metric
isn't
stable
and
ready
for
translation
until
that
review
period
is
ended.
G
We
would
sync
up
the
matrix
translations
into
the
chinese
version,
as
you
mentioned
there
may
be.
Some
have
some
exact
exceptional
case
may
have
a
lot
of
reward
will
work
things
on
some
single
metrics,
but
most
of
the
time
there
are
only
some
single
or
small
change
for
the
matrix.
So
it
would
not
cause
lots
of
lots
of
workload
during
this
review
days
or
review
period
so
yeah.
I.
F
What
kind
of
time
period
are
you
thinking
I
mean
yeah
should
mention
two
months,
but
we
don't
want
to.
We
don't
really
want
to
put
any
undue
pressure
on.
Anyone
is
two
months
realistic.
Would
you
need
more
time?
Are
you
thinking
less
time.
G
I'm
not
sure
the
review
period
you
just
mentioned
in
just
30
days,
which
means
four
weeks.
I
think
we
can.
We
can
think
of
the
holidays
every
day
for
that
things,
because,
based
on
our
experience
in
the
past
translation
work
even
for
the
whole
one
matrix
translation,
it
doesn't
take
so
much
time.
E
Are
we
talking
about
the
workflow
for
this
release
or
for
or
for
all
the
the
release
workflow
for
maybe
after
we
have
this
release
and.
F
F
Yeah,
it's
the
future,
not
not
the
current
work.
E
Can
this
be
an
ongoing
thing
like
one
metric
is
ready
during
this
half
year
we
can
have
some,
maybe
augmented,
workflow,
that
because
it's
not
about
a
new
metric
is
released,
sometimes
maybe
some
we
some
some
metric,
they
they
have
been
updated.
But
how
can
we
know
that
which
section
or
exactly
which,
which
place
is
updated?
D
So
we
already
have
a
guideline
for
that.
In
the
dock
say,
the
working
group
makes
any
changes
in
the
original
english
metrics.
They
would
have
to
include
a
label
in
the
pr
or
the
issue
which
refers
to
that
change.
That
says
that,
like
this
particular
pr
needs
some
attention
from
the
translations
community
and
from
that
way
you
could
understand
and
gauge
where
the
changes
are
required
in
the
metric.
F
I
think
that's
a
good
idea,
yeah,
however,
so
I
would
like
to
point
out
so
this
this
document
that
that
yash
has
created
these
are
these.
Are
things
we've
discussed
on
on
how
we
can
streamline
the
process
and
get
the
translations
get
the
chinese
translations
released?
However,
the
the
translation,
the
translation
team?
F
We
we
really
need
your
your
help
with
the
process
in
figuring
this
out,
because
we
don't
want
to.
We
don't
want
this
to
be
a
situation
where
we're
like
look
at
this
handbook.
You
should
do
it
this
way,
you're
doing
the
work
we
would.
We
would
really
love
it
if
you
could
tell
us
the
best
way
to
do
it.
F
So
maybe,
if
you
could
look
at
this
document
and
edit
it
and
and
and
give
us
some
ideas
on
how
you
think
the
process
would
best
work,
you
mean
this
document
right
here.
Yes,.
G
A
No,
this
is
the
so
there's
two
and
just
to
be
clear.
There's
two
documents
like
I
have
flipped
between
one
is
metrics
translation
guideline
document
and
the
other
is
our
agenda,
and
I
I-
and
this
is
the
first
time
we're
sharing
this
document
with
this
group,
so
yeah,
okay.
So
this
is
a
proposed
process.
I
do
think
the
idea
of
having
a
translation,
because
there's
a
repository
for
the
translations
right
kevin.
Yes,
so
allow
you
know
allowing
for
the
creation
of
a
release
folk.
G
F
So
instruction
or
ideas,
so
that's
actually
that's
the
question.
I
think
that's
the
discussion
that
we're
having
here,
it's
like
what
do
you?
What
do
you
want
that
to
look
like
what
do
we
want
it
to
look
like,
so
we
have
some
thoughts
on
what
we'd
like
it
to
look
like
and
that's
what
the
that's,
what
this
document
talks
about
when.
F
You're,
referring
to
the
translations
guidelines
the
translation
guidelines
document,
so
we
we
have
some
general
thoughts
on
on
what
we'd
like
it
to
look
like,
but
we
need
to
know.
We
need
to
know
what
you
would
like
it
to
look
like,
as
well
as
the
translation
team.
So
I
highlighted
that
link
in
the
document
and
and
that's
that's-
a
google
doc
kevin.
So
we
yeah
it's
a
google
doc
and
we
can
tran.
We
can
move
it
to
a
different
document.
If
that's,
if
that's
required,.
A
I
mean
I
think
it
might
be
helpful
to
get
more
eyes
on
it
more
easily
or
if,
in
the
course
of
moving
creating
a
github
repository
copy
of
the
minutes,
perhaps
a
draft
of
the
translations
guidelines
could
be
put
in
that
github
repository
where
we're
keeping
the
minutes
and
then
many
people
could
look
at
it.
Whatever
works.
G
But
that's
fine
for
us,
at
least
for
for
people
who
attend
the
meeting
and
the
people
who
in
the
asian
pacific
community's
members.
I
think,
and
we
we
all
have
access
to
this
school
talk,
okay
from
our
own
land
top
before.
F
F
Okay
on
on
that
translation
guidelines-
page-
if
you,
if
you
look
at
it
towards
the
top
of
the
page,
there
are
four
bold
items:
bold
and
italicized.
F
Those
are
the
those
are
the
high
level
questions
that
that
I
need
to
have
answered
to
help
to
help
coordinate
the
regular
release
and
the
trans
and
the
translation
release.
F
So
and
when
we
talk
about
the
translation
release,
what
we're
talking
about
is,
we
would
actually,
we
create
a
basically
a
hard
pdf
copy
of
the
of
the
metrics.
It's
a
snapshot
in
time.
This
is
the
this
is
the
release
of
the
metrics.
So
it's
the
the
metrics
release.
It's
the
one
time
we
the
one
time
we
do
a
freeze
on
our
metrics
and
the
rest
of
the
time
we
we
work
on
them
so.
G
F
Would
be
really
helpful
and
if
you,
if
you
would
like,
if
the
translation
team
would
like
to
meet
with
with
the
team,
that's
doing
the
metrics
release
and
chat
further,
we
we
would
certainly
be
open
to
that.
F
E
A
A
F
Right
yeah,
so
the
chaos
translations
repository
is
where
the
where
the
translation
teams
are
are
doing
the
work.
The
mars
repository
is
where
we're
automating
the
release
process,
so
we
will
our.
Ultimately,
we
would
like
our
we'll
point,
we'll
point
our
work
at
the
translations:
repo
to
grab
the
updated
metrics
when
we
do
our
release.
B
E
How
about
we
put
it?
We
put
this
agenda
to
the
next
asia-pacific
meeting.
E
A
So
I
think
next
on
the
agenda
is
the
meetup
from
july
8th
discussion
and
output,
who
has
that.
G
Yeah,
it's
decided.
A
G
Yep,
actually,
I'm
very
I'm
very
wondering
to
the
any
feedback
from
from
there
from
from
week
meeting
that's
the
meeting
about
our
matrix
model.
Do
you
have
any
ideas
to
share
with
us
soon.
A
The
the
metrics
model
was,
it,
was
discussed
and
and
presented
in
the
general
chaos
community
meeting
at
11
a.m.
On
tuesday,
the
tuesday
after
we
met
last
and
11
a.m,
central
daylight
time
in
the
united
states,
which
is
like
middle
of
the
night
for
y'all,
and
we,
I
think
it
received
a
great
deal
of
support
and
positive
by
the
sense
that
this
is
a
useful
idea
to
group
metrics
that
are
used
together
together,
as
the
metrics
model
that
you
proposed
did.
So
I
think
it.
I
think
you
got
a
lot
of
positive
discussion.
C
I
just
want
to
add
that
I
think
people
definitely
were
interested
in
it,
a
hundred
percent.
I
think
they
wanted
to
take
a
little
more
time
to
kind
of
read
through
it
and
think
about
it.
So
I
would
like
to
propose
that
we
bring
it
back
to
the
community
this
coming
tuesday.
It's
a
great.
C
Of
circle
back
around
and
see
if
we
can,
because
we
didn't
actually
like
document,
I
don't
think
a
lot
of
the
the
verbal
feedback
that
was
given
maybe
a
little
bit,
but
I
think
people
wanted
a
little
time
to
kind
of
mull
over
it
and
think
about
it
and
then
offer
their
their
feedback.
So
if
that
would
be
okay,
we
can
circle
back
on
it
on
tuesday,
if
that's
okay,.
G
G
Yeah,
we
are
looking
forward
to
the
things
more
moving
forward
and
if
you
need
any
help
and
support
on
that,
we
would
like
to
do
so
online
things,
because
we
have
already
have
some
a
lot
of
discussion
around
the
symmetric
model.
So
if
you
need
more
input
on
thinkings,
we
can
add
more
about
it.
Maybe
even
we
can
discuss
together
about
it
next
time.
F
Yeah,
I
would,
I
would
just
like
to
say
I
I
really
appreciate.
I
really
appreciate
that
work.
The
this
has
been
a
concern
for
me
for
for
a
while
the
different
ways
we
can
categorize
model
and
and
display
metrics.
F
So
currently
the
way
we're
the
way
we
are
kind
of
organizing
them
by
working
group
is.
Is
it's
a
good
way
to
get
the
work
done,
but
it's
not
the
best
way
to
present
the
metrics.
So
so
I
really
appreciate
this
work
and
I'm
it's
an
area
that
I
I'd
like
to
see
more
on.
C
C
I
think
the
thing
that's
going
to
be
tricky
for
us
is
to
figure
out
how
to
display
that,
on
the
website
and
or
other
places
how
to
you
know,
let
people
visualize
that
I
think
that's,
maybe
the
piece
that
we
will
have
to
do
some
some
experimentation
with,
or
you
know,
get
some
get
some
creative
ideas
in
there,
because
that
seems
to
be
the
thing
that
you
know
it's.
C
It
makes
sense,
but
also
like
we
want
to
make
it
make
sense
for
everyone
so
because
it
makes
sense
to
us
because
we're
very
familiar
with
you
know
how
the
metrics
work
and
how
they
interact
with
each
other.
So
that
would
be
the
only
piece.
I
think
that
it,
you
know,
might
be
a
little
difficult
to
to
come
together,
but
I
think
it's
awesome.
C
F
I
do
have
some:
I
have
some
prototype
prototype,
metrics
displays
and
navigation
that
we've
that
we've
built
in
the
past
with
the
idea
of
giving
people
different
ways
to
view
the
metrics
and
one
of
the
one
of
the
things
that
was
kind
of
slowing
us
down
on
that
was
the
was
actually
the
the
website
migration
issues.
F
So,
following
following
website
migration,
we
can
probably
start
kind
of
building
that
feature
and
the
the
initial
thought
is
that
we
we
we
kind
of
create
several
different
ways
of
of
categorizing
and
displaying
the
metrics
and
and
kind
of
create
a
way
for
people
to
almost
almost
pick
their
their
categorization
and
display
it
on
the
website.
So
yeah
yeah.
A
A
F
We
didn't
have
ownership
of
the
website
prior,
so
the
linux
foundation
owned
the
owned
the
website.
So
there
was
there's
a
lot
of
functionality
that
we
didn't
have
access
to.
A
So
limitations
on
our
ability
to
edit
update,
add
plugins
yeah
trend,
making
translations
automated
and
easy.
I
think
the
this
trend,
this
migration,
probably
enables
a
lot
of
the
things
in
the
mars
project.
G
G
You
know
we
have
one
the
whole
day's
event
last
week
last
last
thursday
in
the
morning,
we
have
all
the
presentations
through
the
video
provided
by
by
you
guys,
saying
it's
beta
and
and
match
and
vinyl,
and
we
also
pre.
We
also
have
a
lot
of
presentations
from
different
people
from
from
king
from
celia
and,
as
you
can
see
from
disliked
channel,
we
already
shared
all
the
videos
and
the
presentations
documentations
on
the
dropbox.
G
G
China,
yeah
exactly
and
and
I
and
in
the
afternoon
we
spent
almost
a
half
day
to
to
discussion
all
the
topics.
As
I
mentioned
here,
we
have
two
two
sessions
of
discussion
in
the
first
round
discussion.
We
we
discussed
the
two
topic.
We
have
two
topics.
First
topics
is
about
thinking
of
this
pass
factor
and
elephant
factory
metrics
used
in
communities
and
the
other
topics
is
the
next
thing:
how
to
measure
operational
operation,
events
or
activities
like
meet
up
on
that
day,
successful
or
not.
G
So
we
got
people
ideas
who
attend
the
the
this
meetup
and
have
some
output
viewpoint
so
for
the
best
factor,
as
you
can
see
that
at
least
some
as
some.
Actually
we
have
lots
of
discussions
around
that.
I
just
released
some
an
interesting
viewpoints
output
so
for
the
bus
factor.
G
We
all
believe
that
this,
the
key
contributors
is
very
important
for
the
communities
and
we
have
to
identify
their
values,
and
so
that's
the
key
things
for
for
the
community
to
keep
growth,
health
and
the
viewpoint
too,
that
actually
this
from
the
from
the
investigation
after
we
do,
they
do
some
measuring
so
for
some
companies
or
industry-oriented
open-source
communities.
G
So
this
k
person
and
they
become
the
key
person
or
not
or
they
leave
the
community
or
not
or
join
the
community.
It
does
have
they
have
this.
He
has
nothing
to
do
with
with
with
their
their
own
personal
readings.
It's
just
because
the
people,
the
people
who
who
joined
the
company,
how
interest
or
how
investments
on
this
community
are,
we
lost
the
interest
from
this
community.
G
So
that's
the
things
we
found
out
that
and
and
and
for
the
elephant
factor.
We
also
have
two
viewpoints,
and
first
one
is
that.
G
G
You
know
as
a
kilos,
so
then
they
think
they
can
trust
this
company.
This
community's
product.
B
I
would
maybe
disagree
with
that
just
a
little
bit,
especially
on
the
especially
on
the
risk
side.
So
what
what
I've
seen
at
vmware
is
that
certain
companies
that
lots
of
people
trust
to
do
the
right
thing
in
open
source
projects
haven't
been
so
even
so.
So,
let's
talk
about.
Let's
talk
about
google
firmware
is.
B
So
so
the
google
example
would
be
so
if
you
look
at
projects
like
istio
and
k-native,
google
convinced
other
big
companies
like
vmware,
for
example,
ibm
red
hat
others
to
contribute
loads
of
code
to
istio
and
k-native,
and
they
said
that
they
were
going
to
contribute
those
to
the
cncf
and
we
contributed
a
lot
of
time
and
effort
and
code
to
those
projects.
B
And
then
google
changed
their
mind.
So
we
requested
google
to
do.
B
Their
mind
and
for
some
of
these
projects
like
we
were
able
to
get
some
neutral
governance,
at
least
from
k-native,
but
google
still
owns
the
project
for
istio.
I'm
I'm
not
super
happy
with
their
governance
right
now,
but
it's
you
know.
I'd
say
that
one's
probably
less
important
to
us
than
k
native,
but
you
know
the
other
example
you
can
look
at
recently.
Is
you
know
things
like
elastic
where
they've
re-licensed
elastic,
search
and
cabana?
B
Source
anymore,
because
they've
licensed
it
under
a
license:
that's
not
open
source
and
similarly,
projects
like
grafana,
for
example,
have
been
re-licensed
under
under
a
license
that
not
all
companies
are
are
happy
with
so
we've
also.
You
know,
we've
also
got
grafana
embedded
in
some
of
our
products,
and
we
have.
We
have
customers
who
aren't
happy
with
the
license
that
it
was
re-licensed
under.
So
now
we're
looking
at
what
our
what
our
options
are.
B
You
I
agree
with
you.
A
lot
of
people
aren't
looking
at
this
as
a
risk.
I
think
that
they
should
be.
G
G
A
B
B
G
Okay,
okay,
I
think
the
next
topic
is
about
how
to
barrier
operational
operation
events
or
activities
successful
or
not.
Actually,
this
topic
is
hosted
by
june
june.
Would
you
like
to
share
share
some
thinkings
from
you.
A
Oh,
I
may
be
able
to
fix
that.
That's
right!
Try
now!
Oh
wait
a
minute.
I
have
to
stop
sharing
yeah.
Maybe
try
now.
H
H
This
is
our
meeting
schedule
and
this
is
our
meeting
yeah
picture.
H
Yes
and
and
then
you
can
see,
we
have
a
lot
of
wechat
we
charge
public,
which
are
public
accounts,
to
show
our
meeting.
So
we
can.
We
can
see
this.
This
is
200
200,
86,
yeah
yeah
this
like
this,
so
we
have
kills,
kill,
kills
account
and
open
unit
account
and
men's
ball
account
and
some
other
account
count
to
show
our
meeting
and
in
the
in
the
middle
meeting
and
weekends.
A
G
G
E
H
H
And
18
18
yeah
18
people
write
this
question
so.
H
100
five
five
people:
they
are
developer.
A
H
And
on
this
we
can
say
in
our
meeting:
they
come
from
zero
percent
from
slack.
H
H
Yes,
yes,
so
they
mostly,
and
they
want
to
know
in
this
meeting,
they
want
to
communicate
with
communicate
with
with
our
kill,
kills
people
and
they
want
to
know
they
want
to
know
more
metric
from
from
kills
like
this.
We
can
see.
H
So
the
important
thing
is:
oh,
you
can
see
this
most
people
and
most
people
involved
do
an
open
source
job.
They
all
came
from
company
and
they
and
they're
all
from
like
this
sorry,
I
I'm
not.
H
G
Is
a
survey
result
as
you
can
see.
The
first
question
is
the
people
who
who
contribute
the
open
source
communities?
Is
it
government?
Is
it
conquering
investment
purpose?
G
It's
all
for
full
time
to
join
the
community
contribution,
or
this
is
just
a
personal
interest,
so
the
first
the
first
bucket
you
can
say
that
the
most
of
people
who
attend
the
open
source
community?
Actually
it's
from
company.
G
So
it's
to
let
us
to
let
us
the
full
time
to
attend
the
community's
activities
like
contributions
or
attending
the
events
and
and
the
second
bucket
is
showing
them
the
company
because
of
the
company's
investment
investment.
I
can
attend
it
at
part-time
and
in
the
last
two
and
the
the
last
two,
it's
a
16.66.
G
It's
about
universities,
research
projects.
G
Have
intention
to
attend
basic
open
source
communities,
so
this
is
the
top
three.
G
G
That
I
I
think
it's
slightly
different
from
the
survey
I
can
see
from
from
index
foundations
away
and
from
other
surveys
from
europe
and
north
america,
because
I
can
see
so
lot
a
lot
of
people
from
europe
and
and
north
america.
They
they
have
some
personal
interest,
so
they
attend
these
communities.
G
Okay,
okay,
I
gotta
try
my
best
to
translate
the
whole
things.
This
question
actually
is.
G
So
what
are
the
ways?
Your
open
source
program
quantifies
the
success,
so
that's
mostly
so
how
to
marry
the
community's
success
or
health
health,
so
the
the
the
top
number,
the
the
biggest
number
is
83
83.3
3.,
it's
about
contributors,
number
of
contributors
and
the
the
the
second.
The
biggest
number
is
61.11
it's
about
upstream
contributions,
so
which
means,
and
these
two
metrics
for
for
company
or
communities
communities.
They
think
it's
it's
a
very
important
matrix
for
for
for
the
communities
to
measure
their
community
success.
G
And
also
we
have
some
other
questions
about
fewer
license
violations
and
the
faster
compliance
process,
but
yeah
yeah.
The
next
page
is
about
what
are
the
areas
your
company
has
most
benefited
from
from
open
source
programming
yeah
and
the
biggest
number
is
about
increased
increase
the
speed
and
it
abilities
in
the
development
cycle,
so
yeah
yeah
yeah.
G
The
last
thing
it's
about
yeah,
it's
about
technology
areas,
so
your
company
focus
on
so
the
first
one
is
about
ai
machine
learning
and
and
data
analysis
and
the
next
one
is
it's
a
it's
a
blockchain
and
the
next.
I
think
you're
saying
you
can
understand
cncd
and
yeah.
The
next
is
about
cloud
and
and
the
next
is
about
container
and
container
under
visualization
and
that
works
and
and
the
networking
and
edge
sorry.
This
is
iot
and
iot
and
embedded
the
next.
E
G
About
networking
and
edge
and
open
hardware,
and
about
some
security
security
system
and
the
web
application
development
and
others.
So
so
you
can
see
the
most
people
from
this
meetup
are
coming
from
the
areas
of
the
motion
planning.
H
Yeah-
and
this
is
the
chaos
matrix-
we
try
to
find
out
which
metric
is
very
useful
for
this
meeting
meeting
for
this
meeting,
so
we're
trying
to
find
out
which
matrix
we
just
find
out
common,
matrix
and
event
diversity
to
to
metric
the
speaker,
such
as
presents
present
speaker
and
family
friendlies.
H
Diversity
exists
like
this
and
the
another
is
value,
for
example,
our
g
value,
our
company
value.
So
we
just
found
out
this
metric,
and
maybe
we
maybe
other
people
can
get
us
some
more
matrix
to
to
metric
one
meeting.
A
A
A
H
This
is
wechat.
This
is
a
friends.
H
E
E
G
Successfully
transferred
attracted
to
the
community
coming
contributions.
A
H
A
H
Yeah
yeah,
then
we
can,
we
can
keep
keep
keep
going,
keep
careful
see
those
people's
contribute
in
the
next
weekly
or
next
next
week.
Oh.
A
Okay,
good
wow,
okay,.
H
H
So
this
is
our
our
matrix,
so
where
the
could
you.
H
G
Okay-
and
we
can
see
that
most
of
most
attention
days
coming
from
the
companies
and
universities
is
18
in
total
and
personally,
the
people
is
not
belong
to
the
companies
and
the
universe.
Universities
is
it's
very
small,
and
most
people
do
this,
their
the
their
role
or
care,
and
their
role
is
developers
or
engineers
and
also
they
how
they
can
guide.
G
This
meetup
information
is
mostly
coming
from
their
friends
and
not
from
some
medias
trans
media's
producted,
and
we
have
some
thinkings
how
to
translate
more,
how
to
translate
more
people
who
attend
those
meet
up
or
events
and
finally
attracted.
G
The
users
or
committee
or
developers
of
communities,
if
there
are
any
battery
to
to
let
them
attend
those
meet
up
and
and
also
if
we
found
more
engineers
or
developers,
have
more
interest
on
our
chaos
communities.
Maybe
we
can
how
more
thinkings
are
about
how
to
help
those
developers
or
engineers
to
attend
our
communities
yeah.
That's
all
the
things
that
we
have.
A
Right
we
appreciate
the
update,
it's
very
helpful,
to
know
where
the
asia,
pacific
community
and
the
beijing
meetup
went
in
terms
of
people's
interests
and
and
whatnot.
So
thank
you
very
much
for
sharing
all
that,
I'm
also
more
knowledgeable
about
where
beijing
is
in
china
than
I
was
before.
I
saw
this.
A
Map,
so
that's
a
we'll
take
that
I
we're
a
little
bit
over
time
and
a
few
people
had
to
leave,
but
if
there's
not,
I
think
this
is
a
really
great
meeting
and
thank
you
very
much
everyone.
Thank
you
for
sharing
all
that
wonderful
news
and
we'll
see
you
in
a
couple
weeks.