►
From YouTube: CHAOSS Weekly Community Call 1/18/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Hey
everyone
welcome
to
the
18th
edition
of
chaos.
Community
weekly
call
so
happy
to
see
everybody
here.
I
see
a
couple
of
new
faces.
That's
well
new
names
anyway,
it's
great
to
have
you
just
so
you
know
we
do
not
care
at
all.
If
you
have
your,
if
we
have
your
your
camera
off
totally
fine,
we
don't
care.
It's
really
casual
here.
So
we're
just
really
happy
to
see
you
ayo
shinria.
I
don't
know
if
you
want
to
introduce
yourselves.
That
would
be
great.
A
B
Happy
to
start
thank
you.
I
I'm
still
kind
of
feeling
my
way
around
this,
but
I
just
joined
hpe
as
their
new
osco
program
manager,
focusing
on
compliance,
and
I
had
learned
about
chaos
at
ospo
con
last
september,
and
I've
been
intrigued
by
it,
so
I'm
kind
of
lurking
for
now
to
figure
out
what
role
or
how
I
could
use
this
as
part
of
my
role
at
hpe.
A
To
have
you
here,
yeah,
that's
awesome!
I'm
really
glad
that
you
were
able
to
make
this
meeting.
I
am
for
anyone
who
doesn't
know
I'm
elizabeth.
By
the
way.
I
know
it
says
chaos
community
on
zoom,
I'm
elizabeth,
I'm,
the
community
manager
and
I
do
facilitate
these
meetings.
You'll
see
me
popping
up
at
working
groups
throughout
the
week
and
on
slack
and
other
places
mailing
lists
wherever
else.
A
So,
if
you
have
any
questions
about
chaos
at
all,
rhea
or
aya
sure
anybody
feel
free
to
come
to
me,
I
can
point
you
in
the
right
direction.
If
I
don't
have
the
answer
a
lot
of
times,
I
don't
have
the
answer,
but
I
can
find
out
where
to
find
it
so
yeah.
So
I
will
pick
the
next
person
to
go
and
that
would
be
ayush
hi.
E
C
H
H
F
I
Hello:
everyone,
I'm
vinod
ahuja,
I'm
a
doctoral
student
at
university
of
nebraska
omaha
and
I'm
doing
research
in
open
source
software,
and
I
I
have
been
involved
in
cure
since
beginning,
though
I'm
not
a
co-founder,
but
I
have
been
involved
since
very
beginning
of
this
project.
So
yeah,
that's
all
from
my
end,
and
now
I
can
pick
a
nicole,
maybe.
J
I
just
figured
that
out
hello
everyone
good
morning,
good
afternoon,
good
evening,
wherever
you
are
in
the
world
wow,
it
is
so
exciting
to
see
everyone
on
on
this
call.
It's
amazing
wow
I've.
I
have
been
with
chaos
from
sort
of
early
stages.
I've
been
in
open
source
for
about
a
dozen
years
I
sit
at
intel
in
my
day,
job
participate
in
chaos
outside
my
day
job
and
I'm
just
really
energized
by
open
source,
community
and
developer
engagement.
K
K
I
work
with
the
chaos,
diversity,
equity
and
inclusion,
batching
initiative,
where
we
badge
events
based
on
their
bei
practices,
and
I
my
biggest
focus
recently
has
been
kind
of
bringing
new
people
in
as
well
as
inclusive
naming
in
the
chaos
community
I'll
go
ahead
and
pass
it
to
the
the
chair.
Mat
right
here.
Matt
german
pray
well.
L
Hi,
I'm
matt
germain
pray,
it's
nice
to
meet
you
rhea
and
ayush,
and
it's
good
to
see
everybody
in
the
new
year
as
well.
So
I'm
a
professor
at
the
university
of
nebraska
at
omaha,
I'm
also
one
of
the
co-founders
of
the
chaos
project
and
I
kind
of
like
the
I
guess.
I'd
say
that
I'm
involved
in
many
of
the
parts
of
the
chaos
project
so
in
many
different
pieces
here
and
there.
L
So
I
try
to
attend
the
working
group
meetings
and
one
of
the
challenges
I
think
in
the
chaos
project
and
maybe
any
open
source
project
is
making
sure
things
kind
of
stay
together
and
we
need
people
that
kind
of
live
in
a
variety
of
spots
who
can
translate
across
these
different
areas.
So
that's
what
I
do
don
it's
all
yours.
M
Hello,
everyone,
it's
good
to
be
back,
I'm
dawn
foster,
so
I'm
director
of
open
source
community
strategy
at
vmware
within
our
open
source
program
office
and
I'm
part
of
the
governing
board
for
chaos.
And
I
just
I
just
love
data
and
metrics,
which
is
kind
of
why
I'm
here
and
I
will
pass
it
off
to
indigo.
N
N
My
technical
focus
is
on
telecommunication,
nfv
edge
computing,
and
my
community
focus
is
these
days
are
orienting
towards
what
community
managers
do,
how
to
structure
work
and
obviously,
when
it
comes
to
chaos,
what
kind
of
metrics
are
are
playing
a
role
in
that?
How
can
we
get
a
better
understanding
about
what
our
projects
do?
How
they
are
progressing?
N
B
A
A
I
think
that
should
be
it
in
case.
You
have
not
added
your
name
to
the
agenda
as
an
attendee.
That
would
be
great
if
you
want
to
do
that.
So
we
do
like
to
kind
of
keep
track
of.
You
know
what
the
attendance
is,
not
individuals
if
you're
attending
or
not
we
don't
care.
We
just
want
to
see
how
many
people
are
showing
up
to
these
meetings
and
if,
if
they're
working,
so
that
would
be
the
only
reason
I'm
gonna
go
ahead
and
share.
A
A
So
selfishly
that's
why
I'm
doing
that
yeah,
it's
just
a
little
bit
easier,
so
every
tuesday
from
9
to
10
chicago
time,
which
is
what
all
of
the
chaos
everything
is
based
around
the
u.s
central
chicago
time
zone.
If
you
ever
have
a
question
about
that,
let
me
know,
but
that's
kind
of
how
we
roll
here-
and
it
would
be-
I
didn't
write
this
on
here,
but
it's
just
this
channel
this.
L
A
A
No,
it's
an
extra
the
open
office.
Flowers
is
mostly
for
newcomers
and
then
it's
I'm
just
basically
sitting
here
at
the
at
the
computer
with
the
channel
open
and
if
you
want
to
come
in
and
say
hi
and
ask
questions
great.
If
you
don't
that's
also
funny.
So
it's
just
me,
this
meeting
always
happens
at
the
same
time
and
will
forever
probably
happen
at
the
same
time.
So
does
that
clear
that
up?
Thank
you,
yeah
you're
welcome,
you're
welcome.
That
was
a
great
question.
A
E
A
A
If
I
just
do
it,
if
you
have
a
burning
desire
to
do
it
and
you
want
to
take
one
of
those
tuesdays
have
at
it
like,
I'm,
I'm
not
definitely
not
going
to
stop
you,
but
it
was
almost
more
trouble
than
it
was
worth
to
like
see.
If
we
had
you
know,
volunteers
and
trying
to
recruit
people,
it's
all
been
documented.
I
think
there's
an
open
pr
somewhere
that
just
needs
to
be
merged,
but
it
so
you
know
if
somebody
does
want
to
do
that
absolutely
100.
A
I
will
be
more
than
happy
to
pass
that
torch
to
you
for
that
tues
or
yeah
that
tuesday.
So,
just
let
me
know
send
me
an
email,
elizabeth
chaos.community
and
let
me
know
we'll
just
make
it
a
little
more
free-flowing,
instead
of
like,
because
we
had
before
we
had
like
a
big
spreadsheet
and
we
were,
you
know,
keeping
track
of
it.
Yeah,
that's
like
almost
too
much
overhead
for
what
it
is
right
now
so
yeah.
A
Word
up:
let's
move
on
then
okay,
so
we
did
have
some
stuff
from
last
week.
The
first
one
is
that
we
opened
a
poll.
Last
week
we
talked
about
giving
ourselves
a
name
like
you
know.
Github
employees
call
themselves
hovers
for
instance,
so
we
took
some
some
ideas
from
last
week.
We
dropped
them
in
this
poll
right
here
and
it
looks
like
so
if
you
haven't
voted
and
you
would
like
to
we'll
probably
keep
this
open,
maybe
another
week
just
for
the
heck
of
it.
A
A
A
E
A
I
thought
we
did
with
our
kids
yeah
when
we
were
naming
the
kids
and
pat's
all
of
it.
Yeah
you
gotta
yell,
it
chaotix.
Sorry,
okay,
I
think
it
works.
I
think
we
can
do
it,
but
we'll
give
it
another
week,
just
in
case
sorry
that
was
really
loud.
Sorry
to
everyone
who's
now
awake.
It
was
not
the
sound
adjusted
for
you.
A
A
I
L
G
L
L
And
then
inside
of
the
resources,
we
have
it's
the
quality
checklist,
so
you
should
be
familiar
with
that.
So,
as
we
release
metrics,
there's
a
checklist
that
we
go
through
as
part
of
that
release
process,
and
then
we
also
have
the
two
templates
in
there
for
metrics
and
metrics
models
and
the
difference
between
metrics
and
metrics
models
are
the
metrics
are
kind
of
the
atomic
low-level
items.
L
So,
for
example,
like
age
of
an
issue
or
age
of
a
pull
request
would
be
kind
of
a
low-level
metric
and
metrics
models
are
ways
to
bring
those
metrics
together
in
meaningful
ways.
I'm
just
providing
a
little
bit
of
background
that
some
of
you
should
know.
But
if
you
look
at
take
a
look
at
the
prs
elizabeth,
I
did
just
add
the
update
the
metric
and
there's
two
in
there
23
minutes
ago.
30.
L
L
O
L
O
Page
so
at
the
top
of
the
implementation
section,
we
wanted
to
put
kind
of
a
one
to
two
sentence:
disclaimer
that
would
actually
point
to
a
data
ethics
document
that
lucas
and
sophia
are
kind
of
championing
shame
and
they,
if
okay
sophia,
I'm
sorry.
If
I'm
speaking
out
of
turn,
I
I
believe
you
two
are
champion,
and
I
know
lucas
is
that's
what
he
is,
but.
O
O
O
O
O
O
I
A
A
L
A
Sounds
like
a
great
job
for
them.
These
poor
people
haven't
even
come
together
yet
and
they're
already
overwhelmed.
Okay,
awesome.
So
thank
you
to
all
who
have
worked
on
this
and
thank
you
kevin
for
doing
that.
Pr,
that's
awesome!
Thank
you
in
advance
for
matt
for
reviewing
that
and
merging
it
and
yeah.
L
Yeah
exactly
right
there
or
yeah
yep
outline
proposal
for
the
consideration,
so
I
I
don't
know
if
you
have
this
handy,
I
just
want
to
make
sure
you
you
had
this
and
then
when
I
was
looking
at
this
like,
I
was
wondering
how
we
talked
about
this,
like
how
detailed
we
want
to
get,
because
some
of
these
read
okay
to
me
like
here
are
things
you
need
to
think
about
at
the
highest
level,
like
privacy
data
handling
data
storage.
I
don't
know
how
much
more
you
want
to
say
about
those
kind
of
things.
E
Probably
not
too
much
more
given
the
nuance
in
both
corporate
and
governing
body
opinions
and
how
they
vary
across
regions
and
companies.
So
it's
more
just
to
kind
of
flag
areas
of
interest,
but
I
think
it
definitely
warrants
a
closer
review.
I
know
the
earlier
stages
of
the
document.
If
folks
are
in
it,
there
was
a
lot
of
just
collaborative
suggestion,
so
I
think,
because
I
haven't
looked
at
it
in
a
while.
I
would
want
to
review
everything
again
and
just
I
can.
L
Okay,
I'll
just
I'll
add
that
when
I
was
reading
through
this,
I
it
really
felt
like
it
helped
me
locate
myself
like
oh
yeah.
I
should
think
about
that
if
I'm
using
metrics-
oh,
I
should
probably
think
about
this
too.
All
right,
I
should
so
it
didn't.
I
felt
like
it.
I
did
good
work
even
in
this
form.
Right
now,.
E
Yeah
I
mean,
I
think,
the
it
is
sort
of
the
struggle
of
like
how
much
to
say
that's
helpful,
but
not
being
too
prescriptive,
because
everyone's
implementation
is
gonna
vary,
but
like
even
just
looking
at
this,
like
the
one
area
that
I'm
not
really
sure
how
to
handle
yet
is
dealing
with
third
parties
and
just
kind
of
understanding
the
like.
We
don't
want
to
get
too
prescriptive
on
any
sort
of
particular
regulation.
E
It's
just
like
roles
differ
by
who
you're
working
with
and
how
you're
actually
aggregating
these
things
and
sort
of
the
distinction
between
the
good
data,
control
or
processor.
I
guess
in
the
language
of
gdpr,
but
I
don't
even
know
if
we
want
to
go
there
but
yeah
I'll
I'll.
Take
it
on
as
an
action
to
review
this
again
and
have
some
some
way
of
proposal
of
how
to
move
this
forward.
E
E
E
A
K
Yeah,
so
it
looks
like
the
inclusive
naming.
Initiative
is
kind
of
building
up
their
public
lists
of
what
might
be
like
the
most
important,
not
as
important
and
then
like
kind
of
recommendations
for
things
that
in
work
and
I'm
glad
the
list
isn't
super
long.
Yet
because
it's
got
like
like
five
or
six
terms
right
now,
but
I'm
really
glad
it's
not
super
long
yet,
because
that
way
we
can
have
something
actionable.
K
I
I
just
made
I
made
this
in
kind
of
like
a
review
checklist
kind
of
format
that
we
may
be
able
to
go
over,
or
I
can
do
this
on
my
own
time.
Of
course,
too,
is
it
to
go
over
older,
metrics
or
like
from
the
bottom
upward
in
time
and
say,
have
these
terms,
and
can
we
replace
how
do
we
replace
them?
Basically,
that's
all.
L
L
O
L
O
C
O
Check
the
content,
quality
and
technical
requirements
checklist
so
yep,
oh
yeah,
there
it
is
review,
inclusive
naming
is
right
there
under
content
quality
got
it
so
basically
the
the
checklist
does
two
things
for
us
one.
It
allows
us
to
track
the
the
metrics
that
we're
going
back
and
we're
reviewing,
and
then
it
also
goes
through
the
the
content,
quality
and
the
technical
requirements
or
the
formatting.
O
So
if
we,
if
we
follow
these
checklists,
the
hope
is
that
we
can.
We
can
kind
of
have
consistent,
formatting
and
consistent
uses
of
of
terms
and
so
on.
Okay,
but
so
this
is
how
evolution
is
doing
it
and
we,
I
suppose
we
would.
We
would
recommend
that
other
working
groups
maybe
take
a
look
at
this
and
and
maybe
adopt
it,
but
obviously
it's
up
to
them.
C
A
That
matt,
are
you
saying
that,
like
this,
this
is
kind
of
growing
like
originally,
we
were
just
like.
Let's
just
take
a
look
and
make
sure
that
it
sounds
okay,
but
now,
like
we
have
like
this
official
thing,
that's
pretty
loud
like
go
through
every
metric.
So
are
you
are
you?
It
sounds
like
what
I'm
hearing
is
you're
pretty
concerned
about
the
workload
that
would
take
to
review
those
yeah.
L
L
C
L
C
C
I
K
C
L
A
L
A
A
To
do
all
right,
that's
all
good,
and
then
the
final
thing
is
actually
before
we
talk
about
this.
I
just
want
to
give
a
quick
shout
out
to
carl
who
is
also
on
the
call
who
joined
us
carl
hi.
We're
really
glad
you're
here.
Do
you
mind
taking
a
minute
just
a
couple
seconds,
just
tell
us
how
how
you
are
and
who
you
are
and
yeah
just
introduce
yourself.
If
you
don't
mind.
A
O
O
My
I
do
a
lot
of
work
on
the
website.
I've
got
my
my
focus
is
a
little
bit
all
over
the
place.
I
I
like
to
I
like
to
work
on
the
the
the
community
stuff
so
and
a
lot
of
the
a
lot
of
my
focus
is
on
yeah.
Isn't
it
how
the
working
groups
can
kind
of
sync
all
of
their
things
together
and
use
consistent
language
and
terminology?
So
I
do
metrics
models,
common
working
group
evolution
and
the
website.
A
Thank
you
kevin
and
also
thank
you
carl
for
saying
hello,
we're
really
glad
you're
here,
which
kind
of
leads
me
to
this
onboarding
update.
So
this
has
been
a
thing
that
you
know:
we've
been
wanting
to
build
out
as
over
the
course
of
you
know,
2022.
I
know
that's
on
my
kind
of
personal
goal
to
build
that
experience
out.
I
know
it's
matt
cantu
feels
very
strongly
about
that
as
well.
So
I
just
wanted
to
give
a
quick
update.
A
A
I
point
them
here.
I
bring
them
to
the
community
handbook,
but
I
know
we
had
kind
of
talked
about
doing
more
of
like
a
portal
for
newcomers
to
like
take
them
and
then
then
funnel
them
out
individually,
but
we
have
had
25
24
sorry
responses
to
this
form
since
we
opened
it
at
the
end
of
november,
which
is
it's
cool.
I
think
I
mean
that
considering
our
community
is
not
the
largest
in
the
world,
so
like
percentage-wise,
that's
a
pretty
a
pretty
good
number.
A
A
But
I
did
want
to
give
people
an
update
that
this
form
is
is
being
used
and
if
you
go
to
this
website,
which
I
will
copy
and
put
in
the
minutes,
so
you
don't
have
to
remember
these
leave
that
url.
If
you
see
something
that
maybe
I
could
add,
especially
if
you're
a
new
person,
what
would
be
helpful
for
you,
that
would
be
really
helpful
for
me
to
help
more
newcomers
to
our
project
so
yeah.
A
So
there
you
go
and
if,
if
everybody
just
wants
to
take
a
minute
and
look
in
chat,
carl
gave
us
a
little
bit
more
information
about
themselves.
So
that's
really
fantastic.
We're
really
really
glad
that
you're
here,
carl
okay,
we
have
four
minutes
left
to
talk
about
whatever,
or
we
can
get
your
four
minutes
back.
What
what
do
we
want
to
do
anything
else?
We
need
to
chat
about.
B
C
Kevin
and
I
coordinate
the
group
with
armstrong
and
the
nods
off
in
there
and
we
fought
there's
a
checklist
of
things
that
make
it
basically
things
that
are
grammar
changes
or
clarifying
changes
that
don't
change
the
meaning,
and
this
is
in
the
handbook
for
those
kinds
of
things.
We
won't
run
the
metric
back
through
review
following
the
community
guidelines.
However,
I'm
sure
there
will
be
cases
where
we
do
make
changes
that
are
material
that
do
require
community
review.
We
just
don't
know
which
metrics
that's
going
to
happen
on
ahead
of
time.
C
O
O
So
the
the
inclusive,
inclusive
naming
review
is
just
to
take
a
look
through
our
documents
to
make
sure
that
we
are
using
inclusive
naming
or
not
using
terms
that
are
not
inclusive
any
any
metrics
involving
inclusive
naming
would
more
than
likely
exist
within
the
diversity,
equity
and
inclusion
working
group,
and
I'm
I'm
certain
that
they
probably
have
some
that
are
proposed.
So
so,
if
you're
wanting
to
work
on
inclusive
naming,
metrics,
the
diversity,
equity
and
inclusion,
working
group
is
probably
a
great
place
to
look.
O
Evolution
focuses
primarily
on
kind
of
activity
metrics.
So,
like
the
number
of
commits
the
number
of
change
requests
things
of
that
nature,
then
we
also
have
a
value
working
group
which
which
works
on
metrics,
that
help
help
us
understand
the
the
value
of
a
project
to
a
organization,
an
individual
or
a
community.
O
We
have
common
working
group,
which
kind
of
they
kind
of
take,
whichever
metrics
some
of
those
metrics
kind
of
fit
in
multiple
working
groups,
so
they
kind
of
grab
whatever
they,
whatever
kind
of
falls
on
them,
and
then
we
also
have
a
risk
working
group
and
those
those
metrics
are
obviously
associated
with.
With
risk
so
right
now,
I
think
the
risk
working
group
is
is
focusing
a
lot
on.
O
So
so
yeah,
we
all
have
just
a
little
bit
different
focus
on
the
metrics
that
we
that
we
look
at
and
then
the
and
then
the
community
group
that
that's
been
mentioned
a
couple
times.
The
goal
of
the
community
group
is
to
kind
of
make
sure
that
the
working
groups
are
kind
of
using
the
same
processes
and
terminology
across
chaos
and
we're
presenting
the
metrics
in
an
organized
fashion,
so
that
includes
kind
of
our
our
metrics
release
process
and
the
website
and
some
of
our
the
templates
that
we're
creating.
B
K
It
might
be
worth
mentioning
too.
We
have,
if
you
want
to
know
a
little
bit
more
about
like
the
nature
of
the
metrics
that
we're
working
on
in
each
group
kind
of
distinctly.
We
have
this
spreadsheet
that
covers
like
all,
it's
like
all
of
them
planned
working
on
complete
metrics
and
every
working
group.
If
you
want
information
overload,
but
but
yeah
that
might,
that
might
also
be
helpful
for
anyone
new
to
understand
like
oh.
This
is
the
kind
of
thing
that
this
group
does,
that
kind
of
thing.
O
A
All
right
now
that
we've
thrown
a
ton
of
information
at
our
new
computers.
If
you
do
have
any
questions,
let
me
know
I
can
absolutely
send
you
these
links
again.
I
can
explain
what
they
are.
I
can
I
can
answer
any
questions
you
have
so
just
give
me
a
shout
elizabeth
chaos.community
or
you
can
hit
me
up
on
slack
or
twitter.
Whatever
I'm
available
a
numerous
numerous
ways,
I
think
I
counted
one
time
11
ways
to
reach
me
so
yeah,
I
don't
recommend
you
do
all
11.