►
From YouTube: CHAOSS Weekly Community Call 2/15/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Hey
everyone,
it
is
february
15th
and
you
are
in
the
weekly
community
call
for
chaos.
So
welcome.
Welcome
I'm
elizabeth,
I'm
the
community
manager.
I
usually
facilitate
these
meetings.
That's
why
I'm
here
so
great
to
see
everybody.
The
minutes
are
in
the
chat
there.
If
you
wouldn't
mind
to
add
your
name
as
an
attendee,
we
would
love
that
before
we
start
quick
update
on
my
bengals,
as
you
know,
if
you're
in
the
us
they
lost
so
sad.
B
A
It's
all
good,
you
know
what
we
we
still
love
them
and
now
we're
even
more
excited
about
next
year,
so
you
won't
have
to
listen
to
me
complaining
or
mentioning
the
bengals
until
this
time
next
year.
So
thanks
for
supporting
me,
everyone
in
my
journey
all
right,
I'm
going
to
share
my
screen,
so
we
can
get
to
it
right.
First.
Item
on
the
list
is
an
update
on
the
dei
working
group,
and
I
will
turn
this
over
to
matt
g.
C
Yeah,
so
thanks
right
now
we're
working
on
just
a
variety
of
metrics.
I
think
the
one
that
is
most
like
easiest
for
us
to
work
on
right
now
is
project
demographics.
We
have
an
event:
demographics
metric
that
was
released
a
while
ago
and
we're
using
that
as
a
template
to
start
working
on
event,
demographics,
so
from
a
metrics
perspective,
we're
developing
new
metrics
as
well,
as
you
know,
kind
of
revisiting
some
of
our
ones
that
were
released
in
the
past.
C
I
think
we
spent
a
lot
of
time
recently
talking
about
our
own
onboarding
practices
within
the
chaos
project
and
just
what
we
can
do
in
that
regard,
and
so
that's
been
that's
been
really
productive.
Elizabeth
and
I
you
know,
I
think
elizabeth
and
ruth
have
been
doing
the
the
office
hours
a
couple
times
a
week.
C
C
A
All
right,
we'll
move
on
next
week,
we
were
hoping
to
get
an
update
on
the
value
working
group.
Vanad.
Is
that
okay?
Will
you
be
here
next
week.
A
Since
you
have
confirmed
your
predecessor,
cool
okay,
so
next
item
is
the
g
sock
reminder
we're
in
the
process
of
gathering
ideas.
Here's
a
link
to
the
repo.
If
you
have
ideas,
here's
how
to
do.
It
also
is
probably
a
helpful
thing
which
we
could
probably
change
that
to
2020
too,
but
basically
we're
just
collecting
ideas
in
this
repo,
and
I
did
we
did
have
one
idea
that
I
merged
in
sean.
I
hope
that's:
okay,
yeah,
okay,
yeah,
of
course,
yeah
I
mean.
B
No,
it's
totally
exactly
the
way
it's
supposed
to
work.
A
A
Now,
I'm
okay:
here
we
go.
That
was
an
idea
brought
up
by
matt
cantu,
so
thank
you
matt
and
there
it
is,
if
you're
looking
for
an
example
of
something
that
could
be
an
idea
here
is
one.
A
It's
a
little
different.
This
is
more
of
like
the
event
badging,
so
like
the
bot
that,
like.
A
And
stuff
like
that,
yeah.
A
B
F
B
That's
that's
the
place
that
we're
in
I
I've
got
it
on
my
list
to
put
in
some
auger
stuff
this
week,
and
I
think
I,
I
think
we're
more
labs
aware
and
we're
having
right
I'll
get
to
this
at
the
end,
but
yeah.
I
think
I
think
we're
on
track
perfect.
B
A
Awesome:
okay,
any
questions
for
sean.
C
Yeah,
maybe
we
should
make
sure
that
the
folks
too,
with
gremore
lab,
also
know
that
we
need
ideas.
I
don't
know
that
we
need
them
exactly
by
the
time
the
deadline
closes
for
gsoc
at
google
because
because
our
ideas
are
living
in
a
repository
right,
you
know
what
I
mean.
It's
not
actually
part
of
the
application
process,
but
we
might
want
to
ping
them
just
on,
like
slack
or
even
just
directly
like
daniel.
B
Yeah,
that's
yeah,
I
guess
with
georg
out
we
don't
necessarily
have
a
memorable
person
in
these
meetings,
I'll
ping,
I'll
ping,
daniel
real,
quick
right
now.
Okay,.
A
Okay,
let's
move
on
this
is
just
a
reminder.
We
would
love
to
have
a
photo
of
you
or
your
dog
or
really
anything
your
nft.
No,
we
probably
couldn't
include
that.
A
So,
weird
anyway,
sorry
I'm
showing
my
age
now
because
I
just
think
stuff
like
that
is
just
weird,
but
we
are
compiling
a
big
mural
of
all
of
our
community
people
if
you
are
brand
new.
This
is
your
very
first
meeting.
We
don't
care
you're
still
part
of
us
now,
you're
a
chaotic.
We
would
love
to
have
you
included
in
our
mural.
A
So
if
you
want
to
know
what
we're
looking
for
and
how
to
do
it
where
to
where,
to
put
it,
there's
a
link
here-
and
that
was
just
my
original
post
to
the
mailing
list,
which
you
can
also
join
if
you're,
not
a
member
of
our
mailing
list,
here's
the
stuff!
So
it's
supposed
to
be
the
deadline
today,
if
you,
if
you're
working
on
it,
just
let
me
know
it's
fine,
because
I'm
probably
not
going
to
start
the
mural
today.
A
Just
as
a
you
know,
I'm
going
to
be
honest,
I
probably
won't.
I
probably
won't
even
start
it
for
a
few
days.
Maybe
this
weekend
I
don't
know
so
you
got
time,
but
we
would
love
to
have
you
part
of
that
and
we're
going
to
probably
put
that
on
the
website
somewhere.
We
don't
know
where
but
yeah,
because
chaos
is
five
and
we
want
to
include
everybody
so
questions
on
that.
A
A
Yeah
you're
all
welcome.
I
did
that,
I'm
sorry,
so
are
we
just
should
I
just
share
this
with
everybody
matt,
I
don't
know.
A
Okay,
so
in
the
metrics
models
working
group-
that
is
a
group
that
meets
later
on
today
or
tomorrow
morning,
if
you're
in
asia
pacific
time
it.
What
that
group
aims
to
do
is
pull
other
metrics
together,
pull
our
individual
or
our
atomic
metrics
together
into
bundles
that
people
can
use
to
build
context
around
a
problem
they're
trying
to
solve
a
question
they're
trying
to
answer.
So
we
talk
about
how
to
bring
these
models
or
these
metrics
together
in
different
ways.
A
The
dei
badging
initiative
that
we
have
for
events
has
been
doing
this.
So
what
what
the
end
result
was
was
to
try
to
give
people
who
want
to
use
these
metrics
an
easy
way
to
do
this
and
a
quick
kind
of
summary
of
how
to
do
this,
because
if
you
look
at
our
list
of
metrics,
we
look
at
this
in
the
newcomers
channel
and
in
office
hours.
It's
like
literally
200
pages
of
our
pdf
of
metrics,
and
so
it's
it's
hard
to
digest
and
hard
to
know
like
what
what
you
should
do.
A
A
A
But
the
idea
is
to
yeah
take
this
information,
that's
in
this
doc
and
put
it
into
something
pretty
and
digestible
that
people
can
just
quickly
see.
So
what
I've
done
is
taken.
Our
dei
badging
looked
at
the
different
sections
so
like
the
first
one
is
event:
demographics,
so
here's
the
action
somebody
would
take
develop
a
process
for
measuring
demographics.
The
speakers
entertain
your
event.
Why
it
matters
like,
and
that's
I'm
pulling
some
of
this
from
the
metrics
we've
already
developed.
A
What
type
of
that
applies
to
how
much
time
it
would
take?
I'm
just
guessing
like
that,
could
be
wrong
and
that's
something
that
we
will
iterate
on
as
people
are
putting
these
in
practice
and
giving
us
feedback
again.
Implementation
difficulty,
it's
kind
of
intermediate,
because
it's
a
little
tricky
checklist
for
implementation.
A
I
don't
know
what
the
name
of
that
is
would
be,
but
all
of
these
things
together
would
be
the
toolkit
for
centering
dei
in
your
open
source
event
and
it's
it's
based
on
the
dei
badging
initiative,
and
I
hope
that
makes
sense.
But
if
it
does
not,
please
tell
me.
C
To
me
yeah,
so
I
think
the
when
I
was
taking
a
look
at
this
like
just
kind
of
going
through.
It
is
really
easy
to
read
and
really
easy
to
understand,
we'll
have
to
talk,
maybe
in
the
metrics
model
working
group
about
kind
of
like
this
is
a
lot.
C
This
is
a
lot
of
like
really
how
to
implement
this
toolkit,
or,
in
this
case,
really
this
metric
model
for
for
open
source
dei
in
your
open
source
event,
and
so
we'll
have
to
think
about
just
how
to
present
a
metrics
model
that
could
be
kind
of
high
level
like
here
are
some
things
that
you
need
to
think
about
for
a
particular
thing,
whatever
that
that
model
might
be,
and
this
one
this
is-
has
really
specific
ways
of
implementing
the
metrics
model.
So
that
was
just
something
that
I
was
thinking
about
as.
C
D
C
Risk
or
issue
handling
or
code
development
and
right
now
those
models,
they're
kind
of
high
level
yeah.
Thank
you,
and
they,
they
just
kind
of
say,
like
issue
handling
like
here,
are
some
metrics
that
you
should
think
about.
If
you
care
about
issues
in
your
project,
we
don't
really
go
into
detail
about
how
to
implement
those
particular
metrics.
A
C
A
C
C
A
A
C
C
A
D
C
G
Yes,
real,
quick
I'd
like
to
make
a
comment.
If
I
can
no,
so
I
I
like
the
idea
of
the
toolkits,
but
I
think
this
is
actually
a
step.
It's
a
step
beyond
the
the
models.
I
think
the
the
toolkits
are
are
possibly
the
the
the
applications
that
that
start
to
that
we
start
to
create
based
on
the
models
that
we're
creating.
G
So
for
me,
it's
kind
of
it's
a
progression
that
maybe
it's
the
next
step,
but
we're
not
necessarily
there
yet
and
the
one
way
that
we
can
continue
to
kind
of
build
these
tool
kits
or
or
maybe
build
a
platform
to
to
build
these
tool
kits
and
kind
of
place
them
in
near
the
models
would
be
to
create
a
kind
of
a
a
knowledge
base,
a
metrics
knowledge
base
on
the
website,
which
was,
I
think
that
was
a
term
that
elizabeth
has
used
at
one
point,
so
you
know
in
a
searchable
a
searchable
metrics
knowledge
base.
G
We
would
we
can
create
those
connections
between
the
metrics,
the
models
we
create
and
then
the
applications-
and
I
think
the
I
think
the
toolkit
is
an
application
and
not
necessarily
a
model.
So
I
think
the
model
is
more
of
an
observation
and
kind
of
a
exploration
of
the
relationship
between
metrics,
that's
kind
of
how
I
see
it
anyway,
so
so
I
think
we're
on
the
right
track
with
it.
I
think
it's
just.
I
think
it's
the
next
step
and
maybe
we're
getting
ahead
of
ourselves.
B
I
I
think
well
I
mean
the
metrics
models.
Group
is
building
jupiter
notebooks,
that
use
auger
data
to
actually
show
the
models
in
action,
and
I
think-
and
I've
been
talking
with
daniel-
is
gyro
at
vermour
lab
about
collaborating
on
putting
together
work
examples
of,
in
their
case,
kibana
dashboards.
In
our
case,
jupiter
notebooks
or
some
other
presentation
of
chaos
metrics
organized
according
to
the
way
the
metrics
models
are
defined,
and
I
think
I
think
this
is
an
important
next
step
to
chaos.
B
Having
you,
you
know
sustained
utility
for
for
the
software,
the
open
source
software
community.
So
I
I
think
it
is
something
we
have
just
you
know
and
I'm
working.
You
know
I've
got
to
attend
it
at
the
end,
but
I
think
I
do
think
it's
important
that
we
have
a
place
for
people
to
see
the
expression
of
a
model,
even
if
in
the
metrics
models
depository.
G
B
A
Okay,
that
discussion
will
be
continued
at
the
other
meeting.
Yeah.
A
Are
you
sure,
yeah?
Okay?
Okay,
so
let's
go
to
the
dot
github
thing,
I'm
guessing!
That
was
you
german
prices.
You
see
this.
C
That
is
me
so
we're
we're
obviously
playing
around
with
adding
the
github
folder
to
the
org.
So
we
can.
We
can
add
this
logo
to
the
org
and
we
can
add
some
text
below
don
had
provided
a
nice
example
a
while
back.
The
only
problem
I
have
with
this
is.
It
looks
bad
on
dark
mode,
because
it's
whether
it's
a
white
background,
it
just
shows
up
as
a
big
white
rectangle.
C
You
know
with
chaos
in
there
or
if
I
use
a
png,
you
know
that
it
it's
black
text
on
a
black
background,
so
I
don't
know
if
people
have
thoughts
on
that
or
just
not
even
using
the
cast
logo.
C
It's
just
it's
a
it's
a
really
easy
way
for
us
to
just
at
the
chaos
org,
yeah
kind
of
show
something
that
is
more
than
just
the
list
of
repos
like
what
don
don
had
provided
from
vmware
was
a
really
nice
set
of
text
about,
like
joining
the
community
like
how
to
get
involved.
I
really
really
like
that.
So
where's.
A
A
You
know
maybe,
but
it's
really
lovely,
welcome,
finding
your
way
get
started.
How
awesome
is
that
and
then
we
go
into
the
pinned
and
repositories.
C
A
H
Yeah,
I
think,
there's
a
lot
we
can
do
to
help
newcomers,
especially
using
something
like
this
to
just
help
point
people
in
a
direction
that
makes
sense
yeah.
This
is
beautiful.
I
mean
in
our
case
you
can
see.
One
of
the
one
of
the
challenges
we
have
is
that
we
have
over
70
orgs
github
orgs,
and
so
we
point
people
to
some
of
the
key
ones,
and
we
use
this
to
do
that
because
they
land
on
the
vmware
one
and
they're
like
well.
H
Where
is
spring
or
salt
or
any
of
the
other
things
that
we
any
of
the
other
big
open
source
projects
that
we
run.
So
it's
nice
to
be
able
to
just
point
people
to
the
things
that
we
think
they're
looking
for.
A
H
Good
job
there
dawn
oh
yeah,
so
not
me
zan
ambeal,
I
she's
fabulous
and
I'm
pretty
sure
she
did
that.
A
C
C
It's
interesting,
I
can
say
that
yeah
I
actually
did
yeah
anyway,
it's
interesting.
It's
it's!
It's
really
pretty
cool.
A
I
see
justin's
and
some
comments
in
chat,
okay,
cool
all
right.
So
should
we
move
on.
A
And
this
for
those
who
don't
know
what
this
is
so
in
each
of
our
metrics,
we
have
a
statement
that
makes
people
aware
of
the
fact
that
there
could
be
some
like
sensitive
information
in
the
metrics
and
like
how
they
handle
that
data,
and
you
know
access
it
and
get
it
is
could
be.
A
C
C
C
B
E
Yeah,
just
I
mean
having
something
that
might
have
better
organization
and
table
of
contents
and
organization
for
that
content.
E
Really
nice
just
a
lot.
E
And
find
and
discover
so
maybe
something
like
what
we
have
for
the
community
handbook.
But
I.
A
G
Which,
by
the
way,
I
am,
I
am
proposing
that
work
over
the
summer
when
we
do
we're
doing
some
kind
of
website
revamping.
G
B
A
Okay,
well,
that
is
a
fantastic
segue.
Thank
you,
kevin
also
into
the
handbook
talking
about
a
processor
place
where
we
reflect
on
it,
because
we
don't
have
that.
C
G
C
Yeah
and
josh
carrad
did
an
amazing
job
on
the
handbook.
I
think
it
was
google
season
of
docs
and
I
just
I
feel
like
it
just
kind
of
I
know
it's
on
the
website
and
all
that,
like
you,
can
get
to
it
from
there,
but
I
just
feel
like
we
don't
really
talk
about
it.
Much
and
it's
just
kind
of
hangs
out
there.
B
C
G
I
feel
like
it
exists
kind
of
outside
of
our
normal
collaboration
spaces
and
and
that's
that's,
what
causes
some
problems
for
me.
I'm
not
sure.
I
think
I
think
he
did
a
really
great
job
as
well,
but
but
we
don't
use
git
book
for
anything
else.
G
A
And
I
will
say
this
comes
up:
it's
come
up
several
times
in
the
office
hours.
It
came
up
again
today.
Enoch
asked
about
the
path
to
leadership
and
I
was
like.
Oh,
I
think
that's
in
the
handbook,
so
we
went
there
and
it
was
but
it's
buried.
You
know,
and
you
have
to
know
that
that's
what
you're
looking
for
and
so
yeah
it
was
like.
A
The
discoverability,
I
think
is,
is
a
challenge
and
we
don't
really
have
to
to
kevin's
point
yet
we
don't
really
have
like
an
an
owner
of
it
now
since
just
moved
on,
and
so
if
there
are
issues
in
the
repo
like,
I
don't
even
know.
If
there's
prs,
I
don't,
I
don't
know
like
nobody's
really
managing
that.
So
should
that
be
me
like,
should
I
be
doing?
Should
I
have
been
doing
this
whole
time.
C
No,
maybe
you
and
I
can
can
take
a
look
at
it.
I
I've
been
wanting
to
take
a
look
at
the
content,
but
I
also
like
don's
point
of
maybe
just
trying
to
find
like
points
of
connection
for,
say
the
working
groups
like
what
might
the
working
groups
care?
Like
you
know,
even
just
in
the
spreadsheet,
we
could
link
to
the
metrics
release
process,
so
that's
available.
So
when
you're
looking
at
the
spreadsheet,
it's
just
sitting
right
there
for
you
as
an
example,
there's
probably
other
ways
to
link
like
that.
G
We
can
it
in
the
in
the
website
revamp
we
could
we
could
try
to
link
to
it
through
through
an
online
knowledge
base.
I
suppose
so
that
we
could.
That
could
be
one
of
the
the
key
things
we
do
in
that.
A
And
then
in
the
meantime
I
will
look.
I
will
look
actually
at
the
repo
and
see
what's
what
try
to
clean
it
up
a
little
bit.
I
Yeah,
maybe
to
out
into
the
the
handbook
when
we're
in
the
office
hours
with
elizabeth.
I
actually
realized
that
the
handbook
is
just
so
detached
from
very
many
other
information
of
bits
that
could
be
attached
to
the
pro
to
the
whole
chaos
community
documents
and
the
only
way
you
can
access
it
is
actually
you
either
navigate
through
the
website,
and
you
go
to
that
drop-down
menu
and
click
handbook
or
someone
else
sends
you
a
link
that
hey
actually
what
you're
looking
for
could
be
good
from
the
handbook
here.
I
So
to
me,
I
found
those
that
the
only
two
ways
you
can
actually
access
the
handbook.
If
it's
not
that,
then
you
do
not
know
where
it
is.
Yet.
I've
also
seen
that
actually,
the
handbook
has
a
lot
of
information
that
actually,
when
someone
has
access
to
it,
there
are
very
many
things
that
will
be
clarified
that
are
already
in
one
central
place
whereby
they
will
not
need
to
be
moving
around.
I
So
I
think
the
integration
between
the
handbook
and
the
website
would
be
good
and
accessing
it
made
easier
like
linking
to
it
more
than
any
other
place,
I'm
putting
it
where
it
is
actually
easily
accessible.
Instead
of
someone
else
having
to
post
you
a
link
about
something
that
you
want
to
find
out.
A
Yeah,
we
also
discovered
that
the
search
doesn't
quite
like
the
search
on
the
website
now
doesn't
really
transfer
over
to
the
search
within
the
community
handbook.
So
I'm
sure
kevin
like
what
you
said:
it'll
be
more
integrated,
I
think,
with
the
new
website,
but
yeah.
G
One
of
the
other
one
of
the
other
issues
is
some
of
those.
Some
of
the
documents
within
the
handbook
are
old
and
there
was
there's
some
replication
in
those
documents.
G
So
I
know
we
we've
updated
the
the
release
process
multiple
times
since
that
handbook
was
created
and
I
have
never
updated.
I
don't.
I
actually
don't
know
how
to
update
the
handbook.
I'm
not
sure
I
have
access
to
that.
So
so
we
do
have.
We
have.
We
have
documents
where
we've
outlined
the
process
that
maybe
aren't
in
the
aren't
in
the
handbook.
G
Which,
which
we've
we've
talked
about
before
wanting
to
create
the
documents
in
the
community
repo
and
just
point
point
to
them
from
other
places,
so
we
yeah.
We
definitely
need
to
reduce
replication
and
redundancy
in
our
documents
so
that
we
make
sure
the
the
documents
that
are
the
truth
are
the
ones
we're
pointing
to.
D
And
in
the
handbook
I
observed
like
there
are
links
to
the
github
repo,
which
we
are
updating
regularly
so
maybe
like
we
are
updating
the
github
and
the
links
remain.
The
same
and
handbook
is
in
a
way,
then
updated
by
itself,
like
I
see
a
metric
definition
metric
template.
So
as
we
update
the
template,
the
link
is
still
remains.
The
same
and
handbook
will
point
to
the
user
on
the
template,
or
things
like
these,
so
so
we
maybe
need
like.
This
is
a
good
resource
and
an
asset.
We
can
just
monitor
and
update
it.
B
B
A
B
A
Around
like
release
time
since,
like
during
the
public
comment
period,
we
we
kind
of
stopped
working
on
on
on
metrics
and
the
working
groups,
so
maybe
that
could
be.
You
know
in
line
with
that,
maybe.
G
H
G
We
did
so
we
we
have
a
so
there
actually
is
a
web
content
group
and
we
were
we've
been
handling
a
lot
of
kind
of
the
the
community
activities.
So
the
the
metrics
release
has
been
part
of
that.
We've
done
template
work,
but
it's
an
informal
group
there's
really
just
a
few
of
us.
We
we
had
monthly
meetings
at
one
time,
but
we'll
say
there
was
lack
of
interest,
so
only
one
person
would
show
up
to
those.
G
So
so,
due
to
lack
of
interest,
we
we
stopped
having
those
meetings,
so
I
think
the
when
we
started
moving
some
of
the
community
stuff
into
common
I'm
a
little
bit.
C
A
Yeah,
it's
like,
I
think
it's
handbook.
B
A
Okay,
thanks
matt
for
bringing
that
up.
I'm
going
to
turn
this
over
to
sean,
I'm
guessing
who
put
this
on
here:
update
on
software
contributors
in
chaos
just.
B
That
kermore
lab
and
auger
I
mean
just
having
conversations
about
how
we
can
collaborate
on
really
things
like
the
metrics
models
and
providing
concrete
implementations
and
developing
more
of
a
software
contributor
community
within
chaos.
We
think
the
metrics
models
you
know
collectively.
I
think
we
think
the
metrics
models
provide
an
opportunity
for
for
chaos
to
provide
tools
that
are
that
reflect
those
models
and
are
I
don't
know,
I
don't
want
to
say
easy
to
access,
because
neither
of
our
tool
kits
are
easy,
but
certainly
we're.
B
You
know
both
projects
are
working
in
that
direction
and
so
we're
discussing
ways
to
collaborate
directly
in
the
interests
of
the
overall
chaos
project,
and
so
that's
with
very
initial
stages.
But
that's
one
of
the
things
that
we
said
we
wanted
to
do
this
year
and
I
just
wanted
to
update
everyone
that
you
know
we're
working
on
it.
B
C
Yeah
maybe
read
as
well
kevin
kevin
and
I
and
you
elizabeth
we're
going
to
be
taking
retake,
taking
a
re-look
at
the
website
really
starting
in
summer.
So
if
anybody
has
an
interest
in
that,
that
would
be
great.
I
think
we're
also
looking
for
somebody
who
does
graphic
design
work.
C
So
if
anybody
happens
to
know
anybody
in
this
that's
great
when
I
was
working
on
that
stuff
this
morning,
I'm
like
oh,
this
is
easy,
and
then
you
showed
it
on
the
screen
elizabeth
and
it
was
like.
Oh
okay.
Actually
maybe
we
do
need
to
hire
somebody
so
yeah
stephen
jacobs
at
rit
actually
has
a
graphic
design
group.
B
C
C
They
did
when
we
started,
I
could
reach
out
to
them.
My
concern
is
that
there's
so
many
projects
that
they
might
be
really
overworked.
That
would
be
my
that's
my
one
concern
and
we
do
have
the
funds
through
some
of
the
grants
to
support
an
individual
here.
It
might
just
be
easier
and
faster
to
go
that
route.
H
C
Exactly
okay
yeah,
I'm
happy
to
reach
out
to
brian.
C
F
So
one
of
the
things
that
we're
doing
on
our
stuff
is
we
are
letting
the
volunteers
have
a
lot
of
help
doing
a
lot
of
different
help.
Now
they
don't
get
to
do
the
website
redesign,
because
we
have
too
many
things
that
are
like
trademarked
and
blah
blah
blah,
but
we
are
working
on
tools
for
making
it
easier
for
each
of
those
groups
to
be
able
to
come
in
and
do
the
website
pieces
and
update
the
different
pieces
and
doing
things
of
that
nature.
F
Do
you
all
know
what
tools
and
stuff
you've
already
set
up
for
the
volunteers,
and
you
know
breaking
out
the
website
tasks
and
all
that?
I
think
that
would
be
helpful
in
regards
to
getting
your
volunteers
going
on
that.
G
So
the
website
is,
the
website
is
mostly
populated
with
content
from
from
markdown,
so
content
creation
can
be
can
be
created
on
the
in
our
github
repo
in
markdown
fairly
easily,
and
then
from
a
from
a
design
standpoint.
I
think
the
the
best
way
to
get
volunteers
to
contribute
to
that
would
probably
be
the
construction
of
kind
of
a
a
branding
or
design
handbook,
and
I
think
that
would
probably
be,
and
then
from
that
handbook
the
it's
easy
to
apply
those
those
concepts
and
those
images
to
the
website.
G
So
without
without
giving
a
bunch
of
people
access
to
wordpress.
I
I
think
there
is
room
for
a
lot
of
volunteers
to
contribute
or
many
volunteers
to
contribute.
F
Yeah,
because
what
we
did
is
we're
using
on
gas
fee
so
that
the
volunteers
can
each
have
so
each
working
advisory
group,
as
we
have
to
follow
them
over
there
can
basically
have
control
over
their
own
section
of
the
website,
and
that's
one
of
the
things
that
we're
going
through,
and
configuring
now
literally,
is
so
that
you
know
they
can
go
in
and
put
in
all
their
information
and
do
all
that
there's
just
not
a
lot
of
design
stuff
that
they
actually
get
to
do.
F
Doing
we
are
doing
a
certain
amount
of
design,
but
we
are
doing
templates
in
regards
to
it
so
that
they
they
know
what
they
can
and
can't
change
so
that
they
can
add
stuff
in
there
and
make
it
a
little
bit
more
graph.
F
Trust
me,
I
can't
do
my
marketing
and
design
people
and
not
give
them
that
okay,
they're
gonna
get
pissy
with
me
if
they
don't
get
to
do
some
of
the
stuff
in
their
way,
but
yeah
so
yeah
we're
going
a
little
bit
beyond
just
you
know,
breaking
out
of
the
get
book
kind
of
thing.
G
Part
because
of
the
whole
wordpress
portion,
and
I'm
not
I'm
not
opposed
to
giving
people
access
to
wordpress,
just
probably
not
a
just,
not
a
bunch
of
people.
F
A
All
right
well,
thank
you.
Both
everyone!
Actually
thanks
everybody
for
coming.
We
are
out
of
time
today,
so
we'll
close
this
meeting
out,
and
we
will
see
you
here
next
week
same
time
same
place
have
a
great
day.
Everybody.