►
From YouTube: CHAOSS Weekly Community Call - 12-1-20
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
everyone
and
welcome
to
the
december
1st
edition
of
the
chaos
weekly
community
call,
I
hope
everybody's
doing
great,
and
I
love
the
hats
that
everyone
is
wearing
they're
awesome,
yeah,
we'll
hop
right
in
so
yeah.
I
hope
everyone
had
a
good
break
from
thanksgiving.
Last
week
we
didn't
have
like
it's
gonna,
be
have
to
jog
your
memory
a
little
bit
a
couple
weeks
back,
but
so
I
put
in
the
minutes
I
just
realized
from
last
week,
but
it
actually
was
from
two
weeks
ago.
A
So
sorry,
if
there's
anyone
who's,
detailed
oriented
and
that's
gonna
bother
you
we'll
just
change
that
real,
quick,
so
yeah.
So
last
time
we
met,
we
had
some
action
items
that
we
had
not
discussed
yet
so,
let's
jump
in
those
specifically
we're
talking
about
the
community
reports.
A
First,
we'll
just
hop
on
that
and
it
looks
like
we
don't
have
matt
or
sean
on
the
call.
So
I
will
give
the
update
on
that.
We
are.
I
actually
don't
know
what
the
lf
said
from
matt
and
I
think
that
sean
has
automated
some
of
that
right
vanad.
I
think
so
that
you.
B
A
Okay,
sorry
all
right
we're
working
on
it.
It's
all
good!
It's
all
good!
We
have
had
a
few
requests
come
through,
so
we're
getting,
I
think,
a
little
better
every
time
and
I'm
also
not
sure
so,
I'm
not
sure
what
the
result
of
matt's
conversation
with
lf
on
how
they
handle
their
data
went
and
I'm
not
also
not
sure
about
the
privacy
policy
with
mike
dolan.
So
if
matt
hops
on
later,
we
can
get
those
updates
from
him.
If
not
we'll,
just
get
him
next
time.
A
No
big
deal
moving
ahead,
because
I
know
we
have
a
lot
to
talk
about.
The
community
report
outreach.
So
we
had
a
really
good
meeting
this
morning
and
we'll
we'll
continue
to
meet
every
tuesday
at
9
30
central,
if
anyone's
interested
in
talking
about
this
you're,
more
than
welcome
to
join
the
same
regular
chaos,
zoom
link
so
just
pop
in
whenever
you
want.
A
We
are
currently
looking
at
some
different
buckets
of
people
that
we
want
to
reach
out
to
that.
We
think
that
might
have
an
interest
and
get
some
stuff
out
of
get
some
benefit
out
of
the
community
reports,
and
so
you
can
see
that
we,
I
listed
those
here
in
the
in
the
minutes,
the
one
that
was
a
little
controversial,
that
kind
of
redirected.
A
Our
our
goals
with
the
community
reports
was
the
this
idea
that
potential
or
that
educators
or
people
running
code
boot
camps
might
get
some
benefit
out
of
these
reports
and
it's,
I
know
it
wasn't
kind
of
where
we
saw
the
direction
of
these
going.
We
kind
of
set
them
up
with
the
open
source
maintainer
in
mind,
but
also
you
know,
maybe
like
people
running
ospos
or
inner
source
that
wanted
to
see
projects
that
were
in
their
kind
of
kind
of
wheelhouse.
A
So
the
the
departure
here
is
that
just
a
little
backstory
really
quick.
When
I
was
at
php
women,
we
had
a
lot
of
people
that
would
come
to
our
group
and
ask
where
they
could
participate
because
they
wanted
to,
but
they
didn't
know
where
to
go.
A
They
didn't
want
to
start
so
we
felt
very
kind
of
responsible
for
sending
people
in
a
good
direction
and
not
pointing
them
to
a
project
that
was
going
to
be
toxic
or
terrible,
because
if
they
have
a
terrible
experience,
I
also
had
this
experience
at
github
as
well.
When
I
was
running
the
patchworks,
if
a
newcomer
has
a
bad
experience,
contributing
to
open
source
they're
very
likely,
never
going
to
come
back
to
open
source
in
general,
maybe
you
know
if
we're.
A
A
You
know
what
what
communities
might
be
a
little
bit
more
healthy
than
others,
so
that
was
that
kind
of
led
us
down
this
other
path
of
you
know
all
the
other
people
who
could
request
reports
for
different
reasons,
maybe
not
even
being
a
maintainer,
just
even
an
individual
who
wanted
to
see.
How
is
this
project
that
I'm
considering
contributing
to?
How
do
they?
How
are
they
doing
just
you
know
real
high
level
at
a
real
high
level.
A
So
that's
where
we
kind
of
landed
that
that
was
maybe
a
whole
segment
of
of
the
open
source
community
that
could
really
get
a
good
benefit
from
these
reports.
So
we
kind
of
decided
to-
and
I
would
love
to
hear
this
group's
this
group's
feedback
on
that.
A
We
we
kind
of
decided
to
because
we
can't
control
or
or
even
have
any
insight
into
the
relationship
between
who
is
requesting
these
reports,
and
why
that
we
would,
we
would
continue
to
fill
them
for
whoever
requests
them
for
whatever
reason,
because
we
don't
really
have
the
means
to
track
that
down
into
to
vet
that
so
and
it's
all
public
information
just
to
be
clear
for
everyone
who
isn't
familiar.
It's
completely
public
information
that
we
use
in
these
reports.
A
So
we
decided
that
we
would
continue
to
just
do
to
whoever
requests
them,
but
just
send
the
report
to
that
person
and
then
we're
going,
but
we're
not
going
to
post
publicly.
A
What
we're
going
to
do
instead
is
reach
out
to
maybe
10
or
15
projects
to
see
if
they
would
allow
us
to
run
these
reports
on
their
behalf
and
public
and
and
publish
them
publicly
as
a
sample,
so
that
people
could
see
what
what
these
reports
were
all
about
and
what
they
would
look
like.
So
I
would
love
to
hear
feedback
on
anyone
who
is
interested
in
this
conversation
or
has
thoughts
on.
D
I
do
think
this.
This
kind
of
change
in
mindset
will
require
some
minor
edits
to
the
to
the
form
and
the
page,
just
kind
of
in
the
language
we
use.
D
This
was
discussed
in
the
this
was
discussed
in
that
meeting
as
well,
is
that
we
prior
we'd
been
framing
it
as
get
a
report
on
your
project
where,
where
now
we're
it'll
be
more
like
get
a
report
on
a
project
so
and
we
we
removed
that
ownership.
E
I
component
also
thinking
a
little
bit
about
your
comment
that
we
don't
really
have
a
lot
of
insight
into
the
the
actual
use
case
and
now
that,
if
we
expand
to
different
types
of
individuals
that
they
might
be
interested
in
slightly
different
pieces
of
information
or
how
they
use
it,
it
will
be
slightly
different.
I'm
just
wondering
trying
to
look
at
the
form
again
in
real
time
to
see
if
it
is
there's
any
place
where
we
could
capture
that,
even
if
it's
very
like
just
like
what.
How
do
you
intend
to
use
this
or
like?
E
What
do
you
want
to
learn
from
this
or
something
as
simple
as
that
would
just
shed
a
little
bit
of
light
on
how
people
want
to
use
this
information
that
again
like
depending
on
what
who
they
are
and
if
the
personas
are
changing.
That
could
give
us
a
little
bit
more
insight
into
it.
D
To
that
point
we
we
do
have
the
we
do,
have
the
ability
to
capture
requests
for
certain
metrics
or
certain
things
that
they
want
to
have
measured,
but
you
don't
necessarily
have
the
ability
to
change
up
the
reports
on
an
individual
basis
and
I,
if
matt
was
here,
he
would
probably
say
no.
No,
no.
We
don't
want
to
do
that.
E
B
A
F
I
don't
see
a
problem
with
that,
because
all
the
information
that
we
are
providing
with
the
report
is
aggregated,
so
it's
not
about
individual
people,
it's
not
about
individual
behaviors
or
anything,
and
it's
aggregate
over
a
one
year
time
frame,
I
don't
see
any.
D
D
Oh,
I
was
just
going
to
say
one
of
the
one
of
the
issues
that
was
brought
up
in
that
community
reports
meeting
was
that
a
project
competitor
could
pull
that
data
and
maybe
use
it
to
frame
that
project
in
a
poor
light
or
provide
comparison
between
their
projects,
and
that
might
not
be.
That
might
not
be
something
that
the
project
would
be
happy
about.
G
Yeah
I
mean
that
that
was
actually
this.
I
I
had
a
similar
concern.
I
mean,
although
all
the
information
is
public
like
why
get
in
between
that
right,
I
mean
do
the
job
on
behalf
of
a
like,
a
competing
project
or
the
two
projects
who
don't
get
along
with
with
each
other
and
there's
a
potential
for
for
the
chaos
project.
To
I
mean
why
get
involved
in
the
fight
potentially.
H
G
I
mean
that's
kind
of
dicey
too,
like
there's
some
random
person
that
says,
can
you
run
a
report
on
this
project
abc
and
we
don't
know
what
that
person
is
like?
Does
he
does
he
or
she
belong
to
that
project,
or
it's
just
snooping
around,
because
they're
involved
in
a
competing
project
right,
so
there's
you
know
no
way
to
like
really
enforce
it.
I
mean
this
is
like
I
don't
want
to
start
like
a
whole
big
channel
warms,
but
I
think
you
know
like.
I
would
personally
not
run
the
report
on
somebody's
behalf.
G
Just
give
him
how
to
just
give
him
instructions
on
how
to
do
it.
Like
here's,
where
the
tools
are,
here's
a
white
paper
on
on
how
you
can
you
know
how
you
can
do
metrics
for
whatever
community
you're
interested
and
then
we're
done
with
that,
like
here's,
here's
a
white
paper,
best
practices
on
how
to
do
it,
like
not
run
the
report
on
somebody's
behalf.
G
I
think
that
just
I
think
we're
just
taking
a
lot
more
on
than
than
we
need
to,
but
the
downside
of
that
is
like
we
don't
know
who
was
like
using
that.
Potentially,
but
so
I
mean
that's,
I
obviously
I
haven't
been
involved
in
this,
this
discussion
in
a
separate
meetings,
but
that's
sort
of
my
concern,
but.
H
We
work
with
events,
and
we
have
them
provide
that
they're,
an
organizer
for
the
event
that
they're
working
with,
I
think,
having
like
all
we
ask
for,
is
a
link
and
if
it,
if
it
shows
them
as
an
organizer
for
the
event,
then
that
I
don't
know
what
you
want
to
do
with
that.
But
I
I
think
ray's
right
and
I
I
I
see
that
like
it
should
be
somebody
that's
got
some
kind
of
maintainer
role
in
the
in
the
project.
C
C
You
know,
free
labor
to
do
due
diligence
on
startups
that
could
that
are
open,
source
based
or
yeah,
or
just
kind
of
a
go
fetch
this
rock
type
task
for
us
for
somebody
who's
like
oh
well,
this
takes
no
effort
and
it
will
take
a
bunch
of
effort
for
other
people,
so
we
might
as
well
do
it
so
yeah
being
a
little
particular
about
how
we
filter
so
that
we
don't
end
up
on
menial
tasks
and
or
adding
a
throttle
to
how
many
we're
willing
to
do
be
pretty
choosy
about
it.
C
I
trust
our
judgment
in
this
group,
like
the
request
will
come
in
and
we'll
be
like.
Oh
that
doesn't
feel
right.
We
won't
do
that,
so
I
think
we'll
end
up
getting
to
where
rey
is
right
now,
where
it's
just
like
this
seems
like
something
we're
putting
ourselves
in
the
middle
of.
I
love
that
vision,
though
of
saying
like
our
goal,
is
to
build
a
system
that
is
self-service,
but
I
think
we're
all
acknowledging
that
we
don't
totally
know
what
that
looks
like.
C
So
we
have
to
be
in
the
process
to
experience
the
pain
of
doing
it
a
few
times
and
I
think
we'll
quickly
build
something
external
and
maybe
just
a
comment
on
that.
One
thing
I
think
I
the
anxiety
of
all
open
sources,
a
little
bit
that
people
can
use
it
for
nefarious
things
like.
I
don't
think
we
have
to
worry
ourselves
with
with
that
we're
accepting
that
risk
by
being
open
source
project
in
community,
but
yet
maybe
we
won't
make
it
so
easy
that
we
do
it
for
them.
C
I
I
It-
and
I
I
think
your
point
is
well
taken
too-
that
sometimes
the
process
of
automation
involves
humans
for
a
while
to
understand
kind
of
the
flow
of
work.
What
automation
could
look
like
at
different
spots
and
how
that
automation
can
be
connected.
So
I
agree-
and
I
know
that
sean
with
auger
is
very
much
gearing
towards
an
automated
process
that
is
like
a
hundred
percent
on
his
mind,
gay
org.
It
may
be
a
little
bit
harder
with
cauldron.
I
don't
know
if
you
could
speak
to
that.
F
Yeah
as
of
right
now,
it's
not
on
the
roadmap
to
automate
anything
might
be
down
the
road
cauldron
right
now
has
still
the
challenge
of
also
finding
users
that
actually
get
value
out
of
it.
So
the
user
base
is
still
fairly
small
and
they're
experimenting
with
different
features
to
see
what
people
respond
to
how
they
respond
to
it.
F
A
Okay,
so
it
sounds
like
just
wrapping
up
this
part
of
the
the
meeting.
It
sounds
like
we're,
maybe
not
a
fan
of
providing
the
reports
to
people
who
are
not
open
source
maintainers.
A
Everyone
seems
to
be
kind
of
in
agreement
with
that,
and
I
I'm
totally
fine
with
that
as
well.
So
we
will
take
that
part
out
of
the
outreach
plan
and
just
focus
on
open
source
maintainers.
I
guess
ospos
are
a
little
gray
area
there,
but
they
could.
I
mean,
I
guess
in
theory
they
could
reach
out
to
the
individual
projects
and
just
say
hey.
You
know
we're
curious
about
these
so
about
this
data.
So
would
you
get
that.
C
C
A
Yeah,
I
think,
to
matt
snell's
point
earlier
about
just
asking.
Maybe
maybe
this
is
a
change
that
we
make
on
the
form
I
hate
to
keep
changing
that
form
kevin,
I'm
so
sorry
kevin's
like
stop
changing
it,
but
anyway
we
could
maybe
just
ask
for
a
link
or
well.
Actually
we
do
have
their
github
username
yeah.
A
B
So
github
we
get
to
know
the.
What
are
the
who
are
the
contributors
like
they
can
be
core
contributor,
maintainer
or
periphery
contributor.
We
don't
know
by
looking
at
the
repo
like
it'll,
be
okay
highest
contributor.
Maybe
highest
contributor
is
even
not
a
maintainer,
we
cannot
ascertain
so
how
we
ascertain.
Who
is
the
maintainer?
That
is
the
point.
So
if
any
of
the
contributor
ask
for
the
report,
we
can
just
provide
it
to
them
or
it
has
to
be
with
the
maintainer.
A
D
D
A
I
I
D
Which
we
don't
want
to
be
in
the
middle
of
stuff,
so
the
so
the
language
on
the
form
and
on
that
page
needs
to
change
so
that
it's
as
a
maintainer.
You
can
request
these
reports
and
then
we
need
to
add
a
some
sort
of
user
id
capture
in
the
form,
but
then
on
on
the
the
checking
side.
We're
only
checking
that
they're
a
contributor
is
that.
A
A
So,
okay,
let's
see
so
the
next
item
on
the
list
is
talking
about
chaos
con,
and
I
know
there
has
been
discussion
about
this
in
the
asia
pacific
meetings-
they're
very
keen
to
do
a
chaos
con
china.
So
if
you
all
are
interested
in
that
conversation,
those
apac
meetings
happened
on
was
today
tuesday.
They
happen
on
wednesday
mornings.
A
I
think
king
sent
out
an
email
on
the
mailing
list.
So
if
you
want
more
information
about
what's
on
the
agenda
and
all
of
that
check
your
emails,
because
I'm
assuming
everyone
here
is
subscribed
to
the
mailing
list,
if
you're
not,
then
you
should
be
so
go.
Do
that
and
then
last
time
we
had
said
tf
for
a
deeper
dive
discussion
after
thanksgiving
and
I'm
assuming
that
we
were
also
talking
about
just
the
the
either
north
america
or
european
ks
con.
I'm
not
sure
how
we
wanted
to
talk
about
those
things.
A
I
Yeah,
so
chaos,
cotton
eu
right
is
officially
not
happening
in
two
soon,
so
in
one
month
it's
a
stunner.
I
know
for
everybody,
I'm
sure
you
were
all
booked
for
that.
So
I
think
right
now,
our
our
chaos
con
efforts,
look
like
they
are
kind
of
working
with
king
er
with
the
chaos
con
asia
pacific.
So
I
think
that
there's
discussion
about
perhaps
even
some
in-person
component
to
it,
as
well
as
an
online
component
in
terms
of
north
america
for
2021,
is
there
is
open
source
summit
north
america
on
the
date
books.
C
I
K
F
I
G
Yeah
they
they
moved
it
to
june
to
avoid
conflicts
with,
because
august
wasn't
a
good
time.
That
was
the
conversation
I
had
with
linux
foundation,
events,
people,
but
obviously,
with
the
pandemic
that
sort
of
went
out.
The
window
I
mean,
who
knows
they
might
bring
it
back
to
june,
but
I
think,
like
this
year
next
year,
is
still
going
to
be
a
little
unusual.
I
think
so.
I
A
It
does,
but
I
have
a
follow-up
question.
Basically.
C
F
F
L
G
Now
I
was
going
to
say
by
now
we'll
probably
be
reviewing
cfps
right.
George,
like
you
know,
the
deadline
would
have
been
like
around
now
and
the
cfb
selection
committees
would
be
getting
together
to
you
know,
notify
speakers
like.
I
think
we
tried
to
do
that
before
the
holidays
and
book
travel,
but
assuming
like
like
a
fosum
event,
was
happening
like
or
pre
fosm
event
was
happening
in
like
early
february
right,
so.
F
A
D
I
L
A
Okay,
so
what
I
will
do
is
just
put
a
reminder:
somewhere:
oh
bye,
matt.
You
already
left
the
ghost
of
matt
goodbye,
so
I'll
just
put
a
reminder
somewhere
in
my
calendar,
to
just
bring
this
up
back
at
this
meeting.
I
guess
in
march,
after
the
release
so
cool,
and
then
I
think
we're
down
to
so.
We
have
about
20
minutes
we're
down
to
the
working
group
updates,
hooray,
hooray,
so
five.
A
So
we
have
four
minutes
per
group
right
if
we
have
20
minutes
divided
by
five.
That's
four!
Oh
good!
So
who
wants
to
give
the
d?
And
I
update
you-
have
four
minutes
right.
H
Yeah
I'll
talk
about
badging,
someone
else
can
talk
about
dna.
No,
but
dni
badging
has
its
first
real
application
from
the
open
source
community.
H
So
I'll
put
the
the
issue
in
here
and
the
link
there
so
I'll
put
in
the
chat
too,
but
I'll
just
put
it
everywhere,
but
basically
we
have
our
first
big
application.
We
also
have
a
lot
of
prospects
for
future
future
applications
from
all
kinds
of
organizations,
and
I
am
I'm
just
thrilled,
I'm
I'm.
I
was
beaming
the
whole
last
outreach
meeting,
so
I
I
I'm
just.
H
I
So
I
am
super
I'll
just
say:
I'm
super
happy
too.
This
is
fuss
backstage
that
is
applied,
which
is
great.
So
it's.
I
This
in
in
the
real
world
live
or
whatever
the
phrase
might
be,
yeah
super
happy,
and
then
we
also
talked
in
the
meeting
the
outreach
meeting
we
have
had
conversations.
I
Elizabeth
knows
the
person
rich
who
is
in
charge
of
apache
events,
or
at
least
the
title
associated
with
events
that
apache
whatever
that
title
might
be,
and
then
nicole
has
had
some
really
great
ideas
with
it
sounds
like
some
local
groups
in
the
portland
area
that
would
that
would
benefit
by
going
through
the
program,
another
just
great
context
as
well.
I
I
I
A
No
all
right
and
since
sean
isn't
here
I'll
just
give
a
quick
update
on
evolution
and
bernard
kevin.
You
all
can
jump
in
if
I
miss
something
we
evolution
completed
the
change
across
the
board
from
reviews
to
change
requests,
so
that
nomenclature
is
clarified
now
as
change
requests.
A
And
then
I
think
the
current
metric
that
we're
discussing
is
around
branch
life
cycle
and
strategies
which
was
actually
a
kind
of
a
nudge
or
an
idea
from
the
asia
pacific
group.
So
we
have
had
some
really
good
conversations
about
that
and
it's
still
a
work
in
progress
right
now.
Basically,
why
branches
exist
and
how
long
they
exist
and
what
like,
if
there's
clear
strategies
around
that
for
the
project.
A
I
A
I'm
happy
to
spoon
feed,
it's
totally
fine.
Okay,
let's
move
on
to
comment
because
I
see
there's,
we
do
have
some
other
stuff
to
talk
about
after
we
do
these
updates
so
who
wants
to
give.
I
Uncommon,
I
will
do
the
I'll
read
the
minutes
from
common,
so
I
won't
read
all
the
minutes,
but
it's
also
advancing
metrics.
I
think
vanad
and
sean
are
kind
of
coming
to
some
closure
on
some
of
the
work
that
they're
doing
in
common,
which
is
great
to
see.
So
so
that's
really
the
update.
It's
it's
just
positively.
Moving
forward
on
on
those
metrics.
A
Okay,
I
think
that
was
a
great
update.
Thank
you.
I
think
you're
welcome,
probably
gonna
be
the
same
kind
of
updates
for
risk,
and
also
for
value
just
mostly
advancing
the
metrics
that
we're
talking
about.
I
Them
I
don't
know
if
it's
a
risk
update,
it's
just
I
so
just
thinking
about
kind
of
chaos
as
a
whole,
and
I
know
that
we've
and
people
seem
to
get
don't
get
mad
at
me.
If
I'm
gonna
say
the
word
dependencies,
but
like
I
ca,
I
just
can't
shake
how
important
I
think
this
is.
I
I
really
can't
I
just
think
there's
so
there's
gonna
be
such
a
demand
for
understanding
both
upstream
and
downstream
dependencies
and
the
health
in
that
network.
I
I
just
I
can't
get
beyond
how
important
I
think
this
is
going
to
be,
and
again
you
can
all
just
kind
of
say
sure
whatever,
but
at
some
point
I
I
think
the
chaos
project
has
to
not
only
think
about
metrics,
which
are
advancing
quite
nicely
around
dependencies
sophia.
We
had
the
remember
what
that
one,
that
that
was
brought
forward.
E
Talking
we
talked
a
lot
about
linear
and
potentially
using
it
as
an
average
versus
a
sum,
but
as
a
way
to
quantify
the
age
of
any
individual
version,
but
then
there's
obviously
a
lot
of
discussion
around
how
version
age
isn't
always
a
measure
of
maturity
or
quality
so
trying
to
measure
that,
but
also
whether
or
not
it
would
be
a
useful
metric
to
flourish.
I
think
we
did
make
some
progress
on
thinking
about
how
these
types
of
concepts
could
be
applied.
I
think
I
know
matt
probably
feels
this
as
well.
E
It's
still
a
very
complicated
topic,
so
I
think
the
challenge
for
us
has
been
trying
to
really
narrow
in
on
things
that
are
both
actionable
and
interesting.
Like
are
not
just
things
that
we
can
measure,
and
so
those
are
the
things
we
propose,
but
things
that
are
actually
also
useful
and
given
that
the
topic
is
so
wide
and
complex,
trying
to
figure
out
where
the
overlap
between
those
two
things
has
taken
up.
I
think
maybe
three
or
four
risk
meetings
at
this
point
and
will
probably
continue
to
take
up
a
few
more
going
forward.
I
I
I
agree-
and
I
think
so-
the
way
that
we
have
talked
about
say
like
dna
metrics,
is
kind
of
bringing
them
forward
and
say
the
dna
badging
program,
or
we
even
talk
about,
say,
like
evolution,
metrics,
you
know
and
bringing
those
forward
in
the
community
health
reports,
because
that's
largely
evolution
metrics
something
around
dependencies.
I
can't
help.
This
is
part
of
it
to
sophia's
point
that
we
have
the
metrics
say
like
libya,
we
think
through
what
that
metric
means.
I
But
how
do
we
bring
libya
together
with,
I
don't
know,
whatever
other
dependency
metrics,
we
have
to
to
create
kind
of
a
road
map
for
better
understand.
Not
just
here
are
the
metrics,
but
how
can
you
bring?
You
know,
say
three
metrics
around
dependency
together
to
to
really
provide
a
at
least
a
little
bit
more
transparency
on
your
upstream
dependencies.
I
something
along
those
lines.
The
action
ability
around
those.
E
Yeah-
and
I
think
we've
also
spent
a
lot
of
time
just
thinking
about
the
feasibility
and
tooling-
that's
currently
available,
just
to
know
that
some
things
are
easier
to
collect
and
other
things.
It's
like.
This
would
be
awesome
if
we
could
measure
it,
but
there
isn't
currently
a
tool,
that's
available
as
an
open
source
project
or
something
similar
that
could
be
used
easily.
J
When
does
the
the
risk
working
group
meet
again,
please,
when
do
you
guys
meet
thursday's.
E
D
Oh
interesting
topic
yeah,
so
I
I
haven't
been
to
a
risk
meeting
since
the
time
change,
because
the
the
four
o'clock
time
is
kind
of
weird
for
me,
but
I
I
did
want
to
say
that
dependencies
are
being
talked
about
in
the
evolution
working
group
as
well.
D
There
are
seven
metrics
around
dependencies
that
we've
kind
of
proposed
and
are
talking
about.
So
that's
another
good
place
to
talk
about
dependencies.
Yeah.
B
J
E
I
was
gonna
say
we
we
decided
up
front
to
let
individual
working
groups
talk
about
the
topic,
because
it
is
so
large
and
we
didn't
want
to
combine
everyone
with
the
thought
that
it
might
might
derail
the
broader
conversations,
because
it's
such
a
big
topic.
But
I
think
the
hope
is
that
we
will
come
together
again
at
a
certain
point.
I
think
it
might
be
nice
if
now
that
we're
kind
of
the
risk
group
is
closing
in
on
a
couple
of
metrics
and
ideas
for
metrics.
E
E
Because
I
I
think
we
wanted
to
see
how
this
conversation
could
progress
with
different
focus
areas
to
see,
if
just
like,
I
don't
know,
just
an
ideation,
the
more
people
that
have
space
to
talk
about
the
more
ideas
that
will
surface
versus
forcing
everyone
in
one
room
and
then
only
five
ideas
come
out
because
there's
too
many
voices
happening.
So
I
think
that,
right
now
it
is
a
bit
chaotic,
but
at
a
certain
point
we
should
be
coming
together.
So
I
think
matt,
I'm
guessing
that.
D
Yeah
I
like
that
that'd
be
good.
I
think
there,
I
think,
there's
some
there's
different
perspectives
and
how
we're
looking
at
dependencies
too.
The
the
use
cases
are
different
for
risk
versus
evolution,
and
it
might
be
as
simple
as
saying
you
know:
risk
is
more
focused
on
downstream
and
evolution
is
more
focused
on
upstream
or
something
like
that.
But
the
perspective
is
different,
so
I
think
it's
very
appropriate
for
the
two
different
working
groups
to
be
dealing
with
this
topic.
D
I
A
I
And
I
think
there's
a
I
just
hear
about
it
all
the
time
like
a
lot
of
people
care
about
this
like
deeply
and
providing
guidance.
I
think
would
be
very,
very
welcome
not
only
from
here
the
metrics,
but
here's
ways
that
you
can
bring
these
together,
like
the
actual
methods,
processes
and
methods
that
you
can
use
to
bring
these
together
to
provide
meaning.
A
A
Okay
value,
we'll
just
talk
about
that.
We
got
three
more
minutes.
Matt's.
Not
here,
maybe
looks
like
they
also
did
the
change
request,
update
social
listening,
isn't
was
social
currency
metric
system?
It's
now
socialist
social,
social
listening
I
can
talk
and
then
yes,
we
are
also
having
some
university
ospo
metrics
conversations
in
that
group
as
well.
A
So,
if
you're
interested
in
any
of
those
things,
you
should
come
to
value,
and
then
I
see
someone
put
the
holiday
meeting
schedules
on
here
to
discuss,
I'm
assuming
we
want
to
maybe
decide
whether
or
not
to
cancel
or
when
to
cancel
or
how
we
want
to
do
it.
So
I'm
not
sure
what
you
all
have
done
in
the
past.
So.
D
Maybe
I
dropped
those
in
and
I
threw
those
dates
in
because
the
past
we
generally
have
kind
of
canceled
a
full
month's
worth
of
meetings,
and
if
we
we're
getting
there
pretty
quickly,
as
you
can
see
that
if
we
we
have
maybe
one
week
to
two
weeks
left
before
we
would
start
canceling
meetings
for
the
holidays.
D
H
I'm
okay
with
the
13th
through
18th
and
4th
to
8th,
but
I,
like
my
21st
to
first
to
myself.
I
A
Okay,
so
we're
pretty,
I
would
say,
unanimous,
to
cancel
the
21st
through
the
25th.
That
seems
like
pretty
much
a
no-brainer
and
as
well.
The
next
week
would
be
the
20th
through
the
first
kind
of
a
no-brainer.
So
it's
those
like
fringe
bookend
weeks,
yeah,
that
if
we're
okay.
A
I
A
And
if
you
know,
obviously,
if
you
personally
are
going
to
be
on
vacation
or
whatever
you
don't
have
to
come,
you're
not
obligated
we'd
love
to
see
you,
unlike
matt.
We
would
love
to
see
you,
but
no
I'm
just
using,
of
course,
so.
Okay,
cool
12
49
my
time,
11
49
other
people's
time,
but
one
minute
left.
What's
left,
what
do
we
got.