►
From YouTube: Next 10 years of Node.js - Sep 17 2020
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
Next
10
meeting,
which
is
to
focus
on
you,
know
what
we
need
to
do
to
make
nodes
successful
for
the
next
10
years
and
we
oops.
We
will
follow
what
we
have
on
our
agenda.
So
let
me
pull
that
actually
up
hold
on.
A
So
we
have
on
the
agenda
and
I
also
I
suggest
we
talk
about
them
slightly
under
in
different
orders.
The
first
one
prioritizing
technical
values
is
what
we
spent
the
last
few
meetings
talking
about
and
the
current
status
on
that
is.
We
have
a
pr
open
and
I
guess
I
should
put
that
into
pr
into
the
issue
itself.
A
So
basically,
we've
worked
through.
We
have
a
pr
open
in
node
core,
it
looks
like
it's
been
favorably
received.
This
is
the
pr
right
here,
so
you
know
I
think
we
can.
We
can
agree,
we're
probably
closed
on
capturing
the
technical
values
for
the
project
and
move
on
to
the
other
issues.
So
does
anybody
have
anything
on
that
they'd
like
to
talk
about.
A
Okay,
so
the
next
thing
that's
on
the
agenda
is
the
next
10
years
for
collaborators,
so
we've
talked
about
you
know,
looking
at
the
the
technical
direction
and
think
you
know
the
technology
components
that
would
be
important,
but
mary
opened
this
issue
to
to
basically
reflect
that.
We
probably
also
want
to
include
in
the
overall
discussion.
A
You
know
what
it
should
look
like
for
collaborators,
and
you
know
what
we
should
be
doing
on
that
front
as
well.
So
that's
tagged
for
the
agenda,
so
I
think
at
this
point
those
are
the
only
you
know.
Those
are
the
only
things
we
had
on
the
agenda
and
having
worked
through
the
the
technical
values
we
should
agree
on.
What
we
think
is
the
most
important
thing
to
kind
of
focus
is
the
next
step
towards
moving
this
forward.
A
B
A
A
You
know
I
think,
in
absence
of
that,
it's
a
we
can
like
the
values.
I
think
we
can
come
up
with
a
proposal
and
then
we
need
to
make
sure
that
you
know
we've
got
the
the
the
tsc
like
agreeing
disagreeing,
or
you
know
at
least
at
least.
If
there's
no
opinion,
then
there's
no
opinion,
but
I
think
you
know
hopefully,
hopefully
concrete
things
like
if
we
say
x
is
the
most
important
thing
that
we
work
on.
Hopefully
that
will
generate
discussion
right
if
it's
not
the
right
thing.
A
B
No,
I
mean
I'm
wondering
if
you
know
a
lot
of
this,
would
you
know
there's
a
lot
of
thumbs
up
for
the
technical
doc
and
like
just
as
it
was
so.
It
feels
like
a
lot
of
people
had
time
to
review
it
async,
and
maybe
we
don't
have
any
other
feedback
to
give
right
now.
So.
A
A
So
in
terms
of
the
next
big
thing
to
tackle
you
know,
I
think
we
think
maybe
we
could
spend
a
little
bit
of
time,
brainstorming,
what
other
like
concrete
artifacts.
Would
we
want
to
come
up
with
and
start
to
work
on
right
like
I
can
see,
we
could
have
ones
around.
A
You
know
strategic
technical
area
focus
areas
like
we
think
we
need
to
do
focus
on
a
new
http
on
web
assembly
or
on
you
know
we
could
come
up
with
something
that
tries
to
capture
that
we
could
the
other
one
that
suggested
in
the
in
the
issue.
16
is
to
say,
okay.
Well,
what?
C
Personally,
that
topic
gets
my
vote
for
because
I
think
and
why
I
see
why
I'm
saying
that
is.
I
think
that,
like
you
bring
up
the
hdp
thing,
you
know
this
group
I
mean,
I
think,
really,
that
we
just
need
to
farm
out
to
the
rest
of
the
groups
and
and
contributors
right
and
just
say,
like
here,
open
up
an
issue
to
add
your
item
to
the
list,
whereas
I
think
you
know
talking
through
what
might
be
blockers.
C
A
D
A
Don't
necessarily
have
to
dive
in
but
like
what's
the
next
concrete
step
in
terms
of
getting
that
feedback
so
that
we
can
help
capture
it
you
know.
Is
it?
Is
it
an
issue
in
the
node
repo
that
says
you
know,
please
add
your
technical
or
somewhere.
You
know,
please
add
what
you
think
are
the
you
know
technical
priorities.
B
D
B
D
B
A
B
I'm
thinking
like
we
should
first
identify
like
who
the
audience
is
right,
so
something
like
even
for
our
working
group
sort
of
working
groups
that
we
have
in
the
project.
You
know
we
have
like
I'll.
Just
use
package
maintenance
working
group.
You
know
we
should
consider
the
audience
for
that
to
be
beyond
the
scope
of
of
node
right
and
the
node
community
right.
We
should
be
potentially
reaching
out
to
other
communities
to
ask
them.
If
you
know
these
are
solved
problems
and
right.
B
D
B
Or
anybody
could
have
feedback,
they
want
to
give
us
so
and
it's
not.
A
Yeah,
like
I,
I
think,
the
like
the
constituencies,
I
pasted
the
link
in
the
you
know
we
worked
on
who
were
the
consistent
receipts.
That's
probably
a
good
thing
to
keep
in
mind
in
terms
of
like:
where
should
we
be
getting
feedback
from
right.
E
B
Do
those
tribes
or
or
those
folks
what
are
the
channels
they
use
and
then
that
will
dictate
how
we
go
and
communicate.
B
A
I
mean
I
do
personally
think
just
going
out
and
saying
tell
me:
your
lists
is
not
going
to
work
very
well
like
I,
I
think
you
know
from
what
I
see
working
reasonably
well
is
to
try
and
actually
come
up
with
something
concrete,
even
if
it's
completely
wrong,
and
then
people
know
how
to
you
know
chime
in
on
that
and
say:
oh
something's
missing
or
no.
I
totally
disagree
with
that
or
the
white
space
doesn't
seem
to
get
much
concrete
feedback.
C
A
C
Little
bit
a
little
bit
on
to
that
sort
of
where's
the
on
ramp
for
people,
I
did
go
and
check
the
live
stream
link
on
one
of
the
discussions
we
had
just
recently
like
after
the.
B
About
like,
like
how
do
we
ensure
that
there's
fresh,
you
know,
opinions
a
diverse
group
of
people
coming
to
the
and
contributing
to
the
the
project
over
the
next
decade?
It's
like.
We
have
to
really
consider
yeah
like
exactly
what
you're
saying
was
like.
Like
you
know,
how
did
we
miss
that
opportunity
and
like
was
it
just
that
we
don't
look
at?
I
know
I'm
when
we're
running
the
npm
calls
like.
C
And
so
yeah
go
ahead,
yeah!
No,
it
totally
is.
I
agree
with
you
completely,
and
I
don't
monitor
that
either.
I
know
but
way
back
when,
when
we
were
doing
some
of
the
original
regularly
scheduled
express
tc
meetings,
I
tried
monitoring
the
youtube
chat
because
there
were
a
couple
of
people
who
would
randomly
show
up
like
that,
and
I
wasn't
sure
if
it
was
very
productive
anyway.
C
It
might
be
a
way
where
we
can
both
do
what
we
need
to
do,
where
it's
digging
deep
into
the
technical
issues
or
or
having
that
you
know
maybe
expert
conversation
and
then,
but
still
setting
aside
a
little
bit
to
have
that,
and
that
might
be
a
way
for
us
to
then
also
post
to
those
people
and
say
hey
if
you're
interested
in
this
from
like
a
intro
level
or
beginner
perspective,
here's
a
great
spot
to
start
right,
and
maybe
we
need
to
start
working
on
some
content
for
those
people
to
on
board.
C
You
know,
maybe
that's
in
a
repo
somewhere
or
maybe
it's
on
the
website
or
blog.
A
F
Out
the
answer
sorry
michael,
I
think
it
was
one
of
the
points
we
discussed
about
this
subject
during
the
summit.
I
think
maybe
the
four
or
five
points
something
like
that
about
how
to
bring
community
together
or
to
to
lower
the
entry
level
for
people
which
do
not
participate
currently
to
this
kind
of
meeting
or
stuff
and
oh,
they
can
contribute
or
give
their
feedback
or
stuff
like
that.
F
I
think
it
was
one
of
the
point
where
we
discussed
two
three
months
ago.
A
Like
I'm,
I
guess
I
I
don't
think
I
I'm
like
in
scope
is
saying
that's
one
of
the
key
things,
and
but
I'm
not
sure
solving
it
is
going
to
be,
should
be
the
focus
of
like
we're
not
going
to.
Similarly
to
saying
you
know,
http
is
a
strategic
technical
area,
which
is
what
our
focus
is
on
the
technical
side.
We're
not
going
to
go
then,
and
try
and
figure
out
all
the
ins
and
outs
of
what
has
to
happen
on
the
http
side.
To
make
that
happen
right.
B
Right
so
going
back
to
your
link
there
michael
like,
would
it
be
in
scope
to
more
flush
out,
let's
say
the
personas
of
these
constitution
like
constituents
like?
Would
that
help
then,
like
you
know
like
what
do
these
folks
want?
What
does
a
even
you
know,
hypothetically
like
trying
to
put
that
together
like
what
does
a
direct
end
user
versus
application
owner
want
where
like
because
then
that
would
drive
okay
and
where
did
they
live.
D
B
D
B
A
A
Yeah,
no,
I
think,
I
think,
trying
to
figure
out
what
each
of
those
constituencies
thinks
is
important
is
a
good
way,
because
we
want
to
be
able
to
map
back
the
okay.
Here's
the
technical
direction
you
know
and
http
is
important.
You
should
be
able
to
map
that
back
to
who
right
you're
right
so
that.
A
Yeah
it's
it's
like.
Why
do
we
think
this
will
lead
to
the
success
of
the
project?
It's
because
our
constituencies,
who
were
the
the
people
who
you
know,
are
the
stakeholders.
I
guess
they
are
interested
in
it
for
these
it's
important
to
them.
For
these
reasons
right
it
helps
them
do
x,
y
and
z
or
whatever,
and
therefore
you
know
it's
important
to
them.
Therefore,
it
will
make
node
successful
if
it
does
these
things
so
yeah
I'd
agree
with
that
in
terms
of
a
you
know,
one
of
the
thing
the
next
steps
could
be.
B
C
Right
so
one
thing:
if
we're
looking
for
that
feedback,
I'd
be
interested
to
hear
how
folks
thought
the
like
should
promises,
rejected
promises.
Crash
survey
went
like.
Did
we
get
enough
feedback?
There
was
that
feedback
actually
informative
to
the
decision
making
process
because
surveys
are
hit
or
miss?
I
guess
right,
like.
C
A
A
B
B
C
They're
sure
I
would
just
we
have
nowhere
near
2000,
total
engaged
and
where
I
say
engaged
I
mean
like
if
you
total,
every
individual
who
comes
to
any
meeting
even
remotely
related
in
the
past
year,
and
anybody
who's
commented
on
issues
and
committed.
C
It's
probably
still
not
even
close
to
two
thousand,
so
presumably
that
other
thousand
or
fifteen
hundred
are
probably
broadly
on
the
spectrum
from
beginner
to
node
expert
would
be
my
guess.
Right
like
I
know
it
was
on
twit.
It
was
on
twitter
so
like
if
you
just
take
a
random
assortment
of
of
twitter
people
who
follow
node
folks,
you
know
I
I'm
fairly
confident
we'll
that's
probably
valid
in
some
sort
of
representative
way.
B
A
D
I
think
that
it
was
maybe
included
in
some
email
lists,
but
I
don't
know
I
mean
there
was,
I
think
enough,
like
social
media
promotion
and
distribution,
that
you
know
it
would
be
hard
to
gauge.
You
know
what
percentage
responded
to
it,
because
we
don't.
B
The
interesting
part
is
like
was
that
is
that
many
individuals,
and
is
there
that
individual
constituent
is
their
voice
equal
to,
let's
say
like
push
back
from
an
organization
like
right
like
do
we
do
we
make
decisions
just
based
on
like
these
individual,
that
that
individual
polling
criteria
versus
tapping
potentially
large
organizations,
that
would
also
be
impacted
by
these
changes
right.
A
We've
yeah,
I
mean
we've
worked
on
that
in
the
past
we
had
a
user
feedback
group
and
actually
the
the
surveys
are
kind
of
the
last
remaining
piece
that
came
from
that
work
and
we
tried
to
set
up
a
a
group
which
would
meet
regularly
of
organizations.
You
know
large
organizations
who
were
using
node
to
say:
okay,
we're
gonna,
we're
gonna
meet
we're
willing
to
do
things
like
you
know,
test
out,
changes
and
and
give
feedback,
and
it
basically
petered
out.
A
You
know
lack
of
champions
on
our
side,
and
even
you
know
it
wasn't.
The
engagement
was
still
sort
of
pull
versus
having
you
know,
lots
of
people
jumping
in
and
making
us
vibrant
enough
that
it
kept
going
right
like
when
it
came
to
trying
to
bring
the
group
together.
It
was
mostly
the
champion
trying
to
drum
up
discussion
and
interest
and.
A
B
C
Developer
level,
yeah,
if
you,
if
you
just
let
these
things,
be
driven
by
ics
at
companies,
I
think
you
miss
out
on
a
huge,
huge
opportunity
to
get
you
know
higher
level
engagement
from
those
organizations
right,
I
know
that's
a
topic
that
has
come
up
at
netflix
for
us
is
like
hey:
what
is
the
organization?
We
have
a
bunch
of
people
who
are
involved
in
the
community,
but
what
does
like
the
organization
level?
Engagement,
look
like
and
that's
definitely
been
a
big
question.
C
I
think
if
we
could
answer
that,
that
would
lead
to
a
possible
future
where
we
have
a
really
clean
story
for
those
developer,
application
developers
or
ics
to
go
to
their
organization
at
a
higher
level
and
say
here,
look
node
has
said
you
are
a
constituency,
we
care
about
here's,
what
they
are
doing
to
help
support
you.
What
can
we
do
to
support
them?
And
if
that
story
is
more
clear.
D
A
Yeah-
and
I
think
so
I
think
you're
right-
that's
a
bit
of
a
me
that
is
a
big
gap
there,
so
openjs
foundation
members
like
I'm
just
thinking
what
we
could
make
like
what
what's
going
to
be
in
the
pr
to
fix
that
problem.
A
It
would
be
adding
something,
I'm
just
pasting
in
the
chat,
something
like
this
enterprises
with
no
just
deployments
that
should
include
opengs
foundation
members,
because
that's
certainly
a
constituency
we've
talked
about
going
back
to
and
we
can
right
because
they're
part
of
the
foundation
we
have
contact.
So
that's
that's
a
starting
point.
B
Yeah,
so
I
look
at
that
and
the
way
I've
figured
this
out
that
there's
that
gap
is
just
because,
when
I'm
considering
how
we
wait
it's
similar
to
like
when
we
were
talking
about
the
values
like
how
do
we
weight
our
values
against
each
other?
When
I
look
at
the
contest
constituency
list
that
you
provided,
I
was
like.
Oh,
there
seems
to
be
a
gap
here,
because
would
we
not
wait
an
organization
that
is
supporting,
let's
say
a
whole
bunch
of
node
projects
that
will
have
a
harder?
B
A
Yeah,
I
know
definitely
so
this.
Does
this
sound,
like
you
know
the
enterprises
with
no
just
deployments,
opengs
foundation,
members,
what
let's
work
that
into
something
which
fills
that
in
and
this
one
wasn't
ordered,
but
it's
interesting
to
think
about,
should
that
be
ordered
as
well.
That
list
of
consistent.
B
Yeah
I'm
a
bit
concerned
like
like
we
don't
want
to
like,
and
I
don't
think
I
like
I'm
the
right
person
for
sure
or
like
like
to
figure
out
who
we
care
about
more
or
who
has
like
a
larger
voice
like,
but
right
now
it
just
sounds
like
the
only
way
we've
been
getting
feedback
and
like
we've
taken
that
feedback
and.
D
B
Said
it's
completely,
even
that's
what
is
like
this
seems
like
on
the
individual
level
versus
like
the
organization
level,
especially
potentially
an
organization
supports
the
ecosystem
right
so
like
like
yeah.
The
cloud
providers
like
like
the
ibm's
and
the
microsoft's
and
the
googles
and
the
amazons
right
like
they
potentially
that
organization
like
has,
wants
and
needs
that
and
is
a
constituent
of
the
project
that,
like
we
need
to
our
stakeholders.
C
Oh
sorry,
I
think
that
we
need
to
have
a
very
clear
discussion
once
we
define
what
those
constituencies
are
on.
If
the
larger
group
of
contributors
thinks
there
should
be
an
order,
so
I'm
worried
that
if
we
say
we
think
there
should
be
an
order,
then
we're
going
to
have
to
pay.
A
A
It's
worthwhile
trying
to
order
those
at
this
point
like
that.
I
would
just
say
I
was
just
saying:
that's
an
interesting
thought.
Hadn't
come
to
my
mind.
My
personal
feeling
is
like
we're
aware,
there's
a
lot
of
other
things
to
focus
on
before.
That
would
make
any
sense
or
value,
and
it
probably
like
personally,
I
my
top
my
mind,
is
it
may
never
make
sense
so.
D
B
A
B
C
Might
be
profit
profit-seeking
organization
which
takes
and
never
gives,
is
probably
different
than
individual,
which
takes
and
never
gives
who's
making
a
profit,
though
off
the
open
source
as
well.
Yeah
there's
a
fine.
B
B
000
people
respond,
individuals
respond
to
a
poll
and
there
you
know
if,
if
we
were
waiting,
you
know
8,
000
or
90
of
them,
essentially
don't
contribute
back
to.
You
know
some
of
these
discussions
and
like
etc,
but
respond
and
say
that
they
think
something's
important
and
then
we
have
some
sort
of
like
competing
org.
A
I
think
it's
more
that
what
do
we
think
is
important
to
us
like
and-
and
I
I
think,
your
point
of
it's
not
it's
not
strictly
those
who
come
and
participate
in
the
project
like
it.
If
we
have
some
companies
who
have
massive
deployments
and
if
they,
if
they
don't
have
time
or
interest
in
participating
back,
there's
still
probably
value
to
us
to
understand
what
they're
doing
right.
A
So
you
know
it's
it's
I
I
wouldn't
personally
set
a
bar
that
says
you
have
to
meet.
You
know
you
know
you
have
to
be
here.
As
with
everything
you
know,
I
think
people
who
are
contributing
the
voice
will
be
more
strongly
heard
and
all
these
things
again
like
we
said
we
shouldn't
really
rate
them,
because
I
don't
think
it's
going
to
be
like
well
900,
individual
responses
on
a
survey
overrides
one
business
saying
x
right,
it's
more.
B
A
All
that
information
to
make
our
decision
and
weighting
those
is
never
going
to
be
like
plug
it
into
the
formula
it's
going
to
be.
Okay
from
all
the
information
we've
got,
let's
make
a
people
decision
right
because
that's
what
people
are
better
at
than
you
know,
just
a
formula.
That's
going
to
tell
us.
No
formula
is
going
to
tell
us
what
we
need
to
do
right.
A
B
C
B
You
know,
like
you
know,
if
netflix
or
10
years
ago,
we
we
decided
decided
to
use
a
different
platform
like
we
would
have
missed
out
on
having
a
an
enterprise
person
like
like
team
and
organization
at
the
table
right,
so
I
almost
feel
like
it's
more
like.
We
should
be
more
focused
on
the
startups
than
on
large
organizations
today.
If
we're
talking
about
the
next
10
years,.
A
A
You
know
what
what
makes
the
organization
different
versus
versus
a
bunch
of
individual
contributors,
which
is
what
we
were
talking
about
before
and
and
what's
what's
the
like?
How
do
we
get
to
them
differently
and-
and
you
know,
as
a
consistency
just
trying
to
understand
like
what's
because
there's
some
sort
of
line
versus
you
know
one
person,
if
I
take
note
and
I'd,
deploy
it
myself
at
home
for
some
of
my
stuff.
C
A
Not
sure
it's
even
commercial
right
if
there
is
a
non-profit
with
a
significant
investment
in
node.js
as
an
organization
that
still
kind
of
falls
into
my,
like,
I
think
it's
the
it's
the
investment
part,
not
whether
you're
trying
to
to
make
money
or
what
you're
you
know
if
you're
investing
significant
resources
through
deployments
through,
even
by
contributing
to
the
project
that
that
seems
to
be
more,
you
know,
inclusive.
I.
D
C
Drop
nodejs
deployments
or
like
and
just
say,
organizations
which
use
node.js,
because
even
that,
like
maybe
they're
using
it
for
tooling
and
they're,
you
know
not
like
they're
a
front-end
shop
built
on
top
of
a
sas,
so
they
don't
really
deploy
servers.
They
just
run
front
ends,
and
it's
all
no
jess
tooling,
like
that
to
me
is
the
same.
So
I
I
think
the
more
we've
dug
in
the
more
I
feel
like
going
specific
on
this
is
actually
to
our
detriment.
A
A
B
D
A
Okay,
yeah,
I
was
just
you
know.
I
was
wondering
if
there's
some
sort
of
we
we
could.
That
could
include
every
business
today
right
so
there's,
but
whether
we
need
to
say
that
or
not
you
know
in
the
significant
part
or
not
really
doesn't
matter
it's
it's,
because
we're
only
gonna,
we
haven't
had
the
challenge
of
too
much
feedback,
so
I
think
you're
right
that
it's
better
to
err
on
the
side
of
trying
to
encourage
people
versus
draw
a
line
that
excludes
people
so
anything
more
like
we,
you
know
open.js
foundation.
B
Startups
that
are,
you
know,
betting
they're,
they're
yeah
that
are
making
the
bet
on
node.js
for
the
next
10
years,
like
like.
A
B
A
E
Yeah
would,
in
terms
of
organizations,
maybe
just
like
also
mentioned
just
completely
open
source
for
words
out
there,
depending
on.
A
B
That,
like
they
have
representation
that,
like
their
own
tsc,
that
might
come
and
want
certain
things
right
like
that.
We
would
care
about.
C
B
C
Thing
we
might
be
able
to
do
to
get
out
of
having
to
enumerate
every
single
one
is,
is
structure
the
way
we
list
constituencies
and
say
here's
a
high
level
heading
and
then
just
say
examples
and
then
so
we
treat
these
as
just
examples
and
say:
they're
not
limited
to
they're
just
fit
you're.
You
know
where,
where
you
fit
closest
in
this.
B
A
B
Well,
you
could
just
say
startups
or
startups
enterprises,
foundations.
Governments,
like
you
just
say
those
words
like
in
in
brackets,
even
like.
I
don't
think
you
need
yeah.
A
A
D
B
A
B
A
E
Yeah,
it's
almost
like
no
profits
because
I
just
mean
like
a
larger
organization,
for
let's
say
a
library
or
a
project
or
whatever
are
the
technical
aspect
right
might
include
also
people
from
that
community
that
are
not
necessarily
the
library
authors
right.
That's
a
very
narrow
scope
there
like
so,
I
think,
just
having
the
entire
different
organization
as
a.
E
Yeah,
I
think
with
that
is
fine,
yeah,
just
adding
non-profits
there.
It's
it's
probably
good
enough.
A
A
Well,
like
you
know,
there's
library,
package
authors
is
basically
a
subset
of
developers.
There
are
people
who
are
now
packaging
it
for,
for
you
know
something
else
that
then
people
will
use,
but
people
also
will
write
applications
which
bring
together
so-
and
I
guess
maybe
it's
blurry
like
does
a
library
package
include
like
a
standalone
application.
A
C
D
E
A
C
World
verdaccio,
it's
an
application,
it's
bundled
as
a
library
published
npm,
but
it's
an
application.
I
don't
think
they
they.
I
think
they
have
the
same
needs.
The
same
you
know
wants
as
both
application
developers
and
module
authors
and
I
think
those
by
having
those
two
separately.
I
think
we
cover.
E
A
A
Yeah,
okay,
so
that's
we've
mostly
focused
on
adding
that
in
that
sounds
like
a
good.
Are
we
happy
with
that
as
the
addition.
A
D
A
A
Okay,
okay,
so
it
sounds
like
so
you
know
it
sounds
like
then.
The
next
thing
we
want
to
focus
on
is
figuring
out.
What
we
think
each
of
the
constituencies
needs.
A
Is
that,
like
that,
that.
B
Seems
like
a
reasonable
suggestion,
that's
kind
of
where
I
was
going
yeah
like
and
and
because
again,
like
I'm
trying
to
get
us
to
the
point
where
we
have
a
good
understanding
or
like
the
the
peop
like
we
can
go
to
each
each
constituent
and
say
like.
Is
this
actually
like
here's
our
assumptions
of
things
you
really.
D
B
This
accurate
and
then
you
can
try
to
ensure
that
you're
getting
feedback
from
like
the
right
people
from
the
right
channels.
Right
we
can
map
up
their
wants
and
needs
against
what
we're
actually
planning
and
prioritizing
in
the
next
10
years.
I
think
that's
really
that's
what
we
want
so
yeah
like
next
step,
I
think,
is
to
outline
you
know
what
what
does
this
persona
want
and
need
first
verse
this
and
then
you
know,
then
we
know
when
we're
making
a
decision
who
were
who
that's
tailored
to
like
who,
when
we
choose.
A
A
Okay,
yeah,
I
think
that's
that's
good
as
they
like
to
yeah.
It
makes
sense
to
me
as
a
way
to
try-
and
you
know,
as
opposed
to
just
throwing
out
technology
and
trying
to
say
hey.
We
think
this
is
important
to
have
a
way
we
can
trace
it
back
to
the
constituencies
to
say
why
and
who
cares
and
and
so
forth.
C
A
I
was
thinking
was
like
we're
out
of
time
this
meeting,
but
next
meeting
doing
one
of
the
getting
darcy
to
set
up
the
board
like
he
did
when
we
were
working
on
the
values
and-
and
I
know
we
won't
get
it
right
because
we're
a
small
subset
but
trying
to
have
something
tangible
to
start
with
like
blank.
We
can't
just
go
out
to
the
groups
with
blank
space.
I
think
we
can
try
and
fill
in
the
space
with
what
we
think
is
is
right
and
then
take
that
to
one
of
the
groups.
A
B
Yep
yeah,
I
can
totally
do
that
if
you
can
add
that
as
an
action
item
for
me,
so
I
know
to
prep
it
for
her
next.
A
On
what
each
constituency
needs
darcy,
I
says
it
like
this
action
darcy
to
set
up
board,
I
think
yeah
board,
which
would
be
so
basically
what
would
those
columns
be?
Let's
talk
about
that
like
it's
going
to
be
the
constituency.
E
E
B
B
A
B
F
Because
something
is
not
in
node
are
not
used
by
a
company
or
exceptionally
by
a
small
company
or
smart
subset,
but
let's
say
at
least
currently,
let's
say
an
api
and
stuff
like
that.
I
don't
think
it's
really
used
by
a
lot
of
companies
which
are
using
node.js
to
deploy
some
kind
of
serverless
or
stuff
like
that
or
anything
or
even
a
rest
api.
So
maybe
they
don't
it's
not
they
don't
want,
but
they
don't
really
need
or
they
don't
use
this
kind
of
functionality
or
stuff.
A
A
C
A
D
A
Yeah,
no,
no,
I
think
that's
good,
so
I'm
happy
with
that.
We
are
pretty
much
at
time.
So
I
think
that's
our
next
step.
We
can
open
and
we
can
open
an
issue
when
I
do
the
minutes.
I
can
open
an
issue
to
start
to
say
this.
What
our
next
focal
thing
is,
so
it
shows
up
on
the
agenda
and
we
can
go
from
there.