►
From YouTube: JupyterLab Team Meeting - August 17, 2022
Description
A meeting to share and discuss features, ideas, issues, and pull requests in JupyterLab and other Jupyter frontends. This meeting is open to anyone and everyone.
Join future calls via the Jupyter community calendar: https://docs.jupyter.org/en/latest/community/content-community.html#jupyter-community-meetings
Notes for upcoming meetings can be found on the agenda: https://hackmd.io/Y7fBMQPSQ1C08SDGI-fwtg
Past notes can be found on the JupyterLab team compass: https://github.com/jupyterlab/team-compass/issues?q=is%3Aissue+label%3A%22Dev+Meeting+Minutes%22
A
Welcome
to
the
August
17th
weekly
Jupiter
lab
call.
Today
we
have
14
people
on
our
call
and
if
you
are
just
joining,
please
find
agenda
in
the
chat
and
sign
in
and
add
an
agenda
item.
If
there's
anything
you'd
like
to
discuss,
we
don't
have
an
additional
discussion
section
on
the
end,
but
there's
something
you'd
like
to
talk
about
that
is
a
bit
longer
than
just
an
agenda
item
say
five
minutes,
then
please
add
it
to
the
additional
discussions
section
and
with
that,
why
don't
we
get
started?
B
Hey
good
morning,
good
evening,
everyone
I
had
a
couple
of
action
items
that
came
out
of
the
triage
meeting
last
week,
triages
every
week
on
Thursday
by
the
way
for
those
who
are
unfamiliar
one
is,
should
we
modify
Probot
to
not
tag
issues
from
veteran
contributors
with
the
needs
triage
tag,
because,
typically,
when
we
look
at
issues
in
triage,
if
the
person
filing
it
is
very
experienced,
we
kind
of
accept
that
what
they
file
is
conformant
and
we
don't
need
to
triage
it.
C
Are
you
defining
like
experienced
contributor.
B
That's
a
good
question:
we
would
have
to
come
up
with
a
rubric.
Certainly
things
like
people
who
are
on
the
council
or
distinguished
contributors
would
be
on
that
list.
B
You
know
we
could
also
come
up
with
a
rubric
of
like
if
you've
had
X
number
of
issues
accepted
with
a
percentage
accept
rate,
then
you
get
the
auto
Auto
Acceptance.
It's
not
like
the
the
worst
case.
Is
that,
like
everything
you
submit
so
as
to
go
through
needs
triage
so
like
we're,
not
punishing
people
who
are
have
lower
success
rates.
D
There's
also
a
metadata
from
the
GitHub
environment
that
you
can
use
to
determine
what
type
of
user
is
creating
it.
So,
there's
like
owner
affiliate
I
forget
what
those
are,
but
that
could
be
an
option
instead
of
a
lot
of
list.
A
A
D
A
The
point
of
the
triage
label
is
so
that
we
don't
miss
anything
that
we
truly
don't
know
where
it
belongs,
whether
it
needs
to
be
resolved,
whether
it's
a
Jupiter
lab
issue
or
different
repo
Etc.
But
if
your
level
of
familiarity
with
the
project
is
such
that
right
now,
you
can
modify
labels
go
ahead
and
modify
them.
If
you
feel
that
you
ought
to
have
that-
and
you
don't
just
ask
well
almost
certainly
say
yes
so,
like
the
bot
action
is
meant
to
make
this
automatic
and
seamless.
A
B
Mean
if
you
have
the,
if
you've
gained
the
permission
to
add
and
remove
labels,
you're,
probably
an
experienced
contributor.
Although
I
did
note,
when
I
filed
that
new
issue
and
I
deleted
the
label
I
had
to
do
it
twice,
because
the
label
was
first
part
of
the
template,
then
I
removed.
It
then
Probot
swept
in
and
tagged
it
a
second
time
and
I
had
to
remove
it.
So
it
is
a
little
bit
annoying.
B
You
got
to
get
the
timing
just
right,
so
I
feel
like
modifying
Probot
to
not
go
in
and
tag,
it
might
be
an
improvement,
but
if
you
would
like
to
share
thoughts
or
suggestions
about
that,
please
use
the
the
issue.
Link
provided.
B
One
other
topic
from
triage
is
old,
pull
requests
as
of
moments
ago.
We
have
86
pull
requests
for
Jupiter
lab
alone,
some
of
which
are
quite
old.
The
newest
one
is
an
hour
ago.
The
oldest
one
is
from
December
22nd
2018.,
so
these
old
issues
should
probably
get
the
old
pull.
Requests
should
probably
just
get
closed
out
like
if
we
haven't
accepted
this
thing
after
two
plus
after
what
three
and
a
half
years,
probably
not
going
to
do
it
or
just
ship
it.
B
B
B
D
E
I
mean
kind
of
tangential.
I
know
you
were
joking
about
the
triage
pull
request.
Meeting
but
I
do
know
some
projects
that
have
like
once
they
realize
there's
a
backlog.
They
need
to
go
through
they'll,
be
like
oh
we're
having
like
a
one-off
event
and
they'll,
just
kind
of
do
it
as
needed,
where
they're
like
we're
gonna,
fix
all
these
things
and
make
it
try
and
make
it
like
fun
for
everyone.
So
that
is
a
possibility.
B
I've
had
you
know
both
bug,
fixaphon
and
Bug
file-a-thon
events,
not
at
the
same
company,
because
that
would
be
really
counterproductive,
but
yeah
just
encouraging
folks
to
take
a
look
at
the
pull
requests
because
they,
they
are
numerous.
A
A
Okay.
I'll
remind
you
again
if
you
would
like
to
talk
about
anything,
please
add
to
the
agenda,
but
second
on
the
agenda
today
is
me
so
we've
been
making
good
progress,
a
group
of
us
on
the
lumino2
project,
I
love
the
project
board.
A
I,
see
right
before
this
call
started.
It's
Steve
merged
a
PR
I
had
open.
That's
the
second
link
there,
the
native
iterators
PR.
So
if
you're
not
aware
there
are
some,
there
are
some
API
accessors
in
say
widget,
for
example
like
panel
children,
or
there
are
some
data
structures
throughout
lumino
like
the
Q,
the
linked
list
used
for
messaging
and
a
few
other
things
that
used
a
set
of
custom
homegrown
iterators
that
closely,
but
not
exactly
followed
the
shape
of
native
iterators.
A
A
I
got
from
multiple
people
on
it,
because
it
it's
subtle,
some
of
it's
subtle,
and
so
it
went
in
and
I
would
like
to
do
an
alpha
luminum
to
release
soon,
because
even
though
it
won't
require
a
ton
of
refactoring,
it
will
require
changing
a
bunch
of
things
in
code
that
uses
aluminum.
A
A
Although
we've
kept
that
function
for
one
cycle
and
labeled,
it
deprecated
just
to
make
the
lives
of
people
who
are
changing
their
code,
a
bit
easier
and
I
wrote
a
substantial
top
level
comment
just
to
describe
all
the
API
changes,
because
this
hits
a
lot
of
people
and
use
that
top
level
comment
as
the
basis
for
the
beginning
of
a
migration
from
luminal
one
to
lumino,
2.
so
yeah.
Hopefully
we
can
ship
an
alpha
single
and
update
the
stupid
lab
code
base
as
well.
A
There's
a
bunch
of
stuff
on
that
board.
I
will
again
ask
if
you
have
any
interest
in
working
on
this
stuff.
Please
take
a
look
at
the
board.
Please
claim
an
issue
if
it
hasn't
been
and
if
you
have
questions
I'm
happy
to
answer
them.
A
There
are
probably
other
people
on
this
call
who
are
knowledgeable
and
can
answer
you,
and
it
would
be
really
nice
if
lumino
wasn't
some
black
magic
that
only
a
handful
of
people
know
it
is
the
basis
for
the
Jupiter
front
end
so
that
we
are
shipping,
so
hopefully
more
people
will
get
involved,
yeah
I
guess
that's
all
I
have
to
say
about
that.
I'll
wait
for
a
second,
because
the
next
subject
is
totally
different.
But
if
you
have
any
questions
or
comments,
I'm
happy
to
talk
about
it.
D
A
My
last
point
is,
if
you
are
in
the
Jupiter
lab
Council,
please
consider
either
nominating
another
person
to
the
council
or
consider
nominating
a
member
of
the
council
for
the
software
steering
Council,
because
we
should
pick
someone
to
represent
this
project
in
the
software
student
council.
We
are
aiming
for
the
beginning
of
December
being
a
time
when
the
new
governance
takes
over
from
this
sort
of
transitional
period
that
we're
in
right
now
between
the
steering
Council
and
the
new
governing
structures
that
have
all
passed.
A
The
student
council
has
voted
in
favor
of
them,
but
they
don't
magically
come
into
the
existence.
So
this
is
part
of
the
very,
not
magical
mundane
way.
They
come
into
existence
as
I
ask
for
people
to
nominate
and
we
hold
yeah.
That's
it
for
me.
Any
questions
about
that.
Jason
grout
has
a
comment
and
he
says
we're
aiming
for
having
the
sub
project
councils
in
place
by
October.
That's
right.
A
So
we
have
our
sub-project
Council
and
it
is
pretty
large,
I'm,
I'm
I'm
sure
it
should
be
larger,
so
I
don't
think
it's
so
small
as
to
be
unfair
right
now,
but
it
could
certainly
be
more
fair,
so
yeah,
that's
right
that
we
we're
not
waiting
until
December
to
be
there.
We
want
to
do
that
faster
yeah.
Any
questions
comments.
E
Is
this
a
place
to
ask
questions
about
that
process,
or
would
you
prefer
that's
on
a
mailing
list
like?
Is
this
the
right
call
to
ask
that
sure?
Okay
with
the
nominations,
is
it
similar
in
that
someone
like
nominates
one
person
or
is
it
like
I,
want
to
nominate
these
people
for
us
to
vote
between
like?
Is
there
anything
like
that?
That's
different.
A
Okay,
so
there's
two
things
that
you
can
nominate
people
for
one
is.
You
can
nominate
somebody
to
be
on
the
Jupiter
lab
Council
and
we
do
that
one
at
a
time
and
each
new
person
that's
added.
The
composite
group
has
to
again
handle
voting
on
a
new
nominee
when
it
comes
to
nominating
someone
for
the
to
be
be
our
representative
for
Jupiter
lab
in
the
software
stream.
Council
I,
don't
I,
don't
recall
if
we've
written
much
guidance
about
this
I'll
I'll
check
and
get
back
to
you
on
that.
C
A
What
I
would
say
is
we
you
should
check
with
the
person
you
want
to
nominate
to
see
if
they're
even
willing,
right
like
they
might
just
not
want
to
be
nominated
for
that
it's
a
bit
different
from
nominating
someone
for
the
Jupiter
lab
Council,
because
you're
basically
signing
them
up
to
do
work,
whereas
the
council,
it's
minimal
enough,
that
we
can
just
without
informing
someone,
nominate
them
vote
on
them
and
if
they
get
accepted,
tell
them,
but
to
be
a
to
be
a
representative
for
this
project
and
so
for
student
council.
A
A
Right
now,
because
we
don't
have
a
private
repo,
where
we
can
have
discussions
yet,
but
I
think
we
should
make
a
private
repo
so
that
we
can
use
GitHub
discussions
for
for
this
instead
of
the
mailing
list,
I
think
it's
more
discoverable
and
more
natural
for
the
people
on
the
project.
Does
that
answer
your
question
I
said
a
lot
of
words:
yeah.
E
No
and
sorry
I
wasn't
being
specific.
I
meant
the
second
one
specifically,
but
it's
probably
good
to
have
it
documented
anyway
about
nominating
for
the
software
no
words.
Yes,
software
steering,
Council,
sorry,
words,
okay,
yeah,
that
makes
sense,
I
wasn't
sure
if
there
was
a
set
way
for
that,
but
that
makes
sense
for
figuring
it
out.
Thank
you
cool
thank.
C
Hi
everybody
so
I
stuck
my
foot
in
the
wood
chipper
of
attempts
to
add
toast
libraries
to
Jupiter
lab
a
couple
weeks
ago,
and
so
this
is
the
follow-up
to
that.
C
Based
on
what
everyone
said
on
all
the
feedback
and
suggestions
that
I
got,
there
were
a
couple
of
options
that
were
essentially
already
assembled
either
in
the
form
of
like
experiments
or
the
form
of
actual
functioning
extensions
and
the
most
promising
of
those
was
something
called
tuber
lactoseify,
which
was
extension
by
Frederick,
and
so
what
I
would
like
to
do
is
pull
this
into
the
UI
components.
Library,
there's
a
draft
PR
up
with
it's.
C
It's
still
completely
non-functional
at
this
point,
but
it's
it's
basically
just
Frederick's
code
copy
and
pasted
into
that
library,
and
then
some
modification,
but
essentially
just
like
he's,
he's,
relied
on
like
fontops,
and
so
we
don't
need
to
internally
for
icons
and
stuff
Strangers
Like
That.
E
C
Yeah
so
I
think
the
styling
fits
as
as
is
fits
pretty
well
with
our
overall
styling
I
need
to
tweaking
15s
and
stuff,
but
I
think
it
is
unobjectionable
at
the
very
least
I'm.
B
Not
objecting
to
it
but
I'm
curious
about
like
would
you
consider
using
the
browser's
push
notification
system
in
addition
to,
or
instead
of
the
in-app
push
notifications.
C
The
browsers
like,
for
example,
what
are
you
talking
about
exactly
like.
B
You
know
those
those
wonderful
pop-ups
that
everyone
loves
getting
when
you
go
to
your
favorite
website
and
chrome
says
this
note.
This
website
would
like
to
pop
up
notifications
on
your
desktop.
Would
you
like
to
let
it.
E
C
E
B
C
There
is
a
good
native
thing
for
this,
then
sure
I'd
definitely
consider
using
that,
but
I'm
not
familiar
with
it.
They're.
B
Not
I
I
can
paste
a
link,
but
it's
it's
not
as
Rich.
You
don't
get
customization
for
things
like
appearance,
color
position.
C
Okay,
so
the
the
feedback,
the
feedback
I
got
the
last
time
I
brought
this
up
was
that
we
want
a
Jupiter
lab
component
right.
We
don't
want
that's
a
UI
component
or
something
that's
customized,
with
the
look
and
feel
due
to
the
lab
yep.
So
I
think
this
is,
and
it's
react-based
I
think
this
is
a
good
yeah
overall
direction.
B
One
big
Advantage
is
that,
if
you're
doing
something
in
the
background,
then
Jupiter
lab
can
notify
you
using
a
desktop
notification,
even
if
it's
not
visible
in
your
browser.
At
that
moment,.
B
A
But
we
might
consider
using
native
notifications
as
some
sort
of
conflated
set
of
notifications
like
you
have
200
unread
messages
or
something
like
that,
but
even
that
we
should
I
think
be
careful.
A
Mean
my
my
computer
sounds
like
it's
taking
off,
sometimes
so
fair
enough,
but
to
to
two
comments.
C
D
A
C
A
You
talk
with
Fred
and
he's
happy
with
this,
then
just
use
the
co-author
attribute
that
GitHub
supports
in
your
commit
message.
There's
a
lot.
You
do
a
line
break
after
your
comment
and
then
you
write
code,
author
Dash,
buy
or
something
like
that.
You
you
list
co-author
and
it
it
links
it
automatically
so
that
that's
a.
C
C
Just
pulled
it
into
the
library
instead
of
you
know,
just
using
the
extension
as
was
is
because
I
think
it
makes
just
more
sense
as
part
of
the
UI
component
Library
like.
Why
should
it
be
in
two
different
places.
A
But
yeah
I
think
that's
a
a
reasonable
approach.
I
would
just
want
to
hear
what
yeah.
C
No
I
I
I
I
I
was
hoping
Fred
to
be
on
the
call,
but
I
guess
I'll
try
and
talk
to
him.
One-On-One
later.
A
Cool
any
other
questions
comments
on
this.
A
D
A
C
A
C
No,
no,
no
knee
so
as
for
the
actual
content,
rather
than
the
git
specifics
like
does
anybody
have
any
particular
objections
to
this
like
I
know,
I
know
maybe
you'll
have
to
have
like
I,
don't
know
if
they'll
have
to
rise
to
the
point
of
a
vote,
but
there
were
certainly
lots
of
opinions.
A
I
mean,
as
a
consumer
of
this
Library,
helping
with
the
Jupiter
lab
notifications
extension
that
the
Cal
Poly
team
built
last
year,
I
think
it's
good
I,
don't
know.
I
really
don't
feel
well
informed
enough
to
have
a
strong
opinion
which
is
I
just
kind
of
want
to
see
what
Fred's
thinking
basically
like,
because
he's
now
in
the
fast
UI
mind,
space
and
I
want
to
know.
C
So
what
he
said
what
he
said
specifically
about
that
he
did
comment
on
that
specifically
basically
fast
UI
does
not
or
fast
API
does
not
supply
this
particular
component,
and
it.
D
C
A
C
Of
complicated
for
us
to
re-implement,
you
know,
do
a
lot
of
you
know
remaking
the
wheel,
and
there
are
plenty
of
good
existing
lightweight
things,
and
his
first
example
was
react.
Reactosify,
which
is
you
know
what
this
is
built
on.
C
C
D
General
note
that
the
previous
API
decisions
might
not
care
too
much
about
being
generic
and
replaceable.
D
Libraries
later
on,
then,
there
might
be
a
good
to
do
like
a
pass
of
the
the
extension
if
it
exports
the
token,
the
the
the
API
of
that
to
make
sure
that
it's
as
generic
as
possible
and
as
little
of
the
internal
implementation
bleeds
through.
So.
C
The
the
sort
of
issue
with
that
right
now
is
the
way
that
Frederick
has
a
setup
is
the
the
main
message
that
gets
displayed
like
the
actual
like
text
or
whatever
is
actually
just
a
it's
like
a
generic
react
node.
It
will
essentially
take
like
any
reacts
entity
we
might
want
to
have
it
just
be
like
plain
text
instead
right,
like
it's
kind
of
cool,
that
it
could
take
potentially
like
any
element.
If
someone
wanted
to
do
something
really
custom,
but
probably
it's
just
like
the
basic
interface
just
take
text.
C
A
C
Yeah
I
mean
I,
I,
think
I
think
most
the
the
most
common
use
case
and
the
one
we
should
put
the
most
effort
into
supporting
correctly
is
just
plain
text
right,
that's
going
to
be
95
of
uses
of
this
I.
Imagine,
but
then
somebody
might
want
like
an
emoji
or
like
a
cool
icon
afterwards
or
whatever
and
it'll
be
nice.
If
there's
room
to
customize.
A
C
A
Fun
but
previously
discussed
it
would
help
with
LSPs.
D
A
Events
so
Jupiter
events
is
way.
Upstream
of
this
we
will
have
to
have
a
Jupiter
lab
notifications,
server
extension
that
subscribes
to
events
and
then
reads
and
writes
to
a
database
that
is,
for
notification
purposes.
Now
that.
A
That's
right
so
that'll
be
the
back
end
for
a
front
end
that
will
use
this
component
to
show
you
notifications
as
they
arise,
and
also
there
will
be
a
corresponding
notifications
panel
in
your
sidebar,
where
they
collect
right.
So
this
is
one
piece
of
that
notifications
front
end
is
the
toast.
The
other
piece
of
it
is
like
a
little
sidebar
where
you
can
see
the
either
the
more
details
or
whatever
the
next
action
is
or
whatever
you
missed.
When
you
were
out
or
whatever.
C
C
Well,
you
can't
have
a
button
that
that
triggers
arbitrary
command
from
our
Command
palette
right.
D
Yes,
there
are,
there
are
routines
for
making
toolbar
buttons
and
building
a
button
based
from
a
command
using
the
icon
and
the
caption
and
whatever
right,
I
I
don't
so.
We
can
definitely
do
that.
I'm,
not
sure
how
much
of
it
is
directly
reusable
and
how
much.
A
C
Yeah
I
think
I
think
the
thing
or
the
most
packaged
up
thing
that
does
that
currently,
there's
like
component
called
like
toolbar
command
button
or
something-
and
it's
like
specifically
like
a
toolbar
button,
anything
else,
yeah
I
mean
we
just
have
like
a
command
button
type
or
something
more.
Generic.
C
E
Yep,
it's
me
hello,
hello,
I
am
here
to
remind
you
that
this
month,
August
Jupiter
Community
call
will
be
coming
up
next
week.
Tuesday
time
zone
is
in
the
Lincoln
agenda.
I
know
it
is
7.
A.M,
Pacific
I
think
we
have
a
few
things
on
the
agenda,
but
we
definitely
have
space
for
more.
So
if
there's
something
you're
excited
to
share
I
know,
we've
been
cycling
through
times.
Maybe
this
will
be
a
good
time
for
some
people.
Again,
of
course,
though,
you
are
welcome
to
attend
and
not
share
anything
I.
E
Think
all
of
you
have
heard
my
schviel
before
I'm
recognizing
these
names,
but
just
in
case
this
is
kind
of
a
show
and
tell
for
cross
project
in
the
community
where
we
show
off
and
get
excited
about
people's
work,
share
kind
of
big
Community
ideas,
yeah
so
I
hope
to
see
you
all
there
and
I
think
that's
all
I
have.
E
B
Yeah
I
see
August
30th,
7
A.M
I.
E
Mean
this
just
shows
how
absolutely
not
at
all
scrambled
I've
been
lately.
So
thanks
for
catching
that
it's
two
weeks
then
and
I
can't
count.
So
thank
you
so.
B
E
I
can't
figure
out
what's
happening,
I
guess
at
least
there's
some
humor
for
this
recording
there
you
go.
It
was
just
one
extensive
I,
don't
know
some
kind
of
skit,
so
yeah
no
I
was
wrong.
Thank
you,
I
would
have
showed
up
and
then
like
what's
happening,
but
this
is
good.
A
E
E
A
A
Right
would
anyone
else
like
to
talk
about
something
before
we
move
on
to
the
additional
discussion
section.
A
Oh,
you
know
what
there's
16
people
on
the
call
can
I
ask
if
anyone
on
the
call
knows
how
to
and
is
inclined
to,
please
cut
aluminol
to
Alpha.
If
you
don't
know
how
to
that's,
fine
I'll
get
around
to
it
myself,
but
hey
I'm,
all
about
asking
people
for
help
right.
So
no
one
additional
discussion
time.
A
No
discussion
needed
FYI,
IPI,
widgets
eight
is
being
released
this
week,
awesome
well
done.
I
probably
did
18..
Even
if
there's
no
discussion
does
anyone
want
to
describe
it
in
any
more
detail.
A
So
can
I
tell
you
I
want
to
stop
the
recording
right
now,
because
anything
we
say
that's
recorded
is
more
of
a
commitment
than
what
we
say
and
is
not
recorded
about
when
we're
going
to
release
Jupiter
lab
for.
However,
you
know,
let's,
let's
walk
on
the
wild
side.
When
are
we
releasing
Jupiter
lab
4.
A
It's
a
blocker,
but
it's
not
blocking
us,
because
we
have
so
many
critical
path.
Things
for
Jupiter
lab
4
that
are
still
outstanding.
That
I
think
we
can
get
lumino2
in
pretty
quickly
and
the
biggest
pieces
of
that
luminol2
projects
are
accomplished
already
so
I
think
we're
ready
to
do
alphas,
probably
within
two
weeks,
we're
ready
to
do
either
betas
or
RCs
yeah
I.
Don't
think
that
will
be
something
that
holds
cheaper,
lab
4
back,
but
there's
a
lot.
What
was
it?
D
A
A
D
What's
the
next
release
so
I
I
haven't
you
know,
I
haven't
been
triassing
these
issues,
so
I
don't
know,
but
a
lot
of
them
is
follow-ups
to
some
of
the
major
features
that
have
already
kind
of
gone
in
on
the
main
branch
and
definitely
need
doing.
A
I
think
that
Maybe
in
an
upcoming
call
soon
we
should
have
another
triaging
of
those
issues
and
see
whether
they
need
to
be
done
for
4.0
or
they
can
be
for
full
point
x
or
something
else,
and
you
know
I
think
in
terms
of
rough
estimates.
It
is
mid-august
and
I
think
in
the
back
of
my
own
mind,
it's
always
been
we're
releasing
jukebox
for
this
year
and
that
Still
Remains,
my
intuition,
does
anyone
feel
that's
implausible
at
this
point.
A
I
know
we
have
a
lot
to
do,
but
we've
also
got
a
lot
of
things
in
the
refactor
of
the
RTC
stuff
is
very
close
to
Landing,
and
that
was
a
difficult.
That
was
a
difficult
hurdle.
A
It
fixes
a
bunch
of
stuff
and
it
also
removes
some
deprecated
apis.
The
code
mirror
6
work
was
a
big
hurdle
and
that's
in
Jupiter
LSP
was
a
big
hurdle
and
that's
in
they
all
have
knock-on
effects.
A
That's
right,
so
virtual
notebook
is
not
and
yet
right,
it's
still
under
development,
I
think
and
lumino2
is
not
in
yet,
and
you
know,
RTC
has
more
to
do
still,
there's
no
notion
of
events
or
notifications
in
yet.
But,
to
be
honest,
those
are
purely
additive.
If
it
turned
out,
we
can't
ship
with
that
I
wouldn't
hold
up
to
have
four
for
that.
I'd
put
that
in
a
4.1
or
something
so
yeah
I
don't
know.
Does
anyone
else
have
thoughts.
D
I,
as
far
as
my
understanding
is
there
will
be
should
we
should
hope
that
that's
how,
before
but
yeah
there
also
the
notification
and
are
the
events
plus
their
work
is
still
outstanding.
I
think.
A
Yeah,
although
in
that
case
too,
it
might
be
purely
additive,
you
could
imagine
a
2.1
that
has
it
if
we're
simply
trying
to
make
sure
we
deliver
a
minimum,
viable
server
to
lab
for
Notebook
7.
That
won't
have
us
waiting
for
the
next
major
version
to
release
features
that
are
near
Landing,
but
not
quite
there.
So
it
might
be
that
we
can
ship
server
to
and
then
have
events
being
2.1,
but
I,
don't
think
that's
going
to
be
necessary.
I
think
events
is
close
to
Landing.
A
E
C
A
Okay,
it
looks
like
we've
got
nothing
else
on
the
agenda.
Wait
a
minute
before
stopping
the
recording.
No
I
won't
wait
a
whole
minute.
I'll
wait
some
number
of
seconds.