►
From YouTube: OSPO / TODO Group Working Group June 15 2023
Description
Meeting summary is here: https://chaoss.discourse.group/t/ospo-todo-working-group-june-15-2023/178
A
Awesome,
thank
you
so
welcome
to
the
hospital
working
group
meeting
as
part
of
the
chaos
project.
As
a
reminder,
it
is
covered
under
the
chaos
code
of
conduct,
so
please
be
kind
to
each
other
and
with
that
I
think
we'll
go
ahead
and
get
started.
If
you
haven't
already
the
link
for
the
notes
is
in
the
chat.
If
you
want
to
add
yourself
and
your
comfort
movie,
we've
got
some
some
interesting
ones.
We've
got
a
few
that
I've
never
heard
of
like
I've,
never
heard
of
snatch
or
idiots.
C
That
yeah
welcome
Don
Foster
I'll
I'll.
Do
the
welcome.
So
if
you
haven't
heard
Don
Foster
is
gonna.
Don
is
gonna.
Take
on
the
a
new
role
as
the
Director
of
data
science
for
the
chaos
project,
full-time
starting
in
August
and
Don
is
going
to
be
joining
us
from
VMware
and
I.
Just
can't
tell
you
how
unbelievably
excited
we
are
to
have
Don
join
us
and
thanks
to
the
Sloan
foundation,
for
making
this
possible
that's
great
yeah.
A
Absolutely
so
I
am
I
am
also
super
excited
about
this.
It's
kind
of
it's
kind
of
my
dream.
Job
like
I,
get
to
work
on
chaos
pretty
much
full
time,
so
VMware
was
great,
so
I'm
not
leaving
them
because
it
was
a
terrible
place
to
work.
It's
just
that
this
was.
This
was
too
awesome
for
me
to
turn
down
so
I
get
to
I,
get
to
play
with
data
I
get
to
work
on
chaos
and
I
get
to
do
it
as
the
main
part
of
my
job.
A
A
So
I
think
I'm
going
to
spend
some
time
initially
talking
to
the
auger
team
and
the
grammar
lab
team
and
seeing
if
we
can
better
position
the
software
so
depending
on
the
context
you're
using
it
in
who
you
are
what
you're
trying
to
get
out
of
it
and
try
and
point
people
to
the
the
piece
of
software.
That's
going
to
be
be
best
for
them,
and
then
you
know
also
just
start
to
work
across
the
various
contexts.
To
make
sure
that
we're
that
we
have
sort
of
the
right.
A
The
right
approach
for
all
suppose
for
universities,
for
for
scientific
communities
and
and
just
just
do
what
I
can
to
make
sure
that
we're.
You
know
taking
kind
of
a
a
data,
a
data
based
approach
to
to
looking
at
the
metrics
in
a
way
that
we
we
haven't
necessarily
done
before
so
I'd
like
to
you
know
to
to
help
the
chaos
project
go
move
from.
A
You
know
make
sure
that
I'm
working
on
on
the
stuff
that's
going
to
have
the
most
value
for
for
the
community
from
a
from
a
data
science
approach
and
then
we'll
also
likely
spin
up
some
sort
of
data
science
Community
within
within
chaos.
So
that
could
be.
That
could
be
a
working
group.
Maybe
that's
a
good
place
to
start.
A
D
E
Yeah
just
a
similar
thing
and
not
to
detract
from
auger
and
the
work
that
they're
doing
too,
but
red
hat
is
currently
in
partnership
with
the
auger
team
and
we've
built
a
few
visual
dashboards
and
and
tools
that
go
along
with
that
as
well.
I'm.
Just
timing
in
and
saying
happy
to
talk
to
you
about
our
efforts
when.
D
F
G
Yeah
I
just
wanted
to
to
let
you
know,
because
you
weren't
on
the
call
on
Tuesday,
so
I
don't
know
if
you
listened
to
it
yet,
but
generally
everyone
was
really
pumped
about
this
and
we
talked
a
lot
about
what
we
thought
your
role
could
be
and
they
were
like.
Maybe
we
should
let
Don
tell
us
what
her
role
is
going
to
be
before.
G
Excited
about
it,
but
I,
mostly
just
like
I,
think
something
that
came
up
that
I
want
to
bring
up,
at
least
to
you
directly.
Was
that
clearly
there's
a
lot
of
interest
in
a
role
like
this
than
what
you
could
be
doing
and
so
I
think
not
to
ask
you
for
anything
yet
because
you
haven't
even
started,
but
it's
one
of
those
things
where
the
more
you
can
share
what
you're
working
on
or
how
you
want
to
work
with
the
broader
Community
I
think
the
interest
is
always
going
to
be
higher
than
one
person's
bandwidth.
G
Always
I
would
just
like
wager
a
guess,
mostly
we're
just
super
pumped
to
have
you
in
this
role
and
I.
Think
there's
going
to
be
a
lot
of
things
for
you
to
pick
and
choose
so
the
I
guess
we're
mostly
well
I'm,
mostly
just
waiting
for
guidance
from
you
on
what
you
want
to
work
on
what
you
want
to
take
on
and
how
best
to
sort
of
suggest
and
throw
things
at
you
to
see
how
you
want
to
take
them
like
I.
A
A
C
So
this
is
I'll
just
I'll
I'll
present
this.
This
is
something
that
has
kind
of
come
up
over
the
course
of
the
last
several
weeks
and
I
think
it
leads
into
a
discussion
that
Emma
had
brought
up
in
slack
earlier
this
week
that
we
could
probably
talk
about
as
well,
so
also
talking
with
the
university
ospo
working
group.
So
a
couple
things
that
have
come
up
is
is
trying
to
identify
metrics
or
metrics
models
that
are
appropriate
to
understand
the
use
of
Open
Source
within
an
organization.
C
Do
these
two
I'll
start
here
before
I
show
the
maturity
framework
thing,
but
these
two
kind
of
resonate
with
people
or
do
they
make
sense
or
am
I
completely
off
on
this,
you
know
a
set
of
metrics
about
use
of
Open
Source
within
an
org
and
a
set
of
metrics
kind
of
about
the
value
of
an
open
source
program
office
within
an
organization
curious.
What
people
think
about
that
differentiation?
Yes,.
D
So
I
mean
the
differentiation
is
good,
I
mean
if
we
look
at
what's
happened
in
Industry
recently
being
unable
to
demonstrate
the
value
of
an
ospo
has
had
repercussions
to
say
the
least,
but
again
in
the
University
context.
Is
we've
been
discussing
in
here
off
and
on
for
a
couple
years
now.
Moving
beyond
just
software
is
really
key
to
to
moving
things
forward
at
the
University.
E
I
was
initially
going
to
be
contrary,
but
then
I
decided
I'd
ask
a
clarifying
question
when
you
said
I'm
a
personal
growth.
When
you
said
in
the
minutes,
you
in
the
agenda,
you
have
the
use
of
Open
Source
and
then
the
value
of
Oxbow,
like
are
you
seeing
like,
depending
on
how
you
do
that?
It's
like
use
of
Open
Source,
could
also
be
value
of
Open
Source
well,
but
then
there's
also
the
process
and
how
efficiently
it's
running.
That
could
also
be
a
definition
of
use
like
here's
where
the
contrary
part
comes
in.
E
If
we're
talking
about
value
in
both
cases,
then
I'm
not
sure
the
differentiation
needs
to
be
there.
Okay,
because
if
you
as
an
osbo
can't
you
can't,
you
can't
demonstrate
the
value
of
Open
Source
within
your
organization,
then
you've
got
that
problem
like
now.
You
have
a
problem
as
an
actual
functioning
organization,
because
if
you
can't
deep,
it's
like
you
can't
do
your
job.
E
What
good
are
you
and
I
and
I
I'm
hugely
oversimplifying?
So
you
know
if
we're
talking
about
just
straight
up
value,
I'm
wondering
if
the
differentiation
is
necessary.
If
you
are
talking
about
use
of
Open
Source
like
how
efficiently
does
it
mesh
with
existing
business
plans,
how
good
is
your
onboarding
and
yada
yada
things
like
that?
Then
I
could
see
the
differentiation.
I
Yeah,
the
starting
at
the
end
of
it
I'd,
say
like
for
the
value
of
an
hospital
within
an
organization,
some
of
the
ways
that
you
know
we've
described
or
presented
value
like
that
in
the
past-
and
this
is
not
an
exhaustive
list-
is
now
first
I
think
you
need
to
split
to
inbound
and
outbound
understanding
what
your
focus
is
on
whether
or
not
you're
talking
about
the
value
of
inbound,
open
source
to
an
organization
versus
whether
outbound
is
a
big
difference.
I'm
learning
that
in
government
land,
outbound,
open
source
is
less
of
a
concern.
I
Inbound
is
much
more
of
a
priority
as
opposed
to
corporate
I
suppose
so.
I
would
start
by
just
sort
of
splitting
those
two
streams,
and
then
things
like
number
of
repos
outbounded
is
a
metric
that,
if
you're
tracking
outbound
and
then
you
know
whether
or
not
those
outbounded
repos
actually
are
in
compliance
or
not
I,
think
that
the
maturity
model
around
like
everybody
is
doing
open
source.
I
It's
whether
or
not
your
osbo
is
getting
ahead
of
it
and
helping
to
guide
it
or
whether
or
not
it's
just
going
out
into
the
wild
is
like
a
an
observed
pattern.
I
would
say
that
a
lot
of
organizations
see
so
the
more
that
you
can
outbound
compliant
open
source
projects
that
are
mature
and
then,
depending
on
what
your
maturity
model
is,
is
like
a
value
prop,
for
you
know,
I
would
plug
into
this
area.
I
wouldn't
say
it's.
The
only
one.
I
I
think
that
over
indexing
on
outbound,
open
source
repositories
is
a
mistake
that
a
lot
of
people
sort
of
take
when
they
think
about
the
value
of
an
open
source
program,
but
it
is
one
that
a
lot
of
at
least
in
the
corporate
world.
A
lot
of
folks
put
a
lot
of
emphasis
on
I.
Will
you
know?
Stop
there
because
I've
been
talking
for
a
long
time,
but
I
could
go
on
a
list
of
sort
of
what
I've
seen
people,
stakeholders
thinking
is
valuable
within
you
know,
reporting
out
metrics.
B
Yeah
I
wish
Remy
talks
longer
because
I'm
I'm
hearing
a
lot
of
what
he's
saying
and
I'm
agreeing
with
a
lot
of
it.
I
actually
think
I'm,
gonna,
I'm
gonna
go
on
a
limb
here
and
say:
ospo
maturity
framework
is
way
too
big
by
itself,
just
with
the
two
topics
that
you
have
of
use
of,
Open,
Source
and
then
the
value
of
an
osbo,
because
use
of
Open
Source
is
like
so
diverse
in.
Are
you
talking
about
the
sdlc?
Are
you
talking
about
what
happens
when
a
project
is
deployed?
B
And
how
do
you
maintain
it?
Are
you
talking
about
the
long-term
maintenance
of
projects
like
what
the
maturity
is
in
regards
to
how
up-to-date
dependencies
are?
You
can
go
very
deep
on
just
the
software
development
that
goes
along
with
using
open
source,
especially
when
you're
talking
about
larger
companies
or
even
when
you're
talking
about
startups.
B
You
can
be
very
specific
about
a
lot
of
aspects
of
what
an
ospo
is
delivering
on
in
regards
to
changing
culture,
for
a
use
of
Open
Source
within
an
organization
and
then
to
follow
up
on
the
other
point
that
you
had
first,
which
is
the
metrics
regarding
the
value
of
an
ospo
within
an
organization.
The
like
Myriad
ways
that
an
ospo
delivers
value,
I,
think
normally
and
to
do
aren't
looked
at
as
like
a
maturity
model.
B
But
they're
looked
at
as
like
things
that
you
do
in
an
ospo,
depending
on
situations
that
you
might
run
into
and
then
you
can
grow
the
Osco
by
taking
on
more
responsibilities.
But
it's
not
like,
if
you're
doing
this,
then
you're
mature,
if
you're
doing
this
and
you're
mature.
Maybe
it's
more
like
the
larger
and
the
more
responsibilities
total
that
you've
gathered.
That
might
be
a
maturity
model,
because
you
have
so
much
that
then
interconnects
and
plays
with
one
another
right.
B
I
think
that
this
topic
of
a
maturity
framework
for
an
ospo
is
big
enough,
that
it
should
be
split
into
at
least
two
models
of
using
open
source
effectively
and
then
the
value
of
what
the
Oslo
is
delivering
and
that
wasn't
even
covering
what
Remy
had
started
to
bring
up,
which
is
like
the
the
pitfalls
that
you
can
fall
into
with
publishing
open
source,
and
is
that
even
important?
Is
that
something
that
an
ospo
needs
to
look
at
and
I?
Think
in
that
lens?
B
It's
it's
about
how
much
an
ospo
is
able
to
enable
that
ability,
rather
than
the
actual
success
of
Any
Given
project,
because
most
projects
that
people
open
source
wind
up
doing
very
little.
But
that's
not
the
fault
of
the
hospital
and
that's
not
a
metric
that
they
should
judge
themselves
successful
or
unsuccessful
on,
because
it's
completely
out
of
control.
All
right
now,
I've
been
talking
too
long
and
I'm
going.
This
is.
H
No
I
think
it
was
mostly
covered,
I
mean
I.
Think
just
so
much
like
giant
I
mean
like
main
thoughts.
I'm
also
like
I
mean
also
is
revolving.
Like
is
boss.
This
also
even
the
right.
Definitely
like
I
related
to
the
university
like
having
worked
in
the
university,
the
connection
with
open
science
and
open
education.
H
All
those
things
that
are
might
be
the
capacity
of
an
open
source
programs
office
as
like
Ai
and
LM
start
to
emerge,
and
people
like
there's
an
evolution
as
well
as
the
maturity
like
I'm
kind
of
trying
to
think
about
the
tension
between.
Is
it
about
saying
an
open
source
programs
office
is
a
solution,
and
this
is
what
that
solution
looks
like
or
we'll
be
looking
at
it
as
a
an
evolution
of
how
we
approach
open,
like
use
of
Open
Source
release,
but
release
of
open
things.
H
G
G
G
The
more
that
I
feel
like
if
you're
trying
to
look
at
something
like
a
maturity
model,
then,
instead
of
bounding
it
around
a
team
that
could
look
incredibly
different
by
a
company.
Maybe
we
instead
group
it
by
task
and
maturity
within
task,
and
that
way
it's
like.
Well,
if
I
don't
do
those
five
things,
then
that
shouldn't
detract
from
my
maturity,
because
maybe
either
we'll
do
them
one
day
or
maybe
another
team
will
do
them.
It
won't
necessarily
be
Osco
and
also
we
consulted
on
those,
but
not
necessarily
running
them
all.
H
J
J
You
know
I
really
agree
with
the
idea
of
the
diversity
of
it
that
it
might
be
just
a
little
bit
helpful
to
kind
of
have
a
lens
of
of
thinking
about
how
we
have
to
educate
from
the
beginning
with
where
they
see
their,
where
an
organization
might
see
the
objective
that
they're
trying
to
reach,
because
they
might
want
to
integrate
open
source
in
one
way,
and
there
might
be
another
way
dealing
with
the
contributors.
That's
a
little
bit
different
in
the
metrics
kind
of
will
be
different
for
those
two
things.
C
It
does
so
so
thank
you,
I
and
I.
Actually,
hopefully,
I
can
address
that
in
the
in
a
tab
here
in
a
second,
there
are
comments
in
the
chat
that
I
wasn't
following.
Does
anybody?
Could
anybody
make
sure
those
get
into
the
minutes
here
or
if
you
want
to
comment
on
them
out
in
here,
that'd
be
great
too
no
problem
there,
but
I
see
like
from
Justin.
C
So
this
is
an
amazing
feedback
and
I'm
gonna
I'll
make
the
the
claim
that
those
two
things
that
I
put
on
there
with
respect
to
the
use
of
Open
Source
within
an
organization
and
value
of
an
hospital
was
really
meant
to
just
generate
conversation.
So
I
did
a
great
job
in
in
doing
and
doing
just
just
that,
so
it
gives
you
all.
C
It
gives
me
a
lot
to
think
about,
and
this
will
probably
thank
you
for
putting
those
notes
in
from
the
chat
this
I'm
sure
that
the
next
tab
will
have
no
comments
as
well,
but
I'm
gonna
go
ahead
and
change.
Please
continue
your
comments,
because
what
I'm
trying
to
do
here
is
just
capture
the
conversation.
That's
coming
from
this
group
and
move
us
forward
in
such
ways
that
we
can
think
about
the
metrics
and
metrics
models
that
help
provide
insights
in
whatever
particular
areas
of
the
organization.
C
You
would
like
to
provide
Insight
so
when
we're
trying
to
get
to
a
spot
where
your
osbo
has
particular
challenges
in
your
organization
and
ultimately,
metrics
and
metrics
models
can
provide
insight
and
drive
decisions
around
those
challenges
in
ways
that
are
useful
to
you.
So
if
we
have
to
expand
this
out,
that's
absolutely
no
problem.
F
C
Yes,
I
do
think
that's
what
was
part
of
this
conversation
so
again,
I'm
just
trying
to
I'm
looking
at
one
of
those
things
that
I
put
in
the
prior
sheet,
which
is
just
the
value
of
the
hospital
within
the
organization,
breaking
it
out
into
these
two
domains
around
intelligence
and
governments,
and
now
for
this
example,
just
taking
a
look
at
at
governance.
So
from
a
strategic
alignment
perspective.
This
would
be
an
example
of
a
framework
and
I.
Don't
know
what
the
metrics
or
metrics
models
could
be
to.
C
C
That
can
provide
insight
and
then,
lastly,
around
training,
which
Maria
I
think
this
is
kind
of
what
you
were
talking
about
as
well,
just
being
part
of,
say,
newcomer
training
or
being
available
for
internal
teams,
whatever
it
might
be,
and
so
all
I'm
trying
to
do
is
just
kind
of
frame
the
prior
conversation
and
and
then
to
the
point
of
maybe
there's
more
than
just
these
two
things.
I
totally
agree.
C
100
agree
that
there
may
be
more
than
just
these
two
things
as
to
how
we
think
about
metrics
in
in
this
in
the
osbo
sense,
and
we
could
develop
different
Frameworks
to
help
kind
of
guide.
Us
in
thinking
about
what
are
the
metrics
and
metrics
models
that
have
an
intended
objective,
that
roll
into
practice
and
then
into
a
subsequent
domain.
I,
don't
know
if
this
is
resonates
with
anybody
just
trying
to
to
structure
the
conversation
in
some
way.
F
I
think
I
think
it's
used
I
think
it's
useful
for
structuring
the
conversation
on
on
things
like
strategy.
I.
Think
it's
important
to
call
out
that
you
know
there
is
this.
There's
I
think
there's
a
role
that
can
be
played
and
I
don't
know
by
whom
to
to
try
to
work,
to
explain
the
role
of
an
ospo
as
a
unit
of
strategy
inside
of
an
organization
as
opposed
to
a
cost
center
that
provides
metrics
that
are
or
not
you
know
that
are
that
are
consumed,
but
not
maybe
well
understood.
F
I
I
just
want
to
say
out
loud
that
I
want
to
challenge.
Some
of
the,
like
corporations
have
decided
that
ospo's
are
not
worth
the
money.
I
think
that
a
lot
of
times
in
layoff
situations,
you
just
have
to
lay
off
anything
that
doesn't
perform
at
the
core
of
utmost
business
function.
So,
like,
though,
it
is
really
important
for
us
to
have
this
like
we
need
to
present
the
value
of
ospos
I.
I
Don't
think
that
those
decisions
were
made
that,
like
in
ospo,
is
not
a
valuable
thing
necessarily,
but
that's
me
is
like
an
outsider,
I'm,
not
sure
how
the
individual
decisions
are
made.
I
just
know
that
in
layoff
situations
that
I've
seen
even
letting
go
of
really
good
talented
people
is
is
never
because
of
performance
issues.
It's
usually
just
because
something
has
to
go.
C
B
Yeah
I
I
have
this
fun
thing:
where
I
have
a
hardware
mute
that
this
microphone
turns
off
and
then
I
have
the
software
one
and
zoom
so
Remy
again,
I
wish.
We
would
talk
more
because
I'm
finding
a
lot
of
springboards
from
what
you're
saying
that
I
I
think
the
the
layoff
scenarios
are
are
valid,
that
it
might
not
always
be
the
case
that
it's
it's
you
know
a
cost
center
thing
or
they're,
like
the
hospital,
doesn't
really
matter
that
much
they're,
not
bringing
much
value
I.
C
C
Thanks
Gary,
okay,
so
are
there
other
comments
on
this
like
I
I?
Don't
if
you
all
I,
saw
some
comments
in
the
chat
that
it
seemed
to
at
least
initially
resonate
with
some
people
or
because
Gary
said
it
gives
us
something
to
throw
stuff
at
or
something
like
that,
which
is
cool
too
no
problem
there
like
is
this
worth
continuing
to
think
about,
at
least
from
my
perspective,
to
help
frame
the
conversation
you
could
also
tell
me
no,
this
is
not
helpful
at
all,
and
I
can
restart
so
I'm.
Just
it's
like
this.
C
E
E
C
Okay,
but
I'll
try
to
sift
through
like
these
comments
as
well.
That
came
from
the
chat
and
just
from
just
to
see
if
there
are
other
models
out
there,
that
and
maybe
models
isn't
the
right
word
I
think
Gary
had
brought
that
up.
You
know
what
I
mean
and
I
that's
fair,
but
yeah,
okay,
I'll
go
and
I
don't
care
if
you
all
in
a
week
or
two
weeks
or
six
months,
it
doesn't
matter
as
long
as
it
helps
move
things
forward.
C
That's
all
that's
really
important
to
me
and
then
to
to
to
kind
of
the
last
Point
is
the
conversation
that
Emma
had
brought
up
and
Emma
I.
Don't
know
if
this
is
gonna
fit
with
what
you
had
put
in
the
slack
Channel,
so
Emma
from
what
I
understood
you
had
proposed
that
there
could
be
a
metric,
a
couple
metrics
or
metrics
models
that
organizations
deploy
and
talk
about
within
their
organizations
to
kind
of
see
what
the
distribution
patterns
are
or
what
the
feedback
is
or
how
people
respond
to
the
models.
H
Days,
yeah
so
I'm
kind
of
stuck
in
my
own
head
around
these
things
around,
but
so
I
feel
like
there's
lots
of
great
metrics
lots
of
great
metrics
models
for
the
most
part.
I
can
take
a
metric
and
find
a
way
to
either
through
auger
or
through,
like
data
that
we
have
to
visualize.
Those
and
I
can
try
and
test
those
with
different
audiences
inside
of
whether
it's
maintainers
and
Microsoft
report
the
projects
or
it's
whatever,
but
that's
just
me,
testing
it
and
I
still
I
feel
like.
H
For
that
a
maintainer
said:
well,
who
are
the
contributors,
everyone
right
to
know
that
so
then
I'd
want
to
generate
a
report
right
I
have
generated
reports
like
you'd,
have
Avatar
email
address
like
how
many
contributors
like
more
of
the
report,
so
there's
like
a
Step
Beyond
the
metric-
and
you
know,
maybe
that
goes
differently
for
someone
at
a
different
organization
or
someone
in
a
university
but
I
feel
like
if
we
can
start
to.
This
is
like
that
community
of
practice,
I'm
always
trying
to
like
I
mean
chaos,
is
a
Community
Practice.
H
I,
don't
know,
I
mean
I'm
making
this
up,
because
I
haven't
done
anything
like
that
before,
but
I
think
that
would
be
really
valuable,
at
least
for
me,
to
see
how
that's
going
for
others
and
with
help
create
some
transparency
to
the
actual
implementation
of
metrics,
an
organizations
that
I
don't
think
we
have
and
I
apologize.
If
that's
not
something
others
agree
with.
A
Yeah
I
I,
really
like
that
idea.
I
mean
I
feel
like
I
feel
like
in
the
Cs
project.
We
spent
a
lot
of
time
talking
about
how
to
define
metrics
spent
a
lot
of
time
talking
about
about
the
metrics
themselves,
but
we
don't
really
spend
much
time.
Actually,
you
know
implementing
them
together
and
talking
about
what's
working,
what
isn't
what?
Yes,
you
know,
some
of
the
the
nuances
behind
actually
using
these
metrics,
so
I
think
that's
something
that
I
I
personally
find
find
really
interesting
and
I.
Wonder
I
mean
we.
H
Yeah
and
I
mean
I,
even
visualize
like
when
you
go
to
the
metrics
page,
because
the
metric
well,
here's
a
link
to
how
that's
worked
for
you
know
like
case
study,
but
really
what
we're
doing
is
building
case
studies
and
I
think
that's
what
I'm
describing
and
then
that
would
be
inspiring
to
people.
Oh,
like
you
know,
this
company
tried
it
and
went
this
way
and
well
they
they
decided
to
not
have
this
particular
join
in
the
query
or
something
but
like
it
would
just
help,
move
it
forward
and
create
conversation.
H
H
H
H
C
H
That
one
or
how
or
what
people
have
a
lot
of
questions,
especially
those
type
of
projects
that
are
startupy
who's.
Using
my
technology
like
how
do
I,
you
know
more
potential
Partners
like
what
are
they
building
with
this
thing,
that
our
open
source
project
that's
a
hard
one.
I
know
that
would
be
interesting
to
test
around
that
too
see
what
works
for
different
groups
right.
A
C
J
A
Could
come
out
of
the
work
that
you're
talking
about,
but
I
would
encourage
all
of
the
rest
of
you
to
think
about.
You
know
maybe
doing
a
chaos
case
study
about
the
way
that
you're
using
metrics
within
your
ospo,
in
particular,
Gary
I'd,
love
to
see
I'd
love
to
see
you
do
one
when
you
get
a
little
farther
with
your
with
your
work
but
I
think
it's
something
that
we
should
all
be
thinking
about.
B
Yeah
we
can
move
to
the
next
meeting.
It
was
kind
of
a
follow-on
we
had
mentioned
AI
a
little
bit
while
we
were
talking
and
I
realized
that
there's
probably
some
relevant
work
and
metrics
that
we
would
want
to
track.
This
is
a
brand
new
thing.
So
now
would
be
the
time
for
us
to
start
talking
about
it.