►
From YouTube: Node.js Website Redesign Initiative Meeting
Description
B
B
Okay-
oh
sorry,
I
heard
the
stream.
In
the
background
it
very
much
confused
me
because
it
was
talking
to
myself.
Okay,
so
we're
live
now
with
the
nodejs
website,
redesign
committee
or
initiative.
Do
we
want
to
start
going
down
the
agenda?
We
should
do
introductions
first,
I
see
so
I'll
go
first
sub
judice,
iron,
I'm,
sure
person,
I,
think
no
J's
committee
committee
and
I'm
a
participant
website,
redesign.
B
B
A
B
D
D
C
B
I
was
in
the
last
call
and
I
did
not
hear
that
and
I
also
have
a
summary
and
I,
don't
believe
it
was
discussed
in
the
summary,
so
I
will
that
next
cut.
The
next
call
is
in
about
hour,
I
think
a
month
from
Thursday,
so
I
will
actually
just
end
up
sending
an
email
to
them
today
or
well.
Probably
not
today,
because
I
am
I
have
nine
meetings
today,
but
I
will
do
it.
Dignan.
B
C
Great
thank
you.
I
was
also
thinking
going
by.
I
was
also
thinking
just
before
this
call.
We
can
possibly
vote
to
or
choose
to
move
ahead
with
the
color
palette
for
all
website
property
material
without
having
buy-in
from
marketing
and
for
logo
asset
changing
like
that's
really
what
we
need
approval
for
so
yeah,
yeah
and.
C
D
Well,
that's
just
the
next
topic,
then.
Is
we
need
to
identify
topics
to
discuss,
discuss
at
the
collab
summit?
So
far
we
have
two
things
identified,
getting
started
which
context
for
that
is.
We
wanted
to
see
if
we
could
bring
node
school
content
into
getting
our
new
getting
started.
Partly
because
note
school
content
is
designed
to
be
beginner
friendly
and
should
work
for
anyone
wanting
to
get
started
with
nodejs.
D
D
Another
part
that
was
identified
I
think
was
we
wanted
to
iterate
over
how
we
describe
no
jess
on
the
node.js
org
page
I
believe
tourney
proposed
that
we
work
on
that
to
make
it
to
bring
it
a
little
bit
more
to
make
it
a
bit
more
current
I'm
trying
to
pull
up
the
issue
to
have
more
context
here.
Yeah.
B
So
that
that's
just
basically
like
we
have
we've
had
that
same
description
of
like
nodejs
is
in
a
event-driven
IO
runtime
for
Java
like
it's
a
whole
thing.
That's
a
technical
view
that
isn't
really
super
friendly
to
non-technical.
People
are
people
who
are
not
familiar
with
all
those
terms
and
that's
not
necessarily
a
great
introduction
to
the
project.
B
So
more
of
just
riffing
on
that
and
seeing
how
like
that
stuff
can
be
included
there,
we
shouldn't
drop
that
context,
but
just
making
something.
That's
a
little
bit
more
approachable
because
I
know
like
when
I
opened
the
node.js
10
site
or
node.js
0.10
site
and
0.8
sites
back
when
I
was
getting
started
or
trying
to
that
was
totally
unapproachable
to
me
as
a
someone
interested
in
this,
but
has
no
idea
what
it
is
that
didn't
really
help.
So
you
know
that's
yes,
that's
a
good
start,
but
yeah.
B
There's,
oh
so,
on
the
day,
there
is
something
else
that
we
should
get
to
design
I
have
an
update
for
design
stuff
in
a
bit
once
we're
done
with
this
discussion,
but
on
the
the
run
is
a
code
samples
thing
that
we've
that's
in
that
discussion.
For
for
what
we
should
talk
about
at
collaborator
summit.
B
The
rugged
team
will
be
there
at
the
collaborative
summit
they're
coming
out,
so
we'll
be
able
to
talk
to
them
and
like
have
them
participate
in
the
discussion
as
well
and
kind
of
help
us
guide
that
I
actually
don't
know.
If
Jen
Schiffer
is
going
to
J's
coffee
you,
she
might
be
I'll,
follow
up
with
her
and
see
if
she
wants
to
come
as
well.
If
she
she's
gonna
even
be
able
to
days
earlier,
oh
yeah,
that's
something
to
keep
track
of
as
well.
B
D
B
C
B
C
That's
awesome,
so
Miniland
I
will
be
chatting
this
Saturday
over
the
weekend
to
get
like
a
full,
dedicated
itinerary
for
what's
going
to
be
happening
during
the
during
the
meeting,
so
I'm
hoping
to
keep
it
pretty
well
structured-
and
you
know,
have
a
few
group
exercises
and
subgroups
to
break
off
and
do
their
own
parts
and
keep
iterating
on
content.
We're
interested
so
we'll
get
that
posted
in
an
issue.
My
hope
is
by
Monday
would
be
my
who
will
get
it
written
up
as
a
proposal
and
get
it
posted
in
there.
C
D
B
I'm
sorry,
Greg
Wallace
is
a
member
of
the
Linux
Foundation
and
he
he
works
at
the
Linux
Foundation
and
currently
works
on
some
of
the
marketing
things
around
nodejs
and
the
node.js
foundation.
So
it
might
be
helpful
to
get
him
in
there,
as
well,
even
for
just
a
small
small
period,
if
he's
there,
because
we
could
I
really
do
think
duplicating
effort
across
two
different
sites
is
productive
for
both
for
both
groups,
both
the
project
and
for
the
foundation,
especially
if
we
do
go
like
when
we
get
to
the
implementation
side.
C
So
I
was
just
gonna
say
if
I
remember
correctly,
the
main
concern
is
they
don't
want
it
to
live
in
github,
because
there's
a
lot
of
people
who
don't
know
how
how
to
get
or
how
to
code
and
who
need
to
manage
content
on
the
foundation
will
get
it
so,
depending
on
how
we
make
it,
they
might
be
more
amicable,
the
jumping
on
board
with
this.
So
we
can.
We
can
breach
that
conversation
mm-hmm.
D
D
D
B
And
I,
you
know
I
know
the
rohnke
team
they're
coming
for
this
session.
This
is
what
they're
most
interested
in
or
one
of
the
things
I
know.
Probably
Doc's
will
also
be
interesting
to
them,
just
because
it's
kind
of
part
of
this
as
well.
So
you
know
I
think
that's
that's
where
they
they're
coming
for
or
what
they're
coming
for,
at
least
to
my
understanding
and
then
a
Greg.
B
If
you
will
be
participating,
you
know,
basically,
you
just
have
to
ask
the
people
and
they'll
usually
end
up
saying
yeah
it's
pretty
loose
like
we
can
change
things
around
like
we
could
do
whatever
we
need
you,
but
usually
I,
just
suggest
asking
people
if
you
want
them
to
come
and
usually,
if
you're
asking
them,
they
probably
already
want
to
come
anyway.
So
you
know
that's
a
good
good
thing
to
have
that
said.
B
B
B
C
B
Yeah
so
yeah,
that's
that
you
know,
but
their
their
context
is
also
super
helpful
in
a
few
other
areas
around
the
site,
like
you
know
how
we
were
asking
about
how
the
download
should
be
presented
like
that
kind
of
thing,.
B
D
B
B
B
B
B
E
E
Actually,
the
core,
the
core
repository
for
the
documentation
is
in
node
core.
Actually
so
the
documentation
czar
made
and
updated
up,
created
and
updated
up
at
the
node
code
repository
and
for
the
internationalization
process.
We
are
using
crowding,
actually
so
crowding
for
translating
of
the
documentation
to
various
locales.
So
we
have
actually
made
repository
actually
fetching
and
collecting
up
all
the
documentation
and
syncing
up
with
the
node
quarry
pod
story
for
documentation
for
every
minor
or
major
versions
and
later
on,
translating
them
to
the
locals.
C
Speak
to
that
a
little
bit,
so
we
I've
been
to
a
few
of
the
meetings
with
the
internationalization
team
and
can
I
get
a
good
general
understanding
of
how
the
system
set
up
and
I
think
the
goal
of
first
issue
preface
this
with
this
is
one
of
the
breakout
sessions.
We're
hoping
to
have
at
the
collaboration
is
talking
exactly
about
how
we're
ingesting
documentation
from
both
the
node
course
I'd
and
then
supplying
supplemental
documentation
on
our
side.
C
So
all
that
machinery
is
stuff
we're
gonna
figure
out
I,
hopefully
get
a
more
concrete
answer
for
you
when,
when
we
do
this
the
session
of
leverage
summit,
that
being
said,
I
think
if
any
past
conversations
are
an
indicator,
we
should
hopefully
be
ingesting.
It
rather,
as
is
the
hope,
is
I
believe
not
to
change
too
much
machinery
a
process
on
other
people's
side
and
fingers
crossed.
We
should
be
hooking
into
what
is
already
there,
not
creating
new
new
systems
that
people
have
to
learn
and
integrate
with,
but
again
we'll
we'll
be
talking.
C
B
B
C
B
And
so
that's
you
know,
that's
generally,
where
I
think
the
website
redesign
is
gonna,
be
touching
Doc's
because
you
probably
will
want
to
have
it
be
more
consistent
with
the
new
site
rather
than
the
old
site
yeah.
So
that's
that
is
one
thing
know.
One
thing
we
will
have
to
consider
is
basically
doing
progressive
enhancement
around
it
rather
than
degrading,
because
there's
a
ship
with
node
core
meaning
any
code,
we
change
will
actually
ship
with
node
core,
so
people
might
not
be
online.
B
C
B
And
so
the
those
are
still
applied
in
the
same
templates
so
technically,
like
that's
one
benefit
of
how
we're
doing
this
is
that
it
the
template,
can
change,
but
the
content
will
stay.
The
same.
That's
really
the
only
one
of
the
very
few
upsides
for
us
on
this
cool.
Does
that
did
I
enter
answer
your
question
drove
yes,.
E
Actually,
actually
awesome
that
will
figure
out
some
complete,
concrete
way
sinking
of
the
documentation
with
Internet,
internationalization
repository
or
other
stuffs
at
the
collab
submit,
but
actually
I
wanted
to
actually
would
was
curious
as
with
the
piece
of
internationalization.
Actually,
we
have
fixed.
E
Actually,
we
have
proposed
a
content
structure
for
various
major
versions
for
node
and
have
actually
collected
all
the
documentation
and
as
soon
as
we
get
a
green
flag
from
TSC
about
setting
up
the
crowd
in
so
we'll
actually
start
getting
more
collaborators
for
the
for
translation
purposes
into
locals
and
also
start
translating
documentation
into
the
targeted
languages.
So
if
actually,
there
is
some
scope
that
we
have
to
make
some
changes
in
the
content
or
directory
structure
for
the
documentation
or
anything
such
like
that.
So
we
can
make
those
changes
in
the
next
couple
of
days.
E
This
I
think
will
face
some
trouble,
getting
changes
to
the
content
structure.
So
if
there
might
be
some
major
changes
to
the
content
structure,
we
can
in
make
those
in
the
days
couple
of
days
in
the
coming
days
else,
after
even
after
collaboration
submit
I,
I
guess
with
this
pace
will
actually
start
getting
translated
documents
before
collaborate
or
submit
actually
and.
C
That's
good
so
now.
Thank
you,
I!
Don't
think
we
have
enough
concrete
information
on
how
we
any
changes
we
might
want
to
make
the
concept
structure
to
be
able
to
provide
recommendations.
Yeah,
although
I
don't
see
why
anything,
the
IANA
team
is
doing
right
now
should
have
a
huge
detrimental
effect.
What
we're
trying
to
do
so,
but
that's
good
for
us
to
keep
an
eye
on.
Thank
you
for
yeah
I.
C
B
B
B
A
So,
as
I
alluded
to
at
the
beginning,
I'm
trying
to
kick
off
an
initiative
right
now,
I'm
just
kind
of
referring
to
it
as
the
wish
list
initiative,
it's
kind
of
just
a
way
to
get
more
focused
direction
around
the
help
coming
from
volunteers
as
they
come
into
the
organization
new
contributors,
as
well
as
existing
contributors
that
are
looking
for
areas
to
help.
I
would
like
to
have
a
document
where
they
can
like
kind
of
an
entry
point
for
them
to
find
what
they'd
like
to
work
on.
A
That
specifically
outlines
specific
tasks
that
are
most
helpful
to
the
different
working
groups
and
strategic
initiatives,
etc.
So,
right
now,
I'm
still
kind
of
working
with
the
Hong
Kong
to
try
to
get
a
separate
repo
for
that,
where
eventually,
the
WGS
and
the
strategic
initiatives
will
be
able
to
just
raise
an
issue
on
that
repo
with
any
tasks
they
would
like
help
with,
but
until
I
get
that
acceptance.
I've
just
been
meeting
with
groups
in
meetings
and
leaving
issues
on
repos,
and
things
like
that.
A
So
my
main
intention
here
was
just
to
kind
of
make
my
self
known.
Just
let
you
guys
know
I'm
here
and
available
for
you
to
reach
out
to
if
you
have
any
kind
of
tasks
like
that
that
you
know
you'd
like
to
get
done,
you
just
don't,
have
the
resources
currently
and
I
can
help
drive
some
help
towards
that?
That's
why
I
got
involved
with
the
mentorship
team
specifically,
is
because
that'll
give
me
a
steady
stream
of
new
volunteers
to
direct
towards
things.
So
that's
all
the
context,
I
think
awesome.
B
Yes,
I
think
right
now
how
this,
how
this
group
is
working,
is
we're
going
through
different
stages
of
addressing
the
redesigning
the
website.
So
we
actually
just
completed
information
architecture
a
little
bit
ago
and
I
also
I
noticed
that
we
need
to
update
that
the
readme,
because
I
think
it's
pointing
to
the
previous
phase.
B
So
we
finished
information
architecture
so
like
designing
the
kind
of
structure
of
the
content,
we've
now
moved
into
design,
and
so
that's
you
know
actually
implementing
the
wireframe
that
we
have
that
that
a
debate-
and
you
know
going
through
and
applying
the
concepts
that
we've
come
up
with
to
that
design
and
producing
you,
know
the
resource
for
that
and
the
stage
after
that
will
be
technical
implementation.
So
this
is
where
things
like
you
know:
what
framework
do
we
use
if
we,
if
we
even
use
a
framework?
How
do
we
go
about
implementing
this?
B
C
D
D
Let
them
know
that
we're
progressing
stage
by
stage,
so
they
should
come
back
later
and
revisit
the
project
at
a
stage
that
they're
they're
more
comfortable
contributing
to
so
so
you
may
find
that
what
this
project
needs
now
will
be
different
from
later,
and
maybe
maybe,
if
your
visit,
if
what
you're
doing
is
visiting
every
so
often
and
waiting
for
people
to
reach
out
you'll,
find
that
we
may
reach
out
over
time
with
different
needs.
Sure.
A
Yeah
this
is,
it's
actually
gonna,
be
sort
of
a
living
document,
so
that
repo
I
referred
to
that
I'm
trying
to
get
open
would
be
a
place
for
you
guys
to
update
me
on
what
you
want
changed
like
okay.
We
don't
need
this
anymore
now.
We
need
this
that
kind
of
thing
and
also
the
mentorship
team.
Right
now
we
are
tentatively
planning
for
June
15th
to
be
our
first
like
cohort
kick-off
date
to
start
mentoring,
people
so
that
first
run
is
just
going
to
be
for
one
month
the
eventually
it'll
be
for
longer.
A
So
if
you
are
in
a
phase
where
you
have
actually
smaller
tasks
that
you
need
help
with,
that
would
be
more
convenient
for
us
right
now.
That's
what
I'm,
trying
to
gather
up
right
now
is
just
small,
like
one
month
type
things
that
people
can
work
on
during
our
trial
room,
and
we
don't
have
to
come
up
with
everything
in
this
meeting
I
like
sagging
up
in
a
issue
on
your
repo
after
the
meeting
or
however,
you'd
like
to
proceed.