►
From YouTube: Community Committee Meeting
Description
A
There
we
go
okay,
we
are
live
now.
Sorry
for,
let's
start
everybody
on
the
YouTube
stream,
we
are
going
to
dive
right
in
our
agenda.
This
week
is
number
issue
number
461
in
calm,
calm,
everybody
who's
in
on
the
call.
If
you
haven't
already,
please
throw
your
names
into
the
meeting
minutes
talk.
I
think
most
of
us
has
done,
have
done
that
already
awesome
and
could
actually
get
somebody
to
volunteer
to
help
taking
notes.
I
would
appreciate
that
greatly.
A
A
C
Yeah,
so
we've
been
going
on
mentorship,
but
I
think
love
with
the
program
better
and
make
it
more
scalable
for
to
announce
it
to
the
whole
node.js
community
at
the
moment
we're
sound.
Hopefully,
this
is
like
the
last
bit
round
before
we
actually
like
announce
it
to
everyone.
I
mean
by
announcing
announcing
it
to
everyone,
is
like
gathering
more
mentors
from
the
whole
project
currently
were
just
targeting
working
groups,
and
currently
we
have
amazing
12
mentors
that
we're
gonna
start
with,
hopefully
within,
like
the
next
two
one
to
two
weeks.
D
Yes,
so
you're
getting
we're
actually
getting
a
lot
of
contributors
from
the
community
coming
in
and
so
just
working
that
process
I
did
I
was
able
to
add
another
person
to
our
editor
list.
Matteo.
So
that's
been
helpful.
So
thanks
or
folks
who
respond
to
me-
and
you
know
so-
we
can
get
some
of
this
more
technical
content.
D
You
know,
basically,
we
reviewed
and
make
sure
that
it's
where
we
want
it
to
be
for
quality
wise,
also
just
really
quickly
we're
continuing
our
work
on
the
working
groups,
series
reached
out
to
Michael
and
we've
got
a
couple
of
leads
coming
through
around
some.
You
know
some
additional
working
group
blogs
that
we
can
do
I.
Think
that
there's
a
great
opportunity
with
the
mentorship
working
group
so
I
would
love
to
you
know,
connect
on
that
and
I
can
follow
up
directly
and
see
how
we
can
get
something
off
the
ground.
D
It
sounds
like
there's
some
good
momentum
there
so
happy
to
support
any
way.
I
can
to
get
that
information
out
on
the
blog,
so
more
people
can
get
excited
about
it
and
more
people
can
participate,
but
so
far
so
good
with
the
node.js
collection
stuff,
seeing
a
really
good,
seeing
a
good
stream
of
content
actually
coming
in
from
the
community,
which
is
awesome.
A
B
So
you
know
we're
still
working
on
the
same
things
that
we
discussed
the
last
time,
which
was
you
know,
we're
looking
to
do
user
feedback
sessions
in
the
like
physical
meetups,
we're
working
towards
one
that
you
know,
Dan
is
going
to
coordinate
in
I.
Think
it's
late
April
to
a
sort
of
our
trial
run.
Then
we'll
have
a
deck
that
you
know
has
the
structure
and
having
validated
the
sort
of
approach
we
can
have
other
meetups
rollout
as
well.
B
So
that's
sort
of
the
next
up
on
that
one,
the
other
one
is
amad
is,
and
we
have
scheduled
sort
of
a
kickoff
to
re
to
get
get.
Basically,
the
enterprise
subgroup
going
again-
and
you
know-
we've
been
working
with
Tracy
to
you-
know,
put
together
a
blog
post.
So
we
should
see
that
going
out
fairly
soon
in
terms
of
like
you
know
what
it
is,
who
we're
looking
forward
to
join
and
then
the
first
mean
to.
E
F
B
Is
the
enterprise
subgroup
specifically
saying
it's
a
sub
group
of
user
feedback?
The
other
one
is,
is
no
more
we've
archived
the
repo
we
agreed
again.
Anything
future
on
that
front
should
be
under
the
auspices
of
the
user
feedback
group
and
will
be
like
it's
it's
a
sub
group
in
the
sense
of
like
you
know
we're
trying
to
get
feedback
from
you
know
all
end-users
through
the
you
know,
and
what
our
current
approach
through
that
is
through
the
meetups.
F
Yeah
sure
website
redesign
last
meeting.
We
briefly
discussed
a
couple
of
issues
related
to
no
just
a
dev,
specifically
around
navigation
and
discussion,
around
code
coverage
and
alternative
solutions,
just
providing
credit
I
think
a
PR
has
been
made
I.
Remember
it
going
through
I'm,
not
sure
it's
an
area
around
attributing
credit
to
people
who
have
been
burying
documentation.
F
F
We
also
briefly
discussed
a
call
for
proposals
for
the
collaborator
summit,
so
we'll
be
submitting
one
or
two
for
that.
If
anyone
has
any
suggestions
around
what
they
want
to
get
out
of
a
session
with
website
redesign
do
get
in
touch,
I,
think,
DMS
and
Twitter
or
make
an
issue
in
website
redesign
that'd
be
really
cool,
otherwise
Adam
unless
I've
covered.
We.
A
Also
talked
about
and
can
kind
of
cross
over
as
a
Nitin
and
update
as
well.
We
talked
about
getting
a
time
set
up
for
a
spin
out
meeting
to
talk
about
Ayten
and
integration
with
the
new
site,
so
Zeke
everything
them
today
to
get
the
meeting
scheduled
for
hopefully
this
upcoming
week
sometime
we're
gonna
talk
about
what
it'll
take
to
get
the
internationalization
artifacts
in
a
consumable
format
for
the
new
site.
So
how
do
we
publish
that
that
module
how's
it
ingested
as
a
you
know,
etc,
etc?
A
G
B
H
H
A
A
F
Totally
this
is
a
sorry
folks
for
people
who
have
heard
this
before,
but
we
will
be
pushing
this
over
the
next
couple
weeks,
just
quick
reminders
for
people
to
get
their
sessions
in
for
Berlin.
So
the
collaborator
summit,
in
a
nutshell,
is
happening
at
the
end
of
May,
I.
Believe
the
30th
and
31st
right
before
Gia's
confi
you.
If
anyone
was
already
planning
to
go
that
for
context.
It's
designed
to
like
start
with
that
and
then
like
people
after
that
would
be
able
to
go
to
Jess
I'm,
for
you
are
the
these
are
open.
F
So
you
can
submit
that
on
issue
149
in
the
summit,
repo
I'm,
linking
that
in
the
chat
here,
it's
a
slightly
different
process
so
before
we
used
to
submit
them
just
through
github,
now
we're
submitting
them
through
a
Google
Form.
There
is
like
you'll,
still
be
able
to
do
the
other
one
we're
trying
to
make
it
so
that
the
forum
is
the
source
of
truth.
F
So
if
you
can
do
submitted
by
the
forum
and
if
necessary,
what
we're
doing
is
we
could
create
another
issue
and
github
if
we
want
to
like
pull
the
community
community
to
see
what
kind
of
responses
there
are,
but
just
do
get
the
sessions
in.
So
we
can
start
scheduling
you
because
the
agenda
is
up
and
we're
starting
to
spot
stuff
in
it's
a
little
different
this
time.
Now,
it's
not
just
no
jazz.
It's
the
open,
gist
foundation.
F
Projects
are
all
coming
to
Berlin,
so
this
is
going
to
be
super
cool
and
sessions
will
be
much
broader,
which
also
makes
planning
all
this
extra
complicated.
So
the
earlier
you
get
those
submissions
and
the
easier
it
is
for
the
people
to
review
them,
and
you
get
your
you
know
thumbs
up
sooner,
which
means
you
can
start
making
travel
plans,
but
also,
actually,
arguably,
more
importantly,
submit
travel
fund
requests
ASAP.
We
need
to
make
sure
those
requests
go.
G
F
A
Awesome
thank
you
for
the
update.
Let's
swap
up
the
agenda
a
little
bit
here
to
throw
Sarah
Sarah
Conway,
you
wanted
to
talk
about
the
user
survey
and
nodejs
Interactive's
CFP
yeah.
G
G
I'm
sure
we
had
a
little
bit
of
a
committee
with
some
foundation,
employees,
community
folks-
and
you
know
we
definitely
be
crossing
over
into
the
JSF
projects
this
year
and
things
like
that
so
was
wondering
if
there
are
any
volunteers
for
that
and
if
you
want
to
just
speak
up
on
github
or
contact
me
afterwards,
either
way
it's
fine.
Yes,.
F
F
Last
year,
if
I
remember
the
process
correctly,
we
had
one
designated
person
from
each
committee
whose
final
sign-off
was
needed.
Correct
me,
if
I'm
wrong
for
anyone
who
was
there
for
that,
for
us,
it
was
gem,
I,
believe
gems
no
longer
with
us.
So
would
the
process
be
similar
where
you'd
need
a
similar
like
sign-off
from
a
director
responsible,
individual
from
each
community
of
committee,
and
it
would
be
necessary
to
have
the
proposal
go
through.
I
Just
gonna
say
just
to
manage
expectations
even
with
that
sign
up.
It's
ultimately
still
up
to
the
like
the
executive
director,
because
last
year,
altom
utley
I
believe
it
was
Chris
and
Mark
who
signed
off
on
the
lineup,
regardless
of
like
Cooper
marquees,
are
representing
that
and
we'll
also
have
I
would
assume
way
more
people
because
of
the
various
projects
that
we've
got
as
part
of
the
larger
foundation.
But.
B
My
one
bit
of
feedback
would
would
be
like
I
didn't
know
that
there
was
maybe
a
sign-off
by
one
group
from
each
of
the
committee's
yeah,
but
like
I,
think
having
a
little
bit
more.
A
few
more
cycles
of
consultation
would
be,
as
you
know,
III
filled
in
my
okay
and
I,
never
heard
anything
after
that
and
I
think
it
would
have
been
better
if
it
was
like
okay,
we
all
spent
the
time
we
reviewed
them,
but
you're
kind
of
just
ringing,
a
very
large
number
and
it's
it's
st.
with
a
number.
B
It
would
be
good
to
have
come
back
and
said:
well,
here's
the
top
X.
You
know
what
are
people's
comments
on
that
right?
You
know
not
not
that
it
was.
You
know
whatever,
but
just
a
little
bit
more
of
the
yeah
we've
narrowed
it
down
based
on
the
initial
numbering,
and
he
which
would
your
preferences
be
or
something
I
think
would
be
a
good
good
thing
to
include
yeah.
G
I
Think
something
that
I
think
we're
kind
of
here
to
give
feedback
to
the
events
team.
Is
that
not
to
be
to
have
a
little
more
transparency
even
or
like
managing
expectations
even
of
the
people
reviewing
of
what
the
process
is
right
so,
like
making
sure
everyone
understands
like
okay,
we're
reviewing
and
giving
points
to
these
individual
talks,
but
ultimately
these
three
people
are
actually
designing
the
lineup
or
like
we
get
in
the
lineup
like
I,
think
that
that's
helpful,
yeah
yeah,
that
said,
like
I,
mean
I've.
You
know
we
run
processes
in
different
ways.
I
With
my
personal,
you
know
the
conference's
I
run
outside
of
this.
We
have
a
different
process
than
this.
One
is
because
there's
also,
you
know
the
corporate
membership
to
consider
as
part
of
the
discussion
and
the
way
that
the
events
team
manages
the
event
so
I
think
again,
it's
always
good
to
have
transparency,
even
if
it
you
know
so
that
people
understand
like
how
the
decisions
are
being
made.
Yeah.
E
I
G
Wonderful
yeah
I
think
you
know
documents
like
thinking
through
what
we
liked
from
last
year
for
what
we
might
want
to
change
and
then
documenting
that
one
just
for
the
committee
and
the
people
that
will
be
involved.
So
there's
you
know
clear
expectations
but
then
potentially
making
that
process
public
and
a
blog
post
of
some
sort
I
know
at
times
we've
done
that.
Then
there
was
some
hesitation
and
not
wanting
to
do
that.
G
G
Do
and
I'd
be
happy
to
share
that.
I
was
just
diving
through
that
last
week
and
really
like
I,
think
we
had
about
70
responses
and
not
everyone
fills
out
everything
that
I
really
sort
of
tried
to
see
what
patterns
were
there.
I
mean
there
was
definitely
some
of
the
things
that
I
remember
or
you
know,
desire
to
have
more
technical
content
desire
to
have
the
content
labeled
a
little
bit.
G
You
know
almost
the
way
you
have
like
ski
runs
that
are
like
beginner
or
you
know:
green
blue
black,
like
have
the
content
labeled
a
little
bit
more
to
know
if
this
is
the
inner
content
or
intermediate
content,
etc.
You
know
the
I
know
we
go
back
and
forth
about
the
length
of
sessions
and
keynotes
and
that
one
was
almost
almost
evenly
split
between
people
that
thought
it
was
just
write
to
people
who
wanted
a
little
longer.
Obviously,
no
one
wanted
shorter
yeah
I.
Do
yeah
I'd
be
happy
to
share
the
survey
I've.
I
Seen
yeah
in
the
surveys
that
I
do
it's
the
same,
so
yeah
I
was
thinking
that
it
might
help
to
have
like
for
the
people
who
end
up
reviewing.
It
might
be
nice
to
have
like
a
little
wrap-up
or
synthesis
of
that
then
just
take
provide
context
of
like
you
know,
while
reviewing
we
should
consider
these
things.
I
think
I
had
shared
that
the
events
team
in
prior
years,
where
I
usually
provide
sort
of
like
a
steering
document
for,
like
you
know,
we
prioritize.
We
want
to
make
sure
and
prioritize
diversity.
I
You
know
and
representation
of
our
speakers
to
make
sure
that
we
have.
You
know
education.
You
know
location
around
the
world
language.
You
know
technology,
disabilities,
those
sorts
of
things
represented
on
our
speaker,
set,
as
part
of
you
know
that
as
well
as
you
know,
interesting,
like
trends
that
we
see
that
are
really
important
this
year,
that
we
think
need
to
be
represented
on
stage
as
well
as
the
feedback
that
we
had
gotten
last
year
that
we
need
to
make
for
providing.
I
G
I
can
I
can
get
a
document
like
that
started
and
it
might
have
you
know
a
little
bit
the
input
from
well-being
so
from
last
year,
which
was
a
wasn't,
everyone
doesn't
fill
it
out,
but
it's
certainly
a
sampling,
and
then
you
know,
maybe
it
could
be
a
little
bit
of
a
working
doc
and
people
can
that
are
on
board
with
being
part
of
the
CFP
review
process
can
just
weigh
in
and
that
could
help
guide
the
whole
process.
Yeah.
Absolutely.
I
G
I
I
I
think
that's!
Okay,
because,
like
you
need
lots
of
writers,
especially
with
the
number
of
you
know,
applications
that
will
receive
at
work
so
I
think
I've
seen
in
past
years,
often
times
reviewers
don't
get
the
full
set
reviewed.
If
you
have
enough
people
reviewing
that's
absolutely
okay
with
you
committee,
the
sort
of
the
producers
or
the
chairs
end
up
being
able
to
help
provide
assistance
and
then
ultimately
write.
The
executive,
director
and
team
help
make
sure
that
we've
covered
all
of
our
bases
and
our
meeting
the
project
need
is
well.
G
I
should
qualify
to
that
with
you
know
not
knowing
who
the
eg
is
going
to
be.
You
know
they
might
have
a
slightly
different
preference.
I
mean
we
have
had
project
for
the
IDI
does
not
want
to
be
the
final
decision-maker
on
this
and
purposely
does
give
that
role
to
a
co-chair
gave
it
to
co-chairs,
for
example,
so
I
you
know,
I,
don't
want
to
say
exactly
how
it'll
work,
but
you're
right
last
year
was
definitely
marked
the
first
with
the
final
sign-off
yeah.
I
A
G
A
J
G
And
then
the
other
item
too
I
just
wanted
to
talk
about
was
the
node
adoption
survey,
so
user
survey
that
we
usually
do
annually-
and
this
is
the
sort
of
larger,
comprehensive
survey
that
Tracy
Hines
has
really
been
instrumental
in
helping
us
with
through
the
years.
We
are
getting
ready
to
kick
that
off
and
I
was
similarly
looking
for
volunteers
who
might
want
to
help
not
completely
redo
the
questions,
because
we're
we're
hopefully
getting
to
a
few
years.
G
G
I
I
think
that
would
like
any
year
that
we
have
someone
who
can
provide.
You
know
a
language,
translation
or
a
couple
of
people
for
a
language.
Translation
like
I
would
love
to
have
that
call.
We
won't
need
that
yet,
but
I
know
Joey
was
essential
to
that
happening.
I
think
two
years
ago
and
spent
time
and
then
ended
up
I
think
crowdsourcing
a
little
bit
of
help
because
it
was
just
so
much
work.
I
I
B
A
G
I
So
we
would
probably
want
to
get
either.
You
know,
find
a
way
to
pull
the
survey
out
of
the
PDF
mode
or
upload
the
PDF
itself,
and
it
you
know,
comment
because,
yes,
y'all
are
right,
it
would
be
great
to
get
feedback
and
try
to
figure
out
ways
how
we
can
you
know,
modify
the
questions
without
destroying
the
multi-year.
A
I
B
But
it's
sort
of
like
I
think
we
can
just
we
can
get
a
better
sense
of
kind
of
community
ownership
and
by
doing
that,
once
a
year
and
yeah
I
think
so
I
think
the
suggestion
of
getting
like
the
PDF
into
an
issue
somewhere
with
you
know
some
of
the
expectations
up
front.
Saying
hey!
You
know
we
may
not
be
able
to
change
it
wholesale
because
we
need
to
consider
consistency,
but
we
want
to
make
sure
that
we
start
to
incorporate
feedback
year
over
year.
So
here's
your
chance
to
give
us
new
questions.
B
G
It
is
good
we
are
I,
actually
met
and
discussed
this
with
Joey
yesterday,
and
we
thought
it
was
smart
to
keep
this
as
a
node
survey.
One.
You
know,
there's
a
lot
being
worked
out
in
terms
of
what
marketing
support
and
what
the
needs
are
for
marketing
with,
and
data
and
research
across
all
the
projects-
and
you
know,
there's
probably
going
to
be
some
cheering
based
on
different
levels
and
obviously
node
is
at
that
impact
level,
as
are
I
know
for
others.
G
But
it's
already
60
questions
long
and
we
just
felt
that
we
should
keep
this
focused
on
node
I.
Think
there's
other
work
being
done
in
the
community
and
different
with
a
different
foundation
that
might
even
be
looking
at
the
JavaScript
overall
ecosystem
and
some
trends
and
how
technologies
are
being
used.
That
jory
thought
might
be
really
relevant
and
useful
for
us
to
sort
of
cope,
remote
or
share
and
leverage
so
that
we
might
not
even
need
to
do
a
second
or
survey
on
the
other
JSF
projects
that
make
sense.
Yeah.
B
E
A
Sarah,
this
is
a
this
is
a
tangent
for
one
I
love
the
idea
of
foundation
offering
service
as
a
service
for
crew
members
member
projects,
but
as
you
as
you
look
at
like
the
kind
of
state
of
j/s
survey
of
JavaScript
across
the
internet,
might
be
worth
reaching
out
to
the
folks
who
do
state
of
jeaious,
since
they
have
a
bunch
of
prior
art
and
have
done
really
well.
I'm.
Just
wanna
make
sure
it's
on
your
radar,
okay,
yeah
I.
G
A
Chugging
right
along
so
up
next,
we
have
a
PR
open
in
comic-con,
this
number
462.
This
is
adding
the
nodejs
outreach
initiative
to
the
readme.
So
for
folks
who
were
moving
on
on
the
last
call,
there's
been
last
couple
calls
there's
been
a
few
rumblings
of
the
need
for
a
new,
a
new
effort,
a
new
push
here.
We
had
three
or
four
tickets
across
multiple
repos,
asking
for
more
resources
for
community
organizers
and
greedy
advocates
to
really
be
able
to
organize
local
activities
and
have
support
in
organizing
local
activities.
A
For
folks
who
might
not
want
might
not
know
exactly
how
to
get
started.
So
from
this
we
spun
off
and
actually
had
our
first
inaugural
meeting
last
week,
we
spun
off
the
reboot
of
the
outreach
initiative
which
we're
gonna
be
focusing
a
lot
on
making
sure
that
local
organizers
actually
have
the
resources
they
need
to
organize
local
local
meetups
and
then
help
help
with
amplification
and
promotion
of
those
or
discovery
for
people.
There's
a
whole
lot
of
questions.
A
That'll
need
to
get
answered
here
in
first
clarifying
things
like
we
aren't
organizing
meetups,
who
are
helping
provide
resources
and
then
helping
people
connect
with
local
ones,
so
we're
very
much
in
a
service
and
resourcing
position,
not
in
a
organization
position,
but
you
know
there's
a
huge
ask
from
from
folks
around
the
community,
there's
a
huge
opportunity
here
to
get
people
connected
and
help
amplify
the
reach
of
these
things.
Ways
that
we
haven't
before
and
psyched
to
see
what
we
can
do.
There's
a
lot
of
work
here.
A
It
looks
like
we
have
a
few
ship,
it's
on
the
yeah,
a
few
approvals
on
the
PR
already
so
barring
any
strong
naysayers
here,
hopefully
they're
right,
I'm
gonna,
merge
this
in
and
then,
if
you're
I'm,
just
gonna
make
a
CTA
here.
If
you're
interested
in
helping
out
see
how
we
can
provide
extra
support
for
these.
These
types
of
organizers,
like
we're
gonna,
start
our
regular
meetings
every
other
Tuesday.
A
Awesome
I'm
seeing
this
ship
it's
rollin
so
this
week
and
part
of
that
is
also
a
oh,
hey
owner.
Welcome
back
yeah,
so
part
of
that
is
also
an
introduction
to
it's
a
good
segue
into
our
next
issue.
We
have
two
Jewish
folks
on
this
call
have
been
engaged
elsewhere,
one
of
which
Ahmad
always
I,
have
an
PR
open
for
his
nomination
here
at
calm,
calm
and.
A
A
For
always
so
we
we
haven't
had
a
new
member
in
in
a
while
at
a
new
member
nomination
in
a
while,
so
I
I
would
like
to
start
the
the
tradition
just
so
it
becomes
a
normal
thing,
even
if
we
haven't
done
it
already
of
having
a
small
private
session
at
the
end
of
meetings
where
we
have
new
member
nominations.
Just
you
know,
I
make
sure
people
have
the
space
to
give
get
feedback
and
say
hey,
okay
or
or
nice
in
in
a
private
venue.
A
F
I
was
just
gonna
say
that
there
was
an
issue
opened
issue:
465
been
Tyrael,
offering
a
resignation
in
the
palm
come
so
I
went
ahead
and
PR
do
this
at
the
beginning
of
the
meeting.
Just
to
help
with
that.
But
I
did
just
want
to
say
thank
you
to
Ben
for
the
veep
work
he
has
done
over
the
past
year.
Plus
he's
been
a
member
and.
A
Thanks
for
participating
in
the
community
can
be
appreciated,
then
a
hundred
percent
Ben's
the
Ben's.
The
reason
why
the
outreach
initiative
is
retaking
off
right
now
and
he's
done
he's
contributed
a
lot
over
the
last
year
year
and
a
half
as
well
so
yeah.
Thank
you
for
surfacing
that
dirty.
It's
important.
K
I
just
wanted
to
continue
what
Sara
mentioned
towards
the
end
or
towards
the
end
of
which
at
about
the
node
adoption
survey,
so
I
think
such
service
sounds
like
a
great
idea
for
the
outreach
initiative
program
like
getting
people
on
board.
So
I
really
don't
have
much
details
about
the
survey
thing
but
I
think.
If
we
conduct
these
surveys
and
something
like
the
state
of
the
JavaScript
which
you've
shortly
mentioned,
they
can
be
a
good,
adding
value
to
the
outreach
initiative.
K
A
G
G
A
I'll
I'll
get
you
two
connected
over
over
email.
I'll
write
the
intro
email
after
this.
Thank
we'll,
see
we'll
see
how
we
can
you
know
how
we
can
help
service
no
more.