►
From YouTube: CHAOSS Web Content Meeting Jan 19 2023
Description
Minutes from this meeting are here: https://docs.google.com/document/d/1p079Q75RZ2Duk-nX4osXY2v3oFjqF6-BTZG6XPx8iQ4/edit#heading=h.ktrrulbihiis
A
A
A
C
B
D
C
A
Yeah,
so
the
the
website
repository
does
store
some
of
our
documents
on
the
on
our
website,
but
the
rest
of
the
website
is
in
WordPress.
So
there
really
aren't
a
lot
of
documents
for
some
of
that
that
piece
of
things
and
then
we
have
a
WordPress
plugin
that
takes
information
from
GitHub
and
puts
it
into
the
website,
so
that
website
repository
is
kind
of
supplemental
and
it's
just
used
piecemeal.
And
then
we
pull
all
of
our
metrics
information
on
the
website
from
the
individual
working
group
repositories.
A
So
the
badging
website
has
a
there's
a
whole
team
of
folks
working
on
that
project,
so
I
would
maybe
connect
with
them
and
I
believe
they.
There
is
a
a
slack
channel
for
that
that
you
can
kind
of
pop
in
there
and
connect
with
that.
That
team,
which
I
can
give
you
that
information
after
this
call
I'll
just
need
to
look
it
up
and.
A
Yeah
yeah
I'll
I'll
kind
of
let
that
team
figure
out
because
I
know
there's
a
lot
of
people
working
on
that
team
and
so
to
coordinate
those
I
would
maybe
defer
to
that
team
to
assign
something
to
you.
I,
don't
know
that
I'm
the
right
person
to
do
that
so
so
yeah,
but
I
will
connect
you
with
that
team
for
sure.
Thank
you
so
much.
A
Okay,
and
so
the
second
thing
on
the
agenda
is
to
just
let
everybody
know,
we,
we
think
we
may
have
solved
the
problem,
hopefully
problem
the
conversation,
the
discussion
around
stable,
URLs
versus
our
diet,
the
human
I
can
speak
human,
readable
URLs
that
we're
currently
using
that
do
change
if
we
change
the
name
of
a
metric.
The
URL
also
changes
which
kind
of
creates
issues
for
folks
who
are
relying
on
those
stable,
URLs
auger
is
one
of
those
folks
and
other
software
projects
to
that
reference.
A
B
D
B
A
A
Like
as
a
process,
just
point
of
note,
I'll
just
put
that
in
here
just
to
document
it
somewhere,
we
won't
know
the
URL
until
we
publish
them.
So
then
we'll
have
to
go
back
and
add
that
in
after
it's
been
published,
so
each
metric
will
have
like
a
little
extra
step
to
it.
But
you
know
what,
in
the
grand
scheme
of
things,
it's
not
that
bad
and
we're
not
releasing
thousands
of
metrics
at
a
time,
maybe
one
or
two
so
yeah
I
think
it
will
be
okay.
D
B
D
A
B
A
B
D
B
B
C
B
B
At
them,
I
think
that
was
going
to
be.
My
one
comment
here
is
making
like
just
going
through.
So
Kevin
is
adding
the
keywords
to
the
metrics,
because
right
now
it's
only
the
context
tags
so
just
to
help
with
searching
and
so
I
mean
that
kind
of
I
feel
like
that
kind
of
occurs
behind
the
scenes.
You
know
what
I
mean
like
UI
change.
B
I
do
think
it's.
It
would
probably
be
good
to
just
let
the
knowledge
base
or
or
the
whole
website
sit
for
like
six
months
or
something
before
we
try
to
do
anything
else
with
it
just
so
we
can
capture
the
things
that
you're
talking
about
Elizabeth
like
yeah.
Yesterday
we
found
out
that
link
you
know
or,
like
the
content,
seems
a
little
bit
weird.
Maybe
we
should
update
that
or
I.
Don't
know
just
stuff
like
that.
Just.
A
A
A
B
A
B
B
D
A
B
A
B
B
B
A
B
A
B
A
Because
we
do
have
other
documents
in
the
community
repo
for
the
handbook,
I
will
say
some
of
these
issues
and
I'm.
Not
actually
this
actually
brings
up
a
good
point
is
that
sometimes
the
like
there
was
one
in
particular.
This
conversation
was
kind
of
going.
We
were
going
back
and
forth
between
slack
and
GitHub,
and
I
were
so
like
half
of
the
conversation
was
in
slack
and
half
of
it
was
on
issues.
That's.
A
B
B
They're
pertinent
to
the
home
yeah:
maybe
we
should
encourage
like
not
using
DMs
and
then
having
this
in
the
website,
WG
Channel
and
then
at
least
in
this
issue.
We
could
at
least
cross-link
to
the
the
channel
and
just
say,
there's
more
conversation
also
occurring
yeah.
We
could
at
least
connect
them,
because
if
it's
a
DM,
obviously
nobody
can
see
it
right.
A
B
B
A
A
B
A
A
A
B
D
A
A
D
A
Yeah,
because
we
don't
really
have
any,
you
know
what
something
that
would
be
helpful,
I
think
is
like
a
doc
that
said
when
to
use
what
like,
when
do
we
use
slack?
When
do
we
use
discourse
or
when
do
we
use
GitHub
issues
in
the
meeting
so
like
that,
might
help
newcomers
also
kind
of
know
where
to
post
a
question
or
an
issue
or
something
like
that.
Yeah.
B
And
maybe
that's
like
kind
of
that
conversation
we
were
having
with
the
tour
guides
like
it's
like.
You
know
how
to
just
encourage
people,
if
you
haven't
noticed
like
even
sometimes
in
slack
I'm,
trying
to
encourage
folks
to
have
like
if
it's
a
general,
if
it's
posted
in
general
or
newcomers
like
if
it's
an
auger
question
like
let's,
we
can
go
ahead
and
move
that
over
yeah
yeah.
B
I'm
wondering
if
we
could
just
add
like
for
the
people
who
are
at
the
community
meeting
like
if
you're,
seeing
things
that
are
happening
in
slack
I
mean
or
in
an
issue
that
you
don't
think
is
the
right
location.
Yeah
just
feel
free
to
to
hop
on
and
make
a
suggestion
as
to
where
you
think
it
would
be
best
suited.
A
A
Yeah-
that's
not
great,
so
maybe
just
something
like
about
how
we
interact
with
each
other.
Here's
the
here's,
the
three
channels
that
we
use,
slack,
GitHub
and
or
four
channels
slack
GitHub,
soon
to
be
discourse
in
meetings
and
here's
where
you'd
use
what
you
know
would
be
helpful,
I'm,
actually
gonna.