►
From YouTube: CHAOSS Weekly Community Call August 16, 2022
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Okay,
hey
everybody:
it's
tuesday,
alma
said
wednesdays,
tuesday
august
16th
and
you're
at
the
weekly
community
call
for
chaos
happy
to
see
everybody's
faces.
You
all
look
awesome
and
we're
really
happy
that
you're
here,
let
me
find
the
share
screen
there.
We
go.
A
A
B
Oh,
I
have
to
okay,
you
just
go
ahead
and
start.
We
can
all
look
at
the
minutes
because
I
have
to
do
something
in
system
preferences.
A
Yeah,
okay,
so
everybody
you
have
a
link
to
the
minutes,
but
we
will
put
them
in
the
meeting
chat
in
case.
You
need
them
as
always
feel
free
to
add
your
name
if
you
want,
if
you
don't
want
to
you,
don't
have
to
that's
fine
first
item
on
the
agenda.
A
Is
that
the
community
handbook,
folks
that
are
working
on
that
ruth
and
shoya
they're,
looking
for
further
review
of
the
folder
structure,
so
I
guess
we're
trying
to
sort
out
how
people
can
navigate
through
the
community
handbook-
and
there
is
an
issue
here.
Let's
just
link
to
that
in
the
chat
here
and
we'll
see.
B
A
Yes,
so
anyway,
there
is
this
issue
that
shoya
has
opened
in
the
community
repo,
and
I
linked
to
it
in
the
in
the
chat
here.
If
we
can
take
a
look
at
that
and
see
kind
of
what
is
what's
going
on
here,
it
looks
like
the
way
that
we
currently
have
the
docs
structured
might
not
be
the
best
way
for
navigation.
A
D
A
A
Yep
yep
we're
just
looking
at
this
this
issue
that
shoya
opened
as
a
request
at
a
request
from
her
and
ruth
to
get
some
feedback
on
the
community
on
maybe
ideas
about
how
we
can
better
structure
this,
to
make
it
easier
to
navigate.
D
So
I
I
should
point
out
on
this
list
the
the
stuff
that's
in
the
parentheses.
Next
to
the
title,
for
example,
how
work
is
done
these
are.
These
are
notes
that
I've
kind
of
dropped
in
because
they
they
relate
to
how
we
are
going
to
kind
of
pull
information
out
of
the
the
community
handbooks
up
into
the
website,
right
so
from
from
the
the
website
knowledge
base
perspective,
we've
kind
of
we've
got
these
three.
D
D
And
then
various
other
pages,
maybe
so
so
that
that's
why
those
parentheses
are
there,
so
you
can
ignore
them
as
far
as
the
the
the
structure
of
the
actual
community
handbooks.
B
D
Yeah,
we're
not
really
not
really
part
participation
isn't
the
best
word
for
for
like
the
for
newcomers.
It
is
the
guide
to
yeah
how
to
contribute
new
participation,
but
then
the
the
other
two
paths
are
really
more
about
kind
of
sorting
the
types
of
information
that
different
types
of
participants
may
need.
Okay,
right.
B
D
Yes,
yeah
yeah,
actually,
the
yeah
they're.
As
far
as
the
knowledge
base
is
concerned,
both
of
those
areas
would
probably
be
pulled
into
the
same
knowledge
base.
Okay,
so
the
working
groups
and
governance
are
yeah.
It's
basically
yeah,
okay,
how
we
work
or
how
work
is
done.
D
D
Messages
we
send
out
externally.
These
are
just
these.
Are
these
are
broadcast
channels
that
that
chaos
uses
to
to
publish
information
right?
So,
as
far
as
this
section
is
go,
goes,
there's
probably
not
going
to
be
a
whole
lot
of
content
in
here
other
than
kind
of
just
brief
descriptions
of
what
those
are
from
a
knowledge-based
standpoint,
the
messages
we
send
out
in
externally.
D
D
B
C
B
D
Yeah,
so
the
three
points
are
metrics
models,
how
we
work
and
newcomers.
D
Okay,
I
am
fine
with
the
having
it
explicitly
as
as
community
resources,
though,
as
well
kind
of
out
from
that,
from
a
knowledge
voice
based
standpoint.
We
can
pick
and
choose
what
we're
pulling
in,
so
the
structure
doesn't
have
to
match
one
to
one.
B
D
Wonder
from
just
the
way
it's
structured,
if
templates
would
be,
it
would
be
harder
to
find
if
it
was
moved
into
that
those
howie
categories
rather
than
having
its
own.
You
know
bucket
for
community
resources,
okay
right
and
I'm
not
I'm
not
sure.
Community
resources
is
the
the
perfect
header
for
this
one.
Okay,
but
I
do
think
there's
there's
value
in
keeping
it
separate
from
the
it
having
its
own
section.
Okay,.
A
D
However,
where
we
can,
we
will
we'll
first
look
to
the
community
handbook
to
see
if
that
documentation
is
created
and
if
it
is
we'll
try
to
use
it.
That
way.
We
have
these
likes
as
we've
discussed
prior
the
the
the
single
points
of
truth
right.
A
D
So
so,
for
a
lot
of
the
stuff
in
the
community
handbook,
we
will
well
for
the
knowledge
base.
All
of
it
will
be
pulled
from
the
community
handbook,
but
there
are
other
parts
of
the
website
where
we
will
also
pull
from
the
community
handbook,
for
example,
mission
statements,
project
charters.
D
D
So
it's
it's
not,
I
don't
think
it'll
be
one-to-one
there.
There
will
be
times
when
we
need
to
create
things
specifically
in
the
website
repo.
However,
I
think
our
kind
of
default.
A
B
I
was
just
wondering
just
listening
to
kevin
talk
if
we
had
like
on
those
panels
again,
I'm
thinking
of
the
webpage,
those
the
newcomers
the
base.
You
know
how
to
participate
like
if
you're,
a
community
member
and
then
metrics
models
as
a
top
level
category
totally
fine.
Should
we
have
something
in
the
handbook
that
points
people
to
metrics
and
metrics
models
in
some
way,
because.
D
D
D
Okay,
because
that
information
already
exists
in
the
working
groups,
repositories
and
it's
and
from
a
website
perspective.
It's
it's
not
a
problem
for
us
to
pull
that
information
from
the
the
the
working
groups
individually.
Okay,.
B
C
D
We
were
to
if
we
were
to
duplicate
it
here.
I
would
worry
about.
You
know,
problems
with
replication.
You
know
that
that
that
would
exist
right
they'll.
The
version
versioning
could
be
weird
so.
A
But
kevin
will
the
knowledge
base
then
be
able
to
still
pull
from
the
metrics
like?
Is
it
also
pulling
stuff
from
the
website
and
the
repos
and
everything?
In
addition,.
D
D
The
knowledge
that
we
can
point,
we
can
point
individual
knowledge,
base
topics
and
knowledge-based
pages
to
whatever
repo
we
would
like.
So
it's
a.
A
D
It's
a
little
bit
of
a
kind
of
a
grab
bag
for
us
right,
so
we
can.
We
can
grab
the
information
from
where
we
need
it
for
the
for
the
community
handbook
stuff
this
that
that
single
point
that
single
point
where,
where
everything
exists,
it
would
be,
we
think,
there's
a
lot
of
value
in
having
it
in
the
handbook,
rather
than
spread
out
in
a
bunch
of
other
places,
but
the
the
metrics
and
models
those
those
kind
of
belong
to
the
working
groups.
A
So
kevin,
it
seems
like
you
kind
of
like
the
idea
of
lumpy
some
of
these
some
of
these
topics
here
into
those
buckets
about
how
work
is
done,
and
then
newcomers
is
that,
would
that
be
fair
statement.
D
I
I
do,
but
it's
also
it's
not
completely
necessary.
I
suppose
I
mean
I'd
like
content
to
be
organized
contents
that
that's
similar
I'd
like
to
be
organized,
but
I
think
the
comment
that
I
had
made
to.
D
To
that
to
that
team
was
that
I,
this
this
structure
should
kind
of
be
like
a
table
of
contents
in
a
in
a
book
and
a
table
of
contents.
Also
kind
of
it
lays
out
a
story,
and
then
the
story
for
us
is
kind
of
the
it's
the
story
of
of
of
of
how
to
contribute
and
how
we
do
work
right.
So
when
we,
if
we,
if
we
look
at
the
the
structure
of
these
files,
it
should
be,
it
should
kind
of
create
an
explicit
pathway.
D
D
D
A
D
We
will
be
polling,
we'll
be
polling
topic
areas
by
folder
right,
so
how,
in
so
in
this
example,
governance
would
be
a
topic
area
in
our
knowledge
base.
A
D
Yes,
yeah,
I
agree,
and
the
and
the
naming
convention
for
the
folders
needs
to
be
needs
to
be
pretty
explicit,
because
the
the
the
name
of
these
folders
will
also
be
topic.
Areas
in
the
knowledge
base
right,
so
governance
is
a
topic
area
and
it'll
be
a
searchable
topic
area
in
the
knowledge
base.
B
D
Explicit,
I
would
like
it
to
be
more
explicit
than
it
is,
but
I
don't
think
it
needs
to
be
as
explicit
as
you
just
described
so
somewhere
in
between
yeah
and
that
the
and
one
comment
I
would
have
about
governance
currently
is,
I
don't
think
slack
mailing
list
and
zoom
meetings
belong
in
the
governance
folder.
I
think
those
probably
belong
up
in
the
how
we
work
in
one
of
the
howie
works
in
the
upper
one.
Probably.
A
I
agree
with
that,
and
also
I
wanted
to
just
add
that
I'm
not
sure
how
we
can
integrate
like
historically,
where
docs
are
so,
for
instance,
the
data
use
document
is
was
like
it
made
more
sense
to
go
into
governance,
but
because
it's
already
linked
in
every
single
metric
to
a
hard
link
when
they
moved
that
it
broke
everything.
So
we
had
to
just
keep
it
at
that
high
level
for
now,
but
it
was
like
it
doesn't
really
fit
in
with
this
new
structure.
So
I'm
not
sure
how
to
am
I
making
sense.
D
A
Would
it
be
easier
for
ruth
and
shoya
to
kind
of
just
do
what
they
think
is
best
and
then
bring
that
back
to
the
community
for
our
feedback
instead
of
us
trying
to
sort
this
out?
What
would
be
the
easiest
to
move
forward.
D
I
think
it
is
a
little
bit
of
a
complex
problem
for
them,
which
is
why
I
think
they're
trying
to
get
some
feedback
from
us
on
it.
D
A
D
I
so
I
should
say
that
those
those
high-level
buckets
would
do
include.
They
include
multiple
folders
from
the
from
the
community
handbook
all
right.
So
I'm
I'm
not
suggesting
that
that
how
we
work
is
one
folder
and
we
put
everything
in
it
because
there'd
be
a
bunch
of
stuff.
That
would
be.
That
would
be
in
that
in
the
repo
on
the
website.
D
So
how
we,
how
work
is
done
is
I
I
think
it's
a
it.
It
describes
the
information
that's
in
there,
which
I
do
think
is
important
right.
So
we
have
there's
there's
different
information
in
each
of
these
different
kind
of
folders,
and
some
of
it
describes
how
we
do
work.
Some
of
it
describes
our
output,
some
of
it
describes
the
history
and
and
mixing
and
matching
that
different
type
of
content.
D
D
The
the
chaos
working
groups
folder
is
going
to
explicitly
tell
them,
whereas
if
they
were
to,
if
they
were
to
look
in
the
the
history
section
or
the
about
chaos,
they're
going
to
see
history
about
working
groups,
but
not
necessarily
how
to
actually
work
within
a
working
group
right,
so
the
that
could
be
a
confusing
path
for
them.
D
So
separating
out
the
separating
out
that
different
types
of
content,
I
think
is-
is
helpful
for
a
user
when
they,
when
they
land
on
these
pages,
and
then
it
goes
back
to
the
just
the
explicit
naming
right.
So
we
know
we
know
very
explicitly
that
this
is.
This
is
how
to
work
in
working
groups
or
how
to
contribute.
D
And
community
initiatives
are
these:
are
these
are
programs
or
projects
that
where
chaos
is
creating
something
right
and
and
when
we
go
down
to
the
chaos
median
outreach?
These
are.
This
is
not.
This
is
not
about
slack
or
the
mailing
list
or
zoom,
because
those
tools
are
used
to
to
actually
coordinate
and
do
work,
chaos,
media
and
outreach.
This
is
these
are
broadcast
channels
where
we're
we're
sending
out
information.
A
I
was
just
going
to
say:
would
it
be
helpful
if
maybe
as
homework,
we
ask
people
to
give
us
examples
of
community
handbooks
that
they
really
like
for
communities
that
they
have
joined
or
that
there
are
other
communities
that
they're
part
of
just?
So
we
can
kind
of
visualize
like
what
that.
What
what
may
be
a
good
example
would
be
because
it's
it
is
hard,
I'm
kind
of
with
sophia,
like
it's
really
hard
for
me
to
visualize
like
what
the
best
way
to
do.
A
D
A
A
A
We
have
about
20
minutes
left
roughly,
not
quite
so
is
it
okay?
If
we
move
on
with
that
action
item
in
place,.
A
Because
that's
what
we're
gonna
do
so
here
we
go
all
right.
The
next
item
on
here
thanks
everybody
for
your
your
your
eyes
on
that
appreciate
that
very
much.
A
The
next
item
is
that
as
part
of
outreachy,
one
of
so
like
every
week,
there
are
assignments
from
outreachy
to
the
mentors
and
mentees,
and
this
week's
assignment
might
have
been
last
week's
assignment
is
for
the
outreachy
mentee
to
do
a
couple
of
informal
chats
with
people
who
are
working
in
open
source
just
to
get
an
idea
of
like
how,
like
other
options
for
careers-
and
you
know
just
some
general
advice
about
like
how
to
how
to
participate
in
open
source
later
on
and
just
how
to
build
your
career
in
open
source.
A
So
if
there's
anybody
that
would
be
interested
precious
is
our
outreaching
mentor
for
the
auger
project,
and
so
there's
anybody
out
there
and
like
we
can't
do
that
with
her.
That's
part
of
the
rules
is
like
her
mentors
can't
be
that
informal
chat.
So
we
would
love
volunteers
in
the
community
that
would
be
willing
to
chat
with
precious
just
about
kind
of
how
their
career
has
gone
and-
and
you
know
just
an
informal
chat.
A
A
So
I
won't
put
anybody
on
the
spot
if
that
is
something
that
you're
interested
in
doing
connect
with
me
or
sean
and
we'll
connect
you
with
questions.
You
know
I
can
set
up
a
time
that
works
for
you
guys
not
a
big
deal.
C
C
Anyway,
I'll
see,
if
I
can,
I
may
have
some
availability
today,
if
she's
available
as
well,
and
if
other
people
are
willing
to
join
I'm
available.
A
Yeah
she
she's
also
on
slack,
if
it's
easier
for
you
to
reach
out
to
her
directly
she's
precious,
oh
on.
C
C
A
Anybody
else
too,
if
it's
easier,
just
for
you
to
reach
out
straight
to
her
feel
free
to
do
that.
She's
also
in
the
dei
working
group,
you'll
see
her
around
a
few
different
places.
So
yep
you'll
see
her
in
slack.
A
The
next
item
on
our
agenda
comes
from
the
dei
working
group,
as
a
part
of
you
know,
working
group
stuff
that
you
do.
You
go
through
old
issues
and
prs
and
whatnot,
and
one
of
the
open
issues
in
the
dei
working
group,
as
this
inclusive
naming
initiative,
just
kind
of
building
that
connection
with
that
group
and
us,
and
if
you're
not
familiar
with
them,
they're
another
open
source
project.
That
is
a
part
of
the
linux
foundation
and
they
aim
to
remove
non-inclusive
language
from
open
source
documentation
code
wherever
it
might
show
up.
A
They
maintain
a
list
of
kind
of
like
borderline
offensive.
Some
are
outwardly
offensive
terms
that
can
easily
just
be
changed
and
we
can
all
kind
of
move
our
or,
I
should
say,
evolve
our
language
to
be
more
inclusive
of
everyone.
So
it's
a
great
project
and
I'm
just
a
lurker
in
their
slack.
A
So
in
the
dei
working
group
we
just
weren't
sure
of
like
is
there
someone
that
is
super
interested
in
this?
That
wants
to
take
it
on
as
as
just
something
that
they,
you
know,
is
as
a
passion
project
for
them
just
to
kind
of
be
more
involved
in
that
group
and
chaos
and
build
help
build
that
bridge,
or
should
we
have
it
as
a
separate
internship
program?
A
A
B
A
They
have
a
lot
of
different
depending
on
like
what
you
want
to
be
involved
in,
because
I
think
they're,
so
they
not
only
do
they
kind
of
develop
these
lists
of
things
that
maybe
could
be
worded
differently,
but
they
also
are
working
on
some
software
that
will
be
act
as
a
linter
to
help
you
just
run
through.
You
know
just
run
your
project
through
it
and
it
will
identify,
maybe
even
replace
for
you.
A
So
I
think
that
software
is
a
encode
is
a
piece
of
their
work
as
well,
and
then
I
think
they,
you
know,
try
to
also
educate
people.
So
it's
it's
very
similar
to
kind
of
what
we
do.
You
know
there's
there's
like
those
kind
of
three
areas.
D
B
I
mean
I
would
say,
if
somebody's
interested,
you
know,
maybe
a
good
first
step,
and
this
would
be
just
participating
in
one
or
two
of
the
inclusive
naming
initiative
meetings
that
they
have
and
then
kind
of
bringing
back
what
you
learned
to
the
chaos
dei
working
group
like
you,
know,
yeah
not
necessarily
doing
any
work
in
either
of
them,
but
just
trying
to
build
the
build
the
relationship
between
them.
Just
you
know,
that's
it.
So
I
think
it'd
be
a
pretty
straightforward
connection.
B
A
I
think
even
too,
you
could
also
just
join
their
slack
and
just
kind
of
get
a
feel
for
the
community
and
see
if
it's
something
that
you
want
to
maybe
participate
in
more
or
you
know
kind
of
move
forward
with
it.
And
if
it's
not
that's
fine
too,
but
it
is
a
great
group
of
people.
So
I
just
personally,
I
think
this
is
a
really
important
thing.
I
just
don't
have
the
time
to
participate
in
the
way
that
I
should
so
I.
B
Think
something
similar
would
be
kind
of
like
how
we
have
a
lot
of
folks
in
the
chaos
community,
for
example,
connected
with
the
to
do
group.
So
it's
not
like
we're
all
necessarily
participating
in
the
to
do
group
or
anything
like
that.
But
it's
it's
nice
to
hear
what
is
going
on
in
the
to
do.
Group.
C
C
We
know
like
open
source
with
inherited
code
that
we're
writing
from
name
with
naming
conversion
type
of
functions.
For
example,
you
go
to
most
code
basis,
proprietary
or
cs.q,
dot,
destroy
those
kind
of
methods
that
they
were
calling
functions
and
things
that
were
very
aggressive.
C
C
Does
it
really
have
that
inclusive
inclusivity
or
whatever
we
may
want
to
worry
about
at
that
moment,
then
once
people
are
coming
in
from
documentation
or
they
want
to
read
your
comment
and
as
times
goes
on,
this
kind
of
problem
is
addressed
from
the
code
base.
It's
solid
but
naming
only
the
documentations
without
thinking
about
code
base.
So
I
know
it's
challenging
to
reverse
engineering
and
start
by
naming
things,
but
then
we
should
start
thinking
up
front
when
we
are
writing
especially
piece
of
code
think
about
naming
variables
properly
and
functions.
A
Yeah,
I
totally
agree
armstrong.
Thank
you
for
bringing
that
up.
I
yeah.
I
think
that
that
is
a
part
of
what
they
care
about
as
well.
Is
it's
not
just
documentation
but
deep
in
the
code
you
know
and
just
kind
of
how
we
think
and
how
we
approach
problems
and
the
way
we
communicate
with
each
other
in
general,
so
yeah,
it's
a
great
group.
I
did
notice
that
their
website
is
down,
so
maybe
they
need
help
with
the
website.
I
don't
know
I'm
just
guessing
they
might.
A
I
don't
know,
but
I'm
sure
that's
a
working
group.
You
could
join
so
so
that
being
said,
the
last
thing
on
the
agenda
is
chaos
con
and
it
looks
like
somebody
has
a
question
for
chaos,
con
committee
and
we're
looking
for
pictures
and
bios
of
the
speakers.