►
From YouTube: CHAOSS Weekly Community Call October 4, 2022
Description
Minutes and notes from this meeting can be found on https://chaoss.community/participate.
A
Hi
everyone,
it's
October
4th
and
you're
at
the
chaos
weekly
community
meeting,
I'm
Elizabeth,
the
community
manager
good
to
see
everybody
here
we
have
a
late
group,
but
that's
all
right.
We
are
we're
the
ones
that
are
going
to
keep
the
ball
going
for
everybody
else.
So
Here,
Comes
Kevin,
we'll
drop
the
minutes
in
here
for
him
and
anybody
else
that
needs
them.
C
B
B
A
Okay:
let's
go
on
to
the
agenda:
I
guess
we'll,
like
do
some
stuff,
so
the
first
reminder
is
to
take.
If
you
have
not
already,
please
take
our
community
survey
and
share
experience
with
us
so
that
we
can
make
our
community
better
more,
welcoming,
more
inclusive,
it's
open
until
October
12th,
but
I
would
not
recommend
waiting
to
the
last
minute.
You
can
take
it
at
any
time
between
now
and
then
and
if
you've
started
it
don't
forget
to
go
back
and
finish
it
and
of
course
it
is
completely
Anonymous.
A
B
A
A
D
A
D
A
A
Yeah
right
right,
I
really
like
those,
because
even
if
they're,
like
sometimes
we'll
have
people
who
are
maybe
not
brand
new
to
the
community
but
kind
of
new,
and
so
it
gives
us
a
chance
to
really
get
to
know
them
and
they
get
to
know
us
and
they
can.
They
know
enough
about
what
to
ask
it's
almost
harder
when
you
have
somebody
that
doesn't
know
anything
about
chaos.
A
B
A
Okay,
well
we'll
go
ahead
and
move
on
then
gay
org
is
not
here
and
I.
Think
this
action
item
was
his
I.
I
was
looking
at
this
a
little
earlier.
I,
don't
know
that
all
of
the
suggestions
have
been
merged
in
yet
so
we
might
want
to
wait
for
Georg
to
kind
of
move
this
forward.
I
think
so
you
still
have
time.
If
you
haven't
had
a
chance
to
offer
any
suggestions,
you
can
still
do
that.
A
Here's
I'll
drop
it
in
here
in
the
chat
and
just
for
context
for
anybody
who
missed
it.
This
is
a
new
group
we're
looking
to
form
called
our
Communications
working
group,
which
would
do
these
things
amplify
the
work
that
we're
doing
internally
also
kind
of
amplify
the
work
others
are
doing
with
our
metrics
or
in
this
in
the
metric
space.
D
B
D
B
D
B
A
B
D
D
B
D
A
C
A
Oh
yeah,
yeah
I
think
we
had
it
in
here.
Wait.
A
second
Zoom
is
yeah
I
think
so,
if
you
go
down
to
the
roles
and
the
governance
they
put
in
here,
chaos
Community
manager,
okay
among
other
teams.
If
if
that
I
mean
like
I'm
I'm
fine
with
that
or
if
we
think
it
needs
another
person
in
there,
that's
fine
too,
like
I,
don't
have
strong
feelings
about
it
either
way.
But
I
would
like
to
be
involved.
Uncomfortable.
D
D
A
A
A
F
D
D
It
gets
a
little
hard
to
read,
sometimes
just
overall
the
document
with
all
the
stuff
in
it
and
then
I
would
we
were
looking
particularly
at
the
the
rules
right
here
and
just
talking
about
how
we'll
have
to
we
will
have
to
identify
who
those
people
are
really
before
the
working
group
starts
meeting
so
that
it's
not
just
one
person
or
two
people.
You
know
what
I
mean
absent
of
these
rules
like
if
we're
gonna
want
to
include
them,
then
we
probably
have
to
to
have
people
take
those
on.
F
My
my
headset
just
grabbed
onto
my
hair
piece,
that's
fun
so
kind
of
regarding
the
roll
setup.
I
did
set
up
a
spot
down
below
where
we
put
one
page
descriptions
and
the
idea
of
the
description
is
to
have
one
third
of
the
page,
defining
the
purpose
of
the
roll
one
third
of
the
page,
onboarding
the
individual
into
that
role,
and
then
one
third
of
the
page
allowing
that
individual
to
perform
those
duties
by
attaching
standard
operating
procedures.
So
the
standard
operating
procedure.
B
F
F
A
lot
more
formal
than
what
I
think
chaos
is
going
to
want,
but
I
literally
just
copy
and
pasted
it
from
the
standard
operating
procedures
that
I
used
for
my
clients,
like,
for
instance,
I.
Don't
think
that
we're
going
to
need
to
be
addendums.
We
already
have
the
references
definition
and
with
the
charter,
I
normally
recommend
keeping
this
all
in
one
document
and
actually
publishing
it
as
a
quote:
unquote:
role,
Playbook,
where
people
are
able
to
onboard
on
tools
and
then
attaching
it
to
the
public
guide.
F
But
that
may
not
be
something
that
chaos
wants
to
do
because
you
already
have
in
GitHub
a
very
disparate
and
set
up
structure
of
separate
documents
and
I
I.
Think
we
probably
want
to
go
with
that
design
that
infrastructure
over
the
all-in-one
document
infrastructure
just
to
maintain
continuity
between
the
welcome
book,
yeah.
D
I
mean
I
would
suspect
that
the
the
charter,
like
the
charter-ness
of
it,
would
just
be
part
of
the
readme
file
in
a
GitHub
repository.
So
we
don't
really
have
I
think
the
only
Charter
we
really
have
is
for
the
project
as
a
whole.
But,
like
then
many
of
the
working
groups
have
like
descriptions
of
what
they
do
and
kind
of
how
they
lay
out
their
work,
just
in
the
readme.
So
to
your
point,
Benny
yeah
I
think
it
would
be
distributed
across
a
couple.
Different
documents.
F
B
D
Well
personally,
I
would
I
would
just
like
to
to
kind
of
read
because
there's
been
so
much
work
done
on
it
just
kind
of
read
it
one
more
time.
It's
maybe
not
necessarily
a
review,
but
just
kind
of
read
a
document
that
doesn't
have
like
so
many
edits
and
so
many
comments
on
it
like
those
are
all
like
I'm.
Just
looking
at.
D
D
C
D
C
F
Yeah
and
one
of
the
other
things
that's
really
really
critical
here-
is
for
a
Community
Charter,
it's
important
to
try
and
beg,
but
progress,
small,
just
because
we
have
the
roles
available
on
the
charter
does
not
build
immediately
or
on
time.
This
is
something
that
we
can
establish,
grow
and
scale
as
needed.
B
B
A
D
So
we're
exploring
like
positively
exploring
a
chaos,
Africa
open,
Collective
So.
Currently
the
chaos
project
has
an
open
Collective
account,
but
the
idea
here
is
to
provide
financial
support
for
the
work
that's
occurring
in
Africa.
That
would
be
kind
of
managed
differently
than
than
the
chaos
open.
Collective
account
that
we
have-
and
we've
talked
through
this
a
little
bit
with
with
Ruth
and
I,
did
share
it
too,
with
like
the
finance
team
and
the
chaos
project,
and
that
was
it
was
received
positively.
D
So
I
think
one
of
the
biggest
questions
that
we
have
right
now
and
the
answer
well.
I
know
the
answer
is:
is
there
a
fiscal
host
that
we
could
use
in
Africa?
That's
part
of
open
Collective,
and
the
answer
is
no,
so
we
may
have
to
set
up
chaos
Africa
as
its
own
as
its
own
Collective.
That's
all
and
I
know
that
Ruth
had
reached
out
to
Samson
as
well
just
to
kind
of
find
out
how
open
Collective
is
being
used
for
Oscar.
Another
group
in
Africa.
B
E
I
could
give
updates
on
Dart
the
last
Community,
the
last
Community
she
called.
We
heard
there
was
a
discussion
around
people
having
contributors
working
on
issues
that
are
really
not
good
enough,
just
because
they
want
to
earn
may
be
thus
works,
but
I
was
having
a
discussion
with
Ruth
today's
book
and
in
this
same
document,
I
think
down
there,
though
I
have
not
yet
updated
those
kinds
of
issues
we're
going
to
follow
up.
You
could
just
scroll
down
down
down
down
yep
in
that
section
up.
E
E
Also,
there
is
another
repository
that
supports
the
budging
board,
which
is
the
budging
scripts
that
is
written
totally
in
shell
script,
but
also
it's
part
of
margin
board,
so
our
focus
is
creating
well-curated
issues
that
are
that
are
in
those
three
in
those
are
four
or
five
repositories.
Currently,
almost
all
issues
like
last
time
when
I
made
an
announcement
in
that
in
the
chaosam
general
group.
E
Apart
from
that,
I
think
there
was
also
a
discussion
with
Ruth
about
how
we
could
tap
into
some
contributions
in
the
chaos
organization.
But,
of
course,
a
lot
of
repositories.
There
are
around
metrics
and
also
I
think
are
around
creating
content
that
is
around
metrics.
So
it
was
hard
to
choose
what
kind
of
issues
we
could
actually
vote
for
Oktoberfest
since
I
think
it
worked.
E
It
couldn't
be
enough
for
someone
to
just
hop
into
a
metric
and
then
maybe
make
some
edits
in
the
dock,
and
we
consider
that,
as
as
a
a
under
consider
it
as
a
contribution,
so
yeah
that's
what's
going
on
around
Oktoberfest
and
hopefully,
by
the
end
of
this
week.
Almost
all
issues
that
may
need
to
be
worked
on
will
be
updated
and
up
for
anyone
willing
to
make
the
contribution.
E
D
Do
we
in
the
chaos
project
have
any
like
ability
to
control
hectoberfest
contributions
so
like,
if
somebody
just
shows
up
to
Auger
and
they
issue
a
PR
for
a
for
a
typo
right
as
Enoch
was
kind
of
talking
about,
I
mean,
and
then
you
accept
it.
You
know
what
I
mean
you
merge
it
you're,
like
that's
that's
fair
yeah.
D
C
G
G
E
Yep
I
I
understand
that
there
is
a
ton
for
any
you
could
there
is
a
level
you
can
put
on
any
pull
request
or
on
any
contribution.
That
is
what
they're
recognizing
as
October
1st
and
I.
Think
it's
October
1st
accepted.
That's
like
the
labor
that,
if,
if
a
pull
request
or
if
a
contribution
has
been
accepted,
you
go
on
to
add
another
label
onto
it,
I
think
that
qualifies
it
to
be
accepted
as
as
a
meaningful
contribution
so
far.
E
E
That
right
a
one
or
an
issue
to
be
recognized
as
a
hackable
first
issue.
It
has
to
have
a
level
hack
to
professed
and
then
for
reach
to
be
recognized
as
a
meaningful
contribution
that
was
part
of
October
1st
once
it
is
maybe
merged
or
even
if
it's
not
merged
the
maintainer
just
goes
on
to
add
October
first
accepted
level.
H
B
E
E
E
B
H
B
A
E
A
E
F
B
B
D
D
D
C
We're
not
we're
not
going
out
and
promoting
it,
but
we'll
okay
be
friendly
to
anyone
that
wants
to
contribute
in
the
past
as
xenix
suggested.
Sometimes
when
you
promote
it,
you
end
up
with
a
lot
of
these
really
small
contributions,
which
are
you
know
it
could
be
good,
but
typo
correction
is
not.
You
know
something
that
we
did
get
a
lot
of.
That
I
mean
that's,
not
yes,
that's
grounded
in
reality,.
C
D
Maybe
like
I'm
thinking
Elizabeth
like
are
messaging
out
to
like
slack
or
to
on
Twitter
like
if
you
want
to
participate
in
Oktoberfest
with
chaos
and
I.
Think
Ruth
has
been
putting
this
out
too
on
chaos.
Africa
like
these
are
the
these
are
the
areas
that
we
would
love
for
you
to
work,
these
being
the
ones
I'm
pointing
to
that.
You
can't
see
the
slack
bot,
the
bot,
the
badging
bot,
the
badging
design
and
badging
website.
D
D
E
Affairs
was
majorly
to
get
most
of
the
our
folks
in
Africa
participating
or
having
something
to
work
on
as
they
join
the
community
active
lease
or
most
of
the
motivation
came
from
that,
and
given
the
fact
that
these
for
repositories
at
least
I
was
mostly
active
on
them
and
I
volunteered
to
be
so
much
available,
it
was.
It
was
okay
with
us
going
forward
with
having
contributions
towards
okay,
okay,.
B
A
B
D
This
is
it's
just
a
thought.
I
felt
like
you
know,
because
I
was
looking
at
the
newsletter
you
had
and
I
know
that
we
don't
have
an
official
release
like
in
October
and
I.
Don't
know
if
that's
I
don't
know.
I
have
just
like
a
variety
of
thoughts
here
like
so
like
really
like
editing
a
metric
like
just
revisiting.
D
That's
all
good,
but
I
find
even
like
I,
find
myself
like
I
feel,
like
I'm
85,
confident
in
the
process,
and
then,
if
a
different
working
group
is
also
85,
confident
and
then
all
of
our
working
groups,
all
five
of
them
are
85
like
it
just
doesn't
add
up
real
well
and
I
feel
like
the
process
has
some
gaps
in
it.
Sometimes
and
but
anyway,
that's
just
I,
don't
know
what
other
people
are
thinking
about.
D
H
H
In
the
past,
Kevin
and
Kirk
have
been
looking
into
it
and
then
for
last,
two
releases
have
been
actively
participating,
but
not
as
an
official
release,
manager
or
something
but
like
for
diff,
because
I
attend
many
of
the
working
groups
and
I
go
through
that
process
of
looking
into
the
list
that
everything
is
in
order
to
go
through
it.
Okay,
but
like
to
be
honest.
Taking
this
role
is
a
big
challenge,
a
big
awesome.
It.
D
G
G
Since
we
started
doing
these
metrics
releases
I
made
an
effort
to
go
to
as
many
working
groups
as
I
could
I
helped
to
define
the
process
for
the
release
and
and
then,
when
the,
when
the
releases
would
come
up,
I
would
visit
the
working
groups
to
help
walk
them
through
the
process.
Yeah,
so
I,
don't
think
the
the
positions
never
been
formalized
but
I
would
say.
I've
been
I've
been
doing
that
in
the
past.
G
G
Take
it
that
way
so
yeah
I
can
to
to
vanad's
point.
I
can
speak
to
how
difficult
this
is
because
it
does
involve
visiting
every
working
group
and
being
aware
of
of
all
of
the
metrics
I.
Think
because
of
this
work,
I
think
some
of
the
some
of
the
issues
with
the
kind
of
revisiting
the
metrics
we
identified
some
of
those
issues
and
we've
we've
identified
several
other
issues
that
have
kind
of
that.
G
We're
kind
of
working
towards
to
help
kind
of
put
all
the
working
groups
on
the
same
page.
But
it
is
a
it's
a
a
pretty
it's
a
big
ask
to
to
to
maintain
that
rule
all
the
way
through,
because
it
is
a
you
go.
You
have
to
go
to
all
the
meetings.
So
it's
it
really
is
something
it's
not
it's
not
that
we'd
want
One
release
manager,
I,
I,
really
think
this
is
something
where
we
need
more
than
one.
H
That's
what
I
was
also
proposing
that
we
should
just
split
it
into
two
percent,
so
that
like
because
it's
a
big
ask
going
through
each
metric
takes
a
lot
of
time
and
yeah,
if
maybe
a
splitting
into.
If
we
have
four
or
five
working
groups,
we
can
split
into
two
percent
in
this
way,
like
I
I.
Don't
want
all
the
burden
on
the
cave
and
to
take
care
of
all
these
things
yep.
So.
D
G
So
I
know-
informally,
we've
mentioned
this
a
couple
times
in
in
a
few
of
the
meetings,
but
there
is
kind
of
the
thought
that,
with
the
knowledge
base
in
place
and
presenting
presenting
our
metrics
and
models
in
this
in
this
this
searchable
way,
maybe
we
maybe
we
can
lighten
up
on
the
that
standard,
metrics
release
right
where
we're.
Currently,
we
do
two
official
metrics
releases
a
year,
and
then
we
also
have
the
The
Continuous
metrics
release
process.
G
So
we've
been
kind
of
tossing
around
the
idea
of
actually
getting
rid
of
the
getting
rid
of
the
official
metrics
releases
with
the
PDF
and
just
doing
the
continuous
metrics
release
process
which
would
publish
those
metrics
directly
to
the
knowledge
base,
I
like
that
which
which
would
make
the
process
more
manageable.
But
but
there
is
still
we
we
would
still
have
to
go
through
the
continuous
release
process
and
then
I
do
I.
G
Do
also
think
there
is
value
in
having
in
having
a
couple
people
as
the
release
managers
just
because
they,
you
know
the
the
metrics
are
one
of
the
the
main
deliverables
that
this
project
creates
and
having
consistency
in
the
way
that
they're
kind
of
defined
and
presented.
The
terminology
we
use
I
think
is
really
important
so
that
that
the
the
release
manager
role
can
really
act
as
a
almost
like.
B
H
H
I
I
felt
that
was
a
booster
for
a
lot
of
working
groups
like
they
were
very
slow
in
the
during
six
months
time,
but
when
there's
a
release
time
coming,
they
started
pushing
more
metrics.
So
removing
that
release
cycle
and
having
continuous
release
was
I.
I,
don't
know,
maybe
make
working
groups
a
little
lazy
or
foreign.
G
C
G
What
happened
yeah
and
additionally,
even
though
even
though
reviews
can
occur
during
the
continuous
release
process,
the
only
time
we
ever
get
any
real
action
on
the
reviews.
Community
reviews
of
the
metrics
is
during
that
that
review
period,
where
we,
where
we'd,
make
a
point
of
telling
everyone
to
go
and
review
so
so
there
is,
there
is
definitely
value
in
in
in
having
that
that
fork
forcing
function,
slash,
release
date.
G
So
that's
something
to
it's
something:
to
consider
and
I
think
to
to
what
I
said
earlier.
That's
just
something:
we've
been
we've
been
contemplating,
so
it's
not
something
that
we're
planning
or
it's
just
kind
of
things.
We've
been
talking
about
to
make
the
process
easier.
So
maybe
maybe
the
answer
is
we.
We
keep
the
two
release
dates.
Maybe
we
go
down
to
One
release
date
a
year
that
work,
I,
I.
D
G
Yes,
that's
the
yeah,
that's
the
other
part
of
that
conversation
is
we've.
We've
added
translation
to
the
website
and
if
our
primary,
if
our
primary
way
of
presenting
the
metrics
is
through
the
knowledge
base,
then
we're
gonna
have
we're
gonna
have
that
that
kind
of
automatic
translation
through
the
website.
So
there
there
are
some
quality
control
issues.
G
So
one
of
the
proposals
that
I
was
I
was
going
to
have
kind
of
moving
forward
after
the
website.
Redesign
was
to
maybe
see
if
we
could,
rather
than
having
the
translation
teams
working
on
translating
these
whole
documents
for
the
PDF
release.
If
we
could
have
the
translation
teams,
take
a
look
at
the
knowledge
base
pages
and
make
sure
that
the
the
documents
are
translating
properly
there
yeah
and
then
we
can
edit
them,
but
but
once
again
that's
just
something:
we've
been
we've
started
to
contemplate.
G
G
If
people
who
speak
two
or
three
languages
could
maybe
take
a
peek,
and
let
us
know
if
the
if
it's
working,
okay,
I
know
the
Asia
Pacific
group
has
has
looked
at
it
a
little
bit
and
they've
recommended
some
some
changes
or
some
some
edits,
but
we
do
have,
and
and
also
if
there
are
any
languages
that
we
need
to
add
to
the
website.
We
can
do
that
as
well.
G
A
Fantastic
any
other
questions
or
comments,
because
we
are
right
at
time,
so
good
timing
really
be
quickly
before
we
go.
I
I
put
this
on
the
thing
and
then
I
deleted
it
because
I
thought.
Oh,
it's
already
happened,
but
it
actually
has
not
happened
so
I'm,
I'm,
dumb
I,
don't
know
how
calendars
work.
So
thank
you
for
putting
it
back
on
whoever.