►
From YouTube: Node.js user feedback team meeting 12 Jan
B
All
right,
great
thanks,
Michael
we're
alive.
This
is
the
no
just
user
feedback
team,
and
this
is
our
lab.
I
weekly
meeting
today
we
have
a
pretty
full
agenda.
I'm
gonna
ask
for
help
getting
moved
over
to
the
final
topic
planning
for
our
first
public
session
by
the
40
minute
mark.
So
maybe
someone
could
give
me
a
time
check
at
the
30
minute
mark
and
at
40
minute
mark
I'd
like
to
hard
cut
over
to
planning
for
the
the
public
session
in
February.
B
A
A
No,
it's
that
well
I,
think
it's
like
it's
a
blind
vote
right,
so
there's
a
tool
that
they
send
out
a
vote.
Everybody
gets
to
vote.
Nobody
actually
knows
how
people
voted
and
to
support
that
it
takes
more
time
to
actually
set
up
the
tool
to
send
out
the
invites
get
people
to
do
it.
So
it's
not
just
an
in
person
got
it.
Fixing
that,
like
you
know
what
wait.
B
B
A
B
B
Okay,
does
the
agenda
for
this
meeting
show
up
now?
Yes,
great
all
right,
so
lots
been
going
on.
We've
had
vigorous
discussion
around
the
enterprise
advisory
group
and
I
want
to
make
sure
we
get
into
that.
But
you
know
kind
of
riffing
on
the
calm,
calm
work
and
you
know
trying
to
maintain
a
cadence
on
some
of
the
the
regular
things
that
were
doing
for
the
holidays.
I
identified
the
the
key
initiatives
for
the
user
feedback
group
and
labeled
them
on
github.
B
So
if
you
click
through
this
you'll
you'll
find
that
these
key
tracking
issues
for
our
three
main
areas.
Those
three
things
are
the
the
benchmarking
working
group
survey,
the
energies
of
feedback
outreach
and
to
engage
participants
and
they
had
been
Enterprise
advisory
group
and
then
at
the
bottom,
on
February,
9th
three
pence
without
our
first
public
user
feedback
meeting
and
I
want
to
make
sure
that
that
you
know
as
we
go
through
and
we
take
care
of.
You
know
our
sort
of
internal
check-in.
E
B
A
B
That
so
the
benchmarking
working
group
survey,
you
know
big
shout
out
and
thanks
to
the
noches
foundation
and
Greg
Wallace,
for
setting
everything
up
and
being
present
for
us
over
the
holidays,
Michael
I
know
you've.
You've
had
a
chance
to
review
some
of
the
the
data
coming
in
from
the
this.
The
surveys
yeah
I'd
love
to
get
your
feedback
on.
You
know
how
that's
going
whether
the
data
looks
like
it's
going
to
be
useful
and
usable
by
the
benchmarking
workgroup
right.
C
A
B
Yeah
we
did
get
some
some
some
feedback
from
folks
yeah.
We
asked
a
few
of
the
questions.
Were
you
know
in
your
organization?
You
know
quantify
the
entire
spectrum
of
you
know
what
your
organization
is
using
and
you
know
an
individual
who
happens
to
work
at
one
of
the
biggest
organizations.
It's
like
I
do
I,
can't
I,
don't
have
access
to
that
information
or
the
context
to
share
that.
So
you
know
that
will
be
an
interesting.
Some
tuning
of
you
know,
wording
I,
think
right.
Yeah,
I'm,
emailing
expectations,
yeah.
A
D
A
D
And
I
mean
generally
like
a
lot
of
like
that.
The
things
that
are
relevant
to
note
are
gonna,
be
the
people.
The
people
answering
are
gonna,
be
the
ones
that
are
relevant
to
note.
That'll
work
and
that'll,
probably
like
their
team
and
surrounding
groups,
will
probably
be
the
most
or
at
least
part
of
the
most
relevant
wants
to
to
the
survey
in.
D
B
So
there
are
a
couple
actions
to
be
done
for
context
at
present
were
planning
on
wrapping
up
the
input
from
the
survey
at
the
end
of
the
month.
So
yeah
we
have
had.
You
know
several
sort
of
outreach
blasts.
You
know
over
the
holidays
since
we've
been
back
I
personally
haven't
you
know,
promoted
the
survey
in
the
past
week
or
so
so
you
know
everyone
here
and
you
know
anyone
who's
who
is
watching.
You
know
appreciate
the
you
know
additional
sort
of
outreach
or
signal
boost.
B
You
know
when
we
get
these
tweets
scheduled
it'd,
be
nice
to
put
a
reminder
out.
There
I
believe
I
posted
an
issue
to
calm
calm.
Maybe
I
did
not.
You
know.
I
I
know
I
intended
to
over
the
holidays,
but
you
know
if
we
wanna,
you
know,
seek
out
an
additional
promotion,
calm,
calm
and
the
evangelism
work
group.
B
D
D
A
D
B
B
A
Yeah
I
think
that's
going
well
publicize
again
and
then
at
the
end
of
the
month,
I
guess
to
me.
The
main
thing
we
still
need
to
figure
out
on
that
front
is
what
we
can.
What
and
how
we
make
public,
because
that's
the
key
goal,
I
think
is
you
know
it's
good
to
share
it
with
the
benchmarking
workgroup,
but
I
want
to
make
it.
You
know
there
was
actually
specific
question:
there's
gonna
be
public
I
think
we
want
to
do
that
and
it's
just
a
matter.
I
think
of
you
know.
D
B
B
B
B
The
sake
of
time,
let's
move
on
we've
covered
that
so
and
uses
our
feedback
looking
for
participants,
you
know
that
is
a
process
that
Michael
kicked
off
and
we've
been
getting
your
feedback
rolling
in
in
individuals
rolling
in.
We
don't
have
anywhere
near
relevant
number
as
the
survey.
So
you
know
that's
that's
the
thing,
although
I
don't
think
you
know,
we
can't
have
140
people
in
the.
A
A
B
A
B
B
B
Yeah
ten
to
twenty
folks
have
responded.
You
know,
I
do
think
you
know
out
of
that
pool.
We
have
enough,
so
we've
circumscribed
the
public
feedback,
meaning
to
be
enterprise,
user
feedback
and
I
do
think
we
have
a
sufficient
sample
there
of
the
folks
who
have
raised
their
hands
to
select.
You
know
an
enterprise
user.
A
B
Be
reached
out
to
everybody
and
and
when
we
when
we
said
all
right,
let's,
let's
pick
a
topic
for
this
first
meeting.
Actually
we
said
you
know:
Kopke
had
proposed
in
January
on
this
date
that
we
do.
You
know
new
new
users
and
we
we
put
our
second
one.
It's
like
alright
yeah
cool.
Let's
do
that
first
and
then
in
February,
I'd
love
to
do
this
enterprise
user
feedback.
So
you
know
we.
We
have
the
enterprise
user
feedback
session
penciled
in
as
the
topic
for
for
February,
and
you
know
then
selecting
that
from
that
pool.
B
A
B
Let's
talk
through
that
as
we
sort
of
brainstorm
on
you
know,
this
will
be
our
first.
You
feedback
public
feedback
session,
so
maybe
circum,
you
know
limiting
it
to
only
enterprise.
Users
is
too
constrained
and
we
need
to
sort
of
invite
in
a
broader
audience,
I'm
again.
Okay,
so
lots
of
discussion
this
week
around
the
enterprise
advisory
group,
team
and
I
was
really
happy
with
you
know.
The
support
we
got
yesterday
from
you
know
the
community
committee
and
comm
come
in
in
terms
of
you
know,
providing
feedback
on
all
right.
B
You
know
we're
all
generally
aligned
that
that
some
concept
like
this
should
exist.
We
don't
like
quite
know
how
to
work
out
the
details.
Yet
since
it's
a
new
thing,
you
know
we
have
an
expression.
You
know
expressions
of
concerns
about
you
know
morning
and
some
other
things.
But
you
know
the
the
right
to
exist
is
not
one
of
them
and
you
know
so.
I
was
really
happy
with
with
the
how
we
ended
up
with
the
path
forward
there.
B
So
two
key
takeaways
from
the
community
committee
meeting
on
you
know
what
we
do
next
so,
first
and
foremost
in
terms
of
you
know,
trying
to
facilitate
and
engage
this
group.
It's
you
know
everyone's
comfortable
with
you
know
the
user
feedback
group
continuing
to
iterate
and
engage
in
in
do
outreach
reach
out
to
you
know
the
individuals
who
volunteered
we
have
a
new
individual
from
Walmart
labs
who's
who
has
raised
their
hand
to
participate
who
would
absolutely
fit
the
you
know,
sort
of
rough
sketched
out
criteria
that
we
have
for
that
group.
B
So
you
know
that's
nice
and
you
know
the
the
next
thing
is,
you
know,
probably
to
sit
down
and
invite
the
the
individuals
who
have
expressed
concerns
to
to
join
a
meeting-
and
you
know
talk
face
to
face
about
you-
know
the
concerns.
So
you
know
we
can
delay
those
concerns
if
they're
addressable
or
you
know,
resolve
them.
B
Yeah
I
don't
know
if
attorney
or
Michael
you
have
any
additional
color
to
add
to
that.
But
that's
my
high
level
I
know
I
was
really
frustrated.
Midweek
his
you
know,
Michael
got
the
full
brunt
of
a
you
know
on
Wednesday,
but
you
know:
III
do
see
a
path
forward
and
you
know
I'm
uncomfortable
with
continuing
to
to
feel
like
I
can
work
through
those
concerns
and
you
know
address
them.
I
mean
that's.
A
D
B
B
A
D
B
Yeah
in
general,
you
really
appreciate
the
you
know.
The
feedback
from
you
know
both
the
TSC
and
the
community
committee,
and
you
know
we're
exploring
new
territory
here,
and
so
you
know
it's
it's
novel
stuff
that
we're
working
on.
So
you
know
under
understood
that
we're
you
know
diving
into
the
unknown
navigating
into
the
unknown,
and
so
we're
going
to
have
to
you
know,
do
a
lot
more
wayfinding.
That's
fine!.
B
Now,
just
to
give
this
issue,
you
know
time,
you
know
the
Walmart
labs
you
know
offering
to
join.
You
know
if
you
haven't
checked
out
the
issue.
You
know
it's.
It's
I
was
really
happy,
like
just
click
through
this
forever,
but
it
will
do
it.
Live
I
was
really
happy.
One
of
the
one
of
one
of
the
big
things
that
I've
done
in
setting
up
user
feedback
is
establishing
expectation
of
effort
time.
B
So
you
know
a
lot
of
what
we've
defined
in
terms
of
community
committee
participation.
It
revolves
around
joining
meetings
and
coming
to
meetings
and,
in
you
know,
building
out
user
feedback.
I
I
really
knew
that
that
you
know
in
order
to
get
this
off
the
ground.
We're
gonna
have
to
establish
expectation
for
folks
that
it's
not
just
you
come
to
the
meeting
and
that's
it.
You
know
we
need
you,
as
an
active
member
to
you,
know,
be
potentially
doing
stuff
outside
of
the
the
sessions
so
I've
been
putting
that
in
the
readme.
B
B
Okay,
so
let's
go
ahead
and
move
into
some
planning,
some
brainstorming
around
the
public
user
feedback
meeting,
as
I
said
when
we,
when
we
initially
pencil
this
out,
this
was
you
know
a
brainstorming
session
of
you
know.
Word
we
weird:
how
do
we
establish
a
public
user
feedback
meetings
and
and
what
topics
do
we
do
so
we
picked
a
couple
topics.
B
A
B
A
A
A
Some
topics
may
be
of
more
interest
or
not
different
types
of
people
who
are
involved,
but
I
wasn't
looking
to
say
we're
gonna
pick
some
subset
of
that
for
the
first
meeting,
even
I
can
I
can
kind
of
see
it
being
a
lot
of
round
of
introductions
and
getting
read,
know
who
the
people
are
and
actually
discussing.
You
know
we
have
thoughts
of
how
how
to
make
this
useful,
but
I
think
we
could
get.
You
know
their
input
and
thoughts
as
well.
A
B
A
Yeah
we're
bringing
this
group
together.
We
want
to
get
your
feedback.
You
know
here
are
some
of
our
thoughts
on
how
will
how
we'll
move
forward
with
this?
But
if
you
know,
if
you
have
other
thoughts,
let's
discuss
those
as
well
and
then
maybe
we
can
Peck.
You
know
one
smaller
topic
to
go
into
an
in
detail
like
so,
for
example,
you
know
we're
closing
out
the
benchmarking
working
groups
survey.
A
A
A
Not
not
M,
it's
not
an
IBM
conference.
Ibm
is
helping
they
sort
of
get
it
off
the
ground
right,
but
it's
that
conference
is
offering
space
to
a
bunch
of
open
source
communities.
Nodejs
being
one
of
them
you
know,
Todd
was
was
asked
that
we
be
included
in
that.
So
we
came
up
with
a
proposed
agenda
and
you
know
it's
not
final
or
anything,
but
one
of
the
three.
The
three
things
we
had
on
that
agenda
was:
you
know,
sort
of
an
intro
to
working
group,
strategic
initiatives,
how
to
get
involved
user
feedback.
A
B
A
To
do
some
sort
of
session
where
we
have
you
know
users
in
the
room,
and
we
can,
you
know,
ask
them
questions
and,
and
so
forth
or
or
you'll
start
to
start
use
it
as
a
session
to
do
that.
I
know
you.
You
taught
that
doing
that
one
of
the
other
conference,
and
then
third
one
is
the
user
value
so
anyway,
to
make
up
probably
took
way.
Long
then
longer
they
need
to
say
that,
but
that's
something
else.
We
should
just
brainstorm
on
it.
A
E
B
A
B
B
Yeah
yeah
right
and
perfect,
perfect,
so
I'll
I'll
take
the
action
to
go
and
update
the
the
overall
tone
of
this,
and
you
begin
to
to
you
know,
build
out
in
the
email
for
for
everybody
to
invite
there
so
I'll
be
opposed
to
draft
of
the
evite
email
to
invite.
You
know
all
of
the
folks
who
have
raised
their
hands.
We
should
probably
do
another
round.
B
You
know
tweets
or
invites
to
say
hey
yeah,
we're
doing
this
thing.
You
know,
there's
an
opportunity
to
engage,
and
you
know
Michael
in
addition
to
the
oh,
the
benchmarking
working
group
data.
Would
you
be
comfortable
to
committing
to
you
know
giving
a
brief
presentation
about
what
the
benchmarking
working
group
is
sure?
Okay,.
A
I,
think
is,
you
know,
cuz
it
yeah
I
like
I,
like
the
the
whole
thing
where
you
know
time
to
introduce
and
get
to
know
each
other,
and
then
here's
a
concrete
thing
based.
You
know
we
already
have
some
questions,
so
let's
use
that
time
as
concrete
feedback
to
see
you
know
if
we
get
something
different
or
get
more
depth
or
or
whatever
versus
just
a
survey
right
and
right,
right
and
yeah.
A
A
The
kind
of
thing
you
want
to
be
involved
in
hey
come
and
you
know
join
up.
Will
you
also
send
out
the
like
I?
Think
we've
both
been
getting
the
responses
I
sent
out
the
first
set
of
replies?
Do
you
want
to
send
out
the
next
set
of
replies
to
people
saying
yeah
thanks
you're
on
the
list
and
I'll
take.
B
D
A
D
A
B
Right
and
you
know
just
just
sort
of
scrolling
back
to
you
know
when
I
raised
my
hand,
was
like
yeah
I'd
love
to
go.
Do
that
you
know
in
setting
up
the
the
user
feedback
group.
You
know
my
interest
here
has
always
been
to
yes
in
general,
build
out
this
capability,
but
Mike.
My
sort
of
vocal
group
is,
you
know
where
we
haven't
been
engaging
inside
the
node.js
project.
B
From
my
experience,
a
lot
of
these
enterprise
community
members-
and
you
know
I
know
they
have
a
lot
of
interest
in
you
know
connecting
and
understanding
more
so
you
know,
one
of
my
main
interest
is
to
to
facilitate
that
to
make
that
happen,
but
you
know
that's
not
exclusive
of
building
out
all
the
other
capabilities
and
in
making
this
you
know
a
broad
utility
for
the
the
node
project.
Yeah.
A
B
A
A
B
So
you
know
a
couple
thoughts
there.
Greg
are
you
still
active
I
have
a
question
for
you
if
you're
you're
here
I'm
here,
hey
alright
awesome,
so
you
know
when,
when
we're
doing
you
know
these
video
broadcasts
with
you
know
collaborators
yeah
we're
all
collectively
here
and
you
know
I
assume,
were
you
know
waving
rights
or
whatever,
since
we're
going
to
be
bringing
on
you
know
on
screen,
you
know
end
users.
B
F
Am
NOT
a
lawyer
alright
right,
but
you
know
I,
guess
it
really
sort
of
depends
on
the
topic
right
like
if
you
know
I
mean
if
I'm,
if
I
put
myself
in
the
shoes
of
say
a
director
of
you
know:
infrastructure
development
at
you
know
coca-cola
right
or
whatever
you
know,
I
I
mean
there's
gonna,
be
some
things
that
you
know
I'm
not
supposed
to
talk
about
right
and
I
sort
of
incumbent
on
each
individual,
I.
Think
I
I,
don't
know
my
sense
and
again
I'm,
not
water.
F
Is
it
isn't
a
secret
that
these
meetings
are
public
right?
But
that
being
said,
it
would
probably
be
worthwhile
to
just
let
everybody
who's
participating
know
ahead
of
time.
Here's
the
deal
right.
These
conversations
are
broadcast.
This
is
intended
to
be
a
venue
where
people
who
care
about
this
technology
can
bring
their
perspective
and
you
know,
contribute
their
thoughts
to
improving
the
technology
and
because
it's
open-source
technology
and
because
we
do
everything
in
the
open,
these
conversations
will
be
open
as
well.
F
If
you
know
so,
please
bear
that
in
mind
when
participating
in
these
calls-
and
you
know
you
know
what
I
mean
just
like
you
know,
by
it's
sort
of
like
that
thing.
You
know
you
always
see
on
website.
It's
like
you
know.
By
proceeding,
you
are
acknowledging
that
you
have
read
the
you
know
the
User
Agreement,
it's
similar
right,
it's
like
hey,
but
by
participating.
You
you
know,
understand
that
this
is
the
we're,
a
public
organization
that
we
do
things
in
the
public
and
that
this
conversation
is
going
to
be
public.
B
D
We
codify
some
language
around
that
and
put
it
in
the
repo
either,
so
we
can
directly
link
it
or
we
can
copypasta
just
to
be
able
to
have
that
in
multiple
formats,
so
it's
written
before
they
attend
and
that
we
say
it
before
the
meeting
starts.
We
should
probably
say
it
when
the
meeting
is
live
as
well
like.
B
D
F
F
B
D
B
Yeah
as
Greg
was,
you
know,
laying
that
out.
I
realized
that
there's.
This
is
also
an
opportunity
to
convey
to
those
that
are
coming,
that
this
is
under
the
node.js
code
of
conduct.
Right
yeah,
we,
as
you
know,
members
are
already
you
know,
engaged
in
this
covenant
as
we're
doing
these
things,
but
these
individuals,
you
know,
aren't
necessarily
going
to
do
that
were
dividing
them
to
be
on
screen,
so
I
believe
in
the
this
invitation.
B
You
know
we
should
have
these.
You
know
two
major
citations.
This
is
under
you
know
the
node,
yes
code
of
conduct.
You
know
here's
if
you
want
to
go
dive
in
and
and
do
that
then
you
know
like
like
Tyrion
said:
you
know
craft
something
about
this
being
on
public
record
and
and
act
accordingly
and
then
you
know
finally,
do
we
should
we
engage
the
moderation
team
to
participate
in
this
session
live?
Is
this
a
good
opportunity
for
us
to
say
you
know
this
is
a
you
know,
a
public
venue
a
moderated
and
moderated
space.
A
D
B
A
Just
don't
see
that
that
would
be.
That
would
just
be
too
much
work
to
ask.
You
know
unrelated
people
to
come
to
now.
I
guess
it's
us
from
the
community.
We
do
have
a
responsibility
to
you
know
since
we're.
You
know
you
and
I
are
in
the
meeting
and
we
have
community
members
in
the
meetings.
It's
kind
of
our
responsibility
to
make
sure
things
don't
go
off
the
rails
on
that
front.
B
Right
right-
and
you
know,
since
this
is
the
first
session
right-
you
know
my
thought
there
it
you
know,
brings
from
from
the
code
of
conduct.
You
know
where
you
know,
if
you
know
I,
don't
expect
it
to
happen,
but
yeah
in
the
first
session,
if
there
is
a
situation
that
needs
to
be
addressed
with
someone
who
is,
you
know,
has
the
a
large
public
forum
that
they
be
given
access
to.
How
do
we?
How
do
we
address
that
individual
in
that
space
right
so.
E
A
B
A
D
D
B
Know
yeah
yeah,
I'm
totally
riffing
on
ya,
discussing
you
yesterday,
where
you
know
I
had,
for
example,
I'd,
never
even
considered
reaching
out
and
asking
you
know:
moderation
yeah.
You
know
I
kind
of
assumed
for
them
that
you
know,
there's
no
bandwidth
to
go
and
deal
with
like
working
group
issues
and
and
we're
not.
You
know
we're
not
worthy,
and
you
know
that's
the
you
know,
making
decisions
on
their
behalf.
That's
enough!
I.
B
B
You
know
traditional
normal
day-to-day,
and
you
know
this
is
you
know
just
a
hair
outside
of
you
know
the
main
forum
that
we
deal
with,
which
is
github,
but
we
are
as
working
groups
as
as
teams
constantly
doing.
You
know,
meetings
that
are
broadcast
to
the
noches
YouTube
channel.
So
you
know
we
could
we
could
have
this
be
an
opportunity.
You
know
if
journey
and
Tracy
wanted
to
join
the
meeting.
You
know
just
you
know,
even
just
looking
at
the
other
experience
with
that
lens
and
testing
it'd
be
good,
great.
B
A
A
B
C
C
Here,
because
he's
beginning
of
the
year,
and
can
we
guys
try
to
because,
for
example,
I
am
not
able
to
close
an
issue,
but
we
have
a
couple
of
issues
and
we
need
to
close
them.
We
don't
want
them
to
be
open
like,
for
example,
I
think
right
now
in
another,
in
not
gs
user
we
have
like
probably
two
or
three
at
least
we
can
close
them.
I
will
comment
like,
for
example,
issue
number
21,
the
the
last
meeting
of
December
29.
We
can
close
that
issue,
probably.
B
D
B
B
B
Awesome
so
me
hi,
thank
you
for
bringing
that
up,
and
you
know
thank
you
for
your
patience
in
sort
of
letting
us
go
through
the
process
and
figure
that
out
and
I
welcome
any
any
assistance
that
I
can
get
to.
You
know
you've
worked
through
the
issues.
You
know
it
is.
You
know
a
fair
amount
of
time,
effort
to
go
through
and
internal
all
those
little
things.
So
you
know
any
help
yeah,
because.
A
C
I
saw
a
couple
also
some
some
of
that.
Other
issues
are
linked
together
all
together,
but
we
need.
We
need
to
be
sure
that
it's
an
open
issue,
it's
a
real
issue.
Otherwise
we
need
to
close
that
well
just
to
have
tons
of
open
issues,
because
every
time
so
since,
since
we
will
get
all
these
meetings
going
on,
we'll
have
a
lot
of
issues
we
need
to
blow
them.
That's
yeah.
A
B
E
B
A
Sounds
good,
like
I,
said
I'm
out
next
week,
so
if
you're
wondering
where
I
am
I'm
on
a
beach
somewhere,
so
fantastic
Beach
yeah
thanks
like
I'm,
sorry
I'm
I'm,
here
next
week
until
Friday
I
and
then
the
week
after
that,
I'm
going
so
actually
I
yeah,
maybe
I
miss
I,
miss
I'll
miss
our
next
meeting.
Okay
weeks
right
yeah,
so
I'll
miss
the
next
one.
But
okay.