►
From YouTube: CHAOSS Value Working Group 6/2/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
B
A
Got
it
yep
welcome
everyone!
Welcome
to
the
value
working
group
meeting
for
june
2nd.
Please
add
yourself
in
the
minutes
and
we
have
the
new.
We
have
to
add
a
new.
Yes,
sorry,
my
google
is
not
working
so
I'll.
A
First,
item
on
the
agenda
was
like
a
revision
of
old
matrix
and
kevin
was
supposed
to
bring
a
list.
I
don't
know,
I
don't
see
any
issues
created
in
the
value,
so
maybe
yes
not
done
at
all.
He
didn't
get
the
time
to.
A
A
Anything
on
that
old
metric,
anything
anyone
wants
to
add
or
we
can
move
to
the
another
agenda.
C
So
mine,
I
just
put
it:
I
dropped
a
thing
in
there
I'll
share
my
screen
so
basically
for
the
metrics
that
are
being
that
are
going
back
under
review.
C
All
that
we're
doing
is
when
the
review
is
done.
So
let's
say
that
sean
proposes
some
changes
to
a
metric.
I
might
yeah
we
go
ahead
and
we
make
those
changes
and
we
consider
the
revision
done
and
then
there's
another
metric.
That
goes
through
the
same
thing
and
another
one
and
another
say
we
have
six
metrics
that
are
being
revised.
C
D
Yeah
we're
just
getting
to
the
revision
process
but
elizabeth.
I
guess
okay
yeah!
Well,
okay,
so
it's
just
one
issue
for
all
the
changes,
so
we
would
put
that
issue
in
at
the
completion
of
a
set
of
changes,
not
for
each
change
right.
You
are
correct,
so
you
will
put
one
issue
in
yeah.
I
remember
that
from
dei
yesterday,
that's
a
good
x
number
of
revisions.
Yeah,
that's
a
good
direction
for
the
working
groups.
We
should
bring
that
up
in
the
weekly
meeting
elizabeth.
I
think.
C
D
You
mean
we
can't
really
update
the
handbook.
Did
you
see
my
note
in
slack?
I
don't
know
apparently
so
I
made
a
after
the
web
meeting
last
week.
I
just
went
in
and
created
read
the
docs
dot
io
version
of
our
handbook.
Oh
no,
I
didn't.
E
F
C
F
Yeah,
I
just
mentioned
an
intermediate
step
so
that
in
the
process
of
us
creating
those
docs,
we
don't
lose.
This
list.
D
I
see
okay,
so
what
I
did
with
the
community
handbook
in
its
current
form
is
I
just
published
it
to
read
the
doc
dot
io
with
a
little
jiggering,
and
I
can
make
it
a
little
bit
nicer
than
it
is,
but
it
basically
has
all
the
headings
and
I
can
share
my
screen,
but
I
just
put
the
link
in
chat
as
well.
D
All
the
headings
from
the
handbook
are
there,
and
actually,
if
you
click
on
project
name,
community
handbook
on
the
left,
you'll
see
them
in
the
drop
down.
You'll,
see
them
in
the
left,
nav
as
well.
I
just
have
to
get
that
to
pop
up,
but
it
puts
all
of
them
all
the
handbook
content
into
read
the
docs
format
where.
D
D
D
E
Well,
so
I
guess
I
guess
the
question
on
my
end
is
is,
would
we
maintain
this
as
a
second
handbook,
or
are
you
proposing
that
the
people.
A
E
The
design
work
on
the
handbook
do
this
method,
rather
than
the
the
knowledge
base
project
that
we
have.
D
This
is
like
a
a
way
of
hacking
so
that
we
can
publish
an
updated
version
of
the
handbook
as
we're
developing
the
website
content,
and
this
would
provide
the
opportunity
for
us
to
be
updating
the
content
in
the
handbook,
while
the
web
project
is
going
on,
which
means
that
the
web
project
wouldn't
be
100
percent
solely
responsible
for
updating
the
content
and
then
at
some
point
in
time
you
know
that
project
will
put
it
under.
However,
you
want
to
deploy
it.
E
D
E
By
the
way,
my
only
concern
is
that
we're
not
duplicating
work,
but
since,
since
this
is
being
pulled
from
a
repo,
I
I
think
we
can.
We
can
manage
it
so
that
we're
not
duplicating
work
if
we're
so,
the
new
documents
can
be
created
in
the
in
that
existing
handbook
and
and
moved
into
the
new
structure
of
the
community
repo.
If
that
is,
if
that's
the
plan
right,
elizabeth.
H
D
Yeah,
there's
no
intentionality
or
I
do
not
want
actually
to
read
the
docs
thing
to
be
permanent.
It's
just
a
patch
so
that
we
can
publish
changes
to
our
handbook,
update
the
content
of
our
handbook
and
I
think
that'll
ultimately
help
the
web
project,
because
you
won't
feel
responsible
for
updating
all
of
the
content.
In
the
course
of
doing
your
work.
A
So,
maybe
maybe
sorry
go
ahead.
No,
I'm
just
trying
to
understand.
Do
we
are
having
a
separate
handbook,
so
we
are
having
a
community
thing
like
I'm
confused.
How
many
things
are
we
having
we
have
this.
C
E
So,
from
a
from
like
a
work
standpoint,
I
suggest
that
we
use
that
existing
community
repo
as
the
place
to
create
new
documents.
E
The
community
handbook
repo,
so
the
the
final,
so
the
final
repo,
I
think,
as
we've
been
discussing
it
so
far,
is
going
to
be
the
community
repo.
But
right
now
I'm
proposing
since
you
have
this
set
up.
Let's
create
all
new
documents
that
need
to
be
created
in
that
community
handbook
repo
and
then
we
can
move
those
documents
as
needed
into
the
community
repo
as
we're
building
out
that
that
finalized
version
of
the
handbook.
D
E
E
Really
have
a
preference,
maybe
the
maybe
the
google
summer
of
doc's
students
do.
C
E
I
think
one
of
the
clone
one
of
the
tasks
with
the
with
the
community
repo
is
figuring
out
what
the
the
chapters
of
the
handbook
are,
if
you
will,
or
the
the
folders
and
file
structure.
E
So
the
the
existing
folder
file
structure
that
we
have
for
the
community
handbook
may
not
match
with
the
the
structure
that
that
the
students
build
for
the
the
new
handbook.
D
Well,
if
you,
if
you
pull
it
in
it's
just
another
directory
that
in
a
repo
that
already
exists
and
the
content
can
be
updated
reorganized,
and
we
can
just
continue
to
update
according
to
the
organization
until
you're,
ready
to
launch.
E
Yeah,
when
you're,
when
you're
modifying
existing
content,
you
often
make
design
decisions
based
on
that
existing
content,
because
if,
if
we
start
from
a
blank
slate,
we're
we're
asking
them
to
reimagine
what
that
organization
would
look
like
you
can
you
can
you
can
get
different
results
when
you
do
that?
That's
that's
just
my
thought,
but.
E
Right,
that's:
why
that's
why
I'm
saying
building
that
content
in
one
place
and
then
organizing
it
in
that
in
that
second
place,
maybe
it
may
be
a
way
to
manage
it
and
once
again,
I
think.
E
The
people
who
are
doing
the
work,
but
which
is
not
me
so.
C
E
Seems
to
be
where
you're
going
it's
pulling
from
there
now
we
might
as
well
just
leave
it
and
when
we,
when
they
build
the
knowledge
base,
they're
going
to
pull
from
documents
that
are
in
community
they're,
going
to
pull
from
documents
that
are
in
that
existing
community
handbook.
Okay,
so.
E
E
C
C
F
F
Ultimately,
as
kevin
said,
it
should
be
up
to
the
people
doing
the
work,
so
I
I
don't.
I
I
think
we
should
just
maybe
defer
that
bigger
conversation
to
that
group
and
because
that
doesn't
really
have
a
ton
to
do
with
value
working
group.
To
be
honest,
so
maybe
we
could
defer
to
them
to
see
what
they
want
to
do
with
it.
A
H
E
Let's,
let's
just
leave
it
the
way
it
is
and
we'll
let
the
the
google
summer
of
docs
student
code,
students
figure
out
how
they
want
to
do
it.
Okay,.
D
E
E
A
So
this
will
knowledge
base
will
come
in
future
and
we
will
get
rid
of
community
handbook
repo
right.
E
H
F
A
B
A
I
can
give
you
one
more
minute
to
wrap
it
up.
Maybe
I
was
just
joking
okay.
So
next
item
is
working
group
async
during
the
two-week
period.
I
don't
know
who
has
maybe
anyone
who
has
added
this
can
add.
C
C
A
A
C
I
It
is
background
noise.
Do
I
have
thoughts.
I
I
I
agree
with
you
that
having
some
system
is
helpful,
which
system
works
for
most
people,
especially
since
you
know,
as
I
think,
we've
somewhat
demonstrated
today
in
our
intense
discussion
of
pushes
polls,
and-
and
you
know
I
really
my
own
personal
preference-
is
I
hate
using
git
for
docs?
You
know
it's
just
we
have
so
many.
I
I
I
It
has
always
seemed
way
more
convoluted
as
a
way
to
work
on
docs,
but
the
open
source
world
many
folks
are
still
married
to
doing
everything
and
get,
and
I
get
it,
but
it
drives
me
nuts,
and
that
is
my
personal
sandbox
for
the
day
in
terms
of
you
know,
setting
up
online
gantt
charts-
or
you
know
I'll
own-
this
out
on
that
git
is
one
way
to
do
it
and
there's
project
boards
and
git
where
we
could
do
it.
But
I
don't
know
if
that's
the.
I
The
easiest
on-ramp
to
doing
that
stuff,
so
I
don't
think
I
don't
think
I
really
have
an
answer
for
you
matt.
I
think
again,
though
I
don't
want
to
do
one
of
these
leave
it
up
to
the
people
doing
work
discussions,
it's
maybe
something
that
we
need
to
think
about
and
come
back
to
in
terms
of
how
to
do
that.
Yeah.
I
F
C
So
I
just
feel
like
sometimes
the
and
maybe
different
working
groups
are
different
but
like
we
when
there's
a
two-week
window
and
people
leave
with
action
items
like
I
understand
that,
sometimes
they
just
can't
get
done,
but
sometimes
I
also
feel
like,
like
we
hit
the
meeting
this
meeting,
the
the
sync
meeting
and
we're
like.
Oh,
we
can
do
that
right
now
and
maybe
the
the
synchronous
meeting
is
the
time
to
get
the
work
done.
E
C
E
F
C
E
Often,
for
me,
it
often
depends
on
how
many
action
items
I
pick
up
in
other
working
groups
as
well.
Well,.
F
A
E
C
You
know,
maybe
my
it's
not
really
a
concern
like
my
thoughts,
are
like
a
lot
of
open
source
work
is
done,
asynchronously
and
we're
we're
a
pretty
synchronous,
heavy
community.
We
rely
on
on
zoom
and
I
don't
know
if
that
was
a
function
of
like
just
everybody
being
on
zoom
during
corona.
You
know
during
covid
and
it
was
a
natural
way
to
go.
C
D
F
Yeah,
so
this
sounds
like
a
a
bigger
issue
than
about
shifting,
maybe
to
more
in
the
middle
of,
because
you
know
a
lot
of
people
can't
make
these
meetings
and
I
always
feel
bad.
F
Want
to
so
maybe
incorporating
slack
like
maybe
after
meetings
we
just
like
maybe
copy
the
minutes
and
put
them
in
slack
or
you
know
like
here's
what
we
talked
about
today
for
those
who
missed
it.
You
know
whatever
just
so
that
people
it's
more
like
front
and
center,
because
I
know
like
when
I
feel
when
I
miss
a
meeting
I
feel
completely
lost,
even
though
the
recording's
there,
the
minutes
are
there.
I
still
don't
feel
like.
A
F
A
A
So
with
with
this,
we
don't
have
a
slack
channel
for
the
value,
we'll
create
a
slide
channel
and
I'll
post
today's
summary
and
see
how
community
responds.
D
C
A
D
E
C
D
I
guess
I'm
question
so
what
I
heard
is
that
the
purpose
of
this
is
to
try
to
move
working
group
activity
to
an
asynchronous
mode,
and
I
think
that's
difficult
to
do.
If
all
the
working
groups
are
communicating
in
the
same
channel,
because
then
it
gets
really
hard
to
tease
apart,
like
which
messages
are
for
which
working
group.
E
So
there
was
another
issue
that
elizabeth
identified
and
one
that
one
that
I've
kind
of
seen
as
well,
and
that
is
that
as
we've
as
we've
moved
on,
a
lot
of
our
work
has
kind
of
become
siloed
right.
So
if
you,
if
you
don't,
if
you
miss
a
meeting,
you
kind
of
don't
know,
what's
going
on
right,
so
and
and
and
a
lot
of
people
are
unable
to
attend
all
of
the
meetings
or
the
meeting
that
they
want
to
go
to
every
week
or
every
other
week.
C
D
F
D
Makes
sense
yeah
and
then,
especially,
if
that
wg
value
slack
channel
exists
and
then
my
my
only
question
is:
if
we're
gonna
start
this
now,
how
close
are
we
to
the
discourse
environment
being
up,
because
this
would
be
a
that
would
be
a
better
place
or
I
guess
it's
just
fine
if
we
just
move
it
over
to
discourse,
when
that's
ready,
I
don't
think
that's
a
big
deal.
That's
good,
just
like
just
join
us
on
the
discourse
yeah.
Well,
if
that's
like,
I
don't
know
how
close
we
are
to
launching
that.
F
D
A
D
A
D
E
D
We
could
create
working
group
links
at
the
top
of
the
general
channel.
I
mean
working
groups
are
a
significant
center
of
where
our
work
gets
done
and
if
the
objective
is
to
move
some
of
this
working
group
work
into
an
asynchronous
mode.
D
Making
those
working
group
channels
linked
at
the
top
of
the
general
channel
would
make
it
easier
for
to
point
people
to
how
you
get
involved
in
a
working
group.
In
case
they
missed
this
message
that
we
send
out,
though,
it'll
be
harder
and
harder.
If
we
provide
short
updates
in
the
general
channel
every
week
we
meet.
D
No
it'll
be
easier.
I
just
harder
like,
as
as
we
post
as
each
yeah,
so
hiding
it.
Kevin's
concern
was
hiding
it
in
all
these
different
channels,
and
I
was
like
well
working
groups-
are
the
center
of
most
of
our
activities,
so
it
would
be
reasonable
to
put
link
buttons
at
the
top
of
the
slack
channel
for
the
general
slack
channel
for
each
working
group,
probably
as
abbreviated
of
a
name
as
possible.
C
C
D
C
C
A
I
So
we've
been
in
the
to
do.
Group
we've
been
talking
about.
You
know
aspology
sessions
for
those
who
don't
know
what
those
are.
Those
are
monthly
kind
of
presentations
about
a
certain
aspect
of
working
in
open
source
run
by
the
to
do
group
out
of
the
linux
foundation.
That's
do
group
is
a
conglomeration
of
a
bunch
of
open
source
officers,
experienced
open
source
people
and
what
I
in
ex
and
what
I
termed
in
our
working
group
meeting
yesterday
as
the
ospo
curious,
which
became
there
is
a
term,
so
it
did
so.
I
You
know
one
of
the
possibilities
of
content
for
an
ospology
session
would
be
metrics
and
analytics
indirectly
or
chaos
directly,
and
the
link
in
that
document
is
the
way
you
do
a
pull
request
to
suggest
you
want
to
be
a
part
of
a
session.
If
that's
something
you
folks
want
to
do,
then
you
should
do
that.
Click
on
the
link,
because
I'm
I'm
not
a
hundred
percent
sure
that
it's
accessible
by
people
who
are
not.
C
I
J
I
I
C
I
How
dare
you
expect
me
to
know
day
and
time?
It's
very
selfish
of
you.
It's
it's
generally
the
first
week
of
the
month,
and
I
think
it's
at
11.
me
a
minute,
and
I
will
actually
look
it
up.
I'm
surprised
it
doesn't
stay
on
the
form.
It
probably
should
the
github
repo
is
not
going
to
tell
me.