►
From YouTube: CHAOSS Value (Now OSPO) Working Group, October 6, 2022
Description
Minutes and notes from this meeting can be found on https://chaoss.community/participate.
A
Chaos
largely
for
people
are
coming
to
chaos,
largely
for
the
investment
in
software.
They
they
want
to
see
the
metrics
live
and
so
I
think
these
hosted
Solutions
are
going
to
be
important,
but
I
I
think
also
from
talking
to
Daniel
helping
organizations,
understand
the
metrics
and
build
their
strategy
as
a
Services
component.
That
petergia
offers
that
you
know,
regardless
of
the
software
is
going
to
be
part,
is
a
big
part
of
the
value
ad
for
ospo's,
and
you
know
we
kind
of
understand
the
reasons.
A
People
I
suppose
choose
different
Technologies
and
I
think
it's
largely
pivoting
on
a
question
of
scale,
so
we're
working
on
a
sort
of
a
joint
KS
software
venture
to
Advance
chaos.
D
D
So
the
first
I'd
heard
of
any
transition
was
yesterday
in
the
osbology:
oh
okay,
but
I
kind
of
got
from
Anna's
explanation.
There
I
kind
of
understand,
what's
going
on.
Okay,
so.
C
We're
just
and
then
Dan
welcome,
I,
don't
know
if
you've
been
on
this
call
before
and
if
not
that's
cool
and
but
then
maybe
to
Elizabeth's
point
for
Tony
and
Dan.
Really
what
it
is
is
the
value
working
group.
C
So
we
have
a
variety
of
different
working
groups
in
the
chaos
project,
for
example
the
Dei
working
group
or
a
risk
working
group,
and
this
was
the
value
working
group-
has
kind
of
shifted
several
times
over
the
last
couple
years
in
a
way
that
has
been
kind
of
like
a
boat
drifting
out
at
Sea,
sometimes,
and
so.
C
Yeah
and
so
really
the
the
shift
is
to
kind
of
you
know,
kind
of
cement
things
down
in
this.
C
As
you
saw
yesterday,
Tony
with
that
particular
shift
towards
I
suppose
and
helping
uspos-
and
this
could
be-
and
we'll
have
to
sort
this
out
as
we
go
forward.
But
this
could
be
things
like
for-profit
I
suppose
this
could
be
government
I
suppose
this
could
be
University,
I,
suppose
we'll
kind
of
have
to
sort
that
out
I!
Think
as
we
go.
D
Yeah
and
just
for
your
benefit,
Matt
I
I
am
a
startup.
A
silicon
startup
called
rapid
silicon
and
I
am
the
director
of
our
osbo
inside
of
this
company
and
as
a
startup.
We
we
basically
everything
we
do,
including
our
tape
out
on
open
source
infrastructure,
so
we
realized
very
early
that
we
needed
to
have
an
osbo
to
figure
out
and
manage
things.
That
was
one
of
the
key
things
that
brought
me
over
to
the
company
from
where
I
was
before,
and
in
some
of
my
previous
conversations
here.
D
The
value
working
group
is
of
particular
importance
to
me
because
we
are
taking
a
lot
of
Open
Source
content
in
the
Eda
world
and
turning
it
into
a
commercial
product,
and
we
want
to
understand
the
value
of
where
can,
where
is
the
most
tactically
beneficial
place
for
us
to
contribute
back
into
the
community
documentation
or
code
or
something
else
right.
So
yeah.
This
all
aligns
with
my
understanding
of
okay
right.
C
B
Yes
and
I've
changed
the
title
over
there,
so
so
first
thing
is
on
the
name
team.
We
have
a
PR
like
I
and
I
created
an
issue
and
a
PR2
yeah,
so
yep,
so
I
I
went
through
the
PR,
but
my
only
concern
in
that
PR
was:
let's
realign
the
focus
areas
that
that
we
want
so
that
we
can
like
merge
it
or
maybe
we
can
merge
it
and
then
revise
it
onwards.
Is
the
two
options:
yeah.
B
So
my
first
concern
was
like
that
this
was
a
small
Miner
I'll,
be
like
chaos,
osmometric
working
group.
My
second
concern
was
like
main
object.
These.
B
Is
on
this
one,
this
one,
so
we
need
to
have
a
like
clear
picture
on
the
focus
areas,
because
we
we
needed
a
detailed
Focus
area,
because
in
the
readme
we
have
a
focus
area
that
we
focus
on
right.
Now
we
have
like
individual
value
organization
value.
Does
it
align
with
the
new
direction
that
we
are
taking
like.
B
A
B
Yep
no
purpose
is
fine,
like
let
me
open
the
detail,
a
file
change
so
that
I
can
show
my
comments.
Okay,
so
I'm
fine
with
the
scope
and
I
have
jot
it
out.
I'm
fine
with
the
community
I
was
unable
to
comment
on
this
area
like
these
are
the
areas
that
needs
to
be
worked
on
over
here.
Let
me
expand
that,
so
how
to
join.
It's
like
you're,
welcome
to
join,
explaining,
find
more
Azure
contributor.
Let
me
please
this
was
wrong.
B
Yep,
this
area,
all
the
contributors
are
welcome
to
join
in
the
value
working.
The
area's
interest
include
social
value,
which
we
previously
decided
to
move
it.
That
was
still
there
in
the
same
revision
so
and
we
have
like
individual
organizational
value
and
digital
value
familiar
value.
There
needs
to
be
realigned
so
that
we
we
are
asking
people
to
come
to
join
and
we
we
should
give
them
a
clear
direction
that
what
our
goal
is
are
like
how
they
align
their
interests
with
them.
Yeah,
that's
fine.
C
I
mean
I
think
we
could
maybe
sort
that
out
here
today,
which
would
be
good
from
so
I
think
we
should
probably
merge
this
and
then
issue
another
PR
against
that,
okay
against
the
new
code,
the
other.
The
other
thing
to
think
about
is
for,
for
those
of
you
that
also
kind
of
don't
know
just
from
a
working
perspective.
I'll
share
something
here.
C
Okay,
so
I
just
put
it
in
the
chat
but
Tony
I,
don't
know
if
you've
seen
this
before
the
spreadsheet
I
have
yeah
okay.
So
the
really
kind
of
what
vanat
is
talking
about
is,
like
your
row,
20
row
27..
You
know
what
I
mean
we
kind
of
have
these
these
holders.
C
As
we
move
to
the
new
website
design,
the
concept
of
focus
areas
is
going
to
kind
of
go
away,
so
just
because
it's
going
to
be
a
little
bit
easier
to
serve
the
metrics
based
on
search
and
so
fundamentally
we're
going
to
be
using
context,
tags
and
keyword
tags
so
that
people
could
say
like
I'm
interested
in,
for
example,
they
could
type
organizational
value
or
they
could
type.
C
You
know
what
I
mean
it'll
bring
up
the
metrics
that
are
kind
of
tagged
in
that
way,
and
they
may
be
across
different
working
groups
as
well.
So
the
focus
area
is
for
us
anymore.
They
used
to
be
kind
of
important
because
they
would
show
up
in
our
PDF
and
in
our
release.
There
were
ways
for
us
to
organize
things
to
show
to
people,
but
as
we
had
like
75
metrics,
the
the
organizational
structure,
just
kind
of
started
falling
apart,
and
we
realized
that.
C
A
search
model
would
be
considerably
more
sensible,
so
that's
what
we're
doing
this
summer,
this
fall,
so
the
focus
areas
for
us
anymore
are
really
just
meant
to
help
the
working
group
work.
So
we
could,
in
theory,
get
rid
of
all
Focus
area
names.
You
know
what
I
mean
we
could
just
say
any
metric
in
the
hospital
working
group
is
just
it's.
A
C
A
metric
and
will
identify
him
based
on
how
we
tag
them.
You
know
what
I
mean
so
like
different
different
metrics
might
have
different
collections
of
tags
or
we
can
to
vinod's
point.
We
can
keep
the
focus
areas.
It's
okay,
you
know,
but
it
again
it's
just
really
for
us
so
like
it
would
be
possible.
I'll.
Just
do
an
example
here
to
your
point:
Tony
like
we
could.
You
know
like
look
at
a
focus
area
which
is
I.
Don't
know
like
you
know,
investment
or
something
like
that.
B
C
Know
like
how
you
how
we
understand,
but
again
that's
totally
just
for
us
and
then
we
would
think
about
how
we
consider
possible
Investments
I,
think
that
may
not
be
the
greatest
example,
but
I'm
just
trying
to
get
us
like
get
it
off
the
ground.
So
I
don't
know
if
I,
if
that
makes
sense,.
C
So,
just
just
so
you
know
so
the
the
value
we're
not
really
changing.
Just
in
terms
of
the
metrics,
we
were
partnering
up
with
the
to
do
group,
basically
there's
a
lot
of
organizations,
as
you
know
whether
they're
for-profit
government
academic,
that
are
starting
to
develop
open
source
program
offices
for
a
variety
of
different
reasons
and
we're
partnering
with
the
to
do
group
to
kind
of
rework
the
value
working
group
to
kind
of
serve
as
the
home
for
how
open
source
program
offices
think
about
metrics
that
are
relevant
to
them.
C
C
All
right
so
did
you.
You
merge
that
yep.
B
Not
anybody
so
with
that
we
have
an
old
PR
on
the
on
this
which
you
sent
when
we
were
removing
the
suicide
social
value.
So
I
don't
think
this
needs
to
be
merged.
It'll
create
a
conflict,
so
maybe
I
declined
that
or
but
then
I
don't
get
credit
I
know,
but
for
the
future
you
will
get
the
credits,
I
don't
care.
So
what
was
his
name
this
one
when
we
moved
the
societal
value
to
DIY.
C
C
B
So
I'll
I'll
I'll,
not
I'll,
not
close
it
today,
but
I
want
to
keep
it
for
a
while,
so
that
when
we
rework
on
the
focus
area
and
then
I'll
keep
a
contribution,
you
have
already.
C
B
B
C
But
I
what
I
actually
think
we
should
do
first
before
we
think
about
the
focus
areas
is
like
what
is
the
mission
of
this
okay?
So
now
that
we
have
potential
members
from
the
to
do
group
and
even
potentially
osbo
plus
plus
that
work
as
well,
which
is
I
suppose
within
universities
and
government
agencies
and
like
still
keeping
you
know
without
losing
what
we
have
done,
yep
so
I'm
kind
of
curious
as
to
like
Sean
or
Elizabeth.
C
A
A
You
know
where
they
have
they're
trying
to
figure
out
what
to
do
with
an
ospo
indeed,
and
how
to
how
to
count
things
inside
of
an
ospo
how
to
bring
metrics
to
the
front
and
make
them
useful
in
the
form
of
metric
models,
so
I
mean
I.
Think
it's
about
taking
an
ospo
perspective.
First,
more
than
anything.
A
It
means
that
there
are
I
think
what
we've
defined
with
metrics
models
are
particular
areas
that
I
suppose
may
be
interested
in
whether
they
involve
assessing
the
welcomingness
of
a
community
or
assessing
the
velocity
of
a
community.
Those
are
both
questions
that
are
specific
health
questions.
That
I
suppose
have
asked
repeatedly
newcomer,
stickiness
understanding,
speed
of
responsiveness.
A
I
mean
these
are
there's
a
there's,
a
there's,
a
repertoire
of
maybe
five
or
six
core
questions
that
I
suppose
come
with
wanting
solutions
to
different
flavors
of
those
questions
and
I
think
this
is
maybe
about
refining
the
flavors
that
are
offered
in
a
kind
of
a
more
stock
or
standard
chaos,
tool
distribution,
so
that
people
can
get
the
insights
that
they
want
more
quickly.
Helping.
A
C
A
D
D
Even
when
I
was
participating
about
a
month
ago,
actively
like
a
key
set
of
the
metrics
that
I
found
on
one
of
the
PRS
was
a
suitability
for
use
metric
right.
It's
a
like.
If
someone
in
one
of
our
development
teams
comes
to
me
in
the
hospital
and
says
hey,
can
we
take
on
and
work
on
this
project?
I
have
to
prove
to
senior
leadership
that
it's
worthwhile
for
us
right,
and
so
a
suitable
for
use.
Kind
of
metric
is
also
one
that
we
were
taking
a
look
at
about
a
month
ago.
C
Okay,
because
I
I'm,
having
thought
about
this
for
a
couple
days
now,
I'm
thinking
if
we're
I,
like
your
your
points,
Sean
about
taking
the
ospo
perspective.
First,
like
I,
really
like
that
and
well.
A
C
No
I
like
that,
because
I
think
if
we
have
members
from
again
the
to-do
group
or
Hospital
plus
plus
there's
going
to
be
kind
of
a
desire
to
have
like
artifacts
that
can
go
back
to
the
ospo
and
right.
That's
helpful.
A
C
B
C
Sometimes
we
don't
right
so
kind
of
for
for
Tony
and
Mako
and
we
do
have
a
metrics
model
working
group
and
we'll
have
a
metrics
model.
That
is
say
called
welcomingness
and
you.
D
C
To
understand
community
welcomingness
and
in
that
working
group,
we'll
kind
of
just
brainstorm
like
what
would
be
the
metrics
that
we
would
care
to
look
at
to
understand
welcomingness
and
it's
quite
possible
that
five
of
the
seven
metrics
that
we
are
interested
in
exist
in
the
chaos
project
and
two
just
don't
exist.
We
have
to
publish
those,
but
it's
a
model.
First
kind
of
orientation,
I
think
that
might
be
kind
of
a
good
idea
here.
So
I.
A
Like
that
one
and
that's
I
mean
the
model.
First
orientation
is
really
taking
a
it's
really
putting
this
common
reason
that
people
are
coming
to
chaos,
which
is
to
see
something
to
get
some
metrics,
not
necessarily
to
Define
them.
So
I
think
we
do
have
a
bigger
consumer,
Focus
now
and
I
think
this
group
reflects
that
and
making
the
things
that
we've
accomplished
easily
viewable
in
the
context
of
projects.
Someone
cares
about
I
think
that's!
That's
our
bread
and
butter
going
forward
and
the
metrics
models
help
to
serve
that
agreed.
A
Or
science
or
any
other
industry,
or
do
we
care
that's
my
question
I
think
there
will
I
think
we
care
I,
think
there'll
be
particular
things
that
I
suppose
and
Academia
are
interested
in
that
are
different
than
academic,
corporate
I.
Suppose
and
that's
okay
I
think
how
much
we
develop.
Each
part
of
the
space
depends
on
engagement
from
each
part
of
the
space
yep.
B
Ahead,
my
question
was
on
the
previous
disc
session
on
the
model.
First
aspect
is,
then,
if
we
are
taking
that
approach
as
a
model,
first,
then
how
we
distinguish
our
work
as
an
ospo
working
group
from
the
model
working
group.
Both
are
working
in
a
similar
Direction,
but
we
are
taking
a
hospital
perspective.
B
C
I
think
the
I
mean
part
of
it's
good,
there's
going
to
be
time
zones.
A
lot
of
the
people
who
participate
in
the
metric
model
working
group
are
in
Asia
Pacific,
and
so
that's
a
it's
pretty
late
in
the
day
for
us,
so
that
we
can
accommodate
folks
in
Asia
Pacific,
so
I
think
that
discussion
can
still
carry
on
there.
So
basically
we
do
have.
This
is
the
metrics
model
working
group,
and
these
are
the
models
that
we've
been
developing
there.
C
B
So,
probably
so
yeah,
maybe
there
should
be
some
alignment
with
these
two
working
groups
so
that
we
don't
reinvent
this
thing
that
we
have
already
done
it.
One
group
I.
C
Mean
quite
possibly,
we
could
just
continue
to
have
this,
be
like
a
collection
of
ospo
like
Atomic
metrics,
like
the
kind
of
the
lowest
level
things
that
need
to
be
developed,
and
when
we
develop
a
new
metric
model,
we
simply
place
it
here.
Yeah
I
mean
there's
nothing
that
says
yeah.
If
we
develop
it
here,
it
must
go
on.
C
Maybe
that's
the
approach
that
yeah,
you
know
so
I
have
a
comment
too.
So
how
do
we.
C
C
I
was
gonna.
Also
make
a
point
just
to
your
question,
Elizabeth
and
I.
Think
Sean
I
think
this
is
what
you
were
saying
and
I
agree
that
it's
I
think
we
developed
the
metrics
and
metrics
models
and
tooling
around
the
the
people
who
are
present
in
this.
In
this
call,
I
don't
know
if
that's
what
you're
getting
at
John
but
like
the
you're.
B
C
A
D
A
Think
yeah
I
think
I
have
some
I
think
I
have
two
zooms
up
right
now
is
what's
going
on,
yeah
I
I
was
I,
think
what
I'm
saying
is
the
ospo
lens.
Even
this
is
the
the
lens
that
we
take.
C
So
then
I
have
another
okay,
so
then
I
have
another
question
kind
of
on
that
Sean.
Do
you
think
it's
going
to
be
possible
to
deploy
some
of
these
metrics
models
in
the
public,
facing
instance
of
agar
that
you
have,
or
maybe
you
could
talk
a
little
bit
about
your
conversation
with
Daniel,
like
kind
of
what.
A
Yeah
I
mean
so
I
mean
Daniel
and
I
talked
about
the
SAS
possibilities
emerging
through
the
metrics
model,
working
group
in
Asia,
Pacific
working
group-
and
you
know
he's
aware
of
it-
he's
excited
about
it
and
we
discussed
the
software
as
a
service
model
for
auger,
which
is
coming
down
the
pike
here
in
the
next
week
or
two
and
I
I.
My
ambition
would
be
to
deploy
both
in
in
a
public-facing
way.
A
C
A
And
then
it's
making
those
models,
you
know
making
the
model
implementations
visible.
So.
C
How
so
like?
Let's
say
that
with
Tony
on
the
call
here
so
like,
let's
say
that
there
are
particular
repositories
that
are
communities
that
Tony's
interested
in,
and
we
had
you
and
I
had
talked
about.
This
too
Sean
like
SAS,
can
help
like
kind
of
precede
some
of
the
organizations
that
don't
have
the
time
and.
B
A
C
A
A
There's
so
the
way
that
we
envisioned
going
forward
is,
we
do
have
probably
20
000
repos
that
are
commonly
or
have
been
requested
at
various
times
by
different
entities
that
seem
to
have
some
popularity,
so
we'll
see
the
the
shared
instance
with
those
and
then,
when
you
log
into
it,
you
create
create
an
account
and
you'll
be
able
to
indicate
which
orgs
and
repositories
you're
interested
in
seeing
in
your
view
of
it,
and
you
would
then
see
data
about
your
repositories
that
you
care
about.
A
Think
in
the
metric
model
working
group
we
have
more
I
think
we
have
a
consistent
group
of
stakeholders
that
perhaps
don't
represent
the
entire
world
of
osbo
stakeholders,
and
through
this
group
we
can
refine
those
models
to
be
not
only
useful
to
to
other
stakeholders,
but
also
to
the
people
who
are
part
of
this
group
and
to
other
chaos.
Consumers
that
have
ospos
that
maybe
take
on
a
different
form,
because
we've
learned
that
these
hospitals
are
heterogeneous.
They
have
many
different
concerns,
so.
D
Me
in
our
organization,
so
I
want
to
track
metrics
and
am
tracking
metrics
for
public
repost,
but
I
also
have
to
track
metrics
against
our
internal
repos.
Our
Forks
of
those
repos
to
kind
of
cattle
prod,
some
of
our
developers
to
upstream
and
stuff,
like
that.
So
I
kind
of
need
both
sides
of
auger
and.
A
That,
and
so
that
merely
requires
that
you're
using
tokens
that
have
access
to
those
private
repositories,
and
so
that
would
probably
still
require
a
separate
instance
of
auger,
but
that's
increasingly
easy
to
do
right.
Okay,
because
you
obviously
don't
want
the
private
repo
data
available
to
others
so
right
that
that
would
be
a
reason
that
you
would
still
need
a
your
own
instance
of
auger
if
you're,
incorporating
private,
repos
and
I
think
it's
the
same
situation
with
grimorlab
effectively.
If,
if
it's
not
public,
then
you
need
special
keys,
and
you
probably
don't
want
that.
C
A
D
D
That
I'm
I'm,
going
through
right
now,
is
that
we
don't
I,
don't
need
to
get
into
the
internals
of
our
company,
but
I'm
trying
to
run
auger
on
some
local
hardware,
and
just
the
walkthroughs
aren't
always
completely
transparent.
To
me,
like
the
instructions
are
a
little
contradictory
depending
on
where
you
start,
and
some
of
the
how
to
but
yeah
just
how
to
spin
up
an
auger
instance
as
quickly
and
easily
as
possible
would
be
beneficial,
especially
if
there
was
like
some
way
to
take.
A
A
C
So
I
mean,
is
it
like
Sean
like?
Is
it
a
goal
of
this
of
this
usbo
working
group
to
provide
this
SAS
service
like.
A
C
Okay,
so
then
another
question:
this
is
really
great.
Thank
you
for
so
again
for
you
Sean,
so
like
with
respect
to
the
SAS
instance.
B
C
Because
I
know
that,
like
our
like,
the
work,
that's
being
done
in
Asia
Pacific,
like
the
really
the
the
main
intention
is
to
provide
the
metrics
models.
You
know
what
I
mean
like.
A
I
would
I
would
answer
that,
yes
and
what
those
metrics
models
are
I
think
should
I
would
like
to
see
them
molded
to
fully
meet
the
requirements
that
the
particular
hospitals
have
and
that
that
would
help
us
to
refine
and
make
more
generalizable
the
metric
models
that
we
have
so
I
believe,
there's
a
probably
a
prospective
Gap
in
the
models
we've
built
so
far
that
can
be
filled
by
you
know
wider
input
and
real-time
okay
I'm
an
ospo.
This
is
what
I
need
so
I
think
the
iterate,
the
iteration
power,
is
significant.
C
Okay,
do
you,
okay,
I'm
I'm,
trying
to
also
like
visualize
what
this
service
from
auger
would
look
like?
Do
you
have
any
visual
of
it
at
the
moment
or
not
yet.
A
Like
I
have
a
lot
of
different
visuals,
but
I
don't
have
a
coherent
whole
okay
right
now.
So
there
are
a
number
of
front-end
pieces
that
people
have
put
together.
A
C
A
A
A
A
Least,
yeah
people
yeah
in
two
yeah
in
two
weeks.
Yes,
are
you
going
to
Sweden
yeah
but
I'll
be
back?
Okay,.
A
C
So
I
kind
of
see
it
as
as
three
things
so
one
picking
an
ospo
perspective
yep.
It
is
important
to
demonstrate
in
that
and
that
we're
a
model
first
orientation,
okay,
we're
about
kind
of
bringing
together
metrics
and
ways
that
are
meaningful
for
ospo's
and
then
two
is
just
I
was
trying
to
and
then
two
is
this.
Then
her
intention
is
to
deploy
these
metrics
models
via
VIA
SAS,
Solutions,
okay,
so
that
hospitals
can
interact
with
them.
B
C
Even
doing
the
talk
yesterday
in
the
hospitality
like
clearly
different
organizations
are
at
different
levels
or
different
kind
of
stages
of
ospos,
but
there
are
clearly
like
the
ospos
at
the
large
organizations
that
run
quite
differently
than
the
us.
There
was
like
a
question
you
know
like
how
do
I
even
start
an
ospo
or
something
like
that.
C
I
think
that's
extremely
helpful
for
I
suppose
that
are
potentially
early
in
in
their
Hospital
journey.
I.
D
And
along
those
lines,
how
heterogeneous
osbos
are
one
of
the
experiences
I
had
I?
Think
I
shared
this
with
Sean
and
Elizabeth
when
I
first
started
coming,
I
went
to
OSS
in
Austin
over
the
summer,
and
a
lot
of
people's
perspective
was
from,
like
I,
won't
call
it
a
combative
standpoint
but
like
trying
to
bring
an
osmo
into
an
organization
that
hasn't
had
an
osbo
before
and
maybe
has
some
resistance
to
it.
D
C
D
D
All
of
those
folks
are
very
much
like
they're,
very
good
at
what
they
do
of
like
bringing
an
osmo
into
an
existing
organization,
but
when
the
organization
does
is
like
tell
us
what
to
do
like
that's
actually,
literally,
what
the
CEO
of
our
company
said
is
like
I
was
hired
to
drive
open
source
at
the
company.
I
was
told
I
had
whatever
resources
I
needed
to
have,
but
then
how
to
like
build
that
out
with
with
total,
like
latitude
like
there
wasn't
a
way
to
I.
D
I
didn't
couldn't
find
a
good
way
to
wrap
my
arms
around
that.
Where
do
you
even
start
when
everything
is
possible?
Is.
D
C
Okay,
it's.
C
A
B
C
They're,
the
metrics
that
we
have
to
tell
the
story
to
Executives.
That's
a
different
group
of
metrics,
so
I'm
kind
of
I'm
wondering
if,
as
we
go
through
this
process,
part
of
what
this
working
group
can
do
too
is,
for
example,
Tony
like
if
you're,
if
you're
having
success
in
what
you're
doing
like
if
the
metrics
are
helping
right
get
through
this
Green
Field
like
like.
Why,
like?
How
did
you?
How
was
that
helpful?
Because
others
might
really
appreciate
that.
D
Still
figuring
that
out
day
by
day
myself,
but
yeah
I
just
wanted
to
make
sure
I
mentioned
that,
because
maybe
if,
if
you
are
in
one
of
those
organizations
like
just
off
the
top
of
my
head,
like
a
metric
that
might
be
useful,
it's
just
like
go,
do
a
scan
of
all
of
the
organiz
or
the
code
projects
that
you
might
be
interested
in
using
and
find
out
going
back
to
my
suitability
perspective
earlier
is
like
how
do
you
tell
your
developers?
Okay,
this
is
a
new
thing.
D
D
D
Nothing
else
that
gives
a
new
osbo
lead
like
myself,
a
starting
point:
yeah.
C
D
A
D
A
If
I
think,
if
you
have
those
kinds
of
questions
yeah,
we
can
address
them
so
I
think
if
you
have,
if
you
want
good
documentation,
we
can
go
identify
a
range
of
documentation.
D
And
that's
fine
but
like
for
me:
I've
got
a
one
of
the
projects
that
one
of
our
development
teams
works
in
the
code
is
fine,
but
we
intend
to
productize
it
and
release
it
to
customers,
but
the
documentation
in
that
project
sucks
so
we're
having
all
of
our
developers
spend
their
time.
Writing
really
good
docs
for
that
project.