►
From YouTube: IPython/Jupyter Dev Meeting, April 26, 2016
Description
Meeting of the IPython/Jupyter development team.
A
C
Just
a
little
thing
that
we
did
a
bunch
of
releases
last
week,
4.2
of
notebook
and
I
think
also
4.2
ipython,
and
we
found
a
couple
little
things
with
the
notebook
release.
So
I
think
we
want
to
do
like
a
four
point,
two
point
one
next
week
or
so
because
it
has
PR
fixing
the
thing
that
to
do
with
older
versions
of
widgets.
So
finding
little
things
in
the
4.2
release
that
should
be
fixed
in
pen
of
a
first-round
bug
fix
be
good
in
the
next
few
days.
A
week.
B
A
So
I
can
give
an
update.
I've
been
working
with
carol
on
the
documentation,
so
I'm
just
learning
how
to
s,
approve
or
merge
some
of
her
pull
requests
so
we'll
continue
to
work
together
over
the
next
few
weeks
to
update
the
documentation
and
work
on
formatting
and
content
with
fernando
and
brian.
So
certainly,
if
anyone
has
anything
they'd
like
to
contribute,
send
it
our
way
and
we
can
wrap
it
into
what
we're
putting
together.
D
A
That's
a
good
question.
It
looks
like
right
now
we're
still
using
a
read
the
docs
format,
but
I,
don't
I,
don't
think.
That's
the
end
of
the
game.
I
think
that's
just
the
beginning.
We're
really
just
working
on
content
right
now
and
then,
once
that's
in
good
shape,
we
can
kind
of
turn
it
into
whatever
form
we
want
to
ultimately
use
it
in.
B
But
just
to
just
to
add
to
a
Jason,
I
I
think
I
mean
we
have.
We
have
a
huge
amount
of
rest
still
in
our
sources
and
so
I,
don't
think
I,
don't
think
his
thing's
cool
chain
is
going
away
anytime
soon,
but
I
do
know
that
Sylvan,
for
example,
and
and
John
did
most
of
the
most
of
the
dogs
for
the
recent
IP
widgets
release
was
was
a
notebook
format.
B
I'm
not
I'm
not
sure
that
the
notebook
is
the
most
convenient
way
to
edit
more
api,
ish
adults
or
dogs
that
are
purely
that
really
don't
have
code
that
might
be
more
comfortable.
Just
in
a
text.
Editor
editing
the
markdown
file
or
res
file,
but
I
I
have
the
impression
that
the
if
you
use
Fink's
as
an
endpoint,
that
the
integration
of
markdown
and
mark
down
rest
and
notebooks
as
Anna
source
streams
that
I'll
get
merged
in
the
in
the
final
output
is
starting
to
work
reasonably
well
or
am
I
mistaken.
B
E
C
E
I
by
which
has
both
mock
down
and
notebooks
one
thing
we
must
be
careful
when
we
write
the
notebooks
for
documentation
is
that
the
headers
you
know
in
back
down
in
the
book
correspond
to
what
you
want
to
see
as
headers
globally
on
in
the
final
documentation,
because
this
is
what
is
going
to
be
used
to
make
the
tree.
So
she
make
a
double
world
title.
It's
going
to
be
a
top-level
item
in
the
documentation
which
is
a
mature
with
it
tooks
the
best
thing
or
not.
B
E
B
Yeah,
that's
interesting,
so
I
wonder,
there's
a
way
to
modify
the
markdown
processor
to
basically
bump
up
bump
up
every
every
heading
level
by
one
or
something
like
that
when
they're
being
consumed
that
documentation
so
that
there's
an
enclosing,
there's
an
enclosing
enclosing
tricky
that,
but
for
these
things
are
being
appended
as
node
as
nodes.
Ok,
we
can.
We
can
look
into
that.
B
C
C
D
F
A
One
thing
honor
talked
about
was
creating
a
centralized
events
calendar
for
the
dev
team,
so
creating
a
way
for
us
to
keep
track
of
who's
going
to
which
conferences.
So
maybe
we
could
try,
try
it
out
and
you
guys
could
send
her
a
list
of
the
conference's
that
you're
planning
to
attend.
So
she
can
start
adding
those
to
the
calendar.
A
C
A
D
D
F
And
yeah
it's
it's
still
going.
I've
I
think
when
most
of
the
way
to
a
draft
I've
asked
several
people
home
who
I
know
have
particular
associations
with
particular
parts
of
the
project
to
to
right
and
a
little
paragraph
about
and
the
three
things
that
I
I
wanted
to
fill
in.
Were
the
collaboration
staff
widgets
and
am
ende
grader
and
Jupiter,
and
education
and
I've
deep
pinged
the
relevant
people
by
email
to
fill
that
in
hopefully
in
a
few
days,
they'll
be
a
draft
that
we
can
look
over
and
and
start
improving.
F
B
We
have
we're
trying
to
schedule
a
meeting
that
somebody
here
might
be
interested
in,
so
I
just
want
to
let
you
know
and
if
that's
the
case,
let
just
ping
Jamie
and
I.
There
are
folks
in
Canada
who
are
interested
in
deploying
Jupiter
hop
on
a
relatively
large
scale
for
for
research,
and
so
just
let
us
know
if
you'd
like
to
participate
in
that
discussion,
kind
of
a
larger
scale,
Jupiter
hub
deployments,
min
min
Jamie
and
I
will
will
be
in
that
not
everybody
needs
to
budget.
Anybody
wants
to
just
let
us
out.
A
I
do
so
for
nieto
and
I
will
be
going
over
the
road
map
today.
So
I
just
want
to
make
sure
everybody's
wrapped.
In
the
conversations
we
had
mostly,
you
guys
had
during
the
week-long
depth
meeting
here
in
Berkeley,
you've
wrapped
that
into
the
roadmap
repo
on
github,
because
that's
what
we'll
be
using
to
kind
of
to
drive
our
conversation
and
scheduling
and
planning.