►
From YouTube: Node.js Website Redesign
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
Awesome,
hello,
everybody
and
welcome
to
another
episode
of
website
redesign
yeah.
We
actually
have
two
new
folks
on
the
call
today.
So
let's
do,
let's
do
quick
introductions.
You
can
really
just
technically
did
them
offline,
but
it's
good
to
do
it
online
as
well
so
I'm,
Adam,
calm,
calm,
chairperson
and
co-chair,
or
the
website
redesign
initiative
based
in
San,
Francisco
and
I.
Do
design
systems
over
at
LinkedIn
full-time
no
eat?
How
about
you
sure.
B
So
my
name
is
Mohd
and
I
am
from
india
I'm
a
JavaScript
developer
in
past
I
have
been
a
D
sock.
Student
and
I
have
also
mented
some
of
the
keys
of
students
and
GCI
students
from
past.
We
this
for
context,
Mohit
what're
those.
What
do
those
abbreviations
stand
for
so
jisuk
stands
for.
The
google
Summer
of
Code
and
GCA
is
Google
coding.
Awesome
awesome.
A
C
D
Folks,
I'm
Anil
I
co-chair
website
redesign
with
Adam
I
am
a
member
on
the
calm,
calm
with
no
Jess
and
I
am
a
developer
advocate
at
envision
super
stoked
to
have
two
new
people
here
good
to
meet.
You
John
and
Mohit
yeah
I'm
excited
to
see
where
this
goes.
I
hope
your
first
session
will
be
exciting
facing
you
can
dive
into.
If
not
like
we're
super
happy
to
help
guide
you
towards
something
that
you
feel
like.
You
can
contribute
meaningfully
to
show
Thanks
very.
A
Cool,
so
we're
gonna
take
a
little
different
approach
to
this
meeting
today
since
we're
missing
a
good
number.
The
regulars
and
we
have
two
new
folk
I
figured
we
can
go
through
I
gave
a
miniland.
I
gave
a
talk
over
at
the
community
corner
at
the
Vancouver
conference
that
just
wrapped
up,
and
it
would
be
good
to
have
that
recorded
somewhere.
So
we're
gonna
go
through
that
in
the
beginning.
I'll
share
the
slides
up
here
and
we'll
blow
through
them.
A
Yes,
sweet.
We
will
make
sure
we're
on
make
sure
around
you
disturb
here.
Y'all,
don't
see
my
text
messages
pop
up,
Oh,
awesome,
so
website
redesign.
At
the
conference
we
presented
a
little
bit
of
a
history
of
website,
redesign
I,
so
I
could
already
said:
I'm
Adam,
Miller,
Kham
Kham,
chairperson
Design
Systems
tech,
lead
at
LinkedIn
and
McNeal.
A
Also,
a
comic-con
member
is
a
dev
advocate
at
envision
I
and
we're
gonna
go
over
a
little
bit
about
the
team.
That's
working
on
website
redesigned
the
history
of
the
project
where
we're
at
right
now
and
where
we
kind
of
envision
where
the
future
is
gonna
go.
So
we
we
work
over
on
the
nodejs
github
repo
for
website
redesign
and
our
goal
is
to
try
and
turn
the
website
into
something
that
actually
shows
off
notes
values.
A
I
we
have
about
23
active
contributors
and
Counting
we're
growing
all
the
time,
although
we
have
five
to
seven
core
contributors
that
really
are
driving
a
whole
lot
of
the
content,
but
it's
a
big
community
effort
which
matically
should
for
it
all
together,
and
we
really
want
to
make
sure
the
website
represents
what
nodejs
values.
So
this
is
very
much
inspired
by
nodejs
interactive
by
also
back
in
Vancouver
from
last
year,
where
we
ran
an
exercise
but
with
all
the
contributors
to
try
and
identify
the
core
values
of
nodejs
and
the
taming
major
takeaways.
A
Here
we're
know
it
is
stable,
inclusive,
welcoming
performant
and
fun,
but
if
you
go
and
look
at
the
current
website
yeah
is
it
welcoming
the
the
two
giant
black
bars
at
the
top
and
bottom
really
constrain
the
environment,
we're
using
crazy,
convoluted
language?
That's
not
particularly
approachable
that
is
not
particularly
welcoming
to
any
new
engineers
is
inclusive.
On
top
of
all
the
non
welcoming
language
and
sighin
aspects
that
green
on
dark
gray
is
actually
doesn't
pass.
Colorblind
guidelines
for
for
other
members.
A
In
fact,
I
don't
know
about
you,
but
that
kind
of,
like
it
looks
like
it
was
thrown
together
by
a
engineer.
Hacking
in
their
basement
doesn't
feel
particularly
stable
or
performant
and
doesn't
show
off
no
JSA
production-ready
system,
and
is
it
fun,
I
I,
don't
know.
I
love
corporate
graves
I
think
it's
the
most
fun
way
to
present
any
information,
but
I
have
a
hunch
that
the
rest
of
the
world
does
not
agree.
A
So
we
wanted
to
start
from
the
drawing
board
and
really
peel
back
the
layers
here
and
figure
out
what
the
core,
how
we
can
best
communicate.
What
what
nodejs
is
so
there's
a
lot
of
places
we
could
take
inspiration
from
we
went
and
identified
ten
different
projects,
ranging
from
particularly
in
the
front-end
component
framework
space
and
the
more
programming
languages
space
that
we
fit
into
I
and
we
came
away
with
a
whole
bunch
of
inspiration.
We
actually
published
a
blog
post
called
redesigning
nodejs
part
1.
It's
kind
of
a
competitive
case
study.
A
We
became
an
official
initiative
of
the
community
committee
and
we
decided
we're
going
to
approach
this
like
we're
building
a
product
because
that's
what
a
website
is
so
we're
going
through
four
major
product
phases:
phase
one
was
tackling
information,
architecture
and
user
experience,
so
kind
of
how
all
the
pieces
fit
together.
Stage
two
is
actually
designing
the
thing
and
making
sure
it
actually
conveys.
Nodejs
is
values.
A
We
missing
a
slide
here,
weird
started:
tackling
we
put
together
yeah,
we
in
issue
number
four:
we
started
digging
the
part
at
the
current
website
structure.
It
started
talking
about
how
to
best
structure
it.
After
the
fact,
it
resulted
in
a
pretty
solid
envision
prototype
that
we
that
we
threw
together
receive
feedback
on
iterate
it
on
a
little
bit.
It
lives
over
on
the
envision.
A
You
can
go
and
take
a
look
at
it
still
to
this
day,
I
and
then,
after
receiving
all
this
feedback,
we
and
figuring
out
like
how
the
type
of
information
we're
hoping
to
present
in
the
large
sections
that
we
wanted
to
presented
in
general
effects.
Layouts
we
were
going
for.
We
were
able
to
move
on
to
the
design
pace,
so
we
started
tackling
some
of
the
design
stuff,
specifically,
first
and
foremost.
What
colors
are
we
using?
A
This
resulted
in
yet
another
medium
blog
post
about
color
design,
which
was
a
whole
lot
of
fun,
but
this
took
a
lot
of
time
and
go
figure,
not
a
lot
of
professional
designers,
hang
out
on
github
and
are
engaged
with
the
node.js
projects.
So
I
was
a
little
daunted
about
how
we
were
going
to
complete
this
in
a
reasonable
amount
of
time.
But
luckily,
this
is
about
the
time
when
folks,
over
at
run
kit
owned
by
stripe,
started
to
take
attention
to
the
project.
A
So
francisco
and
joey
often
joined
these
meetings,
but
stripe
has
very
graciously
donated
a
full-time
designer
to
the
project
to
help
out
and
figure
out
how
to
best
represent
the
site
I
ate
at
we're
currently
working
through.
So
the
biggest
thing
that
we
want
to
avoid
right
now
is
design
by
committee,
because,
unlike
with
code,
if
you
throw
the
more
people
you
throw
at
design,
typically
the
worse
that
it
ends
up
coming
out.
So
instead
we're
doing
a
design
by
proposal
process
where
the
designer
joey
is
working
very
closely.
A
With
myself
and
a
couple
other
folks
in
the
in
the
node.js
community
to
bring
together
a
full
proposal
of
what
the
site
could
finally
look
like,
which
will
then
bring
to
this
group
and
eventually
start
growing
the
circle
of
people
who
are
giving
feedback
on
what
could
be
a
full
like
if
we
could
watch
this
today.
Hey
but
the
approach
you
take
luxury
designs
and
that
should
be
coming
down
the
pipeline
fairly
soon
for
for
redesign
work.
A
So,
with
design
work,
oh
and
on
top
of
that
I
run
kit
is
the
the
deficit
run.
Kit
are
doing
a
lot
of
the
work
to
get
live.
Demos
on
the
site
itself,
so
inside
of
our
API
documentation,
you'll
be
able
to
see
runnable
code
right
alongside
the
examples,
and
this
will
also
work
in
getting
started
Docs
as
well.
It
gets
automatically
pulled
out
from
markdown
it's
a
cool
little
bit.
A
A
little
bit
of
tech
and
run
kit
is
slowly
becoming
kind
of
the
de
facto
standard
for
now
on
on
documentation
sites,
it's
used
on
NPM,
it's
used
on
Express
and
it's
used
on
a
whole
slew
of
other
sites
to
show
runnable
code
demos.
So
this
will
bring
a
whole
layer
of
interactivity
to
the
site
as
well.
So
it's
amazing
what
they're,
what
they're
bring
to
the
project
so
with
design
largely
underway
from
somebody
who's
with
very
capable
hands?
A
We've
been
most
recently
focusing
on
content
and
we
want
to
make
sure
that
we're
making
valuable
content
that
actually
enables
people
coming
to
the
site
to
move
quickly
and
get
to
get
to
where
they're
going.
We
started
out
with
voice
and
tone
guidelines
over
on
issue
number
13
that
is
still
in
the
works,
so
I,
it's
a
living
document
and
there's
the
room
for
always
room
for
improvement.
A
And
then
we
ran
an
awesome
ideation
session
over
at
JS
conf
Berlin,
where
we
got
a
group
of
people
in
a
room
and
started
working
through
user
persona
creation
and
then
content
ideation
for
all
those
different
user.
Personas
that
we
identified
and
a
whole
bunch
of
content
came
out
of
there
for
possible
possible
content.
A
People
would
want
to
come
to
the
site
to
consume
and
a
lot
of
that
was
synthesized
over
in
issue
number
60,
where
there
is
a
huge
list
of
possible
content
that
we
need,
some
of
it
more
general,
some
of
a
bit
more
specialized
and
all
of
it
very
valuable.
At
the
end
of
the
day,
there's
still
work,
then
you
we've
done
to
synthesize
this
in
two
major
sections
on
the
site.
If
you
look
at
the
envisioned
prototype,
we
have
a
kind
of
a
concept
of
learning
paths
in
grouping
content
by
type
of
developer.
A
So,
there's
the
basics
that
you
need
to
know
just
to
get
started
and
ojs.
Then
there's
I'm
a
front-end
developer,
who
wants
to
use
node?
What
do
I
need
to
know
about
front-end
build
systems?
What
value
does
this
have
for
me?
I'm,
an
SRE
who's,
looking
to
prop
up
a
node.js
stack
at
my
company.
What
tools
do
I
need
to
know
how
do
I
keep
something
running,
etc,
etc.
A
We
don't
quite
know
exactly
where
this
documentation
files
will
live
exactly
yet,
although
we
had
a
great
session
at
the
club
summit
over
in
Vancouver
talking
about
documentation
ingestion
and
how
we're
gonna
structure
it,
but
for
now,
in
in
lieu
of
a
final
home
for
for
documentation,
we're
keeping
the
website
redesign
repo
the
documentation
folder
in
there
contains
the
readme
about
how
to
RFC
or
how
to
PR
a
documentation
RFC
into
the
folder
and
there's
a
slide
missing
here,
because
this
happened
just
in
the
past
three
days.
But
there
is
an
amazing
content.
A
Creator
in
Flavio
over
in
Italy,
who
recently
published
a
lead,
was
called
the
definitive
nodejs
Handbook,
which
is
a
amazing
amount
of
getting
started,
content
that
he
has
very
kindly
donated
back
to
the
project
and
currently
has
open
in
PR
number
105
on
website
redesign.
It
is
Mineo.
Was
it
4,000
lines
worth
of
documentation,
written
for
getting
started
guides.
A
A
It's
amazing
that
that
he's
contributed
that
back
so
there's
a
lot
of
getting
started,
guides
PRD
and
already
we
just
need
to
do
a
quick
review
of
it
and
we
have
a
volunteer
who
helps
are
in
a
code
school
over
in
Portland,
she's,
gonna,
sick,
a
whole
bunch
of
new
developers
who
are
new
to
the
industry,
to
kind
of
validate
that
it's
a
it's
a
type
of
content
that
they
that
they
need
to
get
started.
Good,
provide
advice
for
improvement,
but
that's
currently
in
the
works
as
well.
A
We
have
we
have
a
lot
moving
forward
on
that
Stage
four
is
gonna,
be
to
build
the
darn
thing
I,
but
at
the
moment
it's
kind
of
a
big
question
mark
I
can
fill
in
some
blanks
about
what
we
talked
about
at
the
at
the
Vancouver
summit
that
just
wrapped
up
a
week
and
a
half
ago.
But
right
now
we
are
very
much
focused
on
the
the
content
and
rolling
out
the
design
at
the
moment,
although
we
should
just
begin
to
start
talking
about
the
tech
right
now
so
I
yeah.
A
A
Nothing,
nothing!
That's
that's
good
for
sharing!
Quite
yet
I'm,
hoping
by
next
meeting,
we
will
have
I
mean
Mineo
can
attest.
I've
been
saying
this
for
forever
he's
a.
He
really
wants
to
keep
a
keep
things
close
to
his
desk.
Let's
stop
sharing
there
we
go,
but
the
timeline
the
timeline
is
or
before
end
of
year.
We're
gonna
have
we're.
Gonna
have
mocks
for
this
group
to
to
look
at
and
review,
which
I'm
quite
excited
for
he's
working
on
some
new
mascot,
ideations,
more
cuffs
and
illustration
style.
A
That's
gonna
be
very
much
used
for
the
for
the
homepage,
but
there's
a
lot
of
stuff.
We
can
do
before
that.
There's
the
chat.
There's
the
check
this
there's
a
lot
of
stuff.
We
can
do
before
that
to
start
working
on
documentation,
ingestion
and
content
curation,
which
will
be
kind
of
independent
of
mr.
A
hanket
demo
and
here's
the
sorry
I'm
posting
links
in
the
chat,
there's
all
the
links
that
were
in
the
presentation
that
we
can
do
even
without
a
final
final
mock,
we'll
know,
the
general
structure
of
the
site
and
styles
can
be,
can
be
layered
on
after
the
fact.
There's
a
bunch
of
build
stuff
we're
going
to
need
to
tackle
first.
D
D
I
find
that
having
something
specific
that
we
guide
people
through
actually
helps
because
in
the
beginning,
when
people
join
our
project
and
I've
been
running
some
workshops
and
opensource
over
the
past
little
while
I
found
that
people
want
to
join
open-source-
and
this
may
not
be
true
for
you,
but
it
may
it
may
be
that
you
want
to
join
open-source
but
you're,
not
yet
sure.
Where.
A
B
C
D
On
well,
it
seems
like
believe
you
may
have
some
familiarity
if
you've
been
contributing
to
another
open-source
project
for
a
while.
You
may
have
some
familiarity
with
processes
that
people
use
typically,
because
you
know
in
processes
we
have
over
here
are
two
meant:
make
sure
that
people
work
in
different
time
zones
and
people
who
don't
do
this
as
a
full-time
job
are
able
to
jump
in
whenever
they
can
and
review
the
stuff
so
I'm
thinking
that
would
be
different
from
what
Jean
might
want
to
get
into
with
John
I'm
thinking.
D
A
Big,
the
big
need
that
we
have
right
now
is:
is
our
communication
content,
so
there's
a
keeping
in
mind
that
we
just
got
a
giant
dump
from
Flavio
and
105
I.
Also
just
posted
a
link
to
issue
number
60,
where
we
had
that
list
of
topics
that
that
we
were
just
didn't
in
touching
on
the
site.
I
and
despite
the
this
year,
amount
of
content
that
Flavio
just
PR
din,
which
it's
there's
still
plenty
left
here
to
to
write
about.
So.
A
D
Is
in
issue
sixty
number
one
I
mean
a
sixty
number
one
issue:
number
61
I'm,
seeing
that
there
is
some
work
happening
around
user
feedback.
Also,
that
seems
like
that
could
use
some
added
just
perspective
about
what
questions
might
be
relevant,
y'all,
Jean
and
mojito.
You
might
find
it.
You
might
find
it
useful
to
jump
in
there
and
click
on
the
forum
that
one
of
the
new
contributors
has
put
together,
and
so
basically,
when
you
go
through
so
I'm
I,
don't
want
to
start
like
completely
from
scratch.
D
It
is.
It
is
quite
helpful.
So
right
now
in
issue
number
61
they're
asking
about
whether
or
not
searching
choices
in
a
forum
would
make
sense
to
do
so.
We're
looking
for
if
there
might
be
an
in
the
extra
perspective
as
to
what
to
prioritize
in
that
forum,
so
you
could
jump
in
there
also
and
out
of
your
perspective,
so.
A
And
let
me
let
me
give
a
brief
I
realize
didn't
I
glossed
over
the
the
text
slide
a
little
too
fast
in
there.
Let
me
give
a
brief
brain
dump
about
what
was
discussed
during
the
last
Vancouver
summit
as
well.
I,
literally
wrapped
up.
We
can
have
to
go.
We.
It
was
our
first
time
reaching
the
topic
of
tech,
architecture
and
tech
requirements
and
the
the
major
points
we
we
agreed
on
in
the
in
the
breakout
session,
where
documentation
used
to
live
alongside
the
content
that
is
documenting.
Hopefully
that's
fairly
non-controversial
so
like
getting
started.
A
Doc's
should
probably
live
in
the
main
nodejs
node
Rico
I
mean,
while
community
community
pages
should
probably
go
live
in
the
comm
come
repo
so
that
they
can
keep
an
active
list.
So
we're
gonna
have
this
model
of
needing
to
pulling
content
from
many
many
different
sources
and
stitch
it
all
together
in
a
sensible
way,
and
so
the
the
direction
we're
hoping
to
take
for
the
documentation
site
is
actually
much
like
what
we've
cobbled
together
with
my
team
at
LinkedIn.
A
Conveniently
where
you
can,
we
have
a
you,
have
a
standard
way
of
kind
of
packaging
documentation.
The
primary
language
is
just
in
markdown
and
at
Build
time
the
web.
The
the
website
depends
directly
just
on
the
git
repos
themselves
and
at
Build
time
it
will
reach
into
each
repository,
find
the
documentation,
stitch
it
together
and
spit
out
a
mostly
static
site
that
that
operates
as
expected.
A
So
we
that's
about
as
far
as
we
got,
we
very
intentionally
did
also
did
not
talk
about
component
frameworks.
We
didn't
talk
about
build
system
choices.
We
didn't
talk
about
because
we're
hoping
to
nail
down
technical
requirements
and
then
come
back
with
recommendations
in
an
extinct
way
for
how
it's
actually
going
to
be
executed
so
at
the
same
time
to
fulfill
those
major
requirements.
If
you
two
have
any
ideas
on
how
that
can
be
best
done,
feel
free
to
go.
A
B
A
We
also
toyed
around
with
the
idea
of
not
even
using
a
component
framework
like
if
this
thing
can
build
to
a
static
site
that
is
honestly
ideal,
like
the
less
the
less
moving
parts,
the
better
for
something
something
this
large
I.
So
keep
that
in
mind
to
as
you
as
you
knock
around
personal
ideas
about
how
this
thing
can
be
structured,
yeah.
A
B
A
Yeah
yeah
there's
there's
a
number
of
open
source
options
that
we
could
probably
pursue
as
well
and
if
they
can,
if
they
can
fulfill
that
requirement
of,
we
need.
We
need
some
way
of,
depending
on
a
gate,
coordinate
in
a
package.json
and
pulling
in
dart,
sucking
in
documentation
and
building
that
into
the
site
like
if
they
can.
As
long
as
I
can
fulfill
that
requirement,
I'd
say
they're
a
candidate
for
for
use
here
so
doing
a
probably.
A
This
should
be
an
issue
open
on
the
on
the
repo,
but
doing
an
audit
of
open
source
options
for
that,
so
we
maybe
don't
have
to
hand
roll
our
own
documentation
stitcher
that
would
be
convened
so
yeah,
it's
one
of
you.
If
one
of
you
actually
would
like
to
open
an
issue
and
kick
that
off
in
the
repo
I
would
greatly
appreciate
it.
I
know:
I've
been
buried
the
last
week
catching
up
on
work
since
the
conference,
so
so,
if
yeah,
if
one
of
you
wants
to
open
it
up
that
way,
they'll
be
amazing.
A
B
A
A
A
Also
agendas
in
issue
number
104
I
think
we
can
blow
through
it
pretty
quick
yeah
and
in
fact
this
one
should
not
be
on
the
agenda.
So
issue
number
21
723
in
nodejs,
slash
node,
creating
a
branch
of
Docs
using
run
kit,
I
just
status.
Update
on
that
Francisco
has
worked
out.
It
seems
like
all
the
technical
issues
with
it
he's
just
waiting
on
a
release
of
es
lint,
plugin
markdown.
He
got
his
pull
request
in
after
that.
The
build
airs
should
fast
and
he
can
get
this
PR
landed,
which
is
exciting.
A
So
this
is
the
first
validation
of
the
live
demo
use
case
and
the
changes
he's
making
the
API
Doc's
right
now
will,
with
a
slight
risk
in
be
almost
exactly
what
we'll
be
using
on
the
new
site,
which
is
exciting
another
another
thing
we're
trying
to
do
is
not
make
the
entire
project
do
any
large
changes
in
order
to
get
the
new
site
out.
So
the
biggest
the
biggest
thing
we
need
to
preserve
there
is
the
current
API
Doc's
need
to
stay
the
same,
but
look
nice
and
function
a
bit
better.
A
So
Francisco
has
been
doing
work
to
make
that
happen.
I
put
PR
number
105
on
the
agenda
for
visibility
sake.
This
is
Flavio's,
add
node,
handbook
content
PR.
It
is
a
huge
beast
of
a
PR.
We're
gonna
get
a
whole
bunch
of
people
in
there
to
help
review
it.
He
granted
this.
This
content
is
stuff,
that's
already
been
reviewed
over
and
over
again,
since
it
was
published
elsewhere,
but
he
made
changes
to
like
even
making
matches
and
mentions.
A
D
D
So
each
one
is
kind
of
self-contained.
I
am
wondering
if
so,
for
one
thing,
part
of
what's
slowing
us
down
that
will
slow
us
down.
Here
is
the
fact
that
it's
a
giant
5,000
line
PR
and
typically
we
try
to
split
these
kind
of
things
up
so
I'm
wondering
if,
for
the
sake
of
the
students
and
anyone
else
who
might
be
reviewing,
we
split
this
up
into
the
individual
section.
A
Something
I
something
I
like
about
it
coming
in
as
a
bulk
PR
is.
We
can
all
look
at
his
no
handbook
branch
and
see
see
it
on
disk,
as
it
will
show
up,
because
part
of
what
the
review
process
will
be
about
is
ordering
of
Docs
and
how
the
pieces
flow
together.
And
you
know
it's
a
it's
a
single
body
of
work,
not
necessarily
standalone,
so
we
can,
we
can
maybe
keep
everything
living
together,
but
still
because
they're
conveniently
numbered.
We
can
divvy
out
sections
to
people
as
they
make
sense,
and
especially.
A
Especially
Jordan
and
our
army
of
developers,
we
can
work
with
work
with
her
to
just
split
up
content.
I
agree,
it's
it's
a
beast
of
a
peacock
and
probably
won't
get
reviewed
unless
there's
some
amount
of
order
to
it,
but
I
also
don't
know
if
there's,
if
having,
what
is
it
53
PRS
opened
up
wouldn't
would
reduce
the
would
reduce
the
barrier
to
entry
here.
D
They're
meant
to
play
together,
I
see
that
makes
sense.
Maybe
then
I'll
start
a
conversation
or
comment
about
having
a
process
around
it.
Maybe
when
we
start
assigning
people
to
it
that
we
link
them
directly
to
the
relevant
section
group
because
scrolling
through
this,
what
yeah
yeah.
So
we
can
give
people
individual
markdown
files
to
review
okay,
yeah.
A
Here's
the
I'm
gonna
link
directly
to
the
yeah.
It's
50
55
individual
directories.
Here's
it
on
Flavio's
github,
oh
yeah,
so
we
can,
we
can
assign
directory
ranges
to
people,
do
it
and
yeah
that'll
probably
help
out.
So
we
can
have
a.
We
can
have
a
call
for
call
for
reviewers
get
a
list
of
names
and
then
divvy
it
up
by
number
of
people.
We
have
yeah.
A
D
A
A
A
A
Think
we
should
punt
on
chatting
about
this,
maybe
until
after
we
get
through
Flavio's
bulk
content
and
then
we
we
talked
about
issue
number
60
a
little
earlier
in
this
meeting,
basically
go
PR
content
in
Mineola,
sir.
Is
there
active
work
that
needs
to
be
done
on
64,
organizing
still,
or
should
we
remove
the
agenda?
Lee.
D
Can
remove
that
part
from
the
issue
I
think
at
this
point
it's
we
use
it
as
reference
yeah.
A
D
A
Yet
it
might
take
like
ten
minutes
to
a
half-hour
to
come
in
I.
Don't
know,
I
just
have
like
a
whatever
that
open-source
slack
invite
server
is
running
I'm,
not
sure
what
the
delay
on
that
is.
If
it
doesn't
end
up
coming
through,
you
can
reach
out
to
the
admins
of
it
or
we
can
ping.
D
A
A
D
Yeah
I
wish
there
was
also
an
option
to
ping
you
when
people
join
that
part
of
the
meeting
like
because
it
it
like
a
doorbell
noise.
When
you
join
say
this
part
of
the
meeting,
if
there's
no
like
waiting
area,
but
if
there
is
a
waiting
area,
you
don't
get
paint
and
there
should
be
an
option
for
meetings
that
are
small
enough,
that
we
yeah
I,
don't
see
when
attendees.