►
From YouTube: CHAOSS.AsiaPacific.May.6.2020
Description
CHAOSS.AsiaPacific.Community.Call
A
B
A
So
today,
I
thought
we
just
start
this
meeting
by
just
welcoming
everybody
greeting
everybody
kind
of
giving
you
an
overview
of
the
the
chaos
project
and
then
I
think
it
might
be
nice
to
spend
a
little
bit
of
time
agenda,
setting
so
kind
of
what
the
new
people
on
the
call
are
interested
in.
And
what
you'd
like
to
talk
about
in
what
you
think
might
be
important.
So
anything
else
people
want
to
add
to
the
agenda.
A
All
right
so
folks
can
chime
in
as
they
would
like
to
so
this
doesn't
have
to
just
be
me
talking
talking
the
entire
time,
so
I'll
start
with
the
the
chaos
overview
right.
So
the
aim
of
chaos
is
it's
kind
of
far-reaching
at
this
point,
so
I
think
briefly.
The
aim
of
chaos
is
to
I
always
say,
provide
transparency
and
actionability
around
open
source
community
health,
so,
as
different
organizations
have
an
interest
in
the
open
source,
that's
in
their
organizations
or
being
released
as
part
of
their
organizational
strategy.
A
Understanding
the
health
of
those
open
source
engagements
is
pretty
important,
so
the
chaos
project
is
kind
of
one
of
the
and
we'd
like
to
say
important
projects
trying
to
aim
to
uncover
health-related
issues
in
these
situations.
So
anybody
want
to
add
anything
dawn
or
Shawn.
Moving
in
this
for
a
while.
A
A
So
from
a
community
perspective,
I
think
you
can
even
just
see
from
the
guestlist
the
time
here
we
have
a
number
of
different
people
representing
kind
of
a
number
of
different
corners
or
come
and
come
at
the
chaos
project
with
a
variety
of
different
interests.
So
we
have,
for
example,
dawn
who's
on
this
call,
who
is
from
pivotal
now
VMware?
We
have
folks
from
Huawei.
You
can
see
folks
from
universities.
A
A
That
have
an
expressed
interest
in
understanding
of
open
source
community
health.
I
would
say
that
the
the
different
organizations
have
generally
the
same
goals
and
understanding
health
deep
down
contextually.
It
might
be
a
little
bit
different,
but
fundamentally
understanding,
Community
Health
seems
to
be
fairly
consistent
across
all
of
these
organizations,
which
I
think
it's
super
helpful
because
it
makes
the
conversations
pretty
normal
in
our
meetings.
A
So
that's
what
the
the
project
is
all
about,
so
community
wise
I'd
say
we
have
ash
I
mean
probably
well
over
a
hundred
people
that
participate
in
a
variety
of
different
ways,
whether
it's
from
the
events,
whether
it's
working
in
metrics,
whether
it's
working
in
software,
it's
a
it's
a
pretty
healthy
group
of
people.
So
that's
that's
kind
of
a
community
in
nutshell.
All
right.
A
The
chaos
project
is
probably
best
considered
to
be
built
around
a
couple.
Different
things.
One
is
the
software
and
the
other
is
the
metrics,
so
I
guess
I'll
start
with
the
metrics,
even
though
there
which
don't
list
the
metrics
themselves.
So
what
we're
doing
is
we're
identifying
metrics
that
help
improve
the
transparency
of
open
source
community
health.
A
The
aim
is
to
identify
and
develop
metrics,
not
necessarily
the
deployment
of
those
metrics,
but
to
develop
the
definition
of
metrics
that
help
improve
transparency
around,
say,
risk
or
improve
transparency,
around
diversity
and
inclusion,
and
so
each
of
the
working
groups
would
say
they
work
in
isolation,
but
they
work
kind
of
focused
on
the
metrics
that
are
relevant
to
those
areas
of
interest
right
so
far,
so
good.
Looking
at
other
people
on
the
call
summary.
A
All
right,
so
this
link
the
Kaos
community
metrics
link
is
the
definitive
set
of
metrics
that
have
been
released
by
the
Kaos
community
..
So
the
work
that's
done
in
the
working
groups
occurs
in
github
and
within
that
work
you
may
see
metrics
say,
for
example,
Shaun
is
participating
in
the
risk.
Working
group
and
Don
is
participating
there,
leading
the
common
working
group,
there's
going
to
be
work
that
they're
doing
that
isn't
necessarily
part
of
the
release.
A
A
So
that's
this
needs
to
be
kind
of
a
abundantly
clear,
because
I
think
this
does
create
some
confusion
that
there's
a
list
of
metrics
on
the
webpage
and
then
there's
a
list
of
metrics
in
the
github
repositories.
Yes,
they're
related,
but
the
github
repos
represent
the
work
in
progress
and
the
web
page
represents
the
released
list.
A
All
right,
so
you
can
take
a
look
at
those
we
have
processes
by
which
we
do
releases
so
from
from
development
within
the
working
group
on
a
new
metric
to
an
open
period
for
community
feedback
on
that
metric
and
then,
ultimately,
getting
it
onto
the
webpage.
So
all
of
these
are
fairly
I'd,
say
fairly
well.
A
Articulated
processes
released
we're
getting
them
there,
so
the
workflow
should
be
fairly
straightforward
and
so
for
anybody
on
this
call
I
don't
know
that
the
the
call
would
be
to
participate
in
every
working
group
just
because
that
would
take
a
lot
of
time
and
a
lot
of
meeting
but
to
identify
a
working
group.
That's
that's
of
interest
to
you.
So
if,
if
diversity
and
inclusion
is
a
issue,
that's
that's
near
and
dear
to
you
or
important
for
your
organization
participate
in
the
diversity
and
inclusion
working
group,
which
has
its
own
meeting.
C
A
And
its
own
github
repository
and
its
own
set
of
metrics
that
is
releasing
if
risk
is
important
to
you,
then
dissipate
in
risk.
So
that
would
probably
be
my
initial
recommendation:
don't
go
into
every
working
group.
It
would
just
be
a
little
too
much,
probably
just
in
terms
of
a
time
commitment,
all
right.
E
The
one
thing,
the
one
thing
that
I
just
want
to
add
is
that
the
the
working
groups
really
are
focused
on
defining
metrics.
So
this
is
really
not
about
writing
code
to
gather
the
metrics.
A
lot
of
the
work
that
we
do
within
the
working
groups
is
about
defining
how
we
should
measure
something.
So
really
anyone
can
participate
in
the
working
groups.
So,
if
you,
you
know
if
you're
normally
writing
documentation
or
if
you're
normally
doing
you
know
things
other
than
development,
you
can
certainly
engage
in
the
working
groups.
E
I
mean
they're
great
for
developers
too,
and
certainly
the
software
working
groups
are
a
little
more
focused
on
on
development,
but
anybody
can
help
us
define
these
metrics.
So
really
it's
really
good
to
have
additional
perspective.
So
how
how
you-
or
maybe
your
company-
or
maybe
your
region,
looks
at
a
particular
metric
and
how
you
might
define
it.
We
found
that
that
varies
quite
a
bit
with
different
different
perspectives,
so
it's
good
to
have
more
more
and
more
people
involved
and
engaged
in
defining
some
of
these
metrics.
A
Excellent
point
and
listening
to
talk
I'll
even
add
on
to
that
I
mean
I,
can't
say
that
there's
ever
been
a
time
that
individual
representing
themselves
or
an
organization
wanted
to
develop
a
metric,
and
we
have
ever
said
no,
that
that's
not
a
metric
that
is,
is
ability
to
be
defined.
Sometimes
we
have
to
find
where
it
fits
best
in
which
working
group,
but
to
Don's
point
we're
very
open
to
the
number
of
different
perspectives.
A
B
D
A
The
John's
point
rate,
so
the
metrics,
then
what
we
do
is
we
in
the
cannes
project.
We
don't
want
to
just
have
metrics
for
metrics
sake.
So
just
developing
the
definitions
of
a
metric
is
excellent,
but
we'd
like
to
see
those
metrics
provide
meaningful,
real-time
data
for
folks
right,
so
that
you
can
make
decisions
and
at
the
moment,
within
the
chaos
project,
there
are
I
would
say
two
two
very
active
software
tools
that
are
focused
on
the
deployment
of
the
chaos
metrics,
as
well
as
perhaps
some
other
metrics
that
haven't
been
defined.
A
Then
I'll
guess
I'll,
add
to
that.
There
are
certain
metrics
that
are
not
easily
deployable
via
software,
so,
for
example,
within
diversity
and
inclusion,
many
of
those
metrics
can't
be
gathered
simply
from
trace
data
or
electronic
tracer.
That's
like
have
repository
activity,
so
the
chaos
project
also
works
on
processes
that
allow
us
to
capture
metrics
that
may
not
be
deployable
via
software.
A
So,
for
example,
we
have
a
diversity
and
inclusion,
diversity,
inclusion,
inclusion,
badging
program,
which
is
more
of
a
somewhat
automated,
but
more
of
a
human
process
to
identify
the
metrics,
the
events
or
what
we
source
projects
are
looking
to
reveal.
So
we're
constantly
a
point.
Is
we're
constantly
working
on
processes
to
make
sure
that
all
of
the
metrics
that
are
deployed
in
chaos
see
the
light
of
day
good,
all
right
good?
A
So
that's
honestly,
I
think
I'll,
that's
20,
15
20
minutes
of
chaos
as
an
overview,
so
without
going
into
too
much
detail,
maybe
I'll
stop
here
for
a
second
and
see
if
folks
have
questions
or
would
like
to
make
comments
or
or
even
if,
if
you
you've
tried
to
approach
the
chaos
project
via
the
website
or
some
other
forum
and
you've
had
problems,
because
that
would
be
great
to
know
what
those
problems
might
be.
It's
all
kind
of
leave
it
open
for
just
a
second
okay,
I.
C
I
I
know
you
organize
the
common
good
group
and
I'm
wearing
how
we
were
very
interesting,
our
open
source
project
who
contributes
for
our
project.
You
know
we
don't
want
to
really
have
the
animal
factor,
that's
the
Oh
self
to
contribute
to
the
project.
We
want
more
and
more
more
and
more
organization
and
company
to
communicate
to
contribute
here.
I
was
asked
gather,
so
we
can.
We
can
click
the
data
from
their
email
commit
commit
ID
email
and
we
can't
recognize
who.
A
C
Which
organizes
organizes
nice,
they
work
for
and
I
know.
Don't
you
just
appropriate
to
two
women
there
and
do
you
have
some
some
function?
Some
can
come
work
out
later,
because
some
of
we
we
must
follow
the
GDP.
Are
you
know
the
priority,
the
people's
priority?
We
do
yeah
yeah,
and
so
we
only
have
their
name
and
their
email
email
ID.
So
how
can
we
recognize
where
organization,
as
the
contributor
come
from,
do
how
an
idea
about
it?
Thank
you.
E
That's
a
really
good
question
and
I
think
that
you've
you've
identified
something
that
I
think
is
one
of
the
I
think
it's
one
of
the
hardest
things
to
define,
because
so
many
people
use
they
use.
Multiple
email
addresses
they
use
personal
Gmail
addresses
and
it
can
be.
It
can
be
quite
difficult
actually
to
to
find
the
organizational
affiliation
for
a
lot
of
these
people.
So
we
do
have
an
organizational
affiliation
metric
defined
within
within
common.
That
provides
some
suggestions
and
both
of
the
tools
have
auger
and
grimore.
Labs
have
have
tools
that
help
with
this.
E
So
grimoire
has
a
tool
called
sorting
hat,
which
helps
you
combine
identities.
You
can
combine
them
based
on
names.
You
can
combine
them
based
on
an
email
address.
It
has
some
some
different
ways
of
doing
that
and
that
can
help
with
some
things.
I've
noticed
this
actually
being
particularly
challenging
actually
with
with
people
in
China,
because
a
lot
of
them
use
multiple
names,
so
they
use
some
of
their
configurations,
have
their
Chinese
name.
Some
of
them
have
the
name
that
they
use
with
English
speakers.
E
B
So
what
would
auger
does
is
it
relies
on
the
email
address,
that's
in
the
get
log
and
that's
publicly
shared
in
the
get
log
and
we
use
github
and
get
lab
and
probably
in
the
future,
bitbucket
to
basically
query
to
see
what
the
user
ID
is
for
a
particular
email.
We
can't
ask
it
for
all
the
emails
for
a
user
ID,
but
we
can
say:
hey.
We
have
this
email
in
a
commit.
Can
you
door
in
a
issue?
Usually
it's
going
to
commit.
B
Can
you
tell
us
who
that
what
your
user
ID
is
for
that
person
and
so
through
that
we're
able
to
map
them
to
what
we
call
a
canonical
user?
So
we
have
a
aliases
table
that
map's
different
email
addresses
to
the
same
canonical
user,
but
we
don't
yet
have
any
way
for
you
to
say
which
email
you
want
to
be
the
canonical
one.
B
The
canonical
one
is
the
first
one
we
find
in
the
commit
log,
so
it's
a
little
bit
accidental
and
when
we
find
and
for
organizational
affiliation
generally,
we
have
a
we've
actually
as
a
organization
case
as
building
a
list
of
corporate
and
project
top-level
domain
names,
so
like
google.com
or
yahoo.com
all
resolve
to
those
corporations
and
when
a
person
makes
a
commit
with
a
new
affiliation.
We
make
a
change
affiliate.
B
We
make
a
change
in
affiliation,
the
first
time
we
find
that
new
corporate
email
in
their
in
their
get
log
or
in
the
api's
that
get
lab
and
github
return.
So
it's
that's
imprecise.
There's
I
think,
there's
ways
to
explicitly
assign
people
a
corporate
affiliation
as
well,
but
we
haven't
our
selves
made
that
easy
to
say
what
day
it
happens
on
it's
just
we
go
by
the
first
contribution,
yeah.
E
B
E
A
A
B
What
understand
the
get
logs
have
been
explicitly
excluded
right
now
from
GD
P
R,
okay,
they're
considered
publicly
available
data,
but
as
you'll
hear
on
the
grimore
lab
podcast
that
will
air
three
or
four
weeks.
Probably
it's.
It's
always
a
topic
of
discussion.
So,
if
you're
deploying
inside
of
your
organization,
one
of
these
tools,
I
think
you
have
more
latitude
than
if
you're
deploying
outside
of
an
organizational
context,
because
in
inside
of
an
organizational
context
effectively,
you
have
some
kind
of
work
relationship
with
the
person
and
resolving
their
identity.
B
One
of
the
main
reasons
gdpr
exists
is
because
of
targeted
advertising
and
the
betrayal
of
privacy
by
content
oriented
sites,
and
since
most
software
work,
it
happens
at
the
command
line
and
they
had
yet
found
a
way
to
serve
ads
to
get
users
and
for
that
reason
I
don't
think
software
developers
using
yet
are
as
of
yet
targets
of
the
ad
industry.
So
through
our
dialogues
and
that
way,
I
think
we're
I
mean
we're
filed.
We
certainly
want
to
follow
the
spirit
and
intent
of
any
laws
that
any
government
passes,
but
it's
a
moving
target.
C
Yeah,
it's
very
helped,
I
think
I.
Think
the
information
from
public
well-well-well
about
is
out
a
page.
That
she'd
appears,
for
example,
linking
information
you
can
we
can.
You
can
get
to
the
API,
firmly
King
and
because
most
of
the
contributor
uses
in
China
they
use
Kukui.
You
cook
you
email
and
in
American
they
use
Gmail,
so
I
think
it's
under
the
same
safety
is
a
best
practice.
Practice
is
for
us
that
we
can
lean
from
it.
Thank
you.
Thank
you.
Don't
force
I
could
see
how.
A
E
In
addition
to
that,
they
have
some
other
sources
so
like
their
their
CL.
A
system
affiliates
people
with
organizations
so
like
VMware,
has
a
corporate
CLA
with
the
with
the
CNC
app
so
I'm
under
that
one,
and
so
because
I'm
under
that
that
legal
agreement,
they
know
that
I
work
for
worked
for
pivotal
and
now
VMware,
so
I
think
they
also
use
some
of
that
data
as
well
to.
A
E
C
D
A
You're,
looking
at
kind
of
pursuing
this
I
might
recommend
that
you
join
perhaps
one
of
the
software
recall
so
grimore,
lab
or
auger,
which
could
help
in
answering
questions
about
the
deployment
and
making
this
information
invisible
to
you
and
eating's.
Those
meetings
are
often
I
mean
they're
open
to
answer
these
types
of
questions,
they're,
not
the
grimore,
lab
and
Hager
calls
are
not
just
there
to
only
focus
on
advancing
the
software
period.
It's
to
provide
an
open
platform
by
ask
questions
in
terms
of
how
they
can
do
things
with
the
software.
F
Everyone,
yes,
hi,
I'm
Frank
as
far
as
I
know,
I
think
things
yes
also
used
some
services
to
match
the
intensity.
They
have
of
different
people.
Different
contributor,
maybe
and
actually
I-
want
to
introduce
myself
first
I'm,
a
PhD
student
from
China
and
majored
in
computer
science
and
very
interesting
open
source
and
then
I
used
to
work
for
Alibaba
Oh
spoke
on
community
initialisation
and
actually
last
year,
I
gave
my
speech
about
my
work,
open
source
and
I
Shanghai,
and
that's
where
I
met.
F
B
I
think
from
a
chaos
perspective
of
we
have
maintained
a
lot.
We've
long
maintained
a
position
of
agnosticism
about
assigning
value.
So
it's
a
metric
as
here
is
my
pick
score
good
or
bad.
We
we
rely
on
the
software
teens
context,
the
people
running
it
or
interested
in
it
to
define
relative
health
of
projects
using
the
metrics.
There
are
research
efforts
underway
that
Matan
eyes
research
groups
to
try
to
categorize
patterns
of
behavior
in
projects,
so
that
projects
where
people
are
committing
and
creating
issues
and
commenting
on
things
in
statistically
similar
ways.
B
E
This
is
one
thing
I'm
talking
about
a
lot
internally
with
my
colleagues
at
VMware
as
well.
Is
that
you
know
we
have.
We
have
projects
that
that
operate
differently
than
others,
so
I
have
kind
of
a
standard
set
of
project.
Health
metrics
and
you
know
occasionally
someone
gets
concerned
because
they're
like
oh
well,
you
know
my
project
isn't
isn't
healthy,
because
the
way
that
you're
measuring
this
doesn't
make
sense
for
my
project
and
for
my
part,
that's
that's
fine.
Your
project
is
different
and
we
just
need
to.
E
We
try
to
come
up
with
how
you
how
you
might
measure
something
but
I
think
in
a
lot
of
cases,
because
because
some
of
these
communities
are
different,
I
think
how
you
interpret
the
results
is
really
really
what
changes,
because
in
a
lot
of
cases
you
can
measure
something
you
know
similar
way.
So
you
can,
you
know,
use
sort
some
of
the
same
metrics,
but
how
you
interpret
them
I.
Think
it's
going
to
be
different
depending
on
the
type
of
project
and
what's
important
to
that
project.
B
E
F
I
understand,
thank
you
and
the
second
one.
Yes,
I,
don't
know
we
Marella
and
auger
are
both
sort
of
dashboard
projects,
so
it
deploys
the
metrics
to
shows
metrics
on
the
website.
But
if
there
any
port
checking
hey
I
was
trying
to
improve
the
magics
automatically
like
gave
notifications
to
community
containers
to
improve
responsiveness
or
even
answer,
frequently
asked
the
questions
automatically.
Something
like
that.
There.
B
There
is
a
augur,
has
a
slack
bot
that
is
gonna,
be
I
just
saw
at
work
last
night,
so
it's
going
to
be
released
like
probably
this
week,
which
lets
you
essentially
assign
an
auger.
You
tell
the
slack
bot
where
your
auger
dashboard
is
and
and
what
kinds
of
notifications
you
want
for
which
repositories,
and
it
will
send
you
the
most
anomalous
indications
in
your
collection
of
repositories
every
day
and
you
get
to
tell
it
with
a
maximum
number
of
anomalous
indications.
B
You
want
to
get
so
if
you're,
monitoring
a
thousand
repositories-
and
you
say
you
want
ten
messages
a
day-
you'll
get
the
ten
most
statistically
out
of
normal
indications
that
occurred
in
that
collection
of
repositories
in
a
day
in
a
slack
channel
that
you
invite
the
slack
bot
to
there
may
or
may
not
be
a
demo
of
that
in
the
augur
meeting
in
an
hour
and
a
half
I
fail
to
ask
my
developer
to
be
there,
for
that.
So
I
have
to
see
if
I
can
get.
B
B
B
I
can
Anna's
guarantee
a
demo.
It
took
it's
quite
late.
It's
at
11:00
a.m.
it's.
It's
like
three
hours
later
than
this
call,
unfortunately,
but
it
is
recorded,
it
is
recorded
and
those
recordings
I
generally
been
tweeting
them
out
via
augurs
twitter
account
and
also
retweeting
them
via
casas
twitter
account,
and
I
can
give
you
that
info
as
well.
F
C
B
I
think
the
we
have
a
I
think
the
value
working
group
has
been
doing
some
work
in
that
area.
I
actually
did
my
dissertation
work
on
network
analysis
and
my
first
research
and
open
source
stuff
perused
a
lot
of
network
analysis.
So
we
have.
We
have
one
google
Summer
of
Code
student
this
summer,
who
has
focused
on
that
as
well
for
the
augur
project.
So
I
don't
know.
B
E
My
PhD
was
also
partly
focused
on
network
analysis
of
open
source
source
projects
seems
to
be
a
common
common
thread
I,
so
the
grimoire
labs
they
they
have
done
some.
They
have
some
forgiveth
a
column,
not
the
not
the
dashboards,
with
the
components
widgets
or
whatever.
They've
had
some
in
the
past
that
have
been
focused
on
network
analysis
that
have
actually
been
pretty
interesting,
so
so
that
might
be
a
good
place,
a
good
place
to
start
frankly,
what
what
I
did
for
my
PhD
is
I.
E
E
You
can
download
everything
into
an
auger
database
and
write
database
queries
that
pull
things
out
based
on
you
know,
whatever
network
analysis,
definitions,
you're
using
in
particular
wasn't
one
of
the
things
I
found
with
a
lot
of
the
tools
that
are
targeted
more
community
managers,
the
network
analysis
tends
to
be
relatively
rudimentary
and
what
I
found
so
I
started
my
PhD
in
2015.
So
the
tools
were
a
lot
less
mature.
B
Cities
logs
and
if
you
wait,
each
interaction
like
a
commit
the
same
or
if
you
look
at
the
size
of
a
commit
to
consider
the
level
of
contribution
and
participation
in
the
network.
I
mean
I.
Think
Don's
probably
seen
a
lot
of
this
like.
If
you
just
take
the
straight
log
data.
It's
not
it's
too
gooey
to
draw
anything
useful
from.
A
A
Listening
to
this
conversation,
there
might
be
two
working
groups
that
might
be
applicable.
One
I
think
is
value,
so
the
aim
of
the
value
working
group
is
to
try
to
to
develop
metrics
that
can
be
used
just
to
come
to
the
chase,
but
to
justify
engagement
in
open
source.
So
oftentimes
there's
a
challenge
in
kind
of
articulating
the
value.
That's
that's
generated
through
open
source
participation,
and
so
the
value
working
group
is
aiming
at
developing
metrics.
That
can
help
in
that
argument.
A
Internally
and
network
analysis
may
help
reveal
that
that,
if
we're
open
sourcing
a
project,
the
network
that
has
been
created
is
valuable
around
this
particular
piece
of
open-source
software
and
the
other
is
risk.
So
the
risk
working
group
may
also
have
an
interest
that,
if
you
can
demonstrate
the
through
network
analysis
that
there's
a
problem
in
the
network
around
a
particular
piece
of
open-source
software,
and
that
may
be
interesting
as
well.
Yeah.
G
And
but
I
think
I
think
they
like
what
I
understand
so
far.
We
work
mostly
a
higher
level
of
abstraction
because,
like
what,
if
you
want
to
use
a
network
analysis
and
certain
things
that
what
don't
have
said
on
all
yours
contributed
might
be.
You
want
to
see
the
between
Izumo
field
and
things
like
that.
It's
a
very
specific
area
that
you
are
applying,
but
now
the
the
metrics
themselves
is
like
a
high
level
of
things
that
you
can
consume
and
interpret
see.
Do
we
want
to
make
findings?
G
It
might
also
reveal
certain
things
that
we
like,
not
necessarily
at
the
problem,
but
some
kind
of
links
that
if
things
works
together,
if
these
two
components
works
together,
they
can
come
up
with
high
efficiencies
and
things
like
that.
So
all
those
type
of
analysis
who
only
come
after
we
have
the
well.
We
can
apply
the
matrix
in
an
open
source
ecosystems
to
find
whatever
your
specific
goals.
G
E
Absolutely
I
would
have
it
agree
with
that.
You
know,
and
the
other
thing
is
there
might
be
some
opportunity
to
define
some
network
metrics
kind
of
from
scratch
and
I.
Think
probably
the
value
group
is
a
good
place
to
start
there.
The
other
the
other
place
I
would
go.
Is
the
grimoire
labs
meeting
as
well?
F
A
Any
other
questions
these
are
great.
Thank
you
for
asking
these
all
right.
So,
just
for
folks,
we
we're
branding
these
meetings
in
about
five
minutes,
so
I
think
maybe
we
could
spend
the
last
five
minutes
just
talking
about
any
agenda
items
that
you
might
wanna
to
see
in
the
next
meeting.
That's
in
two
weeks
on
May
20th.
A
There
are
things
that
you'd
like
to
start
talking
about
in
this
call,
if
you'd
like
to
continue
to
use
this
call
kind
of
as
an
update
on
what's
going
on
in
other
parts
of
the
chaos
project,
but
I'm
happy
to
go
any
direction
here,
a
bit
of
both
that's
totally
fine
as
well.
So
I'll
leave
this
open
a
bit
to
see
if
people
have
thoughts
on
and
what
they'd
like
to
talk
about.
A
A
What's
you
know
the
last
two
weeks
the
timing
is
challenging
to
make
the
calls
during
the
week
and
this
one
fits
well
timing,
wise
I,
think
a
summary
would
be
useful
for
folks,
just
to
kind
of
tell
you
the
developments
that
are
going
on
and
the
working
groups,
any
developments
that
have
been
going
on
software
or
wise
and
I
can
provide
us
a
summary.
Absolutely
no
problem
on
that.
We
get
these
summaries
in
our
in
our
other
community
calls
the
ones
that
are
a
little
bit
less
friendly
for
Asia
Pacific.
A
E
I'd
say
to
that
it
could
be.
You
know
we
can
use
this
meeting.
However,
however,
people
want
to
use
it.
So
you
know,
if
there's
stuff,
that
you
want
more
information
about.
We
could,
you
know
see
if
we
can
have
an
expert
come
in
and
talk
about
a
particular
topic
that
you're
interested
in.
If
you
have
some
metrics
that
you've
been
gathering
that
you
want
some
feedback
on,
we
cure
any
of
you
could
do
a
demo,
and
we
could
you
know
as
a
group
sort
of
brainstorm
around
it.
There
are
lots
of
different
things.
E
A
C
F
A
D
E
B
Didn't
know
some
of
our
media
outlets
and
notes
and
in
the
chat
link
as
well
as
in
the
notes
of
the
meeting
at
the
top
so
like.
If
you
want
to
follow
us
on
Twitter
or
look
at
some
of
the
old
things
on
YouTube
or
make
contributions
directly
to
the
working
group
repos
or
look
through
them.
There's
lots
of
places
to
sort
of
poke
around
and
get
started.