►
From YouTube: Jupyter Community Call - October 26, 2021
Description
Recording from the Jupyter Community Call in October 2021. (Costumes optional, but welcome!)
The notes from this call can be found here: https://jupyter.readthedocs.io/en/latest/community/community-call-notes/2021-october.html
Read more about these calls on Discourse: https://discourse.jupyter.org/t/jupyter-community-calls/668
A
We
go.
We
need
to
change
this
to
speaker
view
for
recording
hello,
hello,
everyone
it's
time
we're
here
for
the
october,
2021
jupiter
community
call
costumes
optional,
but
we
do
have
some
lovely
costume
attendees.
You
know
I'm
gonna
take
off
these
glasses
before
I
lose
my
mind,
but
I
do
have
a
few
things.
I
want
to
remind
you
before
the
call
begins
and
the
first
being
right
that
this
call
is
recorded.
A
You
just
heard
it
say
that,
but
I
always
say
it
for
posterity
and
also
that,
because
this
is
a
jupiter
event,
jupiter
community
event,
we
are
held
to
the
code
of
conduct.
That
includes
me,
so
please
don't
hesitate.
You
can
review
that
anytime
at
jupiter.org
conduct
yeah
and
with
that
we're
going
to
get
started.
A
If
you
haven't
been
here
before
we
kind
of
this
is
just
a
show
and
tell
people
have
signed
up
ahead
of
time
on
things
that
they
want
to
share
and
we're
going
to
go
through
that
I'm
going
to
watch
time
to
make
sure
that
we
get
to
everyone,
but
basically
we're
just
going
to
be
discussing
and
getting
excited
for.
You
know
what
are
people
doing.
A
That's
amazing
with
all
the
hard
work
it
takes
to
keep
these
projects
running
so
with
that
I'm
gonna
actually
link
the
agenda
one
more
time
in
case
anyone
came
in
and
I
didn't
notice
it
that'll
be
in
the
chat,
and
here
we
go.
Oh
please
sign
in
if
you
feel
so
inclined,
that'd,
be
it's
cool
to
see
who's
here.
A
B
C
A
Yes-
and
I
just
shared
the
link
in
the
chat
for
anyone
who
doesn't
know-
this
is
an
issue
discussing
that
classic
notebooks
in
future,
as
it
has
been
in
maintenance
mode
for
a
long
time,
but
I
know
that
the
maintenance
team
has
some
thoughts
on
that.
So
I
won't
paraphrase
the
issue,
I'm
not
up
to
date
on
it,
but
yeah
that'd
be
awesome.
Thank
you
for
calling
that
out
carol.
It
was
really
great
of
him
to
open
it.
A
A
Okay,
then,
we
can
always
come
back
to
that.
If
somebody
wants
to
add
something,
our
agenda
is
really
open
today.
So
if
you
want
to
come
back
to
something
some
kind
of
announcement,
you
remember
later
or
larger
share
feel
free
to
just
throw
it
in
the
agenda
and
we
will
loop
back
to
it,
but
I
mean
oh
yeah
go
ahead.
Sorry.
E
A
E
Interrupt
you.
I
was
just
looking
on
the
list
of
who's
here
and
I
don't
believe
he's
here
yet
so
he
didn't
put
his
name
on
the
agenda,
but
I
believe
fernando
would
like
to
make
a
short
announcement
today
about
what
the
current
state
of
governance
conversation
is,
and
I
have
said
this
now
in
order
to
leave
you
all
disappointed
if
you
can't
make
it,
but
it
just
occurred
to
me
that
he
didn't
put
an
agenda
item.
He
just
put
his
name
on
the
list,
so
forget
I'd,
say
so.
A
Awesome
I
saw
that
too.
I
was
wondering
because
he
did
have
his
name
on
it
briefly,
but
then
it
was
removed.
So
I
don't
know
I
look
at
this
document
a
few
times
a
month
when
I
forget
what's
happening
so
in
that
case,
though,
if
we're
waiting
for
that
share,
I
think
we
actually
have
an
open
agenda
right
now,
I'm
right!
Okay!
Does
anyone
have
anything
that
they'd
like
to
start?
The
discussion
off
with
the
floor
is
open.
A
A
We
can
go
back
to.
I
don't
want
to
call
anyone
specific
out,
even
though
I
know
some
of
you
have
cool
things
going
on
in
the
background.
So
I'm
not
going
to
do
that.
Would
we
like
to
do
a
favorite
notebook
discussion?
We've
done
that
in
the
past
people
share
a
favorite
notebook
that
they
have
that
they
wrote
that
someone
else
wrote
and
talk
about
why
they
think
it's
cool.
B
I
was
going
to
maybe
ask
rollin
or
others
who
might
be
part
of
that
security
meeting
and
just
do
a
quick
update
like
why
it
exists
and
and
what
gets
done
in
it.
G
Sure
I'd
be
happy
to
I.
When
I
come
to
this
meeting,
I
usually
have
an
update
but
from,
but
I
don't
have
one
this
week,
but
just
to
remind
everybody.
The
the
security
meeting
is
the
bi-weekly
meeting
that
happens
on
fridays.
9
a.m.
Pacific
time
myself
and
rick
wagner
from
ucsd
convened
that
meeting
the
minutes
of
that
meeting
go
into
a
jupiter
security
repo,
and
so
you
can
read
what
we've
discussed
there
in
those
notes
on
it's.
G
The
repo
is
jupiter
security
on
github
and
mainly
the
the
purpose
of
that
meeting
is
to
discuss
general
topics
relating
to
security,
not
specific
vulnerabilities
or
anything
of
the
day,
but
basically
discussing
best
practices,
how
the
project
actually
communicates
about
security
within
the
project
and
to
the
external
stakeholders
and
other
other
people
who
are
users
and
trying
to
organize
the
security
effort
kind
of
into
into
kind
of
something
kind
of
coherent.
G
So
there's
currently
work
going
on
to
understand
all
of
the
security
documentation
across
all
of
the
jupiter
projects,
we're
doing
that
with
trusted
ci
and
they're
working
to
kind
of
put
together
a
kind
of
outline
of
all
that
security
documentation
and
make
recommendations
about
how
we
can
improve
it.
So
that's
that's
where
that
sub
project
came
up.
G
We
originally
were
just
trying
to
put
together
plans
for
a
workshop,
but
we
kind
of
got
drafted
into
convening
that
meeting
and
and
trying
to
keep
that
conversation
going,
but
we
want
to
thank
everybody,
who's,
doing
the
real
work
of
of
addressing
vulnerabilities
and
problems,
and
we
what
we,
what
we're
trying
to
do
right
now
is
trying
to
get
a
handle
on
what
the
actual
procedures
are,
that
people
are
following
and
then
trying
to
turn
those
into
actual
policy,
actual
practices
that
people
need
to
follow
when
they're
addressing
vulnerabilities
and
then
announcing
them
and
handling
them,
and
things
like
that,
so
so
that's
kind
of
a
general
overview.
B
Roland
you
and
the
super
computer
folks
over
at
ucsd
are
well
positioned
to
help
us
guide
and
navigate
through
all
of
this.
So
I'm
really
glad
you're
helping
with
the
process
and
helping
others
find
their
process.
H
E
Do
you
have
plans
for
the
security
working
group
being
the
people
who
publish
patches,
or
do
you
want
it
to
remain
the
case
that
the
individual
projects
still
do
those
patch
publications,
as
releases
like,
what's
what's
a
way
to
make
sure
that
security
patches
come
out
and
they
come
out
across
all
the
projects
and
they
come
out
basically
at
the
fastest
rate
that
we
can
sustain.
In
your
mind,.
G
Well,
there's,
I
don't
know
the
answer
to
that.
Yet
it
does
seem
like
individual
sub
projects
kind
of
handle
their
own
vulnerabilities,
but
there
is
a
there
is
a
coordination
layer
and
it's
probably
important
that
there
be
a
coordination
layer
in
the
project.
G
So
there
are
some
things
out
there
where
it
maybe
makes
sense
to
have
conversations
about.
Security
like
numpy
is
probably
not
like
a
really
high
priority
security,
wise
compared
to
say,
jupiter
or
desk,
or
something
like
that.
So
there
is
a
sense
that
there
needs
to
be
a
set
of
practices
within
the
project
and
maybe
beyond,
and
coordination
across
projects
and
some
projects.
G
But
you
know
I
I
think
we
haven't
quite
figured
out
what
that's
going
to
look
like
yet,
but
we
would
encourage
people
who
are
interested
in
the
topic
to
try
to
make
the
meeting.
I
think
I've
I've
mentioned
that
it's
on
fridays
and
every
other
friday
at
9
pacific
it's
on
the
community
calendar,
so
you
can
find
it
that
way.
G
If
we
find
that
we
need
to
move
that
meeting
so
that
more
people
can
join,
we
can
we
can
do
that
as
well.
But
it's
very
much
a
conversation
and
we
are,
you
know,
kind
of
I'd,
say
we're
kind
of
newcomers
to
this
kind
of
governance
process
and
so
we're
still
trying
to
kind
of
pick
up.
What's
actually
going
on
so
the
more
people
who
can
describe
what
they're
doing.
A
A
So
maybe
it
wouldn't
make
sense
to
go
around
say
what
projects
are
different
people
working
on
some
of
you.
I
have
very
much
run
into
in
jupiter
spaces
and
some
of
you
less
so
is
there
anyone
who's
really
excited
about
a
project
they're
working
on
or
just
wants
to
say.
I
can
also
start
if
you
haven't
run
into
me
yet.
A
A
C
Good-Looking
project
there
yeah
and
it
might
be
cool
to
hear
where
executable
books
is
going
because
that's
a
big
project
around
our
world
too.
B
H
The
one
of
the
maintainers
of
executive
books
indeed
and
the
jupiter
book
yeah
so
we're
just
carrying
on
so
actually
we
are
looking
into
becoming
a
jupiter
subproject
kind
of
by
next
september.
Essentially,
we
were
funded
by
sloane,
graham
for
two
years,
mainly
funding
me
to
mess
around
with
stuff,
and
that
comes
to
an
end
in
september
next
september.
H
So
chris
holgroff,
the
other
main
person
on
the
project,
started
to
think
about
how
how
we
move
on
from
that
moving
transition.
So
yeah,
one
of
the
thoughts
is
to
move
to
due
to
sub
projects.
Obviously
we're
keen
looking
at
all
the
governance
things
that
you
guys
are
doing
and
seeing
how
we
can
fit
into
that
yeah.
That's
the
main
kind
of
thrust.
At
the
moment
there
was
obviously
last
last
month
there
was
the
discussion
about
the
variables
in
notebooks
kind
of
keen
to
push
that
one.
H
At
some
point,
I
think
it's
gone
a
little
bit
stale
over
the
last
month,
so
I'm
interested
to
start
talking
about
how
to
yeah
it's
interesting.
I
don't
know
how
other
people
have
found
some
of
the
discourse.
I
think
this
isn't
specific
to
jupiter.
Really
but
I
find
some
of
the
discourse
discussions
they
go,
they
get
very
big
and
very
complex
and
then
they
kind
of
get
dropped
because
they
get
too
over
complex
for
people
to
follow.
H
Oh
yes,
yeah,
yeah,
yeah,
sorry,
I
should
so
what
I
I'll
share
with
you
the
website,
so
the
focus
of
the
executed
books
is
essentially
turning
a
set
of
jupiter
notebooks
into
some
form
of
book,
primarily
whether
it
be
like
an
online
website
or
a
pdf.
H
So
there's
a
nice
gallery
here
and
if
anyone
wants
to
submit
their
own
we've
been
gathering
kind
of
books
that
people
have
been
making
and
so
then
the
idea
is
it.
It
runs
via
sphinx,
which
I'm
sure
a
lot
of
you
know
executes
the
notebooks,
turns
them
into
nice,
html
pages
and
static
website.
H
So
that's
really
the
key
thrust
of
it
as
you,
you
can
see
from
the
gallery.
There's
a
lot
lots
of
like
tutorial
based
things
and
we're
trying
to
push.
You
know
people
just.
C
H
Their
notebooks
out
there
and
we're
working
a
lot
recently
on
kind
of
interactive
approaches
to
these
notebooks
via
there's
a
the
phoebe
project,
and
you
can
launch
you
know
binder
binder
hubs
directly
from
the
from
your
websites
and
things
like
that.
B
We
were
having
assignments
at
chris
in
the
chat
about
missed
parser
and,
if
folks
aren't
aware
of
it,
it's
probably
one
of
the
best
things
that
I've
seen
in
a
long
time
when
it
comes
to
allowing
folks
to
use
restructured
text
and
markdown
in
documentation.
So
maybe
you
want
to
just
give
folks
a
short
snippet
of
what
that
is.
H
Yeah
so
essentially
also
with
with
syncs
before
so.
It's
been
largely
based
on
restructured
text
and,
obviously
in
the
world
of
tubes
and
notebooks,
and
a
lot
of
things
github
and
everything.
It's
a
it's
a
markdown
world.
Basically
the
markdown's
been
getting
better.
We've
got
common
mark
now,
there's
a
kind
of
a
standard
towards
it,
but
at
the
same
time,
it's
kind
of.
If
you
want
to
do
any
kind
of
scientific
publishing,
it's
largely
underpowered.
H
On
the
other
hand,
you
have
restructured
text
which
has
a
lot
of
power,
but
can't
really
be
used
in
notebooks
and
kind
of
general
users,
sometimes
find
it
a
bit
confusing
and
something
they're
not
used
to.
So
the
idea
of
missed
markdown
is
to
bring
mark
down
towards
restructured
text,
giving
you
the
ability
just
to
write
normal
markdown,
but
then
also
adding
in
these
concepts
like
directives
and
roles
to
be
able
to
yeah
have
the
full
power
essentially
of
what
you
can
do
and
restructure
texts,
but
based
on
mark.
C
I
H
Bit
of
her,
so
I
yeah,
if
there's
a
lot
of
interest
in
it,
I'm
happy
to
do
it.
I
mean
yeah,
there's
a
bit
of
a
pain
with
yeah
trying
to
get
sphinx
and
auto
dogs
to
work
with
there,
but
what's
really
nice
also
how
I've
implemented
mister
is
that
I
we've
made
this
I've
made
this
mark
down.
It
python
passes
so
markdown.
It
is
a
big
javascript
library
for
markdown
passing
it's
used
in
fierce
code
and
things
hopefully
soon
in
dupes
and
notebooks.
H
At
the
moment
that
uses
a
different
password,
but
it's
not
the
same
thing,
but
what
it
is.
It
has
very
powerful
mechanism
that
you
can
add
on
extensions,
and
this
is
how
we've
added
in
all
these
extra
feet
and
with
that.
Basically,
it
makes
it
very
easy
to
add
in
the
extra
things
needed
for
these
for
the
dog
strings.
So
I
didn't
vision
being
very
much
like
your
standard
sync
stock
strings
with
like
the
fields
and
parameters
so
yeah.
H
I
was
going
to
implement
that
and
then
work
out
how
to
do
yeah,
the
ap,
the
autodrive
stuff,
but
it's
on
the
cards
very
cool.
J
B
Like
auto,
api
takes
a
different
approach
than
auto
dock
and
it
walks
the
ast
in
terms
of
how
it
gets
the
dock
strings
instead
of
having
to
import
the
libraries
themselves
that
are
being
documented,
so
I
found
you
can
get
once
you
get
the
stubs
from
that.
You
can
kind
of
you
know
if
you
ran
it
through
another
process.
Afterwards,
you
can
kind
of
clean
it
up
a
little,
but
that
was
actually
what
I
was
doing
before
I
got
on
the
call,
but
it's
also,
I
I
think
thinks
auto.
B
Api
is
a
lot
faster
than
auto
doc.
Is
you
know
different
functionality?
You
know
auto
doc's
been
around
longer,
but
you
might
want
to
check
it
out.
If
you
haven't
it's
relatively
it's
probably
like
a
year
or
so
two
years,
maybe.
H
B
And
I
think
you
know,
I
think
the
read
the
docs
fix
has
put
some
love
into
it
as
well.
So
it's
well
maintained.
C
H
Oh
yeah
they're,
great
and
also
yeah
we're
trying
to
get
you
to
book,
so
you
can
make
them
with
wreath
docs
as
well.
H
H
Yeah,
that's
the
main
thing
and
then
yeah
we're
trying
to
get
some
love
into
jupiter
lab
as
well
and
create
a
tube
to
lab
extension.
So
it's
nicer.
It's
really.
The
only
pain
with
all
of
these
extra
things
for
the
market
at
the
moment
is
obviously
when
you're
opening
the
notebook-
and
you
don't
have
anything
you
get
some.
It
doesn't
look
as
nice,
so
we'd
love
to
integrate
more
with
different
notebooks
and
have
it
so
that
you
can
open
them
up
and
they
look
just
as
almost
they
would.
C
Thanks
for
the
update
man,
sorry
we
put
you
on
like
like
last
night.
A
K
K
Yeah,
the
big
changes,
the
introduction
of
our
back
so
role
based
access
control.
K
So
anyway,
no
the
basic
idea
behind
our
back
is
that,
instead
of
saying
someone's,
either
admin
or
not
admin,
you
can
now
sort
of
create
different
roles
within
jupiter,
so
they
could
have.
And
then
that
is
you
can
give
each
role
permissions
on,
say
particular
api
course.
K
So,
for
example,
you
could
have
someone,
you
could
have
say,
maybe
a
teacher
who
has
read
only
full
read-only
access
to
say
all
student
service,
for
example,
but
not
access
to
change
anything
I've
said
link
I've
linked
in
the
changelog.
It's
there's
beat
there's
a
couple
beaters
out
already
so
feel
free
to
play
with
it.
K
It's
been
following
he's
been
following
discourse,
especially
the
gps,
lab
rtc
discussion.
This
is
this
new.
Our
back
work
actually
should
help
to
make
our
back
strong
artifact
to
make
our
jpg
lab
rtc
pos.
So
work
really
well
now,
because
without
that
you
can
basically
give
certain
other
users
access
to
your
server.
K
It's
not
just
a
freefall
anymore.
We
should,
we
actually
would
be
in
the
previous
one
yep
yep.
That's
just
explain
it
rtc
I'll
just
get
used
to
it.
The
other
things
for
you,
some
breaking
api
changes.
So
one
of
the
I
guess
one
of
the
more
notable
changes
is
in
house
of
spawners
are
launched.
K
So
originally
when
jupiter
was
written,
it
was
pretty
much
everything
was
just
running
on
the
vm
setup.
Keep
it
up
single
user,
it
spins
up
a
local
process.
It's
fine!
Since
then.
It's
expanded
quite
a
lot
so
like
containers,
obviously
a
big
thing
now
like
docker,
spawner
and
kubernetes,
and
that
so
that
actually
has
some
sort
of
very
detailed
problems
when
it
comes
to
actually
knowing
what
process
you
actually
launch.
K
In
fact,
if
you
go
again,
you've
got
to
discuss
performance
that
people
are
running
all
sorts
of
random
web
proxies,
it's
all
pretty
cool,
so
the
idea
of
some
of
these
breaking
changes
is
to
actually
make
it
a
lot
easier
to
just
run
whatever
application
you
want
and
not
have
to
worry
so
much
about
what
arguments
are
being
passed,
but
it's
a
great
change
on
the
binder
hub
side
of
things.
A
few
of
us
are
doing
some
work
on
doing
some.
K
What
we
could
bind
having
a
box
so
at
the
moment
binderhub,
which
is
what
runs
mybinder.org,
is
well
officially
only
runs
a
kubernetes,
that's
great
for
scalability,
it's
a
bit
of
a
pain.
If
you
wanted
to
run
it
locally
and
there's
a
bit
of
been
a
lot
of
chat
on
the
discord
form
you
came
up
and
how
can
we
basically
get
the
equivalent
of
bind
hub
but
running
on
vm?
K
So
we've
got
something
prototyped.
You
can
basically
now
run
binder
hub
in
docker
or
podman
if
you're,
that,
if
you're
interested,
so
it
runs
a
single
vm,
it
actually
works
surprisingly.
Well,
it's
not
officially
released
yet
because,
as
part
of
this
work,
we
decided
this
would
be
a
good
time
to
clean
up
some
of
the
internet
apis.
So
we
kind
of
want
to
do
that
before
release
it
and
then,
after
that,
we'll
officially
support
the
api
and
if
someone
else
wants
to
add
some
other
sort
of
platform,
you're
welcome.
K
C
So
I
got
a
question.
This
is
not
necessarily
related,
but
this
is
kind
of
bigger
question
jupiter
hub
binder
hub
folks,
a
couple
years
ago
there
were
people
talking
about
different
experiences
that
were
being
launched
with
these
different
hubs.
Are
there
any
people
who
are
like
focused
on
the
user
journey
user
experience?
C
C
K
I
don't
think
so.
I
mean.
K
Has
been
made
in
jupiter
is
an
attempt
to
sort
of
support
like
to
make
it
easier
to
basically
put
your
own
interface
on
top
of
it.
So
at
the
moment,
if
you
want
to
customize
your
tub,
you
have
to
get
into
january
templates.
You
have
to
set
paths
and
everything
it's
kind
of
yeah.
It
looks
a
bit
tricky
like
to
be
honest.
Even
I
don't
really
understand
it,
but
so
one
of
the
ideas
of
tutorial
is,
you
may
have
a
much
much
cleaner
separation
between
your
back
and
your
front
end.
K
C
C
I've
got
about
100
hours
in
with
rtc
with
people
on
binder
and
it's
totally
just
a
different
experience
like
it's
got
to
be
a
nice
house,
and
you
know
we're
trying
to
design
places
for
people
to
like
feel
comfortable
for
a
little
bit.
So
anybody
comes
along
those
folks,
but
I'd
love
to
organize
around
that.
K
A
C
I
don't
know-
maybe
it's
kind
of
funny,
but
it
gets
to
some
of
these
like
like.
Originally,
you
asked
if
you
want
to
have
the
notebook
conversation,
that's
a
big
one.
I'd
love
to
have
a
notebook
nostalgia.
Conversation
like
all
the
good
things
that
have
happened
because
of
notebooks
like
I
met
carol,
zack
and
isabella,
and
everybody
else
in
this
room
because
of
notebooks.
That's
a
great
thing,
but
maybe
we
can
try
that.
C
Does
that
fix
it
yep
all
right?
Let's
have
fun
with
this,
and
this
way
we'll
kill
a
little
bit
of
time.
Hopefully,
fernando
shows
up
all
right.
Here's
a
wow
okay.
So
this
notebook
is
not
mine.
This
notebook's
mine,
let's
see
all
right,
so
I
wrote
this
one
six
years
ago.
I'm
sorry!
This
is
six
years
ago.
C
So
at
the
time
I
was
working
with
anaconda
and
I
was
doing
a
lot
of
data
visualization
with
bokeh,
which
is
super
cool
because,
like
at
the
time
I
didn't
want
to
write
a
lot
of
javascript
and
bokeh
makes
the
javascript
for
me,
and
this
was
also
before
typescript
time.
This
is
when
we
had
javascript
displays
and
coffeescript
was
still
a
thing.
I
actually
think,
like
adam
existed
at
the
time,
and
people
were
still
writing
their
extensions
in
coffeescript.
C
I
still
think
coffeescripts
of
the
best
programming
languages
ever,
but
don't
anybody
jump
on
me
for
that?
So
what
will
we
do?
What
can
we
do
with
this?
At
the
end,
here
we
wind
up
with
a
plot.
This
is
a
bouquet
plot.
That's
in
the
canvas
and
what
I
used
to
do
is
I
used
to
like
basically
make
bokeh
plots
interact
with
the
javascript
in
the
notebook,
but
I
think
we've
missed
too
many
versions
at
this
point
and
some
of
the
interactions
don't
last
anymore,
but
you
know
at
this
time.
C
I
wasn't
good
at
programming
and
I
was
still
getting
my
feet
wet
with
modern
html
learning
how
to
write
javascript
learning,
how
to
write
python
learning
all
the
tools
kits
in
pi
data
so
like
the
notebook,
was
super
helpful
there
right.
So
what
we
could
do
is
this
one
here
we're
constructing
a
table
ourselves,
there's
probably
a
better
way
to
do
that
now
with
pandas.
I
wasn't
too
great
with
it
then,
but
then
we
do
this
like
super
fun
stuff.
C
C
We
also
need
to
extract
figure
data
from
our
image.
So,
every
time
we
run
this,
we
had
to
basically
import
d3.
We
also
needed
yaml,
but
just
as
easy
as
I
could
import
python
packages
at
this
time
I
could
import
the
javascript
packages
and
at
the
end,
they
let
you
do
this
bet
this
crazy
thing
where
in
javascript
there
was
a
kernel,
there's
a
ipython
object.
That
said,
ipython
notebook,
kernel
execute
and
you
can
just
run
code,
so
you
can
do
super
cool
stuff.
C
Then
we'd
also
have
to
do
a
little
bit
of
editing
of
the
style
and
put
the
html
in
here.
I
don't
even
know
what
I
was
doing
in
this
notebook,
I'm
just
going
through
it
for
the
sake
of
posterity
here,
but
then
we'd
go
and
plot
this
and
the
expectation
would
be
all
the
work
that
we
did
ahead
of
time
would
create
interactions
when
the
plot
was
moving.
I
don't
even
know
what
goes
on
further
here.
C
This
goes
and
commits
a
notebook,
and
then
we
actually
take
the
data
and
we
start
working
with
it
using
pi
query.
That's
a
jquery
layer
in
python,
and
here
we've
got
some
coffeescript
magics.
I
don't
even
know
what's
happening
at
the
end
of
this
notebook.
The
point
of
it
is,
though
I
have
this
notebook.
C
So
thank
you
to
all
to
everybody.
Who's
worked
on
notebooks
over
all
the
years.
This
is
what
got
me
to
where
I
am
today,
and
those
are
some
of
the.
I
don't
know
it's
kind
of
running
through
that
notebook,
like
I
kind
of
miss
the
experimentation
that
way,
but
at
the
same
time
too,
when
I
do
it
now,
I'm
a
lot
more
confident
that
it's
going
to
be
reusable
over
time.
So
I'm
going
to
stop
there.
D
Can
I
I
want
to
share
a
notebook.
You
inspired
me
hell
yeah.
Yes,
this
is
from
eight
years
ago
nice,
one.
D
D
This
is
my
undergraduate
thesis.
Please
don't
read
it,
but
it's
on
github
and
it's
in
notebooks
like
you
can
go.
Look
I
didn't
even
know
how
to
like
use
a
git
ignore.
There's
ipad
checkpoints
right
there
wait.
Are
you
guys
all
seeing
my
screen.
J
D
Yeah
so
like
yeah,
this
is
super
embarrassing,
but,
like
look,
it
shows
up
on
mb
viewer,
it's
like
a
review
of
a
capacitor
and
some
notebooks.
But
what's
really
cool
is
to
do
this?
I
took
and
I
wrote
a
just
to
mimic
what
tony
was
showing
us
was.
I
have
a
notebook.
Look
I'm
still
using
pylab.
Do
you
remember
when
that
was
a
thing
and
it
builds
a
ui.
I
can't
display
it
in
github,
but
it
actually
builds
a
ui
and,
like
I
did
the
same
thing.
D
Tony
did
here's
my
little
javascript
display
and
here
is
some
very
insecure
javascript
to
build
a
ui
in
the
notebook
and
analyze
some
data.
I
don't
know
if
it
still
works,
but
it
builds
this
little
like
interface,
we're
interacting
with
this
impedance
analyzer
from
my
undergraduate
days.
So
you
know
feel
free
to
check
out
this
note
or
this
repo
called
impedance
and
this
other
repo
called
cal
poly
thesis.
K
D
A
D
Well
so
I
was
at
cal
poly,
which
of
course
is
one
of
the
homes
of
jupiter
notebook.
One
of
the
co-founders
brian
was
here.
He
was
my
quantum
mechanics
professor
and
I
was
writing
all
of
this
in
matlab,
as
you
do
as
a
physicist
and
I
was
using
a
less
than
legal
copy
of
matlab
to
do
all
that
and
was
feeling
a
little
bit
guilty
about
that.
So
I
decided
I
would
we
were
chatting
in
one
of
the
classes
and
he
said
you
should
check
out
this
thing.
D
I've
been
working
on
and
this
was
like-
I
python
notebook
like
like
way
before
it
was
ever
released.
I
don't
think
he
wanted
to
show
it
off
very
much,
but
and
then
over
that
summer
we
that's
when
the
the
notebook
really
got
developed
for
that,
like
very
initial
release,
the
ipython
notebook,
which
actually
looks
a
lot
like
jupiter,
lab
today
kind
of
funny
enough,
there's
like
the
side
panel
and
like
if
you
go
look
at
old
python
photos.
I
python
notebook
photos,
it's
pretty
interesting
and
then
yeah.
I
decided
like.
D
I
wonder
if
I
could
write
like
my
whole
thesis.
That's
in
matlab
in
this
you
know
open
source
language
python,
so
I
spent
a
whole
night
translating
everything
I'd
written
matlab
into
into
jupiter,
notebooks
and
then,
what's
even
worse,
is
that
ui
notebook
that
I
showed
you,
the
ui
that
I
had
for
the
machine
prior
to
that
was
in
lab
view.
D
I
don't
know
if
anyone
knows
what
labview
is,
but
there's
a
throwback,
so
I
had
built
an
entire
la
or
a
ui
and
labview,
and
then
was
able
to
recreate
that,
and
it
took
me
a
long
time
to
write
that
labview
code,
because
if
anybody
has
written
labview
code,
it's
nearly
impossible
to
debug.
It's
like
just
the.
D
Yeah,
like
throwing
spaghetti
on
a
plate
and
trying
to
untangle
the
spaghetti
and
so
yeah.
I
did
that
and
then
in
the
night
like
wrote
it
all
in
javascript
that
just
rendered
in
the
notebook
and
then
I
had
a
whole
reproducing
one
notebook
that
had
both
the
ui
at
the
top
of
it
and
then
all
the
analysis
at
the
bottom
of
it.
And
then
I
just
printed
that
notebook
and
turned
it
in.
D
As
my
thesis
which
I
thought
was
really
cool
at
the
time
and
then
I
put
it
on
github
and
talked
about
reproducible
research
for
a
little
while,
which
was
a
very
new
concept
to
me
at
the
time.
So
I
was
very
excited
very
bright-eyed
and
bushy-tailed
yeah,
and
here
I
am
eight
years
later,
nine
years
later,.
C
Yeah
all
the
code
before
my
notebook
like
right
before
that
was
just
matlab
code
and
like
you,
can
slowly
see
it
like
becoming
more
pythonic
and
then
eventually
just
doesn't
exist
anymore,
but
there's
a
practical
programming
language
like
one
thing
that,
like
I
really
missed
from
matlab,
is
the
documentation
like
you
didn't
have
to
leave
matlab
for
documentation.
That's
the
one
thing
I've
always
desired
from
jupiter
is
like
a
place
where
I
could
have
the
documentation
inside,
but
maybe
matthias's
papyri
project
is
going
to
get
us
some
of
that
stuff.
A
I
was
thinking
the
same
thing
about
possibly
papyri.
Let
me
find
you
all
a
link.
A
C
B
That
was
some
high
schoolers
when
I
was
volunteering
at
the
fab
lab
in
san
diego,
a
community
non-profit
maker
space,
and
so
they
would
they
would
draw
on
my
whiteboard,
and
I
just
thought
that
one
was
great.
They
were
a
bunch
of
girls
like
teaching
a
whole
bunch
of
guys
who
didn't
know
how
to
code,
and
it
was
just
the
flip
side
and
it
was
just
very
creative
how
they
did
it.
B
But
the
talk
that
I've
shared
in
the
slack
I
mean
in
the
zoom
chat
is
one
that
we
did
at
qualcomm
for
a
bunch
of
college
interns
as
part
of
a
big
summer.
Grace
hopper
thing
and
jess
hamrick
was
somebody
that
really
did
some
groundbreaking
early
work
on
jupiter
in
or
ipython
in
education,
and
so
it
was
sort
of
a
shout
out
to
a
lot
of
the
work
that
she
did
so.
B
That
one
was
fun
in
fact,
I'm
working
on
another
one
to
try
and
explain
sort
of
kubernetes
type
stuff.
E
I
will
give
a
shadow
of
what
fernando
would
have
said
and
he
can
talk
some
other
time
because
he's
clearly
not
going
to
make
it
in
the
next
11
minutes.
So
this
isn't
that
big
a
surprise.
I
hope,
as
most
of
you
know,
there's
been
a
lot
of
back
and
forth
on
jupiter
governance
and
some
things
have
happened.
E
Last
year
we
created
the
jupiter
distinguished
contributors
body,
and
that
was
one
of
the
three
planks
of
the
new
governance
that
we've
been
heading
toward
slowly
and
right
now
we
are
in
the
voting
phase
of
this
pull
request
that
I
linked
in
the
chat
for
the
software
steering
council
and
because
this
is
not
yet
completed
as
a
vote
and
because
really
it
doesn't
impose
any
specific
call
to
action
now.
The
idea,
I
think,
was
to
just
familiarize
people
with
this
concept
that
there
will
likely
be.
I
mean
everything.
E
Every
everything
is
contingent
until
vote
is
finished,
but
there
will
likely
be
a
software
steering
console
and
the
premise
of
the
software
steering
console
is
for
those
of
you
who
work
on
individual
jupiter
sub
projects.
Those
projects
will
have
a
group
of
decision
makers
who
the
projects
themselves
will
nominate
and
pick
and
those
decision
makers.
E
E
In
addition
to
representatives
from
software
sub-projects,
there
will
be
some
working
groups
who
will
also
have
representatives
in
the
software
steering
council,
and
this
is
a
body
whose
purpose
is
to
just
allow
the
different
projects
to
keep
up
with
what
is
happening,
project
wide,
to
communicate
about
initiatives
that
are
very
likely
going
to
affect
more
than
one
project
and
primarily
to
be
the
body
that
votes
on
and
approves
jupiter
enhancement
proposals
japs
up
until
now,
jobs
have
been
voted
on
by
the
full
jupiter
steering
council
and
hopefully,
when
there
is
a
more
targeted
software
steering
council
with
representatives
from
each
individual
project.
E
The
conversations
can
maybe
happen
a
little
bit
faster
and
the
decisions
can
be
made
a
little
bit
more
quickly.
There
isn't
any
specific
thing
that
you
need
to
do.
This
is
mostly
to
just
let
you
know
that
there
is
a
this
vote
happening.
If
you
have
input
and
you
would
like
to
weigh
in
you
should,
there
is
also
a
weekly
governance-
call
that's
on
the
jupiter
calendar,
which
unfortunately
happens
at
the
same
time
as
the
security
working
group
every
other
week,
but
that
is
an
open
call
that
you
are
welcome
to
join.
E
If
these
issues
are
things
that
you
care
about
and
yeah
the
next
thing
that
is
likely
to
land.
Is
this
software
steering
council
fernando
had
a
lot
more
to
say
just
about
the
context
and
all
that,
but
I
want
to
keep
it
brief,
because
I
have
not
been
as
active
in
the
past
few
weeks
anyway,
because
I'm
on
leave
so
yeah
I
mean,
if
you
have
any
questions,
I
probably
can
answer
them,
but
if
I
can't
I
can
tell
you
where
to
go,
to
get
the
answers.
A
E
Oh
no,
let
me
link
the
discourse
thread.
B
E
So
this
thread
that
I've
linked
it's
a
little
bit
behind
on
the
minutes,
partly
because
I
think
the
last
few
meetings
really
have
been
people
just
inside
google
docs
typing
stuff,
but
at
the
top
level
of
each
meeting
minute.
There's
the
link
to
the
call
the
call
doesn't
happen
on
this
channel,
partly
because
this
channel
is
being
used
for
the
security
working
group
and
partly
because
it
was
initially
on
fernando's
own
channel.
We
just
left
it
there,
but
it
is
open
to
the
public.
E
You
can
come
if
you
want
to
think
and
talk
and
work
on
governance
and
yeah
and
obviously
you're
welcome
to.
A
E
In
that
same
repo,
that
the
pr
is
in
there
is
a
document
called
decision
making
guide
and
it
lays
out
how
to
create
the
voting
body
in
each
subproject.
That
will
eventually
pick
the
representative.
E
So
what
I
would
say
is
look
forward
to
whichever
project
you're
involved
in
in
the
next
few
meetings-
maybe
not
the
next
one,
maybe
the
one
after
or
something
someone
basically
saying
hey.
Let's
start
doing
this,
because
soon
we're
gonna
have
to
pick
a
representative
for
our
project.
So
the
more
people
know
that
this
is
a
thing.
That's
heading
in
that
direction,
the
less
of
a
surprise,
that'll
be,
and
the
more
you
can
think
about
all
right.
Well,
who
is
in
this
project
who
votes
etc?
E
But
really
you
know
I,
I
don't
actually
think
like.
No
one
has
homework
here
if
you're
interested.
I
want
you
to
go,
read
these
things
and
familiarize
yourself,
and
that
would
be
lovely
but,
like
I
don't
want
to
say,
go,
do
work
like
that's
not
what
this
is.
A
E
The
expectation
I
would
have
is
that
the
software
steering
council
does,
if
we're
lucky,
so
does
the
third
and
final
body
the
executive
board,
but
that
document
is
still
in
a
draft
and
there's
a
lot
of
back
and
forth
and
once
a
thing
comes
out
of
draft
voting
takes
up
to
four
weeks.
So
I
hope
so,
but
you
know
if
it
doesn't
it'll
be
soon
thereafter
we're
not
I
mean
this
process
has
taken.
You
know
two
and
a
half
years,
but
we
are
in
the
final
chapter
of
it.
L
And
just
here
for
like
the
last
30
seconds,
but
I
was
hearing
darian
finishing
up
so
sorry,
sorry
for
coming
in
so
late.
I
I
apologize,
but
thanks
darian
for
for
picking
up.
We
do
have.
I
don't
know
if
you
passed
along
the
link,
we
had
some
like
minimal,
slides.
E
I
did
not
know
because
the
slides
look
like
they
might
have
still
had
notes
in
them,
so
I
thought
maybe
I'll
just
verbally
describe
and
I
didn't
give
too
much
context
because
I
waited
to
the
last
second.
So
really,
all
I
said
is:
there's
this
vote
for
the
ssc.
Here's.
What
the
ssc
is,
you
don't
have
any
homework.
Yeah.
L
No,
I
I
think
that
I
think
the
slides
are
fine.
If
anybody
wants
to
get
cool.
Take
a
quick
look,
I
don't
think
there's
anything
there.
That's
that's
an
issue
if
folks
want
to
take
a
quick
look,
but.
L
It's
possible
that
they
have
hold
on.
Let
me
change
the
access
link.
A
D
And
fernando,
if
you
get
a
chance,
go
go
watch
this
video
in
the
in
the
future
that
there
were
notebooks
that
are
seven
to
ten
years
old
that
were
shared
throughout
this
call.
So
it
might
be
a
little
fun
nostalgic
trip
for
you,
we'll.
L
Or
brian
I
mean
yeah,
it
would
be
one
one
of
us
early
on
and
I
mean
who
knows
what's
been
deleted,
probably
tracing
in
terms
of
notebooks
and
usage
tracing
back
to
the
tutorials.
L
From,
for
example,
the
ipython
in-depth
tutorial
was
a
repo
that
we
used
very
early
on
to
teach
workshops
around
and
we
we
did
write
notebooks
for
it
very
early
on
and
so
those
date
back.
Probably
to.
I
think
that
repo
goes
back
to
2011
2012,
which
was
really
back
kind
of
when,
when
when
we,
when
we
announced
when
we
first
announced
it
publicly
and
when
the
format
stabilized
into
the
the
current
json
format
or
at
least
the
earlier
iterations
of
the
current
json-based
format,.
D
L
Are
there
any
quick
questions
on
on
the
governance
on
the
governance
notes?
I
mean,
I
know
that
it
was
kind
of
chaotic
to
show
up
like
this,
and
I
really
do
apologize.
It's
just
the
mornings
or
that
time
with
with
the
kiddos,
but
but
the
the
basic.
L
The
basic
idea
really
is
that
pr
98
was
voted
on
was
kind
of
open
for
a
long
time
and
it
has
gone
in,
but
it's
been
somewhat
dormant
in
a
sense
dormant,
because
the
the
next
phase,
which
is
the
pr
103
on
the
software
student
council,
is
what
really
will
make
it
sort
of
matter
a
lot
more
and
become
much
more
relevant,
but
because
that
pr
is
now
open.
L
It's
probably
a
good
idea
for
folks
to
take
a
look
at
this,
because
technically
this
this
has
been
adopted
and
and
what
we
tried
to
do
was
really
capture
existing
practices
across
the
projects.
But
we
do
want
to
harmonize
them
so
that
it's
a
little
bit
easier
to
have.
L
Jupiter
is
huge
right
and
thank
you
isabella
and
others
for
these
kinds
of
activities
that
help
keep
some
high
level
perspective
on
the
project,
but
precisely
harmonizing
decision
making
and
conversations
and
discussions
and
procedures
across
a
project
as
big
as
hard
and
that's
the
intent
of
this
was
to
read
kind
of
from
what
existed
from
our
practices
not
impose
anything
new
but
formalize
and
structure
those
processes
in
terms
of
how
to
make
especially
and
how
to
make
decisions
across
the
projects
both
individually
and
and
when
things
cut
cut
across
and
the
software
steering
council,
we
hope
will
become
a
good
body
where
those
decisions
that
are
big
and
complicated
can
funnel
in
where
jabs
can
be
managed
and
because
that
one
is
now
in
review.
L
We
really
would
like
people
to
take
a
look
at
what
actually
went
into
98.
What
are
those
guides,
because
we
will
want
to
begin
applying
this
by
basically
formalizing
those
individual
decision-making
bodies,
bootstrapping
them
in
the
process
we
described,
which
would
be
basically
work
with
someone
from
the
steering
council
and
each
individual
team
bootstrap
that
that
formal
voting
body
of
whatever
size
is
appropriate.
L
It's
not
the
same
thing
to
have
a
decision
making
team
for
something
as
big
as
jupiter
hub
as
it
is
to
say
hi
python
that
might
have
a
few
very
few
super
active
people
working
on
it
and
so
sizes
will
matter
and-
and
they
should
be
chosen
kind
of
consistent
with
with
the
structure
of
each
project.
But
if
people
these
are
meant
to
be
living
documents.
So
even
though
these
have
been
merged
and
they're
there
and
they've
been
there
for
a
few
months.
L
If
people
have
concerns
ideas
or
feedback
come
by
either
pitch
in
on
on
github
or
even
come
on
on
on
the
fridays,
as
darian
said,
it's
the
world's
most
boring
podcast,
but
we
do
keep
at
it
and
it
does
produce
produce
these
things,
and
hopefully,
when
all
this
is
merged,
it'll
be
easier
to
kind
of
unlock,
unlock
energy
that
I
think
exists
in
the
community
and
that
I
know
that
people
are
are
impatient
for
so
sorry
for
the
delay.
But
hopefully
these
quick
notes,
there's
links
in
there
to
all
of
the
relevant
documents.
L
So
so
you
folks
can
open
them
from
there
and
and
we're
happy
to
take
feedback,
and
I
do
I
do
want
to
say
this
would
not
have
happened
if
varian
hadn't
been
at
the
helm
for
two
years.
We
owe
him
an
immense
debt
of
gratitude
for
all
the
work
he
has
done
and
like
keeping
us
on
task
and
and
leading
her
really
actually
at
times
a
very
difficult
set
of
conversations
and
he's
been
he's
been
absolutely
incredibly
generous
with
his
time
and
wisdom.
So
thanks
darian.
A
A
At
least
I'm
thinking
december
might
not
be
feasible,
yeah
it's
hard
to
dodge
and
have
a
really
early
call
right
after
november,
so
likely
just
november,
but
to
be
decided
I'll
make
sure
to
announce
it.
That's
my
current
thought,
though,
but
yeah
thank
you.
I'm
happy
they've
been
going,
it's
been
a
been
a
real
adventure
and
I
love
seeing
what
people
are
thinking
about
each
month.
It's
always
a
different
call.
Every
time
never
know
what
I'm
walking
into
yeah.
A
Yeah-
and
in
that
case
I'm
gonna
link,
you
can
always
give
feedback
on
these
calls.
It's
just
a
few
questions,
make
sure
things
aren't
broken
and
you
can
tell
me
if
something's
wrong
or
you
have
ideas,
and
I
do
know
for
sure
we
are
having
a
november
one.
I
do
have
an
agenda
for
that
I'll
link
to
if
you
were
so
inspired
by
today.
You
already
know
what
you
want
to
share
in
a
month
regardless.
A
Thank
you,
everyone
for
your
time
and
thank
you
all
for
your
help,
keeping
things
running
when
we
had
an
empty
agenda
today.
I
think
we
ended
up
with
some
great
discussions,
but
that
would
not
have
been
possible
without
all
your
participation
and
impromptu
shares.
So
thank
you
and
have
a
great
rest
of
your
day,
see
ya.