►
A
Live
now
hi
everyone
so
welcome
to
the
August
third
meeting
for
the
node.js
foundation
community
committee.
We
have
a
couple
items
on
the
agenda
to
go
through
today,
but
first
I'd
like
to
just
kind
of
go
around.
Do
some
introductions
for
everyone
is
here
since
I
know
it
could
be
hard
to
figure
out
who's
talking.
My
name
is
Brian
Hughes
I'm,
the
chairperson
of
the
community
committee,
and
on
github.
My
handle
is
never
yes,
Olivia.
B
E
H
H
A
A
All
right
welcome
everyone
to
the
meeting,
so
we
have
a
three
items
on
the
agenda
today.
The
first
thing
I
want
to
talk
about.
This
is
just
actually
more
per
reminder,
but
this
issue,
number
89
we've
had
some
discussions
online
about
creating
an
email
alias
for
the
community
committee.
This
would
basically
put
a
security
with
the
TSC
DCTC
and
a
few
other
groups.
A
So
at
this
point,
I
think
it
looks
like
we
had
consensus
on
this,
but
the
thing
that
we
need
is
everyone's
actual
email
address.
So,
if
you
all
could
everyone
who
is
a
member,
please
go
to
issue
89
and
I'll?
Let
us
know
which
email
address
you
would
prefer
that
we
use
for
this,
but
it
will
also
go
on
the
website,
so
make
sure
it's
an
email
address
that
you
are
comfortable
having
published
publicly
if
you're,
not
comfortable,
publishing
your
email.
Just
publicly
then
chat
with
me
and
we'll
see
any
comments.
Questions
about
that.
J
J
A
J
B
So
can
I
just
add
something
to
this
mm-hmm,
so
I
think
there's
an
issue
for
this.
Yeah
I
made
an
issue
a
couple
of
weeks
ago
calling
to
list
members
emails
in
in
the
readme
just
like
the
TSE
does
it
just
for
you
know
conforming
to
that
sort
of
standard
and
I
think
like
if
we
have
all
the
email
addresses
and
if
everyone's
okay
with
having
public
anyways
you
might
as
well,
do
this
in
one
sort
of
fell
swoop,
I,
guess
just
a
idea.
Maybe.
A
I
A
I
Awesome
I
have
no
issue
with
you
whatsoever
like
backing
you
down
in
public
record
you're
awesome
having
one
person
for
whom
people
can
contact
always
makes
me
a
bit
leery
or
like
it
makes
you
feel
like
it's
possible
for
that
to
be
abused
again.
I,
don't
suspect
this
happening
to
you
at
all,
but
the
way
this
call
was
set
up
and
then
just
now
it
happened
again
for
this
issue.
You
said
like
email
me
or
message
me.
D
K
J
Go
to
Brian
right,
so
they
coordinate
with
Brian
and
Brian,
is
or
Brian
make
sure
that
the
directors
know
what
they
need
to
be
requesting
at
the
board
meetings
that
that
needs
to
happen,
and
so
we
should
probably
document
this
better
so
that
people
understand
that
as
well
as
for
the
meeting
itself,
yeah
I
mean
having
one
person
coordinating
that
it's
tough
and
it's
because
we're
having
this
problem
around
the
technology
itself,
so
we're
getting
too
big
for
our
britches.
So
I
did
want
to
say
that
we
are
approached
we
are.
J
That's
documented.
It
also
is
a
problem
that
right,
that's
exactly
what
I
was
getting
to
was
that
we
don't
have
a
private
repo
for
for
calm,
calm,
and
because
of
that
there
is
private
information
that
we
do
need
to
share
around.
You
know
sort
of
admin
or
ops
work,
so
that's
something
that
we're
also
going
to
have
to
address
I.
Don't
think
we
need
to
do
that
in
the
meeting
today,
but.
H
J
C
The
TSC
and
ctcf
and
historically
essentially
fixed
this
by
using
the
email,
alias
that
we
have
for
those
which
we
I
suppose
just
discussed
here,
which
I
do
have
a
question
about.
If
that's,
okay,
yeah,
are
you
sitting
that
up
in
just
the
node.js
or
whatever
they
sort
of
email
forward
or
is
there
or
are
you
setting
it
up
under
the
sort
of
automatically
for
configurable
IO
Jess,
one
on
the
repo
on
the
you.
J
Know
the
instruction
that
I
was
given
that
I
may
need
help
on
was
that
I
am
to
create
a
couple
aliases,
and
one
of
them,
of
course,
is
to
help
with
the
the
existing
aliases
that
also
create
a
new
one
for
the
community
committee,
but
that
it
would
be
much
easier
if
I,
actually
just
visit
forwarded
to
the
existing
I/o.
So
everyone
like
the
people
there
would
be
an
at
nodejs
org,
but
it's
not
going
to
like
you
serve
by
ojs
dot
org,
because
that's
already
managed
elsewhere.
C
A
A
All
right,
the
next
one-
this
is
issue
number
95,
invite
interested
website
working
through
the
next
comic-con
meeting.
It's
the
title
of
this
issue,
but
really
I
wanted
to
use
this
as
a
chance
for
us
to
coordinate
on
some
website
efforts
and
see
how
the
website
working
group
and
a
calm
calm
can
work
together.
D
Yes,
if
I
can
unmute
there,
you
go
okay.
So
the
reason
this
kind
of
got
brought
up
in
itial
II
was
because
of
work
that
you
know
originally
got
started
by
Michael
and
I.
Believe
I,
don't
know
how
to
pronounce
his
last
name.
I'll
say
it
just
say
it
first
name
Leo
over
at
site
to
create
a
new
design
for
the
present
ojs
website.
This
is
something
that
I've
tried
to
prioritize
along
for
a
long
time
and
try
to
help
along
and
I'm
pretty
passionate
about,
but
I
know.
Also.
You
know.
D
You
know
I'm
gonna,
make
sure
that
we
kind
of
connect
the
dots
and
with
either
Leo
or
kind
of
stepping
forward
and
just
figure
out
what
our
next
steps
are.
I've
had
discussions
with
a
few
members
of
the
website
working
group
and
III,
the
general
kind
of
idea,
I've
gotten,
is
that
the
design
is
the
hard
part,
and
you
know
implementation
is
the
part
we
can
definitely
do
so.
D
You
know
I
just
kind
of
wanted
to
bring
definitely
I'm
excited
to
have
everyone
here
and
be
able
to
talk
to
you
all
about
how
we
can
kind
of
proceed
with
this.
One
note
I
did
want
to
share.
Is
that
Leo
actually
did
say
you
know
the
project
that
projects
that
were
blocking
him
are
finally
over,
so
he
he
he
and
I.
Don't
I,
don't
believe
is
that
his
name
is
published
either,
but
evil
rabbit
are
both.
You
know
free
and
have
some
cycles
to
do
this.
K
This
has
been
going
on
for
quite
some
time
and
we
have
issues
coming
in
like
oh,
we
should
work
on
the
download
page
or
on
the
home
page
and
we
have
to
say:
okay,
people
we're
working
on
a
redesign
and
it's
been
I
think
over
a
year
now
and
yeah
for
us
it's
hard
to
yea
deal
with
the
kind
of
issues.
So
should
we
just
go
ahead
and
change
something
on
the
page
or
wait
for
the
redesign
or
to
get
some
feedback
where
leo
is
actually
standing?
D
H
D
B
So
flowers
I
remember
when
I
was
still
like
in
the
work
in
the
web
site
working
group.
There
wasn't
issue
I
think
on
the
on
the
website
working
group
somewhere,
where
Leo
posted
a
couple
of
like
really
like
early
design,
iterations
and
asked
like
the
website
folks
for
their
input
on
it.
But
I
think
that
was
the
that's
been
done
on
any
redesign.
J
Yeah
I
just
I
kind
of
wonder
if
we're
at
a
point
with
the
redesign
where,
like
I
wonder
if
it's
been
long
enough,
if
we
need
to
have
another
around,
how
can
we
iterate
on
this
for
the
needs
that
we
need
now
because
I
still
think
I?
Was
there
a
content
management
system
of
any
sort?
As
note
of
that,
okay
and
then
also
like
I,
don't
know
how,
for
how
front-and-center
is
something
like
getting
started,
is
which
I
think
we've
had
so
many
conversations
across
the
project
about
how
important
that
would
be?
J
And
it's
not
just
like
getting
started
and
know
to
like
hello
world,
but
in
different
parts
of
the
project,
even
yeah
I,
just
I.
Do
wonder
if,
like
the
needs
of
you,
know
the
project
and
the
needs
of
the
foundation
co-op,
you
know
whether
they
complement
one
another
when
it
comes
to
the
website
or
whether
they
like
need
to
you
know
a
foundation
needs
to
do
its
own
things
so
that
it's
not
you
know
hindering
the
project's
ability
to
have
the
you
know.
B
B
D
One
of
the
interest
is,
you
know:
I
want
to
help
with
the
nerdiest
website,
but
there's
no
real
place
to
go
start
right
now,
because
of
this
impending
redesign-
and
it's
you
know
like
I,
tell
them
to
go
to
the
noches
or
repo,
but
there's
kind
of
not
a
place,
not
a
place
to
start
with
this
new
thing.
So
you
know
there's
interest
in
helping
and
even
growing
the
website.
Working
group
I
think
it's
a
good
place
to
start
doing
that,
but
I
don't
know
what
kind
of
the
status
of
that
is.
It.
K
J
I
think
that
it
would
just
be
nice
for
us
to
have
like
a
reconvening
of
some
of
these
folks
like
I.
Don't
think
it
needs
to
just
be
me:
eight,
you
know,
I
I,
just
I
think
stakeholders
in
the
room
for
a
conversation.
It
might
be
nothing
I,
don't
want
to
stall
further
progress
either
if
that's
happening,
but
yeah
I
think
it
would
be
good
to
check
in
with
everybody
just
to
see
if
there's
something
you
know
that
we
can,
we
can
do
moving
forward
with
this
they're.
K
J
C
J
K
B
J
J
I
mean
the
biggest
thing
here.
I
would
just
ask
for
those
who
are
present
from
the
website.
Working
group
is
just
make
sure
that
the
that
folks,
who
would
care
about
this
cita
issue
and
website
working
group
I,
know
that
they're
more
likely
to
see
it
there
anyway,
but
I
just
want
to
make
sure
that
folks
don't
feel
like
they
missed
the
boat
on
that
so
just
make
sure
and
and
poke
people.
Please
all.
A
H
Yes,
yes,
I
do
sure.
So,
basically,
where
we're
at
right
now
is,
we
are
totally
ready
to
get
up
and
running
with
planning
out
some
no
together
stuff
in
the
future.
But
the
next
step
that
we
need
to
take
is
Ashley.
Williams
has
the
node
together
repository
under
her
account
on
github
and
rather
than
fully
ported
over
from
Ashley's
account
to
under
nodejs?
She
would
prefer
that
we
take
it.
She's
gonna,
write
deprecated
on
her
version
and
we're
just
gonna.
H
J
I
was
gonna,
say,
that's
also
like
just
from
a
planning
standpoint.
It's
really
nice
for
us
to
not
be
in
a
hurry,
because
the
more
that
we
can
plan
out
the
calendar
for
the
year,
meaning
next
year,
it's
just
the
better
quality
of
the
experience
is
going
to
be
for
everyone,
including
everyone,
who's
volunteering.
You
know
I'm,
mentoring
and
also
just
in
terms
of
budget.
It
will
be
far
more
likely
to
be
approved
if
we're
talking
new
calendar
year.
So
that's
exciting,
I
think
yeah.
J
H
Aren't
copying
and
well,
we
are
essentially
copying
and
pasting
I
believe
I
can
get
some
clarification
from
Ashley
I'll
have
to
go
back
and
look
either
way.
Basically,
we
just
need
the
go-ahead
from
all
of
you
to
say.
Yes,
we
are
ready
for
note
together
to
be
there's,
not
a
difference,
there's
not
a
real
difference.
Well,
we
lose
the.
G
E
H
B
H
D
H
I'm
sure
that
she
would
because
she
already
said
that
I
had
a
conversation
with
her,
because
there
was
a
little
bit
of
confusion.
I
was
like
wait,
am
I
fully
in
control
of
this,
and
she
said
yes,
totally
I'm
sure
right
up.
Excuse
me:
she'll,
write
up
a
whole
thing
that
says
that
we
are
running
it
now
and
that
I
am
in
charge
and
I'm
sure
I
can
get
her.
J
Maintenance
issues
yeah
so
yeah
I,
don't
think
that'll
be
a
problem
yeah.
That
was
the
biggest
concern.
I
had
honestly
with
the
losing
the
commit
history
was
people
just
came
to
see
all
the
work
that
she
put
into
it,
but
they'll
be
able
to
see
it
if
we
link.
So
that's
a
very
simple
solution
for
that.
I
think
the
biggest
the
biggest
part
here
to
you
is
that
we
need
someone
we
need
to
be
able
to
Creek.
We
just
need
a
creative
repo
to
for
us
to
be
able
to
put
that
one
in
all.
A
Right
I
can
create
the
repos,
and
also
in
the
last
meeting
that
we
had
where
we
discussed
this
with
Ashley
directly.
We
did
a
chance.
She
was
okay
with
us,
pulling
from
kuriboh
and
then
pushing
to
the
node
Depot.
It
is
possible
to
actually
maintain
the
entire
commit
history
if
we
just
kind
of
mess
around
with
the
gate,
config
file
a
bit.
A
J
H
That's
that
that's
what
we're
trying
to
do,
but
I
believe
that's
the
only
cost
that
we're
taking
on
that
is
unrelated
to
general,
expectable
general,
like
travel
and
that
kind
of
stuff.
It's
just
a
domain
name,
and
it's
hosted
on
github
pages.
We
may
want
to
move
away
from
that,
but
that's
something
else
that
we
can
explore
further
on.
C
C
J
A
C
J
C
A
A
H
H
H
H
A
All
right,
yeah,
we'll
move
this
to
the
issue
tracker
to
come
to
the
decision
of.
If
we
want
to
fork
and
ask
it
have
done
four
core.
If
we
want
to
pull
from
one
repo
and
push,
you
know
that
we
can
talk
about
the
pros
and
cons
a
little
more
in-depth
there
and
give
us
a
chance
to
can
like
research
a
bit
that
sound
good
to
everyone.
B
H
H
D
Yeah
that
does
bring
up
another
thing,
which
is
actually
the
the
website
stuff
and
it
that
is
a
part
of
the
the
within
there
to
get
those
no
together
website
is
a
part
of
no
together
does,
you
know,
are
members
of
the
website
working
group
interested
in
helping
out?
What's
that
and
kind
of
you
know
maintaining
and
working
on
that.
C
C
I
think,
technically,
if
if
it
was
really
desired,
it
would
be
possible
to
move
the
content
of
that
repo
into
the
main
working
sorry,
the
main
website,
repo
and
I,
have
it
under
that
content
system.
If
you
wanted
the
localization
or
such
things
that
the
our
system
provides,
and
then
it
should
be
possible
through
the
builds
working
group
to
have
that
still
redirect
to
a
separate
domain,
I
believe.
K
C
K
A
A
And
translations
are
always
kind
of
a
tricky
thing,
but
yeah
I
do
think
you
can
like
jail.
I
said
is
that
you
know
if
we
can
at
least
get
on
the
same
system,
we'll
still
have
the
same
problems
with
getting
translations,
but
it's
at
least
a
little
bit
easier
yeah.
You
know,
even
if
it's
a
small
one
I
guess
still
probably
awareness
still
alone,.
A
See
look
at
the
live
stream;
it
doesn't
look
like
it.
If
you
want,
has
any
questions
for
the
community
community.
Of
course,
you
can
always
open
an
issue
on
github
or
post
in
future
live
streams
on
YouTube
in
there
and
we'll
answer
those
and
with
that
owned
I.
Thank
everyone
for
coming
and
participating
in
this
discussion
and
just
for
all
of
the
community
community
members.
We
do
have
a
little
bit
that
we
need
to
discuss
after
we
stop
the
livestream
so
be
sure
to
hang
on.