►
From YouTube: User Feedback Initiative Team Meeting - 2017/12/1
Description
A
B
B
B
Go
ahead
and
start
with
myself
and
then
I'll
go
around
the
list
and
call
folks
out
so
hi
I'm
Dan,
Shaw
I'm.
You
know
one
of
the
primary
coordinators
here
in
the
know,
just
end
user
feedback
group
and
currently
no
js'
at
large-
and
you
know
helping
out
with
with
this
initiative
and
a
couple
other
initiatives
around
the
project.
So
Tierney
I
guess
you
are
no
discount.
Yes,.
A
I
am
hi
I'm
Ginny
siren
I'm
polishing
up
is
no
J's
Foundation.
If
you're.
If
you're
looking
at
the
names
I
am
co-chair
of
the
committee
committee
I'm
a
developer
advocate
at
node
sorts
and
I
just
generally
try
to
help
around
node.js
community
and
should
be
in
community
and
everything
else.
Community
community,
yeah.
C
Michael
Dawson,
like
my
BMS
community,
lead
from
ojs,
also
chair
of
the
PSC
and
active
in
a
number
of
the
working
groups
and
in
particular
interested
in
in
this
one,
because
you
know
I
think
one
of
the
areas
we
can.
You
can
do
better
in
this
getting
more
direct
feedback
from
the
end-users.
We
have
really
good
connection
I
think
to
our
developer
community,
but
getting
some
more
feedback
from
our
end.
Users
would
be
great
and
that's
why
I
volunteered
to
be
the
Hong
Kong
champion
for
this
particular.
D
Me
yeah
hi,
everybody
I
am
hi
Anu
over
here,
so
a
little
bit
about
myself.
I
was
working
for
Microsoft
before
and
then
project
management,
a
lot
of
project
management
staff
around
software,
mostly
in
Romania
and
then
United
States
I
am
a
little
bit
in
entrepreneurship
and
right
now,
I'm
trying
to
help
the
user
feedback
and
I'm
I
would
like
to
get
more
in
in
volunteering
in
and
not
jeaious.
E
My
name
is
Mike
Hostetler
I
am
been
around
the
JavaScript
space
for
a
while
I'm.
Currently,
the
director
of
front-end
engineering
for
a
start-up
in
Chicago
called
raised
marketplace.
I
am
also
the
organizer
of
the
Chicago,
no
js'
meetup,
and
that's
about
it
right
now,
but
have
been
involved
in
community
efforts
with
javascript
in
various
forms
for
about
a
decade.
B
Excellent
all
right!
Well,
thanks!
Everybody
thanks,
really
robust
quorum
today
for
our
first
official
meeting,
so
I
want
to
go
through
this
a
little
bit
of
bookkeeping
here
in
the
agenda
and
we'll
get
into
a
couple
meteor
topics.
First
and
foremost,
we
established
the
the
cadence.
If
you
haven't
had
the
opportunity
are
ready
to
add
the
no
js'
calendar
to
your
links
in
the.
If
you
could
know
GS
orgs
last
calendar,
you
know
I
recommend
adding
that
to
your
whatever
your
cloud.
B
Calendaring
software
is
and
the
end
user
feedback
meetings
have
been
established,
Fridays
at
1700
UTC
noon,
eastern
eleven
a.m.
central
9:00
a.m.
Pacific
every
two
weeks
on
Fridays,
and
so
that
the
next
meeting
will
be
in
two
weeks
on
the
15th
I
guess
it
is
right,
so
really
appreciate
all
the
effort
that
went
into
sort
of
getting
that
set
up
and
getting
us
on
a
regular
cadence.
E
B
C
B
D
C
C
B
It
so,
in
terms
of
you,
know,
no
jest
users,
and
you
know
context
that
you
know
as
a
leader
of
the
the
technical
steering
committee.
You
know
what
in
the
survey
it's,
the
survey
is
largely
useful
for
kind
of
foundation
level.
You
know
gathering
of
information
and
not
necessarily
you
know
a
tool
designed
to
gather
feedback
for
the
the
technical
steering
committee
to
sort
of
optimize.
You
know
that
the
prioritization
of
what
we're
working
on
technically
you
know.
C
C
B
So
my
request
to
all
of
us
here
that
are
members
of
this
initiative.
If
you
haven't,
had
the
chance
to
go
complete
the
survey,
you
know,
let's
try
to
complete
the
survey
between
now
and
our
next
meeting
and
in
this
issue
number
eight.
If
you
find
anything
that
is
relevant
to
you
know
and
user
feedback
that
we
should
be
tracking.
So
if
there's
a
good,
you
know
question
that
that
you
know
deals
with
some
end
user.
Need
that
we
could,
you
know,
draw
that
data
into
what
we're
doing
here.
B
You
know,
let's
make
note
of
it
in
issue
number
eight,
and
you
know
if
there's
anything
that
we
want
to
carry
back
to
you
know
the
foundation
in
terms
of
you
know
how
we
can
improve
this.
How
we
can
you
know
seed
next
year,
survey
with
you
know,
context
and
contents
that
can
not
be
just
just
a
benefit
to
the
foundation
and
you
know
sort
of
the
state
of
the
ecosystem,
reporting
that
the
nodejs
user
survey
feeds.
C
I
think
we
should
almost
make
it
a
one
of
our
deliverables
for
the
year
is
to
you
know
we
can
look
at
the
existing
one
and
say:
okay,
we
understand
that
we're.
Obviously
this
is
the
first
meeting,
so
we're
just
kicking
things
off,
but
once
we're
a
little
further
in,
we
should
think
about.
You
know
how
we
should
influence
the
content
to
that
user
survey
to
you
know
achieve
the
different
types
of
goals
that
we're
trying
to
cover.
That's.
B
Fantastic
I
think
that's
a
great.
Let's
make
sure
we
capture
that
in
our
notes-
and
you
know
probably
worth
supporting
this
kind
of
covers
it,
but
we
should
you
know,
consider
you
know
capturing
that
context
and
pulling
that
back
into.
You
know
our
readme,
maybe
as
a
pull
request,
and
you
know
capture
that
that
you
know
that
is
an
express
intent
of.
C
C
A
I
think
some
kind
of
organization
around
that
what
might
also
be
beneficial
if
we
start
getting
more
feedback
around
that
like
more
bits
of
content
or
bits
of
context
that
can
help
having
something
like
a
label
or
you
know
and
just
having
a
label
or
you
know
one
of
the
you
know
Caban
boards
or
whatever.
That
is
projects.
A
C
I
was
just
thinking.
I
was
just
adjusting
an
issue
as
a
here's,
a
task.
We
use
that
to
figure
out
what
are
all
the
different
bits
and
pieces
we
should
do,
and
some
of
those
things
you
just
said,
are
great
suggestions
for
that
awfully
I.
Just
one
of
the
review
that
says
that
we
everything
we
should
be
doing,
that
we
have
wait
a
sec
there's
an
issue
or
something.
B
C
E
A
This
going
forward,
yeah,
so
I,
think
Michael
and
I
might
be
able
to
give
a
little
bit
of
context.
This
this
survey
is
a
an
annual
survey.
That's
released
and
Annette
like
the
the
results,
are
announced
it
an
interactive
and
the
next
survey
is
released.
It
note
interactive
and
effectively.
What
it
is
is
a
collection
of
data
around
the
usage
of
nodejs,
not
just
by
individual
developers
but
by
individual
developers
at
differing
levels
of
the
ecosystem.
A
So,
for
example,
you
know
at
you
know
a
Microsoft
or
had
tuned
Intel
or
at
a
you
know,
Comcast,
that's
something
a
large
scale
down
to
you
know
SMEs
and
startups.
It
is
attempts
to
gather
a
holistic
view
of
the
Noches
ecosystem
and
the
different
colleges
use
the
different
platforms
and
how
the
developers
and
how
the
users,
even
as
a
corporate
in
the
corporate
sense,
are
using
it,
and
then
we,
you
know,
share
that
back
to
the
ecosystem.
E
Cool
like
would
it
be:
is
there
data
from
previous
years
that
this
was
done,
and
could
we
get
access
to
that
data
to
be
able
to
get
some
trend
lines
here?
Yes,
and
probably
okay
I'd
like
to
create
an
issue
for
that,
just
to
you
know
get
it
so
we
could
do
some
analysis
and
I
think
that
would
help
direct
our
efforts
in
this
working
group
going
forward.
B
That
would
be
great,
and
you
know
that's
it.
That's
a
fantastic
opportunity
for
us
to
begin.
You
know
I
I,
half
expected
the
the
answer
to
be.
You
know
it's
attorneys
kind
of
to
be.
Oh,
we
have
to
privatize
our
data.
You
know
that
that
is
one
of
our.
You
know
areas
of
concern.
Well,
in
this
initiative
with
you're
capturing
this
data,
you
know
how
do
we
you
know
both
you
know
make
that
data
accessible
while
protecting
the
the
identities
of
the
end
users
that
are
that
are
sharing
their
data
with
us.
Yeah.
A
And
that
you
know
that
problem
has
been
solved
many
times
we
just
kind
of
have
to
settle
on
a
solution
and
make
sure
that,
since
we
are
doing
this
as
an
open
side
of
a
project
on
that,
we
are
managing
access
to
that
accordingly,
and
so
did
the
foundation
already.
Has
things
in
place
for
this
survey
monkeys
what
they
used
for
or
have
used
for
the
large
survey?
And
so
that's
a
likely
solution.
A
E
I
mean
I,
think
I.
Oh
that's,
I'm,
just
curious,
even
if
we
had
to
whatever
you
whatever
makes
sense
and
whatever
the
foundation
has
already
set
up,
is
totally
fine
getting
that
and-
and
this
is
I
think
maybe
the
purpose
we
can
get
some
of
that
document
and
the
issue
queue
so
that
we're
up
to
speed
on
it
and
can
support
that
work.
That's
already
been
done
so.
B
So
so
as
an
action
item,
I'll
reach
out
to
Greg
Wallace
and
maybe
to
continue
this
thread,
we
could
invite
Greg
Wallace
to
join
us
at
the
next
and
user
feedback
meeting
and
we
can
have
a
discussion
with
them
and
we
can
share
some
of
that.
That
context
and
the
data
with
us-
and
you
know
we
can-
we
can
also
through
that
establish
a
relationship
with
the
individual
inside
the
foundation,
who's
handling.
This
the
survey.
A
Has
also
raised
her
hand
to
offer
help
as
we
need
it,
so
I'm
I'm
happy
reach
out
to
her
with
any
specific
requests.
There's
several
the
points
we've
already
discussed
around
you
know
getting
the
data
and
understanding
it
and
I
think
is
like
that.
Getting
the
infrastructure
set
up
the
other
things
that
zippy
has
had
hands-on
experience
with
and
will
be
able
to
probably
hopefully
assist
us
I
mean
she
has
a
large
load
of
because
he's
only
doing,
but
she
is
a
resource
for
us
and
a
very
helpful
well.
B
I
know
that
this
data
is
fundamental
to
the
operation
of
the
foundation,
so
anything
that
we
can
do
to
you
know
get
more.
You
know
more
data,
and
better
data
through
will
definitely
be
appreciated.
So
we'll
maybe
I'll
put
an
offer
out
so
both
Greg
and
zippy
to
join
us
next
meeting
on
on
December
15th,
and
you
know
to
have
that
discussion
with
them.
B
All
right,
next
on
the
agenda,
a
benchmarking
team
request
for
survey
so
Michael
Dawson.
Would
you
mind
you
know
kind
of
giving
us
an
introduction
of
you've
got
a
lot
here
and
you
know
as
I
as
I
sort
of
digest
this.
You
know
I'm
trying
to
conceptualize
how
we
how
we
go
and
approach
such
a
you
know
a
meaty
potential
survey.
My
inclination
is
to
break
it
down
into
smaller
chunks,
like
the.
C
C
B
Yeah,
just
you
know
it's
being
so
text
base.
You
know
if
you
were
to
sort
of
pick
the
the
top
five
items
that
that
the
benchmarking
team
really
really
needs
to
know
about.
You
know
that
might
be
you
know
we
might
get
more
respondents
on
that.
Then
you
know
I'm
worried
with
with
you
know
a
15
question.
B
C
B
A
C
A
There's
this
this
kind
of
issue
of
how
long
it
is
it's
not
an
extremely
long
thing,
but
getting
people
to
write
long
form
answers
for
each
of
these
makes
it
a
long
thing
and
that's
you
know
in
this
issue,
that's
kind
of
why
I
was
trying
to
push
a
little
bit
on.
You
know
getting
multiple
choice
in
than
another
option,
because
you
know
some
of
these
questions.
You're
like.
What's
your
preferred
way
to
write
a
secret
is
code
callbacks,
async/await
promises
or
other
having
those
being
multiple.
C
A
And
I
mean
even
with
these,
you
know
you
can
also
do
depending
on
what
survey
tool
we
use
it,
which
I'm
guessing
or
you
going
to
use
Survey
Monkey
since
that's
what
the
foundation
is
already
using
I
believe
it
has
this
feature
where
you
can
terminate
a
survey.
If,
if
you
don't
need
additional
context
like
if
the
answer
no,
do
you
have
infrastructure
employees
for
trekking
performance
on
your
application,
we
can
then
cut
out
the
rest
of
the
questions
that
are
specifically
related
to
that.
B
B
C
A
C
Like
if
we
put
it
in
two
weeks
from
now,
is
everybody
gonna
be
way
on
vacation?
And
so
you
know,
the
timing
versus
you
know.
I
know
in
in
three
weeks
were
too
late,
but
right
two
weeks
too
late
is
one
week
like
if
we
actually
managed
to
review
it
next
week.
Would
it
still
make
sense
to
send
it
out
or
is
it
that
like
we
should
be
targeting
early
January.
A
B
C
B
B
B
C
B
E
Wouldn't
do
those
questions
I,
don't
feel
like
I
need
to
be
included
in
that,
but
I
would
love
to
see
a
set
of
those
questions
that
comes
out
that
could
be
delivered
in
a
face-to-face
format.
So
one
of
my
interests
and
preferences
for
next
year
and
availability
here
in
Chicago
is
sitting
down
and
meeting
with
directors
of
engineering,
VP
of
engineering
getting
conversational
feedback
one-on-one
again
as
the
meetup
coordinator.
This
is
actually
some
things
that
I
do
because
engineer.
Engineering
managers
want
to
find
out
about
how
their
engineers
can
participate
in
the
meet
up,
etc.
E
So
it's
so
it's
a
thing,
I'm
already
kind
of
doing
and
I'd
love
to
have
a
consistent
set
of
questions
that
aligns
with
work.
We're
already
doing
that
I
could
ask
and
bring
back
and
again
I
think
Dee,
Shaw
and
I
had
talked
about
this
briefly
at
a
meeting
to
her
a
few
times
ago,
but
you
know
making
sure
that
those
are
similar.
So
we
can
compare
the
beta
easily
would
be
great
as
an
outcome
of
this
effort
that
I
could
benefit
from
greatly
so.
C
B
Mike
and
yeah-
that
was
definitely
one
of
the
the
reasons
why
I
was
you
know
trying
to
pare
it
down
to
a
smaller
subset
was
actually.
These
are
great
questions
for
for
us,
though,
for
great
fodder
for
us
in
those
discussions,
and
if
we
can
pare
it
down,
then
we
can,
you
know,
go
through
do
an
initial
iteration
and
still
have
you
know
some.
B
You
know
additional
questions
that
we
can
go
back
and
iterate
through.
You
know
since
they're
so
interdependent.
That
may
not
be
as
feasible
this
this
time,
but
you
know
thank
you
for
bringing
that
up
and
it's
very
much
a
your
something
that
I'm
interested
in
doing
as
well
as
we
transition
the
next
question.
I'll
just
drop.
C
B
C
B
C
B
C
I
think
surveys
are
one
mechanism
but
I
think,
as
the
other
Mike
was
mentioning,
you
know,
in-person
high-touch
feedback
is
different
and
valuable,
so
this
is
just
sort
of
like
how
do
we
start
to
identify
the
first
set
of
people
we
might
invite
to
some
sort
of
ailment,
whether
there
they
may
not
be
in
person
but
they're
like
you
know,
verbal
on,
although
we
may
want
to
do
in-person
ones
too,
but
how
do
we
get
started
on?
Who
would
be
in
that
group?.
B
C
Give
you
a
to
give
some
ideas
so,
like
you
know,
I
one
of
the
CEOs
of
a
startup
in
montreal.
That's
using
no
jess
reached
out
to
me
and
we
were
going
to
chat
them.
You
know
one
of
the
things
I
thought
would
be
useful
to
like,
say:
hey.
Are
you
interested
in
joining
this?
My
VM
also.
Has
you
know
some
some
large
organizations
to
trouble
using
nodejs
and
I
was
thinking.
You
know
we
might
bite
one
of
them,
but
I
thought
it's
like
okay.
C
Do
we
just
want
to
find
anybody
who's
interested
to
start
with,
or
are
we
gonna
have
some
plan
in
terms
of
you
know?
Do
we
want
to
go
after
certain
sectors?
You
know
feedback?
Is
we
could
start?
We
just
really
get
add
a
lot
wherever
we
know
we
can
find
interested.
Let's
get
some
momentum
or
we
could
say
let's
prime
time
this
and
say
well,
we're
particularly
interested
in
people
from
this
I
do.
A
Think
that
coordinating
with
the
foundation
here
would
be
very
beneficial.
There
are
certain
verticals
that
the
foundation
has
identified
as
being
strong
right
now
and
are
looking
to
get
more.
You
know,
discussion
around
you
know,
service
is
one
of
them.
There's
a
bunch
of
others.
I
believe
they're,
actually
different
categories
on
the
node.js
collection,
our
son
Jake,
wants
IOT
is
another,
but
basically
you
know
getting
getting.
A
B
B
Let
me
let
me
share
a
tangible
case
that
that
you
know
I'm
going
to
sort
of
flesh
out
into
an
issue
and
and
put
forth
I
had
a
great
meeting
with
you
know
the
head
of
engineering
over
GoPro
yesterday,
and
you
know
they
were
really
interested
in
hosting
a
meet-up
down
in
in
their
their
barn.
They
call
it,
and
so
my
thought
was
to
take
the
the
benchmarking
survey
data
and
basically
bring
that
to
you
know
a
group
presentation
situation.
B
C
But
but
independently
thinking,
we
want
to
build
a
group
of
people
who
would
like
regularly
be
willing
to
show
up
and
participate.
Like
that's
a
that
sounds
to
me
like
you're
gonna,
get
a
bunch
of
well
you'll
get
local
people
who
show
up
for
the
Meetup
and
it'll
be
great,
but
I
I'm,
not
sure
the
next
time
we
didn't.
We
wouldn't.
We
wouldn't
invite
that
same
group,
all
right
right.
B
C
Was
I
was
thinking
like
in
this
case,
maybe
I.
Maybe
you
know,
Jim
was
just
my
thought
that,
like
we
kind
of
had
a
standing
group
of
people
who
of
companies
who
are
you
know,
okay,
there
certainly
are
a
sort
of
smaller
circle
of
friendlies
that
you
know
hey.
We
want
to
test.
We
want
to
get
some
questions
or
survey.
C
Well,
of
course,
they're
all
going
to
answer
the
survey
we'll
go
to
them
and
even
like
we
get
together
with
them
regularly
once
a
month
once
every
two
months
to
say
you
know
what
are
your
problems
what's
going
on
and
I
think
people?
Sometimes
you
only
really
remember
your
current
problems
right,
regular,
touchpoint,
it'll
be
like
well.
C
What's
bothering
you
today,
right
inside
I
know,
stick
stuff
was
blah
and
I'm
just
thinking
that,
like
that's
sort
of
regular,
you
know
finding
that
the
companies
could
be
will
they
definitely
regularly
show
up
and
contribute
it
sort
of
also
a
gateway
into
being
more
regular
contributors
to
the
rest
of
the
budget,
like,
for
example,
that
it's
like?
Oh,
we,
our
biggest
problem,
is
this
and
three
of
them
say:
hey.
We've
all
got
that
problem.
Let's
contribute
to
fix
that
problem.
C
B
C
Do
we
start
to
build
that
list
of
people,
and
you
know
what
my
initial
thought
might
even
be?
If
we
all
just
came
up
with
a
couple
companies,
we
thought
would
be
good
people
to
have
to
meet
with
talk
with
regularly
and
we
try
and
kick
something
off.
You
know,
I,
don't
know
that
we
need
to
super
optimize,
how
we
get
people
into
it
right.
B
C
To
me,
the
question
would
be
the
change
like
do
we
you
know,
is
it
every
month
or
every
other
month
or
I
might
I
might
suggest
again
based
on
time,
like
maybe
every
other
month
right?
Okay-
and
just
you
know
we
want
to,
we
want
to
get
the
them
together,
often
enough
to
get,
but
it's
too
often
then
there's
also
the
risk
of
sort
of
where
burnout
we're
out
right
right.
B
Okay,
so
let's
start
with
bimonthly
at
yeah,
that's
reasonable!
So
you
know
that
will
give
us
I
always
just
a
little
concerned
that
you
know
we
do
need
time
together
to
you
know.
We
really
drive
consensus
here
and
you
know
get
this
group
off
the
ground,
but
I
don't
want
to
eat
into
everybody's
time.
C
C
Okay,
so
I
guess
that
would
be
for
each
of
us
to
think
about
who
we
might
invite
and
start
those
discussions
right.
I
think
the
other
thing
too,
is
you
know:
are
we
comfortable
putting
opening
an
issue?
Basically
a
public
issue
that
says
hey,
you
know
we're
starting
this
up.
Are
there
companies
out
there
that
are
interested
in
participating?
Yes,.
B
I
think
that
that
would
be
very
much
in
line
with
you
know
how
we
should
do
this
transparently.
We
make
sure
that
everyone,
you
know,
feels
invited,
and
then
you
know
where
needs
point.
You
know.
If
we
get
too
much
interest,
then
we
can
begin
to
split
folks
up
into
two
groups:
verticals
and
whatnot.
Yes,.
C
Okay,
so
we
could,
you
know,
I'll,
take
the
option
to
open
an
issue
that
basically
says
you
know
we're
targeting
targeting
the
first
time.
You
know
an
initial
kickoff
of
getting
some
end-user
users
together
for
a
meeting
on
this
on
this
time.
A
time
you
know
this
is
an
issue
to
you
know
where
you
can
express
your
range.
You
know,
let
us
know
if
you're
interested
and
who
the
contact
point
would
be
and
I'll
ask
cb2
to
retweeted
from
the
foundation.
Twitter
account
fantastic
and
then
separately.
You
know
with.
C
B
F
Have
something
actually
so
thanks,
so
the
user
feedback
as
a
group,
it
is
the
focus.
Do
we
want
the
focus
to
be
feedback
on
the
existing
technology,
and
you
know
I,
think
the
benchmarking
survey
had
a
lot
of
good
like
tangible
things
in
that
area.
You
know
asking
what
particular
performance
problems
are.
Restricting
you
from
doing
certain
things,
and
so
that
would
be
an
example
of
like
technology,
specific
feedback,
but
there's
also
other
feedback
that
I
think
is
valuable,
and
but
that
falls
into
more
like
want
to
be
user
feedback
like
as
an
enterprise.
F
B
F
F
F
Because,
in
particular,
I'll
say
I'm
really
interested
in
the
enterprise
aspect
and
all
of
the
things
I've
gotten
feedback
to
myself
on
why
there's
troubles
you
know.
We've
talked
before
about
the
certified
modules.
You
know,
something's,
that's
something!
An
enterprise
is
really
want,
so
I'd
like
feedback
yeah.
Absolutely
we.
C
We,
the
detect,
it's
meant
to
be
like
I,
don't
want
to
exclude
the
technical
feedback,
but
it's
the
the
business
and
higher
level.
Organizational
like
feedback
I
think
is
the
one
where
but
I
know.
Maybe
I
shouldn't
say
that,
because
the
benchmark
you
want
are
specific
things
like
as
the
developers
we
don't,
we
still
need
the
end
user
feedback
on
that.
But
definitely
the
like.
You
said
that
other
feedback,
any
of
the
obstacles
to
using
no
or
the
things
that,
like
in
your
organization,
may
not
be
technical.
F
C
B
Is
it
too
soon
to
try
to
schedule
one
of
our
January
sessions
around
that
and
you
know,
invite
some
people
for
that,
since
we
really
wanted
to
have
Michael
Dawson
on
the
the
February
9th,
since
this
is
in
the
mist,
that's
dear
to
you
William.
Would
you
like
to
try
to
target
the
you
know
January
12th
session.