►
From YouTube: CHAOSS Knowledgebase Audit Meeting July 26, 2023
Description
Meeting minutes are here: https://docs.google.com/document/d/1p079Q75RZ2Duk-nX4osXY2v3oFjqF6-BTZG6XPx8iQ4/edit
A
B
A
A
A
B
A
B
A
C
A
A
B
A
B
B
B
A
A
D
A
D
B
A
A
B
A
B
A
D
A
Here
is
scroll
it
out.
These
are
the
documents
that
we
have
Community
guidelines,
which
is
like
adhere
to
the
community
rules
and
regulations.
Things
like
these
metrics
dco
setup,
which
is
how
to
set
up
your
dco
thing
and
content
contribution,
which
is
mostly
on
the
Block
contribution,
and
what
we
discussed
was
like,
making
a
new
thing
that
how
to
contribute
to
the
website
how
to
contribute
to
the
different
working
groups.
Things
like
this,
so
if
you
so
most
of
these
things
will
be
deleted.
In
that
scenario,.
B
A
A
B
Like
in
the
last
in
the
last
meeting,
we
had
proposed
identifying
some
documents
that
need
to
be
created,
yes
and
then
maybe
having
a
conversation
about
how
those
documents
would
be
created.
If
we
could
ask
for
volunteers
from
working
groups
or
ask
we're
working
them
ourselves,
all
right,
so
to
be
clear
for
the
for
the
how
to
contribute
vulgar.
B
What
the
nod
is
talking
about
is
creating
very
explicit
how
to
contribute
documents
for
specific
tasks,
yes,
which
we
do
not
have
currently
other
than
for
the
dco
setup
and
the
is
it
the
Vlog
or
the
I'm.
Sorry,
the
I
keep
on
it's.
It's
not
on
the
spreadsheet
there,
so
I
keep
on
missing
it.
Just
the
podcast.
A
B
A
A
A
D
When
we
are
asking
for
how
to
contribute
to
the
chaos
project,
who
is
this
for?
Is
it
for
newcomers?
Because
if
it
is
for
newcomers,
we
have
a
proposed
quick
start
for
newcomers?
We
do
have
that
if
it's
how
to
contribute
for
existing
members,
so,
let's
say
you're
an
existing
member
and
you'd
like
to
participate
in
the
podcast
like.
Is
it
because
that's
a
different
person
so.
B
I
would
say
it's
both
of
those
people
I
think
it's.
This
is.
This
would
be
about
documenting,
documenting
our
processes
for
processes
that
need
to
be
documented,
for
example,
and
I
know
so
that
I
know
we're
not
doing
a
metrics
review
now,
but
if
we
were
doing
a
metrics
review,
it's
very.
It
would
be
very
helpful
to
have
that
process
documented
if
we
are
currently
working
on
the
website.
There
are
some
things
that
new
contributors
and
and
core
contributors
may
not
know
about
how
to
contribute
to
the
website.
B
Yes,
so
there
are,
there
are
processes
that
we
we
have
for
doing
specific
things
on
WordPress
and
there
are
processes
that
we
have
for
doing
things
in
the
GitHub
repo
that
would
get
pulled
into
the
into
WordPress.
So
I
think
all
of
the
all
of
the
working
groups
kind
of
have
processes
for
what
they
do,
the
the
way
that
we
Define
metrics.
B
A
B
B
D
Overall
I
have
concerns
about
making
documents
that
are
really
specific,
because
maintaining
them
is
going
to
be
almost
impossible.
I
would
suggest
we
have
subtle
shifts
in
the
way.
We
do
work
all
the
time,
okay
and
then
always
working
to
track
that
down.
Like
the
list
that
you
were
mentioning,
Kevin
I
mean
I
agree.
D
We
have
processes
for
all
those
things,
but
keeping
all
of
those
square
like
we
could
do
one
giant
push
saying:
can
you
all
Define
your
processes
and
then
six
months
later,
we'd
have
to
my
guess
is
probably
do
the
whole
same
thing
again
right
and
so
and
then
I'm
also
with
you
Kevin
like
providing
like
just
high
level
things.
That's
not
helpful
either
like
so
you
know,
I
struggle
with
the
the
really
detail
is
challenging
just
because
I
think
it's
going
to
unravel
pretty
quickly
and
we
can't
maintain
it.
C
C
C
B
B
B
D
I
would
prefer
to
say,
if
you're
interested
in
how
these
work,
we
encourage
you
to
join
these
groups
and
here's
how
to
join
those
groups
and
once
you're
in
those
groups,
they
will
talk
about
the
processes
by
which
they
work.
My
concern
is
is
that
if
we
try
to
maintain
the
slackbot
processes
on
here,
it
will
change
slightly
and
they
will
begin
to
delay
and
we'll
have
to
continue
to
bring
them
together.
So
on
the
website
we
tell
people
how
to
get
to
those
processes
and
how
to
find
them,
but
we
don't
maintain
them
here.
D
D
B
B
But
that's
connected
to
what
I
was
what
I
had
said
earlier,
where
we
figure
out
figure
out
what
documents
are
needed
and
who
would
create
them
and
maybe
reach
out
to
the
working
groups
or
software
groups
to
have
those
done
so
I
think
that
would
still
hold
up.
It
would
just
be
a
matter
of
them
hosting
those
documents
themselves
and
that's
just
pointing
to
them.
D
B
D
C
B
The
folder
yeah
so
does
the
folder
go
away
and
is
it
replaced
with
a
one-pager
that
gives
you
the
the
links
to
to
all
of
these
relevant
how
to
contribute
documents,
if
that's
the
case,
maybe
the
so
the
folder
goes
away
and
we
create
one
document
that
it's
a
one-pager
or
a
two-pager
that
points
to
all
these
different
places.
Where
would
that
document
exist
in
our
current
knowledge
base.
A
D
And
I,
don't
think
the
my
suggestion
is
the
pointer
here
in
how
to
contribute
is
not
to
their
contribution
documents.
It's
to
the
group.
You
want
to
participate
with.
Okay
once
you're
there,
they
will
talk
about
how
to
contribute.
That's
my
suggestion,
and
if
they
have
a
contribution
document
it
can
be.
You
can
ask
for
it.
In
the
first
meeting
right,
okay,.
B
D
A
B
A
B
A
B
Would
say,
based
on
this
discussion
and
if
you
agree
with
me,
two
documents
that
we
know
exist
in
how
to
contribute
would
be
that
one
page
document
that
points
to
points
to
different,
documented
processes:
okay
and
then
the
other
one-
would
be
any
new
contributor
documentation.
That's
been
created
recently,
like
the
quick
start
for
newcomers.
C
A
C
A
A
C
B
A
B
D
D
B
A
C
C
B
A
D
B
B
B
D
So
I'll,
just
I
was
just
thinking
while
I
was
trying
to
help
my
dog,
but
there
seems
to
be
contributor
paths.
I,
don't
know
if
this
is
right
and
contributor
documents
and
and
I
I
know
that
they're
kind
of
intertwined
I'm
sure
but
like
I,
feel
like
at
the
website
at
this
level
here
we're
just
trying
to
set
paths
for
people
like
right.
D
Here's
the
path
to
go
down
and
it'll
ultimately
connect
with
another
path
like
the
auger
path
of
how
to
contribute
or
the
grimor
lab
path
of
how
to
contribute
or
the
Dei
badging
or
you
get
the
whole
idea
like
we.
We
can't
I,
don't
think
that
we
should
attend
to
all
those
paths
here
at
this
level
we
just
kind
of
that
high
level
path
to
point
people
to
the
other
pass,
but
that
it
does
make
me
think
like.
D
B
B
Goes
back
to
what
I
was
saying
at
the
beginning.
We
need
to.
We
need
to
identify
key
or
critical
documents
that
need
to
be
created,
and
we
need
to
then
reach
out
to
those
people
and
and
see
if
we
can
get
those
documents
made.
So
even
if
they're
not
being
housed
in
the
knowledge
base
itself,
the
those
the
documentation
for
chaos
and
the
documentation
of
our
of
our
processes
and
the
documentation
of
the
software
it
needs
to
it
needs
to
exist,
and
we
need
to
point
to
it
explicitly.
Yeah.
D
That's
the
path
they
have
and
the
way
that
Enoch
may
want
to
do
it
with
the
badging
bot
totally
different.
You
know,
we
might
say
the
path
to
contribution
is
attending
meetings
every
every
week.
That's
our
path,
that's
the
way
we
work
and
I
know
nobody's
suggesting
to
standardize
that,
but
it's
just
that
we
can
hand
it
off
to
somebody.
C
B
D
C
B
D
D
B
B
A
So
my
question
then,
is
like:
if
we
have
now
two
things,
one
is
direct
within
the
community
how
to
contribute
and
then
a
main
link,
how
to
contribute
within
the
community
link
in
on
the
website.
So
should
we
keep
two
separate
pointers
on
the
same
thing,
if
you
just
click
to
the
community,
we
have
quick
start
for
new
contributors
and
then
in
the
knowledge
base,
we
have
a
how
to
contribute.
A
A
A
B
Know
one
of
them
will
be:
one
of
them
will
be
the
contributor
roadmap.
One
of
them
will
be
the
the
document
that
Matt
had
proposed,
but
I
think
the
that
how
to
contribute
folder
would
hold.
It
would
still
hold
more
than
one
document,
because
we
can't
we
can't
put
it
all
in.
We
can't
get
it
all
in
one
document.
A
B
A
B
A
B
B
A
C
Was
we
had
like
that?
Our
idea
originally
was
like
we'd
have
a
contribution
path
and
it
it
would
be
like
okay
now
you're
on
participating,
so
it
would
be
contribution,
path,
Dash,
participating
and
then
the
next
one
would
be
like
leading
or
maintaining,
or
something
like
that.
So,
but
we
didn't
get
that
far.
B
A
A
B
D
Just
do
these
things
and
it'll
help
you
right,
I,
don't
like
how
this
this
is
linked
on
step,
four
right.
The
flow
of
that
is
not
intuitive
to
me,
and
so
is
this.
Is
this
document
only
for
newcomers,
as
is
implied
here,
because
the
only
way
you
get
to
it
is
really
off
the
website.
From
this
page,
I
mean
I
would
prefer
to
just
keep
this
I,
don't
know
structurally,
it's
not
clear
or.
A
What
these
two
are
connected,
so
what
I
was
thinking
is
like
keeping
this
fourth
step
as
it
is,
and
then
that
this
contributor
path
page
needs
to
be
redefined
like
it'll,
have
more
explicit
or
all
got
both
to
this
place
for
a
grill,
more
lab.
Go
to
this
place
for
matrix
model,
go
to
this
place
and
start
contributing
over
there.
Okay,.
A
A
B
D
D
A
B
D
D
B
That's
a
that's
a
shortcut
button
that
we've
added
to
the
navigation
of
the
website,
because
we
we
want
to
create.
So
if
you
go
to
the
main
page,
there's
also
a
button
there
right
go
ahead
and
click
on
that
right.
So
we
we
shortcut
to
that
place
in
in
two
places
on
the
website,
because
we
really
want
to
help
newcomers.
Yes,.
D
D
I'm,
saying
is
right
now,
if
you're
an
existing
member
of
the
chaos
project-
and
you
want
to
participate
in
chaos,
cast
the
only
way
to
under
to
understand
like
the
path
to
do
that
is
community
knowledge
base
knowledge
base,
how
to
contribute,
and
then
you
ultimately
get
there
right.
It's
a
little
bit.
It's
fine!
It's
just
it's
a
little
bit
buried
compared
to
how
we
make
that
information
available
for
newcomers
that
they're
they
you
don't
enter,
they
don't
entry
points,
aren't.
A
A
B
I
would
say
that
the
knowledge
base
itself
is
mainly
for
existing
contributors,
like
for
new
contributors,
we've
created
the
that
shortcut
path
that
that
gets
them
to
the
Quick
Start,
but
for
new
control
for
existing
contributors.
If
they're
wanting
to
find
where
chaos
documentation
is
located,
if
the
knowledge
base
should
Point
them
to
it
or
it
should
give
it
to
them
so
the
if
they
want
to
know
how
to
do,
chaos
cast
that
information
should
be
at
least
pointed
to
somewhere
in
the
knowledge
base.
I.
D
B
A
So
just
one
thing
that
needs
to
be
done:
there's
a
one
PR
who
Don
has
already
reviewed
it
and
it
needs
to
be
merged
and
then
updated
on
the
website.
So
Kevin
as
you
are
updating
the
website,
there's
a
one
PR
on
the
common
repo
that
needs
to
be
merged
and
already
reviewed
by
Dawn,
common
and
sorry
in
the
community.
Depot
yeah
yep
Community
people.