►
From YouTube: IPython/Jupyter Dev Meeting, May 10, 2016
Description
Meeting of the IPython/Jupyter development team on May 10, 2016
B
A
Can
kick
it
off
with
all
just
give
a
short
report
on
how
the
roadmap
reviews
going
matias
fernando
and
I
sat
down
and
went
through
both
the
github
roadmap
repo
and
also
the
half
pad,
and
currently
we're
doing
a
lot
of
reconciliation
between
the
two.
So
I
just
want
to
remind
folks
that
it's
super
helpful
for
us
for
you
to
transfer
your
pad
nodes
over
to
the
github
repo.
There
are
some
pieces
of
work
that
are
missing
so
most
of
the
works
there.
C
Awesome
I'll
go
next,
just
a
couple
of
quick
things.
From
the
operations
side,
I
sent
out
an
email
to
everyone
related
to
the
events
calendar,
I'm
looking
to
publish
a
a
public
google
calendar
on
May
seventeenth.
So
if
you
have
anything
that
you'd
like
to
be
included
on
there,
just
send
it
to
me
by
the
16th
about
10
events
on
there
so
far,
but
I'm
sure
there's
a
lot
more
I'll
also
be
adding
events
kind
of
just
from
my
own
research
and
even
if
you're,
not
attending
these
events.
C
If
you're
aware
of
events
that
might
be
interesting
to
the
Jupiter
community,
please
send
those
send
those
my
way,
we're
also
in
the
process
of
transitioning
our
newsletter
to
a
medium
and
just
really
briefly,
on
that
I
think
we've
mostly
worked
through
the
technical
questions
that
archiving
for
the
content
on
that
is
is
not
the
greatest,
but
it's
something
that
I
think
we
have
a
process
in
place
for
now
and
the
next
step
on
that
is
creating
a
custom
sub
domain.
A
little
bit
stalled
on
that
yesterday.
C
D
C
Great
and
that's
pretty
much
it,
we
have
the
content
ready
for
the
next
drop.
I
just
need
to
work
through
the
logistics
of
actually
send
that
sending
that
out
and
a
medium
has
an
integration
with
Twitter,
so
will
have
an
insta
following
for
that.
For
that
newsletter
it
shows
about
1,800
people,
who
are
our
followers
on
Twitter,
who
also
have
medium
accounts,
of
course,
have
to
select
the
within
their
settings.
C
They
have
to
allow
people
that
they
followed
to
send
them
letters,
which
is
how
we'll
be
getting
an
email
out
to
the
followers
that
looks
mostly
like
a
newsletter,
so
we
won't
get
all
of
those
people.
You
know
allowing
us
to
email
them,
but
we
should
be
able
to
build
a
following
for
that
newsletter
pretty
quickly.
Hopefully-
and
that's
that's
it
for
me,
if
you
have
ideas
on
stories
for
upcoming
newsletters,
please
send
them
my
way
since
I'm,
not
a
technical
person.
C
A
E
So
so,
I'm
still
working
on
the
big
repo
merge
for
phosphor
it's
going
well
I'm
nearly
done
with
phosphor
UI
is
basically
spelling
the
end
of
the
merge
that
we
can
move
on
from
there.
My
last
week
was
mostly
washed
because
I
was
moving
from
New
York
to
Texas
so
Texas
now,
so
that's
good
I'll
give
a
bit
of
an
update
for
Brian
as
well,
since
he
was
not
I.
E
Don't
think
he's
going
to
be
here
today
because
he's
still
at
Microsoft,
but
last
week
he
demoed
Jupiter
lab
to
two
different
teams
at
Microsoft
and
that
went
really
exceptionally
well.
So
both
of
those
teams
are
on
board
they're,
basically
wanting
to
make
some
plugins
for
cheaper
glad
to
manage
as
your
resources,
and
so
we
should
get
beginning,
some
traction
with
them,
and
some
good
feedback
and
feature
requests
and
good
driving
use
case.
Crap,
Oh,
simple
lang:
okay,.
A
G
We're
still
working
on
it,
we
had
a
little
sit
down
without
on
that
and
we
were
pretty
solid
on
a
venue
we're
going
to
scope
it
down
from
a
full
two
days,
probably
to
an
evening
social
that
might
be
a
film
screening.
If
we
can,
we
can
line
up
the
right
boy
content
for
it,
and
yeah
I
mean
it's
going
to
be
to
be
pretty
local.
G
G
There
have
been
some
attempts
at
different
times
to
try
and
get
some
of
the
ego
out
of
selection
speakers
and
things
like
that,
and
we're
considering
trying
to
do
some
of
that
stuff
up
on
up
on
github
to
get
people
to
help
us
help
us
build
the
day
that
they
want
to
go
to,
but
the
venue
Georgia
Tech
is
solid.
We're
going
to
be
talking
to
gone
thursday
with
that
squared
away
and
yeah.
So
looking
forward
to
that,
what's.
A
G
I
have
visibility
into
parts
of
the
the
calendar
at
the
venue,
but
not
all
of
them.
So,
but
at
this
point
where
we
are
now
looking
at
at
early
August,
because
you
didn't
pull
the
trigger
fast
enough
on
jhalak
weeks,
so
it'll
be
lovely
in
Atlanta
I'm
sure
just
you
know
room
but
still
be
all
right.
You
got
air
conditioner,
all
right
great
other
than
that.
Nothing
else
too
much
much
to
report
just
kind
of
like
a
little
bit
anytime
stuff.
B
I'll
just
mention
that
Steve
and
I
have
been
working
a
lot
on
the
notebook
architecture
for
Jupiter
lab
the
execution
architecture
for
documents
in
Jupiter
lab.
We
think
we
have
a
pretty
good
model
at
this
point
and
and
we're
actually
implementing
it
to
to
to
see
if
we
really
think
it's
a
good
model,
but
we're
happy
to
discuss
it
with
others.
I
think
we've
run
it
by
Brian
and
Chris,
and
men
at
least,
and
and
we're
happy
to
discuss
that
with
Vinny
with
anybody
that
wants
to.
B
H
B
A
D
G
D
Did
talk
about
that?
Yes,
and
so
they
may
have
people
who
can
help
with
the
internationalisation
stuff,
which
and
we've
had
some
at
least
someone
from
IBM
pop
onto
the
enhanced
proposal
for
internationalization,
so
I
think
there's
a
reasonable
chance
that
might
actually
get
work
started
on
on
that
before
too
long
Wow.
B
D
The
yeah,
if
nurse,
were
that
it's
more
similar
to
what
we're
doing
I
can
never
remember
that
exceed
though
we're
working
at
UCSD
folks
for
to
put
juba
travel
in
front
of
exeed,
which
is
kind
of
all
NSF
computing
resources.
It's
more
analogous
to
that.
But
it's
it.
It's
federated
across
computing
resources
at
many
universities
and
something
called
compute
Canada.
D
B
A
It's
a
fun
hook.
All
right
I
have
a
just
a
short
update
from
Dom
Ian.
He
says
he
has
very
bad
sound
right
now,
but
he's
working
on
full
time
continuum,
internal
stuff,
so
not
too
much
to
share
in
the
open
space.
Oh
and
that's
is
a
faint
lasted
yeah
yeah,
oh
hey!
Pete!
Do
you
want
to
give
an
update
on
what
you're
working
on.
I
Really
not
too
much
other
than
what
I
wrote
there.
We
did
a
first
npm
release
of
the
dashboard
server,
who
thought
was
the
most
interesting
thing,
so
it's
actually
up
on
the
MP
MJS
I
talked
to
John
a
little
while
back
to
make
sure
that
you
know
we
don't
have
a
Jupiter,
namespace
or
anything
I've
sort
of
been
out
of
that
conversation,
but
if
it
needs
to
move
or
if
I've
done
something
we're
on
just.
Let
me
know
we
can
move
the
package.
I
C
Not
for
me,
but
I
did
think
of
something
else
that
would
be
helpful
from
the
group
is
I'm
looking
to
connect
with
I'm
looking
to
connect
with
other
administrators
or
operations,
people
within
open
source
software
projects.
So
if
you
have
contacts
in
that
arena
that
you'd
like
to
share
with
me,
I
just
want
to
connect
with
others
who
are
maybe
doing
something
similar
to
what
I'm
doing.
That
would
be
great
if
you
could
share.
A
A
A
Won't
quite
sure
how
to
get
out
of
it
so
men-
maybe
you-
can
help
me
out
when
I
want
to
get
out
of
it.
Can
you
see
the
spreadsheet?
Yes,
okay
great?
So
this
is
just
a
very
bare-bones
version
of
the
roadmap
that
we're
working
toward
and
what
I
did
was.
I
took
the
information,
that's
in
the
github
repo
roadmap,
repo
and
just
started
bidding
work
into
two
month
increments.
So
you
can
see
on
the
left.
A
Side
is
kind
of
the
the
the
project
or
the
group
of
work
that
were
focused
on
and
then
going
over
to
your
right.
We
have
next,
which
we've
been
as
work
to
be
conducted
in
May
and
June.
The
next
Plus
Ones
july
in
august,
and
then
kind
of
the
future
is
thing
else
and
we'll
just
start
moving
the
work
through
these
two
months
for
clocks,
so
under
each
of
these
projects,
have
the
specific
work
or
features
that
will
be
developed.
A
Now.
Some
of
these
projects-
or
you
know,
products
that
we're
producing
the
notation-
was
version
numbers
instead
of
next
next
plus
one
so
I
tried
to
line
those
up
as
best
that
I
could,
with
the
next
next
plus
1
milestones.
So
you
know,
take
a
look
at
those
I
can
share
this
link
with
folks,
and
you
can
start
making
comments.
Actually,
the
best
thing
to
do
would
be
to
make
the
comment
in
the
github
repo,
so
you're
updating
the
source
file,
because
this
is
just
a
view
of
the
data
so
goes
into.
I
pie,
widgets.
A
A
A
A
D
A
A
A
One
sec,
so
we
also
have
the
results
of
this
survey
where
we
split
up
the
team's,
wouldn't
split
up
the
teams
we
created
teams,
so
we
basically
based
on
folks
responses
to
the
survey.
We
arrange
them
and
we
arranged
you
in
the
teams
where
you
said
you
could
do
different
levels
of
work
so
we're
here.
We
have
colonel
and
events
and
user
engagement
and
widgets
and
then
folks,
no
volunteered
to
take
on
a
leadership
role
there.
A
So
that's
another
piece
that
we
put
together
and
then
I
created
just
a
very
drafty
team
schedule
for
for
the
summer,
because
I
know
people
are
traveling
a
lot
so
I
have
you
know
different
different
people,
different
team
members,
traveling
and
conferences,
and
just
in
one
place
to
have
an
idea
of
where
people
are
are
at
when
we
r
groups
trying
to
get
work
done
I'm
just
going
to
stop
sharing
my
screen.
Okay,
do
you
see
me
or
do
you
see
my
screen?
A
Do
you
see
you
seem
like
a
good
newfangled
technology?
So
that's
that's
where
that's
the
progress
we've
made
on
the
road
map
we're
going
to
continue
to
refine
it
here.
It's
definitely
not
perfect
at
this
point,
but
I
did
want
to
show
progress
and
get
some
early
feedback.
So
you
know
we
make
sure
to
make.
You
know
my
throat
changes
and
instead
of
dropping
the
whole
thing
on
you
at
once,
and
having
a
lot
of
things
be
wrong.
F
Jamie
I'm
not
sure
where
to
put
the
port
of
the
Qt
console,
because
it's
not
really
next
version
of
the
Qt
console.
It's
a
web
version
that
is
currently
residing
in
Jupiter,
jazz,
notebook,
so
I,
don't
know
which
project
next
version.
That
really
is,
but
it's
not
in
the
road
map
right
now,
and
it
probably
should
be
okay.
A
So
that
might
be
a
useful
note
to
make
right
in
the
road
map
itself,
look
like
to
pull
request
and
update
that
with
the
readme
file.
I
guess
so.
It's
very
explicit.
We,
oh
sure,
yeah
put
it
out
there
cool
okay
here.
Okay,
does
anybody
else
have
anything
they
want
to
share
memories
triggered
by
something
I
talked
about
in
the
roadmap:
no
sweet,
memories
of
our
dev
conference.
Okay!
Great!
Well,
thanks!
So
much
for
your
time,
I'm
a
turn
off
for
recording.