►
Description
A
There
we
go
we're
live
all
right,
all
right,
technical
difficulties,
surmounted
and
welcome
to
the
no
js'
foundation
I'm
waiting
to
actually
Kate.
Yes,
the
nosiest
foundation,
technical
steering
committee
meeting
for
Wednesday
November,
7,
2000,
18
I,
guess
somebody
should
be
taking
minutes
and
I'm
guessing
it's
gonna.
Be
me
if
there's
a
volunteer
speak
up,
please
otherwise,
I'm
about
to
open
the
dock.
B
A
Well,
in
the
meantime,
all
uh-oh
okay,
great
thank
thank
you
I
appreciate
that
rod.
Thank
you
very
much.
So
we
start
with
announcements
we
have.
We
have.
We
have
two
new
collaborators
within
the
last
24
hours,
PS,
Marshall
and
Asami,
since
I,
think
of
people
by
their
github
IDs
and
not
their
actual
names,
I'm,
really,
sorry
and
oh,
why
why
D
has
been
nominated
to
be
a
collaborator,
so
that'll,
hopefully
onboarding
will
happen
in
the
next
seven
days
or
something
like
that
the
same,
but
we
also
have
announcements.
A
All
right
great,
so
then,
let's
forge
on
ahead
the
first
and
only
substantial
issue
that
I'm
aware
of
for
the
agenda
is
node
issue
number
two
three
four
three
three.
This
is
about
the
behavior
of
read,
file
and
write
file
when
working
with
file.
Descriptors
and
sakti
put
this
on
the
agenda.
I
believe
we
talked
about
it
last
week
and
we
determined
that
we
would
kick
it
back
to
github,
but
leave
it
on
the
agenda
in
case
consensus
wasn't
for
me
it's
my
impression
that
consensus
seems
to
be
forming
around
option
one
in
that
issue.
C
C
D
B
Yeah,
that's
it!
That's
a
system
thing
it's
it's
sort
of
stored
like
the
essentially
the
kernel
maintains
position
with
the
final
file
descriptor,
so
I
I
think
I
think
they
can
make
me
if
I'm
wrong
exactly
that,
but
the
the
change
in
that
pull
request.
That's
got
the
store
option.
One
is
simply
to
not
reset
position.
It's
just
let
the
file
descriptor
continue
on
from
where
it
is.
It's
not
do
something
with
the
position.
It's
just
done.
Preset,
composition,.
D
C
B
I
mentioned
in
the
issue
that
I
don't
think
citizen
is
going
to
pick
up
anything
because
it's
it's
such
an
obscure
usage
and
I.
Don't
I
can't
imagine
that
it
would
be
easy
to
even
find
anything
with
with
chakras
tool,
because
we're
talking
about
just
different
arguments
to
read
file
on
write
file,
that
the
usage
of
this
kind
of
thing
is
going
to
be
in
a
few
obscure
NPM
packages,
but
possibly
also
in
production
level
apps,
where
people
have
specialized
file.
B
A
It
feels
like
kind
of
like
y2k,
like
you
know,
maybe
it'll
be
a
really
big
impact,
but
probably
not,
but
you
know,
let's
get
word
out
and
get
people
panicking
as
much
as
possible
to
fix
this
if
it
is
gonna
affect
them,
but
it
probably
won't
affect
them.
It's
kind
of
how
it,
but
like
that's
all
good
level,
I,
don't
think
it's
gonna
be
a
whole
lot
of
actual
data.
We're
gonna
have
on
this
until
it's
actually
released,
but
I'm,
not
I'm,
optimist
and
I
suspect.
It's
not
gonna
affect
very
many
people.
A
B
D
E
A
F
C
B
B
B
A
Yeah
I'm
a
motion
that
we
there
we
are
that,
even
though
we
have
a
light
agenda,
I
prefer
that
we
push
these
kinds
of
particulars
back
to
github
so
that
it's
documented
for
everybody
else.
For
one
thing,
that's
that's,
okay.
Is
there
any,
but
it
well.
Is
there
anything
else
that
somebody
feels
needs
to
be
said
or
commented
here
rather
than
in
the
issue
tracker.
Anybody.
A
There's
the
tracking
issues
for
updating
the
TSC
on
board
meetings.
Miles
isn't
here,
so
we're
gonna
skip
that
one
because
he's
the
one
who
provides
the
update
because
he's
the
board
I'm
and
then
there's
these
strategic
initiatives
and
we
usually
go
through
the
list
of
strategic
initiatives.
Whoever's
here
updates
us
on
them.
I
know
one
of
them
is
s
to
sell,
so
that
could
be
rod
if
you
want
to
kick
that
off,
while
I
go
find
the
list
of
strategic
initiatives,
yes
and
there's
actually
stuff
to
report
hooray.
B
So
I
don't
know
if
there's
an
update
today,
but
he'll
certainly
do
we
were
in
the
area
now
of
ironing
out
the
educators
on
the
obscure
platform.
So
that's
just
that's
a
sign
that
we're
getting
really
close.
We
need
to
do
testing
on
a
bi-stability
because
we
can't
we
can't
do
this
without
maybe
nice
building.
A
D
Yes,
nothing
significant
to
report.
However,
the
the
next
parts
of
this
are
a
little
bit
more
of
reliance
on
the
streams
working
group
and
some
of
those
members
are
currently
tied
up
in
doing
other
things.
So,
unless
someone
has
someone
out,
there
wants
to
help
out.
It
has
a
lot
of
streams.
Three
experience
to
help
build
an
adapter
for
that,
it's
going
to
be
a
slow
for
a
while.
A
G
Hello,
so
I
think
works.
There
is
something
to
report
the
one
of
the
things
that
has
been
blocking
progress.
Amazing
cooks
is
the
performance
of
promise
sucks
and
we've
been
trying
to
figure
out
how
to
deal
with
that
and
we
exhale
the
meeting
a
couple
weeks
back
with
the
VA
team
in
many
of
the
diagnostic
working
group
participating.
So
so
so
we
have
a
plan
forward.
A
Okay,
that
is
the
end
of
the
published
agenda.
We
usually
do
I,
don't
see
it
on
the
agenda.
Maybe
we
took
it
off,
but
we
used
to
at
least
do
QA
I,
don't
know
if
anybody
wants
to
check
IRC
or
the
YouTube
channel
to
see
if
there's
any
questions
for
the
technical
steering
committee
I'll
just
kind
of
like
sit
here
quietly
for
10
seconds
and
try
to
look
in
a
few
of
those
places
myself,
but
I
will
probably
miss
things
because
I'm
not
really
good
at
this
kind
of
multitasking.