►
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
A
Don't
think
so:
okay,
so
I'll,
no
announcements
this
week,
I
think
moving
on
to
the
CPC
and
board
meeting
updates.
The
main
thing
I
did
want
to
mention
is
that
there
were
some
updates
to
the
foundation
foundation.
Bylaws
I've
opened
in
the
CPC
repo,
an
update
that
just
gives
a
little
bit
more
information
on
that
and
I'll
post
that
into
the
minutes
in
case,
as
anybody
is
interested
in
looking
at
that,
and
of
course,
the
bottles
themselves
are
available
at
bylaws
that
opened
JSF
dot
org.
So
you
can
go,
take
a
look
there
as
well.
A
A
Okay,
if
not
we'll
move
on
to
the
issues
that
were
tagged
for
an
ogia,
slash
note.
So
the
first
one
is
issue
number
three,
four,
two
six
zero,
which
is
the
tie
next
ten
years
of
node,
that's
follow-on
to
session.
We
had
at
the
collaborator
summit,
which
is
talked
about
to
talk
about.
You
know
what
we
think.
You
know
what
we
think
led
to
the
success
of
the
first
ten
years
of
node
and
to
try
and
do
some
planning
or
strategy
around.
A
What
do
we
need
to
do
for
the
next
end,
the
University
of
node,
to
make
sure
that
that
we
remain
as
successful
as
we've
been
in
the
first
first
group
first
decade,
we
we
did
have
a
session
today.
I
put
it
on
the
I,
put
it
on
the
agenda
here
as
an
FYI.
Just
to
make
sure
you
know
all
the
the
TCC
members
knew
that
it
was
happening.
A
You
know.
In
there
we
talked
a
bit
about
logistics,
and
you
know
it
sounds
like
we're.
Gonna,
try
for
four
to
week
cadence
the
first
thing
we
do
VIN
to
a
little
bit
carrying
on
from
the
discussion
we
had
at
the
collaboratory
summer.
It
was
around
you
know,
not
a
road
map,
because
we
don't
necessarily
like
don't
think
that,
like
you
know,
here's
a
road
map
of
what's
inversions,
make
sense,
but
something
at
the
level
that
talks
about
you
know
what
our
priorities
are.
A
In
terms
of
you
know,
we've
seen
some
projects
have
like
you
know
we
prior
we
value
this
about.
We
value
you
know
in
terms
of
priorities,
but
we
value
this
about
that
and
like
to
have
something.
That's
sort
of
a
you
know
communicates
when
you're,
making
a
decision
in
the
project
what's
going
to
go
into
that
and
what
kind
of
priorities
do
we
think
we
have
as
a
group
of
collaborators
and
then
going
along
with
that
at
the
next
level?
A
Something
that
says
here
are
the
things
we
think
are
strategic,
for,
you
know,
know,
know
being
successful
in
the
next
ten
years,
and
you
know
again
being
something
that
says
if
you,
if
you
come
to
the
project
with
work
in
those
areas,
that
should
be
something
that
the
project
says.
Oh
yeah,
those
are
strategic,
so
we
want
to
bring
those
in,
and
you
know
to
help
help
us
also.
Hopefully,
you
know
have
some
some
some
perspective
on
what
we
think
it's
important
to
do.
A
So
we
we
talked
about
actually
creating
a
file
which
is
gonna,
be
at
the
top
level
of
the
node
repo
and,
to
you
know,
put
some
content
in
that
as
our
next
step
and
I'll
stop
there.
You
know
people
are
interested,
please
come
and
get
involved.
I
think
that
you
know
it
should
be
some
very
interesting
discussions
and
hopefully
it'll
help.
You
know
people
coming
to
the
project
understand
where
we're
coming
from,
because
I
think
we
have
a
lot
of
these
already.
We
just
don't
necessarily
have
them.
A
You
know
written
and
down
in
a
way
that
people
can
find
them.
The
next
issue
is
3405
for
proposal
to
create
rush
team
to
manage
the
backlog.
I
think
we
discussed
that
fairly
well.
Last
time
and
Jewish
was
gonna,
go
off
and
make
a
PR
to
you
know
start
to
pull
some
of
that
into
our
governance.
So
I
don't
know
if
there
actually
needs
to
be
any
more
discussion
and
whether
we
should
just
take
off
the
the
agenda
tag.
I
think.
C
But
one
thing
I
wanted
to
add
really
quickly.
I
had
had
a
conversation
with
someone
about
this
and
just
like
positive
uses
of
the
triage
role
thinking
about
when
you
might
want
to
use
it
when
you
might
not
want
to
use
it,
and
one
of
the
cases
where
they
were
talking
about
the
triage
role,
potentially
being
very
helpful,
is
like
especially
in
like
finding
things
that
people
can
do
and
get
involved
in
the
project
and
and
I
was
thinking
a
little
bit
about
like
some
of
the
logic
that
we
had
rich.
C
You
were
actually
one
of
the
people
who
push
for
this,
and
it
was
great
around
the
original,
like
collaborators
summit
onboarding
stuff,
that
we
would
do
that
built
that
a
note
to
do.
We
would,
you
know,
have
all
these
small
patches.
That
was
definitely
like
busy
work,
but
like
that
work
on
boarded
folks
and
help
them
to
do
stuff.
So
I
think
that,
like
while
we
could
argue
that,
like
you
know,
a
lot
of
the
triage
work
of
labeling,
things
is
something
that
can
be
done
by
a
bot.
C
Some
of
it
is
not
all
automated,
and
maybe
there
is
actually
room
here
to
create
onboarding
paths
for
folks
who
may
not
have
ways
to
get
involved
anyways,
even
if
it's
duplicating
a
little
bit
of
effort,
even
if
it's
not
the
most
efficient
or
effective
way
to
do
that
work.
It
could
be
a
great
way
of
you
know:
onboarding
more
collaborators
seconded
and
so
I.
D
C
B
C
Yeah
I'm
not
going
to
name
the
folks
I
was
talking
to
because
I
didn't
ask
for
permission
for
that,
but
I
think
that
they
have
been
working
on
some
ways
to
to
improve
this
and
look
at
creating
triage
roles
and
other
projects.
So
I'm
gonna
likely
try
to
borrow
from
from
some
of
that
and
see
if
I
can
get
some
of
the
work
that
they've
been
doing
to
help
like
reference
or
influence
how
we
got
into
it
that.
A
Sounds
good
and
you
know
Jewish
who's
been
very
active
in
doing
that
in
the
express
repo
who's
gonna,
bring
that
knowledge
in
context
as
well.
So,
hopefully
we
can
learn
from
what
they've
done
there
too,
and
what
I
I'm
blanking
on
that?
What
we'd
call
that
we
called
it
a
collaborator
where
we
had
people
you
know
and
we
helped
them
with
the
first
commit.
B
D
A
Okay,
so
let's
move
on
to
the
next
one,
the
next
one
is
remain:
the
default
branch
for
master
domain
or
something
similar
that
one
I
think
we're
really
in
a
holding
pattern
waiting
just
to
see
if
we
get
more
sort
of
pattern
or
tooling
or
whatever
out
of
github,
but
we're
leaving
it
on
the
agenda.
So
we
don't
forget
it
I,
don't
know
if
anybody
else
has
any
other
updates
or
thoughts
on
that.
A
Sounds
good
okay,
so,
let's
move
on
to
the
next
one,
it's
bootstrap
include
bootstrapped
environment
and
built-in
snapshot.
That's
32,
984
I
think
we
did
have
a
discussion
last
time
and
Daniel
devious
was
actually
you
know
diving
in
and
taking
a
bit
more
of
a
look.
I
know
he
did
comment
on
the
issue
saying
he's
still
working
on
that
and
and
is
has
a
bit
of
a
holiday
but
I
think
that
was
our
next
step.
So
we're
probably
just
waiting
waiting
on
that
yeah.
A
Okay,
so
I'm
just
gonna,
say
then
Bev
is
digging
in
we'll
wait
until
that
completes
before
for
their
discussion
and
then
the
last
item
on
the
pre
tagged
agenda
is
audit.
Google
account
access,
which
is
3d9,
that's
really
just
so
that
we
don't
forget.
I,
haven't
heard
anything
from
Brian,
yet
so
I,
don't
we
haven't
done
it
yet
so
I'll
just
leave
it
on
for
now
so
I
know
miles.
You
had
a
few
things
you
want
to
add
to
the
agenda.
Do
you
want
to
take
us
through
those?
Let
me
just
yeah.
C
C
So
NPM
seven
is
being
worked
on.
There's
talk
about
how
we
get
it
into
like.
You
know
both
newer
versions
of
the
node
as
well
as
LTS.
It's
been
an
ongoing
conversation
happening
over
at
the
release
team.
There
are
some
breaking
changes.
Obviously
it's
a
it's
a
nice
ember
major
version.
Some
of
them
are
more
disruptive
than
others,
and
one
of
the
things
that
we've
been
trying
to
do
is
kind
of
go
through
and
figure
out.
C
C
Sorry
I
got
distracted,
one
is
an
update
to
help
pure
dependencies
are
resolved
and
it's
kind
of
debatable
about
whether
or
not
whether
or
not
like.
This
would
be
a
good
thing
or
not.
One
could
argue
that,
like
it's
breaking
the
because
it's
making
things
actually
work
properly
and
they
haven't
worked
properly
before,
but
it
does
mean
that,
like
the
package,
locks
and
trees
that
would
be
created
by
NPM
with
this
feature
would
be
different.
C
So
I'm
thinking
right
now
that
what
we're
probably
going
to
aim
to
do
and
what
the
release
team
has
talked
about
is
we're
aiming
to
cut
a
beta
of
seven
before
the
end
of
this
month.
We
would
like
to
land
that
beta
onto
master
so
that
we
can
bespoke
testing
it
with
Sipkins,
so
that
we
could
be
getting
into
the
nightly.
C
Is
getting
some
degree
of
feedback
to
make
sure
there's
no
major
issues
that
we
would
take
that
that
feedback
and
then
determine
whether
or
not
we
would
disable
the
pure
dependency
stuff
and
cut
a
version.
Eight
and
I
think
that
the
overall
hope
would
be
that
we
could
have
a
ga
release
ready
version
of
it
in
September,
with
more
than
enough
lead
time
that
we
could
get
something
into
14.
Well,
it's
the
current.
C
Have
it
into
14
for
at
least
two
weeks
and
hopefully
get
it
into
twelve
before
it
moves
into
maintenance
mode
and
then
exactly
what
the
shape
of
those
things
would
look
like
would
likely
depend
based
on
feedback
that
we
gets
for
from
users
and
from
core
and
what
we
see
in
the
ecosystem.
As
far
as
usage
is
concerned,
so
I
wanted
to
just
update
the
TSC
I
mean
like
for
most
of
the
stuff
regarding
releases,
an
LTS
like
that's
totally
over
on,
like
the
release
team
to
figure
out
but
landing.
C
This
beta
on
master
is
definitely
something
that
gets
into
like
the
core
teams
and
TS
C's
decision-making
framework.
We
do
have
some
prior
art
of
blending
dependencies
with
betas
early
and
at
least
from
both
the
release
team
and
the
NPM
team's
perspective
and
I.
Guess.
I
can't
speak
to
everyone
on
the
release
team,
but
it
seemed
to
be
the
general
feeling
in
the
room
was
that,
especially
since
we're
talking
about
larger
changes,
getting
a
beta
in
master
sooner
so
people
could
be
playing
with.
C
It
would
be
a
really
great
way
to
like
help
make
that
decision
in
an
educated
way
over
the
next
couple
months
and
that,
like
in
general,
like
any
other
change.
If
it
ends
up
being
super
disruptive,
you
know
we
always
could
revert
it
or
like
revisit
it
later.
But
a
lot
of
what
we
want
to
do
is
just
like
make
educated,
informed
research
decisions
about
this.
A
So
from
from
my
personal
perspective,
the
you
know
landing
the
beta
in
master
I
think
doesn't
raise
too
many
questions
like
I,
understand,
thought
there,
and
you
know
the
the
the
for
me.
It's
trying
to
get
something
with.
You
know
a
list
of
breaking
changes
back
into
the
earlier
versions
where,
like
personally
I,
would
kind
of
like
to
understand
like
here's,
the
list
of
cember
majors
and
then,
along
with
them
like
why
it's
okay,
to
have
those
those
breaking
changes.
C
Yeah
we
have
that
list.
Yeah
and
I
could
get
someone
like
Roy
or
Isaac
to
come
and
chat
with
us
about
it.
If
we
just
like
to
be
updated
on
what
they
are,
having
reviewed
it
myself,
the
two
that
I
mentioned
around
lifecycle
scripts,
the
environment
variables
related
to
that
and
and
the
peer
dependencies
to
me
at
least,
appear
to
be
the
only
ones
that
would
like
actually
affect
folks
and
how
they
do
things.
C
A
lot
of
the
rest
are
like
the
internals
have
been
massively
refactored
on
top
of
arborist,
and
it's
one
of
those
things
where,
like
there's
a
really
big
backlog
of
a
lot
of
bugs
and
issues
that
haven't
been
dealt
with
for
years,
that
this
big
refactor
should
be
fixing
a
lot
of
them.
I
think
another
part
of
this-
and
this
is
part
of
like
maybe
a
bit
of
a
larger
strategy
to
be
discussed,
is
like
you
know,
the
NPM
team
does
have
limited
resources.
We
are
exploring.
C
You
know
governance
models
that
could
help
improve
external
collaboration,
but
we
want
to
be
like
very
realistic
about
the
resources
that
we
have
and
if
we
can
find
a
way
to
get
seven
on
12
and
14
like
a
version
of
seven
that
is
okay
and
then
kind
of
punt.
All
of
the
things
that
are
kind
of
make
us
concerned
into
a
version.
Eight,
that's
only
on
15.
C
A
D
A
Can
definitely
understand
that
from
the
flip
side,
like
you
know,
you
just
said
massive
refactor
is
not
the
first
thing
I
like
to
see
go
into
the
stable
LTS
right
like
so
it's
it's
a
matter
of
timing
and
understanding
what
that
is
right,
like
it's
like
hey,
we
finished
this
master
free
factory
yesterday
or
we
finished
it
six
months
ago
and
it's
been
out
there.
People
have
been
using
it.
You
know
that,
yes,.
D
A
C
Try
to
get
it
back
to
12
I
think
that
we
could
have
a
longer
conversation
about
whether
or
not
we
can
do
that.
Well,
12
is
in
maintenance.
This
is
12
s.
Also.
The
first
version
that
we're
doing
like
a
12
month
active
18
month
maintenance,
so
we
have
a
six
month
shorter
window
to
try
to
squeeze
these
things
in,
but
I
think
with
all
of
this.
C
D
A
A
A
That
I
don't
think
it
really
makes
sense.
We
don't
have
too
many
people
here
from
the
strategic.
In
this
initiative
side
there
were
a
few
updates.
You
know,
targets
mentioned
the
update
on
v8
currency
v8
thought
force
landed
on
master,
so
it
sounds
like
we'll
have
8.4
and
sorry
and
there's
a
PR,
the
back
part
it
214
dot
X.
So
it
sounds
like
we
will
go,
tell
TS
with
8.4
and
they're
starting
on
8.54,
but
there
are
some
issues
start
a
performance
you
know.
A
So
they
were
Joey
mentioned
that
there
was
some
work
on
the
the
issue
she
has
opened
was
rebased
and
some
additional
issues
were
resolved
again
appreciate
more
reviews,
and
then
you
know
I
mentioned
that
Dan
made
commented
that
you
know
he
started
to
look
at
dig
into
that
in
terms
of
the
start
of
performance.
Prs
James
mentioned
that
quick
on
work
is
ongoing
and
on
the
build
resources
front,
I
don't
have
anything
to
update
and
Myles
mentioned
that
there's
no
major
update
for
modules,
so
I
guess
actually
we've
got
pretty
decent
covers
there
anyway.
So.