►
From YouTube: CHAOSS Common Working Group April 27, 2023
Description
Minutes from this meeting can be found here: https://docs.google.com/document/d/1xsii5tfmmDwWpuhrFcBJMeYeT3RipJdiCdHrbi0NalQ/edit
A
A
Welcome
to
the
common
metrics
working
group
meeting
for
April
27
2023.
As
a
reminder
we
do.
We
do
follow
the
the
chaos
code
of
conduct
in
these
meetings
and
with
that
I
will
just
we'll
just
go
ahead
and
jump
into
the
agenda.
Hello,
everyone.
The
first
thing
on
the
agenda
is
a
new
metric
to
consider
diff
Delta.
B
A
Okay,
so
I
see
the
the
event
locations
metric
is
the
next
thing
on
the
Gen.
The
agenda.
B
So,
just
to
make
sure
that
we've
figured
out
did
we
figure
out
what
we're
doing
with
that
Kevin
remind
me.
A
I
think
we
should.
We
should
probably
talk
about
it,
because
I
I
didn't
realize
that
common
owns
that
metric
I
was
I
was
assuming
that
Dei
owned
the
the
event
locations
metric.
B
A
I
I
can
give
a
brief
overview
of
this
issue.
I
suppose
so
we
in
Dei
we
have.
We
have
a
metric
called
event,
location,
inclusivity.
A
A
So
after
after
some
discussion
in
the
the
Dei
working
group,
I
think
we
decided
to
merge
it
into
the
event
locations
metric.
But
once
again
the
Assumption
was
that
that
Dei
actually
owned
that
metric,
but
common
is
the
one
that
that
defined
it.
So
this
is
a
metric
that
I
am
working
on
I,
don't
know
if
we
want
to
discuss
the
actual
merger
or
if
you
all
would
prefer
to
wait
and
see
what
the
metric
looks
like.
B
A
So
you
you
had
provided
some
edits
to
the
inclusivity
metric
to
add.
Equity
I
basically
took
those
edits,
removed
them
from
inclusivity
and
added
them
to
the
event
locations
metric
and
then
I'm
going
to
go
through
and
I'll
edit
it
further.
So
basically
what
it,
what
it'll
end
up
being
is
so
right
now
event
locations
is
really
just
a
it's
just
a
it's
almost
a
list
of
where
event
locations
happen.
A
A
Right
so
are
all
of
the
are
all
of
these
conferences
just
happening
in
California.
A
Is
that
where
the
community
members
for
that
project
exist,
do
the
does
the
project
ever
or
does
the
event
ever
occur
in
other
areas,
things
things
of
that
nature
right
so
just
just
kind
of
equity
in
the
way
that
events
are
dispersed
around
the
globe
and
and
whether
or
not
the
that
disbursement
kind
of
matches
where
the
community
is
so
I
think
they
fit
together
fairly
well,
and
would
it
would
address
the
the
Dei
concern
of
equity,
but
it
would
also
address
the
the
location
part,
which
would
still
be
a
main
component
of
it.
B
A
B
I
think
that
sounds
good
just
so,
just
so
you
know,
I
took
that
event
locations
metric
out
of
the
spreadsheet
completely
on
Dei,
just
to
avoid
confusion.
So
if
you
want
to
change
the
spreadsheet
to
go
back
to
in
progress
or,
however,
you
want
to
track
that
you're
working
on
that
the.
B
A
Okay,
yeah,
then
yeah
I
think
I
think
it's
appropriate
to
just
remove
it.
Okay,
because
the
the
one
that
we're
concerned
with
is
the
common
fun
and
when
we,
when
we
and
since
that's
already
been
published,
it'll,
have
to
go
back
through
review
or
whatever,
whatever
that
looks
like
currently
yeah.
A
Think
it's
I
think
it'll
require
a
name
change,
I
was
kind
of
leaning
towards
actually
event
locations,
event,
location
and
equity,
with
an
and
separating
the
location
and
equity,
but
event,
location
equity
could
work
as
well.
I
think
we
could.
We
could
talk
about
that
as
part
of
the
edit
okay.
A
So
the
metrics
audit
progress
that's
going
to
be
matte
as
well.
Yes,.
B
B
I
think
he
just
had
something
right
at
the
beginning
of
this
meeting.
So
as
soon
as
he
took
care
of
that,
then
he
would
be
able
to
join.
So,
hopefully,
it's
not
too
long
and
if
need
be,
I
can
talk
a
little
bit
about
that
because
he
and
I've
been
working
together
on
that,
but
I
think
he
he
would
be
probably
better
soon
discuss
it.
If
he's
here,
so
we
can
give
him
a
minute.
A
Okay
and
then
the
the
last
agenda
item
is
getting
metrics
from
our
software
into
our
metrics
definitions.
It
was
that
a
match.
C
Nope
that
was
me
okay,
so
it's
something
we've
talked
about
a
few
times
in
this
in
this
meeting
because
we
have
loads,
you
know,
so
we
have
what
100
metrics
that
are
defined
on
the
website
and
are
our
tooling
definitely
has
has
more
than
those
those
metrics,
but
we
haven't
actually
just
taken
the
time
to
Define
all
of
those
and
I
got
to
thinking
about
it,
because
peturgia
does
this
metric
of
the
month
thing,
and
this
was
actually
two
metrics
and
they're
really
explicit,
and
these
these
blog
posts
about
exactly
how
it's
defined
and
I'm
thinking.
C
Maybe
we
should
create
some
some
issues
and
just
just
start
defining
some
of
these.
Some
of
these
metrics
in
particular
these
two,
because
I
think
these
are
probably
pretty
easy.
We
just
need
to
verify
that
we
don't
have
them
to
find
somewhere
under
some
other
name,
that
I
didn't
didn't
jump
out
at
me,
but
looking
at
those
metrics
and
maybe
maybe
Sean,
this
is
a
question
for
you:
I'm,
not
sure
whether
these
are
they're
kind
of
risk
metrics
we
could
Define
them
either
place.
I
think
we
just
have
to
pick
one.
D
Yeah
I
I
mean
I,
actually
looked
at
those
metrics
and
they're,
not
what
the
risk
working
group
has
been
talking
about:
okay,
they're,
more
aligned
with
what
the
the
Evolution
working
group
historically
talked
about.
Okay,.
D
Yeah
well
and
I
also
remember
efficiency
coming
up
in
the
metric
model
working
group
and
what
I
don't
but
I
haven't
taken.
The
time
myself
to
look
at
is
whether,
for
example,
efficiency
is,
is
meaning
the
same
thing
and
when
you
talk
about
review
efficiency
like
I
do
know
that
we
talk
about
pull,
request
acceptance
rate,
which
I
think
is
the
same
concept
as
review
efficiency
index,
and
so
the
question
is:
are
there
parameters
or
filters?
I
forget
what
we
call
them
now
in
in
that
report
or
that
merge
request
rate.
D
D
You
know
the
what
one
thing
is
the
like.
The
way
that
this
is
for
these
are
framed
as
risk.
Metrics
isn't
really
consistent
with
the
app
called
arithmetric.
So
that's
you
know,
but
that's
just
a
label.
That's.
C
E
C
D
C
D
It's
good
to
know:
I
can
compress
my
BMI
with
pull
requests
and
issues.
E
E
So
these
two
are
these
like:
we
have
a
atomic
metric
and
we
have
a
model.
So
here
they
are
using
two
metric.
Is
this
a
model
or
is
it
a
metric
and.
C
I
think
it's
I
mean
I,
think
closed
reviews
divided
by
submitted
reviews,
I,
don't
necessarily
I,
don't
I,
don't
think
we
need
to
define
those
as
two
separate
metrics
and
then
Define
this
as
something
that
goes
with
those
I
mean
sort
of
like
like
when
I
defined
the
change
request
ratio.
It
was
it's
basically,
you
know
the
number
of
you
know.
It's
a
ratio
of
two
things
and
I
see.
This
is
just
like
I
mean
closed
reviews
and
submitted
reviews.
That's
it's
not
necessarily
a
metric.
It's
just
a
like
a
data.
A
C
F
F
E
A
Over
the
we.
F
Skipped
over
the
items
you,
you
would
add
it:
okay
and
I'm
guessing
this
was
okay.
C
C
D
A
So
the
other,
the
other
thing
we
had
talked
about
was
the
event
locations
metric.
Turning
that
into
the
event
locations,
Equity
metric
yep,
so
common
owns
that
metric.
So
we
can,
we
can
present
it
to
Dei
as
well,
but
I
will
I'm
working
on
that
metric
and
I
will
present
it
to
common.
In
the
next
week,
yeah.
F
G
F
If
we
need
to
and
like
related
to
that,
there's
the
event
location
metric,
that's
currently
sitting
in
common
and
Dei
has
been
talking
about
what
is
a
Kevin
event:
location,
Equity
yep.
F
So
we're
like
that
may
be
a
metric
that
ends
up
being
evolved
just
a
little
bit
and
then
move
to
Dei
and
again,
like
the
movement
is
really
just
for
that
spreadsheet
and
where
we
might
spend
the
time
talking
about
it,
because
the
release
metrics
are
all
right.
The
working
groups
are
lost
on
the
web
page
in
a
good
way.
A
F
F
F
I
think
somebody
else
added
it
an
individual
who
I'd
have
to
go
track
down
in
slack,
but
they
just
they
had
an
interest
in
bringing
this
back
up
and
just
encouraging
a
conversation.
So
they
are
not
on
the
call
here,
but.
E
F
I
think
I
I.
What
I
had
done
is
I
hadn't
suggested
like
they
had
talked
about
gift,
Delta
and
I
said:
hey
here's
the
the
template.
If
you
want
to
take
a
little
bit
of
time
and
add
it
to
the
template,
and
they
did
that
and
that's
what
you're
seeing
here
so
I
mean
I,
appreciate
the
effort
and
I
thought.
Maybe
we
could
at
least
just
give
it
a
look
here.
E
D
G
The
name
here
is
a
little
bit
misleading
from
the
description
because,
like
what
Sean
is
explaining,
that's
the
right
definition
of
this
Delta
from
the
commit
at
the
commit
level,
but
here
they
are
mostly
talking
about
the
project
level.
At
the
evolution
of
the
project.
Zif
Delta
is
a
small
change
in
terms
of
commit
level,
and
the
GIF
has
also
been
used
at
that
commit
level
where
you
have
two
fights.
You
want
to
see
the
number
of
other
lines
and
deleted
lines
to
calculate
the
Delta
at
that
space.
G
F
D
I
mean
I
I
kind
of
think.
This
exists
in
a
conceptually
similar
way
without
some
of
the
same
descriptions
in
our
lines
of
code
metrics
that
were
originally
under
Revolution.
Like
I
know,
we
talked
about
these
kinds
of
line
of
code
changes
things
very
early
on
in
the
chaos
project,
so
yep.
F
We
had
it
was
around
like
I've,
just
been
kind
of
taking
a
look
at
some
of
those
metrics
and
we
had
like
they
were
like
code
change
commits
like
a
lot
around.
That
is,
code
change,
yeah.
D
There's
code
change
lines
is
where
the
kind
of
thing
I
think
does
exist,
but
not
with
this
level
of
elaboration,
okay
and
certainly
not
with
the
same
objectives.
So
it's
the
same
metric,
but
it's
explained
it's
probably
I
would
say
this
is
a
more
contemporary
explanation
than
what
we
came
up
with
six
or
seven
years
ago.
D
You
know
it's
incorporating
the
astral
motivation,
which
you
know
has
emerged,
obviously,
and
so
I
think
you
know
revisiting
some
of
those
metrics
and
incorporating
these
Concepts
and
rationales
into
them
is
a
good
idea.
Okay,
because
this
does
I
think
update
some.
You
know
what
I
would
I
characterize
these
things
as
core
chaos
like
these
are
some
of
the
core
things
that
people
try.
F
D
F
D
This
well
I
would
say
well,
I
would
suggest
I
mean
I
would
suggest
just
modifying
the
existing
metric
to
incorporate
these
description
and
rational
properties,
because
the
data
is
the
same.
Otherwise
we
end
up
with
two
metrics
that
are
basically
the
same
thing,
but
rationalize
differently
and
I.
Think
that
would
be
confusing.
A
So
there
are,
there
are
two
questions
here,
so
it's
not
just
about
lines
of
code.
It's
also
about
the
how
the
files
and
directories
change
so
because
of
that
we
are
adding
kind
of
there.
I
think
I
think
we
we
there
they
would
be
adding
a
little
bit
more
in
so
so
I
suppose
I
would
ask
the
the
same
question.
I
just
asked
is
good.
A
Could
we
just
treat
this
as
a
model
and
connect
it
to
the
the
lines
of
code
metric
that
we've
already,
because
I
don't
think
we
have
a
files
changed
metric.
G
Like
what
Sun
said,
if
we
look
the
way
commit
I've
done
every
commit,
we
can
count
the
number
of
files
that
that
particular
commit
is
modifying
either
deleting
line
or
adding
some
code
in
that
particular
file.
So
proposal
three
usually
commit
when
analyzed
at
the
lowest
level
of
granularity.
G
They
capture
those
the
line
changes,
but
at
the
subsystem
level
you
now
go
to
the
fire
and
the
directories,
and
things
like
that
to
see
so
we
can
modify
if
necessary.
We
cannot
modify
what
we
already
have
just
to
make
sure
we
keep
the
track
of
it
because
to
my
opinion,
if
we
have
to
Define
so
many
similar
matrixes,
then
might
be
aggregating
them
at
some
point,
can
be
procedures
and
giving
us
more
much
work,
whereas
we
can
just
go
and
modify
what
we
already
have
to
make
it
more
representative.
That's
my
opinion,
though,.
A
So
I
think
that's
why
I
think
that's
why
trading
this
as
a
as
a
model
would
be
would
be
the
easiest
way
out
for
us,
because
the
the
lines
of
code
metric
currently
does
not
account
for
files.
Changed
and
I
do
disagree
with
you
a
little
on
on
how
lines
of
code
and
files
changed
are
kind
of
the
way
that
you
kind
of
described
them
as
similar,
so
I
think
they
can
tell
us
different
things
about
the
code
base.
A
A
So
the
number
of
files,
so
so
I
I
I,
don't
think
the
the
number
of
files
is
trivial,
but
I
also
don't
know
that
we
need
to
necessarily
Define
that
as
a
metric
I
think
we
could
just
talk
about
it
in
as
the
the
in
a
model
actually
in
a
diff
dealt
Delta
model,
and
since
since
this
one
is
also
pretty
heavily
yeah
I
think
this
leads
pretty
heavily
towards
implementation.
So.
E
In
this
I
see,
there's
three
things
like
one
is
Line
scenes
five
scene
directory
exchange,
though
we
have
lines
changed,
I'm,
not
sure
like.
Is
it
going
to
be
a
model
because
all
three
points
to
the
similar
thing,
I'm,
not
sure.
D
Like
adding
files
as
a
parameter,
for
example
right
so
so
it's
a
couple,
I
mean
do
we
do
we,
like?
We
have
a
very
Bare
Bones
description
of
metric
code
changes
lines
it.
It
looks
to
me,
though,
all
of
the
data
that
underlies
this
metric
is
the
same
data
that
is
in
that
existing
metric,
so
I
I
think
I
think
perhaps
this
can
be
a
modification
to
that
metric,
because
it's
it's
fundamentally
just
looking
at
that
angular
piece
of
data
and
and
elaborating
on
it
more
fully.
For
example,
the
file
parameter
like.
D
If
you
can
get
lines
of
code
you
can
get
files
and
I
went.
I,
went
back
and
looked
here
real,
quick
and
I.
We
had
change
request
files
and
change
request,
commit
to
the
candidate
metrics
and
evolution,
but
it
doesn't
look
like
they
ever
got
finished.
So
this
is
not
change
requests,
obviously,
but
conceptually
it's
the
same
thing
it's
another
way
of
getting
at
the
same
data
ultimately,
but
we
can
deal
with
it
at
the
commits
level.
The
change
request
level.
F
D
Two
weeks
is
okay:
yeah
I
was
I
thought
we
decided
we
weren't
meeting
that
week,
but
I
forget
I.
B
G
F
E
G
D
F
Kevin,
would
you
be
able
to
at
least
kind
of
sketch
out
a
model
that
could
be
diff?
Delta,
yes,
like
super
simply
because
then
we'd
have
the
three
things
on
the
table,
which
would
be
this
as
a
metric.
F
F
A
And
I
I,
don't
think
I,
don't
think
any
of
us
have
read
lines
of
code
changed
either
or.
D
E
A
So
when
we
start
when
we
start
adding
multiple
things
to
it
to
measure,
they
I
think
we
we
can,
we
can
confound
it
so.
A
D
The
other
thing
we
could
do
is
just
accept
it,
as
is,
and
refer
to
the
existing
metrics
that
you
know
the
very
basic
information
that
underlies
this.
So
we
could
nominally
change
the
language
and
refer
to
code
changes
lines
and
talk
about
how
this
is
elaborating
on
that
further
and
Kevin
thinks
at
the
metric
model.
I
am
cool
with
that
as
well,
because
I
can
see
that
argument.
A
A
C
Mean
this
this
to
me
looks
like
relatively
so
I
I
think
that
what
this
metric
should
be
is
a
relatively
simple
you're
talking
about
the
the
basically
just
the
you
know,
the
the
diff
between
the
two
files
I
think
that
they've
made
it
a
little
bit
more
complicated,
like
I,
think
that
they've,
so
the
part
that
you've
just
highlighted,
we
would
normally
have
that
in
the
filters
section
of
a
regular
metric
right.
We'd,
be
you
know,
you'd
find
something
relatively
simple.
F
A
Good
idea,
so
I'm
I'm
I'm,
not
opposed
to
I,
mean
the
simplest.
The
simplest
route
is
is
often
the
easiest
route,
so
maybe
the
the
simplest
route
is
to
edit
our
existing
metric
and
add
files
as
a
as
a
filter
like
on
said
and
see,
if
there's
anything
else
from
this
metric
that
could
be
moved
into
the
which
which
metric
are
we
talking
the
lines
of
code
lines,
code,
changed
lines,
code
lines,
code.
A
I
mean
that's
probably
the
that's,
probably
the
easiest
path,
so
maybe
we
maybe
do
that
and
see
if
see
what
that
looks
like
and
then
from
there
we
could
determine
if
we
want
to
take
it
further.
A
I
would
say:
I
I
do
still
think
that
the
the
files
and
directories
is
probably
a
second
metric,
but
second,
second
metrics
can
be
filters
as
well.
So.
A
F
F
D
F
E
A
Okay
and
then
the
the
last
thing
was
the
metrics
audit
progress,
yep.
F
So
I
just
wanted
to
kind
of
keep
people
posted.
The
process
is
changing
just
a
little
bit
here
and
there
as
I
go
through
it.
So
it's
real-time
process
change
as
I
go
through
the
process,
so
the
spreadsheet
is
I'm,
just
really
thankful.
We
have
the
spreadsheet.
It
is
so
incredibly
helpful
in
terms
of
monitoring,
metrics
and
kind
of
auditing
the
metrics.
F
So
there
has
been
I
think
through
this
process,
just
kind
of
ensuring
that
the
spreadsheet
is
up
to
date
with
the
metrics
that
have
been
released
on
the
website,
and
that
should
be
all
good
now
Don.
This
is
kind
of
for
you.
So
I
had
just
moved
that
privacy
statement
down
to
the
bottom
of
all
of
the
common
metrics
we're
actually
going
to
remove
it
because
we
can
do
a
WordPress
so.
F
Of
TRS
we're
actually
going
to
do
a
WordPress
module
that
will
allow
every
metric
to
just
have
that
same
module
at
the
end.
So
we
can.
We
it'll
centralize
the
Privacy
statement
for
everybody,
see
what
I'm
saying
we'll
just
have
the
statement
as
a
markdown
file
in
like
the
community
repo
or
something
like
that
and
Kevin
and
Elizabeth
were
talking
about
getting
it
as
a
module.
Just
at
the
end
of
every
metric
shouldn't
be
too
much
too
much
work.
So
then
we
just
have
it
in
one
place.
F
D
F
D
D
F
Pretty
funny
we're
also,
the
one
of
the
proposals
is
to
remove
the
not
data
the
date
of
last
review,
so
it
at
the
bottom
of
every
metric.
We
had
a
very
random
assortment
of
metrics
that
carried
a
date
of
last
review.
It
was
like
10
or
as
I,
go
through
it's
even
less
than
10
percent,
and
so
what
we
were
going
to
add
was
I
can
go
track
it
down,
but
a
statement
that
would
also
be
in
a
module.
Let
me
let
me
give
me
a
second
I'll.
Go
get
that
statement.
F
F
C
F
Yes,
so
let's
I
can
do
that
to
add
link
to
the
markdown,
I
and
I
have
all
that
in
this
much.
A
E
F
F
D
F
C
I'm
wondering
so
by
us
adding
a
link
to
the
markdown.
We
are
we're.
Gonna
have
to
add
that
to
the
markdown
file
so
that
it
gets
pulled
into
the
the
website
is.
Is
that
also
something
that's
maybe
better
done
in
WordPress,
because
WordPress
pulls
I
mean
it
pulls
everything
from
the
markdown
file
into
into
WordPress?
So
does
it
know
that
link,
and
could
we
add
it?
Could
we
do
something
Dynamic
within
WordPress
to
add
the
link
to
the
markdown
file
that
it's
pulled
things
from
that
way?
C
C
Kevin
knows
of
like
a
way
to
do
this
or
if
Elizabeth
knows
of
a
way
to
do
this.
A
So
so
you're
you're
saying
basically.
So
what
would
that?
What
would
that
link
look
like
to
you?
Would
it
be
like
click
on
the
document,
and
it
takes
you
to
GitHub
or
a
button
that
would
exist.
B
A
So
that
would
be
so
it's
probably
we
can
add,
we
could
add
a
module
to
the
template
and
and
with
that
with
that
code
or
that
button
or
that
link
in
it,
and
then
when
we
create
a
metric
that
that
module
would
automatically
be
created,
along
with
the.
A
Yeah,
so
then
we
would
just
have
to
go
in
and
edit
that
module
so
that
the
link
was
pointing
to
the
appropriate
place.
A
So
the
when
you
when
you
when
you
would
create
a
metric,
you
would
have
to
add
that
you
have
to.
You
have
to
add
that
link
or
that
address
to
the
GitHub
module,
and
then
we
would
add
it
to
the
link
module
and
then
you
would
add
keywords.
You
would
add
context
words
and
you
would
add
the
name
of
the
metric
and
theoretically,
that
those,
if
you
do
all
of
those
tasks,
you've
added
a
you've
added
a
metric
to
the
the
list.
Isn't
that
long
you
can
you
can
you
can
it's?
A
It
takes
about
five
minutes
to
publish
a
metric
that
way,
maybe
less
so
it's
not
a
as
long
as
it's
part
of
the
template.
I,
don't
think
that's
an
issue.
So,
yes,
we
could
we
could.
A
E
A
The
disclaimer
one
that
you
were
talking
about
prior
okay,
so
a
metrics
template
page,
would
have
three
modules
on
it.
It
would
have
the
GitHub
module
it
have
have
that
disclaimer
module
and
then
it
would
have
the
the
link
module
we
wouldn't
have
to.
We
wouldn't
have
to
edit
the
disclaimer
module.
That
would
just
always
exist
the
two
places.
The
two
modules
we
would
have
to
edit
would
be
the
GitHub
module,
which
is
the
actual
metric
and
then
we'd
have
to
add
that
link
to
the
the
link
module
as
well.
A
E
A
But
it
can
be
added
to
the
template
so
that
basically
it
would
create
a
list
of
when
it's
added
to
the
template.
We
have
a
list
of
they're
like
five
or
six
things
we
have
to
do
when
we,
when
we
publish
a
metric
and
oh
that's
just
a
matter
of
I,
see
what's
happening,
no,
no,
the
X.
We
could
add
it
to
the
actual
temp
word.
It
would
be
a
WordPress
template
of
what
a
metric
looks
like
so
that
module
would
automatically
populate
when
we
create
a
new
metric.
Okay,.
A
So,
just
for
it's.
A
Do
that
I,
gotcha,
okay,
so
so
I
I
think
we
should
consider
that
as
well.
But
that's
for
I
think
there's
a
there's!
Another
group-
that's
gonna,
be
looking
at
that.
So.
F
Okay,
just
kind
of
those
last
two
points,
I'm
just
kind
of
going
through
the
metrics
for
readability
like
I
found
a
few
typos,
sometimes
I
find
some
markup
in
there.
You
know
what
I
mean
just
to
remove
that
kind
of
stuff,
so
I
am
doing
edits
to
some
of
the
metrics,
but
with
no
content
change,
edits,
they're,
really
just
structural
edits.
E
F
And
then,
once
kind
of
this
is
done,
I
think
we
can
start
adding
the
keywords
and
context
tags,
because
those
there
aren't
many
that
include
that
right
now
on
the
website.
But
there
is
still
a
little
bit
of
work
that
needs
to
be
done
in
the
spreadsheet,
like,
for
example,
risk
all
the
keywords
right
now
in
risk
or
just
say,
risk.
D
D
E
D
All
right
I'll
take
that
on
for
the
next
time
that
this
group
meets.
Thank
you
Sean.
F
So
and
Elizabeth
and
I
are
just
kind
of
doing
this
work
so
just
suffice
it
to
say
we're
really
trying
to
align
the
spreadsheet
with
the
released
metrics
and
the
keywords
that
we're
trying
to
get
all
of
this
like
lined
up.
There
were
some.
They
were
starting
to
deviate
just
a
little
bit,
but
we're
spending
quite
a
bit
of
time.
Just.
F
F
D
F
As
well,
no
just
at
this
point
just
add
them
to
the
spreadsheet.
That
would
be
most
helpful,
okay,
yep
and
then
because
that'll
be
the
next
round.
Then
then
Elizabeth
and
I
will
just
go
through
like
kind
of
metric
by
Metric,
again
adding
keywords
and
context
tags
so
having
them
in
the
spreadsheet
is
the
most
helpful
thing
right
now.
E
F
A
And
I
will
as
soon
as
they're
in
the
spreadsheet
I
can
also
add
them
to.