►
From YouTube: JupyterLab Team Meeting - 26 July 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/205
A
B
Yeah
I
just
wanted
to
bring
that
issue
again
since
it's
been
open
for
almost
two
months
and
the
the
lab
Council
was
still
mentioned
on
the
on
the
issue
and
so
I
think
it's
been
enough
visibility
and
it's
just
the
last
check.
If
someone
has
in
here
any
concern.
So
the
the
issue
is
that
this
logo
is
is
is
coming
from
absolutely
nowhere.
I,
don't
think
anyone
has
the
source
of
this
logo,
but
it's
on
the
GitHub
organization.
B
So
the
idea
is
to
replace
it
with
the
official
tubular
logo
taken
from
the
Jupiter
design
report.
So
I
will
proceed
with
this
change
if
no
one
has
any
concern.
So,
if
you
have
anything
to
say
say
here
now
or
in
down
the
issue-
and
the
second
point
I
have
was
about
the
notebook
7
release,
so
we
released
the
book
seven
last
week
and
in
the
beginning
of
this
meeting
we
also
published
the
blog
post
and
now
we
need
some
help.
B
So
if
you
have
a
time
or
if
you
are
what
I
want
to
work
on,
you
know
pretty
much
trip
to
that
related
stuff.
You
can
also
help
with
notebook
7.
So
some
folks
have
reported
issues,
but
not
as
many
as
I
think
we
could
have
expected,
which
is
which
is
good
news,
but
there
are
a
couple
of
them.
So
if
you
have
time
to
monitor
the
recall,
that
would
be
super
great
and
also
check
the
discourse
somewhere.
B
Sometimes
people
will
post
the
topics
there
when
they
have
issues,
and
we
also
have
a
7.0.x
milestone
with
a
quite
a
long
backlog
of
things
to
to
to
do
there.
So
so
there
is
plenty
plenty
to
do
if
you're,
if
you're,
looking
for
making
some
contribution
to
notebook,
7.
and
that's
it
foreign.
C
I
just
wanted
to
add
one
thing,
so
I
think
everyone
on
the
call
knows,
but
just
in
case,
and
also
because
this
will
be
published
to
the
broader
public,
because
notebook
7
is
a
brand
new
application
built
with
Jupiter
lab
components.
It
is
something
that
anyone
on
this
call,
or
anyone
with
an
interest
in
this
call,
has
the
ability
to
work
on
right.
So,
if
you've
done
anything
in
Jupiter,
lab
working
on,
Notebook
will
actually
be
easier.
C
It's
a
simpler
application
with
viewer
extensions
and
it
was
architected
from
the
ground
up
to
be
a
Jupiter
lab
remix
using
the
Jupiter
front
end,
and
so
some
of
the
tooling
is
actually
a
bit
more
modern
than
you
might
be
used
to
with
lab,
because
it's
just
less
I
can
go
wrong,
so
it
is
not
just
appropriate
for
Jeremy
to
be
bringing
this
up
here.
It's
like
this
is
our
code.
Already
right,
it's
it's
most
of
notebook.
7's
code
actually
resides
in
github.com.
C
It's
just.
You
wouldn't
know
that
looking
at
the
repo,
so
you
really
are
all
capable
of
looking
at
some
of
these
issues
and
just
remember
notebook
is
like
the
most
popular
thing
we've
ever
released.
So
if
you
want
to
work
on
something
that
you're
confident
lots
of
people
are
going
to
see,
it's
a
good
one.
D
blog
post,
but
it
seems
like
there's
a
interest
in
an
accessibility,
focused
blog
post
in
the
future,
and
if
anybody
wants
to
see
how
they
might
help
that
effort
immediately,
we
actually
have
a
fairly
large
meta
issue
that
we
do
need
some
help
on
and
I'm
just
gonna
drop
that
in
the
chat,
so
yeah
any
support
and
any
experience
with
Jupiter
lab
will
definitely
help
with
accessibility.
Also.
D
A
Cool
any
other
comments,
questions
about
the
first
part
of
the
agenda
here.
A
If
not
I
dropped
in
I
didn't
put
my
name
on
it,
but
the
Jupiter
con
YouTube
page
now
has
lots
of
recordings
from
jupitercon
2023.
Almost
all
the
content
is
there
if
you're
expecting
to
see
a
session
recording-
and
you
don't
see
it-
there-
please
reach
out
to
Gail
and
Sylvan,
and
they
have
a
couple
of
files
that
I
think
they
still
have
not
been
able
to
upload
successfully.
But
please
share
this
stuff,
promote
it
LinkedIn,
Mastodon,
Twitter
or
X
or
whatever.
A
It
is
any
medium
that
you
use
to
reach
out
to
the
community,
and-
and
thank
you
all
for
you
who
presented
and
recorded
and
helped
produce
this
content.
A
And
then
I
had
one
other
item
which
is
from
the
security
team.
The
Jupiter
bug
Bounty
program
is
live.
We
got
a
grant
from
the
European
commission
about
this
and
it's
been
in
kind
of
a
pilot
stage
for
a
while.
I
just
dropped
a
link
into
the
chat.
A
If
you
want
to
check
it
out,
the
it
covers
Jupiter
lab
Jupiter
server
and
Jupiter
Hub,
so
anybody
who
finds
a
security
vulnerability
and
it
can
get
a
bounty
of
anywhere
from
250
euros
to
5
000
Euros,
depending
on
the
the
severity
of
it
and
I,
was
looking
through
the
rules
about
like
who
can
participate
and
I'm,
not
I
believe
that
we
we
can
like.
We
all
can
if
we
find
issues,
but
please
take
a
look
at
that.
A
There's
already
been
some
submissions
coming
in
folks
from
Integrity
have
been
helping
to
triage
these,
and
please
publicize
this
on
your
favorite
social
media
as
well.
We're
also
working
on
a
blog
post
to
try
to
get
the
word
out
more
officially
from
Jupiter
to
make
sure,
because
it's
one
of
those
things
it
it's
on
Integrity,
not
a
lot
of
people
know
who
that
is
so
we're
trying
to
emphasize.
Yes,
this
is
an
official
effort,
officially
endorsed
by
Jupiter.
A
C
Wanted
to
ask
Gabriel
if
you're
going
to
be
able
to
work
on
that
one
open,
tap
shop
issue
and
if
you're,
not,
if
there's
a
volunteer
to
help
pick
it
up
from
him,
because
I
don't
want
you
to
feel
like
you're
stuck
with
it
until
it
comes
out.
But
if
you're
happy
to
work
on
it.
That's
great
too,
if
not
now's
a
great
time
to
solicit
volunteers.
F
Which?
Which
one.
F
Although,
if
you
could
follow
up
with
well,
if
someone
could
I
think
we're
talking
about
the
same
thing,
but
if
you
could,
if
you
there
is
something
you
want
to
post
I
can
double
check
just
to
make
sure
that
we
aren't
somehow
Cross
miscommunicating
or
something
no.
C
Great
cool
awesome,
yeah
I,
wasn't
sure,
because
I
knew
that
Mike
had
reviewed
it
and
there
was
a
thing
that
needed
to
be
changed,
but
I
didn't
know
if
you
were
still
available
so
I
didn't
want.
I
didn't
want
it
to
get
stuck,
but
I
also
didn't
want
it
to
feel
like
it's.
Your
burden
alone.
D
Oh
I've
been
watching
an
issue
and
it's
been
incredible
to
see
it
go
on
since
February
now,
but
Nick
has
been
trying
to
get
this
mermaid
diagram
thing
in
and
it
seems
like
he
just
keeps
updating,
CI
and
updating
CI
and
updating
CI.
Is
it
any
way
we
could
talk
about
that
as
a
feature,
because
one
of
the
things
we
talked
about
in
The
Notebook
meeting
before
was
like
Mark.
These
blog
post
is
marketing.
I.
D
Think
the
mermaid
thing
is
the
feature
a
lot
of
companies
put
out
Mermaid
as
a
feature,
and
this
is
something
that
I
really
think
people
are
gonna
like
so
I'm
yeah.
A
D
C
There
anyone
here,
who
is
I
think
Isabella
is,
but
is
there
anyone
from
the
sfc?
That
knows
whether
this
thing
hinges
on
the
jet
or
if
this
thing
is
independent
of
the
job
I'm
not
aware
right,
because
there's
also
Jupiter
enhancement
proposal
about
making
this
part
of
the
standard
Jupiter
offering
for
markdown
and
that
one
I
think
is
still
in
the
voting
phase.
I
don't
know
if
this
is
dependent
on
that
and
that's
why
it's
still
open
or
if
there's
some
other
reason.
C
Okay,
cool
I.
G
Can
relate
my
my
biased
feedback
on
what
I've
heard
from
various
sources,
brace
yourselves
so
yeah
indeed,
so,
basically,
it
does
not
change
the
notebook
format,
because
the
markdown
format
inside
of
that
is
not
currently
specified.
There
is
a
separate
jet
that
will
instantiate
that.
So
at
this
point
the
markdown
format
is
not
actually
controlled
by
a
Jep
or
the
the
the
markdown
itself,
because
it
does
not
change
the
schema.
G
It
therefore
does
not
need
a
gif
and
will
not
hinge
on
the
Jet
and
that
jet
will
not
pass
because
I
don't
know
whatever
that
you
can
go,
read
the
joke,
but
yeah,
that's
my
understanding,
so
it
has
already
been
merged
into
Envy.
Convert
I'm
waiting
for
the
lab,
merge
to
update
the
version
of
mermaid
on
Envy,
convert
and
I.
Don't
know
if
it's
already
been
deployed
to
Envy
viewer,
but
it's
possible,
so
we're
just
end
arounding
having
consensus,
because
there
is
no
consensus
somewhat
Jupiter.
Markdown
is
today
that.
G
D
G
Pass
that
test,
obviously
it
is
not
that
that's
about.
H
This
adding
another
drop
down
entry
for
the
cell
type
so
either
mark
down.
G
G
G
This
is
adopting
the
same
markdown
syntax
used
by
GitHub
gitlab
hedge
dock
I'm,
trying
to
think
else
who
does
it
native,
like
okay,.
G
Of
instead
of
if
it
fail,
if
you
do
not
have
this
feature,
it
will
draw
a
unsyntex
highlighted
block
that
is
still
readable.
Okay,
look
at
that
and
be
like
hey.
That
looks
like
a
diagram.
You
know
like
I
can
read
that
you
know.
Okay
thanks
and
the
Coalition
of
the
Willing
will
draw
it
as
a
picture.
So.
C
C
Are
we
promoting
de
facto
standard?
C
G
Yeah
I
mean
I
I
inadvertently,
took
it
out
of
of
draft
and
Steve
merged
it.
But
you
know
that's
not
on
Steve.
That's
on
me
for
taking
a
draft.
C
G
C
Okay,
so
anyone
have
does
everyone
have
like
an
objection
here?
Is
it
just
because
it's
complicated
and
hard?
Is
it
just
because
CI
fails
like
what's
holding
us
back.
I
How
often
does
mermaid
introduce
incompatible
changes
and
so
I'm
thinking
of
if
we
support
this
sort
of
officially,
as
in
we
distribute
a
plug-in
by
default,
then
if
someone
writes
mermaid
JS
diagram-
and
you
know,
we
haven't
updated
to
the
latest
version
of
mermaid
yet
or
they're
running
an
old
version
of
jupy
or
whatever,
or
we
update
to
a
new
version
and
now
their
mermaid
diagram
doesn't
work
anymore
Etc.
I
So
we're
sort
of
adopting
any
of
the
faults
of
the
mermaid.js
implementation
with
regards
to
backwards
compatibility
and
things
like
that,
and
it's
not
so
much
I
mean
we
can
just
say
or
use
whatever
mermaid
does,
whatever
the
version
is,
but
there
will
be
support,
requests
coming
in,
saying,
hey
my
document
doesn't
render
anymore.
I
Do
you
can
you?
Can
you
give
us
a
sense
for
the
mermaid.js
implementation
here.
G
G
A
great
diagram
love
that
guy
flow
charts
that
I
wrote
for
NB
mermaid,
which
I
still
get
requests
for.
How
do
I
install
this
in
Jupiter
lab
a
decade
ago,
still
draw
so
it's.
This
is
not
for
writing
publication
grade.
G
You
know
tick
Z,
whatever
stuff
that's
going
to
render
on
a
40
year
old
toaster,
it's
very
similar
to
map
checks,
Every
Time,
We,
Touch,
math
Jacks.
We
break
something
right.
You
can't
just
go
to
contact
because
that'll
break
something
you
can't
just
go
to
law,
Tech,
5
or
12,
or
whatever
they're
up
to
it'll
break
something
so.
H
G
That
would
have
been
a
great
thing
to
raise.
You
know
four
months
ago,
five
months
ago,
after
I
did
all
this
work.
So
point
is
this
has
been
mentioned
several
times
in
this
discussion.
I,
don't
know
what
the
blocker
is:
architecturally,
fine
I,
don't
care.
I
already
wrote
this
as
an
extension
right,
and
it
was
expressed
in
one
of
these
meetings
that
people
were
interested
in
having
mermaid
any
kind
of
diagramming.
Anything
that
didn't
require
a
kernel,
and
that
is
what
is
provided
there
and.
I
You
know
one
more
question
about
backwards
compatibility,
so
you
said
that
the
same
key
diagrams,
for
example,
will
render
and
Jupiter
lab,
but
not
in
big
convert.
What
do
they
look
like
in
in
be
convert?
Are
they
an
error,
or
does
it
fall
back
to
the
text.
G
I
A
I
Wait
hold
on,
can
we
can
we
close
the
loop
on
Nick's
thing
because
I
realized,
like
it's
an
ongoing
issue,
that's
been
going
on
for
months.
Nick
has
put
a
tremendous
amount
of
work
into
it.
I
know
he's
gotten
frustrated
with
this
Etc
as
a
Next
Step,
when
we're
at
a
point
where
there's
uncertainty
about
whether
we
should
move
forward
with
something
whether
we
should
pull
back
from
something
Etc
I
think
the
the
process
is
to
hold
a
Jupiter
Council
vote.
G
The
the
objections
that
have
been
raised-
one
put
it
back
into
an
extension-
take
it
out,
Andy
convert
great,
then
no
one
can
rely
on
it.
So
it
doesn't
matter
so
there
you
go
two.
The
extension
yeah
great
all
right,
yeah,
put
your
thumb
down
so
we're
unless
you're
reacting
to
the
the
vote.
I,
don't
know
someone
just
put
their
thumb
up
and
I.
Don't
know
what
it
means.
The.
G
A
G
Well
size
the
size
of
it
is
large
because
they
ship
a
lot
of
junk
in
there
there's
a
lot
of
D3
in
there.
So
it's
going
to
add
probably
about
a
Meg
and
a
half
to
the
distribution.
This
is
a
sizable
chunk.
This
is
like
up
there
with
what
blueprint
used
to
do
you
know
is.
G
G
I
So,
given
it's
been
open
and
I
know,
there's
been
a
lot
of
discussion
around
it.
I
propose
we
have
a
vote
in
on
the
council
list
or
or
or
even
better
a
public
vote
on
the
on
the
repo
and
then
we'll
have
closure
and
can
move
forward.
H
E
I
A
lot
the
majority
of
the
council
is
not
on.
The
call
is
my
guess,.
C
Just
I
hate
these
public
votes,
I
still
think
it
would
be
nicer
for
us
to
privately
vote.
You
know
like
citizens
of
civilized
places,
but
what,
but
that
seems
like
the
lowest
hanging
fruit,
the
place
to
do
it.
We
tag
the
Jupiter
lab
Council
team
on
the
pr
we
put
the
names
there.
We
put
the
yes,
no
abstains
there
and
we
leave
it
open
for
seven
days
and
a
week
from
today.
The
thing
is
over.
C
I
And
let
me
thank
again
Nick
for
one
pushing
us
forward,
pushing
it
through
being
really
patient
with
this,
regardless
of
the
outcome.
Thank
you.
So
much
Nick.
A
H
Yeah,
so
I
was
wondering
about
why
we
switched
from
cookie
cutter
to
copier,
because
I
spend
a
lot
of
time,
doing,
work
toward
and
thinking
about,
making
the
user
and
developer
experience
in
the
Jupiter
ecosystem
better
for
people
and
I
feel
like
this
really
just
contributes
to
kind
of
tools
and
process
churn,
which
I
I
experienced
a
lot
of
myself
coming
on
as
a
Jupiter
contributor.
G
Supports
updates,
so
if
previously,
you
wanted
to
migrate
an
extension
from
one
thing
to
another,
there
was
a
handmade
script
that
re-ran,
with
your
inputs
from
your
old
thing
and
then
calculated
a
bunch
of
diffs.
This
actually
supports
code.
Mods
copier
is
not
unmaintained,
but
it's
not
no.
No,
they
did
release
like
a
month
ago,
so
they
they
found
some
maintainers.
That
would
keep
her
running,
but
they
have
not
been
particularly
responsive
to
improving
stuff
over
time.
G
So
Frederick
was
tired
with
trying
to
keep
the
migration
scripts
running
to
support
people
that
were
using
the
cookie
cutter
copier
lets
you
do
that
internally
and
frankly,
we
should
just
make
that
a
dependency.
So
it's
not
another
tool,
Jupiter
lab
extension.
You
know
right.
F
H
Switching
integrated
in
I
really
think
the
the
I
mean
the
developer.
Experience
is
it's.
It's
not
good.
Now,
I
think
there's
too
many
tools
too
many
processes,
and
it's
there's
a
lot
of
churn.
C
So,
switching
from
cookie
cutter
to
copier
is
really
new
and
it
brings
this
one
major
thing
we
want
right.
Like
just
imagine
imagine
the
way
you
built
your
extension
was
actually
taking
an
extension
type
date
that
we
had
before
can
get
doing
whatever
and
then
constantly
rebasing
copier
is
supposed
to
help
with
that,
but
because
it's
new,
you
know
first,
it
was
rolling
it
out
this
way,
but
having
it
integrated
into
the
Jupiter
command
line
tool
would
be
great,
I,
don't
know
if
I.
C
To
work
on
it,
but
I
do
think
that's
a
good
idea.
H
And
I
think,
like
the
thing
that
I
always
think
of
right
is
I,
mean
I.
Think
a
lot
of
the
things
that
a
lot
of
decisions
that
get
made
are
a
lot
of
us
are
software
engineers,
and
we
do
really
software
engineering,
oriented
processes
and
use
a
lot
of
those
tools,
so
I
mean
I,
always
think
about
I
mean
how
do
we
accommodate
someone
who's,
a
whatever
a
data,
scientist
or
physicist
biologist
who's,
trying
to
write
an
extension
or
who's
trying
to
contribute
to
core?
H
A
Thank
you,
Eric.
Okay,
does
anybody
have
anything
else?
They
would
like
to
talk
about
on
the
record,
because
I
want
to
make
sure
I
save
time
for
off
the
Record
discussions.
A
Yeah,
thank
you
yeah
in
about.
Was
it
35
minutes
because
it's
10,
15
Pacific
35
minutes
accessibility
call.
Thank
you.
Tony.
A
Okay,
I'll
tell
you
what
I'm
gonna
stop
the
recording
momentarily,
so
brace
yourselves.
Three
two.