►
From YouTube: CHAOSS.Value.WG.Oct.8.2020
Description
CHAOSS.Value.WG.Oct.8.2020
A
Yeah
welcome
to
the
value
working
group
on
whatever
day
it
is
and
whatever
year
it
is.
Oh
october,
8th
2020.,
we
are
jumping
in
we've,
got
pretty
common
crew
here.
So
there's
no
need
for
introductions
want
to
see
what
are
on
people's
minds
when
it
comes
to
agenda
items.
Otherwise
we
can
get
to
the
recurring
ones
that
were
coming
up
the
last
couple
weeks
or
last
couple
meetings.
A
I
think
the
the
biggest
one
being
on
my
end
that
I
think
I
worked
through
first
draft
of
project
popularity
that
I'd
love
to
get
some
eyes
on
and
discussion
around
and
then
there's
the
alternate.
A
The
dev
focus
popularity
as
opposed
to
the
reputation
based
popularity
that
is
still
outstanding,
but
we
can
dig
into
that
so
matt
added
a
couple
items.
Anyone
else
have
things
on
their
mind:
they
want
to
bring
up
or
follow
up
on.
D
B
A
A
Okay,
okay,
great
scm
or
anything
else
on
zoom
people
have
questions
on
good
to
go
all
right,
so
fcms
discussion
yeah.
I
just
finished
watching
last
week's
conversation.
If
people
are
out
of
the
loop
on
that,
it
was
very
revealing
about
the
the
conver
conversation
about
sms
so
what's
evolved.
Since
then,.
B
I
don't
know
which
there
were
a
couple
videos
one.
I
think
the
biggest
thing
is
we
have
to
change
the
name.
B
Just
we
got
legal
advice
to
from
the
lf
that,
if,
if
they
are
hoping
to
use
scms
as
a
name
for
their
business,
the
trademark-
and
they
want
to
trademark
that
name
trademark-
can
just
get
real
thorny,
because
if
you
can't
prove
the
origin
of
a
name,
you
actually
can't
get
trademark
or
you
can
lose
trademark
right,
and
so,
if,
if
they
want
to
use
the
name-
and
we
have
it
in
the
chaos
project,
it
just
doesn't
it
doesn't
line
up.
B
We
can't
do
that,
and
so,
and
I
do
think
benia
and
dylan
had
had
at
least
mentioned.
The
trademark
was
something
that
they
were
maybe
pursuing
or
was
maybe
on
their
mind
like
down
the
road.
So
the
recommendation
was
just
to
change
the
name
in
the
chaos
project,
and
I
think
we
had
come
up
with
a
name
that
was
social
listening.
A
That
sounds
heavenly
on
my
ears
honestly,
because,
like
it's
just,
I
know
exactly
what
you're
talking
about
when
you
say
social
listening
and
it's
nice
generic,
so
we
won't
run
into
yeah.
So
that
is
my
overwhelming
plus
one.
B
Okay
right
on
so
I
can,
I
can
make
those
changes.
I
think
at
this
point
it's
been
pretty
much
talked
about
enough,
and
so
I.
A
Shouldn't
be
too
hard,
yeah
that'll
be
it'll,
be
really
fun
to
share,
like,
I
think
pretty
much.
Every
it's
a
bit
of
an
aside,
but
every
every
devrel
team
or
kind
of
community
builder
I
hang
out
with
on
the
internet,
is,
is
trying
to
figure
out
how
to
measure
their
community
and
I've
wanted
to
point
them
towards
scms
for
a
while.
A
A
I
think
this
could
be
like
rolled
out
to
a
lot
of
teams,
so
it's
very
encouraging
anyway,
if
you
need
a
if
you
need
a
review
on
a
pr
or
anything
just
tag
me
on
github
awesome,
not
during
your
week
off,
though
god,
no
I'm
gonna
as
much
as
I
do,
love
github
activities,
the
the
new
interface
does
make
it
seem
like
yet
another
inbox.
I
have
to
manage,
so
I
will
be
turning
that
off.
Yeah.
A
D
Wow
yep,
I
see
how
I
reverse.
D
A
C
Before
before
we
move
on
on
the
social
listening
metric,
we
have
discussed
at
some
point
of
breaking
out
into
individual
metrics
and
all
that
yeah.
We
were
discussing
that.
Maybe
that's
a
lot
of
work
and
yeah.
Our
time
is
better
spent
elsewhere,
because
we
have
the
social
listening,
metric
defined
sure
it's
maybe
a
little
much
in
one
metric,
but
it's
enough
to
get
people's
ideas
going.
Yeah
yeah
and
I
think
we
achieved
that
without
doing
much
more
work
on
it.
For
now,
we
can
focus
on
other
things.
C
E
D
D
B
I
don't
think
so
if
to
elizabeth's
point,
if
somebody
would
like
to
do
that,
I
think
value
this
working
group
would
be
a
good
place
to
do
that,
but
keeping
meetings
off
the
calendar
is
cool
by
me.
Yeah.
D
D
I
mean
there
were
some
useful
metrics.
I
thought
that
emerged
from
it,
but
it
sounds
like
I
guess
I
don't
I'm
a
little
confused
about
where
that's
going
then
or
not.
D
B
Yes,
so
unless
we
want
people
to
so
we
had
a
couple
options
here,
so
one
is
to
break
it
out
fully
into
the
10
metrics
that
you
identified
and
build
those
metrics
out,
but
we
don't
seem
to
have
a
champion
to
do
that
and
the
amount
of
effort
to
do
that
is
pretty
high.
So
I
mean
if,
if
you
are
offering
to
to
do
that,
then
that's
cool.
B
The
other
option
was
to
have
scms
become
a
program.
You
know
like
dna
badging,
but
again
we
really
didn't
have
the
capacity
to
the
bandwidth
to
shepherd
that
as
a
like,
a
service
that
we
offered
in
the
chaos
project.
So
that
was
also
a
challenge,
so
we're
trying
to
balance
what
is
the
most
sensible
way
to
still
capture
this
information
and
make
it
available.
A
To
people
totally
get
it,
so
is
this
still
related
to
the
comments
sean
you
you
have
from
issue
75
and
just
pop
that
in
and
I'll
add
that
to
the.
D
A
A
A
moment
to
review
that
and
see
if
that's
captured
the
the
next
steps
that
are
on
your
mind
or
we're
kind
of
you
know
a
bit
of
a
gap
between
our
open
issues.
D
A
Totally
you
did
so
that
pull
request
is
built
into
the
metric.
A
Com
yeah
the
release
metric
under
communal,
so
okay
focus
area,
communal
value,
scms,
okay,
but,
like
I,
I
think,
we've
kind
of
I
personally
have
lost
the
thread
on
the
discrete
you
know
what
we
were
calling
atomic
metrics
that
you
pointed
out
yep.
I
know
I
know
them
because
I
spent
you
know
an
afternoon.
A
A
D
A
A
Right,
yeah
yeah,
so
I'm
I'm
around
next
week,
I'm
out
the
week
after,
oh
okay,
so
yeah
I'll
miss
this
meeting
in
two
weeks:
okay,
all
right
yeah!
So
let
me
read
it
over.
Let
me
put
it
on
my
trello
board.
Yeah
take
a
moment
to
metric
again,
so
look
through
it.
If
75
isn't
the
right
place
to
follow
up
on
it.
Let's,
let's
open
a
new
issue
to
do
so
and
I'll.
I
would
team
up
with
you
to
go
through
that
at
least
totally
that
was
totally.
D
B
Could
I
make
one
suggestion
on
the
work?
Maybe
when
you're
going
through
those?
Is
it
five
to
ten
atomic
metrics?
I
think
I
had
eleven
when
I
was
also
eleven.
Okay,
maybe
try
to
place
them
in
the
spreadsheet
as
well.
I
mean
we
could
start
kind
of
capturing
them
in
the
spreadsheet
under
a
focus
area,
and
the
remark
could
be.
This
is
pulled
out
from
the
social
listening
method.
I
think
if
we
just
go
that
far
right
now,
that.
A
Okay,
all
right
great
question
your
gun
following
up
there.
Thank
you
anything
else
on.
A
Okay,
so
from
the
question
of
popularity,
we
had
the
initial
conversation
that
separated
out
this
idea
of,
like
the
reputation
of
the
project
versus
the
market
share
of
the
project.
B
A
D
B
A
A
D
D
He's
really
andy
sandberg,
and
this
is
he's
doing.
A
Such
a
funny
that's
a
great
thread.
I
can
definitely
think
of
worse
comparisons.
So,
anyway,
speaking
of
comparisons,
let's
talk
about
popularity
that
was
a
weak
transition,
we'll
take
it.
We
yeah.
We
basically
got
to
the
point
of
saying:
there
are
two
discrete
methods
to
discussing
popularity.
A
One
has
to
do
more
with
usage
adoption
development
type
popularity
that
there's
some
comments
on
in
progress
here
and
some
updates
from
sean,
but
I
don't
know
exactly
where
we
left
off
there.
What
I
wanted
to
draw
your
attention
to
the
project
popularity
reputation.
A
I
think
I
got
this
down
to
something
where
I'm
ready
for
this
group
of
people
to
kind
of
do
the
really
detailed
review
of
it
to
see
if
it's
ready
to
open
into
a
pr
most
notably,
I
would
really
like
some
other
visualizations.
I
grabbed
this
one
from
devstats
from
the
kubernetes.
D
D
D
A
Yeah
yeah
so.
A
Very
distinct,
without
a
doubt,
I'm
just
playing
so
tools.
I
listed
territory,
agar
devstats.
I
guess
I'm
sure
there
are
more,
but
those
are
the
ones
that
come
to
mind.
That
matter
to
me,
and
I
have
a
little
bit
of
a
description
of
data
collection
strategies,
I
I
will
need
somebody
else's
opinion
on
whether
that's
helpful
or
insufficient,
but
is
is
that
a
draft
document
is
that
link
in
the
media
minutes
or
in
the
yes
yeah
I'll
stop
sharing,
and
it
should
be
linked
to
you
when
you
see.
A
A
A
A
A
I
wrote
it
with
the
intention
of
framing
it
toward
the
scenario
when
you're
in
a
business
context
and
you're,
making
the
decision
on
whether
to
use
one
project
or
another
the
I.
I
really
had
this
like
idea
of
implicit
bias
in
my
head,
as
I
was
writing
it
of
like
when
people
don't
have
clear
about
like
understanding
of
the
value
they
need
to
derive
from
something
we
kind
of
default
to
this
lens
of
popularity,
without
discussing
it
openly
and
that's
why
I'm
so
fascinated
by
it.
A
So
that's
the
story.
I
was
telling
myself
but
your
story,
elizabeth
of,
like
I'm
an
individual,
do
I
want
to
contribute
to
this
version
of
a
container
runtime
or
that
version
of
a
container
in
time,
because
there's
more
popularity
over
here,
that's
it's
the
same
assessment
but
different
context.
E
And
also
like
matt,
said,
matt
g
said
job
opportunities.
So
if
I
have
to
learn
a
framework
which
one
am
I
going
to
learn,
you
know
for
the
most
opportunities.
Oh
maybe
I'll,
learn
the
one
that
has
the
most
stars
and
seems
to
be
the
most
popular.
Because
then
I
know
that
that's
a
more
valuable
skill
to
know
this
framework
and
be
familiar
with
it
and
maybe
even
contribute
to
it
than
something
else
that
nobody's
ever
heard
of
that
doesn't
have
any
stars.
A
Yeah,
so
this
this
reminds
me
of
a
challenge
that
I
see
as
times
of
like
I
guess
in
the
description
we
could
maybe
talk
about
the
interconnectedness
to
other
metrics
or,
like
I
think
you
know
this
probably
isn't
the
right
venue
to
do
so.
But
I
I
have
been
wondering
if
there's
a
pitch
for
like
in
the
default
template.
A
There
is
an
interdependent
or
interdependency
type
section
to
a
metric
of
like
this
also
relates
to
how
we
think
about
x
and
also
could
depend
on
y,
and
we
start
linking
across
working
groups
or
within
working
groups.
If
the
context
calls
for
it.
B
So
I
think
that's
a
good
idea
to
date.
We
just
kind
of
had
it
those
relationships
built
as
links
in
the
text.
You
know
so,
if
you're
referring
to
something
we
would
just
say
so,
for
example,
the
metric
that
is
called
change,
requests
which
are
basically
like
pull
requests.
B
We
have
a
a
metric
called
change
requests
and
then
we
have
a
series
of
companion
metrics,
like
you
know,
number
of
open
change,
requests,
number
of
closed
change
requests,
and
so
in
that
case
the
latter
two
would
reference
the
first
one
because
we're
yeah,
but
having
an
explicit
section
of
like
what
other
metrics.
Are
you
talking
about
or
you're
pulling
from?
That's
a
nice
idea.
D
A
Could
be
fun
yeah?
It's
definitely
come
to
my
mind
a
few
times
I'm
happy
to
open,
maybe
in
the
in
our
chaos
metrics
or
I
can
just
put
a
placeholder
issue
in
there
to
further
discuss
that
yeah
cool
and
this
one
elizabeth.
I
really
like
your
point.
I
I
added
in
the
in
our
document
to
links
it's
to
the
individual
value,
job
opportunities
and
individual
and
individual
value,
organizational
projects,
skill
demand,
if
you
take
a
peek
at
those
and
if
you
think
they
fit
into
what
you
were
saying
like.
A
D
A
Fine
yeah,
I
I
have
been
interested
in
in
getting
that
one
further
too.
I
know
dwayne
tentatively
offered
to
follow
up
on
it,
but
we
haven't
reconnected
so
you're
already.
A
D
A
Oh
and
yeah,
oh
there,
there
is
no
predefined
context.
I
I
added
a
context
to
project
popularity
reputation
because
it
was
just
the
lens
I
was
thinking
through.
I
don't
think
there
was.
We
didn't
agree
to
one
ahead
of
time
when
it
came
to
project
popularity,
development
and
usage.
Well,
that's
what
I
added
in
what
you're
saying
so
it.
A
Yeah,
I
I
guess,
because
I
I
think.
A
A
D
A
D
A
Kevin
added
this
when
we
had
the
initial
discussion
of
engagement,
how
conversations
take
place
around
issues
and
pull
requests
clones?
How
many
followers
do
people
can
yeah?
Oh,
how
many
followers
do
the
people
contributing
to
pull
requests
and
issues
have,
but
that's
relevant
in
both
contacts?
D
D
C
So
one
one
thing
we
have
done
with
other
metrics
is
to
say:
hey.
We
are
looking
at
this
idea
of
looking
at
the
project
like
in
this
case,
project
popularity
and
then,
if
we
have
different
lenses
in
the
objectives
we
can
have,
we
sometimes
have
like
bullet
lists.
Of
these
are
the
different
things
we
can
use
this
metric
for
and
then
in
the
data
collection.
If
that's
the
same,
then
it
makes
sense
to
have
those
lenses
just
be
listed
in
the
objectives.
A
Yeah,
that's
great
so
reviewing
the
meta
above
the
notes
at
the
beginning.
It
really
hinges
on.
There
is
a
conversation
around
is
popularity
about
reputation
or
is
popularity
about
market
share.
I
think
that's
the
most
concise
way
of
saying
it
like
who's
actually
used
more.
Is
you
don't
measure
github
stars
to
find
out
who's
used
more
you
measure,
you
know,
I
guess
downloads,
but
that's
yeah
you're,
trying
to
I
guess,
you're.
What
you're
attempting
to
calculate
with
your
measurement
is
different.
D
I
I
think,
you're
getting
it
yeah
at
the
very
beginning
of
a
project.
It's
all.
I
think
reputation,
because
there
is
no
market
share,
like
the
reputation
of
the
people
or
the
project
or
the
organization
would
lead
me
to
get
involved
in
something
very
early
and
then
farther
down
the
line
and
really,
as
an
open
source
contributor.
D
That
would
be
I'd,
be
looking
for
reputation
to
decide
where
I
would
make
a
contribution
or
invest
my
time
as
a
sort
of
freelance
open
source
contributor
setting
aside
my
own
interests
or
her
needs.
D
That's
that's
how
I
might
make
a
decision,
but
if
I'm
approaching
it
from
a
corporate
perspective,
then
popularity
is
related
to
my
ability
to
get
a
job
somewhere
else.
If
I
don't
like
where
I
work,
and
so
then
you're
getting
into
the
market
share
things
like
what
are
the
people
at
the
devops
meetings
or
the
the
local
meetups
really
talking
about
that's
when
I
was
a
developer,
that's
the
lens
that
I
saw
the
choices
about
what
technologies
to
pursue.
That's
how
I,
how
many
decisions
in
my
own
head
was?
D
A
A
Yeah,
it's
you're
right,
it's
pre
pre-market
share
more
just
like
the
doesn't
have
the
energy
like.
We
have
all
these
weird
metaphors
to
apply
to
it
as
opposed
to
mind,
share
yeah,
exactly
all
the
words
are
listed
out
at
the
beginning
of
that
bottom.
One
mind:
share
influence,
interest,
excitement,
momentum,
so
so
sean
are
you
saying
like
there?
D
D
You
may
be
able
to
take
that
from
a
developer
perspective
as
well.
I
mean
it
kind
of
depends
on
your
profile,
so
I
think
it's
this
phases
of
a
project
life
cycle
like
at
the
very
beginning.
The
reputation
of
the
people
involved
in
the
project
is
how
you
decide
whether
or
not
to
invest
early,
but
so
I
don't
if
they
are
different.
I
think
I
I
think
I
think
there's
different.
D
I
mean
I
wouldn't
so
I
wouldn't
measure
if
I'm
thinking
about
it
from
a
reputation
perspective,
I'm
interested
in
the
followers
of
the
individuals
involved
in
it
a
lot
more
than
I
am
in
pull
requests,
forks,
repo
stars
or
issues.
I
might
be
interested
in
blog
posts
and-
and
I
think
the
the
followers
of
the
individual
like
at
the
reputation
level,
I'm
interested
in
how
many
followers
the
individual
developers
involved
in
this
project
have
totally.
That
is
more.
What
reputation
is.
E
E
I
think
there
is
a
connection
or
some
I
don't
know
how
we
want
to
explicitly
call
that
out,
but
things
like
trust
and
utility,
and
you
know
the
other
three
that
I
can't
remember
right
now,
but
there
is
some.
I
think
reputation
does
touch
on
some
of
those
issues.
E
A
E
D
I
think
I
think
it's
the
it
is
the
followers
stuff
I'm
pretty
good
comment.
Then
I
actually
did
a
paper
about
this,
but
open
source
developers
absolutely
follow
individual
developers
with
a
lot
of
followers
from
project
to
project
yeah,
and
so,
if
you're
talking
about
reputation,
I
think
it
it's
the
organizations
that
are
involved
and
the
individuals
that
are
involved
that
that
so
that's
it's.
The
stars,
maybe
are
the
forks
on
existing
projects
inside
that
github,
org
or
gitlab.org,
and
it's
the
followers
that
the
individual
developers
have
like.
D
A
A
D
D
D
A
D
D
A
leading
indication,
reputation
is
a
leading
indicator.
Development
and
usage
is
a
a
legging
or
a
parallel
indicator.
Probably
lagging
would
be
a
good
way
to
draw
a.
E
Do
we
care
about
people
who
are
giving
talks
at
large
conferences
or
popular
conferences
like
does
that
fit
in
here
somewhere?
I
feel
like.
D
D
A
D
A
And
tally:
it's
not
graceful
but
you're.
I
totally
did
that
when
I
was
looking
for
who's
influential
in
like
the
go
programming
language
in
2015.
A
Totally
yeah
absolutely
yeah.
I
didn't
learn
it
well
enough
to
do
it
as
a
like
to
be
good
at
it,
but
yeah.
I
was
trying
to
pay
attention
yeah,
okay,
so
I
we're
coming
up
on
time,
so
I
don't
know
I
I
don't
feel
like.
I
have
like
a
a
very
clear
conclusion
on
what
to
do.
I
think
we
should
probably
I'm
gonna,
keep
thinking
about
it
and
see
if
these
do
separate
into
these
leading
and
lagging
indicators.
C
A
Yeah
no,
but
your
edits
are
appreciated.
Yeah,
I
think
where
sean
was
going
and
and
elizabeth
got
us
started
down
that
path
of
it
will
make
the
whole
thing
make
more
sense
and
kind
of
reminds
us
that
there
could
be
two
separate
concepts
happening
at
once
here.
A
B
A
A
D
A
A
I
don't
have
an
opinion
on
that,
yet
if
people
come
up
with
one
I'm
just
going
to
update
some
of
the
notes
in
the
open
issue
for
popularity,
I
welcome
dialogue
and
github
issues
or
violent
the
mailing
list.
Let's
be
respectful
of
people's
calendars.
I
think
I
need
to
put
put
a
pin
in
the
conversation
for
today
sound
good.
Thank
you.
Thank
you
man
for
me,
yeah.
I
made
some.