►
From YouTube: JupyterLab Team Meeting - February 23, 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+
B
Yeah,
as
some
of
you
may
know,
we
have
a
jupiter
community
building
committee
that
was
formed
at
the
end
of
last
year
to
take
over
or
to
formalize
the
organization
of
the
jupiter
community
workshops
and
jupiter,
con,
etc,
and
and
look
at
community
events
in
general
and
one
of
our
first
tasks.
B
So
this
committee
is
sylvan
corley
on
ruffle
kabba
and
myself
for
now,
and
one
of
our
first
tasks
was
to
find
a
person
that
could
help
manage
events
and
and
create
events
and
help
the
community
event
process
and
we
were
lucky
to
find
gail
arlington
who's
here
on
our
call.
She
just
joined
num
focus
to
work
on
jupiter
community
events,
just
I
think
a
week
or
two
ago,
and
so
with
that
I'll.
Let
gail
introduce
herself.
C
Yes,
thank
you
jason.
Yes,
I
I
think
today
is
day
11
for
me,
so
my
name
is
gail
arlington
and,
as
jason
just
mentioned,
I'm
I
am
the
new
community
events
manager.
So
I
have
about
a
little
over
16
years
of
experience,
corporate
freelance
entertainment
and
and
nonprofit,
but
but
I
I
I
really
love
I'm
fueled
by
bringing
passionate
communities
together
and
having
a
shared
experience,
and
so
I'm
really
really
looking
forward
to
getting
to
know.
C
You
know
the
jupiter
community
and
I'm
going
to
be
working
on
the
jupiter
con.
So
I'm
going
to
have
a
blog
post,
that's
going
to
be
coming
out.
C
Hopefully
next
week
is
what
I'm
hoping
and
that
is
going
to
be
a
poll,
and
so
I'm
pulling
the
community
about
jupiter
con
just
to
see
where
everyone's
comfort,
level
and
interest
is
so
keep
a
lookout.
For
that
and
just
a
little
background,
I
used
to
walk
people
through.
I
used
to
run
kind
of
the
a
to
z
of
curriculum
events.
That
was
my
last
job
for
at
the
university
of
texas.
C
So
I
used
to
help
people,
you
know,
do
the
zoom,
how
to
record
and
how
to
do
transcripts,
and
so
I
I
was
holding
myself
back
from
like
giving
you
the
the
lightning
talk
on
it.
But
I
really
am
thankful
for
allowing
me
to
take
a
few
seconds
to
introduce
myself
and-
and
thank
you
again
so
I'm
excited
to
be
here.
D
A
Unfortunately,
I
see
that
mike
is
not
there,
but
mike
has
opened
an
issue
that
I
have
linked,
but
mainly
the
keyboard
shortcut
being
destroyed
in
the
sense
that
when
you
are
opening
the
settings
editor
automatically
saving
them,
so
that's
mean
dumping
all
the
list,
as
the
user
settings
mike
is
considering
that's
a
blocking
issue
for
3.3,
I
looked
at
it.
The
main
trouble
is
this
is
one
of
those
settings
that
get
a
transformation,
so
that
means
the
user
settings
are
merged
with
the
default
one
and
that's
not
the
classical
behavior.
A
Let's
say
of
a
settings
jupiter
app,
so
I
was
looking
at
it
to
figure
out.
What's
the
best
way
to
fix
it,
and
I
see
two
paths
either
it's
to
allow
another
transformation
in
this
settings,
plugin
itself
prior
to
saving
or
the
other
way
would
be
to
say
when
you
are
registering
a
specific
setting
editor
for
plug-in.
You
can
also
define
a
transformer
to
be
applied
to
the
to
the
data
before
saving
them,
and
I
don't
know
what
which
approach
would
be
the
best.
A
One
thing:
that's
both
for
me
a
bit
with
the
adding
the
transformer
inside
the
settings.
Plugging
directly
is
that
those
transformers
they
are
their
signature
for
now
is
I
receive
a
plugin
and
I
give
back
another
the
same
plugin
but
transform,
and
maybe
it's
not
such
a
great
api
for
just
saying,
okay,
I
want
to
transform
the
the
data
that
I
want
to
save
so
yeah
yeah
nick
there
are
lists,
so
that
makes
it
messy
when
trying
to
figure
out.
A
A
E
F
H
Just
a
quick
update
for
me
as
a
follow-up
to
I
can't
remember
it
was
last
week
or
two
weeks
ago,
where
martha
jason
and
I
volunteered
to
submit
a
talk
for
what's
new
in
jupiter
lab
to
sci-fi,
we
submitted
that
so
we'll,
hopefully
hear
back
from
them
soon.
Martha
is
also
looking
into
doing
a
tutorial,
so
she
and
I
are
collabing
on
that
and
jason
may
or
may
not
also
pitch
in
yeah.
If
people
are
interested
in
that,
should
they
reach
out
to
you
martha.
I
Sure
yeah-
and
I
I
don't
know
if
you
said
what
the
tutorial
would
be
on
it-
was
like
developing
extensions
for
jupiter
lab,
which
I
did
a
tutorial.
I
think
in
2020
at
jupiter
con.
That
was
on
that.
So
I'm
planning
on
repurposing
a
lot
of
that
but
yeah.
If
anyone
wants
to
be
involved,
feel
free
to
reach
out
to
me
on
twitter.
H
I
think
timing
wise
the
last
time
we
did
the
tutorial
it
was
prior
to
pre-built
extensions.
So
a
lot
of
our
prior
recordings
aren't
exactly
applicable
anymore.
G
I
think
it
would
be
great
to
see
if
we
could.
We
could
even
show
how
to
make
an
extension
for
notebook
v7
in
that
case,
because
that
would
just
be
the
same
process.
G
H
J
Okay,
hi
good
morning,
good
afternoon,
good
evening,
everyone.
So
I
have
a
couple
topics
I
wanted
to
discuss.
One
is
a
pull
request
that
I've
had
open
for
a
little
while
that
has
some
work
in
progress,
changes
for
a
cell
toolbar,
and
let
me
see
if
I
can
share
my
screen,
really
quick
to
do
a
small
demo.
So
this
is
a
binder.
The
link
is
in
the
hack
md
in
case
anyone
wants
to
mess
with
it
live
while
we're
watching.
J
So
the
idea
is
that
we've
got
this
small
toolbar
adapted
from
frederick's
work
on
the
enhanced
cell
toolbar,
that's
on
every
cell,
so
you
can
move
things
down
or
up.
Add
a
new
cell
above
or
below
delete
a
cell
or
copy
it
to
the
clipboard
and
in
response
to
some
of
the
early
testing,
the
toolbar
does
not
appear
if
there's
any
overlap,
however,
this
is
only
detected
once
when
you
initially
focus
the
the
cell.
So
if
I
type
a
new
cell-
and
I
and
I
add
something
like
like
this.
J
So
the
the
toolbar
is
not
monitored
live,
but
when
I
refocus
this
it
doesn't
appear
so
I
spent
some
time
yesterday
kind
of
working
on
some
concepts
to
monitor
in
real
time
which
either
didn't
work
or
had
a
major
negative
effect
on
performance.
J
So
folks
are
any
ideas
about
how
to
listen
for
events.
I
think
I
also
opened
a
discourse
thread
about
this
as
well,
which
I
can
link
from
the
page
and
then
also
I
notice
there's
an
interesting
quirk
in
that
all
rendered
markdown.
Well,
actually,
no,
not
all
rendered
well.
Now
I
think
all
rendered
markdown
will
be
rendered
with
the
full
width,
and
so
I've
just
suppressed
the
overlap
detection
for
now
for
rendered
markdown.
But
clearly
we
want
to
work
on
that
as
well.
J
Oh,
someone
found
my
discourse
thread.
Thank
you,
so
yeah,
please
feel
free
to
play
around
with
this
seeking
feedback.
We
discussed
it
with
some
other
folks
last
week.
Still
a
work
in
progress.
I'd
call
it
alpha
right
now,
but
if
you
find
any
weird
bugs
that
I
haven't
please
let
me
know
one
other
aspect
I
wanted
to
discuss
with
the
group.
Is
we
moved
the
triage
meeting
from
9
a.m,
pacific
to
10
a.m,
pacific
on
thursdays
last
week,
so
that
the
server
meeting
could
include
a
collaborative
hour
at
9
00
a.m?
J
As
a
result
of
that,
the
triage
meeting
participation
went
down
a
lot
because
our
friends
in
europe,
that's
even
later
and
for
folks
on
the
west
coast,
that's
getting
into
scrum
hour.
So
I'm
wondering
if
we
should
continue
to
have
the
triage
meeting,
because
I
felt
like
last
wednesday
we
did
a
bunch
of
triaging
towards
the
end
of
this
meeting.
We
had
much
better
participation.
D
Ux
wise,
I
mean
it's
kind
of
anti-feature
right
because,
like
when
there's
content
in
the
cell-
and
you
want
to
like
copy
that,
I
mean:
could
this?
Could
you
change
it
to
be
not
inside
the
cell
but
outside
the
cell
kind
of
like
a
a
toolbar
that
hovered?
So
if
you
like
hover
over
the
cell,
it
would
appear.
J
We
have
done
that
in
the
past.
I'm
not
sure
is
brian
on
the
call
go
ahead.
Yeah
brian
and
I
we're
kind
of
going
back
and
forth
about
some
concepts
here.
K
Yeah,
the
the
biggest
so
there's
a
couple
different
factors
that
we're
looking
at
one
is
over
over
a
very
long
period
of
time.
The
last
decade
users
have
communicated
very
strongly
that
they
don't
want
more
space
between
the
cells
in
a
notebook
that
it's
critical
for
them
to
see
as
much
code
as
possible,
and
so
one
of
the
design
constraints
that
jason
had
for
this
was
no
additional
new
space
in
new
cells.
K
He
did
have
an
initial
version
that
put
the
cell
put
the
cell
toolbar
overlapping
with
the
top
border.
The
challenge
is
that
the
cells
are
close
enough.
It
gets
really
hard
to
tell
which
cell
that
toolbar
is
attached
to
and
the
further
up
you
move
it
the
less
clear
it
gets
the
further
down.
You
move
it.
It
still
overlaps
with
the
content
in
the
cell,
so
it
it
felt
like
an
unwinnable
trade-off.
K
K
When
you
do
that,
a
toolbar
above
yeah,
you
basically
have
to
add
borders
drop
shadows
to
make
it
distinguishable,
and
we
felt
like
that
also
added
visual
clutter.
So
those
were
the
factors
we
can
certainly
show.
If
jason
can
post
mockups
that
we
did
for
the
other
scenarios
we
may
want
to
make
this
configurable,
though
there
may
be
enough
yeah
that
that
may
be
a
factor.
K
K
Yeah
our
our
plan-
and
I
think
it's
a
separate
question-
is
to
put
some
sort
of
control
there
that
allows
a
user
to
run
the
cell
yep
pretty
common
in
a
number
of
other
notebook
implementations,
but
we
just
haven't
gotten
there
yet.
J
Yeah
and
in
fact,
already
implemented
by
frederick's,
enhanced
cell
toolbar,
frederick
called
it
helper
buttons,
and
I
kept
that
code
in
there
so
that
we
can
add
that
in
later
we
also
talked
about
adding
a
a
plus
button
for
a
new
cell
near
that
area.
But
that's
that's
been
removed
for
the
time
being.
K
The
other
factor
that
we
used
here
is
this
comes
from
the
the
work
that
adam
rule
and
others
have
done
in
analyzing.
Notebooks.
Is
that
if
you
look
across
all
notebook
public
notebooks
on
github,
most
cells
are
code
cells.
I
forget
the
exact
percentage,
and
so
we
felt
like
it.
K
It
was
more
important
to
put
new
cell
interactions
that
were
focused
on
code
and
trying
to
do
markdown
and
code,
and
it
you
end
up
with
a
lot
of
visual
clutter
when
you
try
to
put
too
much
and
so
we're
trying
to
walk
that
balance.
But
we
realize
different
users
may
have
different
preferences
on
that.
J
Yeah
thanks
everyone
for
adding
your
feedback
in
the
the
hack,
md
notes.
L
One
not
trying
to
bike
shed,
but
just
one
idea
that
we
had
thrown
around
in
co
lab
that
may
be
relevant
here.
You
know
the
the
it
seems
like
the
current
placement
is
good.
The
only
issue
is
that
if
you
were
gonna
have
text
over
there
where
the
toolbar
is,
you
know
obviously
the
two
obscure
one
another.
Did
you
ponder
something
we
talked
about
and
didn't
do
was
making
it
so
that
it
was
usually
transparent.
L
But
when
you
got
close,
it
became
more
opaque
so
that
by
default
you
could
still
see
through
it.
And
you
know
I
mean
it's
not
perfect,
but,
like
you
can
basically
see
what's
going
on
over
there.
You
know
all
of
these,
as
you
say,
are
trade-offs
but
like
that
was
one
that
we
did
not
explore,
but
like
at
least
tossed
around.
So
you
know
yeah.
J
The
mvp
craig
is
that
we're
just
going
to
hide
it
completely
because
the
cell
toolbar
is
not
strictly
necessary.
This
is
like-
and
I
say
this
without
disrespect.
This
is
the
v2
concept
is
to
have
some
way
of
like
making
it
duck
out
of
the
way
we
want
to
make
sure
it's
discoverable
accessible,
visible,
all
the
other
good
things,
while
also
not
being
obtrusive,
which,
as
anyone
who's
worked
in
front
end
development
knows,
is
practically
turing
award-winning
to
get
totally
right,
so
we're
going
to
continue
to
iterate
on
this.
J
F
Maybe
a
shortcut
in
command
mode
that
toggles
it
on
and
off
so
that
you
could
trivially
bring
it
back
explicitly,
even
if
it's
turned
itself
off,
but
I'm
not
sure
like
you
know.
Some
idea
that
somebody
spit
balls
in
the
middle
of
a
call
is
probably
going
to
be
less
meritorious
than
something
you've
spent
time
truly
thinking
through.
J
Now
we've
had
some
really
good
discussions
with
this
group
with
our
ux
designer
luna,
who
is
one
ua
wong
on
the
github
thread.
Yeah.
One
question
is
like:
if
we
collapse
it,
should
we
have
some
sort
of
affordance
to
make
it
appear
either
with
the
keyboard
shortcut
or
the
button
or
or
something
else
to
to
make
it
appear
again
so
yeah.
These
are
all
really
good
bits
of
feedback.
I
thank
you
all
for
adding
them
into
the
notes
here,
I'll
copy
them
out
once
we're
done
with
this
discussion,
any
opinions.
A
My
plan
is
to
continue
it
when
we
have
time
at
the
end
of
the
meeting,
so
that
will
deepen
by
time
to
time.
So
for
now
people
are
doing
great
job,
so
we
were
only
six
open.
So
that's
great
and
again
you
can
keep.
I
don't
know
about
the
church
meeting.
I
don't
have
much
time
to
participate.
Unfortunately,
personally,
but.
J
Yeah,
it's
not
great
for
anyone.
Unfortunately,
10
a.m
is
a
little
bit
too
late
for
our
friends
in
europe
and
a
little
bit
too
late
for
our
friends
in
the
on
the
west
coast
of
the
us,
so
there's
only
so
many
hours
that
work
for
everyone.
Let's,
let's
try
to
have
one
this
week
and
then,
if
we
continue
to
have
low
participation,
I
I
might
just
remove
from
the
calendar
effective
next
week.
H
Is
there
anything
stopping
us
from
making
it
optional
so
weeks
where
we
don't
get
to
triage?
During
this
meeting
we
can
add,
we
can
run
the
meeting
in
weeks
where
we
do
get
to
triage.
We
can
cancel
it
because
we
don't
need
it
because
we
don't
always
have
time
to
triage
at
the
end
of
this
meeting.
But
when
we
do
assuming,
we
don't
need
that
meeting
very
much.
J
Yeah
I
hear
you
I
will.
I
will
think
about
that.
Let's
plan
on
having
it
this
week
because
it's
it's
looking
kind
of
like
we
may
not
get
to
triage
stuff.
Today
we
have
a
fairly
time
intensive
agenda
today,
yeah,
let's,
let's
keep
an
eye
on
that
and
encourage
folks
to
participate,
but
I
agree:
we
may
not
need
it
every
week.
M
Yeah
I
mean
the
original
motivation
for
the
triage
meeting
was
actually
geared
towards
the
notebook
v7
release,
so
we
could
go
through
that
backlog.
It
seems
like
if
y'all
are
keeping
up
to
pace
then
you
know,
maybe
it's
a
good.
I
I
did
it
as
a
community
thing.
If
it's
a
burden
it
shouldn't
be,
but
you
know
I
think
we're
still
gonna
have
to
find
a
way
to
organize
and
rally
people
around
notebook
triaging,
as
we
you
know,
cross
that
hurdle.
So
maybe
that's
something
to
consider.
A
Thanks
tony
reason,
I
just
added
also
a
comment
about
the
the
toolbar
toolbar
that
maybe
we
we
could
use
some
similar
pattern
to
the
toolbar
to
to
create
a
button.
That's
say
three
dots
and
say:
okay,
if
you
click
there,
you
will
have
more
information
in
case
the
user
is
close
to
there,
but
that.
J
If
you
look
at
the
the
original
issue,
luna's
mock-ups
actually
included
that
and
the
the
little
dot
dot
button,
and
it
was
perhaps
a
little
bit
too
small.
A
J
Yeah-
and
I
also
made
it
a
point
to
like
even
keep
the
css
class
names
different
from
yours,
so
that
if
someone
wanted
to
disable
the
cell
toolbar
extension
in
favor
of
the
enhanced
cell
toolbar,
I
want
to
be
able
to
do
that
without
conflict.
So
and
and
once
again.
Thank
you
very
much
frederick
for
helping
to
to
build
kind
of
the
the
predecessor
to
the
work
that
I've
been
doing.
J
For
both,
I'm
not
sure
what
it
explicitly
says,
but
that
is
kind
of
the
the
broad
agenda
for
it.
E
Yeah
because,
while
at
the
notebook
meeting
I
said,
I
would
go
to
the
no
classic
notebook
issues,
so
I'm
gonna
try.
I
don't
know
if
it
makes
sense
to
let's
say,
split
into
that
triage
meeting,
because
while
sometimes
there
are
dependencies,
but
I
think
for
the
classic
notebooks,
there
are
a
lot
of
to
be
discussed
which
doesn't
depend
on
jupiter
lab.
So
I
don't
know
if
we
can
say
the
first
part
would
be
for
classic
and
the
second
part
would
be
for
that.
G
J
G
E
Yeah
yeah,
yes,
I
guess
I
guess
some
issues,
but
I
guess
also
a
lot
of
the
historical
issues
still
needs
to
be
addressed.
We
we
don't
want
to
drop
the
existing
notebook
user
and
say
well
just
wait.
We're
gonna
wait
for
a
few
months
or
migrate
to
notebook
seven
to
solve
their
issue.
E
So
probably
I
can
can
try
to
identify
the
subset
of
issues
which
does
not
depend
on
on
rate
or
lab,
and
but
this
is
why
maybe
there
there
should
be
or
there
could
be,
a
dedicated
notebook
triage
which
does
not
depend
on,
I
would
say,
support
classic
notebook
and
migrate
classic.
But
maybe
maybe
it's
too
much.
Maybe
it's
I
don't
know.
J
Okay,
well,
if
we
have
no
other
comments,
I
I
think
we
should
make
sure
that
everyone
else
has
time
to
discuss
their
items.
G
G
I
think
now
it
should
be
ready
to
go
now
and
the
idea
would
be
to
get
that
one
in
and
then
there
is
another
request
that
extracts
the
markdown
password
into
a
separate
plugin
that
we
should
also
be
able
to
merge
and
following
these
two
merges,
then
the
idea
would
be
to
make
a
new
for
those
or
pre-release
so
yeah
that
would
unbox
quite
a
few
things
on
a
downstream
project.
So
yeah,
that's
just
a
heads
up
of
things
that
are
likely
to
happen
very
soon.
E
Thanks
to
yeah
for
the
notebook
team,
I
I
still
have
tried
the
on
my
environment
rebuilding
from
scratch
and
I
still
don't
get
the
notebook,
but
maybe
it's
my
environment.
So
maybe
at
some
point-
and
I
I've
seen
you
every
pride
that
it
was
for
you
so
maybe
zach
on
this
call.
Maybe
if
you
have
time
at
some
point,
you
can
try
out
also.
M
I
am
thank
you
isabella's
doing
stuff
for
the
community
away
from
the
community
today,
so
I'm
running
the
accessibility
meeting,
15
minutes
after
this
hope
to
see
somebody
all
there.
Thank
you.
A
And
then
the
jason,
that's
you
that
I've
written
the
question
I
don't
have
precise
update
but
karas
is
there.
So
maybe
he
can
replied.
A
That's
json:
that's
asking
for
an
update
on
rtc
and
cell
level
undo
issue.
B
N
A
I
put
in
the
additional
notes
a
point
that
jeremy
has
raised
on
the
issue
regarding
the
release
process
and
the
maintainer
list.
I
didn't
copy
paste
the
proposed
list,
but
I
think
that
was
the
point
you
want
to
to
raise
jeremy
to
to
establish
the
first
list
of
people
that
are
that
have
rights
to
to
do
release
and
be
sure
that
we
know
who
they
are
and
who
we
can
ask
for.
I
presume
yeah.
G
I
forgot
to
bring
that
one
up
too,
so
I
think
I
think
something
back
from
the
couple
of
just
a
couple
of
weeks
been
that
the
release
process
and
also
the
expectations
in
terms
of
timelines
were
not
really
clear,
and
I
think
this
request
tries
to
at
least
fix
some
of
these
issues,
and
part
of
that
is
maybe
being
more
transparent
on
who
can
make
releases
and
who
is
going
to
make
releases
until
now.
I
think
he
was
more.
G
I
think
steve
did
a
lot
json
as
well,
and
I
think
then
it
was
pretty
much
anyone
who
wanted
to
make
a
release
who
could
make
a
one.
So
the
idea
with
having
some
kind
of
group
like
this
would
be
to
just
have
some
contacts
that
people
could
just
reach
out
to
and
if
they
want
to
know
more
about
yeah,
when
the
next
three
is
going
to
happen
in
case
they
don't
have
their
answers
during
these
weekly
course
so
yeah.
G
If
you
would
like
to
be
able
to
make
releases
for
triple
labs,
that
would
be
really
really
great.
I
think
the
larger
this
group
is
the
the
better
because
then
we
kind
of
dispatch
a
little
bit
this.
This
chore
among
people
and
I
kind
of
also
increase
the
knowledge
on
you
know
what
it
takes
to
make
a
release.
But
good
news
is
that
with
the
reuse,
it's
much
much
simpler
nowadays,
so
yeah
so
yeah.
G
If
you
are
interested
comment
on
the
request
or
just
reach
out
on
the
app
guitar
channel.