►
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
Great
welcome
everyone
thanks
for
joining
another
node.js
website.
Redesign
meeting
today
is
like
the
28th
of
july
and
our
meeting
issue
in
the
node.js
repo
is
1660..
A
There
is
a
pretty
short
agenda
here,
so
we
will
probably
have
a
short
meeting.
Oh
and
I
see
I
see,
the
first
issue
is
to
add
you
thomas,
or
do
you
go
by
lance?
What
do
you
prefer.
A
Okay,
cool-
the
first
issue
here
is
to
add
lance
to
the
team.
Oh,
this
is
a.
This
is
an
issue.
Let's
see.
A
Yeah,
I
I've
been
saying
rodeon,
but
I'm
not
sure.
So
let
me
let
me
I'm
surprised
that
I
feel
like
we
have
a
process
for
this,
and
if
we
don't
it
should
be
made
more
clear.
Anyone
says
please
read
contributing
guidelines.
Yeah
see
we
need.
A
We
need
something
that
makes
this
clear
because
I
mean
not
that
just
creating
an
issue
that
ben
did
and
nominating
you
is
a
bad
thing,
but
if
we
have
a
process
I'll
hear
it
here,
so
I
should
I'm
going
to
create
an
issue
to
make
clear
how
to
add
someone
to
the
team
actually.
C
A
The
link
for
that
process,
yeah,
is
it.
Let
me
see
where
what
I
saw.
I
saw
contributing
yeah
how
to
be
exactly
that's
exactly
what
I
was
looking
for.
Thank
you.
So
it's
it's
it's
I
think
nice
and
fine
to
especially
if
you're
nominating
someone
that's
great,
to
throw
up
an
issue,
but
we
should
to
actually
add
someone-
and
I
think
that
would
probably
be
the
best
way
rather
than
an
issue-
is
to
open
up
a
p,
a
pull
request.
A
I
can
create
that
yeah,
if
you
wouldn't
mind
linked
to
the
spot.
It's
pretty
basic
you're,
just
basically
adding
yourself
in
in
the
list.
Alphabetically,
and
you
know
folks
who
are
involved,
will
approve
it
and
then
within
72
hours,
without
any
objections
we
would
merge
that
in
and
then
add
you
to
the
team
and
and
so
on
and
so
forth.
A
A
So
that's
are
you
familiar
with,
like
the
closing
verbiage
in
in
pull
requests
and
stuff
lance,
the
closing
yeah?
So
if
you
open
up
a
pull
request
and
in
the
description
you
say-
closes
colon
oh
yeah,
yeah,
yeah,
yeah,
so
yeah.
If
you
would
do
that,
that
would
be
awesome
and
when
we
can
manage
that
that'll
be
perfect
cool
and
then
the
other
one
is
adding
rhodion,
which
I
hope,
I'm
saying
that
right
or
let
me
even
see
yeah
rhodium
is-
is
their
name
great.
A
I'm
gonna
merge
this
assuming
this
worked,
yep,
okay,
cool
so
squashing
and
merging
that
one
and
then
I
need
to
add
rhodion
to
the
team
as
well.
I
think,
if
I
remember
correctly,
looking
at
the
notes
here
requests
once
the
requirements
are
met
and
approved,
pull
requests
can
be
merged
and
a
member
of
the
node.js
community
committee
will
add
the
new
person
to
the
no
just
dev
team,
and
I
should
make
these
hot
links
so
much
to
do.
Let's
see.
A
A
A
A
A
Great,
so
I
opened
up
that
pr.
I
will
share
it
in
zoom,
since
we're
just
kind
of
hanging
out
here
feel
free
to
just
take
a
quick
peek
at
that
and
throw
a
thumb
on
there,
and
I
will
merge
that
after
I
think
72
hours
so
yeah,
that's
it
for
our
agenda
right.
I
mean
the
only
other
thing
that
I
think
is
worth
mentioning.
A
Is
I
don't
know
if
anyone's
looked
at
this
document
that
we
started,
I
think
I
don't
think
it
was
last
week
was
maybe
the
week,
the
last
meeting,
but
maybe
the
one
before
looking
to
document
kind
of
the
state
of
the
redesigned
work
with
an
out
with
a
with
the
the
thinking
being
that
we
will
start
to
bring
in
folks
from
other
teams
like
the
current
nodejs.org
team
and
the
documentation
team
and
the
internationalization
team,
and
basically
having
one
document
to
point
people
to
to
give
them
all
the
context
on
where
we
are
and
what
we
still
need
to
do
and
how
we
may
need
to
work
together
with
other
teams
within
the
node.js
org.
A
So
if
anybody
has
any,
oh
here
comes
ben.
If
anybody
has
any,
you
know
stuff
to
add
there,
please
do
so,
hey
which
ben
is.
This
is
halverson
yeah.
This
is
alvarez.
How
are
you,
how
are
you
ben
here?
We
are
good.
A
Yeah,
so
we
just
get
you
up
to
speed
ben.
We
were
talking
for
a
few
minutes
at
first
and
then
got
the
stream
going
and
basically
our
two
agenda
items
are
adding
people
to
the
team.
Lance
is
going
to
who's
on.
The
call
here
is
going
to
create
a
pr
to
add
them
to
themselves
to
the
readme.
D
A
Okay,
yeah,
I
was
in
sure,
actually
yeah
not
a
big
deal,
and
I
appreciate
you
recognizing
the
work
that
folks
are
doing
and
and
encouraging
them
to
be
officially
kind
of
recognized
on
the
team.
A
A
So
the
only
two
agenda
items
were
that
we
had
were
those
two
team
updates
and
I
was
just
sharing
with
lance
and
minish
the
hack
md
file
that
we
started
working
on
what
not
last
meeting,
maybe
so,
maybe
a
month
ago,
I'm
not
oh.
Actually,
we
meet
weekly
so.
D
Yeah,
like
two
weeks
ago,.
A
Yeah,
so
I've
been
too
busy
to
really
do
anything
at
all
lately.
So
I'm
not
sure
you
know
if
there
are
any
updates
or
anything
on
the
documentation
side.
I
know
tierney
had
posted
something
in
slack,
but
you
know.
D
Last
week
michael
dawson
joined
us
and
you
went
through
oh
yeah
and
it's
that's
actually
on
youtube.
So
if
you
want
to
watch
that
you
can
cool,
but
we
actually
when,
as
we
were
going
through
the
screen
or
through
the
meeting,
we
were
adding
notes
to
that
file.
A
Awesome,
I
will
look
at
that,
so,
oh
I
see
I
see
okay,
so
I
feel
like
this
document.
I
appreciate
that
that
the
feedback
is
in
this
document
or
at
least
probably.
A
Yeah
yeah,
if
it's
in
the
meeting
notes,
that's
great,
I
think
maybe
taking
action
items
or
at
least
issues
bug,
bug
reports,
whatever
feature
requests
out
of
this
would
be
a
good
next
step
yeah,
and
then
we
can
delete
this
section.
D
Yeah
my
note
core
comment
in
there
has
been
merged,
so
that
can
also
be
removed.
A
Oh
cool
trying
to
see
which
one
you're
talking
about
here
so
navigation,
deciding
on
which
link
to
keep
on
top
nav
bar
when
we
move
motorcycle
new
one,
so
that
yeah.
So
I
struggle
with
this
a
little
bit.
A
My
challenge
is
that
there
was
design
work
done
a
while
ago
and,
like
information
architecture
work
done
a
while
ago,
and
I
wasn't
there
and
I
don't
have
any
of
the
like
conversational
context
or
the
decisional.
You
know
the
the
reasons
why
decisions
were
made
and
this
was
the
design
we
got.
But
I'm
inclined
to.
A
A
My
inclination
is
to
not
re-litigate
those
sorts
of
things
right
now,
meaning
let's
get
the
design
implemented.
Let's
fill
the
gaps
between
the
design
and
the
current
implementation.
Let's
make
sure
current
feature
parity
happens
and
then
we
can
kind
of
go
back
and
look
at
top
navigation
and
sort
of
those
sorts
of
things.
Does
that
make
sense
yeah?
I
agree
I
mean
unless
it's
a
clear
like.
Oh,
this
was
an
oversight.
A
We
really
shouldn't
do
this
or
something
you
know,
then
that's
a
different
story,
but
I
don't
want
to
get
to
the
minutia
of
of
design
decisions
and
ia
decisions
at
least
not
right
now,
so
I'm
kind
of
browsing
the
notes.
A
A
Yeah,
the
the
general
questions
at
the
bottom
are
interesting
too,
but
also
are
kind
of
you
know
things
we
should
keep
around,
but-
and
I
mean
I
think
the
table
of
contents
is
a
good
question
like
that's,
maybe
not
something.
We
should
have
right
now
and
just
hide
it
for
now
and
then
leave
it
for
later.
Yeah,
wonderful,.
D
Is
the
table
of
contents
prop
an
optional
thing?
Can
we
like
turn
that,
on
and
off
by
page.
A
Yeah
that
wouldn't
be
bad
just
for
now
we
can
kind
of
make.
You
know,
that's
again,
a
decision
we
can
make
later
on
the
the
less
that
we
kind
of
add
to
it
and
and
give
people
more
things
to
kind
of
quibble
about,
probably
the
better
you
know
yeah,
I
don't
know
if
I've
ever
used.
The
word
quibble.
It's
a
good.
A
Word:
cool!
Well,
okay!
So
that's
interesting!
So
an
action
item
is
to
break
those
into
action
items
or
release
issues
and
such
that
would
be
great
any
any
other
things
that
we
want
to
talk
about,
ben
or
anyone.
I
actually
had
yeah
go
ahead.
C
A
Okay,
so
what
I'm
curious-
and
this
might
be
good
to
put
into
an
issue-
you
know
an
issue
titled,
you
know
move
to
netlify.
A
A
What
might
break
you
know
before
we
make
a
move
like
this
I'd
like
to
try
and
understand
it
fully,
but
I
don't
I
don't
have
the
context
or
I'll
I'll
show
it
to
you
actually.
D
C
Right
so
basically,
we
need
a
server
side
to
redirect
for
this
thing,
like
changing
from
old
slugs
to
a
new
one
and
metal
file.
Has
that
feature
yes
netlify?
Has
that
feature
you
just
have
to
write
this
underscore
redirects
file
and
it
will
work.
A
Okay,
interesting
yeah.
I
still
think
that
it
would
be
good
if
you
were
able
to
document
that
in
an
issue
and
we'd
have
miles
and
other
folks
chime
in.
I
don't
know
what
features
we're
getting
right
now
that
we
would
have
to
either
migrate
or
or
not
have
from
gcp
to
to
netlify,
but
that
would
be
an
issue
would
be
a
great
place
to
kind
of
flesh
that
out
and
and
understand.
A
A
Let
me
interrupt
you
one
moment:
manish
before
we
switch
gears,
did
I
hear
ben?
Did
you
have
a
comment
on
the
move
to
netlify
before
you
talk.
D
Yeah
yeah,
so
one
thing
that
we'll
end
up
giving
up
is
our
ability
to
create
staging
urls
like
as
we
are
today
in
that.
If
I
I
don't
know
they
have
the
ability
to
create
preview
links
that
was
kind
of
how
we
came
up
with
our
staging
thing
from
the
from
that
idea.
D
But
I
don't
know
if
it's
possible
for
a
for
person
or
somebody,
that's
not
a
member
or
a
contributor
to
to
generate
how
would
they
generate
a
staging
url
if
they're,
not
a
member
of
the
organization
or
or
a
contributor,
all
right
and
yeah.
So
that's
going
to
be
an
issue
this
right
right
now
we
have
staging.node.js.dev
and
then
whatever
the
pr
number
is
that
is
generated
and
those
files
are
generated
and
saved
into
a
google
cloud
bucket
for
each
year
that
we
generate
by
typing
in
slash
preview.
A
Yeah,
do
you
know
manish
if
that
is
a
something
we
can
do
with
netlify,
I'm
I'm
not.
I
don't
know.
C
I
think
a
preview
links
are
supported
on
netlife,
but
I
like
the
suggestion
that
I
was
going
to
make,
was
use
versailles
instead
of
metal.
D
Yeah
yeah,
all
these
static
side
generators
have
the
that
feature,
but
it's
under
your
assumption
that
you're
already
part
of
an
organization-
and
it
probably
uses
like
branches,
not
like
pr
numbers.
So
then
we
are
we're.
Gonna
have
to
come
up
with
like
some
kind
of
convention
on
pr
ranch
names.
D
There's
a
lot
of
questions.
I
have.
A
Yeah
about
this
also,
I
just
wonder,
are
we?
Are
we
going
from
something
that's
donated
to
something
that
we
would
need
to
pay
for
and
and
while
versailles
is
an
interesting
company
and
guillermo
is
great
and
everybody
you
know
whatever,
but
you
know
I
don't
know
if
we,
if
I
don't
know
if
we're
getting
something
for
free
from
them,
I
know
that
they
reached
out
to
us
recently.
A
That's
they
would
give
us
something
for
free
if
we
did
some
other
thing
for
them
and
we
decided
not
to,
and-
and
so
I
just
I
don't,
I
don't
want
to
relitigate
that
either
and
I
just
want
to
I'm
kind
of
mindful.
C
A
So
I
think
you
know
the
point
still
remains
we
should,
if
you
can,
if
you
can
document
an
issue
that
would
be
great,
we
can
talk
it
through
there.
We
might
need
to
kind
of
you
know
demo
or
or
try
this
out
somehow
before
we
actually
move
to
it.
If
we
decide
to
I,
I
would
love
to
like
see
it
working
before
we
before
we
approve
that
sort
of
a
change.
C
A
Cool
but
thank
you
manish.
I
appreciate
your
work
on
that
cool
all
right,
so
back
to
remark,
situation.
C
A
Okay
and
and
again
wha,
what's
the
reasoning
for
a
move,
the.
C
C
D
Yeah
yeah,
so
the
reason
for
the
change
is
right
now
we're
using
markdown,
we
use
mdx.
What
we're
trying
to
do
is
like
on
the
slash,
learn,
page
all
that's
markdown
files,
and
we
want
a
button
that
says
copy
that
will
copy
the
text
to
the
clipboard,
so
we
tried
using
a
gatsby
plugin
but
see
how
it
switches
to
has
that
little
checkbox.
D
We
wanted
something
to
indicate
and
the
plugin
that
we
I
tried,
doesn't
support
that
right
now.
So
this
is
an
alternative
switch
to
mdx.
So
with
mdx
we
would
have
javascript
components
in
a
markdown
file,
so
so
that
that
chart
that
minus
showed
could
then
be
dynamic
instead
of
a
static
file.
A
Okay
and
the
what
is
the
amount
of
effort?
Do
we
think
to
change
all
of
the
closing
tag
situations
like?
Is
that
also
going
to
be
a
problem
in,
for
example,
documentation,
and
is
that
that
was.
C
D
Yeah
well
in
the
core
docs.
I
think
it's
just
regular
markdown.
I
don't
think
they're
using
any
html
in
there
in
the
core
docs,
but
we
would
have
to
verify
that
I'm
not
100
on
that
yeah,
I'm
not
either
on
the
markdown
for
the
slash
learn
pages.
Those
are
definitely
all
marked
out
because
it
wouldn't
work
otherwise,
yeah.
A
Become
just
looking
at
a
recent
doc
file,
you
know.
One
question
I
have
is
are
html
comments
that
that
should
not
be
a
problem
right.
I
would.
A
Okay,
yeah
because
they
use
html
comments
for
some
kind
of
context
for
some
of
the
documentation.
You
know
like
when,
when
a
feature
was
added
essentially.
B
A
Okay:
okay,
that's
interesting.
A
You
know
those
are
the
only
thoughts
that
I
was
having
and
I'm
just
still
kind
of
scrolling
around
looking
to
see.
If
I
see
any
other
html,
which
I
don't
really
so
that's
good.
A
Okay,
yeah,
I
think
it's
interesting.
I
mean
I
I'm,
I
think,
we're
kind
of
really
at
a
point
where
we
do
need
to
start
bringing
in
other
teams
to
kind
of
verify
assumptions
and
things
like
that,
but
I
also
I'm
not
sure
we're
ready
to
bring
in
other
teams.
Yet
it's
it's
sort
of
this
like
little
gray
zone
that
we're
you
know
between
between
phases
here,
but
it
would
be
interesting
to
get
some
other
folks.
Looking
at
some
of
the
stuff.
A
But
otherwise
that
one
that
one
looks
good
to
me
I'll
I'll,
take
a
look
at
it
after
the
meeting
and
put
a
thumb
on
it.
D
All
right
cool,
so
I
I
mentioned
earlier
that
my
pr
to
for
node
core
to
support
markdown
is
merged.
So
that
means
we
can
start
adding
front
matter
that
we
can
use
to
the
those
dots.
But
before
we
do
that,
we
should
probably
figure
out
what
we
want
to
add
and
that
we
can
actually
use
yeah
creating
a
bunch
of
like.
A
Rewards
yeah
yeah.
What
let
me
ask
you
ben
first
of
all,
is
there
a
doc's
team?
Yeah?
That's
that's
unfortunate.
I
mean
it's.
It's.
D
A
If
we
should
have
a
powwow
before
we
start
making
any
you
know
front
matter,
changes
and
you
know
sit
down
with
rich
and
anyone
else.
Who's
focused
on
that.
I
I've
been
wondering
for
a
while.
If
we
should
be
if
we
should
have
a
docs
team-
and
I
know
that
that's
a
complaint
of
node.js
is
that
the
docs
really
aren't
that
user
friendly,
which
is
a
whole
nother
conversation.
D
One
thing
I
would
love
to
see
soon
is
a
search
feature.
D
Because
all
the
more
modern
doc
websites
of
just
about
any
site
has
a
built-in
search
functionality.
A
I
wonder
yeah,
I
think
a
docs
team
would
be
great,
and
maybe
now
so
I
I
feel
like
I
can
ask
michael
who
usually
has
some
historical
context,
michael
dawson,
what
if
there
was
one
or
what,
but
I
feel
like
we
should.
We
should
have
one-
and
you
know
at
the
very
least,
to
work
through
this
transition,
but
also
just
to
think
through
how
to
really
improve
node
docs.
A
I
don't
know
if
anybody
you
know
has
an.
D
A
Yeah
yeah,
I
struggle
because
I
I
you
know,
I
always
want
to
be
doing
things
and
helping
and
and
like
yeah.
We
should
do
this.
We
should
have
this
and
I'm
like
I
should.
I
should
help
make
a
doc's
team,
but
really
do
I
have
time
to
do
that.
A
Oh,
but
I
think
I
think
it
makes
sense,
particularly
right
now
in
terms
of
the
redesign
work
you
know.
At
the
very
least,
I
don't
want
to
say
a
temporary
docs
team,
but
something
to
really
kind
of
set
aside
some
time
to
really
work
through
docs
and
the
redesign
work
anyway.
I'm
kind
of
just
thinking
out
loud
at
this
point:
okay,.
D
The
site
yeah
yeah,
so
in
the
in
the
design
there
actually
is
a
search
box
in
the
top
right
corner.
D
Yeah
that's
one
way.
I
actually
had
a
kind
of
working
example
a
while
ago,
I
thought
so
sometime
last
year
and
the
problem
that
I
ran
into
is
since
I
had
a
free
tier,
our
json
is
huge
and
it
exceeded
the
free
tier.
So
I
wasn't
able
to
like.
D
The
open
source
project-
I
think
they
do
have
an
open
source
like
here,
but
I'm
not
like
a
representative
of
anything
I'm
just
an
individual.
So
I
can't
like
reach
out
myself
yeah.
A
All
right:
well,
let's,
let's
maybe
we
can
move
this
over
to
slack
in
terms
of
just
maybe
pinging,
rich
and
michael
and
seeing
what
may
have
happened
in
the
past,
and
you
know
if
there's
any
appetite
for
having
a
docs
team.
At
the
very
least
you
know
through
this
transitional
phase,
but
I
really
think
it
would
be
good
to
have
an
actual
team.
That's
that's
focused
on
improving
the
docs
and
and
making
them.
You
know
more
user-friendly
and
and
consumable.
D
So,
going
back
to
the
front
meter
like
without
like
talking
about
like
integrating
it
from
the
node
forward
side,
what
what
do
we
want?
Just
from
like
an
information
implementation
like,
I
think
we
would
want
the
title.
We
don't
want
a
slug,
probably
category.
A
Yeah,
that's
a
good
question,
like
I
think
some
of
the
stuff
in
the
current
docs
is
is
really
specific
to
sections
of
the
dock.
So,
like
we
can't
add,
like
you
know
when
that
feature
was
added
per
se,
yeah.
D
Yeah,
that's
another
question
so
right
now,
they're
doing
like
the
way
they
the
docs
are
generated
are
through
those
comments
so
like
when
things
were
added
so
like.
If
something
was
added
in
like
14x
there's
a
comment
like
it
was
added
here.
But
so
then,
if
you
go
to
like
version
six
or
something
or
previous,
that
the
generation
of
the
version
six
file
doesn't
display
the
newer
stuff.
A
C
D
A
Yeah
yeah
I
mean
I
I
I
would
assume
as
much
because
what
else
would
we
do?
You
know.
D
A
Yeah,
but
I
wonder
if
your
you
know,
your
company
has
their
app
on
node
10
and
you
don't
have
the
resources
to
migrate
or
what
have
you?
You
probably
want
to
look
at
the
node
10
docs.
You
know
what
I
mean
like
if
you
start
looking
at
14
you're
like
oh,
but
is
this
in
no
10?
It's
not
clear
to
me.
I
you
know,
I
think,
and
I
don't
know
what
other
platforms
do.
A
I'm
not
sure,
but
it
seems
like
this
is
something
that
even
if
it
was
an
idea
that
you
know
the
majority
might
go
along
with
I'm
sure
that
there
are
lots
of
people
who
would
be
like
no.
No,
no!
No!
No,
you
know
so
that's
like
one
of
the
first
things
I
think
we
would
need
to
solve
is
how
we
parse
these
documents
and
are
able
to
spit
them
out
into
their
individual
versions.
A
A
This
kind
of
conversation
to
slack,
although
I
usually
would
prefer
not
to
do
you
know,
rather
do
things
in
public
like
in
an
issue,
but
we
may
want
to
just
kind
of
powwow
with
with
some
folks
who
have
more
context
and
and
background
and
work
through
what
some
of
these
issues
might
be
and
whether
we
should
at
least
form
a
team
to
kind
of
work
through
them
so
good
times.
A
A
I
will
share
this
link
with
anyone
who
has
interest
so
there's
11
people
who
are
were
on
some
sort
of
documentation,
team.
A
Maybe
next
year
it's
a
you
know
a
seasonal
thing
come
on.
How
do
I
I
don't
want
to
do
that.
I
want
to
actually
select
this
text.
Oh
you're,
great,
no
jay,
yes,.
A
A
D
D
You
want
to
ask
the
questions
for
them.
Well,
one
person
was
just
asking
he
wanted
to
join
the
redesign
and
doc
team,
so
I
just
pointed
them
to
the
you
know,
page.
A
Yeah,
if
you're
watching
right
now
and
that's
your
question,
which
is
a
great
question-
essentially
it's
this
stuff
is
open
source
and
we
encourage
you
to
just
start
getting
involved
watching.
These
meetings
is
a
great
way
to
sort
of
get
up
to
speed
on
what
we're
working
on
and
what
we're
thinking
about,
but
definitely
take
a
look
at
the
issues
and
the
prs
get
yourself
familiar
with
the
code
base
and
feel
free
to
join
the
slack
org.
A
We
are
operating
in
the
openjs
foundation,
slack
if
you
go
to
openjsforfoundation.org
collaborate,
you'll
find
links
to
the
calendar
and
to
how
you
join
slack
and
all
that
stuff
and
please
feel
free
to
to
start
getting
involved.
A
Once
you
kind
of
contribute
to
the
effort
for
some
time,
then
you
know
you
might
get
promoted
to
the
team.
We'd
be
happy
to
have
folks
be
involved
and
give
them
more
privileges,
as
as
we
you
know,
do
the
work
and
yeah.
So
please
get
involved,
we'd
be
happy
to
have
you
any
other
questions
no
looks
like
I'm
looking
at
the
season
of
docs
right
now
for
2021,
and
it
looks
like
it
is
in
process
already.
A
A
So
it's
definitely
something
we
could
look
at
taking
advantage
of
in
2022,
but
I
think
we
might
have
missed
it
for
this
year,
so
but
yeah
we
should
have
that
on
the
radar
and
maybe
even
yeah,
I
don't
know
dark
steam
would
be.
A
Great,
what
else.
A
A
A
So
I
wonder
if
there's
an
issue,
what's
the
last
closed
issue?
A
D
I
guess
kind
of
similar
to
the
docs
as
categories.
Maybe
we
can
talk
about
what
we
want
to
include.
I
know
we
have
like
news
and
and
announcements.
I
guess
those
are
kind
of
we're
kind
of
defining
those
as
the
same
right
now
and
then
right
now
we're
using.
I
think,
medium
right.
A
I
don't
think
so,
medium
node.js,
let's
see.
C
A
A
Yeah
interesting,
I
find
medium
to
be
a
problematic
platform,
so
I
would
love
to
move
off
of
it,
or
even
at
least
have
a
canonical
source
first
and
foremost,
and
then
you
know
we
could
syndicate
to
medium
and
and
too.
A
But
you
know,
that's
that's
something
that
we
would
need
to
talk
about
with,
with
with
other
folks.
B
A
And
I
feel,
like
you
know
we
could
have,
I
feel
like
tags
and
labels.
You
know,
makes
more
sense
than
categories
because
I
feel,
like
you
know,
or
maybe
we
I'm
conflating
the
two
but
like
I
could
see
something
being
having
a
security
tag
and
a
news
or
announcement
tag.
You
know,
like
news
and
announcements
to
me
is
so
generic,
like
isn't
everything.
A
News
and
announcement
yeah
but
yeah
like
security
and
releases,
and
you
know,
and
then
you
know
beyond
that
we
could.
We
could
figure
out
some
sort
of
labeling
or
or
tagging
system.
That
makes
sense.
D
Yeah
yeah,
I
think,
categories
that
versus
tags
are
basically
the
same
thing.
Yeah.
A
As
long
as
it's
not
you
know,
like
a
singular
thing,
I
can't
think
of
the
word
I'm
looking
for,
but,
like
exclusive
of
other,
you
know
you
can
only
be
in
one
category.
If
that's
not
the
case
yeah
I
mean
I
would
imagine
we
might
even
adopt
some
sort
of
label
system.
That's
directly
uses
like
you
know,
github
repo
names
or
something
you
know.
So
it's
very
clearly
like
this
is
that
team's
content
or
area
of
concern,
or
some
way
of
getting
around
that.
A
So
it's
a
good
question.
I
mean
I
don't
even
know
if
people
are
fully
on
board
on
having
a
blog
on
the
node.js
website,
I'm
all
for
it,
but
I
don't
you
know
that
we
would
need
to
have
that
sort
of
conversation.
D
So,
who
else
would
need
to
be
onboarded?
D
A
It's
a
good
question.
I
mean
I
would
think
at
least
some
some
support
from
key
players,
especially
like
probably
tsc
and
other
other
leadership
in
in
the
project.
I
guess
you'd
say
you
know,
michael
james
snell,
rich
trott
tyranny
miles.
A
You
know
I
mean
not
that
they
are
the
gatekeepers,
but
I
think
just
getting
other
people
approving
of
a
move
like
that
would
would
make
me
feel
more
comfortable,
nice,
oh
good,
so
yeah
I
mean
I
feel
like
we
have
a
lot
of
open
questions
and
they're
sort
of
some
of
them
are
pretty
big
questions,
and
I
don't
know
what
the
best
way
to
deal
with
that
is,
I
mean
typically,
we
would
want
to
just
create
an
issue
and
kind
of
maybe
we
should
just
create
issues
for
each
of
these
yeah
yeah.
C
A
Worry
because
the
website
redesign
repo
has
a
lot
of
issues.
It's
very
issue
active.
We
just
need
to
make
sure
that
they-
maybe
we
even
pin
some
of
them.
You
know
yeah
yeah.
We
can
do
that
yeah,
some
of
these
important
ones.
We
should
probably
be
pinning
so.
D
We'd
also
use
the
project
board
more
on
some
of
these
and
yeah.
These
open
questions
like
how
we
did
with
the
other
stuff.
That's
a
really
good
idea.
A
A
If
you
can't
tell
I
get
a
little
overwhelmed
by
the
website.
Redesign
effort,
sometimes
yeah
yeah,
but
it's
good
to
like
throw
things
up
on
a
project
board
or
something
and
be
like.
Oh
okay,
this
isn't
as
bad
as
it
sometimes
feels
so
yeah
all
right,
cool
well,
so
yeah.
I
think
we
should.
We
should
have
a
few
issues
for
some
of
these
things.
I
think
it
makes
sense
to
you
know,
maybe
even
instead
of
in
slack,
we
should
have
these
conversations
and
issues
and
and
raise
awareness
of
them
in
slack.
A
You
know,
create
an
issue
for,
should
we
have
a
docs
team,
you
know
at
a
minimum
to
help
us
integrate
docs
into
the
redesign
and
point
people
you
know
and
slack
to
that
issue
and
we'll
have
the
conversation
there.
A
A
Talk
through
and
work
on,
yeah
cool,
any
other
questions
in
the
youtube
that
you
saw.
Let
me
check
yeah,
no
okay,
good
all
right.
Well
with
that.
Maybe
we
should
call
rap.
You
know
talk
more
on
the
issues
and
slack,
and
you
know
thanks
everybody
for
all
that
you're
doing.