►
From YouTube: Node.js Website Redesign Initiative Meeting
Description
B
Awesome,
hello,
everybody
and
thank
you
for
joining
for
another
episode
of
the
website
redesign
committee:
let's
go
around
quickly,
do
that's
like
we
always
do.
I'm
Adam
I'm,
a
software
engineer
at
LinkedIn
and
a
member
of
the
community
committee
and
co-chair
of
the
website
redesign
can
be
turning
on
ago.
Yeah.
A
C
B
Awesome
cool,
so,
let's
get
started,
we
have
a
pretty
full
agenda,
especially
if
we
spin
off
into
some
of
the
conversations
I'm
expecting
it
looks
like
website.
Wireframes
made
it
on
to
the
agenda
again.
I
think
we
just
forgot
to
take
the
label
off.
If
you
have
anything,
we
wanted
to
talk
about
I
can't.
B
Okay,
awesome,
it
looks
like
there
was
a
comment:
yeah
no
I,
don't
think
there's
anything.
Any
new
news
steps
to
discuss
here.
He'd
agreed
last
time
that
we're
moving
on
to
a
visual
design
preparing
for
visual
design.
After
this
point
and
I
think
we're
in
the
same
place
for
number
12
I.
We
just
forgot
to
remove
the
ticket
recap
from
last
time.
We
got
a
couple
over
the
last
couple
meetings.
B
B
Okay,
let's
dive
into
it,
probably
the
most
visual
thing
to
look
at
which
I
expect
us
to
kind
of
spin
off
into
a
process
talk
again
because
we're
trying
to
figure
out
exactly
how
we're
going
to
be
managing
design
contributions,
that's
where
the
conversation
left
off
last
time.
So
quick
recap
from
last
time.
This
time,
I,
remember
it.
We
we
were
discussing
I
we
wanted.
B
So
I
went
ahead
and
made
a
whole
slew
of
tickets
for
laying
the
foundation
of
a
no
js'
design
system.
So
we
can
keep
some
of
these.
So
we
can
keep
all
these
foundations
kind
of
consistent
and
we
don't
have
to
do
a
bunch
of
wrangling
work
from
people
who
want
to
contribute
more
detailed,
mocks
of
actual
pages
together.
B
So
we
have
a
project
underneath
the
org
now,
which
is
called
a
call
for
designers
roadmap,
which
I've
been
keeping
these
tickets
under.
Presumably
when
all
the
tickets
in
this
project
move
over
to
the
right-hand
column,
we'll
be
ready
for
that.
That
call
and
I
kind
of
kicked
it
off
with
the
first
design
systems,
feature
proposal,
which
will
probably
also
be
the
most
contentious
I
assume
because
it's
it's
involves
some
color
tweaks,
so
that
is
issue
number
42,
I'd
love
to
dive
in
and
start
discussion
on.
A
B
Yeah
totally
so
there's
a
medium
post
attached,
which,
with
a
lot
more
like
design,
rationale
and
nitty-gritty
how
how
this
stuff
was
made,
get
into
the
the
color
theory
and
the
science
of
it
a
little
bit
and
goes
into
the
nitty-gritty
of
like
how,
by
unifying
the
nodejs
green
color,
vertical
brand
colors
changed
just
a
a
hint
to
kind
of
make
it
all
more
cohesive
and
more
internally
consistent,
and
it
shows
it
shows
the
difference
here.
Pantone
colors
remain
the
same,
so
you
don't.
You
know
we're
not
updating
any
physical
things
or
printed
things.
B
It's
really
just
digital
assets
that
need
to
be
changed
for
the
most
part,
but
by
by
making
these
couple
small
tweaks
in
that
green
vertical
only
do
we
keep
the
nodejs
brand
consistent,
keep
saying
those
had
before,
but
it
locks
it
in
with
this
other
extended
color
palette,
which
we
can
use
for
both
website
redesign
UI
affordances.
The
badges
team
wants
to
use
this
for
creating
illustrations,
spec
and
badges
spec
and
having
more
colors
and
more
emotions
at
our
disposal,
but
because
of
my
approach
to
this
proposal,
there's
a
few
outstanding
questions.
B
Still,
the
first
of
which
will
actually
extend
to
any
foundation
like
how
do
we
leave
this
working
group
in
the
the
Comicon
as
a
whole
and
and
if
needed,
the
foundation
itself?
What's
the
process
for
approving
these
things,
I
we
make
these
kind
of
foundational
like
this
is
node
brand
design
guideline.
How
do
we?
How
do
we
institutionalize
that
question?
B
Apache
2
license
design
system
library
I,
as
it
kind
of
lays
the
foundation
for
the
rationale
and
the
the
extra
color
verticals
and
then
question
number
four:
it's
just
what
do
we
think
about
the
extended
color
palette
we
like
it
is
going
to
pursue?
Is
it
something
we
feel
like
we're,
gonna
need
long
term
and
yeah.
So
that's
that's
kind
of
the
conversation
I'd
like
to
have
around
color
palette
specifically
and,
as
we
start
pursuing
these
design
systems
tickets
as
a
whole.
How
do
we
want
to
structure
the
conversation
awesome.
A
G
Now
so
mmm-hmm
I
guess
one
of
the
brand
document
on
the
brand
changes.
Ideally
I
think
maybe
just
asked
to
join
the
marketing
committee
meeting
and
see
and
just
propose
what
you
want
to
change.
I,
don't
know.
Are
you
talking
about
like
colors
in
the
fonts
as
long
as
the
logo
is
consistent,
mm-hmm
I,
don't
think
it's
a
big
deal.
B
Yeah,
there's
no
there's
no
design
changes
in
the
logo
itself.
Really,
the
only
changes
being
proposed
are
slight
changes.
Those
three
greens
I
click
on
the
medium
article
in
the
in
ticket
number
42,
and
it
provides
a
lot
of
rationale
and
why
these
changes
are
needed
to
kind
of
make
the
nodejs
improve
the
nodejs
friend
as
a
whole.
I.
G
G
A
Sorry
sorry
mark
I
was
just
I.
Do
think
that
we
are
kind
of
proposing
a
little
bit
of
a
tweak
to
the
nodejs
logo
itself
and
it's
literally
like
the
underlying
hex
of
exodus
of
all
colors.
That
consists
that
it
is
like
the
structure,
isn't
gonna
change.
It's
just
gonna
be
slight
like
tweaks
to
make
it
consistent
to
an
actual
color
system
and
I
understand
it.
Like
anna
has
put
a
lot
of
work
into
this.
It
is
also
technically
employed
by
a
foundation
member.
A
Imagine
if
he
presented
this,
the
Marketing
Committee
and
full
disclosure
forever
here.
I've
sat
on
the
marketing
committee
for
a
while
I've
helped
out
there
I've
commented
and
you
know,
but
we
do
stuff
there
pretty
frequently
if
he
brought
this
there
I,
don't
imagine
that
there
would
be
a
lot
of
contention
around
them
saying
let
no,
let's
keep
it
inconsistent
rather
than
have
you
know
a
well-thought-out
design
system.
Well,
let's.
G
Just
just
to
go
back,
we
have
a
trademark
that
is
granted
to
us
by
Joya
and
we've
established
this
as
a
trademark.
So
when
you
change
that
stuff,
it
could
potentially
change
our
trademark,
which
are
it's
becomes
an
additional
trademark.
I,
don't
know
if
it's
a
I
have
to
check
the
details
on
that.
So.
G
B
B
I
the
like
I
guess,
like
like
I,
said
before
the
the
logo
itself,
the
recommended
Pantone
colors
for
when
you're
going
and
making
a
print
version
of
the
logo,
don't
change
because
the
the
changes
in
tint
you
are
just
really
slight,
so
that
what
used
in
conjunction
with
with
the
rest
of
the
colour
system,
it
really
just
locks
in
the
the
three
main
brand
colors
themselves.
I
do
ramp
a
little
nicer,
I
internally
with
themselves,
and
it
actually
improves
kind
of
the.
B
Structural
integrity
for
lack
of
a
better
word
of
the
logo
itself,
but
the
colour
changes
are
so
slight
that
unless
you
have
a
really
close
eye
for
design,
you're-
probably
not
going
to
notice
it.
Unless
it's
explicitly
pointed
out
to
you.
So
it's
probably
something
that
we
can.
We
can
work
towards
institutionalizing
without
blocking
on
it,
but
I
think
we
should
definitely
start
the
conversation.
G
B
A
G
B
If
you
look
at
the
it
really
shows
in
the
the
hexagons
gradient
right
in
the
middle
of
the
or
the
previous
version,
it
gets
really
muddy,
and
that's
because
the
the
hues
between
the
two
greens
that
it's
it's
grading
between
technically
transition
pretty
drastically,
and
so
as
it
starts
going
as
it
starts,
starts
transitioning.
It
starts
to
get
muddy
in
the
middle,
whereas
the
updated
version
to
keep
some
more
smooth
and
and
solid
look.
B
G
Blow
it
up,
it's,
let's
not
get
too
deep
into
it,
because
maybe
it's
not
the
idea.
I
just
want
to
make
sure
that
that
if
we
update
it
we
don't
and
we
do
the
correct
things
so
that
we
don't
validate
or
any
trademarks.
Definitely
I
hundred
a
degree
of
that
I,
don't
I
mean
I,
don't
see
a
big
problem
and
changing
it.
If
that
and
none
of
us
are
lawyers
and.
B
B
A
B
All
these
design
systems
features
to
really
be
be
fleshed
out
and
stuck
into
a
single
packet
like
we
had
discussed
before
to
hand
off
to
any
designers
that
that
need
that
and
I
think
at
least
for
for
things
that
don't
affect
brand
or
color,
which
I
think
color
extend
the
color
palette,
be
the
only
one.
We
can
probably
make
that
choice
internally
here
on
the
website.
Redesign
committee
I
does
that?
Does
that
sound
like.
C
Before
we
finally
go
into
implementation
or
asking
for
help
so
whoever's
coming
on
unprotected
p.m.
assistance
or
from
the
community
aspect
of
things
already
knows
what
we
want
to
work
it
and
like
have
an
idea
what
we
actually
want
them
to
work
on.
So
I
actually
think
we
should
have
a
demo,
probably
at
the
end
of
the
month,
on
nest
weeks.
Whenever,
before
we
go
home,
it's
asking
for
more
help
and
a
demo
of
what
specifically.
C
B
Yeah
I
love
so,
regardless
of
what
we
make
for
these,
these
foundational
things
I'd
love
like.
Maybe
not
this
level
of
detail
for
the
color
changes,
but
at
least
like
a
visual
demo,
of
what
we're
expecting
from
these
Design
Systems
foundations
and
I.
Think
that's
the
best
possible
way.
We
can
help
keep
consistency,
as
we
start
enlisting
community
members
for
more
detailed
designs.
So
setting
that
standard
of
of
what
level
of
detail
we
go
into
now
will
help
us
immensely
down
the
line.
Tierney
welcome
back.
Thank.
A
B
A
What
I
was
what
I
was
trying
to
say
about
that
first
bullet
point
in
there?
Let
me
get
back
to
that.
Was
that
I
don't
necessarily
know
if
we
need
to
go
down
the
path
of
like
bringing
it
to
the
foundation.
It's
more
of
an
implementation
thing
on
our
side
and
like
Mark
was
saying:
I,
don't
know.
If
we
like
it
changes,
the
website
can
be.
Did
the
foundation
website
rather
can
be
done.
A
You
know
going
down
line
that
shouldn't
be
too
big
of
an
issue
hopefully,
but
like
getting
this
in,
you
know,
push
through
I
think
we
just
need
to
get
buy-in
from
the
project
more
broadly
and
I
definitely
do
think
it
would
be
helpful
to
present
it
to
the
and
share
this
context
with
the
the
marketing
committee.
Just
so
they
can
have
context.
A
I'ma,
cuz
I
think
they
appreciate
that
we're
doing
some
of
this
work,
but
you
know
III
do
think
that
we
want
to
just
get
buy-in
from
the
project,
because
that's
generally,
where
I've
seen
the
most
concern
about
things
like
this
is
just
that
they
wondered.
People
want
to
have
a
voice
and
they
wanted
to
say
you
know
they
want
to
make
their
own
tweaks
and
people
have
opinions.
I
I,
don't
think
we're
gonna
get
a
ton
of
negative
input.
A
B
B
A
The
nodejs
started
work
website,
so
you
know
I,
don't
think
we'll
need
to
go
through
that
same
level
process,
but
this
is
adding
in
a
bunch
of
new
things
that
honestly
I
think
is
a
really
good
foundation
for
us,
and
so
people
would
just
want
to
kind
of
have
their
say
and
and
be
able
to
kind
of
give
their
input
on
it
as
well,
but
like
line-height
stuff
for
now
yeah.
We
don't
end
this.
B
Turn
people's
I
do
to
website
redesign
so
sort
of
website
specific
things
if
they're
they
want
to
be
engaged
with
that
they'll
they'll
know
what's
happening
after
we
have
level
of
this
as
well,
so
cool
I
think
that's
kind
of
the
direction
the
conversation
was
headed
while
you
were
offline
as
well.
So
it's
does
anybody
feel
differently,
or
do
we
kind
of
have
consensus
about
how
we
think
that'll
go.
E
Sweet,
okay,
hey
Adam,
actually
I
wanted
to
add
something
like
for
the
typography
iconography
grid
system,
color
system,
any
any
of
the
design
process
or
some
process
that
we'll
be
introducing
and
implementing
of
in
the
new
website.
Coming
up.
So
can
we
or
can
community
committee
can
introduce
or
initiate
some
sub
projects
and
little
open-source
projects
under
nosiest
foundation
about
like
a
photo
version
either
the
4k
version
version
of
the
open-source
project
or
open
source?
E
E
So
so
that
will
be
like
something
that
we
can
get
some
native
feeling
about
design
things
and
other
stuffs.
Actually,
like
I
haven't
read
all
those
proposals
have
you
made
in
the
last
two
days
like
I
was
having
exam
today,
so
I
will
go
through
them
and
also
proposing
a
little
idea
to
the
community
committee
about
introducing
some
little
or
tiny
projects
about
initiating
such
open
source
projects
and
the
nosiest
foundation
itself.
Yeah.
B
B
It
makes
sense
to
manage
that
locally,
like
like
what
happened
with
these,
these
color
verticals
that
we
use
as
a
foundation
or
this
color
system
proposal
from
mineral
UI
for
things
like
font
awesome,
if
we're
saying
use
font
awesome,
let's
just
point
to
their
website,
I,
don't
think
there's
as
much
value
in
pulling
it
in
under
the
nodejs
project
itself,
but
I
do
think.
There's
a
great
opportunity
here
to
spin
out
the
Design
Systems
guidance
into
its
own
repo.
B
At
some
point,
once
website
redesign
feels
like
it's
in
a
mature
State
but
I
think
for
now.
Let's,
let's
definitely
incubate
it
here
in
this
project,
and
we
can.
We
can
move
it
to
a
more
dedicated
central
location
after
its
mature
and
I.
Think
we'll
just
need
to
use
our
discretion
or
when
an
itch
we-we-we
fork
project,
so
we
fork
documentation
or
if
we
just
point
to
the
original
websites
and
say
you
use
that
that's
our
standard
I
will
want
me
to
make
that
call
like.
E
We
are
very
limited
to
the
though
they
are
having
a
very
large
number
of
icons,
but
we
are
limited
to
the
icons
they
do
offer,
but
before
node.js
like
we
can
have
more
icons
being
built
by
our
designers
or
people
involved
in
the
I.
Can
project
iconography
project
so
that
we
can
have
more
control
over
the
different
stuffs
or
projects.
I.
Think.
A
We've
definitely
taken
the
approach
of
doing
things
ourselves,
the
first
time
or
you
know
maintaining
things
ourselves,
and
you
know
what
I've
found
is
that
we
are
we
we
have
more
success.
Would
we
are
additive
to
projects
or
others,
because
it
enables
those
others
to
come
and
kind
of
contribute
to
us
and
also
like?
If
we
need
extra
icons,
we
can
do
additional
icons
on
top
of
whatever
system
we
choose,
like.
That's,
that's
less
maintenance
burden
for
us,
because
we
actually
have
you
know
a
pretty
extensive.
A
Like
you
know,
this
is
just
under
the
assumptions
that
we
go
with
font
awesome,
which
I
not
actually
asserting
that
we're
going
to
do
that.
But
you
know,
under
the
assumption
that
we
won't
was
fun
on
to
some.
If
there
was
an
icon
that
we
needed
that
wasn't
in
there
less
standard
library,
we
could,
you
know,
go
ahead
and
build
that
into
its
own
repository
in
our
in
our
organization,
but
going
through
and
duplicating
a
lot
of
the
work
like
Adam
was
saying
is
a
very
heavy
maintenance
burden
and
what
I
would
I
guess?
A
The
main
thing
I've
seen
she
says.
Success
with
for
us
is
reducing
maintenance
burden
as
much
as
humanly
possible
and
there-
and
you
know
these
other
things-
are
already
doing
so
much
to
maintain
themselves.
It's
kind
of
you
know
similar
to
going
out
and
rebuilding
an
ojs
that
we
have
a
lot
of
people
who
do
this
and
just
like
they
do
and
I
think
it's
good
to
be
additive
to
them
and
which
also
supports
those
projects
and
lifts
them
up.
A
You
know,
as
you
know,
we're
all
in
nodejs
right
now
we're
all
working
on
this
I.
Don't
it's
hard
for
us
to
realize.
Sometimes
how
important
buy-in
from
the
nodejs
project
is
to
people.
It
really
does
mean
a
lot,
and
you
know
having
that
support.
You
know
for
us:
it's
not
really
support
we're
using
a
library
that
they're
building
and
we're.
You
know
very
appreciative
of
that,
but
having
that
recognition
for
work
that
others
are
doing
is
actually
really
beneficial
for
their
ecosystem
as
a
whole.
A
A
It
will
vary
greatly
depending
on
what
we
end
up
doing
and
each
of
those
every
approach
that
there
is
there's
already
quite
a
bit
of
prior
art
and
quite
a
bit
of
work.
That's
been
done
to
make
sure
it's
highly
usable
and
accessible
in
ways
that
we
wouldn't
even
consider
at
this
point
and
that
will
reproduce
again
our
maintenance,
but
in
the
long
run.
C
That's,
we
might
probably
have
a
lot
of
stability
now,
so
it
magining
feelings
like
create
an
internal
Twitter
bootstrap.
All
the
way
game
part
also
so
be
lots
of
work
and
knowing
full
well
that
everybody
here
is
a
volunteer
and
being
probably
be
working
on.
At
the
same
time,
while
working
on
things,
we
still
have
to
consider
the
work
that
we
should
leverage
other
open-source
projects
like
consider
in
Aikido,
so
it's
in
starts.
C
We
also
encourage
open
source
community,
also
encourage
them
by
leveraging
some
of
the
ratios
or
already
are
there,
which
nevertheless
George
I
Gary
is
not
really
bad.
Maybe,
as
the
project
goes
on,
where
we
start
saying
that
we
can't
make
use
of
this
anymore,
then
we
can
encourage
the
use
creating
our
own
resources.
Further
I
was
still
in
Korea.
It
was
like
having
markdown
on
design
concept
where
people
don't
contributing.
So
sorry,
we
contribute
in
traverse
we're
contributing
on
the
projects.
Canned
boo,
true,
like
the
mcdonald
occu
mentation,
on
design
concepts
in
general.
C
If
anybody
will
love
to
contribute
to
this
project,
these
are
the
resources
we
make
use
of.
These
are
the
things
that
should
be
your
guidelines
for
contributing
to
the
project.
Nevertheless,
we
still
how
to
make
use
of
things
that
are
already
existing
to
reduce
the
load
of
maintenance
like
air
inside
so
I
think
it
is
nice
boots
for
now.
C
B
B
B
This
is
for
our
in-person
meeting
coming
up
pretty
soon
we're
we're
I
think
hoping
that,
at
least
in
my
mind,
I
I.
Remember
the
discussion
leading
off
with
us
wanting
to
knock
out
a
lot
of
content.
It's
kind
of
oh,
do
people
have
the
same
impression
from
the
last
conversation
we
had
and
what
do
you
think
we
should
be
doing
at
the
collapse
of
it?
That.
A
Is
definitely
that's
what
my
impression
was
as
well:
I
forgot
until
you
just
so
I'm
glad
she
said
it.
That
said,
I
would
also
like
to
offer
up
something
else
that
happened
to
build
so,
and
this
is
I,
don't
wanna
I,
don't
want
to
get
distracted
off
of
this
subject
really
kind
of
is
tangentially
related
to
something
else.
I
wanted
to
talk
about
I,
don't
to
get
to
Tianjin,
so
actually
I'll
say
this
till
the
end
and
others
can
can
hop
in
with
other
things.
They
want
to
discuss
or
work
on
it.
Build
okay,.
B
D
A
I'd
also
like
to
add
to
that
that
actually
I
at
build
I
had
had
a
few
discussions
about
docks
and
I.
Do
think
that
that's
gonna
be
something
that
we're
gonna
have
to
solve
and
like
we're,
gonna
have
to
figure
out
how
we're
gonna
be
able
to
interface
with
node
core
and
the
docks
there,
and
also
it
completely
change
the
design,
because
we
are
gonna
want
to
have
it
be
consistent
in
some
way
or
another,
and
it's
also
gonna
have
to
be
consistent
without
the
rest
of
the
website,
because
it's
actually
bundled
into
node
core.
A
So
the
talks
are
available
for
users
there,
and
also
making
that
accessible
would
be
fantastic,
I,
don't
think
it's
accessible
at
all
right
now,
so
that
would
be.
You
know
another
awesome
step,
but
with
that
I
I
do
think
that
we
we
are
gonna,
have
to
hash
a
lot
of
things
around.
How
we're
gonna
be
able
to
do
this,
and
the
collaborator
summit
is
gonna,
be
a
really
good
place
for
that,
because
there
will
be
people
who
care
about
docs
in
core
there
as
well
and
who
have
been
maintaining
the
docs
in
core.
A
So
that
might
be
a
good
time
to
do
it
on
top
of
a
website
redesign
session,
but
I
do
think
it
would
be
extremely
useful
for
us
to
be
involved
in
that
discussion.
You
know
in
the
law
in
the
that
group,
because
you
know
like
I
would
really
really
really
love
to
include.
You
know
Runk
it
in
the
way
that
they
demoed
with
the
buffer.
E
A
B
B
Think
the
ideal,
the
ideal
is
we,
we
change
the
TLC's
process
as
little
as
possible.
So
sorry
I'm
getting
a
spam
phone
call
there.
We
changed
the
TF
C's
process
as
little
as
possible
and
have
them
hopefully
still
work
in
markdown
and
we
do
whatever
is
needed
on
the
build
side
or
the
website
to
yeah
hammer
it
into
the
shape
we
need
and.
D
I
guess
another
thing
is
who
exactly?
But
if
you
just
turn
off
JavaScript
on
those
pages,
you'll
actually
see
like
the
degradation
experience
and
it's
it's
essentially
the
same
as
what
you
would
get
today,
which
is
examples
that
just
don't
run
but
like
the
D
style
itself
and
everything
remains
the
same.
B
I
actually
ran
into
that
because
the
for
some
reason
the
LinkedIn
I,
was
on
the
LinkedIn
network
when
I
was
when
that
demo
was
going
on
and
for
some
reason
then
was
was
blocking
the
run.
Kitt
J
s
from
loading
I
need
to
talk
to
our
IT
department
about
that,
but
I
could
still
see
the
examples
clearly
and
read
them
just
fine.
So
it
was
a
good
fallback
experience
going
back
to
what
are
the
priorities
of
getting
started
doc
the
getting
started
section,
the
docs
Nick
the
whole
getting
started
experience.
We
had
a
suggestion.
B
I
can't
find
the
ticket
I
believe
it
was
about
who
recommended
it,
and
it's
been
brought
up
a
couple
times
now.
Creating
user
personas
or
who
are
target
target
audiences
are
I
think
might
help
a
lot
as
we
draft
content
on
location
at
the
the
collaborator
summit,
and
it
might
be
good
to
come
in
with
a
with
a
proposal
for
that.
So
when
we
sit
down
at
the
table
with
with
all
these
other
contributors
who
might
not
have
been
involved
in
these
meetings,
we
can
say
here's
who
we
think
we're
writing
for.
D
Yeah
definitely
and
I
mean
the
stuff
we've
been
talking
about
in
particular
that
we
think
would
be
really
cool
and
kind
of
really
different
than
the
things
we've
seen
before
is
which
I
think
goes
hand
in
hand
with
accessibility
is
localization
of
the
docks,
including
the
example.
So
like
it,
it's
just
really
unfortunate.
D
That
I
mean
you
know,
step.
One
is
certainly
like
the
surrounding
text
might
be
localized
in
your
language,
but
then
you
get
to
the
code
itself
and
all
the
comments
in
the
code
are,
of
course,
in
English,
right
and
it'd
be
really
nice
to
have
like
an
actual
Spanish
experience
or
Portuguese
experience,
or
something
like
that.
So
yeah.
A
B
He's
been
leading
that
initiative
and
it's
is
really
pushing
to
get
a
good
international
experience
for
both
our
encode
documentation.
I,
believe
the
comment,
the
code
comments
and
pretty
soon
the
getting
started,
content
and
all
the
text
content
on
the
website.
Once
we
once
we
integrate
awesome,
so
I'd
love
I,
believe
there
was
a
recommendation
that
we
we
partner
with
with
Ben
or
at
least
to
do
a
joint
session
for
describing
both
what's
going
on
with
website
content,
internationalization
and
possibly
how
work
we're
planning
on
integrating
I'd
like
to
explore
that
more.
B
F
B
Cool
we
have
10
minutes
left,
so
I
know
tyranny.
You
wanted
to
bring
up
one
more
thing
at
the
end,
I
and
so
I'd
like
to
switch
gears
and
hopefully
get
a
quick
consensus
on
meeting
time
before
diving
into
into
your
last
thing.
Reading.
So,
as
has
been
said
multiple
times
in
history,
you're
now
experiencing
7
a.m.
is
really
the
early.
It's.
B
A
B
Like
well
notes
been
making
me
become
a
morning
person,
it's
it's
really
weird
for
me
too,
but
there's
there's
general
want
to
push
this
back
by
at
least
an
hour.
This
meeting
time.
I
know
people
are
in
different
time
zones
and
I
wanted
to
to
make
sure
that
before
we
just
go
and
make
the
choice
to
do
that
that
we're
not
messing
with
anybody
else's
schedule
and
that
everybody
who's
currently
active
and
engaging
with
this
working
group
would
still
be
able
to
make
it
if
it
was
pushed
back
by
an
hour
at
least
I
will.
A
Say
one
hour:
I
would
block
both
myself
and
Mark
Hinkel,
there's
a
weekly
nodejs
certification
meeting
that
happened.
So
you
know
the
certification
project,
that's
completely
outside
of
node
core
and
all
that
stuff.
It's
a
foundation
that
happens
starting
in
five
minutes,
so
that
would
block
myself
and
Mark.
From
joining
this,
the
first
women.
B
Yeah
I
I
would
basically
just
force
us
to
to
skip
a
meeting
if
we,
if
we
don't
or
find
a
different
we've.
C
A
A
So
you
know
one
of
the
things
I
was
discussing
this
James
style
is
that
you
know
it's.
We
he's
been
he's
been
through
the
process
of
design
by
committee
three
times
as
well
with
with
ijs
and
and
nodejs,
and
then
our
Jessica
or
well
the
website
and
then
two
logos,
and
you
know
it's
always
been
a
struggle
and
what
one
thing
we
were
talking
about.
A
Is
that
actually
there's
you
know
corporate
members
who
have
designers,
and
so
you
know
he
actually
said
that
they
have
near
form
itself,
has
a
few
designers
who
are
new
to
the
team
and
he
vouch
for
their
skill.
You
know
new
to
the
team
and
willing
their
they're
opening
up
soon
and
your
form
is
very
generous
with
their
resources
for
noches
and
he
said
that
they
would
possibly
be
able
to
help
out.
A
So
you
know
that
kind
of
sparked
the
idea
of
okay.
Well,
if
you
know
we
can't,
if
we're
not
gonna,
be
able
to
do
this
easily
with
design.
You
know
open
source,
community
members
and
yeah,
that's
still
TBD
I,
don't
know
if
that's
gonna
be
the
case
or
not.
That
is
another
fallback
that
we
can
go
to
is
reaching
out
to
corporate
members.
You
know,
as
we
were
discussing
earlier,
there's
a
marketing
committee
meeting.
A
Just
because
you
know
it's
it's
kind
of
a
little
bit
incentivized,
but
then
we
also
have
you
know
a
dedicated,
a
reason
for
them
to
kind
of
continue
to
participate
and
it'll
be
able
to
be
part
of
their
work
scope.
Hopefully,
so
that's
just
something
I
wanted
to
offer
up
and
I
was
you
know
the
reason
I
was
counting
it
in
about
specifically
about
build
or
about
not
build
that
Jess
coffee
you
was
that
there
might
be
a
possibility,
was
getting
you
know
the
near
form
designer
out
to
do
that.
A
So
I
would
have
to
talk
to
James
about
that,
but
you
know
I
I'm
happy
to
kind
of
bring
that
up
and
see
if
that's
gonna
be
helpful
or
not
a
possibility.
I.
D
Just
wanted
to
chime
in
it's
funny.
You
mention
this
because
so
I
don't
know
you
guys
know,
but
run
kit
is
owned
by
stripe
and
I
had
run
by
them
a
couple
weeks
ago,
if
like
we
could
make
like
an
arguable,
quote-unquote
donation
to
the
nodejs
Foundation
through
stripe,
design
resources
and
they
seemed
relatively
open
to
that
so
I
guess
we'll
throw
our
hat
in
but
like
if
there's
other
people
that
like
really
want
to
do
it.
That's
fine
like
it's
not
like
something
we
are
crazy,
pushing
for
or
anything
just.
D
A
Know
I
think
if
you're,
if
that
is
available,
I
think
you
like,
if,
if
that's
definitely
doable
or
possible,
I,
don't
think
we
should
say
no
like
I,
think
it's
more
of
a
first-come,
first-serve
and
James
was
like
they.
They
will
be
available
in
the
future
they're
relatively
soon,
but
not
not
now,
so
you
know
if
that's
doable,
if
that's
possible,
if
that's
available,
you
know
I
definitely
think,
there's
not
a
reason
to
say
no
did
I
yeah.
D
I
can
follow
up
offline,
I
guess
I
mean
my
own
I
think
we'd
actually
be
more
available
sooner
rather
than
later.
Just
given
our
timeline
I
would
be
curious,
just
given
the
fact
that
using
the
resources,
if
like
we,
would
have
like
a
specific
timeline
for
them
like
oh,
we
would
want.
You
know
from
the
big
four
mid-may
to
the
end
of
August
or
whatever
we
think
it'll
take
its.
If
that's
something
we
think
would
be
doable
like
having
that
kind
of
a
deadline
that
sort
of
thing
yeah.
B
B
The
project
forward
in
a
cohesive
way
so
anytime
that
can
be,
can
be
donated
by
any
group
like
that's
that's
for
for
us
to
appreciate
and
then
manage
appropriately
so
Francisco.
If,
if
that
that
timeline
you
just
gave
of
mid
May
to
August
is,
could
be
a
concrete
proposal,
I'd
say:
let's:
let's
do
it
yeah.
D
I'm,
actually
so
I'll
be
we
go
to
like
stripe
office,
it's
like
once
a
week.
This
is
my
stripe
day
today,
I
guess
it's
good.
We
talked
about
this
I'll
go
and
try
to
get
something
like
this
is
what
we
can
absolutely
concrete
offer,
and
then
you
know
just
wait
for
if
that
works,
for
you
or
if
you
were
like.
D
A
Amazing
I
will
say:
I
Pro,
I,
probably
don't
think
we're
gonna
come
back.
Saying:
oh
I
hope
we
wish
it
was
longer
or
you
know,
I
I.
We
were
hoping
for
a
bit
longer.
I,
don't
think
we're.
Probably
gonna
come
back
with
that.
But
you
know
the
contribution
is
extremely
valuable
and
we
really
do
appreciate
you.
You
know
stepping
it
off
for
this
research,
yeah
yeah.
B
Yeah
there
are
no
shortage
of
design
tasks
and
we'll
we'll
we'll
find
a
way
to
use
any
resources
that
are
better
offered.
That's
for
sure,
cool.
B
So
the
that's
something
that
this
this
group
gets
to
figure
out
as
a
whole,
how
to
manage
I
started
to
go
down
that
path
by
there's
a
there's,
a
projects,
tab
on
the
repo
and
there's
a
there's.
A
new
project
open
called
the
call
for
designers,
roadmap
and
I'm,
hoping
to
keep
all
design
related
and
design
process
related
tickets
here
anything
that
we
need
help
with.
They
say
well
want
it.
Now.
That's
all
there's
focus
stuff
because
we're
working
towards
being
able
to
have
the
open
call
for
hey.
B
We
need
people
to
do
high
fidelity
mocks
of
like
actual
pages
on
the
web
proposed
website
to
them,
propose
and
bring
to
a
discussion
here
and
and
go
through
a
couple
iterations
on,
but
we're
laying
the
design
groundwork,
and
we
certainly
need
designers
to
help
with
that.
So
like
coming
up
with
figuring
out
what
our
iconography
spec
is
and
getting
that
laid
out
figure
out
what
our
typography
spec
is
and
that
worked
out.
B
We're
gonna
need
probably
stuff
for
elevations,
so
that
are,
you
know,
any
drop
shadows
we
make
or
consistent,
and
it's
really
just
design
choices
that
needs
to
be
made
and
documented.
But
that's
that's.
Certainly
the
design
work
we're
doing
at
the
moment
I
think
it's
a
little
bit
early
to
get
people
to
do.