►
From YouTube: Jupyter Community Call - February 28, 2023
Description
Recording from the Jupyter Community Call in February 2023.
The notes from this call can be found here: https://github.com/jupyter/jupyter/issues/691
Read more about these calls on Discourse: https://discourse.jupyter.org/t/jupyter-community-calls/668
A
Cool,
yes,
wonderful,
hello,
hello,
everyone
and
welcome
to
the
February
2023
Jupiter
Community,
call
that
one
that
month
went
really
fast
for
me.
So
I
keep
having
to
remind
myself.
We
are
at
the
end
of
February,
but
before
we
get
started,
I
have
to
do
my
usual
announcements,
so
one
yes,
this
call
is
recorded,
told
you
a
moment
ago,
but
still
the
notes
will
also
be
recorded.
A
It's
posted
publicly
in
a
YouTube
playlist
after
we
right
as
all
Jupiter
Community
engagements
we
are
held
to
the
code
of
conduct,
Jupiter
code
of
conduct
can
be
found
at
any
time
at
jupiter.org
conduct.
That
applies
to
everyone
here,
which
includes
me
in
case.
That's
ever
needed.
And
third,
let
me
know
if
I
pronounce
your
name
wrong,
I'm
trying
to
work
on
my
omnipotent
naming,
you
know
name
pronunciation
Powers,
but
they're
not
there.
A
Yet
so
I
want
to
show
as
much
respect
as
I
can
in
the
meantime,
but
yeah
I
think
that's
my
main
Spiel
for
people
who
may
have
been
here
before
may
not
what
we're
going
to
do
is
follow
this
agenda.
I'm
gonna
link
it
one
more
time.
Sorry,
you'll
probably
see
me
link
that
again
always
reminds
me,
so
basically,
people
have
signed
up
on
here
ahead
of
time,
we're
going
to
kind
of
go
down
the
list,
starting
with
the
short
reports,
the
things
without
that
don't
need
further
discussion
to
longer
discussions.
A
Sometimes
those
include
demos.
Sometimes
those
are
questions
for
the
community,
but
that's
what's
going
to
happen,
so
let
me
know
if
you
have
any
questions
in
the
meantime,
though,
but
that's
my
pods
without
further
Ado
I
can
get
started
with
the
short
reports,
though
I
have
all
the
things
on
this
I
will
be
quiet
for
a
few
moments
in
case
anyone
is
inspired
to
give
us
a
little.
This
thing
you
know,
got
released
this
week.
This
thing
changed
so
yes,
silence
for
me.
A
Okay,
neat
well,
I
have
two
little
things
for
you.
First
I
do
want
to
thank
the
security
project
once
again
for
helping
us
coordinate
with
the
calendar.
We've
had
kind
of
a
back
and
forth
in
the
last
year
trying
to
coordinate
this
is
kind
of
a
popular
time
slot
for
Jupiter
meetings,
because
it
overlaps
with
a
lot
of
time
zones
for
people,
so
super
appreciate
them
being
flexible
so
that
we
could
keep
things
both
on
the
calendar
and
get
our
alternating
weeks
right.
A
So
thank
you
so
much
special
thanks
to
Roland
too
for
coordinating
that
communication
and
yes,
no
collisions
anymore.
Thank
you
for
putting
that
on
the
notes.
I
also
wanted
to
give
a
quick
governance
update.
I
am
you
know,
maybe
not
the
most
knowledgeable
about
everything,
but
I
wanted
to.
Let
people
know
the
as
we're
ramping
up
things.
I
feel
like
it's
been
hard
to
communicate.
Sometimes
this
software
steering
Council
has
met
we're
trying
to
get
regular
meetings
both
for
ourselves
and
for
open
Office
hours
on
the
Jupiter
community
calendar.
A
Just
so
you
know
that
is
a
work
in
progress.
Thanks
for
your
patience,
I
am
doing
that
too.
So,
thanks
for
your
patience
with
me,
specifically
as
I'm
running
around
scheduling,
different
meetings,
so
I
hope
next
time.
Well,
next
time
we
meet
I
should
be
able
to
point
to
that
on
the
calendar.
But
yes,
any
other
governance
questions.
What
are
you
talking
about?
Isabella.
B
A
Nice,
nice,
then
we
will
be
going
to
agenda
items
if
that
is
okay
right
now
we
have
one
on
the
agenda,
but
there's
certainly
a
lot
of
discussion
that
can
happen
there.
Of
course,
if
people
think
of
other
things,
they'd
like
to
discuss,
feel
free
to
add
it,
lower
I'll
keep
checking
the
agenda,
but
without
further
Ado
Rowan.
Take
it
away.
C
C
But
the
the
big
things
that
you
can
do
with
mist
is
that
that
you
can't
really
do
in
Jupiter
book
is
really
support
scientific
documents
and
Publications,
and
so
you
can
create
interactive
like
scientific
documents
with
cross
references
and
really
nice
figures,
and
things
like
that,
as
well
as
export
out
to
a
lot
of
different
PDF
formats,
and
so
from
this.
You
can
get
to
sort
of
high
quality
PDF
documents
quite
easily,
and
these
can
include
Jupiter
outputs
as
well
rendered
static
versions
of
Jupiter
outputs.
C
B
C
And
so
I
want
to
just
quickly
show
you
what
that
sort
of
looks
like
inside
of
Jupiter
lab
now.
So
this
is
Jupiter
lab
with
the
Mist
extension
installed
and
one
of
the
the
big
things
that
can
come
in
with
that
is
adding
metadata
like
Rich
metadata
as
data
to
the
top
of
notebooks,
and
so
this
is
coming
in
as
a
front
matter.
C
Yaml
block
right
now
and
then
you
can
execute
that,
as
you
would
any
other
Jupiter
cell,
and
then
it
gives
you
a
nice
looking
thing
with
like,
like
your
license
information,
your
GitHub
links,
things
like
your
email
and
Orchid
ID.
If
you're
into
that
affiliations,
some
ability
to
add
extra
information
at
the
top
of
your
title
block
as
well,
and
so
this
is
typically
what
a
lot
of
authors
who
are
writing
tutorials,
do
with
custom
HTML
and
the
challenge
with
that.
C
If
folks
are
that
know
some
missed
markdown,
this
is
an
admonition
in
in
Sphinx
terminology,
and
so
that
allows
you
to
create
these
callouts
as
well
as
you
can
start
to
add
class
information
to
this
like
drop
down,
and
so
this
this
is
really
bringing
that
the
sort
of
rendering
capabilities
that
authors
are
looking
for
in
Jupiter
book,
for
example,
into
the
notebook
experience.
We
can
also
have
things
like
cross
references.
A
C
C
Awesome,
the
other
piece
that
we're
working
on
is
bringing
inline
execution
into
these
markdown
cells,
and
so
that
allows
us
this.
The
syntax
here
is
subject
to
change,
but
one
of
the
extensible
parts
of
missed
markdown
is
having
these
roles
and
directives
and
roles
are
an
inline
extension
point,
and
so
this
is
the
the
role
syntax.
C
We
might
change
this
again
in
the
future,
but
this
allows
you
to
access
the
python
kernel
and
execute
different
pieces
and
then
in
like
embed
these
in
line,
and
that
is
pretty
cool
when
you're
starting
to
do
things
like
showing
rays
and
having
narrative
around
around
your
your
text.
So
you
can
do
things
like
evaluate
the
sum
inline
have
the
Max
and
just
like.
Have
these
user
Expressions
be
directly
embedded
in
the
text
that
you're
writing,
and
that
also
happens
with
widgets?
A
A
Okay,
yeah
no
I've
been
seeing
missed
around
for
a
little
while,
as
I've
been
here,
but
I
haven't
actually
seen
I
think
a
full
demo
on
it
before.
So.
Thank
you
for
doing
that.
I'm
super
glad
we'll
have
this
recorded
as
well,
because
it'd
be
a
great
reference
for
me
to
show
people
and
they
have
questions.
A
If
it's
not
too
much
for
me
to
ask
or
too
much
like
oh
I
can't
tell
that
when,
because
I
know
you
mentioned
you're
at
the
notebook
format,
Workshop
that
is
happening
right
now.
Would
you
mind
talking
like
I'm,
assuming
Mist
has
some
overlap
with
your
interests
of
why
you're
there
is
there
any
kind
of
thing
that
you're
thinking
about
it
connected
with
the
notebook
more
than
as
an
extension,
as
you
showed
here.
C
I
think
that
the
types
of
pieces
that
we're
bringing
to
that
discussion
are
sort
of
the
challenges
that
we've
come
across
in
building
this
extension
and
things
like
these
inline
executions
or
sort
of
mixing
the
concept
between
what
is
a
code
cell
that
can
be
executed.
And
then
what
is
a
markdown
that
isn't
is,
is
sort
of
generally
thought
of
just
rendered
and
now
we're
starting
to
mix
execution
into
there.
And
there
aren't
good
places
to
store,
for
example,
this
widget
metadata
or
the
outputs
Associated.
C
And
so
those
are
the
types
of
things
that
are
being
talked
about
and
other
examples
of
that
are
things
like
SQL
cells,
so
different
types
of
inputs
that
have
different
outputs
being
stored
and
so
I
think.
There's
a
general
feeling,
at
least
in
the
workshop,
that
there's
an
expansion
of
the
input,
types
and
better
structures
around
storing
and
dealing
with
those
that
can
accommodate
use
cases
like
mist
or
like
adding
SQL
cells
and
there's
a
number
of
other
examples
there
as
well.
B
A
C
No
I'm
I'm
super
excited
about
this
for
well,
especially
in
like
educational
tutorial
publishing
in
bringing
this
in
scientific
publishing
as
well.
That's
my
day,
job
is
working
with
Publishers
and
societies
who
are
trying
to
Grapple
with
like
how
to
bring
computation,
computational
thinking
into
their
publishing,
workflows
and
especially
thinking
about
the
notebook
format
and
how
you
can
serialize
and
archive
that
appropriately
over
time.
B
D
I
have
a
question:
how
much
of
how
much
of
the
I
don't
know
too
much
about
about
the
back
end
or
actually
I,
don't
know
too
much
about
missed
itself,
but
my
the
question
I've
got
here
is,
if
I
were
to
take,
say
The
Notebook,
that
you've
got
here
and
process
it
into
a
static
HTML
document.
How
much
of
the
content
that
I
see
here
would
would
come
through?
D
D
B
A
A
C
A
Oh,
that's
super
sorry,
I
know,
I
could
dig
into
this
longer.
I'm
gonna
double
check
the
agenda,
real,
quick,
but
I,
don't
think
anything
has
been
added
yet
wow.
Thank
you.
I
think
this
was
Roland.
Taking
all
these
notes.
This
is
awesome.
These
are
probably
the
most
in-depth
Community
call
notes
we've
had
in
a
while.
Thank
you.
A
This
is
a
very
typical
me
question
to
ask
and
I
know.
Sometimes
it
catches
people
off
guard,
but
something
that
I've
wondered.
You
know,
since
particularly
right,
markdown
and
rst,
which
missed
kind
of
is
bringing
them
together
both
have
to
my
knowledge,
fairly
typical,
HTML
outputs,
which
makes
them
a
little
more
accessible.
I,
don't
know
what
happens
when
you
start
mixing
things
with
mist.
I,
don't
know
how
it
reconciles
those
outputs
and
some
of
those
cool
interactivity
things
I
would
bet.
C
B
C
B
A
C
And
so
that's
I
I
think
that's,
there's
I
think
efforts
going
on
in
the
Jupiter
ecosystem,
we're
using
the
same
technology
pieces
as
Jupiter,
and
so
as
Jupiter
improves
accessibility
around
the
widgets
space.
Those
improvements
will
flow
through
here
as
well,
and
so
it's
it's
certainly
on
like
a
lot
of
the
things
that
we
have
top
of
Mind
are
things
like
archive
ability,
structured
data
formats
having
semantic
HTML
outputs
and
paying
attention
to
the
accessibility
scores
as
much
as
we
can
yeah.
A
No,
that
makes
total
sense.
Yeah
that's
good
to
hear,
though,
what
people
are
thinking
and
good
to
hear
that
it
might
be
caught
Upstream,
it's
making
me
yeah.
The
the
this
discussion
is
making
me
think
about
a
previous
job.
That
I
was
not
focused
on
scientific
Publications
exclusively,
but
yeah.
It's
really
interesting
to
see
all
this
come
up
again,
so
awesome
cool,
I
am
being
quiet
again
for
a
moment.
People
are
excited.
I
thought
this
is
a
really
cool
demo,
but
admittedly
I'm
pretty
excitable.
That's
part
of
why
I
run
these
things.
C
That's
it's
super
fun.
We
we
sort
of
launched
the
project
officially
a
week
and
a
half
ago,
and
it's
been
a
ton
of
fun.
Having
folks
come
in
and
find
out
about
it
and
just
get
sort
of
excited
about
the
I
think
the
vision
of
well
trying
to
burn
scientific
publishing
a
step
closer
into
the
the
future
of
computation
and
interactivity
and
reproducibility
and
sort
of
mixing
a
lot
of
these
things
together
and
I.
I,
certainly
think
the
the
Community
Focus
of
Jupiter
is
a
good
place
to
incubate.
A
Yeah,
no,
it's
awesome
to
see
like
I,
remember
a
lot
of
the
things
that
you're
you're
trying
to
tackle
being
like
either
pain,
points
or
like
kind
of
desired
use
cases.
So
it's
pretty
awesome
to
see
them
I'm
glad
you're
getting
that
feedback
from
other
people,
though
too
yeah
cool.
Well,
we
are
roughly
halfway
through
this
call
and
I.
A
A
Well,
I,
perhaps
this
is
I,
don't
know,
I,
don't
know.
Someone
will
think
this
is
the
best
idea,
but
I
have
been
thinking
about
the
notebook
format,
Workshop
going
on
right,
clearly,
I'm,
not
there
for
various
reasons,
but
I
don't
know
if
that
peaked
anyone's
else's
interest.
The
Notebook
really
is
at
the
foundation
of
I,
wouldn't
say
all,
but
definitely
most
I.
Think
of
Jupiter
work,
particularly.
You
know.
A
No
just
me,
then:
okay,
I
can
talk
a
little
more,
but
maybe
I
will
let
you
free
today,
I
don't
want
to
torture
you
all
here,
yeah
I,
have
been
really
curious
right.
One
of
the
big
things
that
I'm
I'm,
hoping
is
a
discussion
here
I
believe
it
came
up-
was
that
we
don't
have
a
type
of
markdown
right
that
we
specify
with
the
notebook
despite
having
these
markdown
cells.
In
some
ways,
this
is
really
good.
A
As
someone
who
works
a
lot
on
accessibility
that
has
created
some
different
problems
for
us
when
we
do
user
testing
in
different
ways,
because
sometimes
we
don't
know
what
we're
going
to
get
people
get
different
kind
of
experiences
and
outputs.
So
that's
something
that
I
am
really
interested
in
seeing
what
comes
from
it
also
a
little
afraid,
sometimes
to
be
honest,
because
I'm
not
sure
you
know
how
that
decision
will
Ripple,
but
that
that's
something
I'm
curious
to
see
what
comes
from
this
that
helps
inspire
people
further.
B
A
No,
that's
part
of
the
problem.
I
haven't
had
a
chance
to
dive
specifically
into
that.
Sometimes
that's
what
happens
because
I
have
all
the
different
projects
and
I
try
and
like
take
the
learnings
from
a
lot
of
the
different
projects.
I
work
on
and
bring
them
to
people,
but
I,
don't
necessarily
get
to
work
on
all
the
solutions
and
problems.
I
see
come
up
because
it's
not
the
like
dedicated
point
of
it
so
I.
A
My
very
tentative
answer
without
a
heavy
technical
background
would
be
just
having
like
knowing
what
markdown
specification.
We're
following
at
all
would
be
would
be
really
helpful
just
because
right,
then
we
have
a
specification
for
that,
because
that
I
think
in
all
spaces,
but
definitely
with
accessibility
thoughts.
It's
really
really
helpful
like
having
those
kind
of
rules,
because
we
know
then
we
can
map
them
on
to
whatever
relevant
things
or
you
know
like
find
other.
B
A
A
I
would
not
say
that
all
the
things
it's
not
always
clear
how
they
correlate
to
some
of
our
use
cases,
because
sometimes
right
kind
of
like
we
were
talking
about
with
Miss
we're
using
things,
maybe
in
ways
that
people
don't
expect
or
we're
kind
of
pushing
them
to
some
limit
that
really.
These
aren't
designed
for
there's
a
lot
of
different
ways,
but
so
trying
to
map
those
one
to
one
and
having
like
knowing
which
markdown
specification.
A
At
least
then
we
know
what
the
specification
is:
we're
kind
of
trying
to
map
places,
whereas
something
I've
had
right
now
and
part
of
the
reason
we
have
done.
Testing
on
kind
of
different
notebook
like
ways
to
interact
I,
don't
want
to
say
exclusively
interfaces,
because
some
of
them
are
like
and
be
converted
to
HTML,
which
is
not
right,
quite
an
interface
anymore,
but
still
like
the
output
we
get
from.
That
is
one
type
of
thing,
but
sometimes
the
way
that
gets
rendered
elsewhere
is
different
and
it'd
be
nice.
A
If
we
could
tell
people
like
no
we're
able
to
fix
that-
and
we
know
it's
going
to
fix
everywhere
or
we
know
what
kind
of
HTML
it's
always
going
to
give
us,
no
matter
where
you
run
it
if
that
kind
of
makes
sense,
because
a
lot
of
the
way
that
a
lot
of
the
accommodations
kind
of
get
hooked
in
at
the
HTML
level.
So
that's
my
limited
yeah
sorry
I
wish
I
had
an
easier
answer
for
you
dangerous
to
ask
me
questions.
C
I
think
at
the
so
at
the
notebook
format,
they
have
they're
sort
of
split
into
three
groups
at
the
stage,
and
so
one
they're
talking
about
a
text
based
format,
I
think
that's.
In
addition
to
sort
of
the
standard
format
but
sort
of
like
either
pointing
like
the
GP
text,
way
of
working
and
sort
of
improving
some
of
the
rough
edges
around
that
from
an
integration
perspective,
there's
a
cell
types
workflow,
which
I
think
is
actually
getting
exactly
to
what
you're
talking
about
about
specifying
the
input
type.
B
C
B
A
A
Yeah
I'm,
assuming
I,
have
the
maybe
I
shouldn't
ask
I'm,
also
curious
to
see
what
comes
with
some
of
the
metadata
conversations,
because
I
know
we
have
that
open
right
now,
I
don't
know
if
anybody
else
has
concerns
for
that
too.
I
know
people
use
so
metadata
for
a
lot,
a
lot
of
different
things
and,
from
my
understanding,
it's
kind
of
an
open
box
right
now,
where
people
put
whatever
they
want,
which
you
know
pros
and
cons
to
that
for
sure.
I
already
met
the
archive
ability
earlier.
That
makes
the
old
archivist
and
me.
B
A
A
E
A
E
C
I
there
is
a
discourse
Community
that
is
going
on
right
now
and
I
could
try
and
find
the
link
to
that
yeah
I,
don't
I
think
most
of
what
they're
doing
right
now
is
sort
of
like
in
in
person
or
in
Workshop
documents
at
the
moment,
but
I'm
sure.
All
of
that
will
become
like
more
widely
available
for
comments
and
and
that
as
their
wrap
up
the
workshop,
I
I,
don't
know.
I
I,
don't
actually
know
the
worst
jobs
going
on
I
just
sat
in
on
an
hour
or
two
this
morning.
A
It's
just
totally
open
and
like
should
there
be
so
I'm,
not
I'm,
not
singularly
aware
I
just
had
suspected
from
their
conversations
that
it
might
come
up,
but
I
can
look
around
for
you.
There
might
be
discourse
might
be
the
right
and
yeah
yeah.
But
I
can
look.
Sorry
I,
don't
have
an
easy
answer
for
you
with.
D
I
think
I'll
share
that
our
use
of
cell
metadata
is
basically
for
for
marking
cells
for
specific
treatment
when
we're
rendering,
either
as
a
notebook
or
a
static
HTML,
or
to
provide
a
way
a
easy
way
to
introspect.
What's
going
on
in
the
cell
and
pick
out
a
piece
of
it
and
send
it
somewhere.
So
we
we
do
a
lot
of
notebook,
prototyping
and
then
creating
a
report
from
it
and
then
chroning
those,
and
sometimes
people,
though,
don't
want
to
go.
Look
at
the
report.
They'll
want
just.
Can
you
post
the?
D
Can
you
post
the
plot
from
that
notebook
into
slack
and
so
having
an
easy
way
to
just
pick
out
the
right
cell
and
get
the
thing
you
need
and
then
send
it
over
to
slack
and
so,
but
basically
that
the
metadata,
the
tag
is
basically
just
set
when
you,
author,
The
Notebook,
there's
no,
no
more
sophisticated
manipulation
of
the
metadata
programmatically
or
anything
like
that.
So
kind
of
a
really
kind
of
very
simple
kind
of
exploitation
of
the
capability.
A
Cool
well,
you've.
You've
all
entertained
me
in
a
longer
discussion
than
probably
any
of
you
were
planning
for
today.
Apologies
for
anyone
who
was
like
oh
I'm,
just
going
to
be
quiet
today.
I
super
appreciate
it,
though
getting
good
info
here
and
I
like
to
hear
what
everyone's
thinking
this
is.
One
of
my
main
touch
points
for
that.
So
I
will
check
the
agenda
one
more
time,
but
I
think
we
just
have
awesome
notes.
Cool
yeah
with
that.
A
Maybe
I
would
like
to
be
free
early
today
reminder
that
the
next
Community
call
will
be
end
of
March
at
the
moment.
I
believe
it's
at
the
same
time
because
of
the
security
groups
or
projects.
So
thank
you
so
much
for
that
and
yeah
I
will
be
updating
posts
with
that
this
will
be
posted
publicly,
but
until
then
I
hope
you
have
a
wonderful
month.
I
will
stop
recording
thank.