►
From YouTube: Node.js User Feedback Initiative Meeting
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).
A
A
B
A
But
you
know
we
might
need
you
know.
Were
you
know,
leaning
on
the
foundation
for
help
definitely
need
a
owner
inside
of
user
feedback
to
be
carrying
that
forward
and
if
subbies
responsibilities
have,
you
know,
begun
to
point
in
other
directions.
You
know
what
I
like
to
do.
Is
you
collaborate
with
them
and
you
figure
out
a
way
to
find
an
owner
for
that
and
opportunity.
B
I,
don't
think
that's
necessarily
I
haven't
heard
anything
that
would
make
me
think
that
that's
the
case,
I
guess
it's
just
a
matter
of
saying.
There's
a
next
step
that
hasn't
taken
place
is
that
the
issue
I
haven't
been
paying
enough
attention,
but
basically
you're
waiting
on
him,
for
something
is
that
that
no
like.
A
You
know
it
it.
What
it
really
needs
is
a
caretaker
if
someone's
gonna
carry
all
the
way
through,
and
you
know
that
that's
the
gap,
not
you
know,
tell
me
what
the
next
thing
to
do
is
someone
to
push
it.
You
know
I
personally,
you
know,
don't
have
the
bandwidth
to
do
it.
I'm
focused
on
the
the
event
and
supporting
that.
So,
if
that
you
know
kind
of
falls
back
on
my
plate,
they
the
thing
that
I'm
gonna
do
is
look
to
recruit.
A
Someone
who
you
know
can
sort
of
care
and
feed
that,
and
you
know,
coordinate
that
through
from
concept
to
completion,
and
you
know
be
the
partner
with
Linux
Foundation
to
to
leverage
the
resources
they're.
Providing
you
know,
I,
don't
know
that
we
can,
you
know
fully
lean
on
the
Linux
Foundation
or
that
we
should,
and
so
just
a
matter.
A
See
you
know
he
hasn't
been
able
to
join
us
for
right
now,
a
couple
months
now
and
you
know
we-
we
have
support
from
the
Lynx
foundation
to
coordinate
with
them
and
you
lean
on
resources
from
them,
but
we
really
need
to
be
driving
it
on
our
ends:
okay,
and
and
bring
you
know,
bringing
the
asks
to
them
right:
okay,
well,
we'll
talk
to
him
and
figure
out.
What's
going
on
there,
cool
yeah,
I'll
good,
you
know
what
no
no
issues
either
way,
but
I
definitely
want
to.
A
You
know,
call
us
on
a
on
a
decision,
especially
since
we
you
know,
we
just
asked
the
Linux
Foundation
to
support
this
effort
with
the
surveys
and
they're
they're
lining
up
resources
for
us.
So
if
we
don't
have
someone
on
Ben
to
be
carrying
that
forward,
then
you
know
that
whomever
is
is
gonna,
be
you
know,
taking
taking
care
of
that
is
going
to
get
frustrated.
Yep.
A
C
C
A
A
E
A
A
B
E
B
A
A
You
know
how
that
group
is
evolving
and
you
know
moving
forward
with
document
and
excited
there.
Do
we
want
to
you
know
along
those
lines,
you
know
dive
into
anything
around
the
enterprise
feedback
blog
post,
or
is
that
you
know
something
that
we're
just
you
know
continuing
to
work
towards
and
we'll
check
in
on
that
later
Tracy
is.
That
is
that.
C
A
So
the
next
is
a
general
user
feedback.
We
have
everything
lined
up
in
May
right.
Mr.
guinea
had
may
the
may
meet
up
in
San.
Francisco
I
still
need
to
finalize
things
with
open
source
for
for
Portland
the
the
following
week
and
then
do
we
want
to
dive
into
it.
Well,
there's
a
couple
things
that
I'd
like
to
touch
on
here
and
I:
don't
know
that
we
can
wrap
up
the
the
the
first
one
this
week.
What
I'd
like
to
do
is
get
James
on
games
now
on
and
begin
to
kind
of
brainstorm
on.
A
What
are
the
topics
that
we're
gonna
go
through?
You
know
go
through
what
what
what
we
want
to
hear
from
from
core
in
a
no
current
release-
and
you
know
brainstorm
around.
What's
going
to
get
folks
the
the
most
engaged
in
a
feedback
mindset
right,
we
want,
we
want
folks
to
you,
know
not
just
be
consuming.
You
know
the
context,
but
really
you'll
be
able
to
to
draw
from
what
we're
sharing,
and
you
know
really
turn
that
around
into
a
you
know:
feedback
loop,
we
that
were
capturing
in
the
second
part
of
the
media.
A
So,
to
do
that
I'd
like
post
that
for
our
next
meeting
we
invite
James,
Snell
and
whomever
else
that
if
we
have
anybody
primed,
they
have
kind
of
have
James
lined
up
and
for
this
first
iteration
I,
don't
know
that
we
have
anybody
else
that
we
could
or
should
invite
or
bring
in
but
I'm
open
to.
You
know
suggestions,
so
we
can,
you
know,
get
get
a
more
concrete
expression
written
down
of
how
we're
going
to
execute
on
that
meet
up.
Okay,.
B
So,
basically,
you
think
yes
and
since
James
is
gonna,
be
part
of
that
first,
one
get
him
involved
and
I
guess
that
sounded
to
me,
like
there's,
been
a
lot
of
interest
shown
and
a
bunch
of
the
other
meetups.
So
my
question
would
be:
do
we
do
want
it?
Do
we
want
to
do
something
with
a
smaller
group
to
kind
of
get
our
heads
around
it
first
or
do
we
want
to
invite
anybody
from
those
other
meetups
to
kind
of
listen
and
participate
in
that
discussion?
Yeah.
A
Correct
me,
if
I'm
wrong,
Tracy
many
folks
have
expressed
interest
in
like
a
user
feedback
in
a
box,
the
kind
of
thing
like
if,
if
you
have
a
program,
that's
defined
I'll,
do
it
and
we're
not
there
yet.
So
you
know
this
this
iteration
of
just
going
and
doing
it
and
you
know
coalescing
our
feedback
is,
you
know,
III
think
if
we
have
folks
who
are
just
sort
of
waiting
for
the
output
of
this
you're
participating,
it's
gonna
slow
us
down
for
this
iteration.
A
What
we
need
are
individuals
who
want
to
contribute
creative
ideas
for
how
we
can
its
creative
ideas-
and
you
know,
subject
matter
expertise
to
how
we
can
best
execute
on
this,
and
you
know
that
that's
that's
the
framing
that
I
want
to
do
because
you
know,
if
folks
are
just
looking
for
to
us.
For
you
know
the
good.
C
B
G
B
C
B
C
Some
level
of
like
I,
don't
know
I,
guess
you
were
thinking
that
he
was
gonna
spill
in
some
level
of
technical
content
or
something
like
it'd
be
really
nice.
Just
to
give
these
people,
you
know
I
initially.
Actually
it
started
off
with
two
blog
posts,
so
one
about
hey.
If
you're
a
user
or
sorry,
you
know,
if
you're
a
speaker.
What
are
you
gonna
do
there
and
then
I
was
creating
another
one
for
if
you
are
a
meetup
organizer.
C
What
are
you
gonna
do
there,
but
then
what
I
realized
was
it's
actually
exactly
the
same
thing.
So
if
we
just
create
one
sort
of
hey,
here's
how
you
run
a
user
feedback
session
that'll
be
good
I'm
in
the
process.
Right
now,
I'll
create
an
issue
right
now
as
well,
but
I'm
gonna
create
an
open,
Google
slides
things.
So
we
can
collaborate
on
slides
because
I
think
that'll
be
really
important
together
as
well.
Cuz.
B
Maybe
if
we
have
time,
we
should
just
go
through
that
and
say
here's
here's
what
we
think
the
structure
is,
then
we
can
get
James's
input
in
terms
of
does
that
fit
with,
because
I
think
it's
kind
of
like
he's
there
just
to
give
a
an
intro
we
mase.
We
may
say
that,
like
the
beginning
of
every
one
of
these,
it's
good
to
give
some
a
talk
on
something
technical
related
to
note.
I,
think.
Actually
that
could
vary
unless
we
think,
depending
on
who's
there
right
or
we.
A
Right
I
think
that's
essential
like
that.
That
is
the
the
you
know,
we're
attaching
to
a
point
in
time
right
and
so
why
do
we
attach
to
the
point
in
time
because
there's
a
major
change
coming,
so
you
know
we
we
can
expect
the
end
user
community
to
you
know
be
as
up-to-date
on
the
day-to-day
of
note
as
we
are
since
we
spend
you
know
a
lot
of
our
time
engagement.
A
So
you
know
this
is
our
opportunity
to
you
know,
share
what's
happening,
and
you
know
honestly,
it
doesn't
have
to
be
exclusively
technical
right
if
right,
you
know
if
attach
to
this
we're.
Also,
you
know
sharing
a
bit
of
the
context
of
what's
going
on
in.
You
know
the
merge
discussion.
You
know
it's
a
great
time
to
sort.
A
Out
the
activities
in
the
node.js
foundation-
and
you
know
let
people
know
you
know,
what's
going
on
yeah.
B
I
think
that
first
section
could
always
be
you
know,
what's
new
in
the
node
community
and
then
for
a
specific
instance,
like
you
know
the
one
you
scheduled
with
James
it's
around
well,
okay,
a
new
release
is
coming
out,
so
we
might
fill
in
for
that
specific
meet.
You
know,
iteration,
we
might
fill
in.
You
know,
what's
new
with
the
nodejs
community,
its
release
time
come
hear
about.
B
What's
going
on
the
releases
right
or
it
could
be
just
a
you
know,
if
they're,
if
we
haven't
actually
tied
it
or
you
know,
a
meet-up
is
doing
one
and
they
haven't
tied
it
to
anything
specific,
it's
whatever
the
speaker
that
they
can
get
or
whatever
they
know
about
that
they
can
fill
in.
You
know,
what's
new
on
the
node
community
on
that
front,
I.
C
B
B
C
B
C
Think
I
don't
know
anytime
I
mean,
like
that
mean
it
made
up
organizers,
for
example.
Right
probably
don't
have
like
zel
know,
but
they,
you
know,
don't
know
in
their
own
way
right
and
so
giving
them
some
sort
of
template
from
us
to
say
hey.
You
should
just
tell
people
in
general
what
these
latest
releases
are
yeah.
You
know
just.
B
C
B
B
B
C
B
C
We
we
need
to
we
and
we
probably
need
to
program
the
content
a
little
bit
more
around.
Also
like
okay,
here's
what
we're
gonna
do
first
or
you
know
like
look,
for
example,
the
slides
are
gonna,
be
really
good
because
it
kind
of
leads
people
through
okay,
hey,
you
know:
here's
the
latest
updates,
here's
the
strategic
initiatives
and
updates
on
efforts.
Okay,
now
here's
what
TSE
really
wants
from
you.
What
are
the
three
questions
we
want
to
get
out
of
this
user
feedback
session?
Nice.
A
A
C
C
C
C
C
So
like
in
this
I
mean
this
is
kind
of
actually
helps
me
with
a
blog
post.
You
write
like
when
somebody
wants
to
screen
share.
We
have
the
leader
speaker
or
meet-up
organizer.
You
know
we
were
talking
about
adding
in
so
late.
Where
do
they
add
in
issues
that
they're
having
with
lilies?
Like
one
thing
is
we
we
definitely
said
once
you
this
for
the
release
right?
Well,
I!
Guess
it's
not
really
it's
like.
Have
you
upgraded?
A
C
A
C
A
A
C
The
bigger
question
is
right,
so
if,
if
we're,
you
know
we're
trying
to
show
people
how
to
get
in
love,
we're
trying
to
show
people
how
to
log,
you
know
messages
so
that
the
TSE
can
see.
You
know
what
the
general
users
are
having
issues
right,
so
so
I'm
gonna
assume
that
that
means
that
you
just
want
people
to
create
more
issues.
Is
that
correct,
yeah.
B
B
The
github
basically
github
issues,
so
it
you
know,
I
think
the
in
this
particular
context.
It's
like
we
do
want
to
get
the
discussion
going
around.
You
know
what
what
you
have
there,
what
problems
of
you
have
you
experienced
upgrading
if
they're
related
to
modules,
we
can
point
them
to
the
package:
maintenance,
repo.
C
B
C
Well,
I
mean
that's
kind
of
the
thing
right
like,
for
example,
if
initially
I
think
what
I
was
so
if
I
were
running
this,
for
example,
I'd
be
like
okay,
well,
here's
what
the
TSE
wants
for
me.
If
have
you
upgraded?
If
not,
why
now,
what
I'd
want
to
do
as
an
organizer
is
have
the
URL
here
and
be
able
to
go
into
you
know:
yeah
I'm,
probably
the
wrong
one,
and
then
I'd
want
to
be
able
to
find
an
issue
number
to
do
like
directly.
C
A
H
B
A
Eliminate
any
you
know,
need
to
go
around
or
go
through
us,
we're
taking
folks
directly
to
the
right.
B
We
need
those
issues
to
be
opened
in
advance,
that's
all
which
is
you
know,
it
might
be.
I
think
we
we
might
open
to
issues.
You
know
one
I
think
there's
already
an
issue
opened
in
package
maintenance,
the
one
we
transferred
around
you
know:
I
have
a
problem
with
a
module.
We
might
just
open
a
similar
one
which
is
I'm
having
problem
upgrading
in
node
10
for
reason,
X.
So.
A
E
I
think
just
based
on
the
context
of
year
of
having
pre-opened
issues
that
people
can
be
pointed
to
makes
perfect
sense.
I
would
still
want
to
refine
that
question
to
be
more
targeted
like
have
you
operated,
not?
Why
is
not
necessarily
you
know
very
targeted
for
because
it
might
be
talking
about
a
person
on
node
four
and
have
enough
waited
to
twelve.
That's
a
large
conversation.
E
B
And
that
would
be
an
interesting
one
too.
So
again,
thinking
of
the
issues
which
I,
like
you
know,
here's
a
place.
People
can
go.
Do
it?
That's,
maybe
if
that's
probably
an
issue
in
the
user
feedback
repo
that
says
we
want
to
better
understand
your
upgrade
cycle.
It's
not
an
issue
in
the
node
repo
that
you
know,
somebody's
gonna
read
and
fix
something.
So
that
could
be
an
issue
in
the
because
I
think
you're
right,
like
that's
kind
of
the
interesting.
B
E
B
Yes,
okay,
so
yeah
I
like
that,
you
know
I.
Think,
though,
I
think
what
you
just
said
is
we
should
we
should
change
the
first
one
to
be
and
I
think
we
should
start
with.
What's
your
upgrade
cycle
like
hey,
we
like
your
feedback
on
on
this.
We
can
talk
a
bit
about
it
today,
but
please
go
put
your
comments
into
here,
because
we'd
like
to
have
a
better
feel
the
second
one
could
be.
Are
you
having
any
problems
upgrading
to
ten
because
of
changes
in
note
itself?
B
F
C
B
B
E
F
C
A
A
No,
no,
if
we,
you
know,
go
back
to
the
beginning,
we
do
have
an
initiative
to
start
rolling
out
some
surveys.
So
you
know
the
the
timing
definitely
aligns
and
also
I
think,
the
time
being
will
align
with
the
the
foundation
survey.
Most
of
all,
so
you
know
we
I
think
we
can
be.
We
can
laugh
and
what
we're
doing
as
a
as
suggestions
for
some
additional
technical
content
that
integrates
with
the
broader
node.js
foundation
survey
that
we've
invited
the
foundation
team
to
provide
to
it
to
engage
the
community
and
get
you
back
up.
B
A
So
yeah
I
think
you
know
that's
that
covers
the
big
you
know
I've
been
trying
to
figure
out
what
are
the
big
gaps?
You
know
the
only
other
thing
that
I
would
you
know
potentially
consider
adding
to
there
is
if
you
wanted
to
go
into
anything
foundation
e
or
you
know,
merge
e,
but
I
I,
don't
know
that
it's
in
the
flow.
B
For
this
particular
like
this
is
very
specific
to
a
a
you
know,
a
focus
on
releases
I
mean
I
could
see.
I
could
see
a
like
a
similar
set
of
questions
around
the
merge
right,
but
probably
a
separate.
It
probably
does
make
sense
to
have
it
be
a
separate
thing,
unless
it
kind
of
depends
on
how
much
we
think
we
can
fit
into
one
session
right
like
if
you
could
fit
two
topics.
You
might
then
say,
here's
the
the
things
and
I
think
what
you're
just
doing
now.
B
A
And
you
know
that
could
be.
You
know
a
point
in
time.
You
know
yeah
thing
that
we're
targeting
the
the
demerger
right.
Okay,
no,
the
next
iteration
is
merger.
You
know
this.
Could
some
Bob
here,
let's
go
out
to
the
meetups
and
you
know
share
this
context
and
you
know
with
that.
I
like
that
were
engaging
folks
to
go
right
to
github
yep,
which
is
where
you
know
it
said:
that's.
That
is
the
source
of
truth
for
the
node.js
project
cans.
A
B
I
didn't
hear
anybody
say
that
I
just
think
I
was
thinking
that
we
would
have
liked
for
each
topic.
We
could
have
a
stock
slide,
so
right
so
like
if,
if
we've
got
this
deck
and
the
an
immediate
organizer
wants
to
run
a
user
feedback
session
for
us,
it's
like
hey
you've
got
it.
You've
got
a
pallet
to
select
from
you
could
pick
the
release
one,
and
maybe
those
are
more
relevant
around
the
to
times
of
the
year.
Where
releases
are
interesting,
another
choice
would
be
the
foundation
merge
which,
which
is
now
there's.
B
A
C
B
Think
what
we're
getting
on
to
is
slightly
different,
so
we
should
absolutely
do
that.
As
part
of
this,
the
question
is:
is
there
any
like
there's
different
focuses
for
what
we
want
feedback
on
one
of
the
topics
might
be
just.
Do
you
understand
what
we're
telling
you
about?
You
know
yeah.
We
have
a
slide
at
the
end
where
we're
telling
you
what
we
think
you
need
to
know.
Does
it
make
any
sense
to
have
a
session
on
how
well
that's
working
for
people
or.
C
C
C
B
A
C
A
Like
I
think
we
would
want
someone,
you
know
if
we
did
really
go
into
the
the
package
issues.
We
really
want
representatives
from
that
group.
You
know
not
just
speaking
on
their
behalf.
Yes,
engaging
and
helping
us
define
what
their
needs
are,
rather
than
all
right.
You
know
on
on
their
bath,
yakked.
B
C
B
The
what
I
want
is
us
to
get
some
more
topics
like
end
user
topics.
It's
like
people
who
are
using
node.
What
do
they
struggle
with
you
know
these?
These
are
still
a
bunch
of
these
are
good
but
focused
on
what
we
are
thinking
about
day
to
day.
It'd
be
good
to
you
know,
get
more
of
the
you
know,
I'm
writing
an
application.
What
is
what
are
my
pain
points
in
using
node.
B
B
Like
Diagnostics
is
a
good
one
in
terms
of
like
you
know,
I
I
think
that
group,
and
we
obviously
should
you
know
open
issue,
discuss
it
with
the
Diagnostics
group,
but
I'm
certainly
would
be
interested
into
like
hey.
What
are
the
tools
you
currently
are
aware
of?
What
do
you
use
regularly?
What
do
you
you
know.
C
B
B
G
A
How
can
we
track
that
back
and
make
sure
that
you
know
we
have
visibility
into
what
we're
generating
right,
because
we
can.
We
can
just
let
everything
proliferate
and
you
know,
probably
do
good
but
I
think
to
like
really
make
user
feedback
the
most
successful.
We
need
a
feedback
loop
it
to
us
to
make
sure.
Oh,
that
got
traction
yeah.
We
tried
that
and
you
know
no
one.
No
one
responded,
you
know.
Are
we
asking
the
wrong
things?
You
know?
Do
people
just
not
care
about?
You
know
that
crazy
harebrained
idea
that
you
saw
but.
B
B
F
B
A
You
know,
III,
think
that
we
don't
mean
to
over
over
engineer
a
solution,
but
I
do
think
we
need
to
plan,
for
you
know
just
some
of
the
ingest
and
I.
If
we,
you
know,
put
a
little
extra
effort.
Upfront
in
you
know,
sort
of
recognizing.
There's
a
feed
lose
the
knee
back.
They
will
put
in
the
the
extra
work
to
make
sure
we
are
getting
the
feedback
on
you.
B
B
A
B
A
So
I
think
that's
a
yes
and
Michael
I.
Think
that
you
know
if
we
don't
correct
that
feedback
into
an
issue,
we
will
struggle
with
capturing
coalescing
that
Steph
feedback.
So
we
should
definitely
encourage
folks
to
pose
to
an
issue
but
I,
guess
the
you
know
the
the
best
pattern
would
be
compost
to
an
issue
and
with
that
issue
we
invite
you
to
come
to
one
of
these
sessions
right.
B
Yeah,
it
could
be
like
we
should
have
the
steps
which
is
one
of
them
is
like
creating
an
issue
saying
that
you're
gonna
do
this
capture.
The
you
know
give
us
information
about
the
date
the
time,
so
we
can
help
promote
once
you've
completed
posts.
Your
comments
on
how
it
went
and
then
come
to
the
next
user
feedback
meeting.
So
we
can
discuss
them
with
you
and
I.
Think
I.
B
C
B
H
A
So
we
do
both
right.
You
know
that
there's
the
initiative
that
we're
getting
feedback
on
where
you
know
so
did
this
one.
Is
that
the
current
release
of
b12-
and
you
know
there
were
talking
about
issues
and
success
whatever
related
with
that,
then,
if
we
invite
the
individual
who's
running
one
to
post
their
issue
and
user
feedback,
then
you
know
we're
gonna
have
their
their.
A
B
It
also
gives
us
the
date
and
time
so
that,
like
you
know,
we
can
make
sure
the
nodejs
or
promotes
it,
and
we
can
all
help
promote
that
session.
So
it's
yeah
I,
think
I.
Think
if
we
open
one
to
say,
hey
here's
the
current
topic
we'd
like
people
to
do
it
on
I'm,
not
sure
if
it
needs
to
be
like
one
month,
because
I
don't
know
that
we're
gonna
be
able
to
churn
out
a
new
one
every
month,
but.
B
H
C
C
B
A
C
B
B
Its
releases
and
that
may
actually
be
for
three
months
then
saying
six
months
I
can
see.
We
could
also
get
to
the
point
where
maybe
there's
a
couple
of
topics
right
like
we've
got
releases
or
you
want
to
do
something
on
the
merge
or
you
want
it.
You
know
there's
three
to
choose
from
we're,
but
it's
not
that
every
month
we'll
have
a
new
topic
that
we
shift
on
to
both
because
it
may
take.
A
A
You
know
what
we're
laying
out
and
empowering
others
to
sort
of
take
and
run
with
that
and
giving
them
the
time
to
sort
of
build
their
own
flows
and
grow
that
if
we
start
out
with
you
know
a
slow
progression
of
things
that
folks
can
do,
then
we'll
build
momentum
with
more
participation.
But
if
we,
if
we
start
with
all
the
things
yeah.
F
B
So
I
would
like
we
start
with
releases.
It's
a
good
focus
and
we'll
learn
a
fair
amount
doing
that
one
we
might
start.
You
know
we
started
brainstorming.
We
might
start
talking
like
among
ourselves
what
the
next
one
would
be
and
getting
ready
for
that.
But
let
the
first
one
roll
out
I
mean
I.
The
thought
that
I
just
had
as
Dan
was
speaking
was.
B
If
we
get
the
template
in
the
pattern
ready,
then
it
should
be
easy
for
somebody
else
in
the
node
organization
to
say:
I
want
some
feedback
on
this
plug
it
in,
and
but
you
know
they
then
are
the
ones
we're
gonna
be
looking
at
the
issues
and
looking
at
the
feedback
and
stuff
like
that.
So
that's
a
good
way
to
then
paralyze.
If
there's
enough
demand,
but
I
think
we
should
just
start
with
releases
if
see
how
it
goes
here
with
the
successes.
B
H
Before
we
end
the
call,
please
can
we
take
a
look
at
user
feedback
session
for
website
redesign.
They
needed
some
sort
of
initial
upon
the
new
notice
web
page.
So
if
you
check
in
it's
in
the
chats
there's
a
link
to
the
comments
under
link
to
the
the
issue,
opening
websites
are
designed
seem
so
or
just
giving
a
look
at
it.
So
we
know
how
we
can
help
them
finish
up
or
the
processes
to
move
forward.
It
says.
A
A
Issue
so,
let's
let's
tag
this
as
user
feedback,
and
you
know
pull
that
in.
If
we're
going
to
man
this
as
a
survey,
then
you
know
right
now:
I
don't
have
someone
who
can
sort
of
take
that
and
spearhead
that.
But
you
know
we
could
do
that
up
as
something
that
that
were
getting
for
feedback,
but
I
would
definitely
want
to
see.
A
F
B
B
I
think
that
you
know
Joe
did
respond
to
me
and
says
it
seems
like
mostly.
What
he's
waiting
on
is
people
to
come
up
with
the
questions
yeah
right.
So,
like
a
Giri,
you
know
if
you
could
put
together
a
here's.
The
survey
questions
we'd
want
I,
think
having
that
in
an
issue
would
be
like.
Okay,
we
have
that.
H
A
A
chicken
and
egg
problem
and
yeah
I
didn't
get
your
question.
We've
had
the
same
challenge
with
promises
like
you
know.
If
we,
if
we're
asked
to
you,
know
design
and
define
all
of
the
other
questions
that
you
know,
another
group
needs.
You
know,
that's
been
a
pattern
where
you
know
it
really
hasn't
gotten
through.
You
know
what
are
our
big
success
in
in
delivering?
A
survey
came
from
the
benchmarking
working
group
that
you
basically
delivered.
A
You
know
99%
complete
questions
to
us
and
we
only
sort
of
did
the
last
little
bit
of
fit
up
and
polished.
That's
what
we
were
able
to
really
deliver
a
survey
on,
but
these
sorts
of
things,
where
you
know
folks,
are
raising
their
hand.
Saying
I
would
like
to
do
a
survey.
We
don't
have
the
the
bandwidth
right
now
to
carry
that
that
effort
forward
help
those
folks,
you
know
design
their
questions
and
then
get
it
to
a
point
where
we
can
actually
deliver
that
as
a
survey
yeah.
H
They
do,
but
they
wanted
more
questions
from
sessions.
Maybe
issues
around
the
entire
knows
projects
that
has
been
placed
on
the
foundation.
Sorry,
these
are
feedback
seen,
so
they
can
generate
more
patience
on,
creates
a
survey
that
it's
actually
okay.
We
need
to
add
documentation
on
these.
We
need
to
add
documentation
on
these.
We
need
to
add
more
articles
based
on
these
feedbacks
who
goes
in
the
user
feedback
sessions
and
survey
who
deltoids
did
probably
yeah
I.
Think.
B
That
would
fit
into
so
that
the
template
we
were
just
talking
about
for
the
user
feedback
session,
because
the
answer
is,
we
haven't
gotten
a
lot
of
user
feedback
because
we've
been
working
on.
How
do
we
get
in
touch
with
the
people
that
slide?
We
just
put
together
that
says
on
releases
here.
Are
the
three
questions
we're
gonna
answer:
here's
the
issues
where
the
questions
can
be.
B
You
know
the
we're
going
to
try
and
get
people
to
put
in
answers
if
the,
if,
if
you
could
put
together
that
slide
for
what
the
website
redesign
or
the
website
team
needs,
that
would
help
us
look
at
it
and
say:
okay,
can
you
take
that
slide,
fit
it
into
the
deck?
And
now
that's
something
we
could
ask
the
the
the
you
know
it
would
be
another
option
to
say:
oh
okay
and
here's
another
timely
thing.
B
We
want
to
ask
these
three
questions:
here's
where
we
want
to
get
the
answers
in
and
in
the
meet
up.
The
goal
is
to
get
somebody
to
say.
Let's
talk
about
this,
let's
actually
write
some
of
the
answers
into
the
issues
and
in
sand
and
make
you
know,
get
all
the
people
there
say,
okay
well
and
continue
to
put
your
answers
into
those
three
issues
right.
B
F
A
Makes
more
sense
thinking
you
better,
alright!
Well
sorry
for
running
over
thanks
Gary
for
bringing
that
to
our
attention.
Go
ahead
and
shut
down
the
stream.