►
From YouTube: Node.js User Feedback Initiative Meeting
Description
C
D
B
D
C
I
did
yeah
I
updated
it
like
a
week
later,
when
I
was
like
trying
to
look
for
this
meeting
and
couldn't
I.
B
B
So
it
was
the
last
meeting
for
a
moment
and
then
took
a
second
since
I
am
usually
trying
to
get
away
from
the
YouTube
screen
as
fast
as
possible
and
pause.
It
I
don't
stay
there.
Okay,
let's
get
started
since
we
have
full
quorum
here,
and
you
know
we're
kind
of
kicking
off
the
new
year.
Why
don't
we?
You
know,
start
to
start
the
year
with
the
just
some
introductions,
and
you
know
like
who
we
are
so
I'll
kick
it
off.
B
F
G
D
H
Yeah
hello
I
mean
hi
I'm,
with
the
project
management
institute,
I'm
a
project
manager
over
here
and
trying
to
help
not
gs
user
feedback.
Thanks
to
then
I
started
with
him.
This
group
and
thanks
to
Michael
right
now
we
have
one
year
in
two
or
three
months,
yes
and
looking
forward
to
help
more.
So
thank
you.
Sevilla.
I
B
B
Why
don't
I?
Just
you
know
we
got
a
couple
topics
around
surveys
will
finally
kick
it
over
to
Giuseppe
for
just
an
update
err
rather
than
me,
going
through
the
list
of
things.
G
Yeah
sure
I,
don't
I,
don't
have
too
much
of
an
update
in
the
sense
that
the
promises
survey
I
asked
mr.
Jules
and
Benjamin
to
try
to
help
shape
the
survey.
So
we
could
get
it
further.
I
think
at
that
point,
when
I
asked
mr.
Jules
had
already
done
some
of
that
work.
So
maybe
he
or
she
didn't
you
know
felt
like
they
had
kind
of
done
that
already
I.
G
You
know
tag
Ben
as
well.
I
hadn't
heard
from
him
I'm
trying
to
figure
out
what's
the
best
way
to
maybe
bump
them
again
ping
them
and
see
if
they
are
interested
in
helping
me
move
this
forward
and
I
was
going
to
move
to
the
upgrading.
The
migration
survey
requests,
but
I
thought
that
it
might
make
sense
to
start
to
develop
work
so
that
when
I
ping,
whoever
is
involved
there,
I
can
give
them
clear
direction.
G
I
have
I
think
Dan
dropped
the
link
in
the
chat
there's.
Also
a
Google
Doc
there
that
I
just
started
to
capture
the
high
level
bits
that
I
think
we
need
and
I'm
gonna
try
to
flesh
out
what
each
of
those
high-level
bits
should
look
like
and
I
don't
know
if
we
should
have
some
sort
of
issue
template
or
anything
like
that
or
something
available
to
people
to
fill
out,
but
yeah
I'm
starting
down
that
path.
G
B
C
We
talked
about,
and
we
talked
about
this
a
little
bit
later
the
year
last
year
and
we're
super
happy
once
you
guys
are
ready
with
the
first
one
for
us
to
just
take
that
and
create
you
know,
help
create
the
process
and
just
kind
of
stick
it
up
in
a
pipeline
right.
What
we
want
is
something
very
repeatable
so
that
it's
not
always
like.
Oh
man,
we
need
to
send
out
a
survey.
Okay,
what
are
the
10
million
things?
We
need
to
do
to
make
this
actually
right.
C
B
And
that's
that's
amazing
and
super
helpful.
You
know
once
we
have
the
content
basically
prepared.
You
know,
then
we
can
hand
it
off
to
that
workflow
and
you
know
I
think
that'll
be
amazing.
Last
time
we
did
the
benchmarking
working
group
survey.
You
know
we
were
able
to
lean
on
the
foundation,
but
the
foundation
was
then
leaning
on
external
subject
matter,
expert
and
contractor.
So
you
know
what
I
think
we
might
need
for
to
sort
of
get
everything
across
the
the
finish
line
here
was
giuseppe,
is
you
know?
B
Maybe
let's
see
if
we
can
go,
and
you
know
get
the
foundation
to
put
a
couple
hours
of
that
individuals
time
you
know
to
give
us
some
of
those.
You
know
key
insights
into.
You
know
how
to
ingest
the
requests
for
survey
put
them
into
a
you,
know,
usable
format.
You
know
what
kind
of
things
we're
looking
for
at
that
point
in
the
pipeline
and
because
you
know
I
I
I
can
help
with
the
mechanics.
I
can't
help
with
the
physics
and
yeah.
E
D
C
B
D
Should
be
part
of
the
process,
I
think
we
want
to
follow
what
we
did
with
the
last
one,
which
was
we
did
put
it
into
get.
We
landed
in
github
so
that
the
data
was
public.
There
was
some
pieces
that
needed
to
be
removed.
I
think,
like
you
know,
it
didn't
include
your
name
and
that
kind
of
stuff,
but
yeah
I,
think
that
should
all
be
part
of
the
flow.
D
So
it's
clear
that
you
know
you
get
a
survey
and
in
the
end
it's
in
the
public
and
maybe
these
pieces
aren't
available,
but
the
rest
of
it
all
is
because
that
is
a
definitely
a
key.
You
know
it's
in
my
mind.
It's
a
key
part
of
what
we're
doing
here.
It's
not
just
that
we
get
to
look
at
the
data,
but
a
broader
group
can
look
at
the
data
and
learn
from
it
as
well.
D
G
Yes,
so,
along
those
lines,
Allah
I'll
try
to
find
some
time
today
or
early
next
week
to
further
flesh
out
what
I
had
started
in
the
Google
Doc.
And
then
you
know
Dan
I,
don't
know.
If
you
find
this
this
person's
name
or
you
know
late
Tracy
I
can
work
with
you
or
Sophia
or
anyone
to
figure
out.
G
C
I
would
just
say
first
things.
First,
let's
just
you
know
get
I
think
last
time
it
was,
you
guys
were
figuring
out.
Okay,
what
you
know,
which
one
should
we
do
and
or
what
questions
should
we
ask
and
then
holidays
hit
us?
So
if
you
tell
me
like
hey
we're
ready
to
go
with
X,
then
let's
just
you
know,
let's
just
get
started
with
the
process
anyways
and
then
ask
all
the
questions
along
the
way.
Okay,.
A
G
I
think
you
know,
maybe,
with
that
in
mind,
I'll
go
back
to
the
promises.
Survey,
see
what
the
status
is.
Maybe
ping,
those
two
key
people
again
and
say
hey.
This
looks
like
you
know
it's
in
this
sort
of
a
state.
Maybe
it's
ready
to
go
and
see
if
anybody
has
any
thoughts
before
we
try
to
move
forward.
If
it
looks
like
it's
something
that
is
out
of
stage
where
we
can
move
forward
on
it
and
then
learn
from
there,
you
know
figure
it
out,
we'll
be
back
I'm.
C
C
B
C
B
In
our
current
current
state,
I
think
we
need
you
know
a
couple
of
hours
of
advisement
with
a
subject
matter
expert
to
really
you
know,
be
able
to
help
and
serve
our
you
know
technical
experts
and
translate
that
into
survey
questions
you
know
just
just
for
contacts.
Even
even
then
you
know
the
individual
that
we
were
working
with
is
expert
in
surveys
and
most
of
the
surveys
that
you
know
the
foundation
has
been
executing
on
our
kind
of
marketing
or
it
right
we're
pulling
in
marketing
resources.
C
Sure
I
mean
I
think
probably
the
best
way
to
do.
That
is
number
one.
Let's
find
the
person
but
number
two,
let's
just
come
up
with
the
questions
and
then,
as
a
last
step
or
as
a
you
know.
Second,
to
last
step
we
have
that
person
review,
so
we
can
come
up
with
the
questions
make
all
of
them.
You
know
semi
wrong
or
leading
or
whatever,
and
then
until
we
really
need
a
person.
You
know
it's
like
you,
like
node,
right
notice,
awesome.
C
C
G
All
right
cool!
Well,
that
sounds
like
a
good
plan,
we'll
just
we'll
move
forward
and
learn
as
we
go.
So
I
will
focus
on
the
promises.
One
first
I
will
try
to
flesh
out
the
framework
aspects
and
we'll
leave
that
issue
open.
Everybody
feel
free
to
get
in
there
whenever
they
think
of
something
notice.
Something
learn
something
and
we'll
keep
that
going
until
it
gets
to
a
decent
state
that
we
can
PR.
It's
PR
something
into
the
repository.
D
That
one
now
I
know
the
person
and
I
forget
his
name
because
I'm
so
bad
at
that
has
sort
of
been
pulled
off
onto
other
things.
He
was
an
IBM.
My
partner
I
think
he's
moved
for
a
company,
but
I'm
still
interested
in
that
one.
So
I
think,
let's
keep
it
on
the
list
and
once
we
get
the
other
ones
out,
we
can
figure
out
what
we
can
do
on
that
one.
Because,
okay,
you
know
I
think
it's
typescript.
B
D
B
That'll,
be
really
good
that
no
a
tipping
point,
where
is
with
you,
know
the
application
ecosystem
layer,
but
you
know
like
promises,
you
know
the
the
community.
You
know
hit
a
tipping
point.
You
know
in
application
development
and
then
nodes
behind
right.
You
know,
and
you
know
the
core
API
is
aren't
in
line
with
the
types
of
behavior
that
the
end
user
community
is
is
trying
to
do
with
the
rest
of
the
platform.
So
you
know
that.
D
I
mean
I,
think
we
getting
that
data
and
then
trying
to
figure
out
what
that
means.
We
think
would
be.
You
know
what
should
know
Deus
as
a
project
be
doing
to
address
that
reality.
As
he
said,
or
you
know
context,
okay
sounds
like
you're
interested
as
well,
so
once
we
get
these
other
two,
we
can
collaborate
to
figure
out
how
to
move
that
one
forward
again
and.
C
B
D
C
E
G
B
G
G
B
Requests
leave
validate
that
you
do
or
don't,
and
let's
rectify
that
we
don't
have
you
on
the
team
so
and
the
official
list
is
that
the
standard
er
nope-
that's
me
hi!
So
let's
get
you
PR
on
to
the
team.
That's
okay!
Let's
rectify
that,
and
ones
deal
with
that.
So
you
can
do
that,
but
you
know,
in
the
sake
of
not
losing
a
very
simple
action
item,
any
thoughts
on
what
the
survey
just
survey.
A
B
C
Think
that's
a
really
big
thing.
You
know
meeting
every
two
weeks
is
obviously
great
with
everyone's
schedule,
but
at
the
same
time
like
yep,
it's
like
man
yeah,
unless
you're
meeting
every
week
the
progress
is
slower
which
okay,
but
let's
do,
meetings
every
week,
I'm
just
kidding.
B
Yeah
yeah
I
would
characterize
this,
like
everyone
has
their
toehold
into
this.
There
are
a
few
individuals
like
you
know,
Michael
who
work
full-time,
but
then
you
know
Michaels
working
full-time
across
all
of
the
things
that
are
going
on,
so
even
even
in
that
the
individuals
that
are
full
time.
You
know
these
touch
points
across
the
working
groups.
Are
you
know?
B
Just
just
you
know
one
of
those
attention
zones
that
they're
hitting
so
that
that
that's
a
good
thing
to
take
into
consideration
as
we're
building
these
frameworks
and
guidelines
that
you
know
that
is
the
the
standard.
Not
you
know
our
normal
business
expectations.
Where
we're
you
know
we're
constantly
driving
towards
that
in
game.
B
D
D
F
E
D
D
B
B
E
D
B
Excellent,
so
this
issue
96,
where
we're
dressing
up
grading
problems,
is
you
know,
kind
of
the
the
conceptual
anchor
for
our
next
step
with
our
meetups
right.
So
let's
move
from
that.
So
the
reason
being
is
you
know
last
time
when
we
had
the
the
major
version
bump,
so
we
moved
from
the
LTS
release.
B
So
you
know,
as
we're
looking
at
kicking
off
are
the
kind
of
next
generation
of
general
user
feedback.
We're
looking
at
the
the
you
know
just
meet
up
format
where
we're
going
to
do
some.
Some
sharing
some
feedback-
and
you
know
broader
promotions.
You
know
and
we're
thinking
about
anchoring
that,
at
least
in
the
first
couple
iterations
in
you
know
in
the
transition
from
ten
to
eleven
currents.
What
was
the
it's
in
March
or
April
Michael,
all
right,
whisper.
G
B
D
It
should
be
like
yeah,
I'm
gonna,
say
it's
April,
okay,.
B
B
B
You
know:
we've
worked
out
a
lot
of
those
those
kinks
and
you
know
provided
that
feedback
to
you
know
the
new
collaborators
and
you
know,
work
that
out,
and
so
you
know
more
more
shops.
Can
you
know,
deploy
with
confidence
and
also
just
just
have
some
context
that
you
know
social
proof,
basically,
that
you
know
a
Tellez
is
doing
it.
Paypal
is
doing
it
Netflix
doing
it,
and
you
know
IBM's
got
this
in
production.
You
know,
we've
we've
all
comfortable
of
this
too
yeah.
B
C
Sure
deal
so
the
whole
idea
we
had
at
the
last
meeting
was
to
get
some
of
the
folks
to
sort
of
test
out
what
it
would
look
like
to
get
user
feedback
from
actual
meetups.
So
we're
thinking
you
know
maybe
Toronto,
maybe
New
York
sounds
like
San
Francisco's.
Okay,
we
just
have
to
schedule
it
in
for
I.
Think
you
said,
April
dan
I've
been
recently
talking
to
Ben
over
at
node
Portland,
so
I
could
probably
poke
him
as
well,
and
he'd
probably
be
interested
in
helping
out
with
that.
C
So
really
what
we
want
to
do
is
create
a
framework,
so
I've
been
working
with
Sophie
to
put
together,
like
kind
of
like
a
how-to,
so
you're
a
contributor
you're
going
to
this
meetup.
What
are
the
different
steps?
You
need
to
do
to
kind
of
create
user
feedback
process
the
same
across
all
the
different
meetups
kind
of
like
a
guideline
of
how
to
do
that.
In
addition
to
that,
we
are
we,
you
know
we
we
did
put
on
the
calendar.
We
have
two
blog
posts,
actually
one
to
be
launched,
generate
14,
so
we're
past.
C
That
deadline
share
the
drafts,
as
you
guys
thank
you
for
the
comments
but
kind
of
need
to
dig
back
into
that
and
figure
out.
Okay
is
this
where
we
thought
we
were
going
and
then
we
did
have
another
one
that
we
wanted
to
schedule,
sort
of
early,
February
and
I
think
this
was
for
enterprise
user
feedback.
So
we
should
probably
start
talking
about
that
and
kind
of
what
we
want
that
blog
post,
maybe
so
yeah
any
comments
on
those
three
things
and
where
your
all's
head
are
at
would
be
great.
Can.
A
D
C
B
An
open
question,
so
the
reason
why
I'm
you
know
pushing
out
as
far
as
April
4sf
node
you
know
is
that's
where
I
know
that
I
can
sort
of
negotiate
new
content
and
not
you
know,
push
out
existing
sponsors
or
whatever.
So
you
know
in
in
our
April
event,
you
know,
I'm
looking
to
you
know,
have
an
anchor
speaker
who
can
come
in
and
you
speak
to
the
release.
You
know,
in
my
case
I'm
gonna
rope
in
James
Snell
to
to
do
that.
Heavy
lifting
you
know,
maybe
maybe
shoot
you
know
Michael.
B
E
B
Candidate
would
be,
you
know,
miles
coming
up
from
New
York.
You
know
that
that's
a
relatively
you
know
straightforward
day
trip
from
New
York
to
Toronto.
So
you
know,
though,
bringing
bringing
that
aspect
right.
We're
we're
gonna,
be
adding
the
the
value
that
any
you
know
we
bring
any
of
those.
You
know
heavy
hitters
and
Tomita
yeah
I
think
we
are
swage
most
of
those
concerns.
B
F
B
F
Think
the
context
that
a
local
organizer
would
ask
rightfully
so
that
you
know
they're
planning
their
events.
Are
we
asking
them
that,
let's,
let's
work
with
you,
whatever?
That
means
to
plan
a
feedback,
specific
event
and
I,
don't
think
to
ask
monetary
per
se
as
much
as
what
is
the
actual
expectation
versus?
Oh,
you
got
an
events
coming
up
in
April,
hey,
let's
bring
Michael
in
and
dedicate
time
to
talk
about
some
right,
I
think.
C
D
D
F
Said
effectively,
that's
the
case.
You
know
when
most
people
meetups
it's
one
talk
40
minutes.
That's
it
right,
nothing!
It's
just
how
we
position
our
our
ask
is.
The
question
is
like:
are
we
offering
speakers
to
provide
certain
topics
within
whatever
schedule
that
the
local
groups
may
or
may
not
want
to
do?
Or
are
we
also
asking
the
local
groups
hey?
D
F
C
D
But
I
guess
it's
more
of
the
like
it's
it's
not
you
know,
I,
don't
think
it's
quite
what
a
mad
said,
which
is
just
like.
We
have
speakers
that
can
come
and
deliver
whatever
topics
you
want.
It's
more
like
we'd
like
to
have
a
topic.
This
topic,
like
we'd,
like
to
take
two
slots
of
twenty
minutes,
and
if
that
happens,
to
be
the
whole
meetup,
maybe
you
know,
then
it
sort
of
bridges
the
thing
it's
not
just
sort
of
like
hey.
We
got
people
who
will
come
and
talk
anytime.
D
It
may
be
that
we
could
offer
that
as
as
a
side
thing
so
forgive.
G
Me
let
me
ask
like
what
what
is
the
the
the
takeaway
from
these
meetups
that
were
hoping
to
get?
Is
it
to
like
gather
more
information
on
you
know,
feedback
from
users
or
particularly
upgrade
problems,
or
so
I
guess,
yeah,
I'm
ganna
think
through
what
would
work
well
in
order,
so
like
went
on
I'm.
Having
is
you
know
what,
if
we
did
I'm
imagining
the
node
feed
the
node
meetup
in
New
York?
G
You
know
we
can
have
a
panel
and
sort
of
a
town
hall
like
setting
where
maybe
somebody
gives
like
a
maybe
15
20
minute
talk
on
like
what's
coming
up
a
node
or
what's
new
in
the
latest
release,
and
then
we
have
a
panel
where
people
can
take
turns
like
a
town
hall
saying
what
their
pain
points
are.
What's
preventing
them
from
upgrading
and
the
panel
can
give
some.
You
know
feedback
and
thoughts,
but
also
somebody's
capturing.
You
know
these
these
items
and
taking
them
back.
Yeah.
D
The
goal
the
goal
is
to
do
that
like
to
do
some
of
the
actual
stuff
and
then
build
like
it's
good
as
a
one-off,
but
anything
else
we
can
do
around
this
as
well.
That
helps
to
build
the
future
engagement
right,
so
I
think
I'm
added
had
pointed
out
earlier
in
one
of
the
other
meetings.
This
it's
just
as
important
to
also
make
people
at
the
end
feel
more
empowered
to
say,
go
open
issues
or
get
involved
in
the
in
the
traditional
feedback
channels.
D
So
it's
like,
let's,
let's
try
and
Clin
and
like
provide
another
way
for
people
to
get
the
feedback
to
us,
reinforce
our
existing
feedback
channels
and
just
try
and
like
I,
think
we're
still
working
to
figure
out.
How
do
we
have
a
stronger
tie
to
those
end
users?
You
know
we've
got
a
good
tie
to
the
core
collaborators,
but
how
do
we
get
stronger
ties?
One?
Let
one
layer
out-
and
this
is
our
current
current
thinking,
so
that's
kind
of
the
strategic
goal.
F
D
J
F
And
what
you're
saying
Dawson
you
were
talking
about
before
is
that
the
KPI.
However,
we
frame
it,
it
should
be
that
we're
actually
opening
up
the
pipeline
of
contributions
to
the
standard,
traditional
channels
that
we
already
have,
but
the
more
we're
able
to
enable
that
the
more
successful
it
is,
whether.
D
D
F
D
G
I
think
like
similar
with
probably
with
Dan,
you
know:
we've
got
a
great
node
meetup
in
New,
York,
City
and
I
can
imagine
you
know
trying
to
do
something
with
them,
and
maybe
it's
even
like
a
quarterly.
You
know
maybe
not
taking
their
meetup
slot,
but
like
an
additional
meetup
quarterly.
That's
that's.
It
meant
to
engage
the
local
community
and
we
can
get
a
cadence
there.
We
can
start
to
flesh
out
formats
and
what
works
well.
Yeah.
C
I,
like
the
repetition
yeah
like
I,
really
love
that
it's
like
this
whole
idea
about
hey,
okay,
you're
hosting
a
node
meetups,
so
part
of
hosting
the
no
meetup
is
every
quarter
or
twice
a
year.
We
have
this
user
feedback
thing
twice.
Yes,
Dan,
I
kind
of
kind
of
agree
with
you
twice
a
year
is
probably
the
right
cadence.
So
saying
like
okay,
every
you
know,
every
just
right,
September
and
every
February
we're
doing
this
thing.
You
know
and.
C
H
C
D
E
C
C
H
D
G
I
could
see
if
we
did
it
if
we
kind
of
did
it
twice
a
year
in
each
location
like
say
just
thinking
about
New
York
from
San
Francisco.
We
could
just
alternate
quarters.
You
know,
I'm
gonna,
give
you
winter
Dan
cuz
it's
not
as
cold
out
there
when
you're
in
summer,
and
we
could
do
spring
and
fall
and
this
you
know
kind
of,
do
it
quarterly,
but
on
each
side,
the
coast
and
then
augment
everywhere
else.
As
we
go
there.
B
You
know
really
interesting
anchors
that
we
have
every
year
and
that's
the
the
the
time
that
our
major
release
goes
current
and
the
time
that
that
major
release
goes
LTS
it's
when
we
really
want
folks
to
pay
attention.
The
you
know
the
LTS
release
is
a
little
bit
more
impactful
in
October.
So
if
we're
you
know
gonna
blow
one
out,
it
should
be
that
one-
and
you
know
in
in
April
that
in
March,
April
and-
and
you
know
crazy
is-
is
there
something?
Is
that
calendar
and
seasoning
it
seasonal
Google.
C
Everyone,
its
deficit,
even
so
I
think
the
reason
that's
good
is
because
you
know
one
thing:
I
did
after
our
meeting
was
ask
tyranny
and
then
ask
internally
as
well.
If
there
was
just
a
list
of
local
node,
meetups
and
I.
Think
I
opened
up
an
issue
in
the
kumkum
repo
to
say:
hey.
Is
there
a
list
of
local
meetups
and
can
we
create
one
because
you
know
I?
Do
that
a
lot
right
like
women
speakers
and
just
you
know,
it's
become
a
gigantic
list.
C
No
communities
gonna
want
to
do
that,
and
once
we
have
that
list
and
that
list
of
organizers
we
can
just
send
out
an
email
blast
and
say,
like
hey
its
user
feedback
time.
We
do
this
once
every
you
know
once
every
two
six
months,
if
you'd
like
to
do
it,
here's
this
thing
and
you
can
run
it
yourself,
like
that's
very,
hopefully,
very
coordinated
in
that
sense
and
of
course
we
do
the
test
for
us,
but
I'm,
just
thinking
a
long
term
of
how
we
can
ski.
D
C
You
know
what
actually
might
be
interesting
is.
Could
we
also
create
sort
of
like
a
markdown
file
somewhere,
maybe
on
Kham
Kham
to
just
say
like
a
list
of
local
contributors
and
just
have
all
the
contributors
you
know,
and
then
that
way
people
can
sort
they're
like
oh
I'm,
in
California,
oh
cool!
Look.
These
people
are
here
that
way
it's
easier.
For
you
know
it
serves
as
a
as
something
for
the
local
node
meetups.
Well,
whether
it's
freeze
or
feedback
or
whether
it's
for
other
things.
H
D
D
C
You
know
this
kind
of
feeds
into
you
know:
foundation
started
that
speaker.
What
does
it.
C
Kind
of
like
that,
a
little
bit
less
maintenance.
Now
the
other
question
is:
should
this
know
it's
gonna
create
some
noise
right
for
you
know
whatever
repo
it's
on
so
should
it
just
be
a
different
repo
of
like
maybe
like
node
meetups
or
something
or
should
it
stay
in
calm,
calm,
yeah,
no.
B
B
C
Good,
so
if
you
guys
are
cool
I'll
proceed
with
those
two
things
then,
and
I
also
created
a
short
thing
that
we
can
start
commenting
on
on
the
user
fee
I'm
going
to
create
an
issue
just
so
to
capture
like
the
stuff
that
we're
brainstorming,
cuz
I,
keep
writing
notes
everywhere
and
forgetting,
where
I'm,
putting
the
notes.
It's
driving
me
crazy,
so
I'll
just
use
the
issues
from
now
on
nice.
D
You
know
cadence,
where
we
have
like
feedback
week
or
something
like
try
and
capture
the
thoughts
that
we
have
and
what
we
think
is
a
good
direction
to
aim
for,
and
here's
what
we're
doing.
You
know
initially
we're
gonna,
try
and
do
one
at
SF
node
and
we're
gonna
try
and
do
one
in
Toronto,
and
we
can
see
if
that
generates
comments,
that
people
that
say,
hey.
D
That's
a
great
idea,
we're
interested
we're,
not
interested
kind
of
gets
the
message
out
and
may
get
us
some
feedback
on
on
the
idea
and
thoughts
that
were
sort
of
working.
As
a
longer-term
saying
you
know,
as
opposed
to
as
a
direct
like
how
to
get
you
know,
a
half
of
its
right
now
is
like
well,
how
do
you
get
involved
through
standard
channels?
D
You
know,
I
can
see
it
being
more
focused
about
we're,
trying
to
create
another
we're
trying
to
improve
that
link
with
the
the
the
greater
circle
of
people,
here's
what
we're
currently
thinking
and
what
we're
doing
to
to
move
in
that
direction.
If
you're
interested
in
participating
in
helping
out
you
know
in
that
effort,
let
us
know
like
if
you're,
if
you
run
out
meetup
and
would
like
to
to
be
involved,
you
know
this
is
what
we're
thinking.
So
let
us
know
what
you
think
if
it
makes
sense
or
not
what.
B
C
D
C
K
D
D
So
you
can
still
reference
the
issue
and
any
references
are
still
there,
but
it's
it's
an
indirection
I'm
sure
inside.
Maybe
we
have
an
older
version
or
the
enterprise
version
of
github
works
slightly
differently,
I'm
sure
it
closed
and
opened
a
new
one.
But
so
do
you
want
me
to
move
it
back
and
and
then
close
and
reference
or
is
like
the
link
being
the
reference
good
enough.
D
D
F
D
D
B
So
if
someone
were
to
come
in
and-
and
you
know
we're
saying-
no
that's
an
issue-
you
know,
for
you
know
some
other
group,
that's
fine,
but
this
issue
that
happens
to
be
you
know
the
evolution
of
our
thinking,
and
you
know
something
that
came
in
to
user
feedback,
and
then
we
collectively,
you
know,
made
the
decision
that
no,
we
need
to
create
a
new
technical
initiative
to
support
these
challenges-
and
you
know
now-
that's
created
over
here.
I'd
like
to
you
know,
maintain
that
thread.
Okay,.