►
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
Yep
all
right
right,
all
right,
we're
rolling,
excellent
I'll
pretend
like
we're,
live
streaming
and
say
thanks
everyone
for
joining
another
episode
of
the
node.js
website.
Redesigned
strategic
initiative
meeting
today
is
the
19th
of
may
yeah
thanks
everybody
for
joining.
We
have
a
short
agenda.
A
I
don't
know
if
anybody
is
good
at
doing
meeting
notes,
but
I
will
paste
the
doc
in
here
and
we
can
kind
of
just
maybe
update.
Some
of
these
details
should
have
done
this
before.
B
That
would
be
me,
I
guess
I
have
a
kinesis
advantage
too
nice.
So
it's
a
ortholinear
keyboard.
I
guess.
A
Sounds
great
nice
cool,
I'm
just
updating
some
of
the
information
here
at
the
top
cool
and
then
so
we
have
three
items
on
our
agenda
which
we
can
crank
through.
Maybe
then
we'll
look
at
the
couple
of
issues
that
till
had
popped
into
the
chat
and
then
maybe
we
can
just
do
a
little
bit
of
kind
of
project
management
work
as
it
were.
A
A
I
guess
I
have
one
thing
I'll
share
something
of
an
announcement
tyranny
and
I
are
the
two
members
of
the
social
team
on
the
no
jazz
social
team
and
we
were
looking
at
the
calendar
which
isn't
really
social
related
but
we're
gonna.
A
We
wanted
to
start
doing
we're
doing
awesome,
automated
tweets
and
we
want
to
do
like
a
weekly
tweet
like
here's,
the
week's
calendar,
if
you
know
for
your
convenience
or
if
you
want
to
get
involved,
here's
multiple
ways
to
get
involved
and
we
were
kvetching
on
the
fact
that
the
calendar
is
by
default
in
pacific
time
zone
and
I'm
in
eastern.
A
So
I
always
have
to
remember
that
and
then
do
the
kind
of
math,
and
so
we
thought
it
would
be
less
u.s,
centric
and
perhaps
easier
for
the
world
to
consume
this
calendar
if
it
was
gmt
greenwich
meantime,
so
we
switched
the
calendar
to
that.
A
So,
if
you're
used
to
looking
at
the
calendar
and
and
grogging
it
through
whatever
filter,
you
know,
if
you're
a
pacific
or
what
have
you
just
know
that
it
has
changed
and
the
the
times
are
gonna
look
different
to
you
and
you'll
have
to
do
your
switch.
Your
mental
gymnastics
around
that
so.
A
Yeah
yeah
and
for
folks
who
just
click
the
add
to
my
google
calendar
button
and
have
it
integrated
in
their
own
calendar,
then
all
that
works
out,
and
it
doesn't
matter,
but
if
you're
looking
at
the
embedded
calendar,
which
is
nodejs.org
calendar,
it
is
now
in
greenwich
that
just
happened
like
20
minutes
ago.
A
So
I
will
add
that
here
in
the
notes
here,
nodejs.org
calendar
is
now
in
gmt
great.
So,
let's
see
jumping
into
the
agenda.
The
first
item
here
is
issue
1193.
A
B
B
C
Or
you
know
just
this
when
you
look
at
this
abstractly,
you
know
like
what
I'm
seeing
is
just
like
a
poor,
responsive
design
layout.
So
it's
kind
of
like
you
know
what
happens
when
the
view
shrinks
to
the
mobile
resolution.
You
know
so
like
if,
if
you're
looking
at
this
like
do
you
need
to
drop
all
those
icons
you
know
for,
do
you
need
to
drop
like
the?
C
What
is
it
the
dark
mode
and
the
github
icon
or
whatever
down
below
you
know
when
it
gets
to
that
resolution
or
you
know
and
or
hamburger
menu?
Is
you
know
fairly
common
for
this
sort
of
thing?
I
think
last
time
we
talked
about
having
you
know
we're,
like,
I
think
joe
said,
you
know,
because
my
mind
initially
goes
to
like
well,
we
could
just
get
a
designer
friend
to
like
look
at
this
and
say
hey.
C
This
would
be
good,
you
know
like
do
it
this
way
or
whatever,
but,
but
I
think
joe
you
mentioned
like,
we
should
probably
just
implement
something
and
move
forward.
A
Yeah
I
mean
my
my
guiding
principle
for
this
sort
of
work.
Is
you
use
the
designs
and
compare
it
to
and
use
the
designs
from
figma
and
the
current
website
and
figure
out?
You
know
what
makes
sense
of
those
two
but
not
diverge,
much
from
them
if
at
all
possible,
and
so
let
me
actually
look
up
on
my
phone
really
quickly.
What
does
the
nodejust.org
website
do
or
hello
becky.
A
You
aren't
here
ben,
but
becky
is
an
ibmer
who
is
interested
in
contributing,
so
I
invited
her
today
so
yeah.
Thank
you
for
joining
so
on
the
the
nodejs.org
website.
They
do
this
kind
of
thing,
which
is
pretty
goofy,
but
not
terrible.
You
know
when
it
works.
Oh.
D
A
Doesn't
it
doesn't
it's
not
sticky
and
I'm
gonna
just
share
my
screen
just
because
why
not
so
if
I
look
at
this,
is
these
are
the
figma
designs
here,
yep
shouldn't
have
my
password
manager.
C
Yeah,
I'm
glad
we're
recording
this
to
your
computer,
because
gonna
have
to
edit
that
out
later
I'm
a
real
professional.
A
So
I
don't
think
that
there
are
even
mobile
designs
looking
at
this
yeah.
No,
can
you
zoom
in
on
that
real,
quick,
again
yeah?
I
just
want
to
double
check,
but
if
we
do
look
at
this,
like
we're
already
veering
off
from
these
designs,
there
isn't
a
search.
You
know
this.
Let
me
just
go
to
nodejs.
C
What
was
what
was
the
design
for
the
the
search,
and
is
that,
like
just
a
feature
that
hasn't
been
implemented
yet
yeah.
B
It's
just
we
just
haven't
got
to.
I
I
tried
implementing
it
with
algolia
quite
a
while
ago,
and
our
json
blob
of
stuff
from
gatsby
is
too
big
for
the
free
free
tier,
oh
gotcha
gotcha.
So
I
abandoned
it.
Okay,.
A
Well,
we'll
look
at
that
later
because
I
don't
think
this
is.
Let's
just
take
a
look
as
we
do.
You
know
we
don't
have
search
on
here
either
so.
C
Can
I
can
I
make
a
suggestion
for
the
mobile,
just
like
a
quick,
just
a
shout
out
feel
free
to
like
it
or
hate
it
for
the
mobile.
I
feel
like
if
the
nav
links
dropped
below
on
that
resolution
on
mobile
resolution
and
the
and
there
were
the
hint
like
the
hamburger
and
the
the
moon
and
the
in
the
github
icon
above
that
that
would
probably
do
it.
You
know,
because
then
it
wouldn't
we
wouldn't
have
that
extra
space.
A
Yeah
so
essentially-
and
I
don't
know
if
I
can
get
this
to
work
here
properly
as
we
might
expect-
so-
this
is
an
ipad
if
I
just
do
some
sort
of
iphone
x
right.
So
we
we
are
kind
of
off
here
so
you're
saying
just
all
these
text
links
should.
C
Drop
yeah
so
get
rid
of
the
node.js
logo
in
the
top
right
left
corner
because
that's
taking
up
real
estate.
So
if
you
just
get
rid
of
that
node.js
logo,
and
then
you
keep
the
text
links
and
then
the
icons
on
the
the
right
of
those
text
links
they
go
top
so
they're
at
the
top
text.
Links
are
below
and
if
we
want
to
put
a
hamburger
in,
it
could
be
hamburger.
Moon,
github
logo
on
the
top.
A
I
that's
not
bad,
let
me
throw
out
another
idea
and
I'm
trying
to
pull
this
up
on
my
phone
real
quickly,
sure
so
interesting.
So
actually
on
my
phone,
it's
working
properly.
A
Oh
yeah,
although
no
learn
doc's
download,
is
not
showing
up,
it
seems
like
you're
missing
some
links.
B
Yeah,
so
actually,
last
night,
I
think
it
was
I
merged
in
a
pr
where
we
hide
the
download
link
on
mobile
gotcha.
Okay,
because
it
doesn't
make
sense
to
download
a
mobile
download
anything
on
a
mobile
device.
B
C
Then
honestly,
this
is,
I
mean
as
long
as
we
have
the
right
links
and
we
don't
lose
anything.
That
is
I
mean
these.
You
know
you
try
to
make
this
contextual
to
mobile,
which
is
great
so
as
long
as
we're
not
losing
anything
that
is,
you
know
right
in
this
context.
You
know
like
just
that.
I
mean
that
looks
good.
You
know
it
looks
fine
to
me.
A
Yeah,
what
I'm
trying
to
do
and
what
I
do
in
some
of
these
instances
as
I
try
to
put
my
miles
and
tierney
hat
on
or
anyone
else,
that's
just
going
to
come
at
this,
and
they
might
complain
like
that.
It's
just
it's
a
little
bit
odd
to
say
I
get
why
we
would
take
it
out,
but
actually,
I
think
like
going
to
the
download
page
and
seeing
like
if
I
click
on
this,
does
this
work
yeah.
B
Because
there
is
more
to
the
downloads
page
than
the
buttons,
so
you
can
see.
A
Yeah,
so
I
think
that
there
is
a
lot
of
good
information
here
sure
so
what
I
would
suggest
kind
of
riffing
a
little
bit
on
what
you
were
saying,
oben.
What
I
would
suggest
is
leave
the
note
up
in
the
top
left
leave
these
two
icons
in.
D
A
C
Html
and
the
markup,
I
guess
like
all
like
all
I'm
thinking
about,
is
like
we're
talking
about
visual
design
too.
So
like
what
looks
pleasing
and
we
just
we
would
just
have
to
like
I
mean
it-
it's
it's
kind
of
trivial
to
try
both
and
see
what
they
look
like.
You
know
to
try
like
something
where
here,
I'm
just
gonna
draw
something
real,
quick,
so
like
node
and
then
do
we
are
we
talking
about
doing
a
hamburger
menu.
A
Get
too
creative
you
know
in
terms
of
taking
over
these
so
for
for
till
and
becky
this
effort
has
been
going
on
for
years.
A
A
But
it's
been
a
long
time
and
I
think
that
we're
actually
kind
of
close-
and
I
would
love
to
see
it,
get
over
the
finish
line
and
then
we
can
add
features
like
well.
Maybe
this
would
be
better
as
a
hamburger
menu
or
maybe
you
know
there
are
lots
of
things
that
we've
kind
of
discussed
that
we
you
know
could
be
like
features
that
we
might
want
to
add
like
an
embedded
calendar
or
you
know
lots
of
other
things,
but
I
want
to
get
like
the
mvp
out
the
door.
C
Can
I
I
just
want
to
show
something
real,
quick,
I'll,
stop,
sharing.
A
C
C
Okay,
so
so
like
these
are
kind
of
the
two
things
we're
talking
about,
and
I
I
think,
if
it's
squared
off
in
the
way
that
you
were
talking
about
joe
with
the
you
know,
sort
of
filled
out
like
that,
I
think
that'd
be
fine
like
this
one.
I
think
that's
what
you're
talking
about
and
I
think
that'll
probably
probably
be
best
as
I
look
at
it
visually.
So
I
think
that's
a
good
idea.
A
I
don't
know
about
how
it's
implemented
and
how
you
know
you're
kind
of
pulling
that
out
of
the
flow
of
the
document,
so
that
might
need
to
be
tweaked.
I'm
not
sure.
C
But
I
mean
like
essentially
what
you
know
just
looking
at
this
visually:
you
have
like
a
nav
component.
Probably
I
mean
I
haven't
looked
at
it.
So
ben
would
know
right
but
like
to
me,
it
just
looks
like
I've
got
the
note
object,
which
is
always
going
to
be
there.
I've
got
like
a
nav
component,
you
know
with
the
with
the
links
and
stuff,
and
then
I
have
another
component,
which
is
like
my
my
other
links.
C
My
you
know
my
dark
mode,
light
mode
and
whatever
so
I
to
me,
it
looks
like
a
simple
layout
problem
is,
would
that
be
right?
Ben,
like
is,
it
is
yeah.
B
Yeah
you're
right,
let's
say
ul
list:
oh
yeah
joe,
has
the
elements
open
great
there.
It
is
yep.
C
So
pretty
much
after
that,
it's
just
like,
however,
you
want
to
display
them.
Usually
it's
like
flex
or
something
flexbox
or
whatever.
A
Yeah
that
would
be
that'll
be
good.
Does
someone
want
to
kind
of
write
that
up
in
that
issue
like
what
we're
talking
about.
B
No,
I
can
write
it
if
you
want,
but
I.
D
B
Was
going
to
say,
did
you
want
me
to
revert
the
download
link
and
bring
it
back.
B
A
E
Yeah,
I
think,
instead
of
rewriting
the
committed
change,
can
we
include
that
in
the
in
the
new
ticket
we
are
going
to
do.
E
A
I
think
it's
cleaner
to
just
have
ben
revert
what
he
did
and
then
move
forward.
Personally,
okay,
all
right
cool
and
then
manisha's
is
said
that
they're
working
on
it.
So
we
can
ping
them.
I
think
they're
in
the
slack
and
let
them
know
this
direction.
A
Cool
all
right,
moving.
A
On
see
so
this
actually
is
on
my
radar
miles
made
me
admin
and
I
can
make
this
change.
I
was
gonna
make
it
last
week,
but
I
didn't
so.
I
will
maybe
make
it
this
week
but
be
aware.
A
A
And
then
this
community
page
is
on
the
agenda
as
well.
Oh
nice,
it's
in
a
project
as
well,
so
ben.
Do
you
have
any
update
on
on
this?
This
issue
is
on
the
agenda
and
there's
a
bunch
of
stuff
here,
but
if
you
want
to,
let's
even
update
us
all.
B
So
the
things
that
still
need
to
be
worked
on
are
on
the
sidebar.
I
don't
think
anyone's
actively
working
on
it.
So
if
you
go
to
node.js.dev,
slash
community
I'll
write
that
in
the
in
the
chat,
so
you
guys
can
click
on
it.
B
B
So
that's
what
we
what
we
need
to
do
next
on
on
these
on
this
page,
okay,
which
link
it
is
all
the
links
on
the
left.
A
But
but
hang
on,
hang
on,
though,
all
the
links
on
the
left
are
from
the
design,
and
I
think
that
that
was
just
like
a
kind
of
pie
in
the
sky
sort
of.
Let
me
get
to
that
like.
If
we
had
all
these
things
or
you
know,
here's
all
the
things
you
might
see
in
a
community
page
right.
B
A
Don't
think
that
we
should
go
and
implement
all
these
pages.
I
think
that
we
should
align
this
with
what
we
think
the
community
section
should
be,
and
again
I'm
always
nervous
about
being
creative
here.
But
I
think
if
we
went
to
here-
and
we
went
to
about-
let's
see.
A
Because
I
feel
like
this
has
been
discussed
a
million
times
and
I
feel
like
decisions
were
made
on
what
should
be
on
this
community
page.
But
I
don't
know
what
those
decisions
are.
I
could
look
and
see
if
there
has.
If
it
you
know,
we
try
to
do
everything
in
issues
right
and
and
pull
requests.
C
Decisions,
I
think,
just
finding
a
history
if
there's
any
history
of
a
conversation
about
that
before
that'd
be
great.
Otherwise,
it
looks
like
we'll
need
to
kind
of
triage
and,
and
also
you
know,
filter
there
and
just
and
accordingly,
like
filter
this
down
to
what
is
essential.
C
Some
of
these
things
could
probably
be
don't
necessarily
need
to
be
pages
if
there
are
other,
if
they're,
just
linking
out
to
things
like
if
we
wanted
to
keep
something
like
community
publications,
we
probably
just
link
out
to
like
you
know,
wherever
the
node.js
blog
is
gonna
live
or
whatever
stuff
like
that.
A
I'm
sorry
I
was
trying
to
parse
this,
and
then
I
just
heard
you
talking
about
the
blog.
What
are
we
talking
about.
C
It's
nothing
super
vital.
I
was
just
saying
along
along
with
what
you
were
talking
about.
We
need
to
filter
down
pair
this
down
to
what
is
essential
to
be
in
here
and
not
create
extra
work
for
ourselves.
So,
like
you
know
we're
talking
about,
if
we
need
a
couple
of
pages
to
exist
here,
that's
great,
maybe
some
of
these.
If
we
want
some
of
these
things
like
community
publications
or
whatever,
for
now,
we
could
link
you
know
some.
C
Some
things
might
link
out
to
like
the
blog
or
you
know
whatever
it
is,
but
it
seems
like
there
is
some
parody.
You
know
as
long
as
there's
some
kind
of
parody
between
how
this
is
represented
in
nodejs.org
and
here
that'll
be
that'll,
be
good.
B
Was
when
divya
was
attempting
to
implement
it
and
then
ahmad
came
in
and
implemented
something
yeah.
B
Remember:
tyranny,
yeah
and
then
tierney
said:
why
are
we
following
the
design?
We
should
follow
the
visit
the
designs
and
we
were
like
okay,
we'll
follow
the
design.
A
Okay,
so
here's
what
I
propose
we
do
here.
This
is
this
and
we
were
just
looking
at
it
right
somewhere
in
here.
B
B
A
Okay,
so
what
I
think
we
should
do
here
and
I'm
glad
that
you
know
this
kind
of
exists
like
the
layout
is
the
design
for
the
layout
is
implemented
and
that's
great,
and
then
we
just
need
to
figure
out.
You
know.
A
I
think
that
we
should
make
an
issue
for
this
in
terms
of
what
should
be
on
the
community
page
and
what
should
be
in
the
sidebar
and
what
is
the
expected
interaction
in
the
sense
of
if
I
click
on
a
left,
sidebar
nav.
Does
it
take
me
to
a
new
page,
or
is
the
community
page,
one
giant
page
that
you
you
jump
down
to
that
section?
A
A
What's
cool
about
this
is
that
this
is
an
implementation
of.
So
what
I
think
would
be
great
is
if
we
took
this
implementation
right
and
basically
basically
copied
it
to
an
about
page
so
that
we
have
this
sort
of
thing
and
then
implement
because
on
the
current
website
here
let
me
close
this.
This
is
the
redesign
we
have
an
about
link
down
here.
A
I
think
that
when
we
click
on
that
it
should
implement
this
design,
but
with
this
content
yeah
with
this
same
interaction
where,
if
I
click
here,
it's
a
new
page,
I
click
here,
it's
a
new
page
right
and
then,
if
we
do
that,
we're
mimicking
the
current
website,
we're
also
setting
the
paradigm
for
how
community
page
would
be
implemented.
If
we
had
clear
guidance
on
the
implementation,
but
we're
taking
the
interaction
and
this
content
and
implementing
it
from
the
about
link
from
down
here.
Does
that
make.
B
Sense
yeah,
I
actually
have
a
pr
for
the
about
page
and
what
does
that.
B
Sort
of
I
copy
pasted
the
current
text
from
node.js.org
about
and
put
it
into
this
our
card
design.
So
there's
a
if
you
go
to
the
open
pr's
you
can,
you
can
see
it.
So
it's
it's.
Is
it
just
this
page?
It's
just
it's
just
this
text
right
here.
There
is
no
sidebar
at
the
moment.
A
Okay,
so
yeah,
if
you
and
it's
awesome,
that
you
have
an
open
pr,
do
you
with
your
experience
here?
Would
it
be
hard
to
convert
that
pr
to
have
the
sidebar?
No,
it
would
be
yeah
it'd,
be
okay,
straightforward,
cool
and
then
in
that
implementation,
like
this
link
would
be
the
same.
Where
it'd
be.
You
know
just
slash
about
as
if
you
had
clicked
on
the
about,
and
then
you
know
these
I
mean
hell.
If
you
want
to
just
copy
paste.
B
A
Cool,
so
if
you
want
to
get
that
set
up
for
the
about
page
and
then
do
a
pr
for
each
of
the
pages,
that
sounds
fine
with
me
or
if
you
want
to
just
throw
it
all
in
one
pr,
you
know
and
and
just
make
it
clear.
The
text
does
not
need
to
be
reviewed.
This
is
pulled
directly
from
the
website,
we're
just
kind
of
reviewing
the
layout
and
the
interaction.
B
Yeah
I
was
gonna
go
with
one
pr
per
page,
just
keep
to
keep
the
pr
small,
because
the
text
is
quite
a
bit
and
sure
that
sounds
good
to
me.
C
I
think
that
yeah
I
I'm
was
just
gonna
agree
with
you
on
that,
I
think
creating
creating
this
kind.
This
is
the
way
that
the
community
is
used
to
interfacing
with,
like
what
node.js
is
looking
at
this
page,
and
so
like
just
continuing
that
on
instead
of
trying
to
reinvent
the
wheel,
I
think
it's
probably
the
the
best
foot
forward
and
so
yeah.
I
really
I
like
your
approach
here,
joe.
A
E
Cool
so
I
think
then
I
can
also
help
you
on
this,
like
there
are
many
pages
here
right,
yep
yep,.
B
This
would
be,
I
should
create.
B
Issues
for
each
of
these
pages,
so
there
are
also
open
pr's
for
the
trademark
policy,
privacy
policy
and
there's
another
one
down
the
bottom.
I
forget
the
third
one:
oh
security,
yeah.
B
Yeah,
so
those
are
all
open,
pr's
that
could
use
I
either
I
I
gave
it
thumbs
up,
but
you
know
more
eyes
are
always
better.
So.
A
Well,
but
let
me
ask
you
what
the
implementation
is,
because
what
I
would
expect
in
taking
this
and
moving
it
to
you
know
this
format
or
whatever
that,
when
you
click
on
sorry
to
bounce
around
here,
when
you
click
on
privacy
policy,
for
example,
it
would
take
you
to
the
about.
B
What
I
mean
yeah,
so
if
you
I'll
find
the
pr
number
and
you
can
take
a
look,
if
you
like
sure.
B
So
it's
pr1298,
okay,
let's
see
so
I'll
paste
it
for
you.
B
And
then
the
the
staging
link,
these
things
are
awesome.
I
like
I
like
how
miles
set
this
up
for
us.
Yeah.
A
And
this
is
for
trademark,
okay
yeah.
So
if
I
look
into
here
and
so
for
folks
who
are
new
when
you
open
a
pr
like
this
there's
a
github
action
that
creates
a
preview,
and
so
you
can
click
in
here
and
see
what
what
this
this
looks
like.
So
this
was
sorry.
Was
this
trademark.
D
A
So
cool
the
I'm,
assuming
that
this
is
the
same
content,
I
would
see
here
yep,
but
oh,
that's
not
that's
the
wrong
one
trademark
beautiful!
So
that's
that
that's
that
great,
so
all
I
would
ask
is
that
this
be
moved
into
this
style
with
the
about
links
here.
A
So
essentially,
what
ends
up
happening
then
is
some
of
these
are
just
like
quick
links
into
that
section.
Yeah
and
later
on,
we
might
say:
well
that's
dumb!
Let's
take
these
things
out.
Let's
do
some
information
architecture
review
here.
That's
fine!
But
let's
just
get
this,
like,
I
said,
aligned
as
much
as
we
can
with
the
design
current
implementation
get
that
out
the
door
and
then
work
on
improvements.
A
Cool
wow
we
yeah
are
just.
I
think
this
is
good
we're.
This
is
progress,
so
that's
cool,
I
think,
ben
once
you
get
the
community
or
the
about
section
implemented
with
the
sidebar.
A
A
Okay,
essentially,
a
template
to
to
get
other
folks
going.
A
And
becky,
if
you
can,
I
encourage
you
to
join
the
the
slack
because
you
know
there
may
be
some
comments
in
there
like
I
could
imagine
ben
halverson,
saying:
hey,
here's,
the
community
or
sorry
the
about
page
with
the
left,
sidebar
implemented.
You
know,
jatil
might
jump
in
and
say
here's
the
next
page
and
then
it
would
be
clear
how
these
pr's
would
take
shape.
C
Hey
joe
really
quickly,
would
you
mind
navigating
back
to
the
view
of
node.js.dev,
really
quick,
which
one
oh
dot,
dev
just
yeah,
just
okay,
I'm
gonna
just
take
a.
Can.
I
take
a
little
picture
of
everybody
to
post
on
the
tweets
for
this
to
I
just
want
to
like
gain
some.
You
know
goodwill
here
for
node.js.
Can
everybody
give
me
a
thumbs
up
real,
quick
like
this
and
just
thumbs
up
yay,
all
right,
sweet?
Okay,
I'm
going
to
tweet
that.
E
Okay,
one
more
one
more
update
like
tomorrow
is
storage's
birthday,
so
we
are
expecting
some
cutes.
A
Ben
you
should
think
about
joining
oben.
You
should
think
about
joining
the
social
team
with
me
and
tierney.
C
Yeah,
absolutely,
I
feel
like
right
now,
just
you
know
navigating
trying
to
yeah
trying
to
like
wade
into
the
stream.
So
I'm
like
trying
to
be
careful,
but
you
know
yeah.
C
A
That
is
the
agenda,
so
that's
great,
I'm
glad
that
we
got
through
that
and
we
frankly
don't
have
a
lot
of
time
beyond
that.
So
I'm
not
sure
what
would
be
the
best
use
of
our
time.
A
Oh
I'm
I'm
going
to
jump
into
this
project
view
just
for
one
to
like
show
jatil
and
becky,
and
maybe
we
can
review
this
a
little
bit.
The
way
I
built
this
out
with
with
ben
halverson
is
we
looked
at
the
nodejs.dev
site
and
designs
and
we
looked
at
nodejs.org
and
just
tried
to
pinpoint
what
needs
to
be
done
with
a
quick
kind
of
overview
of?
What's
maybe
missing
and
so
like.
A
These
are
the
smaller
effort,
things
that
would
be
really
great
to
have
implemented-
and
I
think,
like
security
and
about
is,
is
what
we
were
just
talking
about.
So
it
would
be
great
to
have
jatil
and
becky
help
in
that
effort.
So
don't
don't
you
know,
folks,
don't
hog
all
the
pr's,
let's,
let's
spread,
spread
the
work
around.
So
that
would
be
great.
A
That's
awesome,
so,
interestingly,
we
don't
have
any
banners
up,
so
I
cannot
show
you
what
that
looks
like
that's.
A
A
A
Had
a
blm
one
up
there
too,
that
we
took
down
not
too
long.
A
So
you
know,
maybe
that's
not
even
a
big
deal
right
now
I
mean,
I
guess
I
guess
a
primary
one
would
be
fine
and
then
maybe
the
secondary
one
is
is
secondary.
Yeah.
I
was
wondering
about
that.
B
Like
where
would
where
would
it
sit
in
in
the
ui
of
node.js.dev?
Would
it
be
at
the
very
top
above
everything,
or
would
it
be
above
run,
javascript
everywhere.
A
That's
a
very
good
question
and
yeah:
that's
a
really
good
question.
I
don't
know,
that's
would
be
great
to
have
some
sort
of
design
committee
that
would
approve
these
sorts
of
things,
so
we
don't
have
to
think
about
it.
A
You
know
what,
since
there
isn't
a
design
for
this,
I'm
gonna
kind
of
put
it
over.
Here
too,
you
know
maybe
even
put
it
at
the
top,
because
we
don't
even
have
you
know
an
implementation
on
the
current
site
to
look
at
so
screw
it
we're
gonna,
put
it
over
there
for
now.
So
in
terms
of
the
download
section
and
I'm
just
kind
of
talking
out
loud
here
for
for
folks
who
are
involved
or
on
the
call.
A
A
B
A
Greatest
yeah
cool.
So
if
we
look
at
this-
and
we
look
at
downloads
here,
number
one
there's
a
different
design,
so
some
of
it
is
going
to
take
a
little
bit
of
mental
mapping,
but
there
are
changes
that
need
to
happen
here
that
would
align
with
this.
A
B
Yeah,
so
this
design,
the
current
design,
was
based
on
the
actual
designs
and
then
yeah.
There's
a
release
schedule
on
under
the
releases
page
that
you
found
yeah.
So
I
think
I
think,
in
the
design
when
there
was
a
designer
they
kind
of
combined
the
downloads
page
with
the
releases
page
it's
in
here
somewhere.
B
A
Over
on
the
right,
that
is
hilarious
yeah,
that
is
not
even
that's
the
don't
look
here.
Stuff
is
implemented
anyway.
What's
done
is
done,
we'll
figure
it
out
so
like,
for
example,
node.js
13?
This
should
not
be
here.
You
know
like
once
once
we
move
on
to
the
next
odd
release.
The
previous
odd
release
goes
away
fairly
quickly.
A
So,
for
example,
15
eol
is
in
like
a
week
or
two,
and
that's
because
you
know
version
16
was
released
for
folks
who
don't
know.
We
do
major
releases
on
even
numbers
and
development
on
odd
numbers
where,
where
version
17
will
be
coming
soon,
there's
there's
kind
of
some
overlap
and
some
gaps
as
as
this
works
out,
but
once
17
comes
out,
then
you
know
we
will.
We
will
focus
on
doing
development
there
and
then
you
back
port
everything
to
the
the
you
know:
maintenance.
A
I
don't
know
if
that
makes
sense
so
anyway,
my
point
being
version
13
isn't
mentioned
here
at
all,
and
so
it
should
be
removed
from
here.
So
I
think
it
would
be
good
to
go
through
this.
That
may
be
the
only
issue.
I'm
not
sure
I
guess
the
other
issue
is
that
this
is
built
from
a
json
file.
A
If
I'm
not
mistaken,
and
it
would
be
awesome
like
we're
engineers
right,
we
should
make
things
that
that
manage
themselves.
So
if
we
go
to
node.js
releases,
so
this
is
the
actual
repo
and
then
this
is
the
actual
json
file.
A
B
Right,
yeah,
the,
I
think,
the
reason
we
went
with
our
own
because
it,
the
downloads
page
on
dev,
is
also
coming
from
a
json
file,
but
it
has
an
additional
parameter
or
or
property
called
released
or
or
not
or
as
a
boolean,
and
we
were
using
that
that
as
a
flag
to
to
show
whether
the
hexagon
is
filled
in
or
not
yeah.
I
remember
talking
about
this
yeah.
We
remember
we
talked
about
this
previously,
so
I
can
create
it.
B
I'm
taking
writing
down
some
notes
now
in
the
in
our
notes
to
create
a
an
issue.
A
Right,
yeah-
and
I
think
I
think
what
we've
discussed
before
ben
halverson
is-
is
to
pull
in
this
json
and
then
you
know
munch
it
massage
it
to
whatever
way
we
want,
but
always
be
kind
of
pulling
in
from
the
source
of
truth
and
then
making
it
fit.
What
we
need
for
our
ui.
C
Is
this
exported
at
all
anywhere,
or
is
it
just
just
live
in
the
release
repository
like
raw
like
that,
like
because
what
I'm,
what
I'm
thinking
is
like
if
this
is
the
canonical
source
of
truth,
for
the
releases
then
like?
Wouldn't
it
be
advanta
advantageous?
If
there's
a
lot
of
projects
depending
on
it
to
export
it
via
like
a
module
or
something.
A
C
Yeah
or
like
or
more
that's,
that's
less
maintenance,
yeah,
yeah
yeah.
That
makes
sense.
A
A
We
may
need
to
think
about.
If
you
could
go
on
mute,
then
sorry
you're!
Oh
I'm!
Sorry!
That's
all
right!
I
work
with
a
lot
of
people
with
loud
keyboards,
so.
D
A
C
Yeah,
we
don't
want
to
serve
stealth
data
for
sure
yeah.
It's
like
thinking
through
what
the
thinking
through
what
the
what
requires
the
least
amount
of
maintenance,
as
well
as
just
like,
depending
on
something
from
another
repository
like
this.
So
I
think,
like
like
you're,
saying
yeah,
just
kind
of
like
fetching
it
you
know
for
now
is
probably
totally
fine
to
bring
it
in
that
way
and
then,
if
we
needed
to
yeah,
let's
just
keep
it
simple.
A
Even
instead
of
exposing
it
through
the
website
itself,
just
have
a
link
that
goes
direct
to
this
and
people
can
consume
it.
However,
yeah
exactly
before
we
wrap
up,
I
wanted
to
just
see
if
you
know
to
till
and
becky.
If
you
have
questions,
are
there
things
that
we
could
you
know,
while
we
only
have
a
few
minutes
left?
Are
there
anything
anything
come
to
mind?
That
would
be
helpful
to
you.
E
So
yeah,
so
we
decided
to
fetch
this
json,
which
we
are
currently
being
right.
E
E
B
Unmuted
yeah,
so
I
guess
I
would
use
fetch,
you
know
window.fetch
and
make
a
json
request.
Okay
and
then
parse
over.
F
A
Yeah
and
and
that's
a
great
that
brings
up
a
good
point
too.
You
know
when,
when
you
becky
or
or
anyone
watching
this
later
or
what
have
you,
if
you're
looking
at
this
repo
and
this
work
and
something
isn't
clear
to
you,
number
one
feel
free
to
ask
any
of
us,
but
also
help
us
make
it
better.
You
know,
because
I
think
a
lot
of
this
work
has
been
going
on
for
a
while
and
it
has
evolved.
A
I
think
even
like
you
know,
technology
choices
and
and
guides
and
instructions
and
docs
so
anywhere.
You
see
something
not
making
sense,
especially
if
you
are
like
this
doesn't
make
sense.
Oh,
I
figured
out
how
this
does
make
sense.
Please,
like
open
a
pr
to
update
the
documentation,
open,
a
pr
to
update
the
storybook
open.
A
pr
to
you
know,
explain
how
the
left
nav
bar
works
for
the
next
person
who
needs
to
implement
something
like
any
of
these.
Things
are
very,
very
welcome.
A
I
I
haven't
had
the
chance
to
really
dig
in
lately
to
see
how
the
documentation
aligns
with
the
actual
project
and
the
experience
and
the
the
development
of
it.
So
I'm
not
sure,
but
someone
with
fresh
eyes
is
always
the
best
way
to
kind
of
make
things
work
better
for
everyone
else
coming
along
and
those
are
usually
nice,
small,
easy
pr's
that
aren't
you
don't
have
to
worry
about
breaking
the
website
or
anything
so
cool.
G
Anything
else
before
we
kind
of
look
to
wrap
yeah.
I
pestered
two
issue
numbers
one,
one:
five,
three
and
one:
seven:
six.
Yes,
let's
take
a
look
at
that,
let's
see
so
this
is
the.
A
Issue
what
was
it
again?
What's
the
first
one,
one
one,
five
three
yeah,
I
probably
did
something
wrong
here,
so
issues.
G
There
we
go
so
the
blog.
I
think
these
issues
are
open.
A
These
are
sort
of
in
order
these
mvp
phases,
and
maybe
I
should
even
label
them.
You
know
phase.
One
is
this,
which
is
these
things
and
then,
like
the
blog,
is
sort
of
a
bigger
question
here.
A
A
A
A
Okay,
this
website
is
pretty
good,
it's
pretty
complete.
Yes,
we
have
big
things
like
the
blog.
We
have
big
things
like
localization
of
the
content
and
docs.
You
know
these
are
a
couple
of
big
things
that
we
need
to
work
out,
but
if
we
get
all
the
other
stuff
done,
I
I
feel
comfortable
going
to
the
larger
group
of
these
other
teams
and
saying:
okay,
look
things
are
looking
really
good.
We've
got
a
good
layout
and
everything's
working
well.
Now
we
need
to
handle
these
bigger
things
that
we
actually
need.
A
Perhaps
some
tsc
input
we
need
to
coordinate
with
the
docs
team.
We
need
to
coordinate
with
the
internationalization
team,
but
everything
else
is
in
place
and
and
I
would
feel
more
comfortable
bringing
people
into
our
you
know
we're
basically
cleaning
up
our
mess
before
people
come
over
to
visit
the
house.
You
know,
so
that's
that's
what
my
thinking
is
here.
E
Okay,
so
I
made
a
contribution
to
or
node.js
work
as
well
yeah
like
a
few
contribution,
few
documentation
change-
and
I
recently
I
touched
the
node.js
though
I
added
the
shell
command,
one
shall
command,
that's
it
so
so
going
forward.
I
will
stick
with
the
same
forum,
so
we
can.
A
Okay,
great
I
mean,
and,
and
I'm
I'm
you
know,
there's
a
an
issue
open.
I
don't
know
if
it's
an
admin
or
what
but
yeah
right
was
that
it
did.
I
catch
it
about
like
getting
the
two
teams
together.
This
isn't
private
right.
No,
okay,.
B
I
think
it
was
in
node.js.org
the
one
that
that
rich
trot
opened.
Okay,.
C
Speaking
of
that,
just
as
we're
ending
up
here
a
little
last
announcement
too
so
ben
halverson
not
this
week,
but
next
week
he's
going
to
jump
over
with
us
in
the
internationalization
working
group
and
kind
of
give
us
a
rundown,
a
rundown
he's
going
to
help
us
look
through.
You
know
the
node.js.org
in
the
context
of
of
integrating
internationalization
into
it
and
we'll
give
ben
context.
C
If
anybody
else
would
like
to
join
us
at
that
meeting,
so
not
this
friday,
but
the
friday
after
totally
welcome
to
love
to
have
you
there.
If
you
want
to
gain
context
for
either
or
both
sides,
I
think
it's
going
to
be
something
that's
a
stream
of
work.
You
know
to
get
that
integrated
into
into
node.js,
so
either
way
it
doesn't
have
to
be
seen
necessarily
as
a
as
like
a
hey.
You
know,
let's
get
this
done
first
and
then
do
that.
C
I
feel
like
just
there's
ongoing
work
and
there
always
will
be
ongoing
work
for
internationalization
and
getting
this
translated.
So
the
more
we
can
just
continue
to
sync
and
see
it
progress
into
being
a
reality
for
node.js.dev
yeah,
so
anyways
y'all
are
invited.
C
A
C
And
also
just
for
context,
too
we're
going
to
get
someone
from
nodejs.org
who
understands
you
know
how
the
document
api
documentation
is,
is
generated
and
built,
and
that
sort
of
thing.
So
we
want
to
get
context
on
like
a
rounded
perspective
of
how
you
know
international
the
internationalization
working
group.
Can
you
know
stream
to
get
into
both
of
those
streams,
making
sure
that
translations
are
going
out
and
available
because
that's
sort
of
the
topology
we
have
right
now,
which
is
nodejs.org
node.js
at
dev?
C
Those
are
our
two
are
two
targets,
but
we
yeah.
So
you
might
hear
more
about
that
too.
If
you,
if
you
want
to
join,
to
see
how
those
docs
are
generated
and
built
which
will
be
cool.
A
Yeah
definitely
keep
me
posted.
I
look
forward
to
hearing
more
about
all
those
efforts,
all
right
cool,
that's
we're
over
time
and
I've
got
somebody
else,
sending
me
messages
about
another
meeting,
so
I
gotta
drop,
but
I
appreciate
everybody
all
right.
You
too.