►
From YouTube: CHAOSS Asia Pacific Community Call 7-28-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
All
right
so
welcome
everybody
to
july
28th
every
for
everybody
on
this
call.
It's
not
july
29th,
yet
for
anybody,
asia,
pacific
call.
So
let's
see,
if
you
could
add
yourself
to
the
minutes.
That
would
be
great.
I
think
everybody
has.
We
have
a
few
things
on
the
agenda
for
today
and
I
think
the
I'll
wait
for
elizabeth
on
the
the
other
one
on
the
promoting
of
the
asia
pacific
call,
but
I
think
I'd
like
to
talk
a
little
bit
about
the
translation,
so
there's
been
quite
a
bit.
A
That's
been
happening
with
respect
to
the
translation
so
nico-
I
don't
know
if
nico,
I
don't
know
if
you're
familiar
with
this,
but
we're
translating
the
metrics
into
a
variety
of
different
languages
and
at
the
moment
we're
kind
of
working
through
the
process
by
which
this
would
get
done.
So
we
I
read
it
somewhere,
so
yeah.
A
The
idea
is
right
that
we
haven't
it's
a
good
idea
to
do
these
translations,
but
it's
harder
to
put
this
process
into
practice,
and
so
a
lot
of
people
on
this
call
are
part
of
the
translations
repository
so
and
then
josh
is
a
google
summer
of
code
student
who's
been
working
with
ritik
as
well
on
the
metrics
release
process.
So
how
do
we
automate
the
metrics
release
so
as
working
groups
develop
metrics?
A
So
I'm
going
to
turn
it
over
to
yash
for
a
second
to
talk
about
kind
of
where
we're
at
at
the
moment,
with
respect
to
to
how
we're
thinking
about
doing
translations
so
josh
do
you
you
need
to
share
your
screen
or
anything.
I
just
shared
my
speech.
Can
I
do
it?
How
do
I
need
to
post
questions
there?
You're
good
now.
A
B
So
we
are
essentially
trying
to
create
a
process
which
defines
from
right
from
the
very
beginning
when
the
metric
ideas
really
is,
you
know,
discussed
in
the
working
group.
So
once
the
idea
is
discussed,
we
formulate
a
metric,
then
we
create
a
pr
to
the
working
group
and
we
add
them
to
the
original
working
group
repositories.
B
So
what
we
are
trying
to
do
is
create
a
process
that
would
help
the
translations
community
know
that
a
particular
metric
has
been
updated,
changed
or
a
new
metric
has
been
released.
So
it
involves
a
lot
of
things
and
there
are
some
very
easy
things
to
miss.
For
example,
the
working
groups
often
debate
on
each
particular
word,
so
those
changes
can
go
unnoticed.
B
B
So
I
believe
kevin
had
a
few
questions
and
we
have
some
answers
to
them
and
we
would
like
everyone
to
just
take
a
look
and
if
they
want
to
add
their
suggestions,
if
they
have
anything
else
to
add,
it
would
be
really
helpful.
So
the
first
question
kevin
pointed
out
was
how
should
the
english
metrics
release
team
signal
that
the
metric
needs
to
be
translated
so
currently,
for
that
we
have
a
release,
notes
issue
in
each
working
group
repository,
for
example.
B
B
So
yeah,
so
we
want
to
reference
that
issue
and
from
there
we
want
to
say,
like
hey,
the
translations
community
can
take
a
look
at
that
issue
and
know
what
changes
have
been
done
to
what
metric.
Additionally,
we
also
want
to
create
label.
The
prs
that
affect
the
metrics
with
say,
needs
translation
attention
or
any
of
that
particular
sort
of
label
that
could
help
them
know.
A
So
it
sounds
like
there
are:
are
there
more
ways
of
signaling,
so
the
first
would
be
the
use
of
the
the
issue.
A
The
metrics
release,
issue
correct.
Yes,
in
that
issue,
you
open
the
issue.
A
B
How
do
you
propose
to
do
that?
So
what
we
want
to
do
is
like.
Let's
say
we
have
a
pull
request
in
the
common
working
group
that
adds
a
new
metric,
for
example.
We
have
this
one
here,
so
supposing,
if
this
pr
gets
merged-
and
we
add
a
new
metric,
what
we
essentially
want
can
do
is
reference
the
issue
number
of
the
candidate
release
metric
like
we
can
link
those
two
things
and
we
would
get
a
tag
here
that
hey
this
issue
has
been
referenced
in
this
pr.
A
B
A
Don't
we
have
a
group?
Yes,.
C
C
Yeah,
I
have
a
question
when,
when
will
this,
when
will
this
process
happen
like
before
the
before
the
release,
the
data
off
the
release.
B
Oh
so
this
would
be
a
continuously
updating
process
like
each
time
the
working
group
decides
like
hey,
we
want
to
add
a
new
metric,
so
they
would
have
to.
You
know
reference
this
issue,
so
this
would
be
an
ongoing
process
and
not
necessarily
just
before
the
release,
but
it
would
be
something
that
would
be
occurring
continuously.
C
Because
I
noticed
that,
maybe
is
this-
the
common
metrics
of
glossary,
I
think
there.
If
you
can
look
into
the
issue
list.
I
think
I
I
can
already
saw
some
metric
through
these
candidates.
C
Yeah
I
saw
some
candidates
and
what
we,
what
we
wish
is
if
we
can,
just
once
it
becomes
a
candidate,
and
we
can
just
simultaneously
continuously
trust.
It
translate
it
into
chinese
because
we
kind
of
we
are
working
on
automate
this
process
like
call
some
api
to
do
the
first
version
of
translate
translation
and
because
we
will
rely
on
reviewers
to
review
it.
So,
and
we
wish
this
during
this
process,
we
can
discuss
the
content,
especially
for
those
folks
in
chinese
community.
C
E
A
A
C
Yeah,
if
you
think
this
is
ready
to
be
translated,
you
can
add.
C
Like
another
design
tag
and
maybe
to
attach
the
commit
message
with
with
that
specific
metric
in
the
repository
okay.
B
D
A
Yeah,
so
the
way
that
we
do
releases
is
we
have
a
formal
release
every
six
months
so
yeah
august
over
september
and
then
six
months
after
that,
and
that's
just
how
we
version
the
full
set
of
metrics
for
release.
But
we
also
allow
working
groups
to
release
a
metric
anytime
during
that
six
month
period
and
that's
just
what
we
call
the
continuous
metrics
release.
A
And
so
tomorrow
or
even
today.
The
dei
working
group,
for
example,
may
release
a
metric,
I'm
not
sure,
but
like
for
example,
they
could
so
that
that
metric,
when
it's
released
today,
will
go
under
community
review
for
a
month.
Even
though
it's
not
part
of
the
official
release.
Yet
but
it'll
go
under
community
review
for
a
month
and
then
it'll
become
a
chaos
metric
period
and
then
in
september.
D
D
D
Because,
because
when
I,
when
I'm
do,
when
I'm
doing
the
translation
in
the
past,
like
two
or
three
months,
I
found
that
there
are
some
metrics
they
mentioned
in
the
content
side.
This
metrics
is
under
review.
Welcome
your
comments,
but
except
those
accepted
this
message
I
didn't
find
any
other
areas
to
to
to
have
those
kind
of
information.
D
Okay,
so
so
I'm
kind
of
I'm.
I'm
quite
hope
that
I
can
there's
there's
some
public
place
that
they
can
tell
me
that
okay,
those
metrics,
are
under
review
and
we
are
waiting
for
your
comments
or
something
like
that.
Okay,
so,
like.
A
It's
a
central
place
where
we
can
track
this,
as
opposed
to
necessarily
here
yeah.
I
wonder
if
let
me
pull
something
up
here.
A
So
josh,
can
you
stop
sharing
your
screen
for
a.
D
D
So,
which
means
in
precise
it's
the
matrix,
is
still
under
discussion.
It's
not
how
I
put
it
in
the
release.
Queue.
Something
like
that.
A
D
D
A
A
D
So
before
we
start
any
translations
like
this
kind
of
review,
we
can
put
pop
up
our
ideas
or
comments
for
this
metrics
and
help
them
to
improve
those
metrics
and
then
when,
when
they,
when
the
group
working
group
think
okay,
this
metric
is
ready
to
to
release
and
they
will
add
a
label
side,
okay,
gratitude,
translation
and
they
we
are
going
to
translate
it
into
chinese
or
any
other
languages.
Okay,
so
that's
right.
A
A
A
A
A
A
A
C
B
D
D
B
C
C
A
So
how
okay,
so
this
is
great.
Thank
you
for
the
feedback,
everybody.
This
is
it's.
I
think
it's
so
interesting
that
how
how
challenging
getting
this
process
together
is
it's
it's
really
and
so
so
yash
the
translation
will
lag
just
a
little
bit.
You
know
what
I
mean
it
just
it
has
to,
because
if
it
ends
up
on
the
website,
then
it's
technically
been
released
by
chaos
and
the
translation
would
simply
just
follow
slightly
yep.
So
completely
okay,.
B
D
A
C
Do
you
think
yeah
for
now
and
I
I
can't
find
anyone
else?
Oh
I'm
I
mean
maybe
waiting.
F
B
So
the
is
the
screen.
Yes,
so
we
fix
this
one.
Thank
you,
everyone
for
your
suggestions.
Moving
on
to
the
next
one,
how
does
the
translations
team
signal
that
the
translations
are
ready
for
release,
so
the
process
is
essentially,
how
do
you
tell
the
kevin
or
english
members
like
the
translations
have
been
done?
They
are
up
to
date
and
we
can
now
proceed
with
the
release
of
translated
metrics.
B
D
B
This
do
we
want
a
review
period
for
translated
methods.
D
I
mean
after
after
the
english
I
mean
the
community
release
of
the
matrix
is
ready
for
tr,
it's
ready
for
to
be
translated,
and
then
the
translation
team
would
start
this
translating
work
and
and
it
should
be
done
by
a
pull
request
and
after
this
pro
request
is
merged.
I
think
this
community
release
metrics
translation
work
should
be
ready
and
after
this
is
for
the
cognitive
release
metrics
and
for
the
official
release,
I
think
it's
only
should
be
done
after
the
official
release
of
the
matrix.
D
A
C
I
was
thinking-
maybe
we,
my
opinion
is
maybe
for
the
release.
We
only
need
the
official
metric
chinese
virtual
metric
with
a
pdf
and
a
version
of
them.
D
Yes,
okay,
we
could
do
this
yeah,
I
I
agree.
I
agree.
Pdf
version
could
be,
could
could
only
be
once
following
by
the
official
release,
but
I
mean
we
have
to
keep
updating
with
with
english
versions
matrix
community
metrics
release.
C
B
B
So
we
have
a
file
that
is
the
primary
input,
so
we
were
actually
thinking
that
after
all,
the
pr's
have
been
done
and
the
translations
metrics
are
ready
for
release.
You
could
simply
go
ahead
and
update
this
yaml
file,
which
would
be
there
for
translations
for
chinese
translations,
and
that
could
be
a
helpful
signal
to
us.
Like
hey.
The
translations
are
now
ready
to
release.
We
have
updated
the
yaml
file.
E
E
Automatic
it's
it's
all
xml
based
diy
scripting,
it's
it's
it's
it's
something
that
was
coded
yeah.
B
B
A
A
B
A
A
B
A
B
A
A
A
D
B
A
Technical
fork
hasn't
been
translated,
so
this
would
just
be
another
signal
that
would
help
us.
It
would
also
elevate
the
work
that's
being
done
on
the
translations,
and
yahoo
had
pointed
out
that,
like
we
don't
want
to
necessarily
have
the
translations
occurring
only
every
six
months
or
I'm
sorry,
the
release
of
the
translations
occurring
every
six
months.
It
would
be
very
beneficial
to
get
the
translated
metrics
out
to
a
community
sooner
rather
than
later,
yeah.
The
more
we
can
do
that
the
better.
So
I
think
this
would
be
a
good
place
to
do
that.
A
B
B
C
B
So
yep
we'll
have
two
weeks
I'll
update
the
dock.
With
the
most
recent
change
discussions,
we
are
having
right
now
and
I'll
ask
on
the
slack
channel
to
do
a
final
review,
so
how
much
time
is
needed
and
when
should
translations
be
released?
I
think
we
covered
this.
Do
we
release
it
regarding
lists
or
of
whether
or
not
translation
is
complete?
B
We
have
an
answer
that
we
only
release
when
the
translation
team
signals
to
us
that
the
metrics
are
ready
for
release.
Do
we
need
a
review
period?
This
could
be
partially
overlapping
with
the
community.
C
B
B
B
B
And
thanks
for
adding
this
suggestion,
I
added
it
to
the
actual
doc,
like
the
suggestion
is
mainly
like
we
could
have
a
glossary
or
a
comparison
table
to
ensure
consistent,
enable
between
the
english
and
the
translated
language.
So
I
just
went
ahead
and
added
the
suggestion.
B
D
Because
because
I'm
thinking
of
the
the
community
matrix
release,
you
know
we
have
to
do
some
update,
we
have
to
do
from
which
base
to
to
start
or
the
the
the
matrix
update.
So
I
suggest
to
add
some
commit
hash
to
mark
that.
Okay,
we,
the
previous
translation,
is
start
from
here
and
we
can.
We
can
go
on.
A
B
A
But
it
works,
that's
the
classic
like
developer.
Don't
worry
it's
horrible,
but
it
works.
A
I
can't
understand
it,
maybe
not
horrible,
but
you
can't
understand
it,
but
it
works
so
and
josh.
Thank
you
for
your
kind
of
very
thoughtful
step
through
of
this
process
to
receive
feedback,
so
very
much
appreciated
on
your
organization
and
your
clear
set
of
questions
that
you
had
for
everybody
and
then
thank
you
for
everybody,
for
your
feedback
to
josh
and
to
the
team
that
we
can
improve
this
process.
I
think
you
know
I'd
like
to
say
like,
as
we
two
things
one
as
we
develop
this
process
so,
for
example,
australia.
A
A
B
A
I
think
that
would
be
super
helpful,
especially
as
we
like
we
have
the
opportunity
here
to
in
the
asia
pacific
call
to
talk
through
this
every
day,
but
as
we
offer
this
process
to
say,
spanish
translations
like
it
might
be
nice
to
have
that
artifact
available,
just
as
an
image
saying
here's
how
we're
doing
it
in
other
places,
and
it
might
be
easier
to
understand
for
other
communities
as
we
move
forward
sure
we
can
have
that.
That
would
be
excellent,
all
right,
everybody.
We
are
at
the
end
of
time.
A
Yes,
so
that
was
actually
on
the
agenda,
so
the
metrics
model
that
you
made
so
now
we've
been
waiting
to
move
the
website,
so
the
metrics
model,
again
just
for
everybody,
is
ways
that
we
can
draw
together.
Chaos
metrics
in
kind
of
meaningful
contexts
or
meaningful
scenarios
that
are
helpful
to
others,
and
so
I'm
reading
for
kevin
to
move
the
website
and
we're
going
to
start,
including
the
metrics
model
and
personas,
for
example,
on
the
website
for
people.
So
this
is
now
something
we
can
do
so,
yes,
we
are
going
to
include
it.