►
From YouTube: JupyterLab Team Meeting - 8 March 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
And
would
not
be
here
so
yeah
I
can
close
this
meeting
so
good
morning.
Everyone
please
sign
in
to
the
sign
in
sheet.
If
you
want
to
add
your
stuff
to
agenda
and
let's
start
with
Frederick.
C
C
C
The
trouble
that
I
have
seen
with
that
ID
is
that
typescript
has
a
roadmap
quite
that
then
they
are
respecting
quite
a
lot
about
which
date
is.
They
are
gonna
release
the
final
version
so
this,
but
they
don't
have
that
for
yarn.
As
far
as
I've
seen
so
yeah
I'm
a
bit
predictant
to
say,
let's
try
the
RC
because
yeah
if
we
can
really
Jupiter
4
without
waiting
for
yarn
four
yeah.
That
will
be
probably
better,
but
that's
my
opinion.
I
don't
know
if
others
have
other
thoughts.
A
Well,
any
comments
on
the
topic
no
Frederick,
so
you're
essentially
done
with
everything
you
wanted
to
talk
about.
No.
C
No,
it's
quite
different.
Oh
sorry,
different
topics,
I
will
let
some
some
space
for
people
to
comment
and
before,
instead
of
just
like
raising
everything
at
once,
yep,
okay,
thanks
Jason
for
commenting.
The
next
point
is
it's
about
the
magix
pr
I
don't
know
if
David
is
on,
the
cool
doesn't
seem
so.
D
C
B
C
C
So
that's
the
second
point.
The
third
point
is
about
mermaid
GS,
so
I
don't
know
if
you've
seen
but
Nick
was
very
efficient
to
provide
a
PR
for
supporting
the
same
features
that
GitHub
is
for
Mardon,
meaning
you
can
have
graph
in
more
down
that
will
be
converted
on
the
Fly
I
think
he
demonstrated
last
week
yeah
we
demonstrated
last
week.
C
So
I
commented
on
the
pr
that
one
of
The
Travelers
that
is
going
to
be
introducing
some
discrepancy
between
Jupiter
tool,
but
because
Nick
is
very
effective.
He
has
already
opened
up
here
or
soon
and
we
convert
and
to
support
that,
but
yeah
I
don't
know
like
what
should
we
do?
Should
we
rush
it
for
four,
or
should
we
wait
for
some
discussion
at
the
Jupiter
software
steering
console
but
seems
like
the
best
place,
because
it's
cross
project
features
yeah,
that's
basically
the
point
I
want
to
raise
like.
C
E
I
don't
know
I,
don't
know
how
hard
the
implementation
is.
So
I'm,
not
gonna,
talk
about
that
part
here,
but
Jupiter
lab
markup
has
had
this
for
quite
a
while
now
and
it's
a
great
feature
and
in
my
experience
when
I've
shown
people
that
you
can
do
mermaid
in
Jupiter,
it's
been
a
really
strong
feature
that
people
come
to.
So
you
know
just
from
the
user
side.
E
I
really
advocate
for
this
because
of
the
General
application
of
mermaid
on
both
GitHub
and
gitlab
now,
but
this
would
be
a
great
feature
to
have
without
a
extension.
C
As
we
don't
specify
so
much
markdown
in
Jupiter,
I
was
wondering
like.
Should
we
move
ahead
with
the
users
yeah
user
support,
or
should
we
back
up
a
bit?
That's
yeah,
that's
the
that's!
The
main
question
I
think
so
yeah
and
to
not
take
too
much
time.
Then
I
will
move
to
the
last
point
about
lumino
2..
So
I
was
hoping
to
get
lumino
to
final
release.
C
Last
week,
unfortunately,
we
have
seen
back
when
introducing
that
version
in
Jupiter
lab
and
in
Notebook
7.,
so
I
have
released
a
new
release.
Candidate
Jeremy
has
opened
up
here
on
Jupiter
lab
and
he's
been
merged,
so
I
I'm,
hoping
to
do
a
new
Alpha
of
Jupiter
lab
this
week,
so
that
we
can
also
have
a
new
version
of
notebook,
7
Alpha
and
when
those
two
are
out,
hopefully
we
don't
see
any
more
glitches
and
then
next
week
I
can
release
the
minute
to
final.
C
If
somebody
is
have
seen
some
additional
glitches,
if
they
have
tried
RC
yeah,
don't
hesitate
to
to
ping
me
or
open
an
issue
on
the
appropriate
Repository
yeah.
So
that
was
the
update
for
that
and
yeah
I.
Think
I'm
done
thanks.
A
Thanks
Frederick
yeah
is
if,
if
no
one
doesn't
have
any
questions
or
comments
for
that,
we
can
proceed
to
the
next
topic
to
Carlos
to
saving
the
behavior.
F
Thanks
yeah
I
wanted
to
discuss
the
Save
Us
action,
basically
right
now,
it's
broken
in
Jupiter,
lab
3.6
and
four
in
a
collaborative
mode.
The
reason
is,
basically,
they
save
us
action.
F
How
it
works
is
it
feels
it
renames
the
the
file
in
memory
and
then
it
tries
to
save
the
new
file.
So
once
the
user
ends,
saving
us
with
a
new
name,
basically
Jupiter
lab,
let's
say
kind
of
closes
the
old
document
and
opens
a
new
one
is
not
exactly
doing
that.
It's
just
renaming
the
name
that
we
have
in
in
memory
in
the
client
and
that
says
more
problem
for
FTC.
Basically,
so
it's
the
same
issue
that
we
were
seeing
where
we
were
duplicating
the
the
document
data.
F
Basically,
the
model
that
we
have
loaded
on
the
data
we
have
loaded
in
memory
is
not
going
to
be
the
same
that
we
have
in
the
in
the
bucket.
So
I
would
like
to
propose
to
change
the
behavior
of
the
action,
the
what
the
user
will
see
and
instead
of
renaming
the
file
that
the
user
has
opened,
opening
a
new
one
and
keeping
both
opens
that
way
for
FTC.
F
We
can
just
open
a
new
document
and
we
don't
need
to
rename
the
the
file
for
close
it
and
open,
and
in
November,
which
is
not
get
it
possible.
We
will
need
to
change
the
API
so
yeah
you
open
it
up,
pull
request
to
fix
the
they
save
us
in
RTC,
but
it
changes
the
behavior
just
take
a
look
and
yeah.
Let
me
know
what
you
think
on
that
beer.
F
G
F
So
we
are
creating
a
new
document
with
the
content
that
we
have
in
memory
and
then
we
keep
that
same
document
in
memory
we
just
rename
the
path
of
the
document
and
for
FTC
that's
a
problem.
The
main
problem
right
now
is
that,
right
now
it
doesn't
work.
The
the
reason
is
because
in
RTC
we
are
using
the
new
file
ID
service.
So
basically
the
document
is
not
identified
by
by
the
name
instead
by
uid.
F
So
when
we
rename
the
path
on
the
back
end,
we
detect
that
the
New
Path
is
not
the
same
document.
It's
a
mutable,
so
it
doesn't
allow
us
to
rename
that
a
document
in
memory
and
yeah.
Basically,
we
will
need
to
change
the
the
ux
behavior.
Let's
say:
yeah
save
us.
Instead
of
just
renaming,
it
will
be
opening
a
new
document,
so
the
user
will
see
the
old
document
and
the
new
one
not
sure.
G
So
is
that
effectively
like
having
a
make
a
copy
of
this
document?
And
then
you,
you
see
the
old
document
and
you
see
the
new
document.
Is
that
what
the
user
experience
is.
F
And
we
will
need
to
change
the
the
API,
so
basically
all
so,
all
those
actions
are
done
in
the
document
registry
context
and
it
doesn't
have
access
to
the
document.
Manager
I
mean
okay.
We
we
could
just
change
the
action.
Actually,
we
could
just
change
the
the
command
that
we
have
registered
in
a
common
palette
to
track
to
check
the
widget
that
we
have
open
open.
It
should
be
the
one
active
in
the
screen,
so
we
could
close
it
from
there.
A
H
Yeah,
so
just
out
of
technical
curiosity,
when
you
do
a
save,
as
when
you
get
a
new
document,
will
you
still
have
like
the
undo
state
from
the
previous
document?
Or
will
you
lose
that
yeah?
That's
as
I
I
guess
that
that
will
be
very
predictable
issue
on
on
the
the
repository
then
after
we
released
that
somebody
saved
us
and
they
lost
their
understate.
F
Yeah
yeah
in
nrtc
we
lose
the
state
without
FTC
and
we
could
maybe
keep
the
just
stay.
Let
them
do.
C
Colors
would
it
be
possible
to
to
do
the
save
as
like,
do
the
rename
and
then
do
a
duplicate,
because
I
think
also
in
RTC
case,
like
the
user,
that
is
working
with
another
user
on
the
document?
It's
it
looked
like
the
save,
as
is
closer
to
say,
I'm
renaming
the
current
thing
and
dumping,
a
duplicate
of
a
certain
state
of
the
the
document.
C
F
I
think
you
will
work
because
right
now,
they're
rename
it
works,
because,
basically,
when
we're
getting
in
the
file
in
the
back
end,
we
know
is
the
same
file
we,
so
we
can
rename
it
and
we
will
just
need
to
create
a
new
one.
For
me
from
that
file
right,
we
will
need
to
create
the
old,
the
a
new
file
with
the
old
name.
Let's
say:
oh
yeah
it
to
work.
C
Just
to
answer
to
Json:
it's
not
really
a
rename,
but
from
a
technical
point
of
view,
it's
closer
is
the
closer
closest
action.
If
you
want
to
keep
undo
and
hope
that
the
user
that
are
collaborating
are
still
in
the
same
document.
G
I
think
you'll
save,
as
is
more
like
checkpointing
a
document
and
then
and
then
working
from
the
checkpoint.
So
to
me
a
rename
is
I
want
to
change
what
I
call
this
document
and
bring
everyone
along
to
me.
A
save,
as
is
I'm,
going
to
step
out
of
the
collaborative
session
with
everyone
into
a
new
checkpoint,
but
I
don't
want
to
force
everyone
else
to
move
to
my
new
document
and
so
I
think
of
it
much
more
as
a
duplicate
leave.
G
H
Users,
they're
not
going
to
be
in
collaborative
state
right,
they're,
just
going
to
be
working
alone
on
the
document
and
when
you
click
save
as
you're
just
going
to
say,
like
all
right,
I
need
to
say,
I
can't
I
have
this
file
I
received
from
somebody
else.
I
made
some
edits
and
actually
I
don't
want
to
overwrite
the
Old
State
I
want
to
make
a
new
document
here,
version
two
whatever
and
when
I
save
that,
if
I
suddenly
lose
all
the
understate.
F
H
G
D
I
never
implemented
save
as
similar
I
think
Google
Docs
doesn't
have
CMS.
D
D
Different
I
want
to
take
a
different
direction,
and
then
you
save
as
you're
you
don't
it's
not
renaming
the
file,
it's
making
a
new
file
with
a
different
name,
but
you
still
want
the
same,
undue
State
and
like
you're,
going
to
continue
from
where
you
were
about
in
a
new
Branch
I.
Think
so
I
think
it's
a
sensible
thing
to
implement,
but
I
don't
have
the
answers
to
any
of
these
questions
for
cookout,
but
I
was
thinking
about
them
and
I.
D
Think
I
would
very
much
like
to
keep
the
undue
State
like
Microsoft
Word
does
and
then
keep
at
least
the
recent
his
time.
Travel
history
I
think
it's
a
good
idea
to
have
to
say
this,
but
Jason
your
question
of
what
happens
to
all
the
other
people
with
the
same
file
opened.
Is
there
really
interesting
one
like
for
example?
What
if
you
have
the
same
file
opened
on
another
browser
tab?
You
probably
wanted
to
just
have
the
new
name,
but
maybe
you
don't
and
I
don't
know,
I
really,
don't
know
it's.
D
It's
really
unclear
what
should
happen.
It's
a
lot
more
challenging
to
implement
if
you
make
it
so
that
it
closes,
and
then
you
get
the
new
file
for
everybody
else
too.
D
H
F
Yeah
I
believe
it's
technically
possible
yeah,
but
yeah.
We
need
to
implement
that
the
duplicate
action
in
The
backend,
let's
say
so,
basically
right
now.
What
we
do
is
that
when
a
new
user
joins,
we
open
the
document
from
disk,
then
we
create
a
y
update
with
that
document.
F
So
we
will
need
to
get
the
the
updates
from
the
whole
documenting
memory
in
the
backend
and
create
a
new
a
new
one
instead
of
loading
from
coming
disk.
It.
F
Yeah,
but
right
now
we
are
on
a
mixed
state.
We
are
still
using
the
old
API
with
some
parts
that
we
are
representing.
F
We
will
need
to
implement
everything
specific
for
your
TC
to
do
this
kind
of
operations.
A
Okay,
so
let's,
let's
probably
proceed
to
the
next
topic:
if
there
is
no
one
else,
has
any
questions
or
points
to
take
stuff
in
your
app.
J
Hi
guys
so
basically
I
remember
done
a
past.
Like
couple
weeks,
we
were
discussing
about
the
Google
season
of
docs,
so
I
instantly
thought
about
and
that
it
was
a
great
opportunity
for
the
accessibility
team
to
have
a
technical
writer
that
will
be
focused
on
writing
everything
that
we
want
to
write,
but
we
don't
have
any
bandwidth
to
do
it
right
now.
J
So
it
will
be
just
flag
all
the
features
that
users
can
have
for
accessibility
features
regarding
theming
zoom
and
everything
else,
and
the
second
part
will
be
just
to
have
like
a
user-focused
documentation
that
will
basically
State
the
like
it
will
describe.
The
current
state
of
the
accessibility
features
with
the
audits
that
I
know
that
is
available
and
myself
had
done
in
the
past
year,
which
are
about
the
keyboard,
navigation
and
the
400,
Zoom
audits
and
and
as
a
stretch
goal.
J
We
were
thinking
that
we
can
also
add,
like
a
FAQ
guide,
just
to
explain
how
to
develop
accessible
notebooks
that
will
be
more
for
users
and
both
developers.
So
yeah
that's
been
like
more
of
the
route
that
we
are
thinking
to
do.
I,
don't
know
if
it
like.
If
there's
anyone,
that's
interested
in
the
Google
season
of
dogs.
If
there's
another
proposal
that
we
are
thinking
to
send
or
if
this
sounds
right,
so
yeah
I
want
to
fill
the
room
with
this
idea.
C
Thanks
Stephanie
for
proposing
to
submit
something,
I
would
just
emphasize
that
if
there
are
people
that
want
to
extend
the
scope,
I
would
say
that
that
should
be
done
in
the
same
proposal
a
bit
like
what
we
have
done
for
CGI,
avoiding
to
provide
multiple
proposition
to
Google
doc
program
and
just
try
one
for
one.
Software.
A
Okay,
awesome
so
Isabella
you're
up
yep.
K
Sorry,
you
probably
hear
a
dog
but
I'm
just
here
with
my
usual
announcement,
that
the
Jupiter
accessibility
call
will
be
15
minutes
after
the
scheduled
end
of
this
one.
So
everyone
is
welcome.
I
see
we
have
some
stuff
on
the
agenda,
so
just
your
open
call
thanks.
L
I,
it
was
just
to
mention
that
I
opened
the
job
a
few
weeks
ago
to
add
a
new,
a
new
field
into
the
debugger
and
full
response
from
the
kernel.
So
it's
an
optional
field
and
I
was
wondering
what's
the
next
step
for
that,
because
it
should
be
totally
Backward
Compatible,
and
so
that's
it.
B
F
B
Can
I
just
drop
in
one
quick
admin?
Note
that
I
realized
is
that
next
week
most
of
the
United
States
moves
its
clocks
forward,
but
most
of
Europe
does
not.
So
that
means
that
until
Europe
moves
its
clocks
forward,
you
all
will
have
to
join
us
an
hour
earlier,
because
this
meeting
on
the
Google
Calendar
is
tied
to
the
U.S
specific
time
zone.
So
just
be
aware:
I
added
it
to
the
top
of
the
notes,
but
mark
your
calendars.
A
If
you
use
I
I
must
use
Google,
Calendar
and
Apple
calendar,
so
it
always
shows
all
the
meetings
in
my
time,
so
it
will
probably
be
adjusted
in
your
calendar
if
you
use
those
apps
yep.
Thank
you
for
this
announcement.
A
Does
anyone
has
anything
to
say
about
that?
Nicholas
was
talking
about.
G
K
I,
don't
want
to
make
a
promise
about
it.
I
just
know
as
we're
trying
to
get
a
software
steering
council
stuff,
spinning
up
I,
don't
know
currently
if
anyone
is
looking
at
jeps
until
that
is
the
case,
someone
can
correct
me
if
that's
wrong,
but
I
don't
know
quite
what
the
timeline
for
this
is
just
to
throw
that
out.
There.
I
Right
so
there
were
a
few
pull
requests
into
the
master
branch
which
unfortunately
broke
the
CI,
and
this
thing
happens
for
various
reasons.
And
one
of
the
reasons
is
that
when
the
bot
updates
the
snapshots,
only
part
of
the
tasks
of
the
CI
jobs
run
and
it
can
incorrectly
show
the
green
status,
whereas
some
of
the
jobs
didn't
just
run
because
it
didn't
have
permissions.
I
And
if
anyone
knows
the
solution,
how
to
fix
the
permissions
problem
of
the
Jupiter
lab
ports
so
that
it
always
runs
all
the
jobs.
And
that
would
be
great.
But
in
the
meantime,
I
propose
that
we
enable
marriage
protection
rule
on
Master,
specifically
requiring
that
the
linked
job
passes
every
time,
and
that
should
allow
us
to
have
a
visual
indication
that
some
of
the
jobs
haven't,
run
and
started.
I
And
yeah
I
see
the
questions.
So
first
I
just
wanted
to
reassure
that.
Everyone
is
an
owner
on
the
organization
with
administrator
of
permissions
can
still
bypass
this,
so
they
can
click
on
the
checkbox
and
they
will
still
be
able
to
match
if
there
is
a
situation
which
requires
that,
such
as
silently
managing
a
security
fix
for
example,
so
it
doesn't
prevent
mergers,
but
it
it
just
adds
an
indication.
I
And
we
could
either
choose
to
require
lots
of
jobs,
could
possibly
the
green
stages
of
just
one
and
I
think
that
that
means
like
the
least
controversial
one
which
should
always
pass.
So
what
is
happening
any
comments
to
be
devote,
or
do
we
have
a
consensus
to
see
that.
A
I
had
a
question
like:
is
there
an
issue
about
CI,
because
in
in
the
bullet
points
I
see
a
description
of
managing
a
protection
rule?
It
wanted
to
double
check
if
there
is
an
issue
to
track
the
CCI
problem.
A
Does
anyone
know
how
to
fix
the
rules?
The
permissions
yeah.
I
Oh,
no,
there
isn't.
So
there
is
an
issue
highlighting
which
snapshots
are
failing
and
there
are
already
two
pull
requests
trying
to
fix
the
situation:
mining
metrics
so
that
that's
being
quacked
on,
but
not
I.
I'm,
not
aware
of
an
issue
discussing
why
this
drops
too
much
one
so
yeah
I
can
create
one
and
we'll
link
that
in
the
notes.
Okay,.
A
A
So
no,
no!
Okay!
Look
at
that
now.
We
have
some
additional
discussions
points.
So
let's
go
through
those
Stephanie.
K
M
K
M
It
recorded
thank
you
yeah,
so
yeah.
This
is
I,
had
kind
of
met
with
folks
back
in
December
a
few
months
ago
and
a
previous
Dev
meeting
just
to
float
the
idea
of
hosting
a
few
Studio
days
this
year
and
so
much
delayed.
But
I
wanted
to
kind
of
resurrect
that
conversation
so
I
put
in
a
compass
issue
with
some
ideas
around
dates
in
April,
in
San
Francisco
and
for
New
York
in
August.
But
I
was
curious
and
wanted
to
bring
it
up
like
just
folks.
M
Thoughts
about
whether
having
it
on
a
weekday
or
a
weekend
would
be
more
accessible,
and
you
know
any
sort
of
advice
that
you
might
have
around
how
to
advertise.
It.
I
really
am
I'm
Keen
to
make
it
as
inclusive
as
possible
for
folks
that
are
in
different
fields
or
different.
Whites
might
see
this
in
different
channels,
so
yeah
a
lot
of
open
questions
there.
But
if
anyone
has
any
tips
or
advice
or
thoughts
on
like
weekdays
versus
weekends,
would
really
appreciate
that.
D
N
M
Oh
so
this
would
be
sort
of
a
full
day
event
where
folks
from
the
Jupiter
Community
can
come
together,
and
it's
very
open-ended
like
it's
different
than
a
workshop,
where
there's
not
going
to
be
a
structured
or
a
single
theme.
But
you
know
people
can
come
with
like
issues
or,
if
you're
very
new,
to
Jupiter.
It's
a
good
chance,
I
think
to
network
with
other
folks
in
the
community
that
you
might
not
see
day
to
day
or
pair
with
people
on
issues
that
you're
interested
in
tackling
or
picking
up.
K
It's
not
super
dissimilar
from
a
single
day,
Sprint
yeah
but
I
would
say
even
looser
than
that
and
scope.
O
G
Oh
I
see
some
people
might
be
there.
Awesome,
yes,
I
plan
on
being
there
too,.
M
Past
we've
tried
it
done
weekend
before,
but
then
weekdays
you
know
I
I,
think
maybe
we
could
do
one
versus
the
other
like
New
York.
It
might
be
trickier
to
do
a
weekend
event
just
because
of
how
the
office
works
and
the
booking
of
like
rooms
and
facility
support,
but
I
guess
the
other
piece
that
I
was
curious.
About
too,
is
like
once
we
have
dates
finalized.
M
What
would
be
the
best
way
to
advertise
it
just
outside
of
this
meeting
and
maybe
discourse
I
guess
in
the
past,
like
what
have
you
found
useful
outside
of
just
reaching
out
to
people
individually.
M
K
I
haven't
run
a
ton
of
events
where
I'm
confident
with
souljiling
I
know.
We
ran
the
Jupiter
accessibility
workshops
on
weekends,
with
the
intent
that
they
would
be
more
open,
but
I
I,
don't
know
if
that
actually
panned
out
I'll
say
okay,
so
that
is
like
not
a
large
sample,
so
I
could
be.
So
if
it's
easier
for
you
to
schedule
facilities
on
a
weekday,
my
guess
is,
it
might
at
least
be
worse
worth.
Trying
yeah.
M
Yeah,
maybe
yeah
I
can
try
one
on
the
other,
since
we've
got
at
least
two
dates
set
up
and
I
can
give
feedback
to
you
and,
like
let
folks
know
what
works
better
for
the
next
person
that
wants
to
organize
something
like
this,
but
yeah
more
to
come.
I
I
will
definitely
be
in
future
meetings
as
we
get
dates,
set
up
and
and
have
more
details.
Oh.
K
M
A
And
thank
you
very
much
Stephanie,
so
Gabrielle
and
Florence
your
app.
Please
note
that,
like
there
is
no
here
link.
P
So
I'm
working
currently
on
follow-up
of
PR,
starting
by
Jason
Grote
about
proposing
and
parity
detail
with
a
classic
notebook,
the
ones
that
enabled
to
display
the
shortcuts
and
so
working
on
this
it
appeared
that
maybe
it
would
be
worth
to
discuss
a
bit
more
what
we
want
to
have
in
this
shortcut
display,
or
we
want
to
organize
the
different
shortcuts
by
groups
and
so
right
now
there
is
a
logic
implemented
that
worked
very
well
that
we
were
thinking
about.
Is
there
another
way
to
organize
the
shortcuts?
P
B
Yeah
I
would
say
for
us
that,
when
we
talked
about
this
before
having
like
a
multi-column
layout,
was
discussed
before
so
that
things
could
be
more
visible
in
in
one
screen,
as
opposed
to
a
scrolling
display.
P
B
Think
that
this
looks
really
good
to
start
out
with
and
I
think
if
we
can
display
everything
as
a
sort
of
one
image
cheat
sheet
everything
visible
on
screen
at
once,
even
if
it's
wider,
that
might
be
even
better.
P
And
then
the
idea
when
you
have
different
currents,
so
then
it
would
be
maybe
easier
if
it
is
organizing
category
but
then
right
now
the
logic
is
so.
The
the
display
is
contextual
and
so
in
a
contextual
display
is
the
12
12
kind
of
category
all
not
I.
Don't
know,
I
totally
agree
that
it's.
It
would
be
better
to
have
everything
in
a
single
window
with
a
different
column,
so
I
I'm
thinking
about
how
to
do
this.
But
okay.
B
I
was
looking
at
the
screenshots
from
11960,
which
Jason
grout
had
written,
and
it
I
see
what
you
mean
by
having
like
the
category
listed.
There
personally,
I
think,
there's
a
better
way
to
organize
that,
like
we
could
organize
it
by
grouping
everything
under
the
same
heading,
for
example,
but
like
if
I'm
looking
at
how
Gmail
does
its
shortcuts,
where
it's
a
multi-column
layout
that
if
you
hit
the
question
mark
key
at
least
in
U.S
English,
you
get
something
that
I
I
just
dropped
into
the
chat.
O
Yeah
I
think
if
we
basically
all
agree
that
we
want
the
sort
of
one
screen
and
different
columns
as
much
as
possible
and
the
less
scrolling
as
possible,
and
so
now
the
the
question
is
well.
There's
two
questions
on
a
technical
side:
does
that
mean
having
to
do
everything
from
zero
and
I?
Don't
have
an
answer
to
that
and
on
the
ux
side?
I,
that's
why
I
wanted
to
have
another
meeting
so
that
I
could
understand
what
would
be
the
best
groupings
and
what
goes
where
and
from
my
user
perspective.
A
So
there
are
I
would
say
there
are
a
couple
of
ways,
but
one
really
popular
way
is
a
Google
form.
You
can
create
a
Google
forms.
It
would
like
ask
questions
for
from
person,
people
who
would
like
to
register
right
if
you,
if
you
already
know
date
and
time
that
you
want,
if
you
don't
know
date
and
time
that
you
want
in
Jupiter
lab
Community,
it's
a
really
geographically
diverse
community,
so
choosing
a
good
date
and
time
is
usually,
you
know
like
a
problematic
point.
A
So
something
like
doodle
or
what
is
good,
might
be
a
good
way
and
is
which,
whichever
medium
you
choose
to
let
people
register
you
should
post
a
link
in
this
nodes.
B
B
A
K
And
if
you
want
it
to
be
public,
which
I
would
personally
encourage
it
to
be,
though
I
I
guess,
you
can
always
be
on
the
Jupiter
community
calendar
so
that
people
don't
have
to
register
necessarily
I,
don't
know
if
that's
the
goal
or
not.
O
E
Is
there
space
to
at
a
usage
Point
here
or
are
we
still
sorting
out
the
meeting?
I
think
the
win
is
good
thing
would
be
great
I'd
love
to
attend
this.
This
is
a
great
feature.
We
need
it
in
lab.
E
So
one
of
the
things
I'd
like
to
think
about
in
designing
this,
maybe
is
what
happens
when
you
learn
keyboard
shortcuts
over
time.
So
for
me,
like
the
scrolling,
part's
super
important
because,
like
as
I
gain
skills
with
keyboard
shortcuts
and
they
become
muscle
memory,
I'm
going
to
want
to
learn
more
of
them.
E
So
to
me,
this
keyboard
shortcut
thing
actually
seems
like
a
way
to
almost
measure
progress
because
the
more
keyboard
shortcuts
you
are,
the
more
efficient
you're
getting
and
I
could
totally
see
this
as
a
way
for
people
to
up
their
skills.
Significantly
with
the
right
information
presented
here,.
A
N
Thank
you,
I'm
just
getting
to
this
issue
and
there's
so
I
see
there's
a
lot
of
discussion
if
they
don't
have
time
to
parse
it
in
this
like
at
this
exact
second,
but
my
understanding
is
right.
N
Now,
there's
no
ability
to
put
keyboard
shortcuts
in
Jupiter
lab
correct,
like
this
keyboard
shortcut,
it's
all
new
I,
just
I
guess
I
just
want
to
express
like
one
thing
here,
which
is
even
if
you
have
to
scroll
and
the
current
iteration
here,
uncategorized
I
feel
like
that's
better
than
nothing
so
I
just
hope
it
doesn't
get
like
perfect.
B
Yeah
I
don't
think
that
it's
like
either
Jason's
or
Florence's
concepts
are
bad.
It's
just
that
we
haven't
committed
any
of
them
yet
and
I
think
maybe
setting
out
like
a
road
map
to
say,
commit
version
one
once
we're
satisfied
with
it
then
make
version
two
and
so
on.
As
long
as
someone's
interested
in
improving
on
it,
I
agree.
P
A
A
Okay,
if
there's
not
something
else
to
add
Let's
end
the
recording,
and
then
we
can
proceed
with
other
things,
such
as
Char
charging,
4.0.0
issues
thanks
thanks
for.