►
From YouTube: JupyterLab Team Meeting - 11 January 2023
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/170
A
Okay,
hello
and
welcome
to
the
January
11th
2023
Jupiter,
lab
weekly
call.
We
got
20
people
on
the
call
which
is
great
and
I,
don't
think
we
have
any
announcements
or
anything
that
happen
outside
of
the
regular
agenda
flow.
So
why
don't
we
just
get
started
first
person
on
the
agenda
today
is
Frederick.
B
Hello,
everybody
sorry
I
just
arrived,
so
I
released
the
release
candidate,
zero
for
Jupiter
3.6
I
still
have
a
it's
not
priority
to
36,
it's
actually,
three
five
and
three
six.
We
have,
as
I
said
last
week,
a
small
issue
if
you
use
Jupiter
server,
V2
and
start
Jupiter
lab
as
a
classical
V6
notebook
extension,
it's
not
working.
B
There
is
some
some
trouble
like
between
the
identity
provider
of
Jupiter,
server,
V2
and
and
the
previous
way
of
dealing
with
authentication
that
makes
it
like
not
working,
so
it
induces
also
some
trouble
on
the
CI
for
some
unknown
reason.
So
normally
we
have
this
Jupiter
browser
check
that
should
like
spin
drift
a
lot
and
check
that
the
the
page
is
loaded
and
then
say:
okay
or
not,
and
for
some
reason
locally
it's
working,
but
on
the
ca
it
was
not
working.
B
I
figured
out
how
to
make
it
working
by
explicitly
adding
the
test
extension.
So
that's
fine
and
the
solution
like
it's
not
really
a
solution,
but
the
proposal
in
the
the
pr
that
is
linked
to
deal
with
the
situation
of
Jupiter
server,
V2
being
not
compatible
with
Jupiter
lab
launch.
As
a
classical
notebook,
V6
is
to
print
a
warning
message
if
you
are
trying
to
do
that
and
even
to
a
board,
if
you
say
that
the
default
URL
is
Jupiter
lab
so
yeah.
B
The
main
idea
here
is
that
I
would
like
people
to
to
comment
on
that
just
to
to
give
maybe
a
bit
more
context,
so
that
doesn't
prevent
orange
Jupiter
notebook
that
doesn't
prevent
or
in
Jupiter
lab
ically.
It's
really
that
specific
case
of
running
Jupiter
lab
as
a
classic
Basics
notebook
extension,
so
it
it
won't
happen
either
when
we
move
to
having
Jupiter
app
for
Android
books,
seven,
the
only
trouble
for
now
it's
really
because
of
binder,
because
actually
binder
is
using
exactly
that.
B
B
Not
yet
I
was
posing
for
trip
into
36,
see
if
people
yeah
to
let
them
people
time
to
digest,
but
then
I
can
move
to
the
next
one.
So
on
the
Jupiter
Forefront
through
the
two
main
Breaking
Chains.
That
needs
to
happen
before
starting
beta
is
still
code,
mirror
6
using
tokens.
I'm
almost
done
with
that
one.
B
The
last
bit
I'm
working
on
this
reworking
the
settings
for
quid
mirror
because,
with
the
tokens
I
added
the
ability
to
be
able
to
to
register
new
code
mirror
extension
and
to
make
it
so
that
you
can
also
register
Json
schema
for
that
new
extension
and
so
that
the
settings
for
the
code
in
your
configuration
is
a
dynamically
generated,
and
also
that
means
that
the
settings
for
notebooks
and
file
editors
are
going
to
be
changed
a
bit.
B
So
basically,
there's
going
to
be
the
settings
for
code,
mirror
6,
that's
going
to
be
the
default
and
then
for
a
specific
document.
Then
you
would
be
able
to
override
some
specific
settings
to
say
like,
for
example,
if
you
say
I
want
to
to
display
the
white
spaces
in
code.
Mirror
editors,
but
I
don't
want
to
see
them
like
in
the
margin
sales
editor,
then
you
will
be
able
to
do
so.
So
by
just
saying
the
default
will
be
true,
but
just
for
the
margins
I
will
say:
okay,
I,
don't
want
to
see
them.
B
B
Item
that
knows,
that
needs
to
be
in
lumino2
before
like
starting
beta
and
RC.
So
if
not
I
propose
to
start
releasing
a
better
version
tomorrow
and
so
that
we
can
next
week
release
Lumina
to
RC
and
that
by
the
end
of
the
month
we
have
the
final
version
of
criminal
2,
and
so
this
would
be
one
box.
We
can
check
for
Jupiter
app
for.
A
I
think
you
can
do
a
beta,
there's
an
outstanding
PR
and
that
PR
modifies
the
API
of
menu
bar,
but
I,
think
and
I.
Think
Mike
also
commented
in
the
pr
itself
that
the
method
being
added
instead
of
it
being
protected,
we
can
safely
make
it
private
so
that
it
doesn't
modify
the
API
and
it
doesn't
block
releasing
a
beta.
A
Now
with
the
Proviso
that
we
get,
that
reviewed
and
into
you
know
beta
2
or
something
is
there
anyone
else
working
on
luminos
stuff
that
they
know
will
change
the
apis
and
need
to
stall
before
we
jump
to
Beta,
because
we've
been
in
the
office
stage
and
everything's
kind
of
been
open
to
modification,
but
once
we
switch
to
Beta
we're
signaling
that
we
don't
want
to
modify
the
apis
anymore,
even
if
we
do
fixes
or
enhancements
or
whatever
I
I
think
we're
okay.
But
anyone
else
on
the
call.
A
Okay,
so
Mike
asks
in
the
chat,
does
beta
block,
adding
new
features,
I
think
it
blocks
modifying
the
API
surface
area.
So
if
the
feature
is
an
end
user
feature
know
if
the
feature
changes
the
API
in
an
additive
way,
it's
probably
okay,
but
you
know,
maybe
let's
not.
If
we
don't
have
to
that's
my
intuition,
I,
don't
know
thread
or
someone
else.
If
you
agree.
A
Okay,
that
sounds
fair.
How
about
how
about
we
do
release
a
beta
this
week,
Mike
if
you
get
that
in
awesome
and
we'll
make
an
exception,
because
this
is
a
thing
that
we
do
really
want
for
shadow
Dom
updates.
But
you
know,
if
you
don't
have
the
time
to
we,
either
change
it
in
an
additive
way
and
do
a
2.1
or
we
just
added
to
the
backlog
and
wait
until
Lab,
5
lumino
3..
A
C
Good
morning,
good
evening,
everyone
two
issues
that
I
wanted
to
bring
to
the
attention
of
the
broader
group
discussed
it
with
some
of
you
folks,
but
I.
Don't
think.
We've
discussed
it
on
this
meeting.
C
There's
a
commercial
open
source
product
called
uffizi
that
spins
up
a
preview
environment
for
every
pull
request
and
from
what
I
can
surmise
uffizi
developers
and
Business
Development
people
have
been
going
all
over
GitHub,
putting
out
pull
requests
saying
hey.
We
think
that
your
project
would
benefit
from
uffizi.
They
also
have
a
license
that
makes
it
free
to
use
in
an
unlimited,
quote-unquote
fashion
for
open
source
projects.
C
I'd
encourage
you
to
take
a
look
at
it.
I
linked
it
I
linked
the
pull
request
from
the
notes.
The
good
news
is
that
it
seems
to
be
much
faster
than
binder.
It
launches
a
an
environment
in
a
matter
of
seconds,
rather
than
many
minutes,
the
downside
appears
to
be
that,
like
the
environment
is
shared
which
allows
people
to
do
potentially
bad
things
to
it.
C
The
good
news,
though,
is
that
the
UFC
person
who
opened
that
pull
request
is
receptive
and
responsive
to
questions
and
comments
about
it.
So
if
you
have
any
questions
or
comments,
please
add
add
it
and
tag
the
person
who
opened
it
so
that
they
can
get
back
to
us.
This
is
something
that
they're
they're
offering
to
make
available
for
no
Financial
cost
to
us,
and
if
the
operations
make
it
work,
I'd
be
open
to
accepting
it
any
questions
about
the
ufitsi
request.
D
You
said
it
was
much
faster
than
binder.
Do
you
know
if
it's
because
they
already
they
are
automatically
pre-build
the
pull
request,
I.
C
D
Okay,
I
was
wondering
how
similar
it
would
be
compared
to
the
existing
git
pod
setup.
D
You
know
we,
some
of
us
use
gitbot,
so
you
can
work
on
Twitter
without
setting
up
anything
locally
and
they
also
have
support
for
pre-builds,
which
means
that
when
someone
opens
a
pull
request,
they
automatically
prepaid
the
like
they
pretty
much
launched
the
initial
tasks
which
in
storage
mode
and
so
on
so
I,
don't
know
like
how
much
overlap
there
is
between
these
two
and
how
much
work
it
would
be
for
us
in
the
long
term,
to
maintain
this
new
configuration
for
UFC
yeah.
C
The
other
thing
that's
of
interest
is
that
uffizi
as
they've
configured,
it
uses
what
they
call
uffizi
Cloud,
which
is
they
host
a
software
as
a
service
solution.
They
also
say
that
you
can
run
the
open
source
software
with
your
own
kubernetes
cluster,
which
sounds
free,
except
for
the
fact
that
then
we
have
to
set
up
our
own
kubernetes
cluster
and
maintain
ufitsi
on
it
and
I
I
I
am
also
shaking
my
head.
I,
don't
know
how?
How
involved
that
is.
C
One
other
thing
that
we
noticed
and
I
believe
this
may
be
mitigated
was
that,
because
there's
a
single
environment
set
up
for
each
pull
request,
there's
a
risk
that,
like
person,
number
one
who
opens
the
environment
could
put
some
code.
That
does
something
malicious
or
ties
of
your
browser
or
displays
some
offensive
information,
and
then
other
people
who
click
through
that
environment
would
see
the
same
thing.
It's
shared
I
I
saw
a
comment
saying
that
they
I
believe
were
at
least
trying
to
mitigate
it.
A
So,
just
looking
at
the
pr
that
you
linked
it
is
you've
been
engaging
with
this
and
Jason
grout
has
been
engaging
with
this.
Do
you
have
a
recommendation.
C
I,
don't
we
also
had
a
brief
discussion
on
the
mailing
list
for
the
Jupiter
lab
Council,
but
I
believe
it
was
Jason
groud
who
suggested
that
we
we
broaden
this.
We
don't
just
keep
this
like
via
private
email.
We
we
have
this
discussion
more
out
in
the
open
and
so
I
don't
have
a
conclusive
recommendation
for
it.
I'd,
like
other
folks,
to
check
it
out
and
ask
about
risks
or
questions
that
you
have
I
don't
know
if
Jason
grout
has
anything
to
add
beyond
that.
E
Yeah
I
think
the
one
thing
I
would
say
is:
if
someone's
excited
about
championing
this
in
Jupiter
lab
and
maintaining
sort
of.
If
there's
a
problem
contacting
the
company,
Etc,
then
I
think
it's
a
go.
If,
if
there's
nobody
willing
to
sort
of
maintain
this
from
within
Jupiter
lab
and
the
fact
that
we
had
that
weird
concerning
thing
about
the
the
data
being
left
over
from
one
try
to
the
next
try
which
I
assume
helps
with
their
speed,
then
it's
probably
not
the
right
solution
for
us.
E
So
the
I
think
a
question
on
the
call
is:
is
there
someone
willing
to
champion
this
or
maintain
it
essentially,
and
it
may
be
very
easy
and
the
company's
pretty
excited
to
help
out
it
may
be
just
it
always
works
and
there's
nothing
to
do.
E
C
I
mean
logically,
it
would
be.
Whoever
has
set
up
like
the
binder
stuff
should
consider,
would
would
you
you
know
how
do
you
feel
about
potentially
retiring
the
binder
integration
in
favor
of
the
uffizi
integration,
because,
right
now,
binder
is
costing
us
money.
We
have
to
get
sponsors.
People
on
this
call
or
or
elsewhere
in
the
organization,
have
to
go
solicit.
Sponsors
uffizi
would
become
effectively
a
volunteer
sponsor
for
this,
for
as
long
as
they
support
the
open
source
offering
which
I
hope
is
a
really
long
time.
E
Else,
oh
so,
since
there's
no
hands
up
and
then
I
propose
a
Way
Forward
is
to
post
on
I
know,
there's
several
issues
in
PR's
open
sort
of
around
this.
So
it's
not
clear
exactly
where
the
single
point
of
contact
for
this
is
but
let's
post
on
there-
and
you
know
say,
is
anybody
willing
to
maintain
this
integration
and
if
nobody
responds
to
be
to
be
willing
to
maintain
the
integration,
then
then
there's
our
answer
so.
C
The
UFC
regret
request,
probably
the
well
the
there's,
an
issue
linked
from
that
pull
request,
which
was
which
was
also
opened
by
a
New
feedsy
Biz
Dev
person.
So
we
can
open
another
one
or
just
Co-op
that
one.
Let's.
C
Okay,
one
other
thing
this,
so
today's
January
11th
node
14,
is
reaching
end
of
life
on
April
30th
of
this
year
and,
to
my
surprise,
node
16
is
reaching
end
of
life.
Eight
months
from
today
on
the
11th
of
September,
normally
node
long-term
support
releases,
which
are
even
numbered,
reach
end
of
life
on
April
30th,
node
16,
because
of
one
of
its
dependencies
has
been
moved
up
significantly
so
long
story.
C
and
I
opened
similar
pull
requests
on
some
other
areas
where
I
found
it
like
in
the
cookie
cutter.
So
my
request
is
to
take
a
look
at
that
issue
to
this
I
believe,
there's
a
pull
request.
At
least
one
pull
request
open
related
to
that
and
if
you're
able
to
try
upgrading
to
node
18
as
early
as
possible,
node
20
is
coming
out
later
this
year,
but
it's
not
yet
available.
C
I
think
it's
like
in
development
still,
but
trying
to
get
ahead
of
this
before
we
end
up
inadvertently
supporting
an
end-of-life
product.
C
No
problem,
yeah
I,
actually
saw
some
reports
to
node
12.
Some
some
prefer
some
references
to
that
version,
which
left
support
last
year.
Node
tends
to
move
pretty
fast
as
web
Technologies
do
through
its
life
cycle.
So
even
the
long-term
support
one
only
lasts
for
a
couple
years.
A
A
Okay,
I
had
an
an
update
on
governance.
So,
as
you
know,
last
month
we
had
the
Jupiter
executive,
Council
election
and.
A
We
took
a
while
to
finalize
the
results,
because
we
don't
yet
have
a
standing
committee
to
handle
resolution
of
potential
conflicts
of
interest.
That
is
a
standing
committee.
That's
written
into
the
governance
that
will
have
to
create,
but
since
we
didn't
have
one,
we
ourselves
were
responsible
for
handling
it
and
the
way
we
chose
to
do
it
was
once
we
had
tabulated
the
votes
and
knew
the
three
new
members
who
had
won
in
the
election.
A
But
that
being
said,
we
now
have
all
six
members
of
the
Jupiter
executive
Council.
So
the
three
initial
people
who
were
running
the
election
were
me
and
Brian
Granger
and
Fernando
Perez,
and
now
we
have
three
new
members:
Jason
growl,
Steve,
Sylvester
and
Anna
robocaba,
and
we
also
have
SSC
representatives
for
every
single
Jupiter
sub
project.
A
Now
so
one
of
the
first
things
we
are
doing
in
the
executive
council
is
trying
to
find
a
time
when
every
single
SSC
representative
or
almost
everyone
can
join
so
that
we
can
kick
start
the
software
steering,
console
and
re-invigorate
and
restart
the
Jupiter
enhancement
proposal
process,
because
that
is
one
of
the
main
things
the
software
steering
Council
will
be
doing,
and
Jupiter
no
longer
has
benevolent
dictator
for
life.
He
stepped
down
voluntarily
and
Jupiter
no
longer
has
a
steering
Council
that
has
been
disbanded.
We
are
officially
in
the
new
governance
era.
A
A
G
Yep,
so
I've
got
a
PR
out
that
fixes
the
extension
tutorial,
so
this
fixes
some
bugs
that
were
showing
up
related
to
panel
opening
and
closing,
so
those
bugs
shouldn't
be
fixed.
That
was
based
on
Michael
krasowski's
fix
for
that.
So
thanks
to
him
and
that
that
PR
also
includes
a
bunch
of
other
minor
revisions
and
improvements
to
the
tutorial
and
then
also
I
recreated
the
reference
repository.
G
So
users
can
compare
their
code
to
a
reference
repository
at
different
stages,
so
I
I
wasn't
sure
the
best
way
to
do
that,
but
I
I
have
that
repo
with
the
code
at
different
stages.
So
the
the
current
document
links
to
the
new
repository,
which
is
just
my
repo
one
of
my
repositories,
so
I
didn't
know
what
everybody
thinks
is
the
best
way
to
do
this,
but
I
can
either
transfer
this
to
the
Jupiter,
org
or
I.
G
Don't
know
how
this
would
work,
but
that
I
guess
that's
an
open
question
that
I
have.
But
if
anyone
can
review
the
pr
and
then
I
guess
tell
me
what
to
do
with
this
reference
repository
and
let
me
see
I
think
I.
Think
my
other
question
was
answered
by
Frederick,
but
yeah,
so
I
have
the
pr
and
then
also
I
I,
wanted
to
update
the
developer
guide,
possibly
to
capture
a
little
bit
of
the
information
about
how
the
docs
get
updated.
G
So
I
have
an
eye
toward
doing
that
at
some
point
too.
So,
if
anyone
has
suggestions,
let
me
know.
A
So
in
the
Jupiter
lab
github.org,
the
Jupiter
lab
underscore
apod
repo
is,
is
your?
Is
your
reference
repo?
Is
it
appropriate
to
just
do
a
big
PR
against
the
Jupiter
lab
repo
for
this
extension
or
no.
G
Well,
yeah
I
was
wondering
about
that.
So
I
don't
know
what
access
I
need
to
have
anyway,
for
that
so
I
just
recreated
it
in
a
clean
repository.
It's
it
is
a
bit
tricky
because
I
think
right
now
there
are
different
versions,
so
I
don't
know
if
I
should
be
doing
a
PR
against
that
or
if
I
should
or
if
it's
better
to
just
make
a
clean
repository,
because
I
think
it
only
has
a
few
commits
and
they
correspond
directly
to
different
stages
in
the
tutorial.
G
So
I
don't
know
if
that's
a
a
benefit,
that's
worth
preserving
or
not,
I,
don't
know
what
you
guys
think.
B
B
With
any
history,
without
any
story
so
that
the
user
cannot
get
lost
in
older
version
or
whatever
foreign.
G
A
B
Transferring
it
is
easy,
but
if
you
want
I
will
I
will
I
can
take
your
code
and
then
bring
it
in
the
official
one.
It
would
be
probably
easier
so
that
we
keep
the
branch
for
the
older
version
of
Jupiter
lab.
E
E
Release
notes
include
a
section
about
updating
the
the
example
and
I
think
you
can
just
follow
those
notes
to
update
the
example
so.
A
E
We
iterated
it
Steve,
probably
wrote
the
first
person
and
then
every
time
I
think
it
was
updated.
The
document
was
iterated.
Obviously
you
can
look
in
the
history
of
this
document.
B
If,
if
you
want
to
give
a
try
Eric,
what
you
can
do
is
just
to
Grant
you
the
the
right
on
that
extension.
If
you
want
to
create
to
trade
like
on
another
Branch,
not
maybe
three,
three,
oh
and
then
when
we
are,
when
you
feel
confident,
then
we
can
rename
the
branch
to
be
the
new
3.0.
Something
like
that.
G
Good,
that's
a
good
question.
Okay
Frederica
can
I
ping
you
on
on
gitter,
possibly
today.
B
E
Good
and
and
can
I
just
add
again,
we've
been
iterating
on
these
instructions.
If
you
end
up
using
the
instructions
and
the
release
notes,
if
there's
something
that's
confusing,
please
reach
out,
and
if
there's
something
that
you
think
would
be
useful
to
somebody
else.
The
next
person
doing
this
please
modify
and
iterate
and
add
to
those
instructions.
F
Cool
yeah
just
wanted
to
say,
there's
a
first
accessibility
meeting
of
the
year
after
this
15
minutes.
After
the
next
hour,
10
15.
PST
oops
see
some
of
y'all.
There.
A
Sweet
thanks,
okay,
so
we
do
have
an
item
in
additional
discussions
before
that.
Is
there
anything
anyone
wants
to
talk
about
that
is
not
on
the
agenda
but
could
have
been
I'll.
Give
you
a
second.
F
A
So,
on
the
additional
discussions,
we
have
a
note
about
the
notebook
file
format,
Jupiter
Workshop,
who
added
it,
and
what
would
you
like
to
say
about
it.
B
As
the
organizer
for
the
workshop
just
to
to
tell
people
that
we
have
postponed
the
deadline
for
applying
to
the
workshop
on
next
Monday
and
we
will
also
organize
a
remote
capability.
So
if
people
that
are
especially
in
America
is
it's
in
Paris
I
want
to
join
remotely,
it
will
be
possible.
Of
course
there
is
always
the
trouble
with
the
time
zone
and
other
than
that,
the
there
is
already
a
couple
of
private
stakeholders
that
are
coming
from
different
European
country,
a
bit
less
from
us.
B
So
if
you
want
to
discuss
the
format,
there's
going
to
be
like
people
are
really
interested
in
in
extending
some
notion
for
cells
and
structure
of
the
the
Jason
like,
for
example,
to
be
able
to
read
the
metadata
quickly
without
reading
the
old
content
stuff
like
that.
So
there's
gonna
be
interesting
discussions
if
you're
interested
I,
hope,
I,
yeah,
I
I
put
the
link
for
to
the
form
don't
hesitate
to
to
register.
B
A
Yeah,
so
that
that
is
also
linked
in
the
notes.
The
dates
are
February
28th
to
March
2nd,
and
the
other
date
you
need
to
know
is
that
you
have
five
days
until
the
deadline
elapses
for
going
great
awesome.
A
Okay,
just
I
guess
one
last
call
if
there
is
no
one
I'm
going
to
stop
the
recording,
but
I'll
wait
a
second.