►
From YouTube: CHAOSS Value Working Group September 8, 2022
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
A
C
C
A
C
A
Yeah
this
reminds
me
of
sometimes
when
we
have
the
community
called
centuries.
They
were
number
three
and
then
we
find
ourselves
only
two
of
us
in
the
room
and
instead
of
focusing
on
maybe
what
the
call
is
about
we're
just
going
through
very
many
other
topics
that
are
really
not
related
to
the
call
and
yeah.
C
A
B
A
I
really
only
thought
it
happened
for
the
community
cause,
since
it's
like
a
general
thing
where,
like
nobody,
is
responsible
or
tagged
to
something
but
then
looks
like
even
for
these
other
calls.
It
happens,
and
I
think
elizabeth
has
a
test
of
that
since
she
happens
to
be
in
almost
all
the
other
calls.
A
C
B
I
have
copied
from
previous
meetings
agenda.
It
has
a
lot
of
things,
so
this
needs
to
be.
I
don't
think
tony.
A
B
A
C
Parties
to
be
involved
in
the
meeting
like
tony,
for
instance,
and
others
yeah.
A
B
I've
kept
this
help.md
because
it
was
tony's
idea,
so
maybe
we
need
to
get
his
feedback
if
he
joins.
C
And
I
think
that
that
topic
is
still
really
ambiguous
and
fuzzy
for
me
as
well.
So
I
would
really
like
so
enoch
just
as
a
little
context.
C
There
was
an
idea
brought
up
as
part
of
one
of
the
metrics
that
we
were
working
on
to
have
projects
fill
out,
what
we
were
just
calling
help
dot
md,
which
would
be
like
a
list
of
or
areas
where
a
project
could
use
help.
So
if
someone
wanted
to
join
the
community,
they
could
easily
see
you
know
all
in
one
document
where
else
where
the
project
could
use
help.
C
Around
that
and
it
started
because
a
gentleman
named
tony
had
joined,
who
was
wanting
to
know
as
a
company
where
they
could
provide
value
to
a
project
which
is
the
tie-in
to
the
value
working
group.
Here,
that's
how
it
started
so
he
was
like.
Oh,
it
would
be
great
if
all
this
was
in
just
a
document.
Instead
of
you
know
just
random
issues
that
were
open,
you
know
so
that
they
could
say.
A
Yeah,
I
think
also
maybe
if
yours
here
would
have
context,
but
then
I'm
that
now
you
know
one
thing
that
you
fear
building
is
trying
to
duplicate
a
process
or
trying
to
duplicate
a
standard
that
is
already
known
to
the
larger
community.
Because
then,
when
someone
comes
to
your
to
your
kind
of
setting
or
environment,
the
standards
they
expect,
like
are
international
standards,
I
should
say
imports
so
putting
a
help.md.
A
Yet
if
I'm
contributing,
unless
the
project
is
really
maybe
not
on
github,
but
of
course
I
expect
to
find
information
like
contributing.contributing.md.
A
Or
maybe,
if
I'm
looking
to
contribute
directly,
I
go
to
the
issues
and
check
on
the
issues
that
are
explained
so
unless
there
is
really
specific
information
that
needs
attention,
I
look
at
it
as
duplicating
the
wheel,
because
already
there
are
standards
of
where
what
to
check
where
to
check.
In
case
you
need
to
contribute
to
a
project.
A
So
I
think
that
that
that
would
depend
on
what
time
project
and
where
it
is,
but
already
like
there
already
some
industrial
standards
for
where
to
find
what
you
need
to
contribute,
depending
on
where
it's,
where
you
found
it.
A
So,
but
if
it's
already,
if
it
had
already
taken
the
direction
of
a
metric,
then
I
think
there
was
more
information
that
are
visible
to
make
such
a
conclusion.
B
I
don't
think
it
has
taken
as
a
form
of
patrick.
It
was
more
like
an
idea
to
have
some
place
on
the
repos
on
the
github
or
place.
C
B
C
Yeah,
it
didn't
get
anywhere
near
a
metric
development
level
at
all
like
we
don't
have
a
template
for
it
or
anything.
I
mean
we
had
just
kind
of
been
chatting
about
the
idea
and
how
that
would
fit
in
it.
C
It
came
up
also
as
part
of
a
discussion
about
a
metrics
model
called
business
readiness,
I
think,
was
the
original,
and
that
was
the
issue
that
you
had
opened
vanad
way
back
when
and
you
remember
this
matrix
model
right
and
so
we've
talked
about
it
in
a
few
different
places,
so
that
was
kind
of
like
I
don't.
I
don't
really
know
if
if
tony
was
thinking,
maybe
we
we
would
just
check
for
that
file
as
part
of
a
metric,
I'm
not
entirely
sure
how
it
links
back
to
metric
development.
A
Okay,
yeah
go
ahead.
Now
I
was.
I
was
saying
that
if
his
submission
was
in
a
way
of
getting
a
one
central
place
where
someone
could
come
and
know
that
okay,
you
can
actually
contribute
to
this,
or
you
can
actually
help
with
this.
Then
my
question
would
be
what's
the
use
of
a
readme.
What's
the
use
of
contribute
to
solution?
A
What's
the
use
of
the
issue
section
on
every
repository
and
what's
the
use
of
maybe
having
a
documentation
of
that
project
because
at
least
on
an
industrial
standard,
those
are
the
four
places.
Anybody
who
would
be
contributing
to
an
open
source
project
would
fast
into
entire
industries
before
they
are
like.
Okay,
I
don't
see
how
this
is
making
sense
to
me,
so
I
need
to
check
somewhere
else.
B
Yeah,
I
agree
with
you,
but
like
the
idea
was
to
have
an
especially
focused
highlighting
area
where
we,
where
a
project
tells
what
help
they
need
they
are
looking
for
and
like
a
readme
is
generally
about.
Okay.
What
our
project
is
about
and
like
yeah
good
first
issue
is
the
place
that
tells
okay.
B
We
are
looking
for
help
in
this
area,
but,
like
specifically,
project
is
looking
for
financial
help
or
some
other
help.
They
can
highlight
those
ideas.
I
think
the
idea
is
good,
but
I
don't
know
how
it
aligns
in
with
other
documents,
I'm
not
sure
that
needs
to
be
discussed
or
sorted
out,
but
I
really
like
this
idea
of
like
okay
as
a
project.
We
need
help
in
these
areas.
These
needs
to
be
highlighted
so.
A
Okay,
I
think
maybe
it
would
be
good
if
we
get
context
from
whoever
came
up
with
that.
Okay,
so
that
you
could
hear
his
originality
into
what
all
this,
because
now
also
when
you
talk
about
things
concerning
help,
I'm
also
not
even
starting
to
think
I'm
github
already
has
I'm
like
a
button
that
has
a
donation,
I'm
link.
If
you
want
to
support
your
project
or
you
want,
I
mean
like
for
every
help
that
I
see
you're.
A
C
There
was
also
confusion
around
naming.
It
help
dot
md
because
it
like
some
people
that
had
joined
this
conversation
were
like
well,
I
that
to
me
says:
that's
where
I,
as
a
user,
go
to
get
help
with
my
pr
with
this
project,
like
you
know,
on
the
flip
side.
So
if
there's
there's
a
lot
to
sort
out,
if
we
are
going
to
do
anything
with
this,
which
I
don't
know
that
we
will
but
yeah
there's
a
lot
of
a
lot
of
gray
area
to
define.
A
I
think
we
can
push
it
to
all
try
to
to
to
to
to
challenge
that.
It's
like
the
originator
of
this
idea
can
be
reachable
so
that
we
know
how
to
chat
about
it
and
see
whether
actually
we
aren't
duplicating
anything
or
actually.
Maybe
there
is
something
that
we
need
to
put
somewhere
that
we're
missing,
or
this
is
really
something
it
needs
to
start
on
its
own.
B
So
what
should
be
the
plan?
Do
you
want
to
work
on
the
model,
or
should
we
call
it
a
day.
C
B
A
I
think
it
doesn't
hurt
to
political
an
evening
to
me
and
also
morning
to
you.
B
A
A
A
B
D
D
B
Do
that
yeah
that
then
that's
good?
Let's,
so
I
have
two
things
on
the
agenda
that
I
wanted
a
feedback,
so
maybe
we
can
get
your
yeah
one
is
metric
model.
Let
me
share
the
link
for
you.
Do
you
have
meeting
minutes.
A
B
A
That,
oh.
D
D
B
So
let
me
anyhow
share
this,
so
here.
B
So
one
thought
I
had
like
before
diving
deep
into
this
model
seems
to
be
a
mega
model
which
even
we
discussed
in
the
last
meeting
like
we
want
to
assess
whether
open
source
project
is
ready
for
being
adopted
or
in
a
continuity
so
and,
and
especially
the
metrics.
I
I
see
that
fits
in
this
model
are
so
many
that
I
I'm
thinking
should
we
continue
with
it,
or
that
is
like
my
key
question
so
so,
but
looking
at
the
metric
that
we
want
to
adopt,
we
look
at
the
documentation.
B
B
B
Yeah
because,
like
I,
have
reworked
on
this
entire
metric,
but
when
I
was
reviewing
it,
I
feel
like
okay,
this
fits
because
I
want
to
see
whether
the
documentation
is
there,
because
I'm
adopting
this
project
for
my
organization
will
I
be
able
to
see
the
documentation
the
help
I
need
from
the
documentation,
so
then
code
quality.
I
want
to
assess
the
quality.
I
want
to
assess
the
licensing,
whether
it'll
conflict
with
my
internal
licensing
policies
or
things
like
these,
and
I
want
to
assess
the
riskiness
of
that
project,
whether
it
will
survive
continue.
B
B
C
Yeah,
I
think
if
we
were
to
follow
the
pattern
of
previous
metrics
models,
we've
been
trying
to
keep
them
to
maybe
like
four,
so
it
you
would
for
five.
Maybe
so
you
could
have
like
one
metric
per
sections
like
one
documentation,
one
code
quality
one
license,
but
but
that's
not
it's
not
really
complete
because,
like.
D
I
mean
I'm,
not
I'm
not,
I'm
not
convinced
I
mean
I
don't
I
like,
I'm,
not
I'm
not
a
so
I
mean
a
couple
of
like
initial
sort
of
like
reactions.
One
is
like
I
didn't
actually
understand
what,
like
I
didn't
understand,
what
readiness
meant-
and
I
think
part
of
that
is
part
of
that
is
just
I
don't
know.
I
I
don't
know
enough.
D
I
don't
hang
out
enough
with
people
that
are
talking
and
thinking
in
this
way,
but
I
think
that
that,
but
I
think
also
readiness
is
like
it's
a
little
like
conceptually
like
a
little
like
conceptually
overloaded
in
the
sense
like
ready
for
what
right,
like
ready
to
be
adopted
as
a
dependency
ready
to
be
sort
of
like
used
as
a
relatively
like
sort
of
like
interchangeable
part
of
a
thing
right,
and
I
I
think
that
in
some
sense
this
actually
points
to
a
like,
like
a
like,
a
like
a
conceptual
like
ambiguity,
that's
related
to
the
fact
that
this
is
super
big.
D
Is
that
actually,
like
there's
a
range
of
things
that
one
could
be
ready
for
and
the
kinds
of,
and
that
a
lot
of
details
will
matter
a
lot?
So
I'm
just
not
convinced
that,
like
so,
for
example,
like
license
policy
right,
like
let's
see
so,
you
have
license
coverage
license
deploy.
I
guess
those
are.
Generally
speaking.
D
Those
are
generally
speaking,
things
that
you're
gonna
want,
but
like
a
lot
of
decisions
about
sort
of
like
like
the
specific
license,
is
going
to
make
it
more
or
less
like
appropriate
to
be
adopted,
in
particular
business
context,
depending
on
the
existing
sort
of,
like
you
know,
like
ways
in
which
there
exist,
you
know
like
sort
of
commercializing
like
the
the
product.
Right
like
some
licenses
would
be
great.
Some
licenses
would
not
be
great,
and
it's
just
not
like.
D
Yeah
I
mean,
I
think
that,
like
you,
do
want
to
avoid
something
which
is
like
a
like,
like
I'm,
a
little
afraid
that
business
readiness,
like
is
kind
of
just
like
standing
in,
for
like
kind
of
like
goodness,
and
I
don't
think
that
that
I
mean
yeah,
I'm
just
skeptical-
that
that
can
work
it's
just
it's
just
too
much
like
wouldn't.
Would
you
be
better
off
with
like
four
like
metrics
models,
each
of
which
tell
you
something
about
the
individual
things
and
allow
you
to
sort
of
like,
like
imagine
like?
D
D
So
I
think
that
if,
if
the
decision
is
to
keep
moving
forward
with
it,
I'd
want
to
be,
I
want
to
see
a
little
more
specificity
in
terms
of
like
what
ready
for
what,
because
I
think
that
the
kinds
of
things
that
I
would
expect
or
the
ways
in
which
I
would
evaluate
a
particular
piece
of
software-
will
be
different
if
I'm
going
to
be
depending
on
it.
D
If
I'm
going
to
be
like
contributing
to
it
or
adopting
it
as
a
sort
of
core
part
of
my
business
in
a
way,
that
would
then
mean
that
I
were
like
sort
of
participants
within
the
project
and
I
would
care
about
a
range
of
other
kinds
of
things
in
that
context.
If
it's
just
a
dependency,
I
probably
don't
care
about
questions
like
sort
of
governance
right
like
metrics.
That
would
be
connected
to
governance,
but
if
I'm,
but
if
I'm
gonna
be
participating
in
it,
then
I
might
matter
about
that.
D
Might
matter
a
lot
right
if
this
is
just
like
controlled
by
a
single
organization.
Right,
like
these
sorts
of
things,
so.
B
C
You
know
accessibility,
because
it's
like
required
or
to
get
that
metric.
It's
the
project
has
to
you
know,
do
a
survey
or
whatever,
if
I'm
making
sense
so.
B
I
think
that
is
very
much
clearly
written
in
this.
Even
the
story.
It's
from
organization
perspective
that
as
an
organization
I'm
looking
at
an
open
source
project,
and
I
want
to
assess
whether
I
should
adopt
this
project
or
use
it
in
my
business
context
or
not,
and
what
are
the
metrics
that
will
help
me
to
make
this
decision.
C
C
So
how
am
I
supposed
to
have
insight
into
that?
If
that's
just
something
the
project
decided
to
do
from
there?
You
know
what
I'm
saying
like
they
would
keep
that
maybe
internally
or
maybe
not
have
posted
those
results.
So
is
that,
okay,
that
I
won't
have
access
to
any
of
this
data,
or
is
that
am
I
only
gonna.
B
B
B
D
D
B
Yes,
so
addressing
to
that
question
what
I
did
how
I
picked
the
metric,
I
went
through
the
entire
list.
Okay
is
clones
important
for
me
as
an
organization
I
was
not
sure
so
I
hadn't
picked
it
language.
Yes,
I
missed
it
out.
It
is
important
for
me
as
an
organization,
so
this
is
how
I
picked.
I
went
through
all
these
metrics,
okay,
which
one
are
these
important
for
me
to
decide
to
adopt
an
open
source
project.
B
C
One
other
point
of
note
kevin
and
I
did
some
research
around
why
people
join
and
leave
open
source
communities
and
one
of
the
questions
that
we
asked
was
what
what
characteristics
do
you
look
for
when,
when
joining
or
using
a
project,
and
so
I
can
dig
those
up,
because
there
were
a
few
things
that
did
surface
from
that
that
were
pretty
common,
so
that
might
help
us
narrow
this
down
a
little
bit.
If
that
would
be
helpful.
B
C
Yeah,
I
do
I
I
do
remember
license
was
a
huge
thing.
D
I
think
that,
like
to
the
extent
that,
like
I
mean,
I
think
that
we
should
be
a
little,
I
mean
I
guess
that,
like
I
would,
at
the
very
least,
want
to
be
a
little
bit
more
specific
about
what
constitutes
like
adoption
like
okay.
What
does
it
mean
to
adopt
a
project
and
how
does
different
kinds
of
adoption
might
like
lead.
A
D
To
weigh
these
different
qualities
like
sort
of
differently
that
said,
like
you,
know,
having
like
a
table
of
contents
to
like
a
set
of
like
here's,
a
list
of
if
you've
included
half
of
the
metrics
in
this
in
this
model-
and
this
is
essentially
just
like
a
sort
of
a
selected
table
of
contents
onto
the
existing
list
of
metrics.
That
say
these
are
the
kinds
of
things
that
you
might
want
to
pay
particular
attention
to
when
deciding
to
adopt
a
project
where
adoption
means
one
of
these
three
things.
B
D
B
D
But
I
do
think
that,
like
yeah,
we
might
want
to
think
about
some
more
questions
about,
like
you
might
want
to
think
about
some
more
questions
about
governance
and
leadership.
Participation
by
maybe
there
are
metrics.
I
don't
know
if
there
are
metrics
about
this
already,
but
I
think
that,
like
one
thing,
I
would
care
about
as
a
firm
who's
interested
for
certain
kinds
of
adoption
right
like
if
I'm
going
to
be
building
my
business
on
something
I
care
a
lot
about
the
like.
D
B
B
D
No,
I
was
just
thinking
of
these
of
examples
of,
like
you
know,
they're
they're,
really
high
profile.
Examples
of
you
know
very
large
companies
building
tools
on
existing
projects
where
there's
like
a
patent
thicket
or
ownership
from
some
other
company
and,
like
that's,
that's
like
a
thing
that
they,
you
really
gotta.
D
Thinking
about
adopting
a
project,
so
I
mean
that's
the
kind
of
thing
I
I
don't.
I
don't
yeah
I
was
looking.
I
don't.
I
don't
see
there
being
a
lot
of
existing
metrics.
That
would
capture
that
and
I'm
not
even
sure
where
to
start
with
that,
but
but
yeah.
I
think
I
I
agree
with
you
that
that
something
more
in
that
space
would
be
useful.
C
I
was
just
gonna
say
I
also
do
remember
the
subject
of
dei
coming
up
quite
a
bit
so
companies
there
were
a
few
people
we
talked
to.
That
would
not
even
use
a
pr
project
if
they
looked
at
the
community
and
it
looked
like
it
was
toxic
to
them.
It
like
the
way
people
communicate
with
that
with
it
I
mean
like.
I
was
really
shocked,
but
yeah
so
usage,
even
not
just
even
like
contributing
back,
but
even
using
a
project
that
is
like,
like
blatantly
toxic.
C
I
think
companies
do
look
at
that,
so
I
don't
know
where
that
fits
in
here,
but
I
would
not
entirely
discount
the
dei
yep
lens.
D
C
Yeah
right,
that's
great.
I
was
like
because-
and
you
know
what
the
rationales
it's
open
source-
there's-
probably
an
alternative.
You
know
that
is
not
that
way
so
and
they
didn't
want
to
give
their
give
any
more
visibility
or
give
any
more.
You
know,
project
kudos
to
a
project
that
was
really
not
well
run
in
that
way,.
B
Yep,
so
maybe
then
elizabeth
you
take
out
those
notes
and
whatever
you
can
find
out
for
this
particular
model
to
think
and
yeah,
I'm
not
sure
how
much
we
need
to
expand
it
all.
B
B
B
B
Yeah,
so
organization
wanted
to
pick
any
open
source
project
and
they
want
to
see,
assess
it
either
it's
usable
for
them,
whether
it's
good
for
them
to
contribute
back,
whether
it's
good
for
them
to
adopt
it,
or
even
once
they
have
adopted
over
the
period
of
time.
They
want
to
assess
whether
it's
good
to
continue
with
it
or
think
of
other
alternatives.