►
From YouTube: CHAOSS Web Content Meeting 5/26/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
A
So
last
week
we
we
kind
of
we
just
kind
of
had
a
high
level
discussion
and
kind
of
started
mapping
some
of
this
out
so
right
now.
I
kind
of
I
consider
this
phase
that
we're
in
to
be
kind
of
the
information
gathering
phase,
so
we're
trying
to
trying
to
figure
out
what
what
problems
we
need
to
solve
in
this
website.
Redesign
and
part
of
that
is
understanding
who
our
users
are
and
what
user
paths
they
may
need.
A
Unfortunately,
in
in
some
of
our
previous
discussions
on
user
paths,
we're
having
a
hard
time
finding
explicit
things
that
people
are
looking
for,
that
they
can't
find
they
just
know
when
they
land
on
the
website.
They
can't
find
what
they
want,
but
they're,
not
necessarily
sure
what
they're
looking
for
is
the
kind
of
the
general
consensus
for
for
new
users.
A
I
thought
about
that
as
well,
and
I
think
matt
had
put
that
forward
as
an
option
as
to
yeah.
I
think
I
think
this.
B
C
B
A
Have
we
have
had
some
comments
from
new
users
who
have
basically
said
I
didn't
know
what
chaos
was
yeah
when
I
landed
on
the
website,
which
is
which
is
interesting,
because
I'm
curious
why
they
came
to
the
website
if
they
didn't
know
what
it
was.
So
what
the?
What
that
motivation
was
to
come
to
the
website.
B
I
agree
with
that.
I
mean
just
in
terms
of
not
knowing
what
chaos
is
so
yeah.
Those
are
two
that
I
I
hear
with
respect
to
a
user
study.
That's
I'm!
Okay
with
that.
My
concern
with
this
is
timing,
so
it's
may
26th
and
let's
see
yeah,
we
want
to
get
this
done
this
summer
and
like
if
we
actually
did
a
legitimate
user
study
that
would
take
like
three
weeks.
A
We
could
do
the
user
study
on
the
tail
end
to
to
ensure
that
the
paths
we
have
created
are
working
and
then,
and
then
just
do
our
best
to
create
these
paths
as
we
see
fit
on
the
front
end.
C
I've
I've
it's
been
a
long
time
like
graduate
school,
but
I've
done
lightweight
user
studies
where
there's
just
used
like
tracking
soft.
Like
this,
I
forget
what
the
package
is
and
who
makes
it,
but
it
would
just
be
loaded
on
a
laptop
I've
gone
to
coffee
shops
with
gift
cards
and
just
had
five
people
perform
a
task.
C
C
A
So
I
will
say
this
so
websites
kind
of
follow.
They
follow
certain
rules
and
people
become
accustomed
to
those
rules,
so
they
understand
how
to
navigate
a
website
because
they've
been
on
websites
before
right.
So
the
the
actual
navigation
of
the
website
and
the
the
way
the
menus
work
and
those
things.
It's
not
something
we
really
need
to
test.
We
really
need.
A
We
really
just
need
to
test
if
they
are
finding
that
bit
of
information
they
need-
and
we
could
do
that
in
a
survey
without
without
having
to
do
any
eye
tracking
software
or
specialized
software
which
which
we
do
have
access
to
by
the
way
at
uno,
and
I
have
used
that
before
as
well.
A
I
think
it's
more
a
ask
them
to
complete
some
tasks
and
then
survey
them
if
they
were
able
to
find
the
information,
because
the
I
think
I
think
our
our
big
problem
is
actually
those
user
paths.
Are
they
finding
the
information
they
need?
It's
not.
It's
not
necessarily
are
the
is
the
navigation
working
correctly
or
the
the
software
working
correctly,
which
I
think
you
know
a
traditional
software
user
study
would
really
identify
that.
D
We
could
also
do
a
really
lightweight
poll
in
slack
in
the
commerce
channel,
just
say
what
brought
you
to
the
chaos
website.
Did
you
find
what
you
were
looking
for?
If
not
or
what
were
you
looking
for
and
did
you
find
it
and
something
like
that,
like
I
think,
slack
has
polls
so
that
would
be.
My
vote
is
just
to
do
a
quick
like
informal.
B
A
D
A
Three
question
poll,
and
then
maybe
we
can
do
this
survey
on
the
tail
end,
which
would
be
a
little
more
in-depth
and
we
can
make
adjustments
based
on
the
feedback
we
get
from.
The
survey
with
the.
C
A
A
I
think
that
question
gets
at
if
you,
if
you
found
it
outside
of
the
website
or
off
the
website,
where
did
you
find
it.
D
Okay,
we're
on
the
free
plan
of
this
integration
called
simple
bowl,
and
it
only
will.
Let
us
do
five
respondents,
so
I'll
look
around
and
see
if
there's
others.
B
D
D
C
C
D
Do
a
google
form.
C
C
B
D
C
C
D
It's
about
the
only
comment
I
was
gonna
make
was
that
I
met
with
enoch
and
matt
c
yesterday
to
talk
about
coordination
for
the
dei
badging
bot.
Since
we
do
have
you
know,
multiple
people
wanting
to
kind
of
contribute,
even
though,
like
one
of
them
is
only
in
google's
our
code
student
and
then
what
we
decided,
and
you
all
can
do
this
or
not.
D
So
what
we
are
going
to
try
is
that
enoch
is
going
to
take
his
project,
break
it
down
into
issues
for
his
like
tasks
that
he
wants
to
accomplish,
he's
going
to
self-assign
those
tasks
and
then,
if
anything
else
that
I
use
or
whoever
wants
to
work
on,
they
would
just
create
an
issue
and
assign
themselves
so
that
everybody
knows
what
everybody's
working
on
and
then,
if,
if
there's
something
that
has
an
idea
for
something,
but
he
sees
that
enoch
is
already
kind
of
working
on
that.
D
It's
up
to
that
him
to
contact
enoch
and
say
hey.
I
want
to
do
this
little
piece.
Is
that
okay
and
then
enoch's
going
to
coordinate
that
himself
as
part
of
his
his
project?
So
that's
where
we
landed
we're
going
to
try
and
see
how
it
works.
You
all
can
do
what
you
know
whatever
we
want,
but
that
seemed
to
be
kind
of
a
straightforward
way,
and
that
way,
it's
kind
of
all
clear
of
who's,
doing
what
and
when
and
how
that
all
those
pieces
fit
together.
So
just.
B
D
Correct
and
so
since
we
do
have
multiple
people
working
on
multiple
pieces
of
the
project,
it
might
make
sense
to
have
it
all
in
one
place
and
then
people
just
kind
of
self-assign
their
issues
that
they're
working
on.
Obviously
the
mentors
would
need
to
know
and
kind
of
help
coordinate
that,
but
that
makes
sense
yeah,
so
just
a
thought.
Okay,
now
I'm
gonna
go
work.
A
So
for
the
for
the
knowledge
base
tasks,
do
we
want
to
I'm
sorry,
the
community
handbook
stuff,
which
does
need
to
be
coordinated
with
the
knowledge
base?
Do
we
want
to
do?
We
want
to
coordinate
that
on
the
website
repo,
or
do
we
want
to
coordinate
that
in
the
community
repo
for
the
handbook,
yeah.
B
I
don't
know
I
guess
one,
so
the
question
would
be
is:
are
we
gonna?
We
have
to
obviously
rebuild
the
handbook
because
we
can't
like
we
just
have
to
delete
right
because
we
cannot
get
access
to
it,
and
so
are
we
to
do
something
similar
where
the
handbook
is
like,
uniquely
different
than
the
website,
so.
C
A
And
I
would
like
the
the
folder
structure
to
be
kind
of
created
in
a
way
that
structures
it
like
a
book
right
chapters
of
the
book,
and
then
I
would
like
that
folder
structure
to
have
some
sort
of
duplication
on
the
website
so
that
we
are
pulling.
We
are
pulling
that
information
based
on
that
folder
structure,
kind
of
with
those
naming
conventions
onto
the
website,
so
that
the
website
is
really
just
a
lens
in
which
to
view
this.
A
B
A
Yes,
yep
exactly
from
it
from
a
user
standpoint,
if
you're
searching
for
items
you
don't
leave
the
website,
it
just
pulls
the
mark
down
up
from
the
community
handbook.
I.
E
B
B
Because
we
can
just
turn
that
off
because
at
some
point
we
have
to
like
dump
like
we
have
to
make
sure
people
don't
end
up
at
that
site.
You
know
what
I
mean
we
have
to
disconnect
that
from
the
internet,
and
so,
if
we
just
removed
the
the
domain,
I
think
that
would
take
care
of
it,
which
would
be
the
easiest
answer
and
then
the
content
which
is
still
pretty
decent,
I
think
you
know,
could
be
updated,
yeah
a
lot
of
the
content.
That's
there.
B
B
And
that
was
produced
last
summer
so
and
we
we
don't,
have
access
to
it.
So
we
cannot
get
the
administrative
key,
so
the
person
who
built
it
is
not
responsive,
so
we're
gonna,
we're
gonna,
be
closing
down
that
domain,
keeping
a
lot
of
the
content
there,
but
we
just
this
is
what
we're
talking
about.
We
just
need
to
close
down
that
as
observable
from
the
internet.
A
A
Some
there's
some
content,
that's
kind
of
spread
around
in
other
places
too.
So
there's
there's
community
handbook
content
that
exists
in
a
couple
of
the
other
repos
that
that
we
really
need
to
pull
in
and
merge.
A
But
anyway,
so
that
yeah
that
so
that
was
my
thought
on
it
and
I
think
elizabeth
and
I
have
kind
of
discussed
that
in
the
past
I'm
I
I
think
we
were
kind
of
on
the
same
page.
But
I
would
I
would
give
her
the
ability
to
adjust
or
tweak
that
or
say
something
different.
If
you,
if
you'd
like.
F
F
I
just
don't
say
I
I
actually
still
have
I
can't
access
to
the
edit
version
of
of.
But
yes,
we
discussed
this
before,
because
I
used
I
used
to
develop
on
git
book
with
josh
crock.
But
the
only
thing
is,
I
don't
have
the
the
administration
account,
so
I
can
just
I
can
access
and
I
can
edit
on
the
book
directly,
but
I
can't
add
anyone
in.
I
don't
have
that
account
so,
but
I
think
that
would
be.
F
That
would
be
helpful
to
migrate
the
things
on
gitbook
to
any
like
wordpress
or
markdown,
because
yeah,
so
I
think
the
mic.
I
I
can't
handle
the
migration
for
the
thing.
First,.
A
And
I
would
change
my
I
would
change
what
I
just
said
then,
if,
if,
if,
if
you
have
access
to
it,
we
should
probably
keep
it
open.
Just
in
case
you
need
to
copy
and
paste
stuff.
D
And
we
do
link
to
that
in
quite
a
few
places.
I
think
so
we
might
just
want
to
consider
doing
a
redirect
before
we
totally
shut
off
until
we
catch
them
all
that'd
be
my.
E
Yeah
one
one
question
I
had
was
kevin
when
you
said
the
community
repo
putting
the
markdown
files
in
the
commentary.
What
do
you
mean
the
website
repository
or
the
because
there's
a
community
repository
itself?
I
think.
E
Okay,
so
so,
if
we
put
it
in
the
community
report,
it's
replicated
on
the
website.
A
So
we
so
we
have,
we
can
pull
mark
down
from
any
of
the
repos
into.
A
A
C
C
E
A
Let's
go
to
metrics
definition,
so
this
this
is
a
little
bit.
So
this
is
the
full
release
page
here
right
so
and
we
use
we
use
a
single
column
setup
generally
and
we
treat
and
we
we
go
by
markdown
modules
right.
So
this
section
here
in
white,
this
is
one
module.
So,
theoretically,
this
is
one
markdown
page
and
then
each
time
we
all
of
this
content
comes
in
on
different
markdown
pages
as
well
right.
So
here's
the
diversity
and
inclusion,
so
we
are
pulling
them
from
different
repos.
A
A
So
the
code
that
we
have
to
pull
github
mark
down
onto
the
website
modifies
it's
part
of
wordpress
bakery,
which
is
one
of
the
one
of
the
editing
tools
right.
So
this-
and
this
is
wordpress
bakery
currently
and
when
we
come
down
here,
you
can
see
that
I
you
can
put
in
raw
html.
A
You
can
put
in
text
blocks,
but
this
is
basically
the
way
the
website
is
created.
It's
just
a
bunch
of
github
modules
right
and
if
we
come
down-
and
we
look
at
this
one
specifically.
A
A
A
E
E
E
Yeah,
sorry,
I
thought
about
on
that
question.
So
we
have,
I
think
we
have
the
content
for
the
handbook
in
one
of
the
repositories
as
well.
I
think
there's
a
representative
handbook
so
on
the
chaos
organization,
there's
a
reflection
in
handbook.
I
think
I've
seen
that
before,
but
I've
not
really
come
through
that
repository.
E
E
So
we
have
I'm
trying
to
get
the
link
for
the
handbook
repository
on
chaos
organization.
So
we
have
that
handbook.
There,
I've
not
scanned
through
the
contents
if
it's
the
same
thing
with
what's
on
the
current
handbook,
so
when
trying
to
when
we
want
to
like
move
contents,
do
we
import
the
repository
or
we
just
create
from
scratch
and
start
creating
those
markdown
files
in
a
better
structure.
D
I
think
I
understand
what
you're
saying
ruth
so
like
right
now.
All
of
the
files
are
here,
in
this
hand,
are
in
this
repo
and
you're
wanting
to
know.
Are
we
just
gonna
move
those
straight
over
to
the
community
handbook
in
the
same
format
and
everything
right.
E
C
A
Just
I
definitely
I
I
wouldn't
want
to
use
the
the
current
folder
slash
file
structure.
That's
there
now,
so
the
the
content.
Most
of
the
content,
I
think,
is
going
to
be
usable,
but
those
those
the
folders.
If
you
think
of
those
folders
as
like
chapters
in
a
book
yeah,
they
don't
they're.
Not
they
don't
really
tell
me
what
I'm.
C
B
A
Yeah
yeah,
I
would,
I
think,
I
think
a
lot
of
the
content
is
going
to
be
good,
but
I
think
the
you
know.
C
A
The
the
folder
and
file
structure,
I
think
we
need
to
create
a
folder
and
file
structure,
that's
very,
very
explicit
and
and
acts
as
as
navigation
for
the
handbook
right.
Does
that
make
sense.
B
A
A
Or
the
community
repo
is
the
handbook
itself
and
all
of
those
explicit,
renamed
folders
drop
into
the
community
handbook
or
into
the
community
repo.
That
would
be
an
option
as
well.
Okay,.
E
Yeah-
and
I
think
we
could
like
put
all
this
outreach
programs
into
one
folder
or
something
yep,.
D
C
A
So
I
I
think
this
was
really
this
is.
This
was
really
a
helpful
conversation
to
get
us
started
on
coordinating
the
knowledge
base
work
with
the
website
work.
I
wish
I
wish
yash
was
here,
cause
he's
doing
the
knowledge
based
work
on
the
website.
When
does
when
does
that?
Officially?
When
does
google
summer
code
officially
start?
I
know
this
is
we're
in
kind
of
the
in
between
period.
B
So
then,
if
we,
if,
if
we're
gonna
like
ruth
and
shoya,
who
are
part
of
the
season
of
docs,
I
like
elizabeth's
proposal
with
enoch
to
like
open
issues
to
describe
like
components
of
things
that
he's
working
on
where,
if
ruth
and
shoya,
if
you
follow
that
same
model,
where
do
you
think
well,
there's.
D
B
B
B
Okay,
and
so
maybe
ruth
and
joya
like
just
over
the
next
week,
or
so
maybe
just
start
thinking
about
like
first
initial
tasks
or
first
steps
like
show,
you
like
yours,
might
be
around
like
how
to
shut
down
the
current
handbook.
You
know
what
I
mean
like
how
to
save
that
content
and
and
slowly
shut
it
down.
B
E
F
I
have
several
things
in
mind
and
they
that
they
are
not
like
they
have
to
be
happy.
In
the
same
time.
Maybe
they
are
step
by
step.
But,
yes,
I
agree
with
the
migration
and
thinking
about
re
rethink
about
the
whole
structure
of
the
community,
repo
things
it
is
going
to
be
the
if
we
agree
that
the
community
report
is
going
to
be
the
whole
structure
of
the
handbook.
C
B
Yeah-
and
I
was
just
actually
just
listening
to
ruth
you
and
shaya
talk-
I
mean
like
it's
not
like.
I
was
thinking
if
you're
opening
issues
to
track
things
to
do
like
if
you
two
coordinate,
work
and
open
an
issue,
that's
both
both
of
you
together,
that's
completely
fine,
it's
not
like
shoya!
You
have
to
have
a
set
of
issues
that
are
uniquely
to
you
and
ruth.
You
have
to
have
a
set
of
issues
that
doesn't
make
sense
to
me.
So
just
we
can
have
like
one
or
two
issues
that
we're
all
collectively
looking
at.
A
A
I
would
like
to
wait
and
see
what
some
of
those
responses
are
in
the
poll
we
just
sent
out
and
at
some
point
at
some
point.
I
want
to
start
mapping
those
user
paths
kind
of
wireframe
them
out,
but
I
think
the
next
step
on
the
website
for
me,
you've,
you've
shared
a
website
that
you'd
like
and
you
and
you've
talked
about
the
key
features
that
you
like
about
it
yeah.
So
I
I
think
I'm
going
to.
A
I
think
the
idea
here
would
be
I'm
going
to
create
a
prototype
front
page
based
on
that
website
that
you've
shared
using
some
of
those
the
design
elements
that
you
said
you've
liked
that'd
be
great.
We
can
look
at
that
and
then
we
can
tweak
the
design
of
the
main
page
based
on
that
that'd
be
cool.
B
A
Does
anyone
on
the
call
need
or
want
access
to
the
wordpress
site?
I
know
yes,
you're
gonna
need
it.
A
Okay,
yes,
I
will,
can
you
give
me
what
email
address?
Would
you
like
me
to
use.
B
C
A
Okay,
so
I'm
gonna
give
you
access
and
what's
gonna
happen
is
you're
gonna
get
an
email,
it
says
you
have
access,
however,
I'm
gonna
set
the
password
to
something
crazy,
so
you're
gonna
have
to
go
in
and
and
reset
your
password.
A
A
Does
someone
want
to
take
over
for
me
while
I'm?
Actually,
I
suppose
we
could
be
done
yeah
we're
done.
Okay,.
A
Let
me
know
when
you're
ready
to
chat
yash
about,
I
know
we're
in
the
in-between
period,
so
I'm
not
gonna
ask
you
to
do
anything
right
now.
Let
me
know
when
you
want
to
kind
of
chat
about
beginning
the
work.
A
A
All
right:
well,
I'm
just
gonna
in
I'm
just
gonna-
add
them
into
the
the
admin
here
in
the
background,
so
I
think
we
could.
We
can
end
this
meeting.
A
Don't
if
you
leave
do
not
shut
down
the
meeting,
because
I
will
lose
access
to
the
chat
and
I'm
whoever.
I
guess.