►
From YouTube: CHAOSS Weekly Community Call 3/22/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Hey
everyone
welcome
to
the
chaos
weekly
community
call
it's
march
22nd,
I'm
elizabeth
barron,
I'm
the
community
manager,
so
welcome.
Welcome!
Welcome
we're
super
happy
to
have
everybody
here
today
we
have
a
pretty
big
group,
so
yay,
you
could
literally
be
doing
anything
else
and
you
chose
to
be
here.
So
thank
you
for
that.
We
appreciate
you
we'll
drop
the
minutes
in
one
more
time
and
of
course,
if
you
do
not
want
to
use
your
mic
or
camera,
you
don't
have
to
feel
free
to
use
the
chat
function
in
zoom.
A
B
A
Sorry
to
put
you
on
the
spot
there
mabel
anyway,
let's
get
to
it.
A
B
A
Anything
awesome!
Okay,
so
if
you
would
like
to
please
add
your
name,
I
I'll
add
mine
as
well
to
you,
this
oh
ray
and
I
are
having
a
thumb,
wrestle
fight.
A
A
whole
week
sleeping
through
the
night
awesome,
I
love
that
I
wish
I
had
that
I'm
a
little
jealous,
I'm
not
gonna
lie.
I
had
a
fantastic
weekend.
I
hope
everyone
did
as
well.
I
went
to
flew
into
tampa
florida
to
see
green
day
in
concert
with
my
son
who's
18..
It
was
a
music
festival.
It
was
amazing
and
then
I
started
the
t-shirt
yeah.
Oh
I
wore
it
yesterday.
Oh,
you
didn't
get
to
see
it.
So
I'm
sorry
yeah.
A
It
was
a
really
awesome
weekend
and
he's
a
senior
in
high
school,
so
he's
graduating
and
so
like
yesterday,
I
was
just
crying
all
day
because
I'm
just
like
my
son
is
leaving-
and
I
love
like
we're
just
buddies
so
anyway
I'll
try
not
to
cry
through
this
meeting,
but
if
I
get
to
you
you'll
understand
why
so
there's
a
little
context
around
that,
but
I
hope
everybody's
doing
okay.
A
I
know
things
aren't
great
in
other
parts
of
the
world,
so
I'm
just
want
to
send
some
thoughts
out
to
them
and
if
anyone
knows
I
don't
think
we
have
any
community
members
over
in
the
ukraine
area.
But
if
anyone
does
know
of
anyone,
please
please
let
us
know
I
would.
That
would
be
really
helpful
information
if
we
had
that
knowledge.
A
So
please,
just
let
us
know
we'll
see
what
we
can
do
to
help
them,
but
anyway,
on
a
better
note,
let's
move
on
to
the
agenda,
so
the
first
thing
is,
we
just
want
to
make
sure
everybody
knew
it's
a
kind
of
a
small
group
that
attends
the
dei
badging
meetings.
A
However,
if
you
are
in
that
group
or
were
considering
coming
to
those
meetings,
just
a
couple
of
quick
changes,
they
used
to
be
a
weekly
cadence
for
switching
to
a
bi-weekly
cadence,
but
we're
extending
the
length
of
the
meeting
so
they're
an
hour
long
every
other
week.
The
next
week
is
or
the
next
meeting
is
march
30th,
and
we
also
have
the
new
zoom
link,
which
is
the
chaos
zoom
link.
We
were
using
a
different
one
before,
but
now
we're
back
on
to
the
chaos
zoom
link.
A
I
think
the
also
the
idea
is
that,
eventually
we
will
record
these
again
and
post
them
on
youtube
with
the
rest
of
the
chaos
meetings,
so
just
want
to
make
everybody
aware
of
that.
Do
people
have
questions
about
that
meeting
or
what
dei
badging
it
like?
What
what
that
is
anything
anybody
wants
to
ask
feel
free.
A
Okay,
then
we'll
move
on
so
from
last
week
we
decided
we
would
want
to
have
an
update
on
the
metrics
models
group
and
we
volunteered
you
matt
g.
So
if
you
don't
want
to
do
it,
we
can
certainly
find
we
can
voluntold
someone
else,
but.
D
I
just
had
to
get
it
in
there
really
quickly,
but-
and
I
can
show
you
or
people
want
to
see
like
kind
of
an
example
that
we've
been
working
with
so
just
a
quick
story
on
kind
of,
can
you
go
back
to
the
template
just
describing
why
the
metrics
so
again,
metrics
models
are
they're
collections
of
the
atomic
metrics
that
are
brought
together
in
ways
that
are
kind
of
meaningful,
maybe
more
meaningful
than
just
a
single
metric
by
itself,
and
so
the
why
it
matters
is
just
an
overview
of
why
we
would
bring
these.
D
You
know
half
a
dozen
metrics
together
things
you
need
to
deploy
this
model,
so
it
would
be
a
really
quick
statement
about
you
know
you
need
software.
D
D
We
then
list
all
of
the
metrics
in
there,
in
addition
to
the
difficulty
trying
to
describe
the
difficulty
in
deploying
the
metric,
that's
kind
of
like
an
educated
guess,
I
would
say
on
our
part
on
what
it
would
take
to
deploy
a
metric
and
then
different
ways
to
actually
produce
that
particular
metric,
whether
it's
sample
survey
and
interview
questions
or
a
link
to
a
jupiter
notebook
or
a
link
to
a
public
software
deployment
where
you
can
actually
see
this
model
in
practice.
D
So
we
would
list
all
of
the
metrics
and
they
would
have
a
link
out
to
the
associated
chaos
metric
to
describe
it
a
little
bit
further
and
the
references
and
contributors,
and
so
that's
the
new.
The
new
model.
I
do
need
to
make
this
a
little
bit
clearer,
at
least
in
the
template.
Again.
I
was
just
kind
of
rushing
last
week
to
get
this
out
of
the
metrics
template
and
into
the
into
the
community
or
out
of
the
metrics
repository
and
into
the
community
repository,
so
we're
all
good
there.
D
So
that's
that
I
don't
know
if
anybody
has
questions
on
the
template,
but
that
was
it's
been
kind
of
a
long
time
coming.
I
think
we're
pretty
good
with
it.
So
if
you
go
back
elizabeth
to
the
yeah.
E
Let's
see
matt
there's
one
thing:
I
want
to
call
out
on
that
by
the
way.
Thank
you
for
doing
that.
It
looks
really
good
and
really
usable
right
one.
I
wanted
to
call
out
that
there
was
one
participant
who
felt
that
why
it
matters
had
kind
of
a
negative
overtone.
D
Okay,
yeah,
we
had
changed
it
from
why
you
should
care
yeah,
so
why
to
why
it
matters.
Maybe
this
is
the
positive.
I
think.
D
Yeah
and
honestly,
you
know
luke
is
like
if
it
yeah
what
problem
yeah.
So
as
melbourne
points
out,
I
mean
we're
very
happy.
This
is
still
kind
of
finalizing,
so
we
can
maybe
somebody
else
grab
what
noble
just
said:
what
problem
are
you
trying
to
solve
right
right
could
be
another
one,
and
we
can
certainly
talk
through
that
no
problem
there.
D
Okay,
we
are
in
terms
of
kind
of
getting
these
metric
models
in
front
of
people.
We
are
working
with
with
folks
like
kevin
about
integration
with
the
website.
I
think
the
distribution
is
going
to
be
slightly
different
than
the
way
that
we
distribute
the
metrics
themselves
so
just
kind
of
a
note
there.
I
don't
have
a
ton
of
input
on
that,
as
I
think
we're
still
kind
of
sorting
this
out
as
to
what
the
best
way
to
get
that
done
is.
D
I
know
that
that
shawn,
you
have
been
working
a
lot
on
thinking
how
the
metrics
models
can
be
deployed
in
auger
software,
so
not
just
not
just
providing
them
as
markdown
files,
but
also
as
live
living
examples.
I
don't
know
if
you
want
to
comment
on
that.
We.
B
Ragava
and
I
one
of
your
students
has
built
a
metrics
model
using
auger
data
and
auger
apis,
and
it
is
released
in
the
metrics
working
group.
Metrics
models
and
one
of
the
things
that
we're
aiming
to
do
is
make
that
model
implementation
and
the
definition
of
the
model
available
for
people
to
see
in
a
live
setting.
B
D
I
was
going
through
all
the
w's
that
it
could
be.
So
I
think
one
of
the
things
that
has
come
out
of
the
metrics
model
working
group
is
like
it's
great
to
have
these
as
markdown
files,
but
we
really
need
to
kind
of
push
towards
like
visual,
like
like
actual
implementations
of
these
models,
where
people
can
point
the
model
at
repositories
that
they
care
about
if
it's
software
deployable.
D
So
that's
a
big
thing
that
we're
thinking
through
right
now
and
then
kind
of
to
that
last
point.
I
think
sean-
and
I
were
talking
about
this
yesterday
and
I
think
we
need
to
to
maybe
try
to
find
some
funds
that
can
help
push
this
just
a
little
bit
kind
of
the
same
way
that
that
we
have
done
it
for
like
the
dei
self-reflection
or
even
just
working
with
the
sloan
foundation.
So
it's
not
a
call
out
to
this.
D
This
call
at
all,
but
I
just
want
you
to
know
that
I
think
there's
some
some
issues
of
scale
that
we're
going
to
have
to
address
that
just
on
a
bi-weekly
call.
We
may
not
be
able
to
do
so.
We
might
need
to
try
to
find
a
way
to
do
some
of
this
in
a
more
concerted
way
over
the
course
of
the
next,
whatever
six
months,
so
just
something
that
sean
and
I
were
talking
about.
D
C
Is
there
any
groups
that
have
tried
to
fill
it
out
and
just
kind
of
curious?
How
is
that
going
and
you're
talking
about
it
in
the
risk
working
group
to
see
it
might
make
sense
to
do
metrics
model
just
because
a
lot
of
the
methods
that
we've
been
talking
about
just
are
just
not
really
that
usable
in
a
vacuum,
so
we
thought
a
metric
model
might
be
the
next
logical
step
to
help
provide
more
guidance
and
context
around
what
some
of
these
how
these
facilities
could
be
used.
C
D
Yeah,
so
the
answer
is
yes,
so
I
don't
have
them
in
this
list
sophia,
but
I
can
put
them
here
and
I
can
put
them
in
the
chat.
We
do
have
a
couple
like
kind
of
existing
metrics
models
that
follow
this
template
and
it
might
help
with
what
you're
talking
about
in
risk
is
how
you
would
bring
about
or
bring
together.
D
You
know
a
set
of
whatever
three
to
four
atomic
metrics
that
might
be
meaningful
in
a
model,
so
I'm
happy
to
share
those,
and
if
you
want
to
take
a
if
you
want
to
give
it
a
go
in
the
risk
working
group,
that
would
be
cool
and
then
I'm
not
quite
sure
what
the
workflow
is
yet
like
if
you
develop
them
in
the
the
metrics
models
in
the
worst
risk
working
group
like
how
we
get
those
back
to
the
metrics
model,
we're
working
group
and
not
quite
sure
what
that
dynamic
is
yet.
F
If
you,
if
you
are
working
on
metrics
models
in
your
working
groups,
it's
it's
probably
a
good
idea
to
have
a
discussion
in
your
working
group
kind
of
what
the
difference
is
between
a
between
a
focus
area
and
a
metrics
model,
because
often
times
those
they're
just
they're
they're
kind
of
ways
of
organizing
these
metrics
together.
But
you
just
want
to
make
sure
that
there's
some
consistency
in
in
your
your
focus
area
versus
metrics
models.
B
And
this
this
issue
kevin
raises-
or
this
question
arose
in
the
evolution
meeting
just
now,
where
we
were
starting
to
work
on
a
code
complexity,
metric
model
and
when
we
think
about
co-complexity,
unlike
most
of
our
metrics,
it's
not
those.
The
underlying
metrics
would
not
look
at
activity.
They
would
look
at
the
current
state
of
a
repository
at
a
point
in
time
in
terms
of
the
number
of
lines
of
code,
the
complexity
of
those
lines
of
code
as
measured
through
some
kind
of
kokomo
or
other
algorithm,
and
all
of
that
is
sort
of
a
snapshot.
B
F
F
Yeah,
I
think,
that's,
I
think,
that's
okay.
I
think
you
just
want
to
make
sure
that
you're
in
the
working
group
that
you're
kind
of
consistent
in
how
you
are
separating
those
focus
areas
from
your
from
your
metrics
models
right,
because
we
we
do
kind
of
we
use
them
in
different
ways.
B
F
Just
just
something
to
consider
when,
when
you're,
when
we
start
looking
at
these
because
they're
the
way
that
we
are
organizing
these
metrics,
their
confusion
could
start
to
come
into
play,
and
I
think
fewer
focus
areas
in
working
groups
is
probably
better.
So
so
a
few
fewer
focus
areas
and
more
metrics
models.
I
suppose
this
would
be
better.
E
So
kevin,
I
think
that
that's
a
subtle
point
and
it
would
be
good
to
document
that
so
that
new
community
members
have
a
easier
time
working.
I
with
it
admit
that
I
don't
have
a
firm
grasp.
D
A
A
I
can
do
it.
Okay,.
D
A
An
item
for
me:
okay,
perfect:
the
next
item
on
the
agenda.
We
dropped
this
here.
Just
for
a
point
of
discussion,
I
think
was
from
the
someone
remind
me
from
the
value
working
group
on
thursday
is
that
where
this
came
up,
where
we
started
talking
about
the
how
we're
doing
the
metrics
review-
and
we
just
wanted
to
kind
of
bring
it
to
the
community
just
to
let
everybody
kind
of
know
how.
A
So
just
so
everybody
knows,
the
original
plan
was
for
each
working
group
to
review
old
metrics
themselves
and
for
whatever
reason
that
was
not
actually
happening,
so
so
myself
and
matt
and
kevin
and
sean
decided
to
take
it
upon
ourselves
and
divide
up
the
working
groups.
So
we
are
gonna,
just
take
a
look
at
each
of
the
older
metrics
and
because
there's
some
besides
some
content
changes.
A
There
are
some
just
formatting
changes
that
we
need
to
make
and
some
extra
blurbs
that
are
standard
now
that
we
need
to
include
such
as
the
privacy
statement
and
like
the
date
of
last
reviewed
and
things
like
that.
So
right
now
we're
gonna
be
going
through
each
of
those
metrics
and
then,
if
it,
if
it
looks
like
it's
something
that
needs
to
like
be
reviewed
by
the
group,
then
we
will
bring
it
to
the
group
and
say
yeah.
This
metric,
the
language
is
all
off
it
needs
to.
A
So
so
that's
how
that's
gonna
go
and
then
matt-
and
I
went
over
this
one
in
the
dei
working
group,
which
was
a
separate
conversation,
which
is
why
we're
bringing
it
here
today
to
kind
of
bring
all
of
these
pieces
together,
and
this
is
kind
of
the
process
that
we
took
to
do
it,
and
this
was
an
example
of
the
code
of
conduct
at
event
was
an
example
of,
and
I
haven't
actually
added
my
changes
yet
so
that's
gonna
be
happening,
but
that
was
the
one
that's
an
old
metric
that
we
brought
back
up.
A
We
reopened
the
original
issue,
we're
gonna
tag
it
with
this
tag,
and
then
we
added
a
new
checklist,
the
quality
checklist
that
we
have
now
we
added
that,
and
so
then
we're
gonna-
we're
not
gonna.
Try
to
push
this
through,
though,
with
this
release,
which
is
why
I
haven't
done
it
yet.
So
I
don't
wanna
confuse
the
issue
because
we
have
all
these.
You
know
metrics
candidates
that
are
out
there
kind
of
waiting
to
go
into
this
april
release.
So
we
don't
want
to
muddy
the
waters
and
I'm
great
at
doing
nothing.
A
D
I
think
the
thing
that
we
had
talked
about
is,
if
you
are
revisiting
metric,
it
was
to
reopen
the
original
issue
and
then
just
tag
it
with
that
label.
D
That
seemed
it
see.
My
guess
was,
is
that
I
think
we
talked
about
this
in
value
that
it
was
kind
of
the
workflow
of
getting
it
done.
That
might
have
been
limiting
this
last
time
around,
like
I
just
don't
know
how
to
actually
review
and
submit
that
review,
and
then
I
think
we
would
just
issue
that
pr
against
the
existing
metric,
the
existing
markdown
file,
and
it
should
be
okay
in
the
next
release.
B
A
D
A
Yeah
anything
else
with
this,
anybody
have
questions,
as
you
can
tell.
This
is
a
work
in
progress.
This
is
the
first
real
time
that
we've
actually
needed
to
go
back
and
review.
So
it's
we're
kind
of
working
through
the
process
as
we
go,
which
is
why
it's
been
a
little
ambiguous
a
little
confusing,
but
I
think
I
think,
at
the
end
of
it,
it'll
all
make
sense
and
we'll
have
a
good
process
for
the
future
moving
forward
and.
E
D
A
Going
once
going
twice
all
right,
that
is
okay,
so
this
is,
I
want
to
bring
up.
The
next
thing
is,
I
know.
Last
week
we
started
talking
about
getting
a
few
of
the
pieces
in
place
for
chaos
con.
Do
we
want
to
start
kick
that
off
today
cast
con
planning
people.
A
I
think
the
things
we
were
trying
to
figure
out
was
were
the
date
for
the
cfp
and
maybe
a
few
other
things,
topics
that
we
want
to
hear
about.
So,
okay,
so
usually
just
for
everybody,
who's
new
or
if
case
you
forgot
chaos,
does
a
chaos
con,
which
this
year
we're
gonna.
A
Do
it
in
conjunction
with
os
summit
eu
september
13th
through
16th
in
dublin,
but
so
prior
to
that
we
have
to
plan
for
it
imagine,
but
instead
of
putting
it
yet
another
meeting
on
all
of
our
calendars,
what
we
do
is
we
just
end.
This
weekly
community
call
a
little
bit
early
so
that
people
who
are
on
the
planning
committee
and
are
probably
in
this
call
anyway,
can
just
stick
around.
A
So
we
won't
do
it
every
single
week,
but
occasionally
we
will
do
that
and
today
is
going
to
be
one
of
those
days.
So
we
usually
end
up
half
half
past
when
we're
needing
to
have
some
time
for
the
cast
complaining
committee.
So
that's
what
we're
gonna
do
so,
essentially,
what
I'm
saying
is
we
have
three
minutes
left
in
our
regular
meeting
now
in
case
anybody
wants
to
talk
about
something
that
can
be
talked
about
in
three
minutes.
A
E
A
No,
I
appreciate
that
it's
kind
of
hard
to
bring
all
the
conversations
together,
yeah,
I'm
going
to
add
a
link
to
the
data
use
statement.
D
Because
I
mean
I'll
I'll,
just
kind
of
like
reiterate
what
we
were
talking
about,
or
at
least
what
I
thought
we
were
talking
about,
which
was
with
the
success
of
the
dei
badging
the
event
badging
program.
I
mean
one
of
the
things
that
I
would
really
like
to
think
about
in
2022
is
badging
at
the
project
level
and
how
that
could
work.
D
There's
obvious
problems
with
it,
just
in
terms
of
like
capacity
to
review,
like
re-evaluation
periods,
that
a
project
would
need
to
go
through
like
there
are
all
sorts
of
things
that
are
going
to
be
different
than
event
badging,
but
that
shouldn't
like
get
in
the
way
of
of
really
trying
to
get
this
done.
So
that
was
my
thought.
Yeah
yeah.
I
agree.
D
E
E
D
But
the
advantage
of
those
is
that
they're
self-reflections,
the
disadvantage
of
those
is
that,
as
the
event
badging
program
puts
a
human
in
the
process.
To
really
do
part
of
that
evaluation
yeah,
which
I
like
around
dei-
and
we
wouldn't
have
that
in
these
types
of
programs.
So.
E
I
think
I
I
definitely
have
thoughts,
but
I
should
hold
off
because
I've
used
more
than
that
minute
and
a
half
okay.
A
Yeah
we
can
continue
this
in
general
if
anyone
needs
a
slack
invite,
please
let
me
know
you
can
email
me
at
elizabeth
chaos.community
and
I
will
make
sure
you
get
your
way
to
our
slack
and
then
you'll
be
plopped
in
general
and
the
conversation
will
be
there
right
in
front
of
you.
So,
okay,
oh
melva,
is
saying:
there's
a
harvard
paper
that
was
published
with
sean's
help
that
recommended
chaos.
Hey
imagine.
B
A
Okay,
so
it's
12
30
my
time,
11
30,
other
people
and
whatever
30
wherever
you
are.
So
let's
go
ahead
and
close
this
I'll
stop
sharing.
If
you're
on
the
kscom
planning
committee,
you
want
to
stick
around
that'd,
be
awesome.
If
you're
not
you
are
free
to
go
and
enjoy
your
day
as
you
see
fit,
and
we
again
appreciate
you
being
here,
we'll
see
you
here
next
time
same
same
place
same
time
next
week.