►
From YouTube: CHAOSS Value Working Group August 25, 2022
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
B
Welcome
everyone
welcome
to
the
chaos
valley
working
for
meeting
of
october
25th.
Please
add
yourself
in
the
meeting
minutes.
B
C
B
C
The
this
similar
to
the
dei.md-
it's,
I
think
we
were
look
we're
looking
at
this
as
a
signal
of
how
to
get
help
on
a
project
when
you're
new,
so
it's
different
than
how
you
contribute
it's
different
than
code
of
conduct.
The
whole
aim
of
a
file
like
this
is
to
signal
that
you
hear
these
channels
that,
as
a
newcomer,
you
can
reach
out
to
and
get
help
on
specific
things
and
elizabeth
fill
in
the
blanks.
If
I'm
not
covering
quite
all
of
what
we
discussed
there,
which
I'm
sure.
D
E
E
D
Or
we
could
use
help
with
like
this
interview
campaign.
That's
another
thing,
that's
kind
of
new
and
coming
up,
so
it's
more
than
like
just
here's
an
issue,
go
fix
it
and
close
it
like
it's
more
of
like
more
descriptive
of
what
the
project
where
the
project
feels
like
they're
they're
lacking
or
it
could
use
some
help
like
our
documentation
or
whatever
it
might
be.
But
that's.
D
C
He
was
and-
and
I
do
think
that
where
a
project
specifically
needs
help
was
the
most
that
we
did
discuss
that
more.
I
obviously
had
my
own
construction
of
what
I
want
that
to
be,
but
I
think
that's
not
what
we
talked
about,
that
we
spent
most
of
our
time
on.
D
Yeah-
and
I
think
it
came
from
the
fact
that
tony
had
joined
to
talk
about
that
business
readiness
model
and
he
was
also
saying
like
from
his
point
of
view
as
a
company
like
where
his
companies
should
offer
value
to
an
open
source
project
like
that's,
where
they
were
kind
of
struggling
as
a
company
and
identifying
where
they
could
be
of
the
most
use
to
projects
that
they
care
about
and
that
they
depend
on
and
things
like
that,
and
so
he
was
thinking
if
they
just
had
like
a
help.
D
D
Kind
of
relationship,
a
stronger
support
for
the
selection
of
a.
C
C
I
I
think,
similar
to
what
what
we
might
be
doing
with
the
dei
file.
We
would
have
a
like
one.
I
think
the
current
idea
for
the
dei
file
is
that
we
have
every
you
know
you
have
a
community
repository
where
we
keep
that
file.
So
perhaps,
if
it's
a
project
that
has
40
repositories,
chaos,
for
example,
there's
a
particular
name
of
a
repository
within
any
given
org,
where
we
keep
these
kinds
of
things.
A
A
And
I
mean
if
it's
so
if
I
was
thinking
about
how
an
individual
can
provide
value
to
a
project
versus
how
an
organization
can
provide
value
to
a
project.
Those
are
different
things
to
me.
A
Yes,
so
an
individual
like
the
way
I
would
talk
to
just
a
single
person
would
be
different
than
the
way
I
would
talk
to
like
a
company.
That's
like
hey.
We
would
like
to
support
chaos.
You
know
what
I
mean
we
like
to
bring
value.
Those
are
two
different
things,
not
different,
but
you
know
what
I
mean.
So
if
it's
about
like
company
or
organizational
value
that
can
be
contributed
to
a
project,
that
certainly
would
not
be
issues
I
mean
it
would
be
to
me
it
would
be
things
like
financial
support.
A
It
would
be
things
like
you
know,
helping
helping
around
in
our
case,
maybe
like
data
science
support,
it
would
be
around
things
like
software
development
support
like
these
kind
of
higher
level
things
and
then
under
their
individual
issues,
right
or
dei
badging
support
like
we're
gonna,
do
this
at
scale
like
we
could
use
a
hand.
A
You
know
whatever
mozilla,
to
really
kind
of
make
sure
this
thing
remains
stable.
That's
a
different
kind
of
help,
documents.
C
C
Say
yeah,
I
would
say
that
there's
so
between
between
the
help.mbd
file,
as
discussed
so
far
and
project
roadmap,
I'd,
say:
there's
some
some
continuum
of
detail.
Yeah
and
I
was
thinking.
A
C
And
the
question
is
what
what
maybe
this
is
the
discussion
item,
because
I
don't
think
we
got
this
far
as
what?
What
is
that
level
of
detail
that
we
need
in
order
for
it
to
be
a
useful
file?
And
not
you
know,
platitudes
like
I
need
help
with
documentation
to
me.
That's
a
platitude,
it
doesn't
give
me
any
specific
direction.
It's
like.
C
A
My
my
other
concern
is
that,
like
a
help.md
file,
buried
in
an
orange
set
of
repositories
will
never
be
found.
E
E
C
Well,
so
it
would
I
mean
in
my
mind,
it
would
operate
in.
It
would
follow
exactly
the
same
pattern
as
the
dei.md
file,
and
I
think
I
said
you're
what
what
is,
what
is
the
difference
in
the
effect
of
the
findability
there?
I
suppose
it's
that
people
aren't
even
going
to
look
for
it,
so
they
won't
use
it.
They
won't
take
action.
Well,.
E
F
F
C
D
D
I
think
I
think
that
was
well.
That
was
his
motivation
personally,
but
I
mean
I
guess
it
could
be
either.
A
B
A
E
B
B
So
so
the
decision
is
that
we
are
going
to
take
it
to
the
journal
or
we'll
just
think
on
it
and
we'll
be
discussing
the
next.
D
A
D
C
Yeah,
I
mean
I
I
think
ultimately
it
does.
This
was
to
me
it
was
implied.
This
was
leading
towards
a
badge
that
the
the
metaphor
of
dei
dot,
md
file,
felt
foregrounded
to
me
and
and
the
the
badge.
I
suppose
that
which
wasn't
discussed
before.
I
think
the
point
here
is
to
you
show
up
at
a
project
and
you
honestly,
if
you
don't
know
open
source
and
you've,
never
done
it
before.
B
Moving
to
the
next
item
in
the
agenda
is:
what
is
the
value
from
corporate
open
source
software
point
of
view.
B
Okay,
I
was
moving
to
the
second
item
in
the
agenda
this.
What
is
the
value
from
a
corporate
open
source
point
of
view,
metric
model
discussed
here?
So
can
anyone
share
the
screen?
Someone.
B
E
C
If
I'm
a
business
and
I'm
trying
to
about
it's,
it's
similar
to
other
metrics,
but
expresses
more
detail
effectively
if
I'm
evaluating
a
metric
from
a
business
perspective,
how
prepared
is
this
project
to
be
as
part
of
my
business?
In
other
words,
if,
okay,
it
might
be
the
kind
of
decision
you
make
when
choosing
joe
bernetti's
as
an
alternative
to
kubernetes?
That
project
doesn't
exist.
Yet
I
assume
someone
will
create
it
as
soon
as
we
hang
up,
but
it's
that
kind
of
thing
where
you
know
we're
evaluating.
A
Okay,
so
this
is
like
you're
standing
inside
of
the
organization
yeah
and
you're
surveying
a
variety
of
different
open
source
projects
that
may
suit
a
particular
need
that
you
have
yeah
exactly
okay,.
D
Yeah
and
the
way
this
tied
back
into
the
help.md
was
tony's.
Point
was
well.
If
I
I
have
this
great
project
that
I
think
we
can
use,
but
they're
kind
of
lacking
a
little
in
documentation.
Well,
hey!
That's
something
that
my
organization
can
help
with.
So
that's
not
a
deal
breaker.
That
would
make
strength
in
the
relationship
that
kind
of
stuff.
A
C
A
C
E
A
B
Is
it
here
it
is
so
this
is
a
model
I
would
say
we
can
add
it
to
the
model,
because
we
are
thinking
of
it
in
terms
of
model.
What
different
metrics
that
can
be
used
to
assess
the
readiness
of
an
open
source
project
that
an
organization
can
adopt.
Okay,.
A
So
do
you
think
the
process
would
be
that
we
kind
of
accept
these
changes?
You
know
what
I
mean
and
then
hand
it
off
to
the
metrics
model
group.
B
C
Think
the
last
time
we
got
to
the
point
where
we
felt
like
we'd
done
as
much
as
we
can
and
we
needed
a
couple
weeks
to
reflect
before
we
acted
again
right.
I
think
this
isn't.
This
is
largely
developed
by
the
person,
not
here,
so
perhaps
we
should.
Perhaps
we
should
table
this
and
not
try
to
finish
it
without
the
main
person
here.
A
B
Yes,
we
did
the
same
thing
for
another
metric
model
which
we
developed
in
the
value
working
group,
but
like
even
before
handing
to
them.
We
as
a
group
wanted
to
make
sure
is
it
ready
for
us
to
hand
it
over
to
the
value?
B
B
E
Like
edit
yeah
review,
it
document.
A
You
know
I
just
I
think,
a
few
things,
but
not
if
you
could
you're
you're
in
the
metrics
model
working
group.
So
if
you
could
kind
of
take
a
look
like
things
like
user
stories,
I
think
right
as
points
you
know
what
I
mean
like
one.
Two,
three
more
like
from
a
community
management
community
manager
perspective.
This
matters
from
a
organizational
employee
perspective
this
matters,
so
I
think
we've.
A
A
Yes,
I
think
our
why
it
matters
is
usually
pretty
small
at
this
point
right
why
you
would
care
about
business
readiness
of
an
open
source
project.
A
And
then
was
the
proposal
from
you
all
last
time
that
it
also
includes
things
like
spdx,
like
yeah.
C
These
are
fun
so
yeah
when
you're
looking
at
business
readiness
things
like
licensing
come
into
play
so,
okay,
it
has
some
similarities
with
other
things
that
are
metric
models.
I
think,
but
it
really,
it
is
significantly
more
focused.
I
mean
the
question
is
narrower.
Okay,
I
mean
that's
the
that's.
The
distinguishing
characteristic
for
this
metric
model
is
that
I
think
it's
a
model
is
a
model
right,
yes,
yeah,
so
that
it's
just,
I
think
it's
a
little
bit
more
narrow
in
its
focus
than
some
of
the
other
work.
A
C
So
business
business
readiness
is
the
target
is
making
it.
You
know
using
the
information
to
make
a
decision
before
becoming
engaged
and
most
of
the
other
models
that
I
think
we're
working
on
presume
a
level
of
engagement
already
we're
not
using
them
to
decide
and
now
do
they
would
they
apply
equally,
possibly
I
haven't
looked
carefully
at
the
the
you
know:
I've
been
ticked
and
tied
the
different
metrics
involved
to
determine
similarity.
A
A
E
B
Yeah
readiness,
as
a
keyword,
was
initially
proposed
by
dr
wessermann
in
the
issue
108.
We
have
in
the
meeting
minute
so
yeah.
That
can
be
a
to
me.
It's
more
like.
As
an
organization.
We
are
trying
to
assess
whether
that
project
is
suitable
for
me
to
adopt
or
not
so
right.
A
A
A
C
What
I
mean
yeah
you're
right
this
is
this
is
less
of
it.
Is
it's
absolutely
aimed
at
a
making
a
decision
at
a
moment
in
time
and
not
tracking
the
you
know,
I
would
expect
historical
trajectory
would
be
of
value,
but
obviously,
after
an
organization
makes
a
decision,
they're,
probably
looking
at
different
metrics.
E
D
A
E
B
B
E
E
B
A
B
E
B
B
C
Think
we
were
reflect.
I
think
there
was
a
moment
of
reflection
on
what
concepts
have
sort
of
been
the
center
of
the
value
working
group,
and
I
think
some
of
those
retain
utility
retained
value
to
the
chaos
project
and,
as
we
focus
the
value
working
group
where
it
is
right
now
we
may
we
may
need
to
just
keep
a
list
of
these.
Certainly
social
value
policy
questions
influence
these
these
things.
They
may
not
be
part
of
the
domain
of
the
value
working
group,
but
we
need
to
make
sure
as
a
project
as
a
larger
project.
B
A
A
Is
just
it's
just
kind
of
you
know:
removing
the
societal
value
component,
because
that's
now
ndei
and
just
kind
of
just
cleaning
up
this.
These
goals
and
purposes
statements
through
here.
E
A
A
About
we
had
looked
at
value
from
a
variety
of
ways
how
a
community
generates
or
help
the
value
of
people's
contributions.
E
A
B
E
B
E
E
F
A
F
Just
a
thought:
yeah,
let's,
let's
revisit
okay
after
september
9th,
whatever
meeting
we
have
after
september
9th.
E
A
E
A
E
B
B
So
maybe
we
should
give
it
a
read
because
it
was
previously
labor
investment
and
we
had
renamed
it
and
changed
a
lot
of
things.
So.
E
B
Yes,
I've
removed
and
aligned
it
with
the
title
like
to
be
more
like
reflecting
what
we
are
trying
to
show
from
the
title.
It's
like
how
many
hours
employees
are
working
on
a
project
and
how
that
can
be
assessed.
Okay,.
B
A
B
This
this
will
be
more
of
a
filter
now,
like
a
number
of
hours,
contributed
how,
through
which
we
will
calculate
the
labor
hours,
worked
and
then
assigned
a
dollar.
Very,
maybe.
E
B
B
B
E
E
B
So
internal
contributor
is
what
our
organization.
B
B
Can
you
hear
me
now
yeah,
okay,
so
I'm
saying
initially
it
was
like
who
is
contributing.
A
B
E
B
B
B
B
E
Seen
in
other
projects.
B
E
A
A
A
B
Issue
tags
is
like
same
how
many
issues
that
we
have
submitted
are
tagged
to
our
organization
or.
B
Yep
yep,
it
was
more
from
revising
from
the
labor
our
investment.
D
D
One
service
based
now
yeah,
I'm
thinking
of
like
like
code
like
code,
quality
scanners,
or
something
like
that
that
all
right
I
need
to
do
some
research
hold
on.
E
A
A
A
E
Just
put
in
chat
one-
maybe
I
should
put
it
in
the
document,
but
one
way
I
found
to
to
estimate
it.
If
you
look
in
this
source
file,
I
think
that's
the
the
index.js,
that's
the
clearest
at
the
top.
It
has
some
estimation,
so
it
takes
the
history
of
the
kit
repo
and
takes
the
timestamps,
and
it
makes
some
assumptions
like
you
start
your
day
and
then
you
have
initial
delay
and
then
that's
the
taste
of
the
commit
yeah.
E
E
A
E
E
E
A
E
B
A
E
All
right,
I.