►
From YouTube: CHAOSS Web Content Meeting October 27, 2022
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
B
A
B
A
B
A
A
So
I'll
continue
to
work
on
that
and
it
should
work
with
your
timing,
and
so
then,
what,
when
I'm
done
with
that
I
can
just
start
issuing
pull
requests
to
include
the
context,
tags
and
the
keywords,
and
it
should
be
that
simple
right,
just
a
pull
request
against
the
GitHub
markdown
page.
Is
that
all
you
need
yeah.
C
B
D
B
B
B
B
We've
got
a
header
which
provides
a
little
bit
of
information
on
how
the
metrics
are
created
at
the
bottom
of
the
page.
Currently
we're
doing
the
release
history,
so
we
do
have
the
in
the
general
design.
We've
decided
that
there
would
be
kind
of
these.
These
three
modules
other
than
the
knowledge
base
right.
So
the
first
one
is
up
here.
B
B
B
E
I'm
good,
oh
I,
think
the
most
coherent
web
experience
would
be
each
each
of
those
pieces
of
software
would
just
have
a
page
that
briefly
describes
it
and
then
links
out
to
its
own
preferred
documentation,
So,
Daniel
or
Dior
could
provide
links
for
Churchill
and
I
could
provide
links
in
in
the
narrative
the
text
for
far
we
may.
We
may
have
the
compass
stuff
available
by
the
time
we
launch
as
well
and
that
that
may
be.
You
know
we'll
see
how
whether
that
goes
under
buturgy
or
that
goes
under
Asian
Pacific.
D
A
Is
these
the
topic
like
the
search
for
metrics
and
metrics
models,
the
topic
areas
and
the
release
history?
That's
it
so
just
get
rid
of
this
all
together,
yes,
and
that
the
navigation
across
the
top
could
include
just
software.
You
know
what
I
mean
so
like
when
you
go
to
the
metrics
page
or
this
metric
slash,
metrics
models.
Page
all
you
see
are
those
things
that
are
related
to
metrics
and
metrics
models.
Full
stop.
E
A
A
B
D
B
A
B
B
A
I
would
just
let's
get
rid
of
the
drop
down
on
metrics
and
just
have
it
be
a
metrics
link.
It
just
comes
just
to
this
page
and
then
my
guess
is.
Is
that
I
know
you're
just
talking
about
this
page?
But
my
guess
is
the
one
that
currently
says
Dei
event
badging
as
we
start
getting
project
badging,
that
could
just
say
badging
and
then
it
could
have
a
drop
down,
which
is
event.
A
B
C
B
That's
that's
fine!
That's
that's
easier!
That's
easy
to
maintain
on
this
side
and
it's
the
that's
kind
of
the
default
way
that
we've
been
doing
other
things
as
well
right.
So
the
like
the
we
don't
embed
YouTube
on
the
page.
We
just
link
out
to
this
external
spot
right.
We
don't.
We
don't
embed
chaos,
chaos
in
the
website.
We
just
link
out
to
chaos
cast,
so
the
goal
of
the
website
is
really
just
a
place
to
kind
of
send
people
to.
D
D
C
A
B
E
One
of
the
things
I
hear
for
among
newcomers
frequently
is
you
know:
you've
got
auger
you've
got
grimora
lab
what
what
is
the
difference?
Where
should
I
start
and
I?
Think
brief?
You
know
brief
piece
of
text
about
grimorlab
and
a
brief
piece
of
test
about
text
about
auger
and
possibly
Compass.
If
it's
prepared
at
that
point
would
just
help
people
make
that
decision
without
having
to
jump
out
of
the
site,
like
I'm
talking
like
three
sentences
or
four
sentences
in
a
paragraph
that
just.
B
We
could
put
that
in
the
getting
started
on
the
started
page
and
then
obviously
we
have
the
I
think
that
information
would
be
in
the
in
some
form
on
the
the
Community
page
right,
because
if
we
go
to
the
participate
page
now
like
augering
for
more
labor
are
accounted
for
on
the
on
the
participate
page.
So
I
think
on
the
Community
page.
B
E
Meant
I'm
interested
in
other
people's
perspectives,
because
obviously
I
Come
From
a
Certain
perspective,
but
I
think
more
people
are
when
they
come
to
chaos.
Initially,
they
they
want
to
see
working,
metrics
and
and
so
giving
them
an
opportunity
to
like
have
a
quick
link
to
for
more
Labs
example,
implementation
augers
example,
implementation
and
then
another
link
with
a
brief
explanation
and
a
top
level.
Nav
I
I
think
that
just
helps
it
helps
people
not
have
to
poke
through
the
website
to
find
it.
B
And
that's
going
back
to
going
back
to
why
I
had
initially
thought
that
it
would
be
a
good
idea
to
have
that
software
section
on
the
metrics
page
right.
So
we've
just
presented
all
these
metrics
and
do
you
want
to
see,
and
now
we
we
do
have
software
that
can
Implement
these
metrics.
So
that
was
my
initial
thinking
on
having
that
that
software
area
there.
E
E
Yeah,
what
I'm?
What
I
am
saying
is
that
I
think
people
want
to
know
they
want
to
be
able
to
quickly
find
the
implementations
and
if
we
ask
them
to
click
through
more
things,
they're
less
likely
to
find
what
they're.
Looking
for
but
again,
I
I
have
a
perspective
on
this.
That
may
not
be
the
right
General
perspective.
B
B
E
I
might
I
might
have
a
page
for
software
exactly
like
this.
With
you
know
a
pair,
you
know,
like
a
paragraph,
doesn't
I,
don't
even
think
it
needs
to
be
three
paragraphs
and
then
two
of
these
little
boxes,
maybe
three
for
each
system
with
a
very
short
type
of
description
and
then
a
link
to
install
software
and
a
link
to
exam.
You
know,
example.
E
A
A
Like
that,
just
like
that
and
then
across
the
top,
you
would
have
software
with
no
drop
downs,
which
would
just
take
you
to
the
software
page,
which
looks
scroll
up
a
little
bit.
That
looks
a
lot
like
this
and
instead
of
metrics
and
Metric
no
scroll
up
instead
of
metrics
and
metrics
models,
it
would
just
say
software,
then
to
Sean's
point.
A
It
would
give
a
narrative
about
the
different
types
of
software
and
how
you
might
want
to
think
about
them
and
then
I
like
Sean's
idea
of
the
boxes
instead
of
organization
platform
and
software,
it
would
say:
gramoir
lab
auger
and
Compass
or
crack
it
or
whatever.
You
know
what
I
mean,
and
it
would
just
be
a
those
would
just
be
brief
descriptions,
and
if
that.
E
A
F
A
F
D
A
A
That
would
just
say
auger
is
this
and
then
in
the
platform
box,
which
would
be
like
we're
more
of
that
box,
it
would
say
or
more
lab.
Is
this
and
then
there
would
be
two
links
in
each
of
the
boxes.
So
four
links
total
one
link
would
say
you
know,
get
started
and
one
link
would
say:
live,
live
demo
or
live
implementation,
and
both
of
those
links
would
go
outside
of
this
website.
A
They
would
go
somewhere
else
and
then
more
lab
would
have
two
links
and
one
of
those
links
would
say
get
started
and
one
of
those
links
would
say,
live
implementation
and
again
both
of
those
links
would
go
out
of
this
website
and
that's
it.
That's
all
the
software
Pages
period,
okay
and
Sean
can,
if
Sean
on
his
get
started.
Page
wants
to
include
like
detailed
text
like
we
currently
have
like.
If
he
wants
to
then
that's
his
choice,
but
he
can.
He
can
manage
that
page.
Okay,.
E
C
I
was
just
going
to
say:
I
will
say
when
we
were
doing
the
outreachy,
auger
documentation
project
and
we
were
doing
kind
of
an
audit.
There
was
that
that
page
had
instructions,
the
GitHub
page
had
instructions,
the
August
site
had
instructions,
and
the
community
handbook
had
instructions
to
get
started
and
none
of
them
matched
up.
So
the
more
tight
we
can
keep
this
and
like
the
single
source
of
Truth
is
the
better.
C
So,
yes,
a
plus
to
all
of
this,
the
same
thing
with
grimoire
lab
I
mean
they
didn't
have
that
problem,
I,
don't
know,
but
that
is
linking
out
to
their
site.
My
only
question
about
that,
though,
is
if
someone
comes
to
chaos,
and
they
are
trying
to
search
for
something
auger
related.
How
do
we
incorporate
the
auger
docs,
or
do
we
or
like
what?
How
do
we
solve
that
issue,
because
I
know
that
that's
also
been
something
that
was
confusing
for
newcomers?
C
E
B
B
B
B
B
The
same
box
they'll
probably
be
replication,
we'll
use
that
exact
same
box
on
the
Community
page.
So
because
the
the
Community
page,
the
community
knowledge
base
page
for
the
most
part,
is
replacing
the
participate
page.
So
the
the
calendar
will
be
there
and
that's
also
where
we
have
all
of
kind
of
the
working
group
information,
foreign.
C
Sorry
Kevin
one
quick
other
question
on
that:
metrics
the
models
page
at
the
top
there,
where
we
had
the
narrative
about
the
metrics
I
I,
don't
think
we
actually
explicitly
say
what
a
model
is.
So
if
I
was
going
to
add
like
a
little
sentence
to
that.
Where
is
that
in
the
web?
That's
I
assume,
obviously.
B
B
B
B
A
B
D
B
Looking
at
the
wrong
meeting,
so
he
was
here
last
time:
okay,
so
that's
basically
where
we're
at
on
the
knowledge
base
and
the
knowledge
base
is
kind
of.
What's
holding
us
back
from
kind
of
finishing
up
the
whole
website
design.
So
as
soon
as
the
as
soon
as
the
knowledge
base
is
completely
live,
then
we
can
go
and
we
can
change
everything
else
on
the
website,
including
the
main
navigation,
so
right
now
I'm
in
the
I'm
in
the
process
of
creating
those
content,
areas
and
Elizabeth.
E
I'm,
looking
in
the
I'm
trying
to
figure
out
how
we
publish
the
metrics
is
it
this?
Is
it
this
documents
from
git?
That
plug-in?
Is
that
how
we
pull
stuff
from
GitHub?
No
okay?
What
do
we
do
to
pull
stuff
from
GitHub
because
I
think
it's
it's
whenever
the
name
of
a
metric
changes
and
they
do
or
in
some
cases
there's
a
metric
moves,
a
focus
group
or
something?
Then
it
gets
published
to
a
different
place.
E
I
I,
really
I
would
I
desire
a
a
permanent
link
so
that
the
software
that
we
build
and
the
documentation
that
we
build
around
that
software
can
create.
You
know,
use
those
links
to
point
to
the
related
chaos
metrics
and
not
have
to
figure
out
which
of
the
75
links
breaks
during
every
release,
and
so
I
was
trying
to
look
through
how
we
published
the
code
from
GitHub
to
see
if
there
was
a
parameter
for
creating
a
permalink
for
a
document.
E
B
A
B
So
the
the
plug-in
that
you
had
found
does
something
similar.
Just
not
what
we're
using
it's,
not
what
we're
using
and
it
it
doesn't.
It
doesn't
work
quite
as
well
yeah,
so
I
added
I
added
it
to
the
website
when
we
were
trying
yeah
to
yeah
to
test
to
see
if
it
would
work
out,
because
we,
when
we
initially
moved
from
hosting
from
Linux
Foundation
hosting
it
to
here
yeah.
C
B
B
F
B
B
So
when
a
metric
gets
released,
we
create
a
page
on
the
website
for
it
right
and
it's
the
the
same
process
for
the
knowledge
base
happens
the
exact
same
way.
The
difference
is
that
these
pages
are
stored,
kind
of
in
a
very
haphazard
way
here,
whereas
the
knowledge
base
has
kind
of
a
better
file
structure
system.
So
so,
right
now,
when
we
create
a
metric,
let's
just
look
at
metric
attendee
demographics,
for
example.
B
E
B
D
A
E
B
So
the
the
permalink
gets
gets
populated
based
on
the
name
of
the
page,
and
then
you
can
go
in
and
you
can
adjust
it.
So
we
decided
on
the
the
naming
convention
for
these
that
it
would
be
basically
the
chaos
website
and
then
metric
attendee
demographics
with
an
attended.
Demographics
is
the
name
of
the
the
metric.
Obviously,
if
we
were
to
use
the
same
naming
convention
for
models,
it
would
be
model
and
then
the
name.
E
Okay,
so
what
I?
What
I
would
suggest
is
either
when
the
metric
name
changes,
just
don't
change
the
permalink
or
if,
if
you
know
having
a
permalink,
that's
different
than
the
metric
page
name
is
potentially
confusing,
and
it
might
be
that
instead
of
the
permalink
being
the
name
of
the
metric
that
the
permalink
B
I
don't
know
some
some
kind
of
like.
E
Metric
slash,
an
ID
or
something
you
know,
such
as
some
kind
of
meaningless
piece
of
code.
You
know
meaning
a
meaningless
meaningless
identifier
of
some
kind
that
doesn't
change
ever
and
then
we
can
link
to
it.
Regardless
of
whether
or
not
the
metrics
name
changes.
We're
always
linking.
We've
always
got
this
permalink
that
doesn't
have
any
meaning
that
confuses
people
or
we
just
never
change
the
permalink.
B
So
in
the
in
that
the
text,
the
two
options
that
the
one
option
I
mentioned
was
having
the
URL
redirects,
which
we
do
have
the
ability
to
do,
and
then
the
other
option
that
you
mentioned
was
having
just
a
number
based
permalink
or
which
is
which
is
manageable
as
well,
so
the
so.
The
number
based
that
number
base
permalink
that
would
never
change,
would
be
easier
to
manage
the
the
permalink
that
has
a
very
intuitive
name
in
it
would
be
easier
to
share
right.
B
B
B
E
The
only
advantage
of
the
number
is
that
like
when
we
change
the
name
of
a
metric,
there
isn't
inconsistency
and
I,
don't
know
how
much
of
a
how
much
we
don't
change
metrics
names
that
often
and
I
I
think
this
is
better
than
it
was
because
we
aren't,
you
know
like
when
groups
reorganize
their
focus
groups.
We
were
having
that
change
things
as
well.
B
E
D
B
A
F
A
Kind
of
this
revision
process,
and
so
I
understand
listening
to
you
Sean
and
to
you
Kevin
that
one
is
not
maybe
more
perfect
than
the
other.
Both
have
potential
positives
and
negatives
associated
with
them.
I
I
totally
understand
that
I
think
my
inclination
is
towards
the
number
for
just
partly
in
effort
to
help
ease
the
process
later
where,
when.
D
A
E
B
Oh,
that's!
Fine!
That's
fine
with
me!
I'm,
not
a
I'm
not
attached
to
any
idea.
So,
okay
and
and
I
agree
completely
that
the
redirects
were
I
mean
the
whole
or
the
getting.
This
sorted
is
really
important,
so
the
the
when
we
it
having
the
ability
to
do
redirects
because
of
this
link
security
was
something
that
this
is
one
of
the
reasons
that
we
took
over
hosting
this
website
ourselves,
because
we
didn't
have
the
ability
to
do
the
redirects
prior
yeah.
So.
E
And
and
then
you
know
the
the
main
reason.
Why
is
so
that
when
people
like
when
well
when
the
turkey
and
auger
reference
chaos
metrics
that
they're
implementing
in
their
documentation,
those
are
stable?
And
frankly,
when
other
people
decide
to
put
chaos
metrics
in
reports
or
things
that
those
links
are
stable
for
them
as
well,.
A
F
Yeah
hi,
so
I
have
to
drop
off
soon,
but
so
marked
off
recently
joined
chaos.
Africa
and
you
know,
I
got
I
interacted
with
marked
off
early
this
morning
and
you
know
we're
talking
about
his
experience
and
what
he's
interested
in
so
he
kind
of
like
talked
about
or
said
he
had
experience
in
WordPress
and
I
was
very
excited
and
then
I
asked
about
like
his
experience
level
with
WordPress
and
he's
interested
in
contributing
to
the
website,
and
she
indicated
interest
and
I
I
have
connected
marked
off
with
belema.
F
D
F
Then
about
the
community
handbook
updates,
joy
and
I
kind
of
like
took
a
little
break.
We
were
back,
we
had
a
meeting
this
morning,
so
we
are
continuing
and
working
on
the
handbook,
so
it
would
have
like
more
would
have
it
like
we're,
updating
and
kind
of
like
reviewing
stuff
so
we'd
have
more
updates
next
meeting.
D
B
Because,
if
you're,
if
you're
interested
in
in
working
on
the
website,
maybe
if
we
can
set
up
a
meeting,
just
you
and
I
and
I
can
walk
you
through
the
process
and
coordinate.
And
if
you,
if
you
want
to
do
some
work
on
it,
I
can
coordinate
it
that
way.
So.
Currently,
the
only
person
doing
any
work
on
the
website
is
myself
so
and
and
yeah
she's
doing
the
some
of
the
knowledge
base
work,
although
I
think
he
might
be,
he
might
be
ramping
up.
A
A
A
I
think
right
now
the
metrics
release
and
like
metrics
revisions
is,
is
just
it's
too
complicated.
I
know
this.
Is
this
isn't
a
website
thing
and
but
like
the
website's
kind
of
involved,
because
it
picks
up
this
process?
You
know
what
I
mean
so
right
now,
like
I,
look
at
the
issue
for
creating
a
new
metric
or
the
issue.
A
You
know
what
I'm
talking
about
the
template
or
the
issue
template
for
like
re,
revising
a
metric
I
just
think
it's
too
much,
and
my
guess
is
that,
like
if
I
asked
like
Kevin
and
me
and
Sean
and
Elizabeth
to
describe
the
release
process,
we
would
get
four
different
descriptions
as
to
to
what
needs
to
be
done.
But
it's.
A
D
A
A
metrics
release,
it's
sub-optimal,
it's
not
that
they
don't
again,
not
that
they
don't
know
what
they're
doing
but
like
having
a
person
have
to
be
present
to
do
that.
So
I
would
like
for
Elizabeth
and
myself
to
get
together
and
kind
of
talk
through
through
a
new
simplified
model
for
releasing
a
metric
still
attending
to
the
thing,
hopefully
attending
to
a
lot
of
the
things
that
we
have
and
Kevin
not
like,
creating
a
system
that
would
be
different
for
the
website.
A
B
A
B
Get
and
then
yeah
and
that's
why
this
is
that's
why
this
is
all
here
yeah
the
way
we
I
mean
the
the
release
itself
was
really
about.
Oh,
that's,
it's
twofold.
One
is
the
providing
some
rigor
and
validity
for
the
how
or
how
we're
defining
metrics,
but
then
it
was
also
it's
also
about
how
we
present
those
metrics
to
to
the
the
users
or
the
people
right
so
with
the
with
the
knowledge
base.
F
F
A
B
A
So
I
so
I'd
like
to
make
that
not
two
days
of
work
for
anybody.
You
know
what
I
mean
so
anyway.
That's
that's
what
I'd
like
to
propose,
and
so
maybe
I
know
Kevin
you
and
vanad
and
I
had
kind
of
talked
about
doing
this
as
well,
but
maybe
I
could
just
do
it
with
Elizabeth
I
mean
you're
more
than
welcome
to
be
part
of
that,
but
and.