►
From YouTube: CHAOSS Community Meeting May 2, 2023
Description
Minutes from this meeting can be found here: https://docs.google.com/document/d/1PMDWc6xMe0fNE7shxTK5_HE_ykRBG5w55_Zx5hvzsEY/edit?pli=1#heading=h.x304ic6g3nxl
A
C
C
We're
the
noon,
crew,
I,
hope
everybody's
doing
well.
Let
me
let's
share
this
boom.
We've
been
talking
about
pickled
everything
this
morning,
so
yeah.
If
anybody
else
has
a
pickled
thing,
they
like
feel
free
to
add
that
to
the
list,
I,
don't
see
anybody
putting
pickled
pig's
feet.
Is
that
a
thing
it.
C
C
C
Okay,
so
we're
gonna
hop
into
the
agenda.
We
do
not
have
a
meeting
next
week
so
because
Cascon
is
happening
that
same
day,
even
though
there
isn't
a
strict
conflict,
because
that's
an
afternoon
but
yeah,
if
you
would
like
to
still
connect
with
chaos,
because
we
know
that
you
will
just
miss
us.
If
you
don't
have
chaos
in
your
face
for
one
day,
you
should
join
chaoscon
instead
and
we'll
be
hanging
out
in
the
slack
Channel
if
you're
virtual.
C
D
B
C
A
G
C
B
H
F
C
G
C
F
G
G
It's
because
usually
like
I
feel
like
in
the
mornings
we've
just
like
said
right
after
work
at
lunch
or
something,
and
we
don't
really
have
that
option
as
the
like
evening
sessions,
so
either
right
after
or
maybe
like
a
meet
up
during
chaos
and
I
didn't
or
sorry
during
open
source,
some
I
didn't
know
if
people
wanted
to
do
a
separate
Meetup,
that's
more
like
socially
minded
I'm
happy
to
sort
of
again
like
try
to
get
people
together,
but
I
didn't
know.
If
we
wanted
to
float
a
day
time
or
thing.
B
G
G
F
G
B
Well,
maybe
we
could
do,
we
could
do
like
a
happy
hour
or
coffee
or
something
from
five
to
six
and
then
do
something
something
else
afterwards
and
just
try
to
just
do
something.
Long
and
informal
like
we
could,
even
you
know,
meet
up
in
one
of
the
like
Hotel
restaurants
or
something
kind
of
cheesy.
If
we
wanted
to
just
have
like
drinks
and
snacks.
G
C
C
A
C
F
H
F
H
F
C
C
B
Yes,
I
can
talk
about
this,
so
the
idea
behind
this
was
that
the
chaos
project
has
changed
and
grown
dramatically,
since
the
original
charter
was
put
in
place
for
like
the
governing
board,
and
that
was
really
the
only
governance
document
that
we
had
was
the
was
the
charter.
So
the
idea
behind
this
was
that
we
keep
the
charter,
which
really
does
a
great
job
of
explaining
what
the
governing
board
does
and
then
add
some
additional
governance
material
around
the
the
working
groups,
the
software
all
kinds
of
stuff.
B
You
kind
of
see
it
in
this,
this
governance
diagram,
but
the
idea
was
that
we
we
really
want
to
keep
this
as
simple
as
possible,
so
people
will
tend
to
try
to
want
to
add
everything
to
the
governance
documentation,
but
we
don't
want
that.
We
want
to
keep
it
as
clean
as
we
possibly
can
as
simple
as
we
possibly
can,
because
every
change
we
want
to
make
to
this
in
the
future
is
going
to
require
governing
board
approval.
B
B
I've
left
them
in
the
document
for
now,
just
because
I
think
it's
I
think
it
helps
people
understand
what's
what
what
we're
talking
about
and
which,
which
metrics
working
groups
fit
within
which
category
but
we'll
have
a
separate
page
which
will
have
all
of
those
details,
and
so
we're
not
we're
not
making
this
governance
document
doesn't
actually
make
any
changes
to
what
we're
doing
the
idea
is
that
we're
just
starting
to
document
the
stuff
that
we're
doing
better?
So
so,
don't
think
of
this
as
like
a
big
change
to
anything.
B
B
In
the
chat
was,
can
we
have
a
single
page
for
all
the
highlighted
Parts?
Yes,
absolutely
the
idea
is.
Oh,
you
can
see
right
here
that
teams
that
chaos
page
is
is
probably
where
we
will
we'll
probably
take
that
page
and
kind
of
rewrite
it
so
that
it
has
all
of
the
current
things
on
it
and
it's
up
to
date
and
then
we'll
just
keep
that
page
up
to
date
and
it'll
have
all
the
stuff
on
it.
B
So
it
would
be
similar
to
what
this
is
now,
but
this
is
kind
of
badly
formatted,
but
it
would
have
the
you
know
the
group
name,
so
what
it
is
probably
a
very
brief
description,
a
link
to
where
they
do
their
work.
So
that
could
be
a
repository
that
could
be
somewhere
and
then
it
would
have
the
leadership
roles.
B
B
A
B
And
and
over
time,
I
think
that
you
know
these.
This
will
evolve
over
time.
There
will
be
changes,
we'll
need
to
make
to
it,
but
the
idea
is
we
get
this
as
good
as
we
can
as
simple
as
we
can
and
then
and
then
we
can
evolve
it
later.
So
you
know
we
have
some.
The
only
really
new
thing
that's
in
here
is
the
liaison
role,
which
is
something
that
we've
talked
about,
but
not
actually
implemented,
and
that
that
may
work
or
not
right.
B
B
This
isn't
like
forever
set
in
stone
must
must
be
the
way
it
works
it
just
it
just
requires
governing
board
approval
to
do
it
and
the
other
things
that
we
talked
about
I
I
spent
some
time
talking
to
Vineyard
about
this
is
that
we
probably
want
to
put
more
details
about
what
some
of
these
groups
do
so
like.
Maybe
we
maybe
we'd
want
to
have
like
a
like
a
role,
description
for
like
a
maintainer
and
go
into
loads
of
detail
about
what
the
maintainers
are
doing
or
details
about.
B
B
We
can
create
additional
documents
with
more
details
about
each
of
these
things
and
so
I
think
that
that
will
that
will
also
help
so
over
time,
we'll
we'll
kind
of
beef
this
up
a
little
bit,
but
probably
outside
of
the
the
document
that
way,
because
we're
all
handbooks
that
way,
those
those
can
change
more
frequently
and
we
don't
have
to
vote
on
those
every
time
we
decide
that
a
co-chair
should
also
do
X
or
Y
or
Z.
So.
B
Yeah,
we
can
do
that,
absolutely
it's
one
of
the
things
that
we've
done
in
the
kubernetes
project,
so
in
at
least
within
contributor
strategy.
They
have
role
handbooks
for
each
of
the
roles
and
it's
it's
just
a
really
detailed
description
of
exactly
what
that
does,
that
you
know
that
that
person
or
or
role
is
responsible
for
so.
B
And
so
the
other
thing
that
I
did
so
you
scroll
just
up
just
a
little
tiny
bit
all
right
right
there,
so
where
it
says
maintainers
are
selected
by
the
leaders
of
the
group
to
be
represented,
is
that
there
were
some
questions
about
this.
So
my
idea
was
that
different,
like
the
software
sub
projects,
are
led
by
a
group
of
maintainers
that
the
chapters
are
led
by
chapter
leads.
The
working
groups
are
led
by
chairs,
so
I
could
detail
all
of
that
out.
B
A
D
B
A
B
B
E
Okay,
so
when
we,
when
we
look
at
governing
board,
it's
very
clear
how
the
governing
board
is
is
set
right,
so
the
it
says
that
the
the
governing
board
is
governing
board.
Members
are
picked
by
the
existing
governing
board
when
we
get
to
leads
or
or
work
group
chairs.
It's
very
clear
that
work
group
chairs
are
elected
by
or
selected
by,
consensus
from
the
members
of
the
group,
so
that
is
very
clear.
When
we
get
to
Liaisons
and
maintainers
it
just
says
leaders,
however,
leaders
is
not
used.
E
B
Yeah,
it
depends.
It
depends
on
the
group
so
for
a
software
sub
projects,
it
would
be
the
collection
of
maintainers
because
they
don't
have
chairs
for
the
the
soccer
sub
projects
for
the
working
groups.
It
would
be
chairs
because
that's
kind
of
the
top
level
leadership
for
the
working
groups
I
will
I
will
fix
this
how's.
That
I
will
I
will
reword
this
in
some
way.
B
That
makes
it
clear
so
I'll
either
be
clear
about
who
the
leader
is
in
each
of
the
sections,
so
that
then
I
can
say
this
or
I
will
just
be
more
explicit
in
these
two
places.
All
I'm
gonna
think
about
that
a
little
bit
and
look
at
it
and
then
let
you
know
so
you
can
have
another,
so
people
can
have
another
crack
at
it
to
see
if
if
our
people
are
happy
with
it,
but
no
did
you
have
a
question.
Yes,.
I
So
one
of
I
just
have
a
comment:
I
was
reviewing
the
knowledge
base
and
one
of
the
feeling
that
I
came
across
is,
from
a
newcomer
perspective
like
a
cheerleader
different
terminologies
are
representing,
which
is
making
me
more
confused.
Like
am
I
clear.
What
is
the
difference
between
a
chair,
a
leader,
a
license
or
maintainer?
C
D
C
It
in
a
spreadsheet
and
we
tried
to
like
pull
it
in
and
it
did
not
work
very
well,
but
so
that's
why
we
have
these
example
types
of
contributions
in
this
column
here.
Would
there
be
space
for
this
somewhere
else
or
where
would
you
recommend
do
we?
Where
would
you
recommend
we
put
this
if
we,
if
we
still
want
to
keep
that
open
for
newcomers
to
kind
of
help
them
find
where
they
want
to
go.
B
C
C
C
And
Matt
and
myself
started
it
in
a
spreadsheet
just
so
we
would
have
something
to
point
newcomers
to
informally
that
we're
asking
like
how
can
I
contribute?
It's
like.
Well,
here's
some
teams,
you
can
think
about
joining
and
here's
the
kind
of
contributions
that
you
know
and
then
we
thought
oh
I'll,
put
it
out
on
the
in
the
community.
Knowledge
base
make
it
a
little
more
visible
instead
of
interest
in
a
spreadsheet,
but
that's
where
it
kind
of
stopped.
So
we
haven't
really
looked
at
it
or
I,
don't
think
updated
it
there.
C
It's
just
kind
of
hanging
out
there
like
yeah.
It
still
has
like
some
of
the
older
teams
that
aren't
really
active
any
longer,
so
we
will
need
to
like
make
sure
that
it's
getting
updated
regularly
or
link
it
to
something
else
or
I'm,
not
sure,
but
that
was
the
original
kind
of
evolution
of
this
doc
right
here.
C
B
If
you
go,
if
you
go
back
to
the
governance
updates,
there's
a
section
for
operational
working
groups,
if
you
scroll
scroll
up
just
a
bit
yeah
here,
you
go
so
so
these
are
so.
This
whole
section
was
designed
for
those
exact
things.
So
the
things
that
are
less
formal,
maybe
than
some
of
the
other
working
groups
they
may
have
meetings
they
may
not,
but
they're
focused
around
doing
something
for
the
project.
B
So
this
is
where
we
have
things
like
like
badging,
chaoscon,
Communications
and
and
like
I
said
you
know
we
can.
We
can
add
and
delete
working
groups
as
much
as
we
want
as
long
as
they're,
not
in
the
governance
document
itself.
So
you
know
if
we
need
to
spin
up
a
new
one
on
I.
Don't
know
you
know
some
some
more
translations
or
something
we
can.
We
can
spin
up
spin
things
up
and
down,
especially
within
this
within
this
section.
A
B
G
G
B
Yeah,
that's
a
really
really
good
question.
The
typically.
What
what
I've
tended
to
see
is
is
a
maintainers.md
file
for
projects
that
don't
have
really
granular
permission
structures.
So
the
reason
kubernetes
has
the
owners
files
is
because
they
have
prow,
which
is
a
boss
files,
and
it
looks
specifically,
for
you
know.
Each
subdirectory
of
the
code
has
an
owner's
file
to
tell
you
exactly
who's
responsible
and
who's
allowed,
to
merge,
updates
to
that
particular
bit
of
the
code
for
projects
that
don't
have
that
kind
of
rigorous
structure.
A
B
D
I
B
In
a
pretty
pretty
nice
way,
I
think
it
was
I
might
have
to
poke
around
a
little
bit,
but
there
there
are
some
projects
that
have
done
a
nice
job
of
of
listing
their
their
maintainers.
In
a
way
that
gives
you
a
little
more
details,
yeah,
here's,
here's
an
interesting
one.
I'll
drop
it
in
the
chat,
this
one
for
Harbor,
which
is
a
cncf
project
which
has
things
like
feature
areas
and
leads.
B
It
has
sections
for
the
different
types
of
of
maintainers,
so
it
breaks
out
the
people
that
are
responsible
for
Community
versus
docs
versus
the
code
base.
So
it's
not
that
we
need
anything
this
complicated.
But
my
point
is
that,
like
an
owner's
file
has
to
be
a
specific
structure,
a
maintainers
file,
you
can
structure
it
in
any
way.
That
makes
sense
for
your
project,
because
it's
just
it's
just
free
form
text
like
there's,
no
specific
format
that
it
has
to
have.
H
H
B
A
B
B
A
B
A
C
B
E
B
E
B
E
B
C
D
I
Yeah
I
I
have
posted
that
link.
I
came
across
this
article
where
they
are
using
the
chaos
Matrix,
so
I
wanted
to
bring
to
the
communities
notice
that
they
are
using
chaos
metric
and
trying
to
create
a
database
and
UI
integration.
Things
like
this,
so
just
this
was
more
of
bringing
to
the
community's
knowledge
that.
H
I
H
C
I
I
C
D
Georg,
yes,
last
time,
I
think
we
discussed
about
putting
bibliographic
references
to
our
chaos
metric
page
in
that
way,
any
time
that
people
reference
it,
we
can
count
it
also
to
keep
track.
That's
when
we
we
could
do
I,
don't
know
how
that
went
across,
because
there
are
a
lot
of
things
that
people
are
saying
that
they
build
up
in
demographic
references
now
on
our
end,
we
cannot
track
it.
So
if
we
can
do
that,
then
in
different
Scholastic
website,
we
just
facilitated
that
process.
F
F
D
D
Yeah
we
can
do
the
DUI
or
we
just
use
either
a
simple
like
the
beep
tag
or
different
videographic,
because
not
all
citations
are
using.
Let's
see
deep
text,
some
are
using
like
an
information
system.
I
think
you
guys
are
using
a
different
reference
format.
We
can
just
make
like
two
or
three,
the
most
common
ones,
and
if
we
can
have
the
DUI,
it's
also
good
to
have
it.
D
I
C
Where
we
had
a
reference
over
here,
I
think
we
because
we
were
trying
to
say
if
you
reference
to
the
metric,
do
it
here.
But
then
we
changed
I,
think
our
approach
and
now
we're
adding
that
stable
link
to
every
metrics
page.
But
we
don't
really
have
one
for
I
guess
they
could
just
reference
chaos.community.
C
Thanks,
so
thank
you
so
much
for
finding
this.
That's
really
awesome.
I'm
gonna
have
to
read
through
that
later
on.
Thank
you,
vanon.
If
anybody
sees
I
guess,
if
anybody
sees
anything
else
in
the
other
papers,
here's
the
here's
the
place
where
you
can
add
it
while
it
was
where
did
I
put
it
here
about.