►
From YouTube: Node.js User Feedback Initiative Meeting - Aug 16 2019
Description
B
Welcome
back
everybody:
after
a
bit
of
a
summer
hiatus,
we
are
back
in
action.
We
have
figured
out
how
to
use
the
new
zoom
configuration
kind
of
mostly
by
proxy,
does
Michael
Dawson
and
him
haven't
figured
out
how
to
make
everything
work.
I've
got
some
of
the
basic
set
up
and
still
some
things
to
learn.
A
Is
that
people
recognize
that
a
number
of
these
issues
are
broader
than
just
note,
so
you
could
imagine
a
user
feedback
at
the
CPC
level,
but
I
think
we'd
have
to
figure
out
what
that
means
versus.
What's
going
on
here
right
like
is
it
does
it
tends
to
try
and
get
more
generic
feedback
versus
feedback
on
using
node,
and
it's
not
clear
in
my
mind
how
whether
that
makes
sense
yet
or
not
right.
C
B
B
As
a
prime
example,
you
know,
community
efforts
had
like
gone
all
in
all
across
the
ecosystem
on
promises,
and
we,
you
know,
were
you
know
at
a
point
where
we
weren't
ready
to
move
forward
with
that
largely
due
to
technical
constraints
with
v8,
but
you
know
there's
still
tension
that
needed
to
be
resolved.
So
that's
kind
of
the
founding
purpose
of
user
feedback
is
making
sure
that
we're
bringing
together
the
needs
of
the
community
to
serve.
B
As
you
know,
insight
for
collaborators,
you
know,
as
we
look
at
any
any
other
particular
destination
I,
would
want
us
to
make
sure
that
we're
we're
serving
a
need
right,
but
there's
there's
a
destination
as
a
you
know,
we
are
serve
as
agents
of
someone
and
you
know
when
we
get
in
that
situation.
I
worried
that
we're
not
you
know
directing
that
agency
towards
anything
which
can
lead
to
sort
of
frustration,
and
you
know
just
not
knowing
where
to
even
you
know,
take
a
bit
of
context
and
feedback
right.
A
B
I've
heard
you
know
that
there
is
interest
in
doing
that
at
the
gist
level.
Totally,
you
know
agree
that
there's
an
opportunity
to
do
it.
What
I
haven't
understood
is
doing
it
for
whom-
and
you
know
flipping
that
question.
You
know
who
is
interested
in
getting
feedback,
especially
since
the
mandate
of
the
open
destination
is
so
broad,
like
if
I'm
giving
feedback,
if
I'm
collecting
and
giving
feedback
for
the
jquery
project
yeah.
B
A
For
node,
it's
like,
we
still
have
a
situation
where
I
think
we
can
improve
on
the
flow
of
information
from
the
end
to
the
project
and
we've
tried
a
few
different
ways,
but
we
haven't
solved
the
problem
yet
I
mean
I.
Think
in
my
mind,
if
we
had
solved
the
problem
had
a
really
good
pattern,
that
other
budgets
could
apply.
B
A
A
B
Yeah
make
sense-
and
just
you
know,
counting
our
our
wins
and
our
successes
we've
been
way
more
successful
in
helping
collaborators
and
folks
that
you
know
are
looking
for
a
way
to
get
involved
in
the
project
like
the
promise
initiative,
like
the
the
benchmark
working
group.
Looking
for
more
feedback,
so
you
know
project
to
project.
B
You
know
the
tooling
a
working
group
and
supporting
those
needs.
The
efforts
around
that
eventually
became
the
module
working
group.
Those
have
been
you
know
very
successful
in
facilitating
things
around.
The
project
where
you
know
I've
always
sort
of
reached
for
is
that
that
broader
and
community
it
in
node-
and
you
know
most
of
the
time
when
I'm
you
know
doing
these
sessions
like
folks,
want
to
hear
more.
They
want
to.
They
want
more
insight
into
what's
going
on,
but
they
aren't
necessarily
at
a
loggerhead
with
any
me
right.
B
B
It's
not
really
that
bi-directional
channel
of
user
feedback
and
listening
and
you
know
established
in
the
channel
per
listing-
it's
really
still
the
need
for
bi-directional
contacts
from
the
foundation
that
I
think
materially
changes.
You
know
the
the
direction
of
this
effort.
If
we're
going
to
go
there
and
actually
ratchet
up
the
amount
of
work
that
that
would
produce.
C
B
V12
currents
relays
and
they
have
the
meetups
around
that
a
lot
of
our
meetup
organizers
across
the
world.
We're
very
interested
in
you
know
being
able
to
present
the
information.
You
know
that
that
we're
gathering
that
right
right,
you
know,
being
you
know,
held
abreast
of
you-
know
everything.
That's
going
on
and
known
and
being
able
to
share
that
what's
new,
what's
exciting,
okay,
I
think.
B
B
D
B
Collaborators
that
we
identified-
and
you
know
we
had
the
opportunity
to
serve
the
what
was
it
called
outreach
yeah
like
the
our
biggest
problem,
a
biggest
challenge
with
those
efforts,
whether
it's
outreach,
whether
it's
the
evangelism
working
group,
is
just
bandwidth.
Those
are
you
know,
full-time
roles,
full-time
roles
of
many
of
our
team
members.
You
know
that
we
all
individually,
who
are
in
those
roles,
you
know,
spend
significant
time
building
collateral
the
size
of
those
things.
B
So
you
know
as
a
volunteer
effort.
It's
a
pretty
heavy
volunteer
task.
It's
not
you
know
you're,
showing
up
to
the
meeting
and
doing
a
thing.
It's
really
the
meeting
is
an
anchor
for
you
know.
Hours
of
work
outside
you
know
the
actual
meeting,
where
the
meetings
just
to
check
in
or
an
alignment-
and
you
know
that's
something
that
I
am
some.
We
do
not
like
have
the
bandwidth
for
right
now
right.
The
outreach.
A
To
those
groups
and
right
so
I
think
I
mean
there
is
a
separate
initiative
under
outreach,
and
that's
why
I
would
I
would
I
think
that's
a
different
thing
than
trying
to
get
feedback
right.
Yes
again
so
like
if
you're,
if
you're
saying
this
team
should
stay
more
focused
on
the
feedback
side,
I
would
I
would
agree
with
you
from
matters
that,
like
it,
that
that's
important
but
I
think
it's.
It's
like
you
said,
there's
a
whole
different
set
of
activities,
a
fair
amount
of
work,
and
you
know
we
can't
necessarily
take
that
on.
B
B
A
Yeah
I
mean
I,
think
I.
Think
here
you
know
I
think
that's
that's
important.
It's
a
bigger
effort,
but
I
think
for
here
I
would
still
think
of
focusing
on
what
is
it
can
we
we
can
do
to.
You
know
help
that
flow
of
information
back
from
end
users
and
close
that
original
gap
that
you
know,
as
opposed
to
say,
building
new
meetups,
which
is
perhaps
new
channels
and
that's
good
yeah.
Some
of
the
valuations.
B
A
More
like
I
would
start
first
still
with
if
we've
got
existing
ones,
we
can
leverage
like
we
were
talking
about
and
saying
like
hey.
If
you
can
run
a
feedback
session
for
us
as
part
of
your
meetup.
That
makes
sense
to
me
versus
the
hell
will
help
you
start
a
meetup
in
the
first
books,
cuz
yeah,
it's
different
and
more
work
and
any
again,
if
we
completely
solve
this
problem,
then
it's
time
to
move
on
to
the
other
one,
but
I
think
we
still.
B
A
Still
have
there
still
work
to
be
done
to
say:
we've
got
a
good
flow
of
information
from
our
end
users
into
the
project,
and-
and
you
know,
then
we-
you
know
at
least
from
what
I
understand.
You
know
what
my
current
perspective
is.
We
could
use
more
of
that
and
you
know,
but
unless
we
finally
discover
there
just
aren't
any
problems
and
that's
why
we
don't
hear
anything
right.
B
And
you
know
Ocwen
ping
me
yesterday
and
you
know
we're
not
being
able
to
make
that
at
the
top,
but
you
know
that
that
enterprise
group
definitely
has
pain
that
you
know
we're
experiencing
at
scale.
You
know,
especially,
you
know,
at
pay
power
just
getting
to
a
point
where
we
can
adopt
ten
right
at
this
point
in
the
cycle
due
to
TLS
to
open
itself
issues
I'm.
Finally,
getting
to
a
point
where
you
know
we
packed
that
enough
and
then
and
able
to
use
that.
So
you
know
that's
been
a
big
issue.
B
You
know
we
want
to
be
able
to.
If
you
know
big
pain
point
to
be
that
that,
behind
you
know,
especially
with
all
the
improvements
performance
improvements
to
the
the
the
platform
and
ten,
you
know
that
being
behind
there,
you
know
is
costly.
So,
and
you
know
we,
we
have
appears
there
that
you
know
share
pain
and,
like
so
there's
me,
that's
really
valuable.
I
hope
Achmed
will
he'll
continue
to
be
able
to
to
do
that
as
the
oh,
the
new
role
that
he
is
in
ramps
up
a
bit
of
a
risk.
B
That's
what's
wrong
goals
for
us
per
user
feedback,
then
yeah
that
end
user
user
feedback.
We
keep
pushing,
keep
looking
for
you
know,
new
techniques,
new
approaches,
and
you
know
I'm
increasingly
of
the
mind
that
our
end
users,
you
know,
aren't
in
enough
pain
for
us
to
like
set
up.
You
know
yeah
listening
signal
and
serve
the
needs.
You
know
folks,
folks
are
happy
with
node.
You
know
folks
are
challenged.
You
know
biggest
challenge
that
I
heard
in
you
know
earlier
this
year.
B
That
folks
were
having
with
adoption
node
it
comes
from
AWS
lambda
in
the
Bay
Area,
you
know
being
a
bit
stale
in
their
node
release.
So
it's
a
platform
provider,
not
a
node
core.
You
know
challenge
and
we
have
relatively
limited
influence
on
a
platform
provider
like
that.
So
we
can.
You
know
we
can
highlight
them.
You
know
we
could.
Even
you
know,
sort
of
name
and
chain
them
for
both
little
reasons.
A
Hey
I,
want
to
work
on
this
or
that
and
and
they've
got
a
choice,
and
you
know
they
have
all
the
information
to
me
the
choice
they
want
to
make,
of
course,
but
also
based
on
what
people
are
saying
they
think
is
important
too,
but
if
your,
but
if
the
question,
if
the
answer
is
there
really
isn't
it's
like
yeah,
it's
say
but
you're
saying
that
right
now,
yeah
there's
just
not
enough
pain.
People
are
just
happy.
It's
like
ya,.
B
A
I
mean
I
I,
do
see
things
like
feature,
requests
will
come
in
and
languish
sure.
So
it's
like
you
know
that
that's
I
mean
a
different
model
would
be
to
say.
Let's
look
provide,
make
sure,
there's
a
clear
feature
request
channel
and
then,
when
things
came
in,
you
could
look
to
see.
If
that's
a
common
need
right
like
you,
could
basically
go
out
and
do
surveys
or
do
whatever
to
say.
Okay
well,
is
this
one
person's
need,
or
is
this
like
Arjun
serve,
need
right.
B
I
mean
that
does
balloon.
You
know,
just
in
total
self
self-preservation
again
does
balloon
into
you
know
a
bunch
of
work
that
we're
doing
outside
of
the
working
group,
but
you
know
comes
into
the
the
meeting
rather
than
something
you
know
we
can
be.
You
know
continuing
to
do
through
our
public
sessions,
and
you
know
that
stuff,
like
I,
would
need
to
recruit
more
team
members
to
that
that
have
the
bandwidth
to
do
that
or
get
support
from
the
foundation
to
be
able
to.
B
B
A
B
B
Maybe
we
don't
know
the
context
so
why
something
might
not
be
received
well
or
if
it's
that
one
thing
that,
oh,
my
goodness
like
you
know
everybody
once
a
month
asked
for
that
thing,
but
no
bazillion
times,
and
it's
not
really.
That's
not
really
a
big
challenge
in
our
community.
But
that's
definitely
you
know
a
stork
challenge
and
you
know
any
large
programming
project
you
have.
You
know
I,
like
that.
A
lot
I
think
that
that
could
roots
trap,
like
you
know,
could
bootstrap
something
like
that.
B
A
B
A
A
B
Would
need
foundation
support
for
that
Michael,
the
logistics
of
many
managing.
You
know
those
sorts
of
groups
are
actually
fairly
heavy.
So
there's
a
lot
of
ongoing
touchpoints,
readouts
and
just
kind
of
momentum
building
like
yeah
yeah
I'm
forming
a
a
separate
community
and
you
know
making
sure
that
they,
you
know,
feel
involved
it.
Don't.
If
you
don't
do
the
ongoing
maintenance,
those
sorts
of
groups,
then
they
just
tend
to
atrophy
and
everyone
kind
of
wanders
off
yeah.
B
That's
sure
right,
video,
there's
already
that
group,
so
that
group
comes,
you
know
comes
together
because
they
have
pain
points
and
you
know
they
can
get
together
and
solve
us
collectively
and
I.
You
know
if
there
was
no
pain
related
to
problems
that
you
know
they
have
experience
and
expertise
like
scale
or
deployments.
Then
that
is
a
valuable
group
that
you
know
has
the
context
of
the
things
we
would
need
to
be
able
to
sort
of
seven.
A
A
B
All
three
to
continue
working
on
all
three
and
I'd
like
to
get
to
a
point
where
I
felt
like
I
was
meaningfully
contributing
to
at
least
two
right.
So
you
know,
although
miss
you
know,
Comic
Con
meetings.
Now
we
basically
took
all
of
July
off
here
and
you
have
some
of
the
other
meetings.
If,
with
six
security,
you
know
likewise,
you
know,
I
was
just
two
very
good
work
to
to
run
and
facilitate
meetings
in
July
and
I
asked
one
of
the
other
co-chairs
there
to
take
over.
B
So,
like
things
are
things,
I
can
continue
moving
them
forward.
I,
don't
feel
good
about
the
level
of
commitment
and
responsibility
that
I'm
able
to
achieve
in
any
of
those
three,
and
that's
that's
kind
of
the
the
underlying
reason
for
that
statement.
Right,
I'd
like
to
get
to
the
point
where
you
know
the
commitments
that
I
have
for
open
source
communities.
You
know
I'm
fully
able
to
to
maintain
its
net
commitment,
and
you
know
feel
good
about
the
work
that
I'm
doing
right.
A
A
B
B
You
know,
contribute
back
our
our
experience
want
to
learn
more
about
how
our
peers
are
solving
challenges
like
the
one
we
experienced
with
OpenSSL,
and
you
know
that
that's
valuable
to
us,
but
the
the
the
just
ongoing
turning
the
crank
and
even
you
know
really
making
sure
that
we
have
a
good
agenda
in
any
direction.
Yeah
I'm,
definitely
struggling
with
that
right.
A
A
Lots
of
people
at
the
calm,
calm
level.
You
know
they're
pushing
different
they're
different
different
initiatives.
So,
in
my
mind,
it's
better
if
you
continue
to
help
and
if
you
had
more
cycles
to
push
on
the
user
feedback
side
versus
the
generic
calm,
calm,
stuff,
right,
cuz,
I,
don't
see,
I,
don't
think
we
have
a
huge
problem
on
in
the
generic.
You
know:
calm,
calm,
stuff,
others.
B
B
B
You
know
working
day
today
you
know
so
I
don't
have
that
sort
of
data
input
or
the
calm.
Calm.
That's
the
you
know,
that's
part
of
the
challenge.
There
is,
you
know,
I,
you
know
in
facilitating
user
feedback
has
to
be
directed
somewhere,
and
you
know
if
we
don't
have
the
external
audience
that
were
connecting
things
from
and
the
internal
connective
tissue
that
we're
driving
things
to
then
it's
just
me
talking
guys.
A
A
F
D
B
Yeah
in
the
community
committee
that,
with
the
expressed
purpose
of
connecting
the
broader
end
user
committee
community
to
our
efforts,
folks
that
that
are
you
know,
working
on
the
core
you
tend
to
want
to.
You
know,
focus
and
spend
their
time.
You
know
solving
core
issues,
you
know
programming
and
not
doing
the
more
human
outreach,
and
you
know
this
group
was
formed
to
you,
provided
an
opportunity
for
in
a
forum
for
that
outreach.
D
A
We
should
have
an
agenda
I'm
all
the
way
the
other
working
groups
work
is
we
have
issues
they're
tagged
for
the
agenda,
that's
what
shows
up
and
we
go
through.
Those
is
part
of
the
agenda.
I.
Think,
though
I
mean
we
have
had
some
things
on
the
agenda
like
we
were
working
to
get
sessions
in
to
meetups
like
we,
we
started
by
saying,
let's
see
if
we
can
organize
people
to
come
and
give
us
their
feedback
in
person,
we
tried
that
that
was
a
challenge.
A
We
then
said,
can
we
have
online
meetups
and
we
did
one
of
those,
but
then
the
meetup
tool,
Mina,
basically
said
nope.
You
have
to
be
in
person,
so
the
latest
effort
was
to
say:
can
we
actually
use
sessions
like
a
section
and
existing
meetups
to
get
feedback
and
and
the
the
idea
is
really
just
the
trying?
Yet
if
there's
feedback
from
the
community
and
side
core,
how
do
we
get
that
information
back
to
core?
B
The
main
main
feedback
is,
you
know,
developers
aren't
having
you
know,
any
large
existential
challenges
with
you
know
node
or
upgrading
node.
You
know
relatively
it's
relatively
straightforward.
We've
been
working
hard
since
we
landed
no
to
the
foundation
to
really
ensure
and
deliver
stability
and
yeah
like
we're
doing
that.
That's
great
but
ping,
point
being
a
WS,
lambda
being
you
know
fairly
behind
its
nose
version.
So
it's
not
anything
that
that
the
foundation
or
core
collaborators
could
do.
B
B
D
B
Don't
have
any
so
you
know
you
basically
have
the
the
core
working
the
core
team
of
folks.
You
know
collaborating
on
this.
You
know
reconvening
after
a
bit
of
a
summer
pause,
and
you
know
considering
where
we're
going
to
go
from
here
and
you
know
how
best
to
use.
They
know
the
time
in
our
abilities,
yeah.
A
D
Basically,
here
I
know:
Tracy's
been
in
these
meetings
on
behalf
of
the
foundation
in
the
past
and
she's
been
she's
had
conflicts
lately
with
these
meetings.
So
she
wanted
me
to
sit
in
and
see
if
I
could
kind
of
take
over
for
her.
So
I
am
really
happy
to
help
in
any
way.
That
is
useful
to
you
guys
if
there's
some
way
that
I
can
put
together
an
agenda
for
a
future
meeting
so
that
we
can
be
more
focused
and
get
more
accomplished
and
totally
happy
to
do
that.
D
F
B
B
B
Kind
of
detailed
edges
of
the
platform:
okay,
that's
well
III,
think
you
know
one
person
Michael
Dawson
could
be.
You
know
able
to
begin
to
to
address
and
we
need
you
know
if
we're
ever
gonna
go
that
direction.
I
think
we
need
to
really
recruit.
You
know
more
core
collaborators
to
you
know
to
participate
in
that
right.
Right.
D
Well,
and
and
our
future,
if
you're
having
this
wonderful
problem
of
nobody
actually
having
any
like
super
existential
crisis
right
now,
then
maybe
it
makes
sense
for
us
to
extend
a
little
bit
into
some
of
those
feature
requests
because
those
might
be
also
considered
a
form
of
user
feedback.
I,
don't
know
in
my
mind
the
things
that
people
are
looking
for,
but
I
don't
know
how
realistic
that
is
on
my
part.
So
please
please
correct
me
if
I'm
wrong,
that's.
A
A
C
B
You
know
one
additional
thing
that
I
think
would
be
good
to
know
to
make
sure
we're
doing.
Yo
useful
work
on
behalf
of
someone's
is:
are
those
feature
requests
that
are
coming
into
the
project
challenging
for
the
core
team
to
process
right?
Are
they
like
the
last
thing?
That'd
be
great
or
you
know
not,
you
know,
or
is
it?
Is
it
that
they're
you
know
either
too
targeted
or
too
specific.
D
B
B
A
D
B
Lot
of
those
issues
that
I'm
reading
through
seem
like
more
than
that
second
set
of
issues
that
are
like
really
esoteric
edge
of
the
platform
that
you
know
a
lot
of
those
sorts
of
challenges
for
a
mature
platform
like
node
is
really
you
know,
figuring
out.
If
we
do
that,
one
little
change
over
there
like
is
it
gonna
break?
You
know
a
bazillion
other
things.
You
know
because
we're
making
some
sort
of
trade-off,
yeah,
trusting.
A
G
A
B
Champion
I
wanna
feel
like
I'm.
You
know,
moving
things
forward,
so
I
feel
like
I'm
going
forward
is
the
or
at
least
you
know
giving
space
to
you
know
it
moving
forward.
Is
the
enterprise
right
I
feel
really
good
about
that,
and
actually
you
know
it's
a
hundred
percent
defensible
for
me
in
terms
of
use
of
time
for
work.
It's
great
and
you
know
so.
You
know
that's
that's
great.
B
Many
of
the
proposals
that
we
talked
about
in
terms
of
you
know,
working
group
facilitation
and
other
things
involve
a
level
of
effort
that
I
I
feel
uncomfortable
committing
to
just
because
of
my
current
availability,
not
that
I
don't
think
they're,
yeah,
right
or
needed
by
the
community.
I.
Just
think
that
that
you
know
in
those
cases,
I'd
love
to
see
them
serviced
by
a
group
of
individual
school.
You
know
have
the
time,
interest
and
availability.
You.
F
B
Or
have
you
know
some
other
explicit
need
that
we're
working
towards
right?
You
know
something
that,
were
you
know,
working
toward?
That's
concrete.
You
know,
I
want
to
make
sure
that
that
effort
continues,
and
you
know
we
can
serve
that
enterprise
working
group
I
know
have
some
concerns
that
as
awkward
evolves,
his
new
role
that
he'll
be
able
to
continue
to
move
that
form
and
and
then
he
might
need
two
additional
help
to
support
him.
That
club
would
be
you
know
he
hasn't
liked
that
as
a
concern
on
his
end.
B
A
I,
you
know
I'm
just
thinking
like
in
terms
of
it.
If
that's
it,
it
sounds
like
that
would
open
up
that
would
make
it
clearer
and
open
up
space
for
somebody,
it's
basically
say
ready,
we're
gonna,
you
know
the
the
general
user
feedback
is
gonna,
go
on
a
hiatus
for
a
while
like
then,
then
can't
can't
manage
the
time
to
push
that
in
the
other
day,
and
then
it's
like
that,
if
somebody
else
has
the
time
to
step
up
then
great
and
here,
but
it
makes
it
explicitly.
B
A
It's
basically
saying:
okay,
this
is
where
we're
at
you
know.
We
either
need
to
rally
more
people
to
get
involved.
We've
made
an
effort
on
these
different
areas
and
haven't
been
super.
Successful
I
mean
we
can
take
a
pause
and
then
regroup,
maybe
sometime
later
or
and
but
you
know
the
the
enterprise
user
feedback.
I
guess.
The
only
part,
that's
still
kind
of
activist
is
the
the
surveys,
but
you
know
that
might
be
something
we
can
work
with
the
foundation
to
put
a
point
of
contact
for
that
right.
B
And
you
know
we
are
primarily
a
proxy
and
a
support
mechanism,
for
you
know
what
the
Foundation
provides
there
only
yeah
so
like
it
is
ultimately
that
the
survey
is
ultimately
a
foundation
delivered
capability.
So
you
know
it.
You
know
it
was
a
unique
value
that
that
we
sort
of
helped
other
people
other
groups,
other
working
groups.
It
would
get
access
to
get
better
access
to
better
understanding.
You
know,
rather
than
the
annual
just
the
annual
do
marketing
survey.
D
D
A
A
D
D
A
Sounds
good
so
I
mean
I,
don't
say
we
need
to
make
a
decision
now,
but
it
seems
like
it's
it's
you
know,
as
if
Dan
makes
this
decision.
You
know
the
two
of
the
three.
If
he
says,
hey
I
want
to
focus
on
user
feedback
and
put
more
energy
into
that
to
help
figure
it
next
steps,
then
the
answer
might
be
different
than
hey.
No
I
I
want
to
stay
in
the
kumkum
side,
the
general
compound
side
and
drop
this.
A
You
know
at
that
point:
it's
like
okay,
we
can
it'll
be
clearer
to
the
calm,
calm
that
haters
they're
space.
Somebody
else
wants
to
step
up
you
and
the
rest
of
us
who
are
involved
can
also
think
about
that
same
good,
and
you
know
we'll
see,
see
where
we've
gone.
We
can
at
least
say
we've
made
an
effort
on
this
front
for
sure
we
just
haven't
quite
figured
out
the
answer
yet
right.
B
And
you
know
I'd
also
like
to
before
I,
you
know,
make
any
sort
of
move
like
that.
I'd
like
to
sync
up
with
augmented
to
you,
know,
discuss
how
you
know
how
we're
able
to
keep
that
ever
moving
without
me
doing
this.
Turning
the
crank
stuff
right,
because
you
know
he's
been
able
to
sort
of
you
know,
keep
the
efforts
they're
moving.
You
know
with
some
of
that
basic
momentum
handle
and
you
know
the
dynamic
would
change.
If
there's
you
know,
no
one,
you
know
behind
the
you.
Have
the
core
motion
of
the
yeah.
A
B
D
B
I
made
the
decision
to
say
yeah
cool
all
right,
we'll
we'll
end
it
here,
and
you
know
that's
useful
feedback
for
me
and
you
know
probably
follow
up
with
you
know.
Achmed
and
probably
Mihai
offline
to
you
know
check
with
the
everybody
and
you
know
try
to
kind
of
written,
bring
to
the
table.
Calm.
The
community
committee
know
just
community
committee
that
understanding
you
know
that
would
be
the
faces.
We
are
team
with
the
compound.