►
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
B
B
D
D
A
Looks
like
it
has
sufficient
approvals
with
the
zero
rejections
or
zero
change,
request,
etc,
but
yeah
you're
right.
We
should
wait
for
michael
to
come
back
and
make
a
statement
on
that.
E
All
right
somewhat
related
to
that
in
the
next
10
meeting.
Just
now
there
were
plans
made
for
a
mini
summit,
another
mini
summit
on
the
18th
of
november,
it's
in
the
node.js
or
calendar
and
they're
looking
at
covering
types
and
single
executable,
apps
and
so
just
related
to
the
technical
priorities.
They're
planning
a
mini
summit
to
deep
dive
into
those
two
topics.
F
C
D
D
The
last
repo
that
will
be
done
is
the
core
repo
and
I
think,
we're
kind
of
waiting
to
close
it
on
that
happening,
and
that's
going
to
be
that's
going
to
be
the
one
with
the
most
risk
and
trickiness,
because
you
know
so
many
it
has
the
most
automation
and
a
lot
of
the
automation
may
depend
on
the
name
of
the
branch
and
things
like
that.
But
yeah
I
don't,
but
are
you
suggesting
that
maybe
it
just
doesn't
need
to
be
on
the
agenda
every
week.
A
So
I
I
may
be
wrong
here,
but
at
least
if,
if
I
can
recall
the
history
originally,
there
were
many
reports
which
needed
this.
Migration
and
michael
used
this
issue
as
a
tracker
for
doing
that,
reminding
constantly
reminding
people
constantly
about
the
requirement
of
helping
with
each
repo.
I
was
helping
with
couple
of
reports
and
others
were
helping
with
other
reports,
etc,
so
that
that
was
the
reason
why
it
was
featuring
in
this
meeting
recursively.
B
I
think
I
think,
there's
some
others
as
well,
we're
basically
getting
down
to
the
harder
ones
to
do
or
the
ones
that
have
had
very
little
activity
in
them,
not
not
not
that
they're
motherboardable
but
they're
just
there
and
just
require
people
to
have
the
time
to
go
in
and
sort
of
spot
spot
the
issues
and
do
the
renames
and
things
so.
I've
got
a
I've
got
some
of
the
build-on
repos.
B
We
have
to
evaluate
the
actual
build
repo
itself,
because,
obviously
things
like
jenkins
touches
it
and
there's
you
know,
all
sorts
of
things
could
break
with
build
same
in
the
same
way
with
the
node
called
repo.
It's
almost
like
this
is
a
strategic
initiative
rather
than
something
that
needs
to
be
brought
up.
Every.
D
F
F
D
F
Also,
okay,
like
so
the
quick
question
there
is,
if
and
when
we
are
willing
to
do
node.js
node,
which
will
be
the
main,
the
main,
the
most
prominent
one
to
mess
to
send
a
message
and
then
the
rest,
let
them
be
to
some
extent.
That
would
be
my
approach
and
what
I
would
recommend.
F
So
it's
you
know
there
is
a
lot
of
those
that
needs
to
take
in
a
lot
of
those
is
a
lot
of
work
for
not
so
much
gain,
not
so
much
gain
to
some
extent.
Okay,
it's
changing
from
master
to
main
is,
is
a
statement
position.
F
So
it's
the
moment
you
do
you
migrate,
the
main
one
or
the
main
ones.
You
know
the
one
that
must
attack
the
most
traffic.
Then
I
think
we
might
be
good.
I
don't
know
like
there's
a
long
tail
of
reapers
in
the
no.org
that
have
no
traffic
whatsoever,
so
I'm
not
sure
if
migrating
those
is
actually
you
know
worthwhile.
D
So
well,
we
already
did
migrate
pretty
much
pretty
much
all
of
them.
I
mean
there's
really
just
a
small
number
left,
but
I
wonder
richard.
I
wonder
if
it
makes
sense
to
add
the
build
rep
the
build
agenda
to
this
item
so
that
it
ends
up
on
the
build
working
groups
meeting
agenda.
We
can
make
it
a
priority
there.
Perhaps
I
don't
know
how
you
feel
about
it.
B
Yeah
I
I
can
do
that.
We
tend
not
to
have
that
many
build
group
meetings
but
yeah
we
could
add
it.
D
A
So
the
action
I
have
taken
on
this
is
to
initiate
a
voting
procedure
within
the
tse,
because
we
we
spend
a
lot
of
time
in
discussing
various
trade-offs
and
which
is
possibilities
and
we
could
not
converge
now.
The
good
thing
is
that
we
have
collected
all
opinions
and
insights
and
we
have
converged
into
three
discrete
options
and
that
is
documented
in
tsc
repo
issue
1104.
A
I
am
waiting
for
one
more
month
to
pass
before
we
actually
initiate
the
voting
basically
to
fulfill
option
number
one
which
is
migrate
for
a
subset
only
and
to
define
what
that
subset
would
be.
Looking
like,
I
haven't,
got
sufficient
input
on
the
earth,
so
I
plan
to
bring
people
who
have
provided
the
insights
about
these
options.
F
So
on
the
by
the
look
of
it,
we
have
a
lot
of
people
doing
security
work
in
the
in
in
as
part
of
node.js
note
that
most
of
those
tend
to
align
to
tsc
members
so
or
former
tsc
members
that
have
not
been
removed
from
there
when
they
drop
them
when
they
went
away
from
the
tsc
genetically
we
are
in
the
in
trouble
because
I
mostly
I've
been
for.
F
I
don't
know
one
year
close
to
one
year,
the
the
majority,
the
major
triager
of
node.js
security,
vulnerabilities
and,
more
importantly,
even
if
I'm
not
replying,
if
some,
if
I
don't
triage
nobody
triage
like
now,
there
is
vlad
that
is
now
vlad.
Is
there
and
can
help
each
every
every
now
and
then,
but
you
know,
nothing's
very,
it's
very
little
is
being
there's
very
little
help
on
on
aker1
now.
F
I
would
also
add
that
some
of
the
discussions
that
are
happening
in
there
are
can
be
very
long
and,
to
some
extent
emotionally
draining
in
in
certain
cases
like
in
in
in
some
cases
I
don't
know
if
you're
familiar
with
the
asymmetry
principle,
you
know
it's
from
time
to
time.
You
need
to
invest
double
the
amount
of
energy
to
refute,
to
refute
so,
and
you
know
you
are
essentially
if
it
was
for
the
for
some
of
the
security
researchers,
we
will
have
one
vulnerability
per
week.
F
So
among
the
various
range
of
topics-
okay,
so
you
know
even
stuff
that
is
internal
and
not
used
by
anybody
is
a
security
vulnerability
like
if
you
know
it's
it's
impossible
to
to
cause
I
wouldn't
to
to
to
exploit
this.
They
will
try
to
get
to
get.
I
wanna
to
get
a
cv
out
of
it,
okay
or
a
bounty,
so
fending
off.
This
is
a
lot
of
work,
so
I
ended
up
being.
I
am
a
little
bit
strained
and
it's
a
little
bit
of
a
thankless
job.
F
F
So
I
I
opened
this
pr,
essentially
removing
all
the
people
that
are
not
doing
any
security
work
that
are
not
doing
triaging
in
the
last,
while
include
from
ben
colin
fedor
jazza
james
now
miles
robert,
who
is
on
the
call
she
jakey
that
it's
been
a
long
time
since
you've
done
any
security
work
for
note
and
watson.
F
These
will
need
to
be
reflected
in
the
knucker
one
after
it
plans.
So
but
again
I
opened
this
issue,
but
then
somebody
told
me
that
I
would
did
not
do
it
correctly,
because
you
know
this
was
synchronized
from
with
the
tool
from
from
the
github
work.
So
probably
the
thing
is
to
remove
those
people
from
the
from
that
team.
So
anyhow,
that's
my
that's
a
bit.
Sorry.
D
So
so,
and
then
the
next
issue
on
the
agenda
I
opened
after
some,
you
know
discussion
with
matteo
in
that
issue
in
the
issue
we're
talking
about
now,
which
is
adding
security,
triaging
and
core
repo
governance
and
or
the
charter.
But
it's
largely
what
it's
really
about
is
establishing
a
triage
team,
and
you
know
like
one
that
actually
reflects
reality.
D
D
Basically,
I
guess
I'm
I'm
kind
of
volunteering
to
sort
of
just
take
on
both
of
these
issues
and
try
to
like
push
them
to
to
completion
so
like,
on
the
one
hand,
revise
these
security
teams
and
make
the
listing
in
the
repository
and
for
that
matter,
access
on
hacker
one
reflect
reality
that
we
just
you
know
we
have
a
lot
of
people
who
aren't
involved.
We
have
a
fair
number
of
people
who
aren't
involved
in
the
project
anymore,
who
still
have
security
access,
and
it's
probably
no.
D
It's
definitely
not
a
good
idea
to
to
you
know,
give
people
privileged
access
to
information
who
don't
need
it,
so
we
should
fix
that
and
and
then
the
other
thing
is
the
other
problem
that
mateo
is
alluding
to,
which
is
that
you
know
he's
the
only
person
he's
largely
the
only
he's
doing
the
bulk
of
the
work
here
and
and
is
burning
out
and
we've
had
this
problem
before,
with
other
people
doing
security
work,
and
so
I
want
to
establish,
invested
people
who
yeah
can
sort
of
share
the
load
a
little
bit
that
doesn't
all
fall
to
mateo.
D
So
I
guess
I
mean
we
can
talk
about
this
more
here.
If
anybody
has
things
they
want
to
contribute
or
discuss,
I'm
especially
interested
if
anybody
is
like
yeah,
I
I
want
to
do
more
and
I
don't
have
a
good
reason
why
I
haven't
been
doing
more
so
so
you
know,
and
then,
because
my
intention
is
to
figure
out
a
you
know,
a
small
group
of
people,
six
to
eight
people.
C
Yeah,
I
can
try
to
spend
more
time
trying
I've
been
I've
felt.
I
was
mostly
included
to
help
sort
out
certain
already
triaged
issues.
That's
mostly
what
I've
been
doing
there
when
matia
chases
me
and
asks
for
help,
then
I
try
to
help
out
solving
specific
issues,
but
I
can
try
to
do
some
triaging
as
well.
I
don't
know
how
much
time
I
have,
but
if
you'd
give
me
another
two
weeks
or
so
so
try
to
contribute
something
that
would
be
appreciated.
D
Yeah,
I
mean,
I
don't
think
we're
going
to
be
doing
anything
rash
in
the
next
two
weeks,
but
I
do
think
one
thing
I
want
to
do
is
consolidate
documentation
about
a
triaging
process,
because
I
don't
think
we
I
I
don't
know
that
we
have
a
single
set
of
documents
about
what
our
prices
are
so
like,
for
example,
I'll
often
get
an
email
notification
that
there's
a
cv
waiting
to
be
approved
or
not
or
whatever,
and
I
don't
know-
I
don't
actually
know
what
the
process
is
for
that
like
who
who
gets
to
decide
and
what
the
criteria
are.
D
F
F
F
D
So
again,
unless
there's
people-
I
I
I
wonder
if
we
should
like-
I
don't
know-
if
there's
really
a
whole
lot
to
talk
about
with
this
stuff
other
than
other
than
hey.
Is
anybody
interested
there's
a
lot
to
do,
and
I
I
guess
I'm
I'm
I'm
volunteering
to
and
I'm
happy
to
step
aside
if
somebody
else
wants
to
volunteer
to
figure
all
this
stuff
out,
but
but
I'm
I'm
offering
to
do
it.
So
I
think
that's
kind
of
where
that's
at.
E
One
question:
I
have
reference
in
the
first
pr,
that's
removing
some
folks
from
the
security
team.
Is
it
correct
at
the
moment
all
tsc
members
have
access
to
hacker
one.
Do
we
expect
that
to
change?
Should
it
just
be.
D
Triaging,
and,
and
also
about
like
people
who
are
sort
of
emeritus
security
that
we
probably
want
to
not
have
but
yeah
tsc,
no
expectation
that
tsc
access
will
change.
If
you're
on
the
tsc
you
have
access,
makes
sense.
F
Well
also
because
most
of
the
tsc
member
needs
to
have
access
anyway
for
for
the
follow-up
steps,
so
essentially
actor.
One
is
a
bug
tracker
for
security
things,
okay,
if
we
could
use
something
else,
if
we
wanted
to,
if
that,
if
we
had
anything,
but
it
seems
that
the
best
tool
that
we
can
use
for
that
job,
essentially
it
also
under
bounties,
which
is
nice,
which
is,
I
find
useful,
at
least
for
people
that
are
actually
doing
meaningful
security
work.
B
I
guess
one
question
I
have
over.
There
was
a
comment
made
earlier
about
people
not
being
taken
out
of
the
list
when
they
sort
of
stepped
down
from
the
tfc.
I
was
wondering,
if
that's
on
a
mission
in
say
the
off-boarding
process,
or
was
that
just
because.
F
A
D
B
I
guess
one
observation
I
have
is
obviously
I'm
I'm
new
to
the
tfc,
but
previously
when
I
was
doing
security
releases
and
I
didn't
have
access
to
hacka1
that
made
some
of
the
security
release,
preparation,
interesting
where
I
was
trying
to
backboard
things
to,
like
the
earlier
say,
no
12
lts,
but
wasn't
able
to
access
the
actual
vulnerability
details
to
even
get
like
reproduction
steps,
which
made
things
very
interesting
and
sort
of.
D
I
think
miles
at
one
point
advocated
that
if
you're
a
releaser
we
should
you
know
we
should.
We
should
really
consider
try,
try
to
consider
releasers
or
make
reducers
more
or
less
a
subset
of
the
tsc
for
a
lot
of
those
reasons
that
there's
just
like
freaks,
you
know
you're,
you
have
the
keys
to
the
kingdom
anyway
and
there's
all
this
friction
if
you,
if
you're
not
but
anyway,
I'm
going
to
stop
talking
now,
so
other
people
can
talk.
A
Ok,
so
rich,
do
you
think
the
issue
one
one:
zero,
zero,
add
security
charging
to
core
repo
warrants
a
separate
discussion,
or
do
you
think
it
has
been
covered.
A
D
Well,
joey
added
startup
performance
to
the
to
the
minutes,
which
I
know
she
wants
to
read
them
or
I
can
read
them
if
audio
is
a
problem.
G
Can
you
hear
me
yep?
Yes,
guess
I'll,
just
read
them,
so
I
it's
been
a
while,
since
I
updated
about
star
performance
in
the
tasting
thing,
so
I
guess
I'll
just
you
know
do
one
so
I
landed
most
precursive
focus
for
the
useless
snapshot.
Prolife
and
I
explored
some
extension
options
suggested
by
the
meeting.
Will
we
are
also
discussing
about
maybe
other
than
the
startup
snapshot.
G
That
va
currently
has
maybe
also
try
implementing
sensitive
wrapper
around
their
prototype
of
web
snapshots,
which
is
like
a
smaller
version
of
startup
snapshot.
The
only
like
snapshot
functions
in
objects,
so
the
so
here's
land
snapshot.
Prototype
is
currently
functional
with
the
type
circuit
compiler
and
that
you
can
snapshot
the
type
of
compiler
and
then
start
it
up
again
to
compile
snippets.
G
It
still
needs
apis
for
state
synchronization
and
maybe
a
proper
workaround
for
faster
guys.
Currently,
I
just
coming
out
to
fascinate
eye
versions
of
the
things
that
we
use
them
for
or
if
we
don't
want
to
like
use.
Workarounds,
maybe
add
support
in
v8
for
that,
but
yeah.
Those
are
their
two
main
blockers
right
now.