►
From YouTube: JupyterLab Team Meeting - December 14, 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/152
A
A
A
B
Hello,
everybody.
So
a
couple
of
announcement
on
my
side
there's
been
a
new
announcement
of
a
new
Jupiter
Community
Workshop
that
will
be
focusing
on
the
notebook
file
format,
so
orgies
and
stuff,
or
maybe
something
else
depending
on
the
output
of
the
workshop
and
so
I
think
they
are
the
block
and
there
is
on
the
blog
post
like
more
details
and
also
the
the
form
to
to
apply
for
the
workshop.
B
So
that's
for
the
first
announcement,
the
other
one
is
I
found,
sometimes
to
go
back
to
working
on
a
version
of
the
rice
extension
for
Jupiter
lab,
so
race
extension
has
been
done
by
Damian
and
the
classical
notebook
is
very
popular.
But
there
were
no
versions
to
know
for
Jupiter
lab
I
opened
I.
B
Think
last
year
a
PR,
the
undecision
was
to
make
it
a
separate,
a
separate
python
package
and
so
I
went
ahead
and
released
it
as
a
separated
package,
and
it's
also
a
store
in
in
the
separate
repository
because
I
needed
to
upgrade
like
reviewed,
GS
and
stuff
like
that.
B
So
those
are
for
the
announcement.
So
just
a
status
on
drift
3.6,
it
has
been,
have
been
a
bit
stall
for
doing
the
release.
The
only
feature
missing
is
the
one
about
the
announcement.
Thanks
for
people
that
have
reviewed,
especially
Mike
I
hope,
I
have
taken
all
the
comments
into
account.
B
So
what
CID
is
that
the
somebody
wants
to
look
at
it
or
is
it
okay
and
can
we
move
on
and
could
we
start
doing
the
better
release
yeah
and
regarding
36
other
than
that,
then
there
are
still
some
some
fixes
to
be
done
on
the
CI
so
but
I
think
it
doesn't
block
starting
to
ever
the
beta
like
because
if,
as
usual,
if
we
start
to
have
the
beta
this
week,
that's
mean
that
we
are
gonna,
have
the
final
for
the
end
of
the
year
because
of
the
one
week
between
beta
and
release
candidate
and
then
an
additional
week
for
final
release.
B
And
so
for
the
workshop
for
no,
the
idea
is
to
try
to
have
as
much
as
possible
people
in
person
because,
like
the
dynamic
of
those
kind
of
Workshop,
is
really
better
if
people
can
really
meet
just
like,
for
example,
due
to
the
shift,
I
was
amazed
like
for
the
Jupiter
Elite
Workshop,
like
Nick,
woke
up
very
early
and
to
attend
like
after
the
this
night,
but
I
think
it
makes
the
the
workshop
more
productive
if
people
can
be
in
person.
But
if
there
are
lots
of
requests,
then
of
course
we
can.
B
We
can
set
up
something
remotely
and
there
is
always
also
the
the
backup
plan
due
to
that
may
hit
us.
A
Did
you
have
a
recommendation
for
this
issue
that
you
linked
them?
Men
opened
about
the
location
for
workspaces
settings,
or
did
you
just
want
to
raise
it
as
a
conversation
for
people
to
chime
in
on.
B
B
I
was
not
so
much
there
and
I
mean
I'm
a
bit
less
comfortable
with
the
configuration
path,
handling
and
stuff
like
that
in
the
Jupiter
stack,
so
yeah
I
would
appreciate
if
people
that
are
that,
if
a
bit
more
experience,
especially
in
that
kind
of
discussion,
can
wave
into
just
say
it's
okay,
I
think
it's
perfectly
fine
I
mean
I
mean
knows
what
he
is
doing.
It's
just
to
justif,
to
provide
him
with
a
feedback
for
it.
A
Okay,
so
before
this
gets
lost,
is
there
anyone
on
the
call
who
is
able
to
review
the
announcement
feature,
that's
the
little
pop-up
that
gives
you
Jupiter
related
news.
Basically,.
C
D
A
A
Well,
actually,
it's
interesting
that
you
ask
that
I
think
there
are
a
few
angles
right.
There's
the
user
experience,
there's
the
code
review
and
then
there's
the
security
stance
that
we
might
be
taking
the
Privacy
stance
Etc.
So
you
being
a
member
of
the
security
group
and
the
Jupiter
lab
group
are
well
positioned
to
look
at
it
in
that
regard.
A
B
D
Okay,
I've
done
a
little
bit
of
review
on
kind
of
the
phrasing
and
and
language
used
in
it,
but
I
can
take
another
look
at
that
today.
D
A
And
then
the
last
point
you
had
here
will
we
have
a
call
in
December
28th
when
we
just
take
a
quick,
remote,
maybe
use
a
thumbs
up
or
thumbs
down?
If
you
think
you
will
make
it
to
a
call
on
the
summer,
28th.
A
A
A
A
A
D
Oh
yeah
sure
I
just
had
a
quick
plug
for
Jupiter
scheduler,
which
my
team
at
AWS
worked
on.
We
announced
a
commercial
product
based
on
it
at
AWS
re
invent
last
month,
but
it's
been
available
as
open
source.
We
just
held
off
on
announcing
it
until
this
morning,
when
the
blog
post
went
out,
so
I
pasted
a
link
to
it
in
the
chat.
D
It's
also
in
the
notes,
thanks
to
everyone
in
both
both
within
AWS
and
in
the
broader
Community,
who
helped
us
to
get
merged
in
Jupiter
scheduler
lets
you
run
notebook
jobs
unattended,
either
as
a
one-off
or
on
a
recurring
schedule,
and
you
can
also
customize
it
to
run
based
on
the
custom
back
end.
So
it's
it's
pretty
neat
I!
Hope
you
like
it.
If
not
file
some
issues
and
we'll
get
it
improved.
D
A
Congratulations
and
thanks
for
the
announcement,
okay,
Eric
Gentry,
you
are
up
hey.
F
So
I
talked
to
Darren
about
this
in
the
notebook
meeting
a
little
bit,
but
I
have
improvements
that
I
am
almost
done
with.
So
these
are
improvements
for
the
extension
tutorial
docs.
F
So
I
basically
just
want
to
kind
of
merge
these
improvements
and
make
it
public
so
that
the
current
docs
are
not
broken
for
people,
and
the
experience
is
good,
so
I
just
wanted
to
kind
of
check
on
what
the
best
way
forward
would
be
based
on
what
daring
was
saying
it
looks
like
I
should
be
merging
into
master,
and
so
that's
what
I'm
going
to
try
to
do
going
forward
here
on
my
PR,
so
I
had
a
couple
of
questions.
F
I'm
just
wondering
I
guess.
The
first
question
is
I
know
how
to
build
on
36x.
I
know
how
to
build
a
docs
on
thanks
to
Frederick's
help.
F
I
I
was
able
to
get
rid
of
the
the
JavaScript
API
doc
build
process,
so
that
allowed
me
to
build
locally
I'm,
just
trying
to
figure
out
on
Master.
What
would
be
the
process
for
building
the
dock
should
I,
just
for
and
for
the
purposes
of
previewing
locally
should
I
just
be
pulling
that
environment.yaml
file
over
and
building
another
running
the
same,
build
process
on
master.
A
So
last
week,
I
did
a
get
clean
so
that
I
knew
I
had
a
complete
Blank,
Slate
I
even
deleted
my
local
user
yarn
cache
and
then
I
did
the
recommended,
build
process
and
a
contributing
file.
You
know
the
PIP
install
Dashie
and
all
that
and
then,
when
I
had
the
jlpm
tool
installed
after
the
PIP
install
I
ran
jlpm
docs
and
it
did
work
for
me
in
a
clean
conda
environment
with
a
clean
repo
and
a
clean
yarn
cache.
So.
G
A
You
try
that
set
of
you
know
kind
of
blank
slate
and
it
doesn't
work
for
you,
whatever
errors
that
are
generated,
I
think
raising
that
as
your
issue
in
the
Jupiter
lab,
getter
and
or
in
your
PR
and
then
maybe
tagging
me
and
whoever
else
is
already
participating.
Okay,
it's
probably
your
best
path
forward,
because.
F
That's
good
I'll,
give
that
a
try
and
then
just
in
terms
of
I
guess
like
I'm
just
trying
to
understand,
because
my
goal
here
is
to
merge
this
in
and
and
get
these
improvements
out
there
do.
We
need
a
full
release
of
the
lab
to
get
these
docs
improvements
published
or
how
is
that
going
to
work,
because
the
current
extension
tutorial
right
now,
if
you
search
Jupiter
lab
extension,
tutorial
read
the
docs
stable
is
what
comes
up
so
I'm
wondering
like
do.
A
So
stable
will
probably
the
next
stable
will
be
3.6
right.
It
won't
be
four,
it
won't
be
what's
in
master,
so
if
you're,
if
the
content
of
your
changes
is
applicable
to
both,
then
writing
it
for
master
and
then
having
a
back
Port
PR
for
three
six
is
sensible,
but
Fred
has
his
hand
up,
and
he
knows
more
so.
Okay,.
B
Actually,
I
don't
know
more
I
just
realized,
because
a
user
asks
a
question
about
the
announcement
feature
or
the
notification
feature,
because
actually
the
configuration
makes
it
so
that,
as
soon
as
we
created
a
branch
like
a
3.x3.6.x
branch
and
then
read
the
docs
move
stable
to
that
Branch,
although
there
is
not
yet
any
stable
version,
so
and
I
I
even
don't
know
how
to
switch
it
back.
I
think
that's
where
the
the
option
in
the
Ducks
are
a
bit
faky
for
for
specifying
exactly
which,
for
which
branch
you
want,
but
yeah.
F
Okay,
so
yeah
I
could
I
guess
then
I
would
plan
to
Target
both
so
I
guess:
I'll
try
to
do
Master
and
then
do
a
back
port
to
36x
and
then
hopefully
that
would
then
show
up
in
stable
right
well,.
A
F
A
F
B
F
Cool
all
right
thanks,
guys,
really
appreciate
the
help.
Frederick
Darian
and
Mike
krasowski
really.
A
A
Maybe
that's
configurable,
but
apparently
it's
not
currently
configured
this
way.
If
anyone
understands
the
read
the
docs
environment
configuration
and
and
knows
how
to
do
this,
yeah,
we
probably
should
be
using
tax
for
this
purpose,
because
it
really
is
not
the
case
that
3.6.x
is
stable.
That's
actually
incorrect.
A
Okay,
Ox,
you
are
up.
G
Yeah,
just
a
quick
update
for
me:
I
can
share
a
little
bit
more
information
once
the
recording's
over,
but
my
bandwidth
has
been
reduced
for
specifically
Dev
work
on
Jupiter
lab
in
the
upcoming
months,
so
I
am
no
longer
working
on
the
launcher.
2.0
work
for
now.
G
So
if
somebody
really
wanted
that
and
wants
to
jump
on
it,
they
can
and
I
can
help
kind
of
go
through
the
design.
I'll
try
to
get
that
commented
on
the
issue
soon.
I'm
excited
to
do
a
lot
of
work
on
kind
of
Designing
and
getting
it
figured
out
how
I
was
going
to
do
it
yeah
not
going
to
be
working
on
that
at
least
for
the
foreseeable
future.
G
A
A
H
H
It
shows
the
server
status
on
on
top
right
and
also
an
app
menu
that
you
can
reach
to
like
preferences
of
the
application,
and
it
also
shows
a
control
box
on
Windows
and
Linux
to
close
maximize
and
restore
and
so
on,
and
this
version
also
has
support
for
teams,
light
team
and
dark
team
and
also
assistant
team.
Whatever
you
have
in
the
OS
is
applied.
This
theme
is
applied
to
dialogues
plus
the
Jupiter
lab
UI
that
you
have
so
they
are.
H
They
can
be
kept
in
sync
and
I
created
new
dialogues
using
the
Jupiter
UI
toolkit
Library,
so
that
we
have
a
modern
and
modern
UI
and
consistent
UI
across
the
dialogues,
and
it
works
really.
Nice
and
I
also
introduced
a
New
Jupiter
UI
mode,
which
is
which
I
call
web
app
mode.
This
basically
load
Jupiter
lab
in
in
a
embedded
browser
without
customizing
anything,
and
this
resolves
a
lot
of
compatibility
problems
we
were
facing,
and
another
major
upgrade
here
is
this:
the
electron
upgrade
and
the
security
upgrades
include
in
this
release.
A
A
Okay,
cool
Gabriella:
you
are.
I
Hi
everyone
so
I
was
just
wanted
to
inform
you
that
unless
anyone
strongly
opposes
I
wanted
to
create
this
new
repo
on
Jupiter
lab
on
ux
Research,
so
I
focused
on
new
X3
for
search
and
not
design.
I
know
there's
a
repo
in
Jupiter
about
surveys,
but
it's
just
sort
of
for
the
results
of
the
surveys.
I
I
would
really
like
to
create
a
space
where
I
or
anyone
puts
old
documentation
about
our
personas
who
uses
Jupiter
lab,
and
so
we
can
all
document
it
as
we
go
the
user
Journeys
information
about
how
to
do
some
testing.
If
ever
people
want
to
do
quick,
sort
of
quick
and
dirty
user
tests,
different
ways
of
creating
a
study
and
then
some
all
the
study.
Examples,
of
course,
and
the
results
yeah
I
know
there's
this
repo,
but
it's
on
Jupiter.
I
It's
like
design,
focused
I'd
like
it
to
be
research,
focus
and
to
make
a
difference
between
user
research
and
the
design
assets
like
the.
We
could
have
a
that.
We
both
really
good
to
create
a
design
system
and
put
the
design
assets,
but
I
think
it's
going
to
be
something
very
different
from
a
ux
research,
Whipper.
A
Yeah
yeah
there's
some
work
that
will
happen
on
the
file
system,
but
other
than
that
yeah
you're
right,
I
think
what
do
we
normally
do?
Do
we
normally
just
have
a
team
Compass
issue
proposing
in
the
repo
and
we
voted
on
it
or
I?
Think
renaming
this
one
seems
reasonable,
especially
because
there's
almost
certainly
not
that
many
incoming
links
to
it.
So
so
how
about
this
is
the?
Is
there
anyone
on
the
call
who
objects
to
renaming
Jupiter
lab,
slash
design.
I
A
I
J
I
I
don't
see
any
reason
with
doing
this
or
not
doing
this.
To
be
honest,
I
just
caution
that
the
design
influence
in
this
space
is
small
relative
to
the
developer
influence.
So
you
know
just
trying
to
have
more
Consolidated
spaces
for
designers
and
more
General
places
might
be
helpful
if
we're
going
to
see
this.
J
Otherwise,
if
you're
going
it
alone.
Just
do
your
thing.
You
know,
but
yeah
yeah,
the
I
think
some
of
this
was
originally
motivated
by
having
a
more
General
space
for
designers
in
Jupiter,
as
we
tried
to
figure
it
out,
but
we
weren't
really
able
to
sustain
it.
J
So
I
agree
with
you.
I
agree
with
you,
but
I
think
that
a
small
repo
isn't
the
proper
place
for
some
of
that
stuff
I
mean
some
of
this
gets
back
to
another
sticky
situation,
which
is
the
Jupiter
website
right,
like
the
Jupiter
website
should
say
who
uses
this
and
what
tools
are
out
there
too.
I
It
would
be
a
lot,
it
would
be
a
lot
to
put
I
mean
I
mean
real,
like
a
lot
of
documentation.
It's
not
just
like
a
few
sentences
on
who
uses
it.
J
No
I
think
you
know,
make
a
safe
space
for
yourself,
and
you
know
your
allies
and
stuff
and
get
that
going.
Whatever
is
going
to
make
this
these
repos
succeed,
they
I
think
make
it
happen.
A
Okay,
so
as
a
Next,
Step
I
think
unless
there's
an
objection,
why
don't
we
rename
this
and
if
it
turns
out
to
be
a
place
where
only
you
find
yourself
doing
stuff
Gabriella
and
it
ends
up
being
frustrating?
We
can
figure
out
how
to
improve
that
situation,
but
as
a
starting
point
it
seems
reasonable
and
yeah.
That's
a
good
question.
Tony's
asking:
is
there
stuff
in
the
main,
Jupiter
lab
repo
that
can
be
moved
into
there?
A
I
don't
know,
I,
don't
know
the
answer
to
that.
But
Mike
appears
to
believe.
Yes,
that's
cool,
so
I'll
ask
a
question
again:
anyone
object
to
renaming
design
to
ux
research.
A
K
A
Okay,
great
cool!
No,
as
I
see
your
bullet
point
there
thanks.
A
We
have
two
more
updates
before
yours
and
next
person
is
me,
so
I'll
make
mine,
quick,
I've
linked
to
a
PR
that
creates
a
new
type
of
Jupiter
lab
plugin,
specifically
for
swapping
out
the
Jupiter
lab
application,
Level
service
manager
that
connects
to
the
rest
and
websocket
endpoints,
and
allows
you
to
replace
that
with
your
own
service
manager.
This
has
been
a
request
that
we've
had,
because
the
only
way
to
do
that
currently
is
to
actually
generate
your
own
Jupiter
front-end
application
and
set
it
there
and
you
could
do
an
application.
A
Now
you've
always
had
the
ability
you
were
either
willing
to
cast
the
application
to
unknown
in
typescript
and
then
cast
it
to
any
or
if
you
were
writing
your
extension
in
JavaScript
to
just
do
app.servicemanager
equals
Foo.
The
downside
of
that
is.
If
anyone
else's
plugin
had
loaded
before
and
they
were
subscribed
to
signals,
then
they
would
basically
have
code.
A
That's
never
going
to
get
executed
based
on
an
old
service
manager,
but
you
still
could
roughly
pull
this
off
and
if
you
go
to
the
pr
you'll
see
that
there's
a
back
and
forth
primarily
between
me
and
Eric
Charles,
although
I
think
Jeremy
chant
in
at
the
end
as
well
about
the
security
implications
of
this.
A
So
I
think
we'll
wait
for
a
representative
of
the
security
group
to
take
a
look
again.
Maybe
Jason
wall
can
and
if
not,
then
we'll
actually
have
a
conversation
in
the
security
group's
next
call.
I
personally
believe
there
is
zero
new
security,
Vector
Eric
disagrees
and
I
don't
want
to
have
a
two-person
back
and
forth
infinitely
on
GitHub.
So
hopefully
other
people
can
chime
in
I.
I.
D
Yeah,
just
as
a
to
clarify
the
next
security
meeting
is
currently
scheduled
for
next
Tuesday,
the
20th
at
8
A.M
Pacific,
although
I'm
not
sure
how
big
the
turnout's
gonna
be,
I
will
be
there,
but
others
may
be
on
Christmas
break.
So
we
may
have
to
revisit
this
in
the
new
year.
A
E
Yeah
I,
just
wouldn't
in
general,
want
PR
statistics
that
don't
reference
any
issues
to
have
some
sort
of
motivation
in
the
op
just
like
why?
Why
are
we
doing
this?
What
will
this
gain
us
stat
also
makes
it
easier
for
people
who
are
coming
in
sure.
A
E
Initiative
to
to
or
or
put
it
in
the
pr
thing
itself,
just
like
what
what's
the
purpose
of
it
and
what
is
the
weaknesses
of
the
current
thing.
E
Yeah
because
I
I
think
I
know
what
it
will
do,
but
unless
I
have
a
firm
idea
of
what
what
the
goal
is
and
what
what
the
problems
are
it's
hard
to
say.
Why
do
why
do
shouldn't?
Could
we
do
this
instead
or
you
said
you
were
going
to
do
this,
but
the
pr
does
that
you
know
so
it's
it's
a
lot
easier
to
review.
If
you
have
such
a
a
piece
sure.
A
Yeah,
no
I'm
happy
to
write
a
bit
more
description
on
the
motivation
and
what
what
I
believe
this
provides.
People
yeah.
Yes,.
A
Yeah
sure
thing:
okay,
if
anyone
else
has
any
comments
about
the
service
manager,
not
the
time,
if
not
I'll,
move
on
okay.
The
other
thing
is
that,
as
many
of
you
are
aware,
the.
C
Oh
I
I
just
wanted
to
point
out
a
couple
of
years
ago.
I
almost
wrote
a
plug-in
like
this
or
considered
this,
because
we
were
overriding
and
super
lab
application
and
we
needed
a
different
communication
mechanism
because
of
how
we
were
embedding
it
in
in
the
larger
context
Etc,
and
we
came
to
the
conclusion
that
it
really
did
make
sense
to
override
the
Jupiter
lab
application
to
provide
a
different
service
manager.
C
That
I
don't
know
it
yeah
that
it
just
if
you're,
if
you're
customizing
things
at
that
deep
of
a
level,
it
made
sense
to
go
ahead
and
just
override
the
Jupiter
lab
application,
rather
than
punt
it
to
a
plug-in.
So
I'm
really
curious.
What
your
motivation
is
for
this
well.
A
Now
we
have
something
that
we
didn't
have
a
few
years
ago.
That
demonstrates
to
me
a
really
compelling
use
case,
which
is
Jupiter
light.
It
would
be
really
cool
if
Jupiter
light
just
had
a
plug-in
that
swaps
out
the
service
manager
for
something
that
runs
entirely
client-side
without
having
to
be
a
whole
other
application.
A
If
Jupiter
light
really
can
be
a
spin
of
lab
with
a
set
of
plugins,
and
this
plug-in
means
you
don't
have
to
talk
to
the
server
that
seems
pretty
cool
to
me
and
in
general
I,
don't
have
a
really
imaginative
view
of
this
other
than
to
say
most
other
pieces
of
Jupiter
lab
can
be
swapped
out
with
plugins,
and
this
one
has
been
special
and
difficult
to
do,
but
it
it
doesn't
have
to
be
so
I,
don't
I,
don't
have
like
an
open
and
shut
like
really
compelling
case.
A
It's
just
it
seems
like
low
hanging
through
and
it
seems
like
I
can
think
of
one
use
case.
That
would
benefit
from
it.
C
You're
on
yeah,
the
flip
side
of
that
is
it
I
just
scanned
your
PR,
it
looks
like
it
does
put
some
restrictions
on
the
extension.
That's
doing
this,
so
it's
not
the
same
as
just
a
vanilla
extension
overwriting,
some
random
part
of
Jupiter
lab
like
there.
It
is
treating
this
extension
somewhat
special
with
special
restrictions,
yeah.
A
But
we
already
have
firearm
for
that.
Mime
renderers
are
special
extensions
too,
and
in
fact,
in
the
notebook
call.
Today
we
had
a
discussion
about.
Perhaps
we
need
to
define
a
notebook
plugin
because
sooner
or
later,
we're
going
to
want
to
give
people
a
way
of
knowing
whether
their
plugins
compatible
with
both
Lobby
and
notebook,
and
we
don't
currently
have
that
so
there's,
probably
some
flexible
thinking
in
the
space
that
we're
gonna
do
in
the
coming
year.
E
So
you
mentioned
the
randomized
plugins
already
exist,
but
that's
a
special
kind
of
plug-in
that
is
built
on
top
of
the
regular
plugin
system
right.
What
we're
saying
here
that
this
is
a
this
is
a
magical
extension
that
the.
A
It
doesn't
have
dependencies,
it
doesn't
so
it
takes
a
minimum.
It
takes
all
the
optional
lumino
application,
plugins
attributes,
and
it
removes
them.
It
says
they're
not
available
to
you.
All
you
can
have
is
activate
you
get
a
lumino
application,
not
a
Jupiter
front
end,
not
a
Jupiter
lab,
and
you
provide
this
one
token.
It
is
special.
It
is
weird,
but
then
again,
someone
who
says
I
want
to
use
a
whole
different
back
end
is
doing
something
special
and
weird
and
they're
doing
something.
Presumably
pre-application
they're,
not
saying
also
give
me
a
command
palette.
C
A
Its
own
hype,
it
has
its
own
type
and
it
is
like
the
the
whole
thing
is
at
least
enforced
on
a
typescript
level
right,
and
we
can
probably
put
in
some
developer
friendly
warnings
and
stuff
like
that.
Like
suppose,
you
write
the
JavaScript
version
of
it
or
something.
Maybe
we
throw
in
some
warnings
that
say:
Hey.
Look.
You
have
dependencies
here.
This
isn't
going
to
work,
something
like
that.
A
Maybe
I
propose,
because
this
is
not
going
to
move
until
we
talk
about
it
next
week
anyway,
that
we
move
on
because
we're
running
a
bit
low
on
time.
Vidar
is
that,
okay
with
you.
E
Yeah
but
just
forgot
to
remove
lower
my
hand.
A
Oh
okay,
cool,
okay,
so
I
was
gonna.
Just
quickly
update
people
on
the
executive,
Council
election,
it
happened
and
between
the
results
being
tabulated
and
an
announcement
being
made.
There's
a
phase
where
all
six
members
of
the
nascent
executive
Council
need
to
disclose
their
interests
so
that
we
can
resolve
whether
there
are
conflicts
of
interest.
Once
that's
resolved,
we'll
be
making
an
announcement
and
I'm
pretty
sure
that
announcement
will
be
on
Monday.
A
E
E
E
B
The
actually
I
only
have
opened
one
PR
that
I
put
in
Old.
That
would
remove
an
endpoint
because
in
my
refactoring
of
the
extension
manager,
I
changed
the
logic
for
and
the
listing
endpoint.
You
know
the
ability
to
say
a
white
list
or
Blacklist
some
extension,
because
now
everything
is
on
the
on
the
server
side.
So
the
front
end
doesn't
need
that
endpoint
directly,
but
I
did
not
merge
it,
and
so,
as
far
as
I
know,
we
can
move
on
like
this
and
not
change,
not
if
breaking
change
at
the
Jupiter
lab
server
level.
G
G
E
Location
of
the
preferred
there
on
the
contents
manager
interpreter
server,
and
they
don't
have
the
latest
version
of
triple
lab.
It
will
just
be
ignored
right
or
Jupiter.
Lab
server
I
mean
so
it's
hopefully
not
going
to
be
an
issue,
but
I
just
wanted
to
make
sure
make
sure
I
wasn't
needing
to
backboard
anything
or
do
some
extra.
A
K
Hello,
so
I
will
make
a
small
demo
of
an
extension
that
we've
been
working
on
the
past
two
months.
It's
mainly
prototype
for
a
Sim
editor.
K
K
You
can
also
play
on
the
font
size,
for
instance,
and
also
I-
have
implemented
some
fonts
family
in
order
to
be
able
to
to
change.
So
it's
not
working
this
time,
but
it's
working
it's
because
of
the
of
Zoom
I
think
so
the
idea
is
to
be
about
for
a
user
to
to
play
with
this
different
variable,
and
if
the
user
is
IP,
then
the
ID
is
also
to
implement
something
to
export
the
team.
So
it's
not
made
right
now,
but
I
will
do
it.
So
that's
it.
K
If
you
have
any
suggestion
of
things
that
can
be
added
or
changed,
please
feel
free
to
propose.
Thank
you.
A
K
K
C
K
Sorry,
yes,
I
will
I
can
share
for
the
moment
it's
only
on
my
repo,
but
we
will
be
great
to
soon
to.
A
A
All
right,
I
think
just
from
the
sampling
of.
A
E
A
E
Yeah,
because
because
the
main
thing
I
would
say
that
the
main
thing
that
is
once
you
have
a
teaming
system,
UI
there
that
works,
the
the
very
next
thing
you
will
want
is
an
export
button
right
so
that
you
can
share
your
awesome
team
with
everybody
else
without
having
to
you
know,
be
an
npn
master
or
yeah.
I
really
know
about
git,
orb
and
anything
right.
Maybe
this
is
a
file.
I,
don't
know
how
teams
are
best
shared
other
than
true
npm
packages
or
python
packages
right.
A
E
So
is
there
that
might
be
a
more
Central
thing
to
improve
if
there
is
room
for
improvement,
but
but
yeah
I
just
know
that
once
once
this
is
out
there,
the
very
first
question
people
will
have.
This
was
like
cool.
How
can
I
share
this
theme?
I
made
with
my
friends
or
my
team
or
whatever.
A
Right
Tony.
J
J
It's
people
who
get
really
excited
about
being
able
to
change
the
UI,
but
yeah
for
a
while
deathbeds
has
had
like
a
real
Lo-Fi
version,
which
we've
always
had,
which
we
always
do,
but
this
one
has
fonts
in
it
which
seemed
to
be
a
challenge,
but
there's
also
I,
guess
you
can
call
it
a
primitive
configuration
system
for
this
for
the
themes.
J
So,
basically,
what
we're
doing
is
putting
like
a
style,
CSS
sort
of
syntax
in
the
Jupiter
config
files
and
sharing
those
around
is
Json,
and
that
helps
with
the
configuration
here.
But
yeah
I,
don't
know
if
this
helps
with
thinking
about
the
problem.
The
configuration
part
a
little
bit.
A
B
Just
to
mention
that
the
next
step
for
the
extension
is
to
have
a
server
site
that
will
reuse
the
cookie
cutter
to
try
to
produce
an
extension
that
will
be
set
up
with
the
the
value
that
the
user
is
is
chosen,
but
yeah
that
leaf
still
open.
The
question
like
how
can
I
still
edit
that
version.
A
Again
so
Florence,
thank
you
so
much
okay,
so
she's
linked
the
repo.
If
you
are
chomping
up
the
bit
to
play
with
it,
go
check
it
out
there,
if
not
I'm,
sure
it'll
be
available
and
uninstallable
version
soon.
A
Okay,
we
have
two
additional
discussion
items.
One
was
about
deaf
meetings
over
the
holidays,
which
I
think
we
decided
we'll
meet
next
week,
but
not
the
week
after
and
perhaps
next
week.
We
can
make
a
decision
about
the
week
after
that.
A
D
I
have
asked
about
tutorials
admission
because
my
team
wants
to
put
that
in,
but
I
haven't
heard
anything
about
even
opening
for
submission
for
proposals
for
tutorials,
so
yeah.
Currently
the
date,
the
deadline
is
December
15th.
It
may
be
extended,
but
don't
quote
me
on
that.
D
Okay,
yeah
tutorial
submission
is
not
opened
yet
the
last
I
saw
is
that
we
want
to
get
it
available
sometime
in
December,
but
we're
running
out
of
time
in
December.
G
C
So
if
you
submit
so,
if,
if
you
want
to
put
in
a
talk,
submit
it
before
the
deadline
tomorrow
and
if
that
deadline
is
extended,
which
who
knows
might
be,
you
have
the
chance
to
update
your
talk,
you
know
but
get
it
in
by
tomorrow.
You
know
the
current
deadline
and
if
it
happens
to
be
extended,
you
can
like
continue
workshopping
the
description
and
stuff
like
that.
That's.