►
From YouTube: CHAOSS OSPO Working Group Meeting May 18 2023
Description
You can see a recap of this meeting and continue the conversation in our Discourse thread here: https://chaoss.discourse.group/t/ospo-todo-working-group-meeting-summary-may-18-2023/141
C
Hey
everybody
Welcome
to
the
chaos
Hospital
metrics
working
group
meeting.
We
do
abide
by
the
chaos
code
of
conduct.
The
meeting
is
being
recorded
and
will
be
published
later
for
people
who
haven't
seen
it
you're
welcome
to
keep
your
cameras
on
or
off
whatever
your
preference
is
we're
not
super
picky,
and
if
you
don't
mind,
if
you
want
to
put
your
name
down
on
the
attendees
along
with
the
last
book
that
you
read,
that
would
be
great.
C
So
we
have.
We
have
a
few
things
on
the
agenda
today.
This
is
looking
like
a
pretty
good
agenda,
so
so
Gary
I
did
put
the
project
viability
assessment
on
the
very
first
part
of
the
agenda,
because
we
keep
saying
we're
going
to
do
it
and
then
we
don't
get
to
it
so
we're
gonna.
Do
it
first,
just
to
make
sure
so
I
don't
know.
Gary
I
think
this
came
up
in
a
discussion
that
you
were
having
with
somebody.
Do
you
want
us
at
the
stage
for
this
yeah.
D
I'd
love
to
yeah,
please
I
also
appreciate
that
bringing
it
up
one
time
and
not
making
it
onto
the
agenda
counts
as
I
keep
bringing
it
up.
I
I
appreciate
it
being
first,
though
I
I
at
Verizon,
We,
Care,
a
Lot
or
let
me
start
with
I,
started
this
job
at
Verizon.
This
is
my
fourth
week
and
I'm
tasked
with
like
project
viability.
How
does
that
work?
D
How
do
you
gauge
whether
or
not
that
project
is
going
to
be
viable?
How
do
you
say
this
is
going
to
be
viable,
but
you
know
for
a
couple
of
years
or
10
years
or
five
years,
or
this
is
something
that
we
should
instead
use
vendor
software
for,
like
what
are
some
things
that
we
think
about
to
make
that
determination,
I'm
in
the
process
of
working
through
the
very
large
backlog
of
metrics.
That
chaos
has
to
say
these
are
things
that
we
can
automatically
gauge.
D
These
are
things
that
require
physical,
like
or
physical,
like
effort
from
some
employee
or
some
person,
and
then
these
are
strong,
weak
or
moderate,
like
fits
and
so
in.
In
this
conversation,
I'd
love
to
because
it's
so
many
people
and
because
there's
such
a
diverse
opinion,
I
would
love
to
hear
how
everyone
thinks
about
viability,
what
they
think
are
very
important
metrics
and
what
they
think
are
maybe
not
important
metrics
to
gauge
whether
or
not
you
would
adopt
a
project
or
how
you
would
gauge
if
that
project
is
going
to
stay
viable
in
the
future.
C
Yeah
I've
actually
done
a
few
advancements
recently
for
things
that
basically
open
source
projects
that
people
were
considering
making
kind
of
a
key
element
of
one
of
our
products.
So
super
important
to
you
know
to
look
at
some
of
those,
and
some
of
the
assessments
are
like
yeah.
That
seems
great,
and
one
of
them
was
like.
Oh
no,
please,
please
don't
so
so
it's
it's
kind
of
it's
kind
of
across
the
board
and
I'll
be
honest
like
when
it
comes
to
these
types
of
Assessments.
C
Oh
Alyssa
I
think:
can
you
mute
like
there's
somebody
else
talking
that's
coming
up
on
your
mic,
so
one
of
the
things
I
look
at
is
adoption,
like
are
other
people
actually
using
this
thing,
and
this
is
especially
true
if
it's
owned
by
like
like
a
company
or
you
know
a
competitor
even
like,
are
they
the
only
ones
using
it
or
are
there?
Are
there
a
bunch
of
people
using
it
because
the
more
people
are
using
it,
the
the
better
off
you'll,
be
over
the
over
the
long
term?
C
I
look
at
I
look
at
governance,
so
if
it's,
you
know
if
it's
owned
by
a
little
tiny
startup,
for
example,
that
that's
probably
kind
of
a
high
risk.
If
it's
owned
by
you
know,
maybe
a
company
that
I
trust
more
around
open
source,
maybe
that's
sort
of
medium
risk.
If
it's
owned
by
Foundation,
that's
probably
low
risk,
lower
risk,
anyways
from
a
governance
perspective,
I,
look
at
whether
or
not
they're
keeping
up
with
pull
requests
or
issues.
C
So
this
one
is
more
of
a
more
of
a
metric,
but
are
they
do
they
have
a
gigantic
backlog
of
issues
and
pull
requests
that
they're
not
closing
in
a
timely
manner?
It's
something
I
look
at
I,
look
at
a
whole
bunch
of
like
project
policies,
so
is
it
under
an
OSI
license
is:
do
they
have
a
code
of
conduct?
Do
they
have
a
security
policy?
C
Do
they
have
contributing
documentation?
Can
I
find
information
about
their
governance?
It's
another
thing
that
I
look
at
and
then
and
then
I
look
at
security,
so
I
run
the
OSS
app
scorecard
and
I.
Look
in
particular
I.
Look
at
so
look
at
the
overall
score
and
then
I
dig
down
into
it,
but
in
particular
I
look
at
open
vulnerabilities
and
whether
they
have
some
of
them.
C
You
know
a
big
pile
of
like
critical
vulnerabilities
that
are
open
and
that
that,
for
me,
is
a
gigantic
red
flag
along
with
some
of
the
other
stuff
in
the
ossf
report.
So
that's
that's
kind
of
how
I
do
like
that.
So
these
are
like
quick
assessments,
so
this
is
gut
gut
check.
Does
this
seem
like
something
that
might
be
okay,
or
does
this
seem
like
a
gigantic
red
flag
and,
let's
run
away
from
it,
but
I'd
be
curious
to
see
what
other
people,
what
other
people
do
I
mean?
D
Yeah,
that's
super
helpful
and
I
never
thought
about
it
as
like
different
degrees
of
how
you
might
be
evaluating
a
project
right
of
it
takes
less
effort
if
somebody
wants
to
investigate
or
do
a
proof
of
concept
or
something
that
maybe
doesn't
need
the
same
level
of
scrutiny
that
oh,
this
is
going
to
go
on.
You
know
a
very
important
piece
of
Hardware
that
gets
shipped
all
around
the
country
like
that's
something
that
needs
to
be
a
lot
more
secure.
A
D
A
A
C
D
C
G
Yeah
I
have
a
couple
of
thoughts,
especially
that
it's
it's
really
different
by
use
case,
and
so
the
consideration
for
using
something
internally
versus
using
something
in
a
product
have
different
considerations.
Like
say
how
easy
is
it
to
become
a
contributor
to
the
project
and
work
on
the
project
say
you
might
want
to
have
more
investment
in
the
community
if
you're
trying
to
also
create
a
product
around
it
and
so
understanding?
A
One
of
the
things
that
Wayne
O'brien
did
when
he
was
Osco
directorate.
Indeed,
that
I
thought
was
that
never
heard
of
anyone
else
doing
this.
He
looked
at
all
of
the
projects.
He
depended
on
up
and
down
the
dependency
chain,
and
he
then
identified
which
projects
across
his
portfolio
he
was
most
dependent
on
so
that
he
had
several
thousand
projects
that
were
directly
his
responsibility,
but
over
11
000
projects
that
he
was
dependent
on
to
one
degree
or
another,
and
so
he
used
dependency
analysis
to
identify
projects.
A
They
depended
on
that
they
should
invest
something
in
and
I,
think
I
think.
That's
one
way
to
think
about.
You
know
as
an
as
a
company
who
levered
is
open
source.
How
do
you
decide
which
projects
that
you
want
to
help
make
more
viable
with
limited
resources,
obviously
and
I?
Think
looking
across
all
of
the
things
you
use
for
most
commonly
Incorporated
dependencies
is
I
thought
it
was
a
really
great
strategy
that
Dwayne
employed.
D
A
E
D
J
I
would
everything
everyone
has
said:
I
don't
have
a
lot
to
add
there
at
Microsoft.
We
have
a
lot
of
automation
around
things
like
license.
Compliance
and
security,
I
I
would
just
say
that
at
scale
one
of
the
things
that
is
it
challenges
like
within
each
organization.
We
ask
like
a
business
reviewer
to
be
accountable
for
kind
of
the
final
sign-off.
For
these
types
of
things
and
and
there's
you
know,
how
do
you
pass
on
this
type
of
wisdom
and
tools
to
those
folks,
some
of
them
don't?
J
We
would
do
this
intuitively
right.
They
would
like
for
a
lot
of
these
things
intuitively
we
can
provide
some
guidance,
but
there's
definitely
like
stuff,
we'll
find
some
that
will
go
quite
in
depth
to
things
like
you
know,
there's
no
activity
here,
I'm
gonna
make
calls
on,
like
you
know,
we're
not
going
to
use
that.
There's
no
activity,
but
there
actually
are
plenty
of
packages,
for
example
that
you
know
don't
have
activity
but
are
not
necessarily
a
risk.
C
E
C
D
C
Okay,
next
up
I
thought,
maybe
we'd
just
spend
at
least
a
few
minutes
on
on
chaoscon
and
the
open
source
Summit
in
in
Vancouver,
and
maybe
talk
about
some
some
key
takeaways.
What
we
learned
other
thoughts,
I,
think
Matt
and
Sophia
I
saw
you
talking
in
one
of
the
channels
about
putting
together
some
some
notes.
Do
you
wanna?
Do
you
want
to
start
with?
Do
you
want
to
start
with
that?
Not
to
put
you
on
the
spot.
F
G
Well,
we
kind
of
split
it
between
talk
and
discussion
and
try
to
balance
the
time
between
both
and
most
people.
I
talk
to
really
like
that
format.
They
they
liked
being
able
to
meet
people
and
have
sort
of
facilitated
reasons
to
talk
to
each
other
and
then
so
I
think
in
general
I
think
that
was
really
positive
feedback
for
us
as
a
community
running
event.
So
I
thought
that
was
fun.
G
G
C
You
know
we
we
need
to
replace
maintainers
and
we're
not
going
to
replace
them
right
now
with
new
people
who
are
coming
in,
you
know
new
to
open
source
new
to
development
new
to
a
project
we
need
people
with,
like,
in
particular,
I
think
I
use
the
example
of
FCD
right.
It's
a
key
value
store,
it's
essentially
a
database.
We
need
experienced
people
who
know
how
to
build
databases
to
contribute
to
projects
like
that
and
eventually
become
maintainers,
because
it's
not
it's
not
an
easy
project
to
contribute
to,
and
so
yeah
I
think.
F
C
About
both
it's
about
this
maintainer
pipeline,
so
so
the
idea
is
that
you
know
you
maintainers
aren't
going
to
maintain
a
piece
of
software
forever.
So
you
need.
You
need
this
pipeline
of
people
who
are
eventually
going
to
replace
these
maintainers
and
you
need
people
with
a
variety
of
skill
sets
and
experience
to
do
that
because
you
know
when
you
replace
a
maintainer
they're
going
to
have
to
be
relatively
experienced.
So
maybe
they
started
in
a
mentorship
program
and
were
brand
new.
But
it's
going
to
take
them.
C
F
C
Part
of
the
reason
we're
having
a
shortage
of
maintainers
is
that
some
of
these
companies
have
laid
a
bunch
of
people
off
and
those
people
aren't
necessarily
working
on
those
open
source
projects
anymore,
so
we're
losing
some
maintainers,
because
they're
employers
are
are
letting
people
off
or
because
their
employers
are
de-prioritizing
things.
So
I
had
one
case
where
I
was
talking
to
somebody
and
he
used
to
be
a
maintainer
for
a
certain
project
and
the
company
he
works
for
was
like
no.
We
we're
not
going
to
pay
you
to
do
that
anymore.
A
A
H
C
B
I'll
get
some
of
my
feedback
I,
really
like
the
format
of
chaoscon.
It
was
my
first
chaoscon
and
I
really
liked
the
the
breakouts,
especially
you
know,
asking
to
talk
to
people
that
you
didn't
necessarily
know
and
collaborate
so
that
I
I
appreciate
that
I
think
the
setup
from
both
Sophia
and
Emma
were
really
great
and
I
really
liked
the
questions.
Sophia,
that,
like
you,
the
themes
that
you
asked
us
to
start
with
and
then
the
sets
of
questions
to
to
move
the
conversation.
That
was
really
helpful.
B
I'm
still
really
impressed
with
the
group
that
week
ahead
around
this
five
love
languages
of
osbo.
So
probably
we'll
continue
to
talk
about
that
in
my
free
time
was
one
of
the
takeaways
and
so
I
really
and
I.
Think
chaoscon
as
like
a
full
day.
Conversation
was
really
was
really
helpful.
You
know
like
it
was
as
opposed
to
the
other
days
where
you
had
to
like
jump
in
and
out
of
like
talks
or
events.
B
A
I'd
say
for
for
something
like
this
talks
and
small
group
things
to
work.
Well,
you
need
an
excellent
facilitator
and
Sophia
Sophia
did
it
like
and
Sophia
and
I.
Think
Don
and
gay
are
I
mean
together
just
a
really
a
group
of
people
whose
personalities
are
well
suited
to
coordinating
people
without
ordering
them
around
yeah.
A
B
Yeah
I
thought
it
was
great
for
the
rest
of
the
conference.
You
know,
I
I
feel
like
one
of
the
themes
that
I
was
I,
thought
I,
don't
know
it's
like
I
almost
feel
like
it's
sometimes
I
felt
like
learning
a
new
word
and
then
seeing
it
everywhere.
You
know
so
I
feel
like
something
that
I've
heard
by
saws
a
recurring
theme
in
the
conference
for
the
ones.
B
The
events
that
I
attended
were
like
a
conversation
around
like
best
practices
and
standards
and
I,
don't
know
if
that's
like
a
reflection
of
like
Linux
Foundation
priorities
or
like
where
I
am
in
my
own,
like
you
know,
path
and
journey
or
what
I'm
paying
attention
to
at
the
moment.
But,
like
you
know,
standards
I've
never
been
like
excited
about
standards
create
the
the
graduates.
B
The
the
journey,
the
process
of
Standards
creation
seems
like
pretty
boring
when
it
comes
to
like
open
source
Community
work,
but
I
I
think
that
there's
there's
a
lot
of
like
interesting
and
exciting.
Like
conversations
that
I
seem
to
have
like
gone
into
about
like
how
do
you
create
kind
of
best
practices,
agreement
standards,
not
in
a
kind
of
you
know,
mandate
sort
of
way,
but
rather
from
a
much
more
Collective
and
dynamic
conversation,
and
so
I
thought
that
was
one
of
like
the
most
meaningful
takeaways.
B
For
me,
as
well
as
just
continuing
conversation
around,
you
know,
how
do
you
quantify
and
qualify
value
when
it
comes
to
open
source
and
the
work
that
we
do
is
like
when
we
ask
about
space
so,
but
that
one
has
been
like
a
recurring
theme.
I
feel
like
in
a
lot
of
the
open
source
conversations
that
we
take
part
in
the
standards.
One
was
like
something
that
I
was
not
expecting
to
see,
so
those
were
some
of
my
takeaways.
Also
Vancouver
is
like
so
beautiful.
B
C
C
H
It
seems
as
as
Alyssa
was
talking.
She
was
basically
covering
all
my
points,
but
I
didn't
I
did
love
the
format.
I
love
the
fact
that
George
went
and
bought
a
bunch
of
food
for
us,
so
it
made
everything
it
just
made.
Everything
feel
very
casual
and
like
like
you're
entering
a
family,
so
that
was
a
nice
touch
and
I
I
didn't
really
like
I
did
really
like
the
Curiosity
hooks
that
I
get
that
kept
me
thinking
for
the
rest
of
the
conference
and
the
fact
that
this
was
on
kioskanos
on
day.
H
One
really
helped
because
I
felt,
like
the
rest
of
the
conference,
was
at
blur
that
I
didn't
really
experience
the
rest
of
the
conference,
but
I
was
there
for
chaoscon
and
I.
Have
all
my
notes
for
chaos
gone
and
not
for
anything
else?
So
so
that
was
good,
so
I
really
did
enjoy
the
conference.
Okay,.
J
J
Everyone
who
came
up
with
all
that
it
was
a
pleasure
to
be
with
everyone
like
I,
was
just
so
happy
to
be
at
a
conference
and
see
everyone.
You
know
I
just
and
what
a
great
group
of
people
I
think.
Maybe
there's
a
story.
Someday
I,
don't
know
Elizabeth.
If
you
started
telling
that
like
how
was
the
chaos
con
metrics
like?
How
do
we
place
them
against
our
community
and,
like
just
maybe
there's
some
examples
that
that
we
could
be
showing
or
case
studies
about
how
the
chaos
community
you
know
is
welcoming?
J
I
have
drank
the
Kool-Aid
apparently
over
here,
I
was
really
struck.
Oh
I'm
also
very
excited
about
auger
and
I.
You
know,
there's
that
prompt
to
you
know
not
to
build
things,
and
you
know
how
much
work
has
gone
into
that
I.
Would
I'm
really
excited
to
try
and
see
what's
play
with
that
new
technology
and
bring
break
yourself
into
that?
A
Yeah
I
I
think
chaos
would
certainly
like
to
work
closely
with
your
hospital.
I
mean
GitHub
is
most
of
the
data,
so
you
do
have
it
I
I
think
what
we've
done
with
both
auger
and
grimorlab
is
some
pretty
good
data
engineering
to
organize
the
data
in
a
way
that
I
suppose
and
others
want
to
look
at
it
and
that's
not
the
way.
It
naturally
occurs
on
the
GitHub
platform.
A
You
know
we
we
pulled
from
literally
hundreds
of
different
apis
in
order
to
assemble
the
data
in
a
structured
format
to
provide
chaos,
metrics
and
I.
Think
I
think
there's
there's
things
we
can
learn
from
each
other,
but
the
big,
perhaps
the
biggest
benefit,
given
that
you
actually
have
user
interface
developers
and
data
scientists
is
just
some
of
the
data
engineering
work
that
we've
done.
I
think
could
help
platforms
a
lot
and
help
the
community
a
lot
and
I
so
I'll
just
throw
that
out.
There
I
know
I've
said.
J
A
J
Not
like
it
came
to
me
yeah
but
I,
know
they're
interested
in
that
and
I.
You
know
yeah
so
and
then
just
you
know,
the
conference
I
can
kind
of
I
took
really
good
notes,
also
Christine
for
chaoscon,
and
then
my
other
notes
were
just
great
but
I
feel
like
there's
like
the
whole
conference,
including
to
some
extent,
has
kind
of
felt
like
we're.
J
Still,
you
know,
that's
still
a
problem
we
haven't
solved
and
then
the
a
you
know
AI
people,
you
know
Covenant
co-pilot
llm's
like
there's
that
fear
of
the
future
like
it
feels
like
this
impending
Shadow
is
coming
and
most
of
those
conversations
for
me
happen
in
like
hallways
or
smaller
talks,
or
they
weren't
really
on
the
stage.
But
I
felt
like
they're,
like
there's
sort
of
an
equal
amount
of
focus
on
the
present,
but
fear
of
the
future,
so
that
was
just
kind
of
a
meta.
J
A
meta
observation,
I
think
I
think
especially
around
make
communities
and
AI
or
llms
like
maybe
there's
something
to
learn
there.
So
that's
something
actually
I'm
gonna,
try
and
understand,
like
what
do
people
mean
by
open,
not
opening
but
like
open
source
AI
when
they're
talking
about
like
that
sort
of
stuff
happening,
I
think
maybe
there's
some
measurements
that
need
to
be
built
pretty
soon
around
like
communities
around
that
kind
of
technology,
so
I'm
gonna
be
learning
there
I
think
most
other
things
were
covered.
J
Someone
gave
me
a
good
idea,
based
on
our
our
calculation,
to
show
the
impact
of
external
contributions
on
internal
projects
where
I've
proposed
that
we
try
and
figure
out
some
sort
of
formula
that
gives
us
a
monetary
value
for
what
those
mean
I,
don't
know
how
far
we'll
get,
but
I'll
definitely
report
back
on
that.
So
that
was
another
outcome
of
chaos.
Funding
like
that's
a
great.
J
I
Yeah
no
I
agree
with
a
lot
of
what
Emma
said
and
in
thinking
through
a
lot
of
what
everyone
has
kind
of
said
in
this
meeting
at
chaoscon
and
at
the
OSS
Summit
conference,
I
started
to
think
through,
like
what
I
really
wish
I
had
for
my
aspo
was
a
Playbook
and
I.
Don't
know
if
Matt
you
might
be
able
to
answer
this.
I
I
These
are
all
the
different
metrics
that
you
could
potentially
be
using
for
these
different
topics,
because
I
think
what
I
was
feeling
like
I
was
like
trying
to
gather
all
of
the
good
pieces
that
everyone
was
trying
to
say
and
write
them
down
and
make
it
into
like
my
strategy
and
my
what
we're
doing
in
our
hospital.
But
I
was
like.
Oh
it'd
be
nice
if,
like
we
just
kind
of
had
that
too,
so
just
an
idea.
F
F
So
is
it
Chan?
Is
it
about
like
where
an
ospo
is
kind
of
in
their
journey
and
what
they
should
be
looking
at
at
those
different
stages?
So,
like
early
I
suppose
you
know
like
a
early
starting
osbo
and
maybe
hear
the
things
that
you
should
think
about
yeah
later
in
the
journey.
You
know
like
that.
I.
F
Okay,
so
I
guess
I
have
two
comments.
One
I
think
I
need
a
little
bit
more
clarity
still
from
Anna
on
the
book
chapter
we
had
talked
about
this
last
time,
so
it's
not
I,
don't
think
it's
real
clear
if
the
book
chap
or
the
book
itself
is
going
to
be
like
an
anthology
where
each
each
chapter
is
kind
of
different
from
every
other.
F
I
Yeah
and
I
think
that's
okay,
it
was
just
something:
I
was
thinking
of,
even
as
like
Gary
was
starting
to
you
know,
pull
all
the
knowledge
From
Dawn
I
was
like.
Oh
that's
like
those
are
things
I
wish.
I
could
have
jumped
to
a
page
and
saw
all
of
that
too.
So,
but
yeah
just
an
idea
to
keep
him
back
in
the
back
of
our
minds.
E
E
C
F
But
in
the
interim
not
to
talk
about
it
today,
but
tan,
if
you
do,
if
you
look
at
them
the
meeting
minutes,
but
here
I'll
just
share
my
screen
really
fast,
you
can
click
here.
It's
just
this
ospo
maturity
framework
and
it
might
be
something
that
can
help
this
conversation.
And
if
you
have
comments,
maybe
before
the
next
meeting,
never
thoughts
it'd
be
great,
you
could
put
it
just
in
there.
Maybe
we
could
talk
prior
to
the
next
meeting.
A
Yeah
I
shared
the
links
and
some
commentary
on
on
the
beta
project
that
we're
doing
it's
coming
along
and
it's
in
release.
Now
you
can
sign
in
create
an
account.
Add
your
repos
we'll
get
the
data
in
the
next
week.
There'll
be
email
updates
on
when
your
data
is
collected.
If
we
don't
already
have
it,
that's
that's
the
short
of
it.
I'll
talk
about
this
in
small
chunks
over
time.
J
Don
one
quick
question
on
auger,
because
I
was
playing
with
it
a
little
bit
when
it
says
there's
not
enough
data
available
is.
Is
it
possible
to
get
a
will
there
be
so
I'm,
not
really
asking
for
something,
some
sort
of
description
of
what
that
threshold
is
just
out
of
interest,
because
sometimes
I
feel
like
that
data
should
exist
or.
A
It
could
be
that
we
just
haven't
that
was
I
made
a
very
large
collection
at
chaoscon,
so
I'm
gonna,
look
at
I'm,
gonna,
look
for
power
toys
and
see
what's
going
on
there
and
and
then
look
to
provide
more
direct
messages
on
the
on
the
auger
interface.
The
the
primary
interface
we're
going
to
is
the
eight
not
one,
because
it's
a
dash
plotly
data
science
tool,
much
more
easy
to
modify
than
most
web
stuff,
but
but
obviously
the
other
auger
front
end
still
exists.
So
I'll
take
I'll.
A
A
A
C
D
That's
a
pretty
solvable
problem
for
future
proofing
those
references
and
links,
because
I
think
that
they
do
provide
important
context
for
why
the
metrics
are
the
way
that
they
are
I'm.
Basically
signing
up
to
be
like
I
can
just
put
in
a
bunch
of
Link
changes
to
an
archive
website
like
if
we
have
a
preference.
Otherwise
I
was
just
going
to
use
the
Wayback
machine.
K
M
I
was
just
gonna
say:
yes,
it's
it's
hosted
on
GitHub,
so
those
the
metrics
are
individually
hosted
on
GitHub
in
the
repo
for
the
the
working
group
that
defined
them.
So
the
the
example
one
that
you
had
mentioned
is
a
Dei
metric,
so
yeah
that
one
is
actually
hosted
in
the
the
Dei
working
group,
repo.
So,
okay
in
the
near
future,
we
will
actually
be
adding
a
link.
That'll
take
you
directly
to
where
that
document
is
hosted.
D
E
D
E
E
F
Think
what
I,
what
I
was
gonna
say
what
I
would
like
to
do
is
kind
of
take
a
look
at
the
discussion
we
had
today
around
viability
and
just
see
if
that
can't
be
kind
of
brought
together,
whether
through
existing
metrics.
You
know
just
as
ways
to
think
about
some
of
these
topics
that
came
up
or
models.
You
know
what
I
mean
like
is
there
a
way
we
can
start
kind
of
coalescing
that
conversation
into
metrics
or
models.