►
From YouTube: IPython/Jupyter Dev Meeting, August 16, 2016
Description
Meeting of the IPython/Jupyter development team for August 16, 2016
Meeting Notes: https://jupyter.hackpad.com/August-2016-NVKlJmYxWK2
A
Morning,
everyone,
this
is
the
August,
sixteenth,
Jupiter
ipython,
that
meeting
and
as
usual,
let's
the
notes
are
on
the
hack
pad
we're
now
using
the
standard
channel
for
reference.
This
is
going
to
be
the
we
now
have
kind
of
a
project
white
account
for
these
meetings.
So
you,
the
URL,
will
stop
changing
week
to
week
and
let's
see
the
first
person
that
is
present
is
Steven,
because
Carol
is
not
making
an
in-person
social
life
or
notes
Steve
go
ahead.
Is
there
anything
that.
A
B
No
just
to
say
that
the
Jupiter
lab
presentation
I
gave
that
in
atlanta
was
very
well
received.
Lots
of
great
feedback,
all
a
dozen
hand
shut
up
in
the
end.
A
lot
of
great,
enthusiastic
feedback
and
suggestions
does
a
fun
time,
thanks
to
Nick
and
Tony,
for
setting
that
up
and
there's
an
open
issue.
I
linked
in
the
hack
pad
of
how
to
enable
third-party
extensions.
B
I
was
great
to
work
with
nick
friday
afternoon
last
week,
use
his
experience
in
creating
notebook
extensions
to
get
us
a
lot
further
down
the
path,
and
I
was
going
in
on
how
to
do
lab
extension.
So
I'm
going
to
carry
that
baton
this
we
try
to
try
to
get
something
working,
so
any
feedback
is
appreciated
on
that.
Do.
A
B
So
what
we
created
last
week
was
a
script
that
resides
in
jupiter
lab
that
helps,
make
this
possible
and
also
a
fork
of
Sullivan's
cookie,
widget,
cookie
cutter
template
that
uses
that
script
to
generate
the
right
content
and
basically
I'm
going
to
take
those
two
pieces
and
update
the
web
pack
build
of
Jupiter
lab
the
the
Jupiter
life
extension
itself
and
then
carry
that
forward
to
Jupiter
jayesh
widgets.
And
then
the
real
test
will
be
PQ
plot
have
something
that
depends
on
another
extension.
B
A
I
was
thinking,
and
you
can
let
us
know
when
you
think
the
time
is
right.
Just
a
couple
days
ago
I
was
using
ipython
pearl
and
I
was
realizing.
I
python
perl
has
an
extension,
which
is
the
cluster,
the
little
clusters
tab,
and
we
obviously
don't
want
to
kind
of
hard
bake
that
into
the
UI.
The
way
we
have
done
it
in
the
past.
A
That
should
be
basically
the
standalone
extension
that
we
provide
with
I
Python
Perl,
but
since
that
that
is
one
of
the
parents
of
projects
that
we
officially
maintain
its
a
good
candidate
for
for
reporting
it.
So,
but
you
can,
let
us
know
when,
when
you
think
the
time
is
right
to
play
with
that
one
for.
A
C
That
I
presented
on
Jupiter
lab
over
the
weekend
at
PI
data
and
SF.
It
was
a
great
conference
lots
of
interesting
talks
on
well.
You
know
these
pythons
conferences
are
mostly
how
people
are
using
the
Jupiter
notebook
in
different
ways
and
some
good
questions
about
the
demo.
You
know
one
question
came
up
about
leaflet
and
if
you
could
switch
out
the
base
map
for
that,
so
that's
probably
a
good
answer
to
have
in
your
pocket,
show
the
maps
functionality
and
that
yeah
that's
about
it
cool.
A
A
Yeah
no
I
heard
I
heard
great
things
about
I'm
glad
I
went
well,
I
didn't
make
it
to
PI
data,
because
I
was
at
the
as
Thomas
was
joking.
I
was
at
the
other
Bay
Area
data
conference
over
the
weekend,
which
is
kdd,
gave
a
talk
at
the
BB
p.m.
workshop
activity.
I
left
a
link
if
anyone's
interested
that
was
kind
of
a
more
a
combination
of
Jupiter,
material
and
kind
of
a
broader
picture,
diversity
and
chow,
and
in
that
community
great
audience.
A
Actually
two
really
neat
neat
program,
something
that
I
think
we
we
can
consider
for
I.
Think
non
focus
has
been
doing
rigged
up
in
that
in
that
regard,
but
but
this
was
a
very
well
structured
workshop,
focusing
on
on
what,
as
the
title
says,
broadening
participation
to
other
communities
in
in
this
space
and
and
they
did
a
very
thorough
job.
They
had
to
talk
shoot.
A
Sorry,
we
get
basically
weird
random
spammy
incoming
calls
here
organized
with
students
were
there
for
two
days
and
had
lots
of
guidance
and
support
their
travel
costs
were
covered
and
there
was
an
entire
kind
of
training
program
for
them
to
engage,
including
tutorials
and
mentorship,
and
so
I
think
it's
it's
a
good
model
to
keep
in
mind,
as
our
community
grows
in
how
to
approach
the
problem.
So,
if
anyone's
interested
in
that
topic,
let
me
know-
and
we
can
I
have
some
context
with
the
organizers.
D
I
come
back
and
diving
multiple
for
a
few
weeks
away
from
active
work
on
the
project.
I
also
was
at
hi-data
SF.
I
gave
a
talk
about
all
tear
on
one
thing
that
I
think
is
relevant
for
the
broader
community.
Is
that
we're
thinking
about
possibly
doing
a
jupiter
day,
new
york
city
I'll
be
out
in
new
york
city
for
some
of
the
fall
and
september-october.
C
A
Seen
it
I
haven't,
played
with
it
so
I
don't
know,
I,
don't
know
specifically
how
how
well
it
works
and
how
they're
addressing
the
that
one
of
the
perennial
issues
with
content
with
distributing
content
on
github
is
is
the
the
moment
you
hit
the
moment.
The
person
receiving
the
content
makes
changes
in
place,
which
is
a
very
natural
thing
to
do.
They
have
a
copy
of
it.
They
make
changes
and
new
new
content
arrives
now
you're
sort
of
hitting
hitting
full-blown
the
merge,
the
idea
of
merging
and
conflicts
and
whatnot
and
I.
A
Okay
but
II,
but
I've
seen
that
problem,
even
with
assignments
I
mean
unless
you,
you
really
manage
kind
of
a
separate
copy
and
whatnot.
If
you
make
updates
to
any
of
the
material
thats
related
to
an
assignment,
and
the
student
has
touched
it
in
any
way
already
I
mean
I've
had
that
problem
even
with
stuff
that
you
would
think
of
as
an
assignment
when
I
distributed
it
via
the
idea.
So
I'd
love
to
see
what
they've
done
on
that
problem.
They're.
E
A
A
A
F
Ok,
yeah
I've
attended
some
meat
past
but
I
good
to
see
you
Fernando,
my
mom
I,
don't
have
a
ton
to
report
this
week,
I've
been
I've,
been
focused
on
closing
out
open
PRS
on
the
notebook
repo
on
so
I've,
been
working
with
TS
and
Men
and
smothers
on
that.
Yes,
we've
almost
close
out
all
of
the
4.3
milestone,
PRS
open
PRS,
which
is
good
I,
think
you
still
have
a
couple
issues
that
we
should
address.
You
know
before
thinking
about
doing
it
release,
but
we're
getting
closer
to
that.
That's
good.
E
Anything
for
the
group,
yeah
I
will
just
continue
that
you're
doing
a
really
really
good
work.
I'm
really
happy
to
see
things
moving
forward,
and
you
definitely
have
fresh
ideas
and
improvements
to
the
workflow
that
are
really
welcome,
and
that's
even
if
the
legacy
netbook
would
make
developments
much
this
year.
E
Was
wondering
if
we
should
do
some
more
broad
introduction
so
that
the
community
knows
you
at
some
point,
but
probably
something
we
want
to
sink
is
Brian
and
at
some
point
we
want
to
do
that
for
I
might
as
well,
because
I
know
that
one
of
the
comment
I
had
a
few
years
ago
is
that
people
don't
know
who
is
actually
working
at
a
book
and
who
is
not,
and
many
people
are
not
on
the
mailing
list
and
so
having
a
blog
post
to
say:
hey,
we
have
this
person
works.
Half
time
works
full
time.
A
A
We've
been
sending
emails
to
the
mailing
list,
but
that's
a
good
point
that
maybe
maybe
when,
when
we
bring
someone
someone
on
board
instead
of
just
sending
that
as
an
email,
we
should
just
make
it
a
quick
blog
post.
When
you
came
on
board
what
I
did
was
I
sent
it
only
any
mail
to
the
mailing
list.
I
don't
think
I
don't
think
we
did
that
as
blog
post
and
I.
E
A
We
can,
with
what
we
can
do
is
just
when
people
arrive,
send
a
quick
email
to
the
list,
which
is
where
the
more
kind
of
the
more
regular
people
hang
out
and
then
after
some
period
goes
by
any
nucleus.
That
weird,
maybe
may
have
been
over
too
long,
because
this
idea
just
came
up,
but
but
we
can
in
general,
just
wait.
A
few
weeks
give
people
a
chance
it
going
to
settle
in
and
then
make
it
slightly
broader
announcement
done
on
the
blog
that
that's
probably
good
plan
yeah.
Oh
you!
E
A
A
Okay,
well,
we'll
give
you
a
minute
to
see
if
you
can
sort
it
out,
but
but
yeah.
We
can't
hear
you
right
now.
I
just
remembered
I
did
send
an
email
to
the
mailing
list
about
the
notion
of
getting
a
little
bit
more
structured
into
teams,
and
so
I
think
we
want
to
try
to
move
forward
with
with
that.
Let
us
know
if
you
have,
if
you
have
any
thoughts
on
the
mailing
list
and
obviously,
as
I
said
its
preliminary,
it's
a
first
draft.
Don't
get
pissed
at
me.
A
I
tried
to
both
ingest
and
got
it
I
mean
Jamie
did
all
the
hard
work,
but
but
we
try
to
decide
together
with
Brian
kind
of
how
how
did
lay
out
things,
taking
your
input
into
account,
but
also
looking
at
everything,
that's
on
the
table,
trying
to
not
leave
a
key
gaps,
and
so,
let's,
let's
move
forward
with
with
that,
but
Sylvan
you
were
the
last
one
and
so
we're
sort
of
coming
to
the
end
of
the
meeting.
I
don't
know
if
we
are
going
to
get
your
voice
today,
not.
C
C
A
A
Doubt
it
I
mean
we're
saying:
we've
never
seen
that
problem
before
anyway,
we're
not
gonna
be
debugging
blue
jeans.
Right
now,
nope
we
can't
hear
Mike
and
we
can
fear
Sylvan
and
we're
not
going
to
start
debugging
this
right
now.
So
anyone
else
have
anything
classmate
it
and
otherwise.
Sorry
about
selvin
Mike.
Your
notes,
Sylvan,
speak
by
notes
on
the
hack
bad
this
time
around
all.
E
C
C
E
C
A
I
guess
I
guess
it's:
we
need
to
find
a
good
balance,
and
since
we
are
trying
to
move
to
making
releases
very
frequently,
then
having
the
which
means
the
release
process
needs
to
be
simple
enough
to
make
a
very
low
overhead
how
to
find
a
way
to
make
a
quick
announcement
as
part
of
that
that
is
sufficient
to
get
the
message
out,
but
that
doesn't
become
a
big
burden
of
like
well.
The
release
is
five
minutes,
but
I
have
to
spend
three
hours.
Writing
a
blog,
a
big
blog
post
about
it.
E
Yeah
I
think
mean,
did
release
I,
don't
remember
which
one
one
of
the
Jupiter
Kyon's
or
or
something
like
that,
which
also
is
still
eat
a
small
one
grand
earlier
that
you
want
to
get
43
soon-ish
when
it's
ready
and
I
want
to
get
Mike
to
release
and
be
convert
five
in
a
bíblia
Mon
sesh
time
to
polish
some
issues
and
have
Micro
through
the
release
process.
At
someone
who
is
new
to
the
reeds
process
goes
through
the
notes
and
say:
hey
this
I
don't
understand.
This
is
not
clear
and
ultimate.
A
A
C
C
A
Updates
to
share
at
the
fine
thanks,
oh
cool,
thank
you
Anna,
just
from
reading
from
the
chat
since
Mike
and
Sylvan
are
both
having
audio
problems.
Mike
mentioned
that
he
was
at
a
conference
at
cox
I,
and
there
was
there
were
good
potential
collaborations
about
the
notebook
and
publication
issue
that
he's
going
to
be
working
on
so
great
thanks
for
letting
us
know,
Mike
and
Sylvan
did
bring
something
up
Nick.
This
might
be
perhaps
for
you
or
I
I,
think
from
the
team
year.
A
Maybe
one
of
the
more
connected
to
anaconda,
but
Sylvan
was
bringing
up
that
in
the
latest
anaconda
release.
The
version
of
I
phi
widgets
that
got
included
is
really
really
old
and
I.
We
don't
know
if
that
was
an
oversight
or
an
accident,
but
it
might
be
if,
if
you
can
look
into
it
or
talk
to
Sylvan
and
find
out
what's
going
on
because.
A
A
D
Yeah
I
believe
it
was
an
oversight
that
it
is
is
just
those
three
or
four
winner,
because
we
had
discussed
having
widgets
in
there,
but
I
mean
the
other
path
forward.
Is
that
we
can
actually
use
build
time,
config
files
that
are
in
a
predictable
location
and
have
them
loaded?
That's
you
know,
that's
really
what
we
that's,
what
anaconda
needs
right
we
had.
We
had.
We
had
done
all
that
work
around
making
stuff
work
for
Conda,
and
we
hadn't
taken
anaconda
into
account.