►
From YouTube: JupyterLab Team Meeting - August 31, 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
Hello
and
welcome
to
the
August
31st
Jupiter
lab
weekly
call.
Today.
We've
got
18
people
on
the
call
and,
if
you
haven't
already
please
add
your
name
to
the
agenda
which
is
linked
in
the
chat
and
if
you'd
like
to
talk
about
something.
Please
add
a
bullet
point
in
the
agenda
subsection
and
if
you
have
something
that
might
take
longer
than
let's
say
five
minutes,
add
it
to
the
additional
discussion
section.
A
We've
got
two
people
on
the
agenda
already,
so
that's
a
start.
Hopefully
there
will
be
more
and
why
don't
we
get
started
with
Jason
w.
B
Ow,
hey
everyone,
so
I
had
a
quick
observation
about
triage
because
we
were
just
before
we
started
the
recording
talking
about
triaging
issues.
We
have
a
weekly
triage
on
Thursdays
at
10
A.M
Pacific
time,
and
it's
often
with
all
due
respect,
people
who
show
up
it's
often
a
struggle
to
get
people
interested
in
coming
to
Jupiter
lab
triage
after
the
server
call.
So
what
would
folks
think
about
moving
it
to
Wednesday
after
the
close
of
this
meeting,
so
that
folks,
who
joined
for
the
Jupiter
lab
meeting,
could
remain
on
for
issue
triaging.
C
The
accessibility
meeting
after
this
I'm.
A
B
B
But
it's
like
it's
I'd
like
to
catch
people,
it's
like
for
for
those
Americans
about
the
same
age
as
me,
there
was
this
notion
of
a
time
slot
hit
where,
if
you
wanted,
a
certain
TV
show
to
be
popular.
You
put
it
on
after
a
very
popular
show.
I
want
that
with
triage
I
want
you
guys
to
retain
people
from
the
lab
meeting,
so.
B
After
the
community
call,
that's
the
monthly
Community
call
right.
B
So
I'm,
okay,
with
keeping
the
triage
meeting
as
it
is
I,
will
also
use
this
opportunity
to
encourage
people
to
come
to
triage.
If
you
can,
if
your
schedule
can
bear
it,
because
we've
also
recently
started
to
triage
notebook
issues
as
well.
Rosio
is
leading
that
portion
and
if
anyone
wants
to
triage
additional
projects,
you
know
more
suggestions
are
welcome.
A
And
I
think
if
it
turned
out
that
that
call
actually
had
too
many
people,
because
there
were
too
many
projects
being
represented,
we
could
start
using
the
zoom
breakout
room
feature
and
still
have
like
triage
power
hour
or
whatever.
That
would
be
a
good
problem
to
have
so.
B
C
Hey
hey
Jason,
I'm
curious
like
while
we're,
maybe,
if
we're
not
done
the
logistics,
I'm
curious
about
how
the
triaging
thing
has
been
going
like
what
kind
of
positive
impact
have
you
guys
been
seeing
on
the
project
with
it
since
you've
been
kind
of
keeping
up
like?
What's
the
benefit
for
folks
joining
this
well.
B
Let
me
share
in
the
chat
the
triage
meeting
notes,
so
you
can
see
how
how
much
stuff
we're
getting
through.
In
a
typical
week,
we
usually
triage
about
a
dozen
issues
in
lab
and
I
would
say:
low
single
digits
numbers
in
Notebook
right
now,
and
the
the
impact
of
the
project
is
that
when
people
file
an
issue,
they
should
expect
that
somebody
is
going
to
respond
to
it
in
some
way
within
a
week
and
that
encourages
people
to
file
new
issues.
B
We're
also
using
this
as
an
opportunity
to
be
extra
nice
to
newbies
people
who
have
just
filed
their
first
issue
to
even
if
they
file
something
that's
a
duplicate
or
that
we're
not
going
to
consider.
We
need
to
reach
out
to
them
and
say
hey
thanks
for
submitting
thanks,
for
you
know,
contributing
and
encouraging
them
to
do
so
again.
B
We've
also
occasionally
looked
at
older
issues
or
older
pull
requests,
which
I
think
we've
had
mixed
results
on
it.
One
other
effect
is
that
the
people
who
do
the
triaging
sometimes
get
follow-ups
from
people
who
are
curious
about
things
or
who
want
to
submit
a
pull
request
or
who
want
more
information
about
the
project.
So
we're
we're
effectively
marketing
ourselves
as
being
actively
involved
with
our
own
project
and
actively
reaching
out
to
people
who
are
interested
and
also
encouraging
people
to
you
know,
file
well-formed
issues
as
well.
A
Yeah,
there's
I
think
one
of
the
points
of
utility
from
doing
the
triage
call
together
is
no
one
person
has
to
feel
completely
on
the
hook
for
closing
an
issue
that
either
has
been
abandoned
or
isn't
well
formed
or
whatever
at
least
you
can
say,
hey
look.
We
had
consensus,
we
talked
about
this
and
I
I.
Don't
know
it
seems
like
a
harder
thing
to
do
on
your
own.
A
A
I
think
I
think
we
could
try
that
it
would
really
be
dependent
on
each
each
one
of
those
having
at
least
one
person
who's
willing
to
lead
because,
unlike
unlike
some
of
the
other
calls,
this
one
ends
up
featuring
like
it's.
It's
a
working
call
right,
so
someone's
sharing
their
screen
and
like
doing
this
stuff.
So
if,
if
someone
commits
to
a
time
that
works
for
them,
we
will
try
really
hard
to
make
sure
you're,
not
the
only
person
there
yeah.
B
I
think
this
is
a
good
intention,
especially
if
we
want
to
bring
folks
in
Asia
Pacific
into
the
fold.
One
other
challenges
that
frankly,
there
isn't
really
enough
triage
load
to
fill
two
hours
worth
of
effort
and
I,
don't
think
two
half
hour
meetings
would
be
worth
the
cost
to
coordinate.
But
if
we
want
to
kind
of
rotate
through,
you
know
rotate
through
the
duty
load
or
we
could
start
reviewing
PR
as
Mike
points
out.
B
A
D
B
C
Ahead,
you
know
one
of
the
ways
we
act,
so
we
did
some
before
we
like
did
the
Jupiter
lab
triaging.
We
actually
started
because
we
were
trying
to
do
notebook
triaging
because
that's
like
when
the
pep
and
all
that
or
the
Japan
stuff
came
out
right.
C
So
what
wound
up
being
actually
really
in
the
notebook
tree
icing
was
fun
because
we
just
picked
certain
search
or
filtering
parameters
and
start
going
through
a
bulk
of
things
right
where
it's
like.
Oh
there's,
this
one
plug-in
that's
mentioned
a
bunch
of
times.
There's
these
things
mentioned
a
bunch
of
times,
but
you
can
actually
like
using
some
of
the
search
criteria
and
filtering
you
can
actually
make
that
notebook
issue
event
kind
of
purposeful.
C
So,
like
things
that
have
high
reaction
numbers,
you
know
just
doing
a
little
bit
of
filtering
and
cleaning
up
and
having
some
eyes
there,
and
it
can
kind
of
help
you
like
there
was
one
day
when
we
got
rid
of
like
20
issues,
just
because
we
found
lots
of
duplicates
with
a
good
search
criteria.
You
know.
B
Yeah
I
mean
I
think
once
an
issue
gets
sufficiently
old
as
well
for
the
good
of
the
project.
Just
you
know,
closing
it
out
and
asking
people
to
reopen
it
can
be
annoying.
But
frankly,
there
are
a
lot
of
issues
that
just
aren't
going
to
get
fixed
and
or
or
have
already
been
fixed
or
are
no
longer
relevant.
B
A
C
Show-Offs
yeah,
but
one
of
the
things
that
y'all
mentioned
that
like
kind
of
I
was
like
oh
I,
haven't
seen
that
yet
is
doing
pull
request,
reviews
and
maybe
it's
not
the
triage
format
but
maybe
like
y'all,
could
record
videos
of
how
you
triage
issues
like
a
review,
pull
request
or
maybe
get
together
with
somebody
and
review
the
pull
request.
But,
like
I
think
you
know,
issues
are
nice
right
and
Pull
and
pull
request.
A
This
actually
overlaps
a
bit
with
what
has
been
going
on
with
Jupiter
server
and
their
contributing
our
calls.
So
most
of
those
are
fixing
a
bug,
adding
a
feature
or
doing
a
common
thing
that,
like
how
do
I
write
a
server
extension
that
kind
of
thing
but
I
think
within
the
agreement
of
that
would
be.
How
do
you
review
a
PR,
but
that
is
very
much
oriented
toward
server
and
its
ecosystem
and
less
front-end,
stuff
and
I
know
I've
been
asked
about.
A
How
do
you
do
PR
reviews
I
certainly
wouldn't
feel
great,
recording
that
right,
I
don't
want
to
record
myself
critiquing
stuff.
Other
people
have
written
for
sure
I'll.
Do
it
for
an
audience
like
because
I
imagine
we
all
have
good
faith
toward
each
other
and
we're
not
there
to
be
hostile.
But
I
wouldn't
feel
great
about
posting
that
one
on
YouTube.
B
E
First
is
about
the
python
logo
for
python
files,
so
there
was
a
initial
filed
from
the
python
trademark
committee.
They
highlighted
that
the
logo
that
we
are
currently
using
does
not
comply
with
the
guidelines,
so
it
doesn't
have
the
eyes
and
the
shape
is
Right
slightly
wrong.
E
There
isn't
a
problem
with
changing
colors
in
principle,
so
we
could
apply
and
use
a
blue
logo
for
python
to
have
the
python
file
icon
as
it
currently
is,
and
as
it
shows
in
the
file
browser,
we
just
need
to
adjust
the
shape
slightly
and
at
the
eyes,
and
the
alternative
is
to
use
the
python
logo
as
as
this
used
for
notebooks
and
consoles
without
any
changes
to
the
colors.
E
So
in
order
to
use
the
logo
with
different
color,
we
would
need
to
just
submit
a
quick
email
and
we
get
a
got
a
reply.
Dots
such
a
request
will
be
approved,
but
my
question
is
whether
we
want
to
go
with
the
two
color
logo
standard,
local,
so
harmonize
the
use
of
logos
or
to
have
distinct
logo
for
python
files
to
highlight
that
this
one
will
not
create
a
running
character
to
make
Extinction.
As
it
is
currently.
F
I
made
a
note
on
the
hack
MD
and
on
the
issue
after
seeing
that
there
was
a
there's,
an
open
PR
that
we
discussed
I
think
it's
almost
a
month
ago
now
about
switching
to
the
standard
logo.
It's
one
that
I
cleaned
up,
slash
customized
for
elyra,
where
I
removed
all
the
extraneous
SVG
Gunk.
So
we
could
easily
recolor
it
for
theming
and
they
added
that
in
that
PR.
F
If
you,
if
we
want
it
to
stick
to
that,
like
blue,
we
could
still
use
that
custom
SVG,
that's
all
cleaned
up
and
then
just
set
it
to
Blue
in
the
CSS,
but
I
think
using
that
standard
their
logo,
essentially,
but
just
with
a
cleaned
up.
Svg
is
probably
the
best
way
moving
forward.
What
whether
or
not
we
actually
use
the
standard
colors
on
it.
A
F
Can
open
that
the
pr
that
I
linked
isn't
mine,
but
they
were
using
an
icon
that
I
gave
them
so
I
can
just
open
it.
Pr
myself
with
the
icon
I
made,
and
then
that
can
open
the
discussion
on
whether
or
not
we
want
to
adjust
it
to
still
use
the
single
color
or
not.
C
D
F
Yeah,
this
is
me
speaking
from
previous
research,
not
discussions
with
specific
people,
but
as
far
as
I
could
understand
from
previous
conversations
and
discussions
online
and
from
their
own
documentation,
essentially
gray
scaling
it
so
like
setting
it
to
a
solid
color.
For
contrast,
as
long
as
you're
still
using
their
icon
is
allowed.
B
D
Allowed
without
approval.
F
As
far
as
I
could
tell
without
approval,
but
I
would
still
for
my
PR
I'd
still
ping.
The
person
who
raised
this
and
ask
them
to
confirm
that
so.
E
I
I
took
a
pretty
detailed
look
at
the
guidelines
and
they
are
inconsistent
in
one
place,
so
you
can
do
that
without
approval
and
in
other
they
ask
to
ask
they
suggest
that
you
ask
for
approval
whenever
you
change
the
colors,
but
in
the
issue
that
we
linked
there
is
that
both
people
in
the
committee
suggested
that
it's
likely
that
we
will
get
approval.
Just
for
the
bookkeeping
to
to
take
a
formal
note
of
the
requests
that
they
suggest.
We
submit
a
formal
request
via
email.
F
I
on
a
separate
note,
though,
do
we
even
care
about
getting
it
all
in
one
color
for
our
use
case,
or
are
we
okay
using
the
icon,
as
is
there's
lots
of
screenshots
on
both
the
issue
that
I
linked
and
if
anybody's
ever
opened
to
Lyra
we've
already
been
using
this
icon
in
a
Lyra
for
years
it
as
far
as
my
opinion,
it
contrasts
perfectly
fine,
but
is
there
any
issue
with
Just
keep
not
having
to
deal
with
this
whole
color
thing,
but
just
using
the
icon,
as
is
or
are
people
here
on?
F
I'd
never
thought
about
it
that
way,
because
the
the
kernels
already
use
a
separate
icon,
because
Colonels
provide
their
own
PNG
and
it's
pretty
clearly
a
different
icon,
just
size
contrast
pixelization.
F
It's
actually
been
a
complaint
with
our
customers
using
elyra
they're
like
hey.
Why
aren't
these
the
same
icon,
they're,
both
python
and
but
like
as
a
Lyra,
we're
just
providing
Jupiter,
as
is
so?
We
can't
fix
what
the
kernels
that
they
are
using
are
providing.
F
We
can
only
tell
them:
hey
that's
on
your
kernel,
but
it
that
has
been
an
issue
in
the
past
for
our
customers,
but
from
a
different
direction
than
I.
Think
you
were
meeting.
A
So,
for
the
sake
of
resolving
this
sooner
because
we've
got
an
actual
complaint
from
the
psf,
why
don't
we
take
Mike's
suggestion
from
the
chat
and
take
a
quick
poll?
So
if
you
want
all
blue
I
will
ask
you
to
raise
your
hands
or
thumbs
up
or
whatever
and
we'll
count
those
and
then,
if
you
want,
as
is
I'll
ask
again
so
with
that
being
said,
if
you
want
all
blue,
please
do
an
emoji.
A
A
A
F
F
C
C
Because
so
I've
deflated
a
few
kernels
and
stuff
like
that.
So
right
now
the
kernels
look
for
a
logo
with
a
file
name
and
a
PNG
to
it,
and
when
we've
been
doing
audits
at
400
percent,
those
pngs
don't
work
right.
So
by
shipping
around
image,
the
pngs
as
the
logos
we
actually
can't
get
accessible
icons
for
the
kernels
is
there?
Is
it
that
calcified
to
the
point
where
we
couldn't
reuse,
something
from
Jupiter
lab
or
is
there
a
possible
way
to
reuse
some
of
the
stuff?
You
all
have.
F
C
Right
yeah,
because
we
were
talking
about
going-
and
you
know
hitting
the
major
three
like
Julia
R
and
python
right,
but
that
means
we'd
have
to
make
re
like
pull.
Requests
of
three
different
repos
go
through
a
bunch
of
different
things
there.
If
we
could
reuse
some
components,
somehow
I
think
it
would
circumvent
some
extra
effort
in
having
these
features.
F
Yeah
I
I
would
agree
with
you.
It
would
be
worth
opening
an
issue.
It
is
something
yeah.
It
is
something
that
our
customers
have
complained
about.
The
resolution
of
those
icons
compared
to
the
rest
of
them
in
Jupiter
lab.
E
There
is
already
an
issue
about
this
I
think
that's
in
the
chat
and
I
just
wanted
to
highlight
that
the
proposed
icon
in
the
pull
requests
that
Alex
mentioned
it
doesn't
seem
to
be
to
have
the
gradient.
Would
that
be
easy
to
add
the
gradient
back
so
that
it
reflects
the
original
python
logo
perfectly
I.
F
I
can
actually
give
you
a
hard
no
on
that
SVG
gradients
require
the
use
of
IDs
and
IDs,
and
SVG
files
is
incompatible
with
our
current
implementation
of
lab
icons.
F
F
The
the
official
python
SVG
does
have
gradient
support
as
I
downloaded
it
from
the
official
I.
Don't.
F
Possibly
I
copied
ours
about
a
year
and
a
half
ago,
right
after
we
switched
to
lab
icons.
F
But
I
can
look
into
that
as
part
of
my
PR,
but
I
do
know
as
a
fact
Radiance
won't
work
with
lab
icons
there.
We
could
open
an
issue
to
address
that
I
have
considered
doing
that,
but
when
I
tried
an
initial
attempt
at
fixing
it
inside
core,
it
was
a
nest
of
issues
that
I
decided.
I
wasn't
worth
my
Dev
hours,
because
nobody,
no
customer
had
asked
me
to
do
it.
A
A
Thank
you,
I'm,
going
to
take
this
moment
to
remind
everyone
that.
A
D
It
to
the
agenda,
what
I
was
saying
and
apparently
I
was
muted.
So
there
definitely
was
some
I
can
work
done
within
the
last
year
and
a
half
because
my
attention
team
had
some
people
working
on
it.
So
I'm
not
clear
on
the
details,
but
there
was
some
workout.
So
I
was
just
checking
in
on
that.
A
The
first
one
is
lumino2
and
Jupiter
lab,
and
even
though
we
are
still
working
on
the
lumino
2
release
and
there
are
still
more
features
and
performance
enhancements
that
we
need
to
make
because
the
biggest
API
changes
have
already
been
merged.
We've
published
Alphas
and
I've
linked
to
the
pr
to
migrate,
Jupiter
lab
from
Lumina
one
to
two
and
there's
a
work
in
progress.
Migration
guide
in
the
lumino
read
the
docs
page
that
talks
about
the
changes
from
Lumina
one
to
two.
A
If
you
look
at
the
pr,
it
touches
a
lot
of
files,
but
it's
not
actually
a
particularly
heavy
PR,
and
it
is
indicative
of
the
sort
of
work
you
will
have
to
do
to
migrate.
Your
extension
over
from
luminal
one
to
two,
a
AKA
Jupiter
lab
three
to
four
once
this
PR
is
in.
We
can
publish
another
Jupiter
lab
Alpha
and
apply
the
same
treatment
to
notebook
7.,
but
notebook
7
depends
both
on
lab
packages
and
on
lumino
packages.
So
we
can't
do
that
right
now.
A
If
you,
if
you'd
like
to
contribute
to
this,
there
is
a
lumino
2
project
board
with
some
outstanding
issues
I've
linked
it
before.
But
let
me
find
it
again
because
all
the
help
we
can
get
is
appreciated,
and
if
someone
wants
to
work
on
bringing
lumino
to
here's,
the
project
board
bring
illuminol2
to
notebook.
7.
I
planned
on
doing
it
just
because
I
made
the
biggest
API
changes
this
time
around
and
I've
got
the
experience
of
having
done
this
with
Jupiter
lab
already.
A
So
it
should
be
fairly
straightforward
for
me
to
do
with
notebook
7..
But
if
someone
wants
to
learn
about
this
part
of
the
stack
and
wants
to
Port
notebook
7
from
Lumina
one
to
two
probably
next
week
when
we
have
these
packages
published
I
am
happy
to
help
you
with
it
and
if
not,
I
will
do
it
myself.
But
if
you
want
to
work
on
this,
I
guess
get
in
touch.
A
I
will
write
an
issue
in
the
notebook
repo
today,
so
you
can
either
ping
me
there
or
find
me
on
some
other
channel
I'm
not
hard
to
find
yeah.
I
know
any
questions
about.
What's
in
this,
because
it's
it's
kind
of
big
but
I've
also
brought
it
up
enough
times
that
you
might
already
know
and
not
want
to
hear
it
again.
D
A
A
So
please,
forgive
me
for
repeating
myself,
but
we're
aiming
for
the
Jupiter
lab
Council
to
be
fully
formed
and
to
pick
its
software
steering
Council
representative
by
October
3rd,
so
I
think
we
decided
mid-september
is
when
we
want
to
have
the
deadline
for
nominations
of
a
member
of
the
Jupiter
lab
Council
to
represent
this
project
on
the
SSC.
A
And
so,
if
you
want
to
nominate
someone,
Fred
has
sent
out
a
link
to
a
Google
form
that
he
created.
Just
please
make
sure
that
you
have
confirmed
with
that
person
that
they
want
to
be.
A
They
would
accept
if
they
actually
were
voted
in
and
add
them.
If
you
wish
there
are
a
few
constraints.
One
is
you
have
to
be
a
member
of
the
Chipotle
Council
two
is.
You
cannot
be
both
on
the
newly
forming
Jupiter
executive
Council
and
the
newly
forming
software
steering
Council.
So
if
you
actually
want
to
run
for
the
Jupiter
executive
Council,
then
don't
do
SSC
and
three
is
again.
If
you
want
to
nominate
someone
just
confirm
with
them
that
they
want
to
do
it.
A
But
beyond
that
go
to
town
and
in
the
interim,
if
there's
someone
you
would
like
to
nominate
to
join
the
Jupiter
lab
Council.
Please
do
I
think
Jason
growl
is
on
this
call.
So
if
there's
something
that
I've
missed,
that
you
can
fill
in
I
would
appreciate
it.