►
From YouTube: CHAOSS Weekly Community Call 4-27-21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everyone
welcome
to
the
april
27th
version
of
our
weekly
community
call
so
happy
to
see
all
your
faces
and
your
avatars
staring
back
at
me.
It's
wonderful
makes
my
day
makes
my
day
better
for
sure.
Sean
has
kindly
posted
the
minutes
and
agenda
in
the
chat.
So
if
you
would
be
so
kind
as
to
add
your
name,
if
you
feel
like
it
and
let
us
know
how
you're
doing
that
would
be
great,
I
will
add
my
name
here:
there's
an
empty
slot
here.
D
A
F
Gonna
have
to
have
we're
gonna
have
to
have
the
matt
matthew
like
have
you
seen
the
one
like
the
josh
throw
down
in
the
nebraska
cornfield.
G
A
Stay
tuned,
okay,
so
let's
go
ahead
and
get
started
before
we
jump
into
the
agenda.
I
just
want
to
take
a
minute
and
check
in
with
our
folks
who
are
in
india
or
have
friends
and
family
in
india.
A
I
just
want
to
check
in
with
you
if
you
feel
like
letting
us
know
how
you're
doing
I'm
just
really
super
concerned
about
you,
and
I
want
to
know
if
there's
something
we
can
do
to
help
you.
I
don't
know
what
that
would
be,
but
if
there
is
something
we're
here
for
you,
so
if
anyone
wants
to
jump
in
and
let
us
know
how
you're
doing
that'll
be
great.
G
Hello,
am
I
yeah
currently
I'm
staying
in
my
university
campus
and
our
semester
is
over,
so
the
university
is
forcing
us
to
go
to
homes,
but
for
now
there
is
no
problem
in
my
own.
Everyone
is
healthy.
H
So
apparently
in
my
city,
the
situation
is
quite
bad
and
like
we
are
getting
exponential
price
in
the
quorum
cases.
Scientific
models
do
predict
that
we'll
have
a
peak
around
15th
of
may,
but,
let's
hope,
the
earlier.
It
goes.
H
A
Okay,
well
we'll
go
ahead
and
move
on,
but
again,
if
you
all
think
of
anything,
if
we
can
support
you
in
any
way,
let
us
know
for
sure,
because
we're
here
to
do
that,
jumping
ahead
to
our
we
did
a
super
scientific
twitter
poll
last
week,
just
to
kind
of
ask
our
community
like
how
we
can
help
you
and
what
you're
struggling
with,
because
we
just
wanted
to
find
out
what
their
pain
points
were.
A
So
we
had
a
bunch
of
great
ideas
last
week,
of
which
I
could
implement
very
few
of
them,
because
the
twitter
polls
are
very
limited
to
25
characters
and
four
responses,
so
I
had
to
kind
of
do
my
best
to
you
know
be
concise,
but
anyway.
So
this
I
dropped
a
link
or
a
screenshot
of
what
the
results
were
in
the
minutes
there.
So
I
don't
know
if
we
wanted
to
take
a
minute
and
talk
about
it.
It's
kind
of
interesting
I
think
do
we
want
to.
J
A
I
think
that
yeah,
I
think
that
the
way
it
reads
to
me,
which
is
clearly
biased,
but
you
know
I
think
it's
just
not
even
knowing
where
to
start
and
not
knowing
how
to
get
any
data.
That
would
answer
questions
that
are
on
your
mind
or
even
what
data
there
could
be
out
there.
K
K
The
results,
arguably,
could
be
13
plus
30
for
the
problem
being
about.
You
know,
putting
the
data
to
use
finding
insights
and
doing
things
that
are
actionable,
and
I
can
say
that
in
our
group
at
miraco
we're
thinking
about
a
lot
and
I'm
thinking
about
a
lot.
K
L
I
agree
with
lucas
and
I
I
think
further,
that
that
first
question
that
knowing
what
data
to
get
could
probably
be
split
into
two
as
well,
and
because
I
think
it
it
could
be
interpreted
as
knowing
what
questions
to
ask
and
then
and
then
also
the
specific
metrics
that
can
connect
to
those
questions.
F
So
yesterday,
on
a
podcast,
that's
not
released,
it
was
myself
and
elizabeth
and
sophia
and
don
and
georg-
and
we
were
talking
about
the
podcast
itself.
So
it's
a
meta
podcast.
I
guess,
but
one
of
the
things
that
we
talked
about
was
in
the
chaos
project
that
we're
kind
of
at
this
point.
F
I
think
it
was
you
that
brought
it
up
sofia
kind
of
at
this
point.
You
know
where
we've
done
a
lot
of
the
work
to
start
to
articulate
the
metrics.
You
know
we
have
whatever
60
some
odd
metrics
and
connecting
them
to
tooling,
but
really
at
that
point
now
where
we
as
a
community
might
want
to
start
helping
people
through
through
that
first
part.
So
we
have
all
the
tools
in
place
and
like
helping
people
know
what
data
to
get.
I
think
we're
doing
this
right.
F
So,
for
example,
in
the
dni
badging
program,
we're
helping
people
know
what
data
to
get
with
respect
to
event
badging.
You
know
it's
not
perfect,
but
it's
helping
people.
So
you
know,
maybe
because
the
data
is
so
evenly
split
like.
F
Saying
like
33
24,
13
30.
like
there's
nothing
that
like
it's
like.
Oh
my
gosh,
this
is
the
this
is
the
thing.
This
is
the
one
thing,
so
maybe,
as
a
community,
we
start
thinking
about
how
we
can
help
overcoming
each
one
of
these,
whether
it's
to
lucas's
point
like
the
end
of
the
chain
right,
interpreting
the
data
and
then
putting
it
to
use
or
to
kevin's
point
like
even
knowing
what
questions
to
ask
and
then
subsequently
what
data
to
get
and
then
obviously
collecting
the
data.
So
it
just
it
to
me.
F
This
just
reinforces
what
we
talked
about
yesterday
in
the
podcast
that
nobody's
heard
that
we're
in
this
spot
of
of
maybe
thinking
about
how
we
can
be
more
deliberate
in
helping
people
through
through
this
phase,
because
we
have
a
lot
of
good
good
pieces
in.
M
J
I
think
so,
I'm
also,
I
guess,
I'd
be
kind
of
touching
this
and
tooling,
but
say
like
knowing
what
data
to
get
some
more
metrics
are
more
or
less
specific
about
sourcing,
in
terms
of
where
we're
actually
extracting
data
from
and
the
tools
could
be
platform
specific.
But
I'm
also
wondering,
if
that's
the
the
top
selection,
then
maybe
it
would
behoove
us
to
sort
of
aggregate
all
the
sources
that
we
use
or
just
are
common
in
use.
J
The
more
I
can
uncover
other
kinds
of
data
sources
and,
depending
on
what
your
needs
are,
there's
sort
of
the
alignment
between
what
source
makes
the
most
sense
to
answer
your
question,
but
like
most
of
the
time,
people
are
using
github,
but
there's
more
than
that,
so
maybe
it
might
be
worthwhile
to
have
so
sort
of
like
these
are
the
top
five
sources
that
programs
are
using
to
answer
these
kinds
of
questions
I
mean
I
feel
like
it's.
J
A
lot
of
like
might
be
feels
a
little
bit
foundational
and
it's
sort
of
like
a
lot
more
specific
than
a
lot
of
what
our
metrics
currently
do
today.
I
think
they're
a
lot
more
general
and
generalized
on
purpose,
so
that
we're
not
platform
specific
or
data
source
specific.
J
But
if
the
challenge
is
an
implementation,
then
the
first
question
is:
where
do
you
get
data
from?
So
if
it's
sort
of
like
a
these
are
the
things
that
we
use
or
other
programs
have
used
and
then
provide
direct
links
to
their
documentation
and
their
apis
and
tools
that
work
with
them.
I
mean,
I
think
it's
I
don't
know
how
useful
that
is.
J
I
think
it
would
be
useful
for
some
folks
that
are
brand
new
to
stuff
like
this,
but
that's
kind
of
how
I
interpret
how
we
could
make
it
sort
of
I
mean.
I
think
there
are
many
things
we
could
do
to
make
this
more
usable,
but
that's
sort
of
the
first
thing
and
just
in
terms
of
where
you
start.
B
One
and
I
think,
there's
an
sort
of
a
orthogonal
or
sideways
perspective
on
where
you,
knowing
what
data
to
get
do
you
there's
assume
you
have
a
platform
whatever
it
is.
Should
I
be
looking
at
issues?
Should
I
be
looking
at
pull
requests
commits
these.
These
are
questions
that
that
often
come
up
and
the
ones
that
have
been
most
commonly
requested
from
auger
at
least
are
focused
on
new
contributors.
Retention
of
new
contributors
lag
time
associated
with
pull,
request,
creation
and
merging.
F
So
was
your
sean
like?
Was
it
mapping
a
little
bit
of
what's
like
what
you
can
get
from
github.
F
B
More
to
what
kind
of
you
know
step
back,
what
are
your
goals
and
for
for
groups
whose
goal
is
to
attract
and
entertain
contributors?
There's
a
few
there's.
A
few
kinds
of
reports
that
have
been
requested
are
used
fairly.
Often,
new,
contributor
retention
and
full
request.
B
Responsiveness
is
one
issue,
responsiveness
is
another,
so
these
are
all
things
that
are,
I
think,
parts
of
metrics
that
we
produce.
So
we
have
these
60
metrics,
but
when
people
have
a
goal
of
sustaining
their
community
or
they
tend
to
go
after
the
sort
of
collection
of
metrics,
I'm
just
I'm
describing
which
is
different
than-
and
I
think
we
don't
know
that
we
do.
I
don't
know
that
we
explain
well
enough
like
sort
of
what
some
people
are
doing
or
what
some
of
the
case
studies
are.
B
N
I'm
in
listening
to
the
conversation,
it
feels
like
a
couple
of
things:
matt
you
brought
up
in
an
earlier
meeting
or
discussion,
the
use
of,
and
I'm
not
sure
if
this
was
the
exact
terminology,
but
user
scenarios.
M
N
And
it
feels
like
yeah
I
I
love
that
idea
just
me
personally,
because
you
know
someone
who's
coming
in.
Who
is
new
to
the
body
of
work
created
by
the
chaos
project
team.
N
It
feels
like
would
be
helpful.
Okay,
you
know
and
start
with
the
objective.
Do
you
want
to
retain
and
grow?
You
know
your
contributor
base.
Do
you
want
to
what
you
know?
What's
your
what's
your
objective,
let
you
know
and
and
walk
through
the
user
scenario
and
here's
and
and
then
pull
from
the
body
of
work.
N
N
I
don't
you
know
not
that
I
don't
have
a
passion
to
attend
this
meeting
just,
but
you
know
they
don't
fit
in
my
schedule
for
some
reason
or
another
and
I'm
like
wow,
I
I
don't
really
know
you
know
I
I
I
have
less
of
an
idea
of
what
what's
you
know
a
bead
on
you
know
this
group
or
that
group,
or
what
have
you
right?
Imagine
somebody
who's
completely
new
coming
into
this
and
like?
Where
do
I
even
start.
O
I've
got
kind
of
an
idea
here,
that's
that's
sent
from
work
working
with
our
tripoli,
esa,
open
they
have
a
meeting
their
community
advising
advisory
group
meetings
have
a
check-in
with
every
subgroup
of
that
community
advisory
group
and
then
the
people
check
in
say
like
within
a
few
minutes
or
even
less,
what's
going
on
in
that
group
and
what
they're
working
towards-
and
I
think
that's
a
really
really
good
idea.
P
I
I
guess
we
have
this
follow-up
from
every
working
group
on
our
monthly
meeting
like
first
monday
meeting,
where
every
group
shares
their
stories
or
whatever,
whatever
the
progress
they
are
doing.
Maybe
we
can
structure
or
like
customize
it
like
how
to
bring
some
scenarios
in
those
things
like
okay,
a
particular
working
group
might
look
okay.
We
looked
at
this
scenario
and
we
can
think
of
these
as
a
sharing
with
the
community
that
these
are
the
few
metrics
we
can
use
as
a
particular
scenario
from
a
group
perspective.
L
I
think
we,
I
think
we
need
to
be
really
really
careful
about
how
we
come
up
with
these
user
stories
and
how
we
present
them.
The
the
problem
I've
had
with
the
language
of
user
stories
in
the
past
is
user
stories.
It's
a
matter
of
perspective.
User
stories
are
usually
used
by
people
who
are
designing
something
to
describe
like
what
they're
designing
it.
For,
alternatively,
we
could
look
at
it
as
requirements
gathering
if
we,
if
we're
talking
about
design
and
in
requirements,
gathering
we're
grabbing
those
user
stories
from
the
community.
L
L
So,
if
we're,
if
we're
coming
up
with
these
stories
ourselves
based
on
how
we're
building
these
metrics,
then
there
is
a
there
is
a
validity
issue
right.
We're
telling
people
how
we
think
these
metrics
can
be
used,
but
they're
not
necessarily
connected
to
the
community
itself.
P
So,
listening
to
your
talk,
maybe
it's
a
proposal
for
a
chaos
that
we
should
do
a
research
and
reach
out
to
people
to
understand
what
are
their
stories
that
we
can
bring
to
the
chaos
as
a
community
and
because
our
goal
is
to
help
the
different
communities
to
assess
their
health
or
sustainability
of
their
project
and
going
forward,
but
until
unless
we
don't
have
their
stories,
how
how
we
can
like
we
can
assume.
Okay,
we
are
observing
these
things
but
bringing
those
stories.
L
I
think
I
think
all
of
the
activities
we've
discussed
are
good.
I
just
I
just
want
to
be.
I
think
we
just
need
to
be
careful
how
we
characterize
these,
so
we
everything
that's
been
talked
about,
sounds
great,
just
just
be
really
careful
about
how
we
present
these
user
stories
and
what
we
say
they
are
right,
based
on
based
on
how
we've
collected
and
connected
the
data
together.
O
And
also
you
gotta
remember
that
we
all
have
to
remember
too,
including
me,
this
stem
from
how
do
we
get
people
started
with
the
project
and
how
do
we
get
people
into
space
where
they're
comfortable
with
the
metrics
of
the
chaos
project?
It
sounds
like
onboarding
to
me,
and
the
user
stories
are
an
idea.
There
are
also
a
lot
of
other
ideas.
I
think
learning
paths
is
also
great
in
respect
to
how
do
we
get
what's
someone's
starting
point
with
the
chaos
project
for
the
longest
time?
O
So
I
just
think
that
that
that
beginning
point
is
like
the
most
crucial
like
way
to
determine,
if
so
like
for,
for
someone
to
determine
if
they
want
to
work
with
the
chaos
project
or
not.
So
I
think
that's
really
important
to
to
pay
mine
too.
D
I
I
feel,
like
I
could
add,
as
somebody
who's
new
to
all
of
this.
It
seems
a
little
bit
meta
for
me
to
be
speaking
now,
but
having
recently
tried
to
figure
out
what
the
chaos
community
was
all
about.
I
know
like
when
I
went
to
the
project
or
the
participate
page.
D
I
didn't
scroll
down
far
enough
at
first
to
realize
that
that
was
where
all
the
good
information
was,
but
it
just
it
took
me
quite
a
few
days
to
kind
of
get
a
sense
of
what's
going
on
how
you
know
the
sense
of
how
welcoming
is
just
how
much
documentation
all
of
these
committees
as
well
as
well
the
phrase
to
if
you
want
to
be
a
duck,
you
gotta,
learn
to
quack
like
a
duck.
I
I
was
just
trying
to
figure
out
like
ooh
values
committee.
That
seems
interesting
ooh.
You
know
diversity.
D
That
seems
like
just
there's.
There
are
a
lot
of
new
phrases
and
terms
and
for
me,
as
a
developer
part
of
a
really
big
project.
You
know
the
question
I
came
with
was
we've
been
measuring
all
this
stuff
in
the
drupal
community
for
over
five
years
now-
and
I
was
thinking
I
was
starting
to
think-
oh,
my
gosh-
are
we
measuring
the
right
stuff,
so
I'm
going
through
all
the
metrics
and
whatnot?
D
So
I
think
just
from
that
point
that
point
of
view
I
feel
like
helping
funnel
people
into
the
right
groups,
or
just
I
don't
even
know
how
you
solve
that
of
trying
the
language
barrier
of
of
just
the
metrics.
L
Matthew
as
a
as
a
new
contributor,
if
you
do,
if
you
do
have
ideas
on
some
high
level,
thoughts
on
on
things
to
address
that
participate,
page
I'd
love
it.
If
you
could
open
an
issue
to
share
your
thoughts
on
the
website,
repository.
D
So
so
that's
a
good
example
like
is,
is
that
would
I
open
that
with
the
common?
Was
it
the
common
group
that
we're
in
now.
O
I
just
posted
the
repository
link
in
the
chat
as
well.
Okay,.
L
Yes,
that
would
be
the
web
content
group.
So
it's
not
it's
not
a
metrics
working
group
got
you.
A
Maybe
we
should
have
it
like
a
dedicated
team
that
focuses
on
onboarding
and
kind
of
distilling
these,
oh
thanks,
matt
snell.
I
got
two
thumbs
up
on
that.
Yes,
I
think
that
would
be
important
just
to
have
like
a
deliberate
focus
people.
You
know
it's
kind
of
one
of
those
things
if
nobody
owns,
if
everybody
owns
it,
nobody
owns
it
kind
of
thing.
So
I
would
like
to
see
that
if
that's
something
we
feel
like,
we
should.
B
I
think
I
think
some
describing
some
ways
that
some
goals
and
questions
that
we've
encountered
from
folks
in
different
working
groups
and
how
we've
gone
about
working
together
to
answer
them.
You
know
taking
the
metrics
from
concept
and
definition
to
some
kind
of
presentation
that
that's
useful
to
people.
I
think
we
have
a
lot
of
examples
of
that
in
the
in
the
tools
that
we
have
so
somehow.
F
F
F
If
you
want
to
get
a
better
understanding
of,
say,
contributor
experience
here
are
the
metrics
that
could
be
helpful
for
you
and
then
to
sophia's.
Earlier
point
here
are
the
data
sources
that
could
be
useful
to
you
when
you're
trying
to
understand
contributor
experience
and
then
maybe
to
matthew
and
matt's
point
like
if
you're
interested
in
knowing
more
here
are
the
working
groups
that
where
we
talk
about
these
particular
metrics
like
that,
could
be
a
funnel
to
get
people
to
my.
B
I
think
the
second
point
you
made
about
the
scenarios
and
showing
examples
that
moves
the
chaos
curious
to
sort
of
past
curious
to
possibly
interested,
and
then
at
that
point
we
want
to
see
if
there's
a
way,
we
can
help
shepherd
new
contributors
who
are
interested
into
the
project.
I
I
have
some
concern
right
now
that
people
don't
perhaps
fully
understand
all
of
the
things
that
are
enabled
through
the
chaos
project
when
they
come
to
our
page.
So
if
they're
curious,
it's
a
lot
of
information,
that's
overwhelming
and
they
may
not
persist
to
understand
it.
L
I
agree
that
there
there's
that
there's
a
lot
of
complexity
in
the
chaos
project,
so
all
the
different
working
groups,
some
of
the
working
groups,
define
metrics.
Some
of
the
working
groups
do
other
things,
and
then
we
have
two
pieces
of
software
that
are
being
created
also
so
that
there's
a
lot
of
complexity.
It
is
it's
if
you're
new
to
the
project
and
you're
trying
to
figure
out
where
to
participate.
That
is,
it
can
be
difficult,
but
I
I
do
agree
with
matt
the.
L
I
think
the
user
scenarios
is
a
different
thing,
but,
and
I
actually
think
the
user
scenarios
are,
I
think,
that's
part
of
our
our
core
mission,
the
metrics
definition,
and
I
view
it
as
kind
of
a
categorization
or
way
of
collecting
these
metrics
together
that
that
that
helped
define
them
and
and
provide
descriptions
of
of
how
to
use
them.
So
I
think
user
scenarios
are
part
of
our
our
core.
Q
Function:
yeah
totally.
I
was
just
itching
to
talk
yeah,
so
something
I
wanted
to.
Okay.
There
are
three
things
I
hope
I
don't
forget
them
all.
Q
So
the
first
thing
is:
I
totally
agree
that,
like
you
know,
for
a
new
command,
navigating
the
site
and
understanding
working
groups
right,
it's
like
pretty
difficult,
because
I've
had
up
to
three
calls
like
people,
people
from
my
network,
trying
to
contribute
to
chaos-
and
I
had
to
you
know:
one-on-one,
you
know,
have
a
call
with
them
and
look
at
all
the
working
groups
on
the
site
and
trust
me.
Q
I
also
found
it
difficult
finding
some
things
right,
even
if
I've
been
details
for
a
while
and
then
the
second
thing
I
wanted
to
see
is
we
could
start
off
by
you
know
recognizing
new
contributors
on
weekly
calls
right.
Q
So
let's
say
you
see
someone
who
maybe
you've
not
so
the
person
hasn't
joined
this
call
before
and
like
okay,
if
you
are
available
to,
if
you
can
introduce
yourself-
and
you
know,
tell
us
or
why-
or
you
are
not
necessarily
why
that
might
encountered,
but
how
you
got
involved,
how
you
want
to
get
involved
with
chaos
right
then.
A
third
thing
I
wanted
to
mention
is
so
this
this
might
be
long
term,
but
we
can
introduce
maybe
monthly,
new
comma
call.
Q
That
newcomer
calls
that
you
know
people
wanting
to
get
involved
with
chaos.
Can
you
know
we
do
like
a
demo
and
you
know
introduce
them
to
different
working
groups,
and
you
know
because
I
think
there
was
a
time
where
somebody
wanted
to
contribute
to
chaos,
and
I
think
he
he
was
attending
a
different
meeting
from
what
he
wanted
to
do
right.
So
I
I
think,
that's
that's
what
one
of
them
the
three
things
I
wanted
to
like
point
out.
We
could
you
know,
plan
long
term
for
a
monthly
call.
R
Yeah,
I
really
like
the
idea
of
having,
like
a
newcomer,
call
that
people
could
just
join
and
and
learn
more
about
the
project
I
mean
you
can
even
you
can
even
run
those
as
kind
of
like
office
hours
where
anybody
could
drop
in
and
ask
sort
of
random
random
questions.
And
it's
you
know
anything.
It's
free
games,
no
bad
questions,
kind
of
model.
C
So
I
don't
know
if
this
is,
I
don't
know
if
this
is
true,
I
mean
I
think
I
wrote
a
bullet
point
somewhere
in
the
dock.
C
I
wonder
if,
like
people
come
to
our
website
or
our
repo
and
look
for
like
they
want
to
measure
some
aspects
of
the
community
and
we're
just
not
addressing
it,
I
mean
I.
I
don't
know
that
for
sure,
because
one
of
the
things
that
I've
been
thinking
about
over
the
I
mean
I
don't
know
how
long
is,
I
think,
we've
done
a
good
job
of
capturing
like
contributions
on
activities
on
repos,
but
outside
of
that,
I'm
not
sure
if
we're
necessarily
addressing
a
lot
of
the
buccaneers
or
requirements
from
from
community
managers.
C
Yeah,
like
you
know,
people
started
a
discussion
on
on
forums
right
or
or
whatever
channels
that
people
are
using
for
communications.
It's
not
code,
but
people
are
starting
conversations
and
starting
topics
like
we're.
C
You
know,
and
that's
could
be
just
as
I
mean
as
valuable
as
contributions
on
the
repo
and,
if
we're
not
addressing
those-
and
you
know,
maybe
people
sort
of
lose
interest
and
drop
off
and
those
are
harder
to
measure
right.
I
mean
you
can
argue
that,
like
activities
on
repos,
like
you,
don't
even
need
like
to
use,
you
can
just
use,
get
the
metrics
from
from
github
or
get
lab
without
having
to
use
any
of
the.
C
F
C
C
For
example,
in
my
current
community,
I'm
doing
this
a
lot
of
times
manually
and
I'm
working
with
some
companies
to
see.
If
we
can
automate
this,
we
have
a
slack
channel
for
community
and
people
post.
A
lot
of
questions
like
I'm
trying
to
do
xyz
and
I'm
stuck,
and
there
are
a
lot
of
people
that
are
really
good
at
like
jumping
in
and
answering
those
questions
and
and
I'm
sure,
there's
a
way
to
sort
of
like
account.
Those
like
I'm.
C
That's
I'm
working
with
some
of
the
outside
organizations
to
help
help
us
do
that.
But
you
know
I
I
like
to
be
able
to
sort
of
recognize
these
people,
like
I
do
with
people
that
are
submitting
code
patches
on
on
github
or
or
whatever
repo
you're
using
right.
This
person
is
like
really
helpful,
like
jumping
on
and
helping
on
board
other
people
and
that's
an
example
and
then
yeah
and
it
could
be
slack
discourse
or
whatever
tool
that
you're
using
in
your
community
yeah.
I
think
we
have.
B
L
E
I'm
just
listening.
I
think
there
are
two
approaches
to
helping
people
come
to
chaos.
E
One
is
we
think
about
what
structure
they
would
expect
and
that
would
make
sense
to
them
to
make
it
more
intuitive,
because
the
structure
that
has
grown
over
the
last
four
years
made
sense
as
we
were
building
on,
but
maybe
we
need
to
restructure
the
chaos
project
and
the
other
approach
is
to
educate
and
explain
how
this
project
is
structured
and
works,
and
so
maybe
having
an
explainer
video
on
the
website.
F
I
will
now
that
my
semester's
over
ish,
I'd
like
to
I
think
office
hours
are
a
good
idea
and
I
would
offer
to
even
do
it
like
just
sit
in
a
zoom
channel
for
an
hour
every
two
weeks.
F
I
mean
it's,
not
a
ton
of
effort,
you
know
with
like
no,
we
have
to
make
sure
there's
no
agenda
like
people
can
literally
just
show
up
and
ask
questions,
and
then
gosh
I
mean
it
really
seems
like
a
slack
channel
is
the
way
to
go
like
a
newcomer
chaos,
newcomer
slack
channel
or
something
like
that,
I
we
haven't
started
c.
B
F
B
B
B
O
We
do,
but
it's
not.
It's
been
used
for
badging,
especially
within
the
starting
up
phases.
So
it's
not
necessarily
structured,
but
it
could
be.
It
could
be
used
for
whatever
it's
it's
a
chaos
slack
so
I'll
hand
that
off
to
whoever
wants
it
in
the
in
the
board,
just
make
a
newcomer
channel
yeah.
R
And
I
think
I
like
about
having
a
slack
channel
or
or
office
hours
is,
I
think
some
people
are
intimidated
by
mailing
lists.
So,
first
of
all,
a
lot
of
people
aren't
really
that
into
email,
but
with
a
mailing
list.
I
don't
know
whether
I'm
emailing
five
people
or
50
000
people.
G
R
L
And
I
I
do
like
the
idea
of
having
a
slack
channel
at
this
time
as
well.
However,
I
do
want
to
point
out
that,
since
chaos
has
begun,
the
idea
of
using
a
slack
channel
or
discourse
or
it's
come
up
multiple
times
and
for
some
reason,
we've
always
decided
not
to
do
it.
So
we
may
want
to
reflect
on
the
reasons
why
we
didn't
want
to
do
it
prior.
R
And
I
think
we
had
a
lot
of
discussions
about
whether
or
not
to
stop
to
spin
up
a
discourse
which
I'll
admit
I've
been
on
the
anti-discourse
side,
because
I
I
think
you
need
to
pick
one
or
the
other.
You
need
to
have
a
forum
or
you
need
to
have
a
mailing
list.
If
you
try
to
do
both
of
them.
You
end
up
with
fragmented
conversations,
they're
mailingless
people.
R
There
are
forum
people
and
you
get
some
of
that
fragmentation
in
in
slack
as
well,
but
because
it's
sort
of
real
time
it
feels
a
little
bit
different
to
me.
I
guess
I
guess
I
would
be
okay
with
a
with
a
slack,
whereas
I
think,
if
we
spun
up
at
discord,
we
would
need
to
spin
down
the
mailing
list
or
make
some
hard
decisions.
That
way.
That's
just
my
my
opinion.
C
Okay,
this
course
okay,
yeah,
I
mean
I
I
I
tend
to
agree
like
we,
I
my
because
I
just
went
through
this
in
our
community.
You,
I
think,
you're
better
off,
starting
with
slack,
because
it's
easier
to
spin
up
and
it's
more
casual.
This
course
is
for
more,
like
a
knowledge
base.
Is
a
knowledge
sharing
thing?
It's
it's
not
a
real-time
communication
tool,
that's
what
slack
is
for,
and
so
you
know,
if
there's
no
sense
in
starting
both
of
them.
C
Just
start
with
slack
that'd
be
my
recommendation
and
if
you
want,
like
jono
bacon
I'll,
try
to
find
a
find
his
blog
post
on
what
both
tools
are
for
and
it
was
pretty
concise,
and
I
thought
it
was
well
done,
but
slack
is
more
for
more
casual
conversations.
I
I
think
that's
what
we
need
like
the
discourse
is
more,
I
mean
that's,
that's,
building
a
community
knowledge
base.
Basically,
I
don't
know
if
we
need
that
right
now,.
F
Please
so
so
I
will
again
I'll
offer
to
pilot
a
slack
channel
and
a
newcomer
like
zoom
or
like
office
hours
zoom
over
the
course
of
summer-ish.
You
know
maybe
for
the
next
two
months
and
you
can
see
how
it
goes
right
like
if
we
run
the
office
hours
on
zoom
and
nobody
ever
comes,
then
obviously
we
don't
need
to
do
that.
But
if
the
offset
it's
a
great
you
know
we
get
a
bunch
of
conversations
in
there
awesome
and
I
can
just
report
that
back
just
see
how
it
works.
Yeah.
D
A
Okay,
oh
go
ahead,
matthew.
D
D
Or
weekly
weekly,
if
not
more,
it
keeps
changing,
there's
a
whole
team
of
people
that
work
on
it
now
yeah,
I
I
it
might
even
be
more
than
that
more
than
weekly
now,
but
I'm
not
sure
I
was
just
gonna
say
that
that
that
has
whole
that
whole
thing
has
grown
as
like
a
team
and
that
it
allows
people
to
just
come
in
and
get
pointed
to
the
right
person
like
even
in
a
massive
big
open
source
software
project,
it
still
often
comes
down
to
like.
D
Oh,
you
need
to
go
talk
to
this
person,
and
I
think
that
can
be
super
helpful
if
there
are,
if
that
person
to
talk
to,
can
help
sort
of
guide
the
journey
for
whatever.
That
might
be,
because
I
mean
I
actually
don't.
I
don't
look
at
your
website
and
your.
I
don't
look
at
the
chaos
community
website
and
see
it
as
like
a
problem
the
way
it
is.
D
I
actually
think
it's
really
well
structured
in
terms
of
finding
things,
but
sometimes
just
that
initial,
like
human
interaction
in
a
sense,
even
though
it
might
be
on
a
channel,
can
be
tremendously
helpful
to
like
there's.
I
mean
I
work
with
a
lot
of
ux
people.
I
know
a
lot
more
about
this
than
I
do
that
funnel
people
in
so
I'm
not
an
expert,
but
I
tend
to
be
more
like
that
that
just
ask
somebody
can
be
really
helpful
if
there
is
a
friendly
place
to
do
that.
D
I
believe
so
I
I
haven't
looked
at
it
in
a
while.
I
can
double
check
on
just
it's
just
security.
I
mean.
L
I
was
just
gonna
say
thank
you.
Thank
you
for
the
the
comments
and
thank
you
everyone
for
the
the
discussion
on
this
real
quick
before
we
move
on,
because
I
know
the
meeting
is
gonna
be
ending
here
pretty
shortly.
I
just
wanted
to
say
that,
in
regards
to
all
of
this,
the
conversation
we've
been
having
about
contributing
and
participating
content
on
the
website
and
in
our
community
handbook
is,
is
actively
maintained
by
the
community.
L
So
if
anyone
would
like
to
to
go
and
help
create
this
content
and
and
move
some
of
these,
these
conversations
we're
having
the
the
contributing
guide
would
be
in
the
governance,
repo
and
then
the
website
repo
is
is,
is
also
maintained
by
the
community.
So
these
are.
These
are
places
where
we
are
actively
doing
these
things
that
we've
been
talking
about
and,
if
you're
interested
in
contributing
to
that,
please
please
go
there
and
help
out.
A
Okay,
I'm
going
to
jump
in
sorry.
Thank
you
kevin.
Thank
you,
everyone
for
that
amazing
awesome
conversation,
so
many
good
ideas.
I'm
super
excited
to
work
on
some
of
these
matt.
I
will
help
you
with
office
hours
and
slack
and
all
of
those
things
we
can
take
that
offline,
though
just
real,
quick,
no
asia,
pacific
call
next
week
resuming
that
on
may
19th.
As
you
see
in
the
meetings
also
matt
snell.
Where
are
you?
Are
you
still
here?
You
are
matt.
Snell
is
taking
some
time
off.
A
O
Yeah,
thank
you.
Ruth
yeah
yeah
go
ahead.
Sorry,
thank
you,
asta
ruth
anita,
and
you
elizabeth.
I
think
you
have
a
couple
more
people
that
are
interested
as
well.
That
may
be
onboarding
before
I
leave
too,
but
I'm
going
to
be
gone
for
the
month
of
may
and
just
a
quick
note.
Thank
you,
everybody
for
everything
in
the
badging
products.
O
So
far,
I'm
really
excited
to
see
how
it
is
when
I
come
back
to
as
long
as
it's
not
on
fire
and
I
I
will
be
coming
back
as
matt
cantu
to
anyone
that
might
need
to
know
about
the
name
change
too.
So
that's
all.
I
have
thank.
A
You
matt,
and
then
I
see
one
other
thing
that
ruth
has
posted
in
here.
There's
a
badging
cfp
abstract
looks
like
ruth's
looking
for
some
feedback
on
that.
If
you
have
time
to
do
that.