►
From YouTube: CHAOSS Common Working Group Meeting June 22, 2023
Description
Meeting summary can be found here: https://chaoss.discourse.group/t/common-working-group-meeting-summary-june-22-2023/191
A
A
Welcome
everyone
to
Common
metrics
working
group,
meeting,
June
22nd
2023.
A
I
think
we're
going
to
have
a
few
people
jumping
in
a
little
bit
late,
so
we'll
we'll
try
to
accommodate
them
when
they
come
in.
If
someone
could,
if,
when
someone
sees
people
come
in,
if
they
could
copy
the
the
meeting
notes
and
drop
them
in
on
a
regular
basis,
that
would
be
helpful
so
to
start
on
the
agenda.
Let's
go
ahead
and
we'll
we're
going
to
jump
to
the
bottom
and
the
nod
is
going
to
give
us
an
update
on
the
knowledge
base
restructuring.
B
A
Now
we're
just
getting
the
meeting
started.
Okay,
Bernard
is
going
to
give
us
an
update
of
the
the
knowledge
base
restructuring.
Okay.
So,
but
not
do
you
want
to
share
your
screen.
A
Not
I
can
do
it
or.
C
B
I
have
multiple
screens,
which
I
think
I've
shared
correctly.
Can
you
see
the
pr?
Yes,
okay?
Okay,
so
what
I've
done
is
I
have
followed
this
structure
exactly
I've
deleted
about
chaos.
Can.
A
You
give
everyone
everyone
kind
of
a
high
level,
okay
description
of
what
of
what
you're
doing
and
why
you're
doing
it
just
for
okay,
Bruno
and
who
may
not
be
aware.
B
Yeah
so
I'm
reviewing
the
knowledge
basis
structure
which
we
have
created
in
our
on
GEOS
website
and
I'm,
like
simplifying
it,
keeping
it
and
like
if
I'm,
removing
the
extra
lab
wordings
or
languages
and
unnecessary
files
and
keeping
it
simple.
So
the
there
are
two
like
current
structure
and
there
is
a
proposed
structure
file.
That's
why,
if
I
open
this
I
hope
you
are
able
to
see
this
so.
B
To
see
the
Excel
file
now
yeah,
so
here
we
have
a
current
structure.
That
is
right
now
how
the
chaos
website
about
the
knowledge
base
section
is
displayed.
So
we
have
this
about
section.
We
have
Community
initiatives
and
working
group
where
there
are
so
many
layers
like
one
folder
within
another
folder,
and
so
many
files,
so
I've
tried
to
simplify
data
and
kept
it
and
aligned
it
with
a
governance
structure.
Also.
B
So
what
we
in
the
last
meeting
working
Ruby
proposed
this
structure
here
is
the
one
from
the
existing
to
a
new
one,
where
we
try
to
get
rid
of
about
chaos,
General
FAQ,
Mission
values,
because
these
are
already
on
the
first
page
of
the
chaos
website.
B
So
we
are
trying
not
to
repeat
things
over
the
period
of
time,
so
what
I've
done
is
like
I've
deleted
these
files
within
that
PR
and
then
I
created
a
new
chaos
folder,
where
I
have
this
different
new
pages
Community
initiatives,
these
Pages
were
already
there,
but
I
have
like
pre-structured
and
copied
the
content
to
make
it
more
in
alignment.
So
now
we
have
Community
initiated
and
we
have
working
group
speech.
We
have
local
chapters
and
software
projects,
so
each
of
these
is
like
different
Community
initiatives.
B
Badge
like
di
badging
is
included
in
the
community
initiatives.
Information
about
all
the
working
groups
like
high
level
information
about
these
working
groups
is
in
this
page.
We
have
local
chapters
and
then
which
is
like
Asia
or
Africa
chapter,
and
then
software
model
and
Garrett,
sorry,
grimo
lab
and
all
that
and
then
I
have
not
worked
on
this
particular
section,
which
we
propose
deleting
this
section
but
I
when
I
looked
at
the
content,
I
felt
like
this
should
not
be
deleted.
B
Maybe
I'll
discuss
it
again
and
figure
out
what
should
we
do
with
it?
So
I
have
not
taken
action
on
this.
One
at
governance
was
agreed
as
no
change,
so
there
is
no
change
on
it
and
then
I
have
revised.
This
community
created
a
community
templates
where
I've
kept
this
metric
template
metric
model
template
which
are
already
there
I
just
moved
those
files
in
those
folders,
and
then
we
have
a
community
resources
which
we
have
slide
deck
link
and
images
and
brand
style
logos.
C
C
Is
it
just
makes
me
a
little
nervous
that
you're
gonna
click
merge
and
we're
gonna
be
like
whoops
that
broke
a
lot
of
stuff,
and
so
that's
I
think
that's
mostly
my
issue
that,
like
I,
agree
that
you're
following
the
path
that
we
talked
about,
but
just
that
the
Cascade
effects
of
something
that
touches
60
files
is
that's
a
very,
very,
very,
very,
very,
very,
very,
very,
very
big
PR
right.
B
So
that
is
by
like,
if
this
needs
to
be
merged,
then
somebody
is
ready
to
work
on
the
WordPress.
If
they
don't
work
on
the
word
present
entire
website
will
be
broken
from
their
knowledge
base.
Portion
of
the
website.
B
So
for
this
either
Elizabeth
or
Kevin
has
to
sit
together
or
I
can
sit
with
them
and
then
they
merge
it
and
then
like
map
it
with
the
WordPress
and
then
work
on
it.
A
Okay,
so
I
I,
actually
I
I,
agree
with
Matt
on
this.
The
the
number
of
changes
is
just
I.
Think
it's
too
much.
A
If
we
especially
considering
it's
not
going
to
be
the
this,
isn't
going
to
be
the
first
or
the
last
time
we
go
in,
and
we
added
all
of
this
all
right
so
I
like
that
it
so
it
gives
us
kind
of
a
it,
gives
us
a
base
framework
to
move
forward
on
so
I'm
I
am
tempted
to
just
say:
let's
do
it
and
and
figure
it
out
me.
D
A
Little
more
tracking
that
I'd,
like
that
I,
would
like
to
have,
for
example,
the
like
the
Mars
project,
we're
removing
it
we're
removing
it
from
the
handbook
when
we
do
this,
which
is
fine,
but
ideally
for
that
project.
A
A
Okay,
so
that
if
we
needed
to
track
that
down
individually
at
a
later
date,
it
would
be
easier
to
find
just
just
as
an
example
right,
and
there
may
be
other
files
in
there
that,
for
the
the
same
thing
right.
D
D
B
B
Or
I
can
or
I
can
suggest
one
more
thing
if
you
want
that,
I
am
willing
to
help
in
that,
regardless.
If
I
get
access
to
the
WordPress
and
I
just
understanding
where
the
files
are
linked,
then
what
I've
done
I
can
also
link
those
in
the
WordPress
too,
for
you
and
then
so
that
it
as
somebody
merges
it.
B
Then
I
start
working
on
the
WordPress
and
adding
those
files
back
so
that
WordPress
stuff
is
not
broken
or
somebody
or
you
Kevin,
you
or
Elizabeth
can
sit
with
me
and
I
can
help
you
go
through
and
we
can
collectively
do
it.
A
B
So
if
we
delete
like
this,
entire
four
files
will
be
deleted.
First,
four
files:
can
you
see
them,
but
can
you
see
my
mouse
moving
yep
yeah,
so
these
four
files
will
be
deleted.
These
four
new
files
will
be
created,
and
this
is
like
new
folder
will
be
created
and
then
I
have
not
worked
on
this.
So
this
will
be
right.
Now,
intact,
governance
is
as
it
is.
There
will
be
no
change.
B
Community
templates
is
a
new
folder
that
I've
created
and
I've
moved
these
files,
which
were
already
there,
but
they
are
moved
to
this
separate
folder.
B
C
B
B
A
I,
don't
so
I
don't
know
that
it
would
it's
not
going
to
take
up
very
much
to
to
get
the
website
up
to
date
on
this
yeah,
because
we're
ultimately
we're
only
talking
about
one.
Two
three
four
looks
like
we'll:
have
five
folders?
A
Yes,
most
of
those,
some
of
those
folders
at
least
one
of
those
folders
won't
have
any
documents
in
it.
A
Yeah
the
other
folders
that'll
that
are
there
do
have
documents
that
will
exist
right,
but
it's
really
not
that
many
right
it's
when
we
when
we
count
these
out,
it's
maybe
20
files
tops
yes,.
A
So
we're
doing
this
transition
we're
transitioning
to
a
much
smaller
knowledge
base
with
the
under,
with
the
understanding
that
we
have
to
in
the
future.
We
need
to
create
a
lot
of
new
documents,
so
I
I,
think
I
could
Elizabeth
Ori
or
Elizabeth
and
I
could
probably
knock
this
out
pretty
fast
and
maybe
take
an
hour.
C
D
Game
I'm
game
and
then
maybe
we
can
enlist
the
community
to
help
us
just
like
kind
of
do
an
audit
of
the
website
and
make
sure
we
didn't
miss
anything.
That
would
be
an
easy
thing
to
ask
the
community
to
do
just
look
through
the
website
poke
around
as
much
as
you
can
see.
If
you
see
anything
that
looks
weird
or
empty.
D
But
not
I
have
a
quick
question,
these
first
ones
that
are
deleted
the
about
and
the
FAQ
and
all
that
so
the
about
page.
That's
on
the
website
right
now
is
that
not
pulled
from
GitHub
is
that
straight
in
WordPress,
Kevin
Dino.
B
B
So
if
you
just
open
the
first
page,
like
your
speech
like
mean
Beach,
this
has
all
the
information
on
the
main
page.
Now,
when
we
go
to
the
knowledge
base,
this
information
is
repeated
over
there.
So
the
repeat,
one
is
deleted.
The
main
pages
are
still
the
same
content.
Okay,
perfect.
A
Yeah,
so
for
the
the
about
page
I,
don't
believe
I'm
pulling
that
from
I'm,
not
pulling
it
from
a
knowledge
base,
I,
don't
believe.
But,
okay,
let
me
double
check
so
for
for
those
high
level
pages
yeah
for
the
about
page.
A
Since
it's
a
kind
of
the
first
level
page
I
think
I
wanted
to
keep
that
in
WordPress,
however,
we
were
supplementing
some
of
those
pages
with
with
knowledge
based
Pages
for
Content,
as
as
we
were
going
along,
but
I
don't
believe
we're
doing
that
on
the
about
page
and
we
actually,
as
from
a
design
standpoint,
we
kind
of
we've
moved
away
from
that
a
little
bit.
So
the
ideally
right
now
with
the
website
design
the
those
kind
of
first
level
Pages
stay
in
WordPress,
the
stuff
that
doesn't
need
to
be
changed.
A
In
just
a
second
I'm
logging
into
the
website
now
to
see
if,
if
that
page
or
if
that
page,
oh.
B
D
C
So
as
you're
doing
that,
Kevin
Okay,
so
if
I
guess
I
have
to
go
back
to
the
size
of
this
PR,
but
not
so
like
if
I
don't
think
a
reason
for
pushing
this
through
is
because
you'd
have
to
redo.
B
B
A
Right,
I'm,
not
so
sure,
I
thought
we
had
more
files
in
the
knowledge
base
than
what
we're
showing
here
so
I.
Don't
think
you.
B
No,
so
there
yeah
there
are
a
couple
of
images
in
the
file
which
are
no
longer
used
anywhere
in
the
website,
but
they
are
in
that
folder.
So
I've,
just
like
deleted
those
images.
There's
a
YouTube
image.
There
is
a
Twitter
image.
There
is
a
somebody's.
You
know
what
you
call
Zoom,
meeting,
click
image
or
I've
removed
all
those
clean.
Those
things.
C
B
B
B
So
how
to
contribute
I
have
not
worked
on
this
area,
this
particular
section.
Can
you
see
this
was
because
in
the
last
meeting
we
decided
we'll
discuss
it
more
on
the
next
meeting,
so
I've
not
worked
on
this
section.
B
I
have
not
deleted
these
that
we
proposed
to
delete,
because
when
I
was
looking
at
the
content,
I
felt
like
break
I
need
to
bring
it
back
to
the
community,
discuss
whether
should
be
deleted
or
not
so
right
now
we
have
worked
on
this
section,
this
one
and
then
from
start.
So
these
are
the
things
that
I've
worked
up
to
this
and
then
from
governance.
A
Okay,
so
so
I
guess
what
I
would
propose,
then,
is
that
using
mats
that
the
thing
that
Matt
said
we
had,
we
create
a
pull
request
that
creates
the
new
folder
structure
and
then
you
create
a
full
request
that
creates
new
files
or
all
of
the
new
files.
Okay,
and
we
don't
delete
anything
yet,
but
maybe
in
the
next
knowledge
base
meeting
we
go
through
those
files
individually,
okay,.
B
A
Decide
if
we
want
to
actually
delete
them
or
if
we
want
to
move
them
to
one
of
the
new
folders
okay,
and
if,
if
we
do
move
them
to
the
new
folders
We
could
take
some
notes
on
how
it
needs
to
be
edited
moving
forward.
That
way,
we're
not
just
because
I,
don't
think,
we've
ever
gone
through
and
said:
hey.
We
want
to
keep
this.
We
want
to
keep
this
delete.
This
delete
this
delete.
This
actually.
A
Not
definitively,
though
we
didn't
go
through
every
file
and
make
those
and
make
those
decisions,
we
I
think
we
were
just
kind
of
doing
it
individually
when
we
were
talking
about
certain
certain
things
right.
A
So
there
are,
there
are
files
in
there
that
we
that
we
may
not
want
to
delete
okay,
that
we
haven't
even
that
we
haven't
talked
about
yet,
maybe
so.
B
B
The
images
like
these
are
the
images
these
are
the
images
they
are
not
used.
Now
this
image
is
not
used
anywhere.
This
image
is
not
used
anywhere,
so
I
like
this
image,
I,
don't
know
where
it's
being
used
now,
so
I
have
I'm
trying
to
clean
those
things.
Okay,
so,
for
example,.
B
B
A
So
that
that
is
probably
a
piece
of
chaos
art
that
we'd
want
to
hold
on
to
okay,
so
rather
than
deleting
that
one,
for
example,
maybe
we
want
to
move
that
into
the
actually?
Maybe
we
keep
it
in
imagery
sources
or
or
are
we
I
think
the
the
plan
was
to
actually
store
the
images
in
a
Google
folder?
So
maybe
this
image
gets
actually
moved
to
a
Google,
folder,
okay
right,
because
the
I
think
the
for
the
images
I
think
we
were
talking
about
creating
a
Google,
doc
or
I'm.
A
The
Google
drive
right
right
so
so
my
point
was
some
of
the
some
of
this
stuff
might
actually
be
stuff.
We
want
to
keep
okay,
maybe
some
of
its
logo,
art
that
we
want
to
keep
the
the
badging
passing,
because.
D
A
Might
want
to
keep
so
we
haven't
gone
through
all
of
the
files
and
and
kind
of
made
those
determinations,
so
maybe
okay,
maybe
we
do
that
before
we
delete
it
that
way,
we
don't
have
to
worry
about
as
much
about
yeah
tracking
this
stuff
down
later.
B
B
So
there
are
two
things
in
the
previous
meeting.
It
was
proposed
that
if
we
delete
anything,
we
can
go
back
to
the
archive
at
any
point
in
time
and
retire
because
nothing
is
deleted
in
reality
from
the
GitHub.
So
that
is
where
I
made
this
decision
to
clean
things,
and
if
you
need
to
retry,
we
can
go
back
and
retry
those
things.
That
was
how.
A
C
C
So
then,
maybe
you
don't
need
me
in
Elizabeth,
because
Elizabeth
is
keep
everything
and
therefore
we
need
a
tiebreaker
on
everything.
The
I
had
another
comment
as
well.
C
Oh,
if,
if
we
do
go
through
this
process,
maybe
one
of
the
things
that
you
could
do
to
help
move
us
through
the
conversation
vanad
is,
it
sounds
like
there
are
a
couple
things
that
you
are
proposing
to
delete
that
are
probably
pretty
obvious
things
to
delete
like
weird
red
dots
like
we
probably
don't
need
to
keep
those
kinds
of
things,
and
maybe
you
could
just
use
your
best
to
scratch
and
I
would
trust
you
on
that
to
just
kind
of
say
this
is
this
is
a
clear
delete.
C
This
is
something
has
been
moved
I.
Can
you
can
explain
where
it
has
been
moved?
You
know
what
I
mean
something
like
something
along
those
lines
and
then
maybe
like
the
image
that
Kevin
was
just
talking
about
like
the
history
you're
like
no,
no,
let's
have
a
discussion
and
that
just
might
move
things
a
little
faster,
okay
having
each
one
being
treated
as
keep
or
not
keep.
A
Like
does
this.
Does
this
really
belong
here?
Let's
delete
it
that
way.
That
would
be
a
way
of
kind
of
organizing
that
into
a
so
the
so
the
steps
would
be
to
create
the
new
folder
structure,
create
the
new
files
and
then
move
all
of
the
existing
files
into
the
folder
that
best
and
then
we
could
go
through
those
individual
folders
and
say
this
document
can
be
deleted.
This
one
needs
to
be
edited.
B
Or
there's
one
other
suggestion
that
that
I'm
thinking
of
like
I'm
thinking
of
picking
as
a
chunk
like
first
thing,
I
picked
this
main
four
files,
I
just
create
a
one
PR
of
deleting
these
four
files,
then
I
create
a
PR
of
this
particular
group,
like
chaos
group,
and
these
five
files
like
which
is
still
manageable.
You
have
a
folder,
you
have
the
files
within
it
like
having
empty
folder
is
still
like,
I
can
foresee.
B
C
B
As
of
today,
I
am
proposing
like
deleting
these
four
and
maybe
five
files,
I'm
deleting
and
some
media
files,
which
I
thought
was
not.
B
C
Yeah
and
if
we
could
take
him
on
his
chunks,
that'd
be
good
and
I.
Think
I
do
think
if
you
could
specify
them
as
like
obvious
deletes,
because
they're
just
and
then
that,
because
that,
if
we
can
do
obvious,
deletes
that
20
might
go
down
to
12.
B
B
D
B
Yeah
I
think
that
will
work
so
I.
Maybe
then
you
can
reject
this
PR
and
I'll
create
a
new
appear
of
different
chunks
like
then
we
can
go
one
by
one
to
each
PR
perfect.
Thank.
A
Okay,
so
we're
we
are
running
out
of
time
for
this
meeting,
so
we're
not
going
to
hit
all
the
agenda
items.
So
is
there
anything
on
the
agenda
that
want
to
that?
We
want
to
make
sure
we
talk
about
so
Ray's.
Not
here
he
did,
he
did
say
we
could
take
a
look
at
that
self-merge
rate
document.
If
we
wanted
to
or
we
could,
we
could
hold
off
until
next.
Next
meeting
on
that
the
nod
had
another
action
item
related
to
the
knowledge
base.
A
B
B
C
A
So
there
was
a
backlog
management
index,
yes
metric.
This
one
Dawn
had
Dawn
and
Daniel
I
think
were
discussing
it.
B
B
B
This
one,
so
yes,
so
I
have
actually
created
this
metric
out
of
that
their
newsletter
where
they
have
discussed
two
different
bad
tricks.
B
So
this
is
like
I
have
written
out
of
that
and
now
it
needs
to
be
reviewed
by
the
group
and
maybe
and
okay.
B
A
A
So,
let's
just
let's
not
I
mean
with
the
other
two.
We
probably
let's
just
leave
it
here,
so
we
remember
it,
but
this.
A
This
one
came
from
the
the
open
science
working
group
meeting
if
I
remember
correctly,
so
this
is
a
metric
that
they,
they
believe
it's
really
important
to
Green
I
like
this
metric
as
well,
but
let's
just
we'll
just
kind
of
tow
it
along
with
us
until.
C
Yep
we
have
the
space
okay,
well,
I
did
want
to
give
Just
One
update
from
the
metrics
model
working
group
meeting.
So
there
was
some
discussion
about.
C
It
was
really
interesting
discussion
about
understanding
community
and
how
people
kind
of
change
roles
in
community
and
some
of
the
work
that
yuhi
and
Liang
were
doing
was
really
impressive.
For
the
watching.
The
video
is
pretty
cool.
C
Sometimes
use
slightly
different
metrics
in
their
like
deployments,
on
whether
it's
Compass
or
some
other
work
that
they're
doing
you
know
what
I
mean
like
the
it's,
not
exactly
a
chaos
metric,
but
it's
it's
kind
of
related
to
our
chaos.
Metrics
and
part
of
me
was
like.
Do
we
actually
try
to
keep
those
two
things
perfectly
aligned?
C
You
know
what
I
mean
where,
if
and
I
I,
just
my
head
exploded
when
I
was
trying
to
think
about
that
that
we
would
try
to
keep
everything
aligned
as
it
goes
out
into
the
world
like
that,
would
be
I.
Think
a
an
errand
that
a
Fool's
Aaron
like
we
just
don't
want
to
do
that.
You
know
like
if
somebody
uses
a
a
metric
say
for
inspiration
and
they
change
it
a
little
bit
like
we
just
can't
keep
track
of
all
of
that
stuff.
C
A
Yeah
go
ahead.
Oh
so
I
would
argue.
We've
we've
never
really
kept
them
aligned
even
internally,
so
auger
more
lab
both
use
metrics
a
little
bit
differently
than
the
chaos
metrics
that
we've
defined.
They
don't
use
the
same.
Oh
oftentimes,
they
don't
even
use
the
same
terminology,
so
I
mean
we've
discussed
in
detail
just
like
the
the
name
of
a
change
request
yeah.
A
C
Yeah,
exactly
for
a
long
time,
I'm
like
I,
think
these
two
things
need
to
be
aligned.
We
need
to
keep
them
perfectly
aligned,
but
so
what
just
as
a
note,
what
Yahoo
is
going
to
be
doing,
at
least
on
the
compass
side
of
things?
But
if
there
are
metrics
that
they're
using
that
are
not
defined
as
part
of
the
chaos
project,
they're
actually
going
to
add
a
component
that
says
this
metric,
you
know,
is
kind
of
inspired
by
or
comes
from
the
thought
process
around.
This
particular
chaos
metric.
C
You
know
what
I
mean
and
they
provide
a
link
to
the
stable
URL
which
I'm
like
that's
really
nice,
you
know
so
if
it's
like,
they
have
metrics
around
say,
like
pull
requests
to
issue
link
ratio,
you
know
what
I
mean,
and
so
that's
a
metric
that
we
don't
have
to
find
and
then
he's
like.
There
are
a
couple
chaos
metrics
that
kind
of
inspired
this
or
at
least
kind
of
touch
on
this
and
we'll
just
list
those
metrics.
There
pull
request
to
issue
link.
A
Wrote
I
wrote
a
paper
on
that
three
four
years
ago,.
C
Well,
let's,
let's
turn
it
into
a
metric,
but
like
there's
but
like
there
are
certain
things
that
they're
doing,
and
that
might
be
an
example
of
one
that
we
turn
into
a
metric,
but
others.
You
know
we
we
don't
so
anyway.
I
just
I
want
to
bring
that
up
just
because
it
came
up
also
in
the
metric
model
discussion
about
how
closely
we
try
to
keep
those
things
aligned.
B
Maybe
I
was
thinking
of
two
things
like
especially
I
I,
don't
know
about
the
compass,
because
on
our
website
we
are
promoting,
augur
and
grimo
lab.
So
maybe
we
can
keep
a
track
of
these
two
software
only
if
they
are
choosing
some
different
name
and
as
a
point,
because
that
is
like
kind
of
a
chaos
thing
for
Compass.
We
are
not
promoting
as
a
part
of
our
software,
but
we
are
just
pointing
out.
So
if
they
use
a
separate
name,
that's
their
call,
but
for
at
least
grimoire
lab
and
auger.
B
A
I
think
that's
why
we
have
the
keywords
partially,
why
we
have
the
keywords
for
synonyms
and
then
I
think
it's
just
perfectly
fair
to
discuss
the
different
names
for
things
in
the
description
of
the
of
the
metric,
but
even
even
jumping
between
get
when
we
talk
about
pulling
the
data
even
jumping
between
GitHub
or
any
of
the
other
platforms,
those
those
names
change,
so
I.
B
A
C
Just
and
our
messaging
would
be
like
listen,
we
make
these
definitions
and
we
understand
they
take
on
different
forms
in
different
pieces
of
software
and
in
different
contexts,
and
we
are
completely
fine
with
that.
But
these
metrics
are
meant
to
serve
as
inspiration
and
ways
to
kind
of
think
about
Community
Health,
but
we
understand
they
may
live
differently
in
in
different
parts
of
the
world
and
I'm.
Okay,
with
that.
D
Just
put
somewhere
on
like
the
Gamora
lab
or
even
in
our
mentors
page,
just
like
auxiliary
metrics
or
other
people
who
are
also
doing
metrics,
something
like
that,
maybe
just
like
a
big
resources,
page
of
links
out
to
other
places,
because
there's
other
obviously,
groups
that
are
doing
metrics
too-
that
aren't
connected
to
chaos
at
all,
but
we'll
give
them
some
love.
That's
fine!
That's.
D
C
A
Talking
about
creating
a
document
that
would
almost
map
the
map,
the
connection
between
chaos,
auger.
D
Nutrigia
give
people
just
like
more
like
if
you're
you're
looking
for
a
metric-
and
you
don't
see
it
here-
here's
some
other
places
you
can
try.
There's.
A
A
Right,
but
we
we
could
take
that
moment
to
actually
actually
create
the
link
to
to
the
chaos
metric.
You
know
when
they
when
they
do
exist,
if
the
name
is
the
same
or
if
it's
a
synonym,
for
example,
if
you're,
if
you're
making
a
list
of
Mater
geometrics,
you
know
when
you
get
to
pull
requests,
we
could
just
link
out,
we
could
link
it.
This
is
a
chaos,
metric
link
to
change
requests
and
then
we
could.
That
would
actually
give
us
kind
of
if
we
just
looked
at
a
uger,
detergia
and
Chaos.
A
B
A
D
A
I
think
that
they're,
both
they're,
both
using
some
sort
of
SQL
database,
aren't
they
yeah.
C
For
more
lab,
isn't
it
other
more
lab?
Doesn't
elasticsearch
database
elastic
but
nonetheless
I.
A
Okay,
oh
cool
yeah
I
would
like
to
see
that
actually
and
if
you
can
get
those
lists,
I
will
I'll
take
some
time
and
try
to
map
them
and
see
what
that
looks
like.
A
Thank
you
for
the
update
the
interesting
stuff
happening
over
in
the
metrics
model.
Working
group
I.
Think
at
this
point.
We
are
over
time,
so
I'll
just
I'll
go
ahead
and
in
this
meeting
out,
unless
there's
anything,
anyone
wanted
to
say
all
good
nope.
Okay,
thank
you
all
see.