►
From YouTube: Non Code Contributor Meeting 20180726
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).
B
Thanks
so
welcome
to
the
July
25th
meeting
of
the
non-code
contributors
guide.
I
am
your
host
now
Abraham's.
We
have
small
attendance
this
week,
most
likely
due
to
Google
next,
and
we
only
have
a
couple
of
things
on
the
invite
or
on
the
agenda.
Rather
so
this
should
be
a
moderately
short
meeting.
B
The
first
thing,
which
has
been
our
issue
for
the
last
couple
meetings,
is:
we
need
to
sort
out
the
zoom
right
now
we
are
using
the
contributes
weekly
zoom.
Hopefully
we
will
be
able
to
continue
using
this
same
zoom
moving
forward.
If
we
cannot
then
we'll
get
that
sorted
out
in
the
next
few
days.
But
if
this
is
going
to
be
the
official
zoom
for
the
meeting,
then
we'll
update
the
invite
and
finally,
everyone
will
actually
have
the
correct
link,
so
that'll
be
great,
we'll
actually
get
people
in
here.
B
B
On
how
we're
going
to
engage
with
them,
really
I
suppose
is
the
first
thing.
So
there
is
a
working
doc
that
I've
set
up
just
for
work
outside
the
minutes.
We're
gonna
put
together,
basically
a
form
letter,
so
that
we
can
have
consistency
in
introducing
the
effort
that
we're
trying
to
accomplish
to
the
SIG's
and
we've
also
got
a
list
of
all
the
SIG's
where
people
can
sign
up
and
claim
what
sig
they
want
to
interact
with,
so
that
we
don't
have
one
person
just
dealing
with
what
we
got
33
SIG's,
something
like
that.
B
So
far,
we
have
exactly
two
sign.
Ups
Bob
took
Sig
multi
cluster
and
a
signed
up
for
sig
p.m.
so
thanks
for
that
guys,
I'm
going
to
sort
of
hold
off
on
signing
up
for
various
SIG's
in
that
context,
until
other
people
have
had
a
chance
and
I'm
going
to
effectively
take
the
dregs.
That's
how
I'm
gonna
look
at
it.
If
nobody
else
signs
up
and
I
guess
I'm
getting
like
30
SIG's
to
deal
with.
B
We
need
to
get
our
blurb
hammered
out
and
we
need
to
figure
out
who's
going
to
bring
that
blurb
to
each
of
the
individual
SIG's
I
was
gonna.
Take
a
first
pass
at
writing
the
blurb.
Does
anyone
have
any
comments?
Any
ways
that
you
would
like
to
approach
group
writing
something
like
that
we
each
take
a
stab
at
it
and
then
try
and
correlate
them
all
together
or
anybody
with
done
anything
like
that
before.
A
B
A
great
question
realistically
we're
we're
trying
to
identify
I'm
I,
mean
we've
said
a
couple
times:
we're
trying
to
identify
the
roles,
we're
trying
to
identify
the
tasks.
But
what
we're
asking
the
cigs
for
in
this
context
is:
how
can
this
group
in
building
a
contributors
guide
for
people
who
do
things
other
than
write
code?
B
B
A
So
it's
we're
writing
a
guide
for
non
code
contributors
and
we
want
to
actually
give
them
some
guidance
and
specifically
where
to
contribute
yeah,
that's
part
of
it.
Yes,
the
EM,
and
how
to
talk
to
various
SIG's
about
non
code
stuff,
all
over
feeling.
A
lot
of
it's
going
to
come
down
to
attend
the
sig
meeting.
A
B
A
A
A
So
and
then
one
of
the
other
questions
there
comes,
how
detailed
are
we
going
to
want
to
get
on
the
other
end?
I
mean
there's,
obviously,
would
be
a
lot
of
value
in
having
a
document
that
says
hey,
you
know,
sig
API
machinery
has
these
particular
non
code
needs,
and
these
are
the
ones
that
are
in
the
main
sig
and
these
are
the
sub
projects
etc.
But
then
such
a
document
would
need
to
be
maintained.
A
B
B
The
initial
idea
was
just
to
put
it
into
just
to
put
it
into
the
contributors
guide,
but
I
think
if
we
can
start
something
that
is
on
that
road
of
documentation
to
process
to,
hopefully
some
form
of
automate,
and
then
it's
sort
of
the
ideal
right
that
that
would
be
a
better
result.
Out
of
this,
that,
to
be
frank,
I
hadn't
really
considered
yeah.
A
C
A
B
A
Suggest
that
we
should
do
is
we
should
brainstorm
some
suggestions
for
non
code
areas
where
si
might
need
help,
just
because
I
think
if
we
run
down
a
list
of
categories,
we're
gonna
get
more
responses
than
if
we
just
say
what
are
all
of
the
areas,
because
it's
probably
that
comes
up
in
people
start.
You
know
scratching
their
heads
and
saying.
Well,
maybe
we
could
kind
of
we.
B
B
Think
if
we
were
to
do
this
to
the
SIG's,
then
we
would
want
to
ask
them
first
and
then
give
them
examples
to
fill
in,
because
I
don't
want
to
restrict
somebody's
idea
of
saying.
Oh
yeah
I
could
use
this
because
it
doesn't
fit
into
the
example
context
that
we've
already
put
together
to
proceed
back.
B
A
B
A
Well,
I
mean
we
want
in
other
things,
it's
just
that.
I
know
that
if
we
put
people
on
the
spot
and
say
what
are
all
the
non
code
things
you
need,
they're
gonna
have
trouble
coming
up
with
things
that
it
does
really
correct
here,
lift
everything
yeah
and
and
that
even
if
we
supply
them
with
some
initial
categories
for
them
to
say
hey,
we
need
that.
We
don't
need
that.
Like.
A
B
I'm
wondering
how
much
of
this
we
want
to
do
verbally
during
a
cig
meeting
versus
how
much
would
we
want
to
mail
out
to
the
list?
I
think
we
should
approach
the
blurb
as
let's
go
into
a
cig
meeting
and
say:
hey
here's,
what
we're
trying
to
accomplish
we're
gonna
mail,
this
out
to
your
mailing
list
or
you
know
it's
a
closed
list.