►
From YouTube: JupyterLab Team Meeting - 15 February 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
Hello
and
welcome
to
the
February
15th
weekly
Jupiter
lab
call.
Today
we
have
20
people
on
the
call
and,
despite
that,
we
have
a
poultry
two
people
on
the
agenda
so
far.
So
if
there's
anything
you'd
like
to
talk
about
your
audience
to
speaker
ratios
pretty
good,
but
with
that
why
don't
we
get
started
Fred?
You
are
up
first.
B
Yeah,
sorry,
there
is
lots
of
bullet
points.
Let's
get
started.
The
first
question
is
in
related
to
Egypt
era.
Before
so.
For
now
we
have
for
this
better
version
of
Lumina
2
and
there
hasn't
been
any
major
PR
breaking
or
bringing
new
API
or
breaking
some
API
like
lately
so
I
have
a
question.
Is
that
is
it
okay
to
move
on
and
to
the
release?
Candidates
did
would
be
to
to
have
the
final
release
of
amino
2.
B
A
So
that
PR
in
the
chat,
I
think
is
ready
to
go.
There
was
a
bug
in
it,
but
I
think
Stephanie
has
pushed
a
fix
for
it.
I
don't
know
if
other
people
who
are
reviewing
it
have
anything
to
say,
but
it
actually
looks
pretty
ready
so
I'm
going
to
take
one
last.
Look
at
that,
so
we
can
get
that
into
SRC,
but
if
it
turns
out
there
was
something
else
up.
We
can
just
put
that
in
rc2,
so
it
shouldn't
it
doesn't
block
an
rc1
I,
don't
think.
Does.
A
Any
luminal
things
that
they're
aware
of
oh.
C
A
A
Sounds
good,
so
Mike
is
the
scrolling
of
tab
bars
one
and
API
change.
Are
you
happy
for
it
to
well
actually
yeah.
E
A
The
question
is
one
week
notice
to
try
to
get
that
in
Fred.
What.
F
A
It
was
the
date
you
had
in
mind
to
do.
Nrc.
B
Oh
I,
I
did
not
have
specific
date
in
mind,
like
I
was
more
about
like
the
sooner
the
better
but
depending
on
what
people
are
important
subject
that
are
left
on
the
table,
but
to
wait
a
week
and
then
do
the
RC.
It's
it's
fine
for
me,
I
mean
and
then
that's
mean.
The
final
would
be
like
big
enough
of
March.
I
won't
be
able
to
do
it
first
of
March,
but
so
I
mean
it's
still.
Fine.
A
Okay,
yeah,
why
don't
we
pick
that,
then?
If,
if
that
seems
to
I,
don't
like
get
what
he
wants
to
end,
and
that
gives
a
few
days
for
Stephanie
to
get
her
test
in
and.
E
B
To
set
one
day,
I
would
say
the
ETA
is
like
March
like
in
a
week
from
now
March
22nd
February.
A
B
So
the
next
one,
so
maybe
I
will
read
the
comment
of
Jason
thanks
for
commenting
directly.
The
question
was
about
what's
the
process
to
Grant
triage
rights
to
new
people,
because
we
have
France
from
constack
that's
interesting
to
to
get
those
rights,
so
apparently
Jason
say
in
the
past
it
was
pretty
liberal.
B
So
if
there
is
no
objection,
then
I
will
grant
forums
the
right
and
if
somebody
then
in
the
cold
is
interested
to
get
them
then
feel
free
to
just
comment
right
now
or
ping
me
and
I
can
grant
you
in
the
same
rights
for
information.
Triage
rights
mean
that
you
can
update
metadata
on
issue
in
PR
and
I.
Think
it's
just
that.
A
Yeah
in
the
past,
basically
anyone
who's
asked
to
triage
we've
gladly,
given
them
the
right
to,
because
it's
something
that's
helpful.
Does
anyone
have
a
Counterpoint,
an
objection,
foreign.
B
Okay
thanks
and
then
next
point,
so
we
have
moved
and
I
didn't
put
more
information
just
in
the
pr.
So
we
have
moved
the
code
for
collaboration,
UI
element
into
the
Jupiter
server
away
doc
package,
so
the
the
repository
that
was
containing
the
back
end
code
and
that
has
been
moved
to
jupyter
lab
organization.
B
B
So
I
was
discussing
with
Carlos
and
we
were
thinking
like
to
rename
the
package
Jupiter
lab
collaboration
and
then
David
blandin,
saying
okay.
Maybe
it
should
be
called
Jupiter
collaboration.
So
the
main
question
is
like
that.
B
Let
me
write
that
David
brought
is
like,
should
it
be
called
more
Jupiter
lab
or
Jupiter
corroboration,
and
the
main
arguments
of
David
was
to
say
that
it
was
not
specific,
like
the
python
code
was
not
specific
to
Jupiter
lab
I.
Think
it's
also
like
bring
maybe
a
more
generic
question.
No
that
notebook
7
is
coming,
should
those
kind
of
extension
that
are
basically
targeting
both
Jupiter
lab
and
notebook
be
called
like
Jupiter
or
something,
or
should
we
call
them
Jupiter
lab
as
their
first
targeting
Jupiter
lab
yeah.
That's
that's
the
question.
B
A
A
Oh
any
other
comments
on
package.
I
guess
people
are
commenting
in
the
chat
and
not
understanding
the
agenda
and
also
the
issue
is
a
good
place,
but
should
we
move
on
to
the
build
tools.
B
Yeah
sure
so
that's
a
question
that
has
been
raised
in
the
past,
but
with
the
release
of
Jupiter
3.6
Darth.
There
are
some
people
that
are
have
trouble,
because
Jupiter
lab
is
needed
for
building
the
package
like
when
you
are
doing
a
pre-built
package
and
as
in
36,
we
introduced
dependency
on
a
rest
compiled
code
package.
Some
author
extension
author
got
into
trouble
to
package
their
own
extension,
although
they
don't
need
that
dependency,
because
that
rest
dependency
is
used
for
RTC.
B
B
B
The
main
consequence
is
just
that
we
will
keep
having
a
heavy
dependency
for
Downstream
extension
author
to
package,
Builder
extension,
so
yeah,
that's
that's
the
only
that's
the
only
thing
and
and
depending
on
what
we
do
with
the
RTC
code
that
we
have
extracted
depending
if
we
keep
it
as
a
as
a
dependency
by
default
or
not,
we
will
still
have
the
like
those
kind
of
trouble
with
the
dependency
that
are
that
relies
on
rest,
compile
code
and
so
that
are
not
available
on
some
architecture.
G
Yeah
so
I,
just
it's
not
very
constructive,
but
one
thing
to
be
careful
of
this.
If
you
do
make
this
an
ex
separate
extension,
you
have
to
care
about
both
backwards
and
forwards
compatibility
right,
because
if
somebody
has
an
extension
that
they
originally
built
for
Jupiter
lab
3.2
and
Jupiter
lab
3.4
comes
out
and
then
something
changes
in
the
Builder.
G
Then
they
also
they
need
they
need
us
an
additional
pin
in
their
setup
right.
They
need
to
pin
diversion
potentially
of
the
Jupiter
lab,
build
tools
or
if
they
don't
have
a
pin,
we
need
to
make
sure
that
that
package
is
both
forwards
and
backwards
compatible
yeah,
that's
that
is
really
true.
It's
producing
extensions
that
are
forward
compatible,
but
that
its
API
is
backwards
compatible.
That's
that's,
I,
think
the
the
way
to
look
at
it,
but
yeah
it's
a
little
bit.
B
A
E
I
want
to
derail
the
larger
discussion
of
extracting
the
build
tools,
but
just
to
address
the
Upstream
issue
where
the
the
rust
compiled
code,
the
Wi-Fi
Library,
didn't,
have
wheels
for
those
other
architectures
I've
kind
of
fallen
into
helping
the
the
CI
on
the
Wi-Fi
repository
I
initially
was
just
interested
in
Wi-Fi
in
the
wasm
realm
and
then
jumped
in
to
try
and
get
CI
working
for
these
their
architectures
like
the
amd60
or
Arch
64..
E
It
has
been
very
slow
to
iterate
on
CI
changes.
So
if
anyone
knows
you
know
who
has
maintainer
on
the
ycr
DT
Wi-Fi
repo,
if
we
could
get
some
other
cheaper
lab
contributors
able
to
merge,
PRS
and
release
on
Wi-Fi,
that
would
help
with
iterating
on
adding
other
architectures
or
building
wheels
for
other
architectures
when
necessary.
Okay,.
B
Thanks
and
so
maybe,
first
to
answer
vdar
and
the
tool
I
think
it's
mainly
python,
like
python
that
are
using
subprocess
and
because
the
Builder
package,
the
npm
package,
is
less
controversial
in
the
sense
that
you
can
always
download
it
from
npm
directly.
B
G
B
B
H
Hey
everyone:
last
week,
I
released
the
new
version
of
YouTube
to
love
desktop,
and
this
was
a
major
upgrade.
I
had
done
a
demo
like
three
weeks
ago
here
and
this
version
introduced
a
lot
of
new
features
and
the
major
Focus
was
on
the
user
experience
and
making
it
more
user
friendly
and
I
announced
it
with
a
blog
post
and
and
the
tweet,
and
there
was
a
lot
of
great
interest,
a
lot
of
Praises
on
the
social
media
and
I
shared
some
stats
on
the
meeting
notes
and
yeah.
Please
check
it
out.
D
H
D
Just
a
brief
highlight
to
an
issue
so
with
the
release
of
Jupiter
White
Oak,
which
was
extracted
and
Jupiter
lab
collaboration.
D
We
have
a
little
bit
more
difficult
situation
for
developers
of
extension
developers
and
co-developers
because
the
API
segmentation
reference
is
not
inevitable.
It
cannot
click
on
items
which
are
in
different
packages.
Different
repositories
and
I
opened
an
issue
to
discuss
how
we
could
interconnect
through
the
documentation
from
what
league
has
investigated.
A
A
Okay,
well,
hopefully,
we
can
fix
this
box
soon,
because
this
is
super
annoying.
So
thanks
for
working
on
it.
F
Thanks
I
just
have
a
quick
thing.
Gabriel
couldn't
make
the
meeting
today,
but
I
know
he's
been
working
on
some
adjustments
to
focus
State
and
Jupiter
lab.
He
said
that
PR
is
ready
for
review
again,
so
I
am
simply
the
messenger.
Today,
thanks.
A
I
mean
you
don't
have
to
answer
now,
but
review
it.
Please.
If
you
are
inclined
okay,
Jason
W,
you
are
up.
A
Let's
see
it
says:
oh
I
see
that
that's
Preamble
for
issue
triage
at
the
bottom
yeah,
so
I
guess
before
we
jump
into
this.
Anyone
have
anything
else
that
I
could
talk
about
if
you'll
recall,
because
we
have
the
feature
freeze
on
the
28th.