►
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
B
A
Announcements
this
week,
I
don't
have
any
board
updates.
I
don't
know
mary
if
you
have
any,
and
I
don't
know,
maybe
if
maybe
there
was
the
announcement
that
mary's
now
our
cpc
represented
representative.
A
Okay,
so
we'll
move
on
to
the
issues
tag
for
the
agenda.
The
first
one
is
34887,
which
is
back
port,
simpler
and
faster,
readable
stream,
async
iterator.
A
A
A
D
D
I
think
that
the
challenge
right
now
is
just
getting
ci
to
pass
so
like
to
me
if
the
folks
from
the
streams
team
are
plus
one
on
this,
you
know
like
I
don't
know
that
subsystem.
I
trust
them
that
this
is
a
good
thing
to
consider.
Backboarding
and
just
as
long
as
ci
is
green,
I'm
personally,
okay,
with
moving
forward.
D
A
Okay,
if
not
we'll
move
on
to
the
next
issue,
which
is
rename
default
branch
from
master
domain
or
something
similar.
A
C
A
Landing:
okay.
A
A
A
A
D
A
quick
point
of
order
which
needs
to
be
promoted
thanks
and
then
yeah.
We
changed
the
branch
for
canary
in
the
gold
mine.
It
was
rather
painless
and
there's
been
no
problems
now
like
that.
Repo
does
not
have
like
the
level
of
engagement
of
some
other
repos,
so
obviously
you
know
much
easier
to
land
there.
D
Now
we
do
also
have
node.js.dev,
which
is
one
of
the
ones
that
I
talked
about
doing
but
have
not
done
yet
and
that
one
would
be
slightly
more
complex
as
it
has
integrations
into
both
continuous,
like
ci
and
cd.
Okay
depend
on
it.
I
have
more
pull
requests
open,
but
the
tools
that
we
used-
fine,
the
redirects
for
hdm
http
links-
are
working
as
expected.
D
I
think
that
there's
still
maybe
a
few
more
features
in
github,
especially
the
get
redirect
stuff
that
we'd
like
to
see
before
core
repo,
and
I
can
follow
up.
I
haven't
checked
in
the
last
couple
weeks,
but
I
can
look
at
where
the
roadmap
is
internally
at
github
to
see
where
that
stuff,
when
that
stuff
may
be
landing.
That
will
make
it
easier
for
us
to
move
the
main
repo
right.
A
Okay
sounds
good
default
changed
for
new
repo
new
repo
creation,
okay,
anything
else.
Anybody
wants
to
add
on
that
one
before
we
move
on.
A
C
C
A
Yeah,
that
was,
I
guess,
my
suggestion
was
that
it
it
it
does
influence
at
least
my
thoughts.
What
other
people's
thoughts
are,
but
you
know
it
would
be
interesting
to
hear
the
rest
of
the
tsc's
feedback
here
is,
like
you
know,
is
fully
private.
Make
sense,
or
you
know
I
was
suggesting.
Maybe
you
know
it's
it's
public
among
the
tse,
but
we
don't
then
say
who
voted
how
publicly
or
you
know.
What
do
people
think
makes
sense.
You
know
fully
public
is
another
option
that
you
know.
D
So
one
quick
question
that
I
have
here:
I've
missed
a
few
of
the
discussions,
so
apologies
in
advance
is
the
tse
itself
extremely
conflicted
like.
Is
there
zero
chance
of
reaching
consensus
on
this
mary?
You
strike
me
as
someone
who
has
spent
probably
the
most
time
researching
talking
to
people
like.
Is
there
a
possibility,
any
possibility
that
perhaps
you
could
propose
one
particular
solution
that
you
think
is
the
best
and
just
see
one
last
time.
If
perhaps
we
could
reach
consensus
on
it
or
is
it
vote
inevitable
and
again
a
conclusion.
A
C
So
before
the
voting,
I
think
there
was
at
least
two
dissenting
opinions.
D
Okay,
two
quick
things.
First,
a
point
of
order:
bethany
needs
to
be
promoted.
Thank
you
and
then
the
second
thing
I
was
going
to
say
is:
I
think
that
we
should
vote
if
we
can't
reach
consensus,
but
I
I
would
personally
appreciate
like
at
this
point
mary,
because
you
have
spent
so
much
time.
Thinking
on
this,
I
myself
would
likely
defer
to
what
you
to
what
you
think.
So,
if
you,
if
you
were
open
to
it
and
wanted
to
even
just
on
a
private
list,
just
make
a
suggestion
and
call
for
objections.
D
I
think
just
one
last
time
of
seeing
if
we
can
do
this
after
all,
that
research
may
just
save
us
time
of
going
through
the
book
process.
If
we
do
go
through
the
vote
process,
I
personally
volunteer
to
help
you
figure
that
out,
if
you'd,
like
support
and
happy
to
follow
through,
so
not
saying
that
we
shouldn't
do
it.
I
just
kind
of
you
know
I
I
have
a
feeling
that
may
be
wrong
that
perhaps
we
can
actually
avoid
a
vote
here.
C
D
That
sounds
perfectly
reasonable.
I
can
dig
it
up
when
we
were
coming
up
with
voting
strategies
for
the
cpc.
I
did
a
lot
of
research
and
on
voting
technologies.
Also,
I
did
some
for
ecma
for
some
related
stuff
I'll
put
some
time
on
my
calendar
tomorrow,
to
gather
all
that
research
and
share
with
you.
So
we'll
just
be
a
survey
of
different
technologies,
so
we
can
pick
one.
A
A
A
Okay
sounds
like
not
so
anyway.
That's
that's
gives
us
a
starting
point
as
a
suggestion
that
we
can
make
anything
more
mary
that
you
want
us
to
talk
about
on
that
that
one
before
we
move
on.
B
I
don't
think
we
can
use
a
public
issue
if
we
don't
want
to
have.
If
it
comes
to
a
vote
and
we've
already
had
non-consensus
in
public,
it
doesn't
make
sense
to
vote
in
private,
so
I
think
just
to
have
the
option
of
having
to
vote
in
private
or
like
public
to
the
tsc
but
private
to
the
rest
of
the
world.
We
can't
do
the
first
discussion
in
public.
C
E
A
C
C
Votes
yeah.
If
we
fail
consensus,
we
should
go
to
a
voting
system
that
allows
one
of
the
options
to
have
more
than
50
percent
of
votes.
C
So
one
option
is
to
have
two
votes
at
least
or
at
most,
and
the
other
option
is
to
allow
for
multiple
choices
on
the
boat.
E
F
So
if
I
may
suggest
something,
if
we
are
all
fine
with
voting
internally
in
the
tsc,
then
I
would
suggest
we
could
just
each
one
of
us
sends
an
email
with
all
the
options
and
that
they
personally
would
feel
comfortable
with,
and
then
we
check
as
soon
as
everyone
voted
or
sent
that
email,
then
we
just
count
them
all
together
and
see.
What
is
the
outcome.
D
So
that
voting
strategy
would
be
approval,
voting,
which
was
one
of
the
things
that
we
had
discussed
as
opposed
to
runoff,
which
is
a
possibility
as
well
and
just
take
the
one
that
has
the
most
approval.
F
C
F
Believe
we
do
not
even
need
really
a
technology
for
it,
but
just
I
mean
if
we
want
to
hide
it
from
each
other
and
then
we
would
need
something,
but
otherwise
I
personally
believe
that
it's
sufficient
to
just
send
the
email
out
with
all
the
different
possibilities
that
we
personally
support.
G
A
A
A
D
D
Looking
at
the
comments,
it
looks
like
mary
likes
the
way
the
banner
was
before
michael
looks
like
you
like
the
new
design
a
little
bit
better.
I
I
think
that
there's
maybe
a
broader
conversation
which
we
are
already
having
about.
Like
you
know
what
are
the
next
steps
with
this
program
and
what
we've
done
here,
which
I
think
is
out
of
scope
from
this
to
me?
I
I
honestly
am
willing
to
just
say
like
hey.
D
If
the
collaborator
who
opened
this
pr
cares
about
it
that
much
and
really
believes
it's
better,
then
we
can
just
do
it,
although
I
do
think
that
the
existing
design
is.
A
D
D
A
A
C
F
Okay,
just
a
question
in
around:
do
we
actually
still
have
something
to
discuss
in
this
case,
or
could
we
just
go
straight
away
and
to
express
our
opinion
on
different
options?
Because
that's
what
I
would
suggest
I,
I
guess
every
one
of
us
in
the
round
has
an
opinion
already.
A
A
Removed
okay,
I
will
remove
the
tag
since
it
was
on
the
agendas
or
anything
that
I
see
that
labels
actually
already
been
removed.
Anything
that
people
did
want
to
talk
about.
A
Okay,
so
let's
move
on
then
audit
google
account
access.
I
know
rich
you'd,
pinged
brian,
who
said
he
would
get
to
it.
I
haven't
seen
anything
yet
on
that
front,
though
I
know
he's
very
busy,
so
we
should
just
leave
that
I
didn't
see
any
updates
for
the
strategic
initiatives,
but
on
the
build
front
I
don't
have
any
update.
A
D
D
There
is
a
bit
like
people
do
not
have
consensus,
it's
called
module
exports
patterns,
so
I'll
just
drop
it
in
the
chat
in
a
second,
as
it's
loading,
we
do
not
have
consensus
as
a
team.
If
this
should
land,
although
in
general
it
seems
like
the
feelings
are
there's
some
people
who
are
you
know
very.
D
Very
much
want
to
see
it
land
and
then
there's
some
people
who
feel
uncomfortable
about
it,
but
not
like
so
uncomfortable
that
they'll
block
sokra
from
the
webpack
team
also
just
came
in
with
some
some
comments
as
well.
It
would
be
very
interesting
you
know
like
I
know.
The
tsc
has
not
been
super
active
in
the
module
stuff,
but
we're
getting
really
close
to
the
interface
being
considered
stable
and
at
least
for
myself
like.
I
was
not
super.
D
D
I
personally
find
that
it
adds
complexity,
that
we
don't
have
right
now
and
makes
the
feature
a
little
harder
to
to
teach,
but
since
a
number
of
people
are
bullish
about
it,
I'm
not
like
in
a
position
to
block,
but
this
one
in
particular
is
one
that
I
think
would
be
good
for
us
all
to
take
a
look
at
and
maybe
think
a
little
bit
more
holistically
about
what
kind
of
experience
we
want
to
have
with
our
module
loader
and
how
much
like
magic
and
features
we
want
to
introduce
if
any
folks
need
a
bit
of
kind
of
like
catching
up
as
to
like,
where
we're
at
right.
D
Now
with
it,
I'm
happy
to
find
time
to
talk
to
you
one
to
one
and
give
you
kind
of
like
a
unbiased,
10,
000
foot
view
of
like
where
we're
at
from
the
future
capacity,
and
what
this
would
accomplish.
I'm
trying
my
best
right
now
to
not
tarnish
introducing
this
with
my
own
opinions.
A
Okay,
thanks
mary
anything
on
future
build
chain.
C
A
A
Issues,
okay
sounds
good.
Thank
you.
The
other
thing
I
might
mention
is
not
necessarily
a
strategic
initiative,
but
in
the
the
the
team
that's
been
looking
at
the
next
10
years
of
node
initi
initiative.
I
would
like
to
just
paste
the
draft.
A
Sorry
next
10
next
10,
just
for
awareness
we've
been
working
like
to
you
know
be.
The
goal
is
to
come
up
with.
You
know
the
technical
direction
goals
plans,
whatever
whatever
we
want
to
call
them
and
in
those
discussions
we
fell
back
to
you
know
needing
to
define
priorities,
capture
the
the
technical
values
and
priorities
of
the
the
project.
A
So
we've
been
working
on
that
the
last
few
meetings,
and
this
pull
request,
I
think,
reflects
something
which
is
pretty
close.
It's
from
the
people
who
participated
it's
what
we
we
think
reflects
the
values
and
prioritization
of
the
project.
A
Next
step
is
to
open
a
pr
in
node
core
to
add
a
document
which
captures
those
which
would
likely
do
you
know
making
sure
we
have
consensus
among
those
who
are
participating,
I'm
in
the
effort
first,
once
we
do
that
we'll.
You
know
I
might
plan
maybe
next
week
sometime
to
open
the
issue,
but
if
people
can
take
a
look
in
advance,
that
would
be
good
as
well.