►
From YouTube: IPython/Jupyter Dev Meeting, June 28, 2016
Description
Meeting of the IPython/Jupyter development team.
Meeting Notes: https://jupyter.hackpad.com/June-2016-Q7Kx6WRqYKg
B
B
A
major
industry
11
comment
about
Peter
stuff
is
that
the
the
pr
about
dashboards,
I,
I,
started.
Commenting
and
I
have
another
round
of
comments
in
half
finished
in
an
open,
github
tab,
but
but
it
would
be
yeah
if
anybody
else
has
has
comments
on
the
dashboard
work,
it
would
be
just
a
reminder
that
that
that
that
graduation
proposal
is
is
open,
bye,
bye,
Peter
and
Gino
and
their
team,
and
so
it
would
be
good
to
have
feedback
from
others
on
on
that
I.
B
Don't
know
if,
if
anything
has
come
up
interesting
there
for
you
Peter
any
any
substantial
changes
that
you've
seen.
I
have
a
few
things
on,
but
it's
mostly
on
the
structure
of
the
repo
that
I
think
would
be
good
to
do
before
before
we
merge
it,
but
otherwise
I'm
pretty
happy
with
the
work
itself.
Has
there
been
any
anything
that
has
elicited
kind
of
major
changes
for
you
on
the
technical
side
as.
B
C
Ya
know:
I
love
nothing
there
yet,
like
you,
like,
you,
said
I
think
you're
the
main
commenter
so
far,
so
just
waiting
for
feedback
I
know
we
just
put
it
out
so
as
it
comes
in
will
definitely
address
it.
I
think
you
know
taking
the
colonel
gateway
as
an
example.
We
after
I
graduated
we
wet
and
actually
created
to
read
the
dock
site
with
Carol's
help,
and
you
don't
cleaned
up
a
lot
of
the
dock
strings
and
things
like
that.
So
I,
don't
doubt
Allah!
That's
gonna
happen
here
too.
C
B
Okay,
well,
I
mean,
if
there's
some
of
some
of
that
work
is
article
work,
but
that
we
want
to
do.
For
example,
one
of
my
comments
was
actually
going
to
be
that
it
would
be
good
to
have
an
actual
doc,
even
if
it's
not
visible
and
read
the
docs
right
away
but
beginning
to
put
a
stings
build
in
place
and
a
proper
docs
directory
and
I
think
we
want
to
encourage
projects
to
begin
building
documentation
as
part
of
the
development
process,
not
as
something
that
happens
much
later.
B
C
Yeah
and
don't
get
me
wrong,
you
know
if
we
need
to
do
that
before
the
pr
goes
in,
for
you
know,
saying
it's
accepted
or
not
no
problem
right,
I
knew
that
was
gonna
be
on
the
radar
right
away
is
given
that
get
all
the
other
Jupiter
projects
have.
It
will
probably
have
to
work
with
Carol
about
what
it
means
to
write
a
you
know,
user-facing
doc
for
an
extension,
I'm,
not
sure,
that's
a
whole
read
the
doc
site
or
something,
but
it's
interesting
new
case
I,
guess
yeah.
C
E
F
D
G
We
had
discussions
with
John
on
the
theme
some
time
ago
and
we
were
saying
that
when
people
go
to
read
the
docs,
they
expect
to
see
the
read
the
docs
team,
even
though
we
may
need
actually
to
add
some
things
for
the
widgets
to
work
in
the
read
the
docs
and
all
and
in
the
visual
aspect,
should
probably
what
people
see
usually
on
with
the
docks
and
the
Jupiter
theme
will
be
a
better
fit
for
self-esteem
pigmentation
on
the
Jupiter
website.
A.
G
Help
but
the
dancing,
it's
awesome,
it's
something
that
a
lot
of
people
work
on
and
fix
on
a
daily
basis,
and
it
works
great
on
multiple
platforms,
a
mobile
device.
We
I,
don't
think
we
have
the
cycles
to
do
something
that
he
is
clearly
better
than
what
they
have
I
mean.
They
are
doing
a
really
good
job
already
and
so.
B
B
E
Mean
I
I
don't
have
any
go
ahead.
Carl
I
was
going
to
say
this
needs
to
be
a
separate
discussion.
I,
don't
think
we're
gonna
resolve
it
here.
I
think
Brian
needs
to
be
part
of
the
discussion
and
he's
not
here.
I
think
what
we
have
is
what
we
have
now
if
we
want
to
go
back
and
do
Jupiter
/
Jupiter
as
a
read,
the
docs
theme
I'm
cool
with
that.
But
you
know
it's
really
not
my
decision
solely
to
make
and
I
need
somebody
who
has
the
authority
to
say
hey.
G
There's
a
technical
thing
here
that
is
that,
even
if
we
do
decide
to
go
with
a
ridah
duck
theme,
we
will
actually
need
to
fork
it
for
certain
features
that
we
added
so
would
be.
Essentially
the
radio
ducks
plus
tweaks
and
all
but
can
read
the
docs
works
great
on.
Even
my
you
know,
android
phone
and
it's
not
the
case
of
their
currency.
So
do
we
have
the
cycles
for
this?
We.
D
B
Okay
but
I
think
as
as
Carol
said,
we're
probably
not
going
to
reach
a
conclusion
on
this.
So
one
question
is,
it
seems,
like
we
have
folks
like
Sylvan,
who
have
looked
into
this
and
my
ts,
aunt,
Carol
and
myself,
and
very
interested
and
exercised
about
the
quality
of
our
documentation.
So
should
we
try,
should
we
try
and
should
we
open
an
issue
about
this
I
think.
D
B
Yeah,
but
as
an
action
item,
because
we're
not
gonna
have
this.
This
whole
discussion
right
here,
let's
open,
let's
open
an
issue
on
on
on
on
on
which
we
PO
I,
guess
it
would
probably
be
the
Jupiter
Jupiter
one
which
is
kind
of
a
apparent
one,
may
be
summarizing
these
points,
and
then
the
people
who
are
interested
can
then
try
to
work
on
work
through
on
that
issue
and
that
subset
can.
We
can
try
to
schedule
a
separate
discussion
to
to
reach
to
find
a
solution
so
that
we
don't.
A
H
B
A
It
might
be
useful
for
people
to
just
you
know,
record
and
github
with
the
requirements
what
they
think
the
requirements
of
the
documentation
are.
Maybe
you
guys
went
through
this
before
I
started,
but
it
sounds
to
me
like.
Maybe
the
team
needs
to
normalize
on
on
what
we
want
the
documentation
to
do
technically.
You
know
be
able
to
be
used
on
iphone
all
that
stuff
and
then
also
with
the
content.
B
Even
if
it's
with
a
very
basic
thing
set
up
things
aside,
is
writing
the
basic
content
and
move
forward
with
that,
so
that
folks,
like
Peter,
not
block
and
there's
no
reason
why
Pete
and
Gino
and
their
team
should
be
blocked
on
this
question,
but
at
the
same
time
that
it
doesn't
feel
like
basically
we're
just
applying
all
the
pressure
on
Carol
to
find
a
solution
to
this,
which
is
not
the
case
by
the
way
Carol
just
in
case
that
wasn't
obvious
that
I
I.
Don't
think
that
this
is
your
problem
by
any
means.
Yeah.
A
B
So
I
think
I
was
I
was
next
and
yeah
the
only
thing
to
discuss
really
that
I
think
we're
all
more
or
less
set
for
the
july.
Twenty
second
mini
workshop.
We've
we've
reached
out
to
a
few
people
who
have
had
who
have
done
jupiter
related
Jupiter
hub
related
things,
or
have
mentioned
that
they
have
deployments
at
on
the
mailing
list.
B
I
J
B
G
K
B
Know
actually,
we
talked
about
the
dashboard
one,
but
I'd
forgotten
that,
yes,
the
declarative,
widgets
one
is
also
there.
So
yes,
feedback
from
folks,
and
both
of
those
would
be,
would
be
very
welcome.
Thomas,
your
last
anything
that
you
want
to
bring
bring
up
for
discussion,
questions
participation
from
others,
input
from
others.
Yes,
yeah.
B
L
Yes,
it
was
I
think
our
materials
for
next
year
should
should
definitely
include
sort
of
more
of
her
more
of
an
on-ramp
I
hadn't
hadn't,
really
tweaked
that
some
of
the
some
of
the
participants
like
had
really
never
programmed
before
the
workshop.
So
it
had
one
day
of
an
introductory
Python
and
get
course
like
you
know,
software
carpentry
materials
before
coming
to
us
ahem.
H
B
A
H
B
That's
it
yeah
planning
to
thank
actually
about
Thomas
Thomas,
maybe
maybe
a
short
short
blurb
about
the
NGC
em
workshop
would
be
cool.
To
have
I
mean
it's
kind
of
highlighting
mean
the
newsletter
is
really
about
short
short,
quick
highlights
of
things
to
note,
and
that
was
that
was
a
valuable
educational
usage.
What
do
you
think
sure
when.
H
H
If
you
have
the
time
also
a
blog
post
could
work
if,
if
you
it's
been
awhile
since
we've
posted
anything
to
the
blog,
so
that
it's
off
you
know,
if
you
want
to
keep
it
short
to
a
couple
sentences
and
a
link,
the
newsletter
is
ideal.
If
you
want
to
do
a
larger
right
up,
then
a
blog
post
would
be
great
yeah.
L
H
B
I
was
just
thinking
honor
that
one
thing
that
might
be
cool
to
put
in
the
newsletter
or
active
projects
for
graduation,
because
it's
not
just
us
who
can
provide
feedback
right,
I
mean
anyone
from
the
from
the
broader
community
and
the
newsletter
is
kind
of
a
way
of
messaging
out
to
people
who
may
not
hang
out
on
the
mailing
list,
all
the
time
and
so
mention
just
just
mention
all.
We
have
two
new
projects
ready
for
graduation.
B
B
B
I've
added
gene
peter.
I
added
under
your
heading
arm
a
little
comment
with
the
link,
and
so
it
literally
could
be
as
simple
as
just
a
couple
sentences
and
a
link
to
the
two
PRS
and
tuning
hope.
The
following
two
topics
are
introduced
for
graduation
dashboards
and
federer
widgets
with
one
sentence,
and
that
should
be
enough.
C
H
B
The
work
because
we
want
feedback
right
and
so
and
we
don't
we
linger
to
linger
for
too
long.
So
I
would
say
this
one.
The
UK
workshop
is
less
because
that's
just
reporting
that
something
happened
and
if
the
recant
that
it
had
later,
it's
not
that
big
of
a
deal.
Oh
this
one,
I
would
say
we
wanted
to
go
out
for
people
to
come
back
to
feedback.
G
H
B
There's
we
won't
have
a
link
to
register,
will
just
put
up
the
I
mean
I,
guess
what
we
can
use
is
just
the
link
to
the
link
to
the
hat
to
the
hack
pad
and
we'll
just
post
on
the
Hat
fat
will
update
it
with
the
information
to
join.
We're
not
gonna
have
formal
registration
it.
So
it's
going
to
be
an
online
thing.
Basically
like
one
of
these
calls
open
blue
jeans.
If
you
want
to
join
and
I
want
to
join,
that's
fine
post
it
on
YouTube.