►
From YouTube: Node.js End User Feedback Initiative
Description
B
B
Michael
Dawson
and
I
had
a
great
sit-down
with
Greg
Wallace
of
the
node.js
Foundation,
the
Linux
Foundation
this
past
week
at
while
I
was
at
Kubek
on,
and
you
know
we
we
came
up
with
some
some
really
nice
insights.
You
know
the
most
notable
takeaway
from
that
was
through
the
existing
efforts
of
the
noches
user
survey.
B
We
have
a
list
of
folks
that
are
already
opted
in
and
engaged
in
providing
feedback
data
that,
with
the
help
of
the
foundation
team,
we're
able
to
go
back
and
you
know,
do
some
targeted
outreach,
so
yeah,
that's
a
real,
exciting
take
away.
Then
we're
going
to
touch
on
the
the
plan
today
for
the
the
rest
of
the
year
and
look
on
into
the
the
next
year.
B
I
expect
that
the
majority
of
our
time
today
to
be
occupied
with
sharing
around
the
you
survey,
and
you
know,
feedback
from
from
Greg,
so
Greg
welcome
thanks
for
joining
us.
And
can
you
kick
us
off
with
a
bit
of
an
overview
of
what?
What
the
you
that
the
survey
is,
and
you
know
what
was
the
cadence
of
it
just
you
know
whom
that
the
folks
here
don't
have
the
context
of
what
would
the
survey
yeah.
C
C
You
can
still
respond
to
it,
we're
already
over
1,500
respondents.
So
it's
a
it's
a
it's
it's
obviously
you
know
as
percentage
of
the
total
number
of
node
users
out
there,
it's
it's
not
a
large
percentage,
but
it's
statistically
significant
as
a
sample,
meaning
that
the
insights
that
we
can
pull
from
this
data
set
are
really
really
useful.
So,
as
you
mentioned
Dan
one
of
the
things
that
we
do
in
the
survey,
it's
it's
completely
anonymous
right.
C
You
don't
have
to
tell
us
the
company
you
work,
for
you,
don't
have
to
give
us
your
name,
your
email
address
or
anything,
but
we
do
say
if
you
would
be
willing
to
be
contacted
by
the
foundation.
As
part
of
you
know,
additional
research
efforts,
you
know,
please
provide
your
email
address,
and
so
you
know
we
get
a
significant
number
of
people
every
every
time
we
do
the
survey
who
who
are
open
to
that
and
so
I.
You
know
with
this
community.
Driven
effort
to
you
know
really
get
into.
C
You
know
much
greater
technical
detail
from
end
users
right
as
I
understand.
You
know
the
mission
of
this
of
this
working
group
with
Rick.
It's
perfect
right.
We
I
can
I
can
put
together
an
email
I
can
send
out.
I
can
sort
of
give
a
top-line
summary
of
your
your
efforts
and
your
your
your
your
interest
in
speaking
with
these
folks
and
then
have
an
opt-in
click
right
where
they
can,
you
know,
say
yeah
totally
more
than
happy
to
help
or
hey
I've
changed
jobs
right
or
hey.
C
You
know
I
just
don't
have
the
time
right
now
and
they
just
delete
the
email
and
no
harm
no
foul.
So
that's
one
way
that
I
can
see
the
work
that
that
we've
been
doing
in
the
foundation
side
on
this
survey,
you
know
being
supportive
of
the
effort
that
you've
got
going
on
here.
The
other
way
is-
and
we
spoke
about
this
also
last
week-
is
you
know
for
the
for
the
surveys
that
are
closed
right,
so
the
one
we
did
in
2016
and
then
the
one
we
did
the
beginning
of
this
year.
C
What
I-
and
this
is
still
on
my
to-do
list,
but
I'll
more
than
happy
to
go
in
there
and,
like
you,
know,
scrub
out
all
of
the
PII
information
right
and
and
give
you
those
datasets,
because
I
think
you'll
find
that
there's
a
lot
of
useful
information
in
there.
A
lot
of
insights
that
you
can
get
just
by
you
know
running
some.
C
You
know
some
pivot
tables
right
and
and
looking
at
the
responses
that
people
provided,
and
so
you
know
that's
like
right,
something
that
you
know
the
foundation.
Is
you
mean
it's
very
aligned
with
our
mission
right.
We're
here
to
you,
know,
help,
accelerate
and
support
the
development
of
this
critical
technology
and
anything
that
we
can
do
to
make
it
easier.
For
you
know,
all
of
you
in
the
community,
to
you
know,
identify
areas
that
need
improvement.
You
know
is
is
something
that
we
want
to
do
so.
B
A
B
Great
well
thanks
great
that
that's
super
helpful.
Now
we
we
went
on
to
to
have
a
discussion
about.
You
know
not
only
how
we
plug
into
this,
but
the
benchmarking
workgroup
came
to
the
community
committee,
and
you
know,
then
that
this
group
that
the
NGOs
our
feedback
group,
you
know
volunteered
to
taken
and
begin
building
out
feedback
for
benchmarking
working
groups
needs
Greg
yeah.
We
asked
for
for
your
assistance
in
in
helping
us
craft
the
the
survey
and
also
have
you
know
a
central
place.
B
Your
foundation
managed
location
where
the
data
is
being
collected,
so
we
can
basically,
you
know,
set
aside
the
responsibility
of
handling
private
data.
For
now,
as
were
bootstrapping
this
initiative,
did
you
have
an
opportunity
to
look
into
that?
What
that's
going
to
take
and
if
it's
going
to
be
possible
for
the
the
foundation
to
set
that
up
for
us.
C
Yeah
so
I
like
it's,
it's
totally,
not
a
problem
at
all.
For
me
to
get
the
survey
into
we
use
Survey,
Monkey
right
and
so
that
that's
not
a
problem
at
all
the
the
the
part
that
I
guess
I'd
like
to
direction
from
you
all
on
is
you
know,
I
just
need
to
know
when
the
survey
is
final,
so
the
you
know
I'm,
not
a
market
research
expert,
you
know
and
I
I'm,
not
even
not
even
close,
and
so
we've
got
a
somebody
either
are
we?
C
And
so
so?
We've
got
we
so
the
Linux,
so
the
Linux
Foundation,
more
broadly,
multiple
projects,
but
I've
I,
spearheaded
at
the
node
foundation
working
with
somebody
who
is-
and
this
fits
all
she
was
right-
is
market
research
and
and
quantitative
market
research
through
surveys
on
principally
she
does
a
little
bit
of
qualitative
stuff,
but
almost
all
of
its
quantitative
and
so
I
asked
her.
C
I
took
the
survey
that
you
all
had
crafted
off
of
github
I,
put
it
into
a
Google
Doc
so
that
she
can
sort
of
more
easily
add
comments
and
things
and
she
did
and
that
was
sent
to
Michael
and
to
you.
Okay,
Michael
provided
some
responses,
but
most
of
the
questions
were
or
comments
were
not
addressed
and
I'll
say
you
know
the
the
single
biggest
piece
of
feedback
that
she
provided
was
every
single
one
of
the
questions
in
there
I
think
almost
without
exception.
C
Maybe
there's
one
is
what's
called
an
open-ended
question
right,
which
means
that
you're
gonna
have
to
it's
gonna
make
your
job
a
lot
harder
when
you
analyze
the
data
right,
because
you
know
it's
a
lot
harder
to
identify
trends
when
it's
free
text
right
unless
you
know
Hadoop,
you
know
sort
of
you
know,
data
scientist
and
have
access
to.
You
know
that
kind
of
unstructured
data.
C
You
know
sentiment
analysis,
yadda,
yadda
yadda,
which
I
don't
and,
and
that's
why
Polly,
the
researcher
recommended
that,
wherever
possible
right,
we
do
our
best
to
change
what
are
currently
open-ended
questions
into
what
she
calls
closed
questions
and
all
that
means
is
you
list
a
series
of
options
to
pick
from
now.
It's
very
likely
that
some
percentage
of
respondents
are
going
want
to
respond
in
a
way
that
isn't
provided
among
the
lists.
C
You
know
that
we
come
up
with,
and
so
you
always
have
to
have
another
category
right
and
but
if
you
you
know,
if
you
know
the
subject
that
you're
asking
about
as
well
as
we
do,
you
usually
get
more
than
90%
right,
95,
98
percent
of
respondents
who
find
among
the
options
in
the
multiple
choice
list
that
you
provide
the
one
that
they
want
right
or
in
some
cases,
the
ones
that
they
want.
It
doesn't
have
to
be
right.
C
Just
because
it's
closed
does
it
mean
it
has
to
be
single
right,
single
option
right,
you
can,
you
can
say,
and
the
question
choose
all
that
apply,
but
it
just
is
going
to
make
your
job.
You
know
after
you've
done
the
survey
and
you're
analyzing
the
results
so
much
easier
right.
Instead
of
having
to
like
read
effectively,
you
know
n
number
of
entries
times.
C
M
number
of
questions
right,
so
I
didn't
see
that
done
in
the
in
the
Google
Doc
and
I
just
wanted
to
make
sure
that
we
had
an
opportunity
to
talk
about
that
because
I'm
more
than
happy
to
put
the
thing
in
as
it
is
now
into
Survey
Monkey
and
put
the
and
the
link-
and
you
know
we
can
go
to
town
and
we'll
help
promote
it
and
all
that
sort
of
stuff.
But
I
just
want
to
make
sure
that
everybody
understands
that
if
you
get
250
300
400.
C
B
A
So
this
is
actually
yeah.
This
is
we
actually
you're
I
actually
outlined
a
little
bit
of
these
answers,
because
this
is
exactly
kind
of
what
I
was
saying
a
little
bit
ago
about
this
surveys
that
we
need
to
have
that
kind
of
close
ended
here.
Your
options
you
can
fill
in
other
if
you
need
to
so
I
think
we
actually
do
have
that
already.
We'd
have
to
go
dig
it
up.
C
C
So
yeah,
that's
my
only
thing
and
you
know
I'll
just
say:
I
mean
you
know:
Dan
I
never
cease
to
be
surprised
by
the
level
of
engagement
that
the
node
community
has
I
mean
you
know
for
us
to
get.
You
know,
1,400
responses
on
the
survey
that
we
did,
the
the
most
recent
one,
not
the
one,
that's
open
now.
The
most
recent
one,
which
you
know
Tracy
and
I
will
both
freely
admit
was
a
bear.
I
mean
it
was
a
probably
a
25
minute
survey
and
1,400
people
finished
it
right.
C
So
you
know
if,
if
all
you
really
want
is
a
handful
of
highly
targeted
responses,
then
you
know
I
would
say:
let's
factor
that
into
our
promotional
strategy,
because
putting
it
out
on
the
node
foundation
or
node.
You
know
no
js'
twitter
handle
is
gonna.
Result
in
you
know
many
many
many
many
many
more
than
that
right
so,
but
you
know,
let's,
let's
make
sure
that
we're
completely
aligned
because
I
don't
want
you
guys
to
end
up
with.
C
C
B
Turny,
you
know,
since
you,
you
looked
up
that
sort
of
bit
of
history
in
community
committee.
You
know
that
predates
this
initiative,
maybe
in
in
the
in
the
meeting
issue,
if
you
could
drop
in
that,
will
get
those
folded
in
you
know.
The
benchmarking
working
group
is,
you
know,
excited
to
get
more
answers,
but
we
are
also
excited
to
get
good
answers
and
help
help
make
sure
that
the.
B
Help
make
sure
that
those
who
come
to
us
in
the
future
right,
we
said
you
know
we're
learning
as
we
basically
begin
to
provide
services
to
the
rest
of
the
community
project,
and
it
sounds
like
you
know,
we're
whether
we
like
it
or
not,
going
to
get
a
lesson
in
you
know:
data
data
gathering
in
statistics,
so
that'd
be
fun.
Yeah.
A
It
looks
like
I
I
gave
the
suggestion
on
one
of
the
questions
and
then
from
there
we,
it
was
suggested
that
the
benchmarking
working
group
just
wanted
to
do
kind
of
broad
text
area
type
questions,
so
I
didn't
continue
to
get
those
all.
But
honestly,
like
looking
at
the
questions,
it
really
shouldn't
be
hard
for
us
to
slap
down
a
multiple
choice.
It
with
other,
especially
since
some
of
them
already
provide
that
it
shouldn't
be
a
huge
undertaking.
B
B
A
B
Well,
yeah
yeah
I'm,
you
can
put
it
out
there.
We're
probably
gonna
mess
this
up
a
bit
in
the
first
pass.
You
know,
and
you
know
it
sounds
just
just
using
the
example
of
this
broader,
no
Jess
user
survey.
You
know
took
the
the
first
year
to
kind
of
work
out
some
of
the
the
kinks
and
you
know
now
there
are
not
a
good
smooth
cadence,
so
you
know
you
know,
try
to
do
our
best,
we're
hoping
to
get
the
survey
out
over
the
the
holidays.
B
You
know
having
a
meeting
me
de
a
sort
of
insight
problem
like
like
benchmarking.
We
thought
that
might
be
a
good,
a
good
opportunity
over
the
holidays.
You
know
during
the
downtime
over
the
holiday
holiday
breaks
that
many
people
across
the
world
are
having
to
sit
down
and
you
know
provide
some
more.
You
know
thoughtful
responses
to
benchmarking.
A
A
B
Great
well
so
I'll
have
a
look
at
the
you
know.
The
survey
that
that's
teed
up
and
I'm
gonna
try
to
wrap
that
up
by
the
end
of
next
week,
so
we
can
get
that
published
and
begin
gathering.
Some
data
I
think
thank
you,
Greg
for
you
know
being
available
and
and
making
that
happen.
Greg
do
you.
When
do
you
turn
into
a
Christmas
pumpkin.
C
C
Is
this
supposed
to
be
single
option
or
can
people
you
know,
select
multiple,
so
you
know
stuff
like
that,
but
and
once
I
get
it
coded
into
Survey
Monkey
I'm
gonna
send
it
as
a
preview
to
I,
guess
you
Dan,
but
to
whoever
else
you
want
to
send
it
to
so
that
you
can
actually
go
through
it
and
be
like
yep.
This
is
all
functioning
the
way
it's
supposed
to,
or
you
can
say.
Oh
no.
C
This
question
was
supposed
to
be
required
and
it's
set
as
not
required,
or
you
know
whatever
stuff
like
that
when
you
need
us
catch
last-minute
things
and
then
once
we're
satisfied,
you
know
we'll
we'll
open
it
I'll
send
you
the
link
and
you
know,
and
then
we
may
have
a
little
bit
of
a
delay
in
terms
of
like
sending
it
out
on
the
node
Twitter
handle,
but
I
should
be
able
to
make
something
like
that
happen.
You
know
like
we
can
just
be
monitoring
and
retweet.
You
know
your
tweets
also.
C
C
Why
is?
Why?
Is
our
the
node
Foundation
survey
bilingual?
Yes,
we
we
did
that
because
we
wanted
to
make
sure
that
we
received
good
responses
from
all
of
the
users
in
China
and
and
and
it
was
really
I
can't
I'm
trying
to
remember.
Why
was
a
big
piece
of
feedback
we
received,
but
Tracy
pines,
who
was
really
like
my
partner
in
crime
on
the
survey
for
the
last
two
years?
C
D
Yes,
actually,
the
my
question:
it
was
mostly
based
on
I'm
pretty
sure
in
China.
There
are
a
lot
of
not
GS
users
and
that's
probably
the
reason,
but
you
guys
cannot
do
it
separately.
I
mean
English
and
Chinese
version
for
the
survey,
because,
probably
in
the
future,
there
might
be
some
possibilities
like
say,
for
example,
German
users,
something
like
that.
D
C
No,
it's
a
great
it's
a
great
point
and
we
talked
about
this
and
it
may.
It
may
come
down
to
a
limitation
of
the
survey
software
that
we
use
because
the
what
we
want
to
what
we
don't
want
to
have
to
do
is
because
if
we
do
multiple
surveys,
the
way
I
understand
it
right
is
with
Survey
Monkey.
If
you
do
a
separate
survey
in
each
language,
then
you
have
separate
data
sets
right.
C
But
I
I
agree.
It's
a
good
point
and
you
know
we
we
we
tried
to
be
responsive
to
the
community
and
nobody
from
you
know
like
Latin,
America
or
Europe,
or
really
anywhere
was
indicating
that
the
language
was
a
barrier
for
them.
They
were
all
fine.
You
know
responding
to
the
questions
in
English.
It
was
the
the
only
place
where
it
was
really
preventing
a
significant
number
of
people
from
responding
according
to
the
feedback
that
we
received
from
the
community
was
was
China,
so
that
was
kind
of
how
we
made
the
decision.
A
Also
like
to
chime
in
on
that
and
say
like
English
to
Chinese,
that's
probably
the
biggest
barrier
in
language
and
like
I'm,
actually
looking
at
numbers,
I'm
working
on
a
project
right
now,
I'm
looking
at
numbers,
it
looks
like
Chinese
about
is
literally
the
second
biggest
market
for
nodejs.
That's
not
English
speaking,
so
it's
really
like
choosing
Chinese
is
that
secondary
option
is
hitting
the
largest
possible
target
with
the
largest
possible
barrier.
A
So
just
doing
that
on
that
kind
of
first
iteration,
you
know
as
the
foundation
and
you
know,
gets
feedback
from
the
end
user
feedback
initiative
and
gets
help
from
us
hitting.
That
is
a
really
important
thing,
because
that
basically
increases
the
surface
area
of
responses
that
we
can
get
effectively
and
get
kind
of
a
me
tap
into
the
the
Chinese
head
of
note
at
node,
end
user.
It
has
historically
for
me
what
I've
talked
to
you
been
a
very
underrepresented
group
in
discussions
around
ojs
and
usage.
A
So
you
know
I
think
it's
the
best
possible
option
at
the
front
and
then
from
there
you
know,
I
think
it
that
can
actually
be
on
the
end
user
feedback
initiative
to
go
and
help
the
foundation
to
get
that
tooling,
set
up
or
figure
out
a
way
we
can
get
that
working
properly
in
a
way
that
we
can
go
enable-
and
you
know
another
another
thing-
I
actually
think
Tracy.
What
we're
talking
about
as
a
part
of
this
is
getting
people
to
translate
it
I
know.
A
C
A
C
Right,
that's
right.
We
did
that's.
That's
absolutely
true.
The
community
offered
that
Chinese
translation
and
it
was
a
wonderful
wonderful
example
of
collaboration,
and
it
was,
you
know,
really
very,
very
valuable.
As
for
the
reasons
that
you
described
thanked,
that
was
thanks
for
adding
that
that
was
yeah
really
good.
So
yeah
I
am
a
great
point.
Thank
you
for
bringing
that
up.
Okay,.
B
B
Greg
is
is
going
to
be
providing
us
the
data
and
we're
going
to
be
posting
it
here
in
the
user,
feedback,
repo
and
then
I
would
love.
Your
participation
in
you
know
boasts.
You
know
helping
us.
You
know
understand
how
we
capture
that
data,
and
you
know,
share
that
data,
and
you
know
we.
We
welcome
your
feedback
on.
B
You
know
the
insights
that
you're
able
to
draw
from
it
and
the
insights
that
and
you
know
we
want
to
make
sure
that
we
share
that
context
back
to
you
know
the
noches
foundation.
So
you
know
if,
if
we're,
you
know
gaining
greater
insight
or
additional
value
out
of
this,
you
know
that
can
be
shared
and
circulated
and
improve
upon
the
processes
for
next
year.
A
C
Yeah
and
that's
the
part
that
I
haven't
done
yet
right
but
is
I.
The
Survey
Monkey
makes
it
super
easy
to
export
the
data
in
a
variety
of
formats,
and
so
what
I'm
gonna
do
is
export
the
data
from
the
previous
two
date.
Surveys
that
are
that
are
closed
right
and
as
as
a
CSV
right
and
then
go
in
and
remove
the
columns
where,
for
example,
we
say
you
know
if
you
would
be
open
to
being
contacted
by
the
foundation,
please
provide
your
email
address
like
I'll,
remove
that
column
and
delete
it
right.
C
There
are
a
few
you
know,
so
it's
stuff
like
that
like
and
so,
and
then
I'm
just
gonna
like
go
through
sandy
check.
It
look
it
over,
but
we
don't
ask
for
people's
name.
We
I
think
we
asked
people
to
tell
us
what
company
they
work
for,
but
it's
optional.
So
you
know,
depending
on
how
everybody
feels
I
may
or
may
not
remove
that
column.
So,
basically,
that's
it
right.
C
There's
like
a
there's
like
a
respondent,
ID
field,
I'm
gonna
leave
that
in
there,
because
you
know
it
may
be
the
case
that,
but
that's
like
you
know
some
random
number
that's
assigned
to
people
as
they
respond
to
the
survey.
So
it's
not.
It
doesn't
correspond
to
any
information
about
that
individual
elsewhere
right.
It's
completely
unique
to
the
to
the
survey
but
leave
it
in
because
you
know
you
all
might
start.
C
Looking
at
the
data
and/or
the
benchmark
working
group
might
start
looking
at
the
data
and
say
they're
paid
Gregg
there's
you
know
four
or
five
folks
who
you
know
in
one
of
the
open
text.
Fields
offered
some
interesting
thoughts
around.
You
know
benchmarking
and
we
would
love
to
follow
up
with
them.
Can
you
go
back
and
check
and
see
if
they
indicated
that
they
would
be
willing
to
be
contacted
by
the
foundation
and
the
only
way
I'll
be
able
to
do?
That
is
if
you're
able
to
tell
me
right
the
the
the
respondent
ID.
C
So
it's
you
know,
it
gets
like
it's
really
it's
a
critically
important
piece
of
work
that
it
be
done
right,
because,
obviously
you
know
it
would
be
a
big
breach
of
privacy
too.
You
know
mistakenly
reveal
people's
email
addresses,
but
it's
not
complicated
right
like
it's,
a
pretty
straightforward
thing.
I
just
have
to
you
know,
sit
down,
you
know
do
it.
You
know
quality
check.
My
work,
you
know
make
sure
that
you
guys
are
comfortable
with
what
you
have
and
then
you
know,
and
then
we
can
publicize
it
going
forward.
C
I
didn't
see
anything
in
the
benchmark.
Survey
and
I
might
be
missing
it,
but
I,
don't
recall
seeing
anything
that
asked
for
any
personally
identifiable
information.
So
I
don't
think
we
have
anything
to
worry
about
there
right,
I
think
that
data
set
should
be
completely
clean
and
completely
anonymous.
You
know
so
I
think
we
should
be
fine.
B
Great
yeah
I
think
the
you
know
my
you
know:
knowledge
of
the
existing
survey
you
know,
and
especially
the
non
open-endedness
of
those
questions,
I
think
lends
itself
to
fewer
privacy
concerns
when
I
think
about
the
benchmarking
survey
and
all
those
open-ended
questions
you
know
they're,
you
know
you
know,
III
do
think,
there's
potential
there,
for
you
know
an
expanded
signature
if
someone's
trying
to
start
hard
to
be
anonymous.
So
you
know
something
first
to
consider
Greg.
A
Do
you
think
you
could
just
share
like
when
you
feel
that
the
data
is
anonymize?
Do
you
think
you
could
share
these
data
set
with
the
members
of
the
inducer
feedback
initiative
beforehand,
just
to
see,
if
like
we
feel
it
is
anonymized
as
well
cuz?
You
know
when
I
was
taking
it?
The
survey
Lester
I
felt
like
oh
yeah.
C
Absolutely
I
mean
I
I
appreciate
that
offer
and
I
would
welcome
that,
and
you
know
I
mean
you
know.
Maybe
what
we
need
to
do
is
remove
all
open-ended
right
right,
which
is
going
to
take
a
little
longer,
but
would
you
know
I
think
maybe
be
you
know
in
addition
to
removing
company
name
I'm
a
little,
you
know,
title
is
a
well
again
like
we
can
leave
the
responses
to
multiple-choice
title
right
and.
B
C
Somebody
cuz
like
that
might
be
another
way
if
somebody's
got
a
very
unique
title
that
wasn't
among
the
options
in
the
drop-down
and
they
rooted
in
as
other
write
that
that
they
could
then
become
identified
and
so
yeah,
like
I
I,
think
it's
I'm
really
glad
that
y'all
are
thinking
about
this
hard
and
and
I.
Think,
let's,
let's
you
know,
look
it
over
and
make
sure
that
we're
all
comfortable
with
it
before
we
make
it
public
great.
B
Great
that
sounds
good,
yeah
and
and
and
I
think.
If
we
err
on
you
know,
especially
in
our
first
pass
here
on,
you
know,
the
side
of
caution
will
be
well
served
and
then
you
know
will
at
least
have
the
opportunity
to
share
you
know.
Maybe
in
the
next
iteration
hey
you
know,
these
data
fields
are
potentially
going
to
be
published
as
a
part
of
our.
B
Can't
see
the
chat,
so
we
have
you
know
now
that
we've
gotten
our
you
know
basic
set
up.
We
have
begun
to
do
outreach
and
invite
folks
to
to
you
know,
send
an
email.
You
know
we're
we're
intentionally
using
email
here
and
and
not
just
github,
because
we
were
wanting
to
engage
end
users
and
user
companies.
B
You
know,
and
you
begin
the
process
of
really
you
know
capturing
and
and
creating
a
bi-directional
channel.
So
you
know,
surveys
are
great,
but
you
know:
I
I
believe
that
the
reason
why
we
have
such
an
engaged
community
is
because
in
node
we
explicitly,
you
know,
establish
an
expectation
that
you
can
participate.
You
can
join
and
you
know
that
your
opinion
is
valued.
So
in
January
we
have
an
initial
feedback
session
which
I
will
set
up
and
that
feedback
is
you're
going
to
be
inviting
companies
who've
recently
chosen,
nodejs
or
evaluating
nodejs.
B
Aren't
the
precipice
of
inviting
in
engaging
with
with
no
Jess
and
using
the
technology
to
you
know,
share
amongst
those
who
have
decided
and
those
who
are
trying
to
decide
and
III.
Think
that'll
be
a
fascinating
exploration.
You
know
having
been
around
now,
for
you
know,
seven
years
and
seeing
those
choices,
I,
I'm
I'm,
expecting
some
some
pleasant
surprises.
You
know,
as
that
impetus
for
adopting,
know,
Dias
evolves
and
changes.
So
we
have
that
penciled
in
for
the
the
12th
of
January.
B
That
will
be
the
first
session
in
the
new
year
and
our
next
meeting
then
in
in
February,
we're
going
to
you
know
open
the
the
public
session
for
enterprise
user
feedback
so
really
excited
to
you
bring
in
you
know,
enterprise
members.
We
have
a
menagerie
of
tell
us
who's
joining
us
today
and
you
know
he's
been
very
much
engaged
with
you
know.
B
The
enterprise
user
community
tell
us
is
a
big
telco
in
in
Canada,
so
I
wanted
to
make
sure
that
that
those
were
on
everybody's
radar
go
back
to
the
the
the
top
level
screen
now
December
29th
I
was,
you
know,
ready
to
cancel
this
tierney.
Are
you
going
to
be
offline
during
that
the
period
of
time
I
lean
on
you,
I.
A
B
Absolutely
not
so
III
just
need
you
know
the
technical
individual
who
has
the
ability
to
flip
on
the
YouTube
stream.
You
know,
I
was
planning
on
canceling
that,
but
with
the
the
benchmarking
working
group
survey
being
in
flight
and
our
objective
to
you
know
to
help
you
know
that
have
traction
over
the
the
holidays.
I'm
thinking
that
you
know,
I
can
probably
make
the
twenty-ninth
work,
and
you
know
we
could.
B
Off
we
go
okay,
cool
great,
well
I'll,
keep
that
on
the
calendar
then-
and
you
know
hopefully
we'll
have
at
least
the
initial
data
to
get
from
the
the
benchmarking
working
group
or,
if
nothing
else,
you
know
just
you
know,
it'll
be
a
moment
to
promote
that,
and
you
know,
grow
awareness
and
it'll.
Give
me
an
opportunity
to
anchor
some
of
the
work
in
preparing,
for
you
know
the
that's
the
sessions
in
January
and
February
great
well.
B
That
gets
us
through
our
agenda
items.
I
wanted
to
open
the
floor
to
any
questions
or
comments.
Before
we
leave
Diego,
you
know
you
decided
to
join
us
and
you've
been
enthusiastic
about
building
community
if
I,
remember
correctly
in
in
Brazil
around
node,
you
know
was.
Was
this
meeting
helpful
to
you?
Is
this
going
to
be
something
that
you're
new
you're
going
to
be
able
to
leverage
to
expand
awareness
in
your
local
community.
E
A
A
I
would
like
to
request
that
that
be
serviced
directly
in
the
comm.
Come
it's
been
surfaced
in
the
TSC
and
the
user
feedback
suggesting
that
it
will
be
proposed
as
a
part
of
the
calm
calm.
Just
it's
not
really
been
discussed
with
the
calm
cuff
you
know,
and
so,
but
it
has
been
discussed
with
the
other
parties.
So
I
would
like
to
request.
Did
that
be
suggested
and
brought
up
to
the
calm?
Calm,
it's
being
proposed
that
it
be
a
part
of
that.
B
So
you
know
that
effort
is,
you
know,
sort
of
in
conjunction
with
the
end
user
feedback
and
it's
backlogged.
Unfortunately,
I
was
I,
got
deathly
ill
after
Kubek
on
last
week,
and
so
it's
backlogged
on
me
just
being
sick
and
having
the
cycles
to
to
go.
You
know
set
up
the
initial
infrastructure
for
that.
So
that's
on
me-
and
you
know
that
is
you
know,
going
to
report
into
the
calm
calm
as
your
the
rest
of
the
end
user
feedback
initiative-
and
you
know,
that's
that's,
what's
happening,
I
guess.
A
You
know
afford
to
report
into
the
com-pub
to
concur,
needs
to
prove
that
it
reports
into
the
calm.
Calm.
That's
just
mainly
the
thing
I
want
to
make
sure
we
have
is
a
discussion
around
that
before
that's
like
finalized
is
to
you
know,
let
the
kumkum
know
it's
going
to
have
something
to
reporting
to
it
and
have
compound
agree
to
having
it
report
to
it.
That's
literally
it's
you
know.
It's
been
service
to
the
TSE
and
the
injuries
your
feedback
itself,
so
I
just
want
to
make
sure
that
discussion
is
also
happening.
A
Even
surfacing
meetings
are
happening
because
nobody
in
the
community
committee
knew
that,
except
for
myself,
getting
emails,
that
I
didn't
have
time
to
pay
attention
to
it.
The
time
unfortunately
see
ya
just
making
sure
that
the
information
is
surfacing
as
it's
happening
to
the
committee
helpful
great.
B
B
It
was
sort
of
slated
for
sometime
in
late
January,
so
you
know
that
that
that
group
won't
will,
you
know
not
be
coming
together
for
for
a
bit
of
time,
so
you
know
we
can
expect
activity
in
in
terms
of
your
landing
discussion
around
that
in
the
community
committee.
You
know
in
the
initial
section
sessions
at
the
beginning
of
next
year.
You
know
once
those
the
the
calendar
sort
of
stabilizes.
B
Great
well
thanks
every
for
joining
us
today.
Looking
forward
to
you
know
getting
our
first
big
work
product
with
the
benchmarking
working
group
out,
and
you
know
we'll
look
to
each
one
of
you
to
do
to
help
us
promote
that,
and
is
for
that
that
insight
that
we
can
improve
the
state
of
benchmarking
in
noches
project
thanks
everybody.