►
From YouTube: CHAOSS.Asia-Pacific.Community.May.20.2020
Description
CHAOSS.Asia-Pacific.Community.May.20.2020
A
Go
ahead
and
hit
the
record
button
so
hi
this
is
me,
xx,
xx,
xx!
This
is
the
second
Asia
Pacific
chaos
call
so
thanks
for
joining
everybody.
The
minutes
are
in
the
chat,
put
them
in
there
again.
If
you
could,
click
on
that
link
and
add
yourself,
that
would
be
great
I.
Think
probably
I
should
send
out
a
call
for
participation
for
this
meeting
more
regularly
as
we're
starting
trying
to
get
this
off
the
ground.
You
don't
I,
mean
I,
think
the
other
yeah
all
fairly
well
attended
at
this
point.
A
lot
are
yeah.
A
So,
just
honestly
we
can.
My
thought
was
at
least
for
today
is
always
kind
of
give
updates
as
to
what's
been
going
on
in
the
chaos
project.
For
the
last
couple
weeks,
for
those
who
haven't
been
able
to
attend
the
weekly
calls
or
any
of
the
working
group
meetings,
does
that
sound
okay
for
folks
yeah,
all
right
so
over
the
course
of
I
guess:
yeah,
I'm
glad
that
Don
and
Sean
are
both
on
here
as
well.
A
You
can
all
help
me
remember
what
we've
done
in
the
last
two
weeks
and
venue
too
so
I
think
maybe
one
of
the
biggest
things
over
the
last
couple
weeks
is:
we've
decided
to
not
run
chaos.
Con
North
America
this
summer,
not
even
as
a
virtual
event,
I
think
with
with
so
many
virtual
events
that
are
going
on.
We
just
we,
we
kind
of
thought
time
was
best
spent
doing
other
activities
that
could
benefit
the
chaos
project.
A
So
in
that
regard,
we
would
like
to
encourage
people
to
participate
in
the
chaos
podcast
so
either
listening
to
the
chaos
podcasts
or
being
a
member
of
the
chaos
podcasts
or
joining
in
for
part
of
the
conversation.
That
would
be
fantastic,
I,
wonder
if
there
would
be
use
and
having
a
podcast
from
folks
in
China
I.
If
that
would
be
helpful
at
all
talking
about
how
open
source
health
is
being
considered
in
organizations
in
the
asia-pacific
area
and
what
people's
thoughts
are
on
that,
but
I
think
that's
something
that
we
could
probably
pretty
easily
arrange.
A
Also
for
those
of
you
that
have
an
interest,
we
would
encourage
you
to
set
up
blogs
so
to
start
blogging
about
what
your
interests
are,
even
with
respect
to
open
source
community
health.
Why
you
care
about
open
source,
community
health,
so
I
think
those
are
the
two
things
that
we're
gonna
start
focusing
on
this
summer.
So
in
the
notes,
could
somebody
go
into
the
community
minutes
and
drop?
Remember
how
we
have
some
notes
on
the
podcasts
and
the
blogs
like
how
to
participate.
A
C
A
A
A
A
couple
of
the
working
groups
have
what
we're
calling
rolling
releases,
so
the
chaos
project
is
on
kind
of
a
six-month
cadence
of
doing
full
metrics
releases,
but
in
between
those
six
months
the
working
groups
can
do
what
we're
calling
continuous
metrics
releases
or
rolling
releases
reading
and
release
one
metric
at
a
time
for
public
comment.
I
think
there's
one
metric
open
right
now
for
public
comment.
I
think
it's
out
of
common
am
I
right
about
that.
Yeah.
B
No
it
there
was
a
evolution,
continuous
release,
one
I
believe
that
went
out,
but
that
was
before
the
last
call.
Okay
and
those
are
I-
think
they're
indicated
on
the
website
now
in
some
way
or
are
they
just
indicated?
I
forget
what
we
decided
there,
they
github
repos
and
they
get
AB
repos
right.
So.
A
B
A
So
so,
from
a
metrics
perspective,
honestly
folks
that
are
on
this
call
the
way
just
to
kind
of
reimburse
eyes.
The
way
that
we
develop
metrics
in
the
KS
project
is
really
to
propose
metrics
within
a
working
group.
So
if
you
have
a
metric
that
you
think
is
a
reasonable
thing
to
take
a
look
at
with
respect
to
risk
or
with
respect
to
evolution
or
with
respect
to
diversity
and
inclusion.
A
Metrics
that
you're,
using
within
your
organization,
metrics
that
you've
discovered
in
academic
writing
metrics
that
you
think
might
be
useful
for
others.
So
really
the
goal
here
is
to
to
encourage
people
to
bring
metrics
ideas
forward
and
then
in
the
working
groups.
We
help
you
and
work
with
you
to
get
those
metrics
into
a
template
that
is
standardized
and
readable
for
all.
So,
for
example,
looking
at
dun
dun
means
the
chaos
common
working
room
and
time
to
close
metric
I.
Don't
even
have
the
foggiest
idea
where
that
began
and
who
began
it
may
be.
A
A
So
as
a
metric
that
everybody
thought
was
useful
and
we
worked
together
over
the
course
of
probably
a
month
or
maybe
a
month
and
a
half
to
formalize
and
articulate
what
that
metric
is
as
relevant
for
everybody.
So,
as
you
have
metrics,
we
do
encourage
you
to
bring
them
forward
and
we
will
help
you
get
a
format.
That's
that's
useful
and
released
for
everybody
right.
C
Yeah
and
we're
always
working
on
defining
metrics
and
the
various
working
groups
too.
So
if
you
don't
have
anything
specific
that
you
want
to
work
on,
but
you
know
that
you
want
to
help
us
define
some
metrics.
You
can
show
up
to
any
of
the
any
of
the
working
group
meetings
or
have
a
look
at
the
zoom
recordings
or
the
notes
from
the
meeting.
You
can
see
what
we're
working
on
and
they're
usually
documents
that
you
can
just
comment
on
or
contribute
to.
C
If
you
have
some
input
so
there's
lots
of
lots
of
different
ways
to
contribute.
You
don't
necessarily
need
to
bring
a
new
metric,
although
those
are
those
are
certainly
welcome,
because
we're
always
trying
to
decide
which
metrics
to
work
on
next
and
if
somebody
has
one
that
is
interesting
to
them.
That
generally
pushes
things
up
in
the
priorities.
A
A
Does
anybody
have
any
thoughts
about
when
we
should
do
the
cadence
for
our
regular
releases
I?
Think
it's
fair
to
even
talk
about
it
here.
So
typically,
we
have
done
regular
releases
where
we
release
say
a
dozen
new
metrics
in
relation
to
as
two
conferences
and
because
conferences
are
gonna,
get
a
little
bit
weird.
E
A
B
B
Since
we
have
the
the
interim
release
process
going
now,
but
a
couple
times
a
year,
I
think
would
make
it
would
show
the
world
what
we're
doing
on
a
more
frequent
basis
and
the
the
cadence
of
like
OSS
summit,
North
America,
which
is
done
at
the
end
of
June
and
July.
Early
July
and
FOSDEM
doesn't
seem
like
those
done
like
obviously
it's
too
late
to
do
one
for
OSS
na
because
it
had
been
in
the
fall
historically,
but
that
that
cadence
doesn't
seem
wildly
off
to
me.
A
Okay,
twice
here,
yeah
I'm
kind
of
inclined
for
twice
a
year
and
I
do
know
that
Kevin
Kevin
is
the
the
person
who
helps
run
the
website
and
kind
of
package,
the
metrics
for
release.
So
if
you
go
to
Kaos
community,
slash
metrics
that
work
is
done
by
Kevin.
I
do
know
that
the
continuous
metrics
release
like
releasing
those
over
the
course
of
the
six
months
makes
his
job
easier.
A
C
Mean
it
kind
of
acts
as
a
it
acts
as
a
forcing
function,
because
the
thing
about
continuous
releases
is
that
there's
no
there's
no
deadline
like
we
just
release
things
as
we.
You
know,
as
we
finished
them,
but
I
always
feel
like
when
there's
a
release
coming
up,
there's
there's
some
pressure
to
get
a
little
bit
more
done.
So
I
feel
like
as
a
working
group
like
in
the
common
and
diversity
inclusion,
the
ones
that
I
participate
in
I
think
the
deadlines
help
us
get
more
metrics
out
the
door.
D
D
A
A
All
right,
so
that's
that's
metrics
and
then
again
the
other
other
part.
The
other
half
of
the
chaos
project
is
software
right.
So
we
have
it's
almost
like
programs
at
this
point.
It's
how
I'm
starting
to
think
about
it,
because
we
have
programs
software,
other
initiatives
that
are
intended
to
bring
the
software
to
light
right,
sorry
or
intended
to
bring
the
metrics
to
light.
So,
as
we
have
say,
I'll
just
stick
with
the
time
to
close
metric.
A
You
know
the
the
metric
definition
by
itself
is
is
useful,
but
it
could
be
more
useful
if
we
can
actually
deploy
that
metric
in
a
piece
of
software.
So
we
can
get
the
results
in
front
of
people,
so
the
ks
project
is
always
working
on
finding
ways,
whether
it's
in
software
or
in
say,
like
the
diversity
and
inclusion
badging
program
of
bringing
those
metrics
forward.
So
people
can
actually
use
them
to
make
meaningful
decisions
around
community
health.
So
one
of
the
pieces
of
software
and
Sean's
on
the
call
right
now
is
augur
and
Sean
weeds.
B
B
B
And
the
other
thing
I
would
show
you
is
we
have
a
little
insight
thing
that
we're
gonna
be
making
a
few
changes.
We
need
to
make
sure,
but
basically
it
shows
you
to
your
most
anomalous
occurrences
where,
if
you
take
a
normal
period
like
say
a
year
or
two
years
to
Train
what
are
the
types
of
events
in
which
repose
that
are
most
outside
of
that
normal
range
periodically
and-
and
you
can
look
at
a
group
of
repose,
so
these
are
twittering
repose
and
you
can
see
the
total
commits
and
I.
Don't
know.
B
If
you
see
my
and
then
you
can
see
the
issues,
so
you
can
see
some
repositories
use
github
issues,
others
don't
and
if
I
go
to
the
emoji
project,
for
example,
I
can
see
who
the
major
contributors
are
lines
per
commit
and
then
something
of
a
cadence
for
pull
requests
and
issues
per
week
and
also
code
changes
per
week.
So
you
can
see
significant
action
for
some
reason
here
at
the
end,
beginning
of
2020
for
that
repository
and
that's
what
augur
does
in
addition,
in
the
back
end
and
I'm,
looking
looking
for.
B
The
schema,
but
one
of
the
cool
parts
of
auger
is
there's
a
lot
more
informations
information
in
the
schema.
I,
don't
know
where.
Actually
this
was
just
redone,
so
I
don't
know
where
the
schema
actually
is
in
the
documentation
anymore,
but
we
have
fairly
detailed
information
about
pull
request
issues.
B
At
this
time
we
have
pull
request
information
that
includes
all
the
files
in
the
pull
request,
all
of
the
commits
in
the
pull
request,
and
then
that
can
be
met
just
with
commit
data,
and
we
have
a
mechanism
that
we're
using
to
resolve
contributors
so
that
individuals
who
use
multiple
email
addresses
can
be
resolved
to
the
same
individual,
which
helps
us
understand
how
many
different
contributors,
a
project
really
has,
and
we
also
have
a
very
recently
released.
Not
quite
questions
schema
I.
D
B
B
B
B
Pull
requests
issues
that
sort
of
thing,
and
so,
if
you
want
to
understand
the
data
inside
of
our
schema
this,
this
link,
which,
if
someone
could
add
to
the
notes
I'll
figure
out
where
it
is,
is
also
helpful
and
very
recently,
we've
released
a
slack
bot
for
augur
and
what
the
slack
bot
does
is.
It
lets
messages
from
what
we
call
the
insight
worker
that
is
tied
very
closely
to
the
insights
on
your
insight
page
and
essentially
it
will
send
you.
B
B
Oops,
it's
as
I
get
it
wrong
and
Twitter
that
lab
stuff
that
I
own
apply
and
then
I'll
see
I
can
decide
which
repos
that
I
want
to
track.
I
think
actually
I
have
this
functionality
where
I
could
just
move
them
all
at
once
now
and
I
can
say,
I
want
to
watch
commit
count.
New
contributors
lines
changed
issue
whatever
I.
B
Maybe
I
only
want
the
ten
most
anomalous
issues
a
day
and
that
saved
my
Augie
settings
and
then
all
I
have
to
do
is
add
Augie
to
slack
and
it's
gonna
say
here's
the
things
that
Augie
needs
to
have
access
to
in
my
select
channel.
So
this
is
my
personal
place
in
a
slack
channel
and
then
I
will
have
messages
that
I
exchanged
with
Augie
below.
B
A
B
This
is
where
I
can
go
to
edit
that
list
of
repos
that
I'm
tracking
and
the
only
reason
we
haven't
widely
publicized
this
yet
is
I-
want
to
get
rid
of
the
need
to
specify
the
port
that
your
back
end
of
augur
is
running
on.
A
B
It's
not
a
random
forest.
It's
a
it's,
not
random
for
some
other
kind
of
machine
learning
algorithm
that
is
essentially
looking
for
over
a
period
of
say
a
thousand
days.
What's
the
normal
level
of
behavior
for
comments
on
an
issue
in
repository
and
if
you
have
some
of
some
event
detected
in
that
repository
for
that
metric,
that's
outside
of
the
range
of
what
is
normal
likes.
D
C
B
Correct
it's
all
based
on
the
repo.
So
the
way,
the
way
that
it
works
is
each
each
morning
at
9:00
a.m.
UTC,
which
was
what
we
did
sited,
would
be
the
standard
time
of
day
will
make
it
configurable
later,
but
that
basically
prevents
Europeans
and
Americans
from
getting
a
bunch
of
anomaly
notifications
as
they're
leaving
work
each
day
and
we'll
work
it
out
to
detect
local
time
zones
in
a
very
near
near
release.
B
B
B
B
In
google,
Summer
of
Code
students
are
working
on
some
really
interesting
projects.
We've
got
three
folks
working
on
machine
learning,
related
things
and
one
person
really
interested
in
feedback,
so
right
now
or
thumbs
up
or
thumbs
down
or
whatever
on
any
of
these
messages
that
we
will
catch
for
that
feedback
and
then
use
that.
A
A
B
Now
I
think
the
church
is
or
grimore
lab
is
doing.
Bi-Weekly
we're
doing
weekly
right
now,
only
because
we
have
a
number
of
google
Summer
of
Code
students
and
we
think
we're
gonna
have
a
lot
of
new
things
to
talk
about,
and
it's
also
a
way
that
I'd
like
to
engage
those
students
in
the
community.
So.
A
A
D
E
Hi
I'm
a
graduate
student
from
China
right.
You
hear
me
yes,
so
I've
participated
in
some
of
your
working
groups
and
especially
folks
on
the
TI
working
groups
and
I've,
been
particularly
interested
in
DTI
badging
program
so
and
I'm,
considering
applying
ecology
as
ot
and
since
the
program
idea
have
already
been
approved
by
Google
right
I,
wonder
during
this
phase.
Apart
from
getting
to
know
more
about
the
project
and
involve
myself
with
mentors
and
maintainers
what
other
things
should
I
do
like?
E
A
So
thanks
for
your
interest,
that's
great
so
I
think
just
so.
You
know,
process
wise,
I,
think
I,
don't
think
Google
has
assigned
the
number
of
slots
for
organization
yet
so
I
still
think
we're
waiting
on
the
google
season
of
docs
to
determine
how
many
people
we
can
support
so
I
think.
That's
still
so.
I
would
wait
on
the
application
right
now,
just
in
terms
of
I'm
not
sure
how
many
slots
we're
gonna
have
so
but
I'm
happy
to
communicate
with
you.
There's
also
are
you
on
slack
no.
E
A
That
would
there
is
a
group
that
is
working
on
the
badging
program
and
it's
a
couple
folks
who
are
in
the
Chaos
project
regularly
and
a
couple
people
one
is
an
outreach
e
student
and
one
is
a
google
Summer
of
Code
student
who
are
also
working
on
the
project
and
that
may
be
a
great
place
for
you
to
connect
as
well.
I'm
on
that
channel
as
well
I
mean
we
could
kind
of
talk
through
what
our
goals
and
objectives
are.
With
respect
to
the
badging
program,
if
you'd
like
to
be
part
of
that,
yeah.
E
A
E
D
A
A
B
A
I'll
also
work
to
and
now
make
sure
this
goes
out
on
the
list
to
get
the
announcement
out
so
and
if
you
have
things,
please
feel
free
to
just
send
them
either
directly
to
me
or
to
add
them
to
this
document,
really
all
open
for
things
that
people
want
to
talk
about
on
this
call
right.
So
so
with
that
I
think
I'll.
Stop
the
recording
and
say
thank
you
for
everybody
for
coming
and
again
we'll
be
on
this
call
in
two
weeks.