►
From YouTube: IPython/Jupyter Dev Meeting, May 31, 2016
Description
Meeting of the IPython/Jupyter development team.
Notes on hackpad: https://jupyter.hackpad.com/May-2016-UO05nLEADSB
A
Hi
everyone-
this
is
the
May
31st
Jupiter
ipython
that
meeting
and
why
don't
we
start
on
catching
up.
I've
been
away
on
travel
for
a
few
weeks,
so
I've
got
a
lot
of
catching
up
to
do
as
Jamie
mentioned
on
the
half
pad
it
spiked
on.
So
we're
probably
missing
a
few
people,
but
we'll
go
with
who
we
have
and
will
be
the
recording
up.
So
Jamie
do
you
wanna?
Oh
my
god.
I'm
share
data
yeah.
C
C
B
So
yeah
last
week,
I
spent
a
lot
of
time
with
the
data
science
education
program,
and
you
know
they
they
did
a
retrospective.
You
know
that
how
the
last
semester
whence
and
then
how
they
want
the
next
semester
to
go
so
the
fall
semester.
So
there's
some
notes
up
in
a
Jupiter
shared
draw
a
document
drive
on
Google,
Drive
or
folder
that
kind
of
puts
board
their
goals
for
the
next.
B
So
you
know,
I
think
there
are
a
few
instructors
there
and
they
just
like
it
to
go
a
little
bit
more
smoothly
with
fewer
surprises,
and
some
of
that
has
to
do
with
just
how
that
course
is
laid
out
and
also
with
some
of
the
technology.
So
I'm
working
with
men
and
her
nato
and
elaine,
and
some
other
folks
on
the
g
sep
team
to
help
with
that
forward,
though
I
think
the
semester
is
going
to
come
very
quickly.
Yeah.
D
B
I
want
to
stay
on
top
of
that,
make
sure
they're
ready
to
go
the
gates
so-
and
that
was
my
first
point
so
continue
to
work
through
the
roadmap
and
clarify
some
items
with
some
team
members,
so
I'd
reached
out
to
some
folks
on
the
team
just
to
clarify
some
of
the
differences
I
found
between
the
hack
pad
notes
from
the
dev
meeting
and
the
roadmap
that
we
haven't
github.
So
that's
that's.
Processing,
don't
work
in
that
statement
of
work
for
the
tech
writer
attended.
A
really
cool
talk
last
week.
B
Combine
that
rockland
eat
stuff,
I,
also
a
debrief
with
Jess
about
greater
before
she
left
so
I
have
a
really
good
set
of
notes
of
where
and
we
greater
is
what
the
plans
are
more
moving
that
forward
and
the
d-sub
hopes
were
asking
about
Emma
greater,
so
those
are
good
to
have
John
output
doesn't
a
shared
location,
no
real
blockers.
You
know,
except
the
learning
curve,
so
hunt
is
keeping
on
going.
I
watch
men
I
want
to
talk
on
Jupiter
hub
from
from
PI
data,
so
that
was
cool
yeah.
A
Right
on
a
quick
question,
I
was
I
was
wondering,
if
are
there
parts
of
the
discussion
with
data
science,
education,
folks
that
we
can
put
in
a
more
public
location,
whether
it's
kind
of
a
public
iPad
or
something
that
is
not
because
Google
Drive
tends
to
be
more
per
sort
of
time.
I
quasi-private
see
ya
and
so
are
there,
and
there
maybe
notes
that
they
took
care
that
they
they
consider
to
be
part
of
what
they're
doing
in
Brooklyn.
A
D
B
A
A
Anything
else
or
any
other
questions
for
Jamie
from
anyone
is
anyone
else
from
who's
in
the
meeting
kind
of
involved
or
has
any
other
feedback
from
kind
of
educational,
Jupiter
hub
deployments
that
that
you
can
relate
to
us
I
think
right.
Today
we
have
most
of
the
post
or
comment
one
of
the
industry
side,
but
you
may
have
heard
anyone
have
anything
on
that.
One:
okay,
I
Ok,
Go
hoarding.
E
Yeah
mostly
been
I've,
it's
been
a
bit
of
a
busy
month
or
so
with
a
Phoenix
conference
here
in
our
way
and
by
data
and
stuff,
and
a
working
on
some
grant
proposal
stuff
and
but
I.
All
of
that
is
behind
me.
Now
it's
on
back
full
on
into
the
uber
hub
stuff.
We
talked
about
at
the
dev
meeting
and
I've
merged
some
new
authentication
stuff
and
I'm
charging
head
there
to
make
it
using
an
be
greater
and
stuff
is
kind
of
the
conical
example
of
the
thing
to
make
easier.
E
The
main
things
that
are
kind
of
four
other
people
are
your
site
by
stuff
is
due
friday.
So
if
we
want
to
do
something
or
euro
site
by
I've
got
to
the
folks,
here
are
going
to
do
a
poster
on
NB
dime
stuff.
But
if
we
want
to
do
a
tutorial,
Clemson
I
can
figure
out.
If
there's
something
we
want
to
do,
I,
don't
I,
don't
know
if
we
want
to
do
something
because
I
feel,
like
I've
kind
of
done,
a
presentation
on
on
every
aspect
of
stuff.
E
Oh,
it
not
past
six
or
nine
months,
but
your
site
by
is
a
bit
of
a
different
audience,
so
maybe
repeating
something
in
super
frio
figuring
out
what
what,
if
anything,
will
definitely
go
regardless
of
whether
we
present
anything.
But
if
there's
something
that
we
think
should
get
presented
as
a
talker
tutorial
or
you.
E
Don't
know
I
guess
we
could
do
just
kind
of
a
state
of
things.
What's
coming
kind
of
talk
or
we
could
do
our.
You
know
I
python,
that
kind
of
tutorial
having
just
done
the
Royal
tutorial
at
Syfy
in
July
and
Jupiter
hub
tutorial
and
various
things
in
the
last
few
months.
I
guess
we
haven't
done.
I
buy
some
dips
in
olive
oil,
although
other
people
have
you
know
what.
F
A
The
web
console
as
a
replacement
for
the
QT
console
sort
of
the
laying
out
the
state
of
that
of
that
system
and
and
that
things
are
coming
from
this
front
and
and
maybe
also
highlighting
some
of
the
the
dashboarding
stuff
from
peter
and
his
team,
if
they're,
okay
with
that,
but
that
you
can
speak
for
them,
but
but
I
think
there's
some
good
stuff
there.
Thank
you
welcome
at.
F
E
A
Actually,
that
that'll
be
a
good
thing
for,
for
you
to
kind
of
get
get
it
close
to
loot
into
the
release
process
so
that
that
we
can
begin
to
and
I've
put
some
of
that
on
your
plate
gradually
and
see
what
about
to
be
automated
and
can
be
or
semi-automated
them
to
pull
by.
You
can
I
think
that
would
be
its
kind
of
a
good
choke
point
at
the
top
level
of
the
project,
pretty
well
for
you
to
tackle
the
chokin,
because
that's
one
thing
that
tends
to
kind
of
clogged
everyone
quite
a
bit.
Okay,.
B
E
Main
thing
that's
very
different
now
than
when
it
was
monolithic,
is
that
for
most
repos
a
release
is
not
a
big
deal
that
it's
just
we've
got
a
few
things
merged
it's
time
to
cut
a
release.
It
takes
an
hour
and
it's
it's
a
it's
a
small
thing,
the
notebook
repo
and
the
ipython
rapport,
of
course
significant
exceptions
to
that.
But
for
a
lot
of
the
small
ones,
I
with
the
number
of
packages
we
have
right
now,
we
should
probably
be
doing
a
release
of
something
every
week.
A
And
that's
good
for
you
come
get
into
that
group.
Oh
I,
don't
know
if
we
want
to
do
a
little
bit
of
a
release
party
min
with
you
and
Jamie,
and-
and
I
am
happy
to
help
as
well
with
so
that
we
transfer-
I
mean
I'm
thinking
of
transferring
some
of
that
knowledge,
not
necessarily
ace
asking
that
that
you
pick
it
up
on.
Quite
up
for
that
that
you
can
get
involved
with
the
process
in.
A
G
E
E
G
E
A
A
E
A
A
Product
I
mean,
even
if
we
don't
sample
that
densely
at
least
a
few
of
the
key
things,
and
a
few
tests
that
potentially
highlight
integration
points
right
tests,
where
it's
not
just
a
unit
test
on
this
thing
happens
to
call
that,
while
we
get
lucky
that
we
test
that
dependency,
but
rather
having
tests
that
explicitly
write,
it
kind
of
check
that
check
for
actual
integration.
We
we
have
never
really
done
that.
Yeah.
H
And
we're
kind
of
starting
to
move
towards
that
for
the
extensions
that
we
want
to
ship
as
part
of
anaconda.
We,
we
are
definitely
going
to
have
to
make
sure
that
everybody
is
in.
You
know,
trying
to
put
menu
items
in
and
child
one
and
then
expect
for
that
to
be
the
right
thing.
So
that's
going
to
be
pretty
interesting,
but
you
know
that
is
continuing
work.
A
G
G
E
A
G
E
A
Okay,
so
that
means
the
the
plan
for
trade.
Wets
is
more
of
stolen,
doing
a
little
bit
of
testing
and
reviewing
and
then
letting
us
know
when
we
cut
a
beta
to
try
and
try
to
elicit
feedback
from
the
public
on
that
beta.
That's
one
more
one:
it
is
the
few
weeks
cycle
of
data
before
we
do
the
release.
Okay,
right,
okay,.
I
I
93
that
you
have
with
cluster
okay
cool
yeah
and
you
can
already
test
it.
I
put
it
in
my
own
personal
heater
pages
that
before
wasn't
using.
So
if
just
among
the
people
who
are
here,
the
meeting
you've
already
has
a
variety
of
browsers.
So
if
you
want
to
check
it
out,
click
on
the
link
that
are
provided
and
if
you
broke
normally,
there
is
a
widgets
tab
e
on
the
web
page
so
that
you
can
see
whether
the
digits
display
another.
A
I
I
I
D
A
This
is
exactly
this
is
exactly
the
kind
of
thing
that
we
want.
I
think
he
was
inspired
by
other
widget,
so
galleries.
It's
part,
of
course,
I
mean
we've
looked
at
these
I
remember
a
while
back
looking
looking
at
other
other
galleries
and
saying
we,
we
need
something
like
this,
so
I
can't
I
can't
thank
you
enough.
Now.
The
sweetie.
I
Alright,
very
cool,
very
cool,
and
so
the
other
thing
is
I,
be
talking
I
be
presenting
a
tutorial
at
PI
data.
Paris,
maybe
put
a
freeze
on
how
to
create
a
custom
multi-step
very
trying
to
engage
more
people
into
this.
So
I
tried
creating
an
entry
on
the
Jupiter
calendar,
but
we
perform
that.
I
got
and
didn't
seem
to
work.
So
maybe
it's
something
wrong,
but
I
don't
speed
appearing
of
the
Canada.
Oh,
the
v,
canada
seems
to
be
completely
empty.
Yeah.
I
B
D
A
I
There
you
see
some
review
right
here.
Probably
but
I
mean
it's
it's
decent
enough
to
be.
There
I
think
at
this
point,
but
I'm
sure
that
I
haven't
tested
and
all
the
mobile
browsers
and
stuff
like
that.
So
if
there
are
the
people
who
are
more
proficient
with
the
boot
rather
than
I,
am
it's
the
time
to
look
at
it.
A
F
G
A
A
I
A
Too
far
from
the
microphone,
ok,
so
I'm
not
we
were
just
saying
that
camera
and
the
camera
is
a
bit
bottlenecked
on
a
few
other
things
as
well.
So
we
won't
let
this
one
linger
for
too
long.
If
he
has
the
cycles,
I
mean
it
looks
great.
It
may
not
be
perfect,
but
let's
not
have
perfectly
the
enemy
of
the
good.
This
is
good,
so
it
can
become
perfect
later
down
the
road
he.
B
A
Is
it
what
to
do
with
the
defect
which
it
we
want
to
do
a
map
Jupiter
hub
deployments
and
educational
Jupiter
deployments,
so
that
we
could
have
an
interactive
map
kind
of
like
the
sage
map
of
developers
like
a
little,
an
interactive
map
where
you,
where
you
can
go
and
see
information
about
both
courses
based
on
Jupiter
and
existing
public
deployments,
or
semi-public
appointments
or
jibri
hub?
So
so,
then,
you
get
open
in
some
cases.
Five.
I
Minute
stuff,
with
a
defect
budget,
you
can
create
a
markers
on
the
map
with
the
locations
of
deployments,
and
we
also
have
a
PR
with
a
that
implements
a
puppet.
You
know
the
leaflet
pop
up,
so
that
in
which
you
can
put
any
other
widget,
you
want
I
damage
it
and
it
should
be.
You
should
work
with
the
study
projects
more
money,
so
it
should
be
too
hot.
Okay,.
A
Cool
yeah
that'll
be
great,
basically
having
having
the
markers,
probably
two
types
of
markers
like
horses
and
hub
with
two
different
colors
and
then,
when
you
hover
clicker
or
something
on
a
marker,
then
you
get
a
little
pop-up
sheet
with
a
teeny
amount
of
information.
Maybe
a
contact
person
or
something
like
that
means
very
basic,
but
I
think
would
be
nice
to
have
that
on
the
other
website.
/,
don't
you
said
you
said
that
that
depends
on
you
have
a
PR
against
type
I
leaflet.
I
A
I
Appear
against
iPad
afraid
that
at
the
pop-up,
like
the
function,
button
he's
a
French
92
of
leaflets
and
it
was
not
wrapped
in
iPad
effect
and
I
was
adding
it
because
we
wanted
to
use
it
for
the
base
hack
here
the
time
and
we
couldn't
because
it
wasn't
there
and
I,
did
ninety
percent
of
the
work
during
the
act
and
did
not
include
it
eventually.
So
it's
there
it's
hanging
there
and
I
can
a
curate.
If
you
need
it's
very
simple:
okay,.
A
I
Hey
I've
got
the
questions.
Are
they
in
fact,
in
the
room
for
a
lot
of
the
widget
libraries?
Is
that
a
lot
of
them
are
actually
need
to
have
some
sort
of
resize
event
so
because
to
be
able
to
relay
out
so
the
mathematical
just
needs
it.
The
block
bhujette
needs
it
for
we
completely
review
review
box
and
the
leaflet
who
just
needs
it
to
compute
the
tires
that
have
to
be
downloaded
so
but
I
mean
I.
I
K
So,
rather
than
the
anecdotal
point
to
that,
is
that
the
original
impetus
originally
very
near
two
years
ago,
when
I
first
started,
phosphor
was
because
there
were
no
resize
events
at
the
dom
and
we
needed
those,
and
so
that
was
basically
that
whole
concept
was
the
genesis
genesis
of
what
brought
phosphor
into
what
it
is
today
was
like
the
need
for
that,
and
as
soon
as
you
need
something
like
that,
it
kind
of
ends
up
infected.
Your
entire
widget
hierarchy
is
sloping.
Is
now
discovering
some
yeah.
F
So
right
now
we
have
a
right
now.
The
widgets
essentially
are
producing
Dom
elements,
backbone
view
classes
that
essentially
your
Dom
elements
with
a
bunch
of
stuff
attached
to
them
as
an
object,
and
then
we
wrap
those
in
phosphorus.
So
there's
only
phosphor
at
the
very
top
level
when
we're
using
it
in
a
phosphor,
notebook
and
I.
Think
what
you're
suggesting
is
we
sort
of
merge?
The
first
review,
the
bagman
view
is
a
meaningful
for
widget,
so
we
make
all
widgets
phosphor
widgets
and
make
the
whole
phosphor
hierarchy
anytime.
F
You
anytime,
you
include
a
widget
anywhere
in
a
page,
will
be
a
phosphor
hierarchy
and
if
it's
embedded
into
a
phosphor
page,
then
resize
events
will
trickle
down
from
the
entire
page
another
other
than
that.
Then
you'll
have
to
trigger
the
top-level
widget.
It's
a
phosphor
alamat.
You
have
to
tell
it
when
it
should
think
that
there's
a
resize
so
when
the
window
resizes
or
something
I
got
and
then
it'll
trickle
up
and
down
the
hierarchy
of
your
small
little
group
of
widgets
I.
Think
that's
what
you
were
yeah.
I
That's
the
that's
the
issue,
because
when
you
use
CSS
layout
you
don't
get
the
resize
events
that
you
want
and
I
mean
you
can
use
a
photonic
anism
ucss.
They
are,
but
the
current
ones
that
you're
using
a
power
just
will
move
out
of
the
box
and,
for
example,
the
simplest
one
is
a
marketing
budget
which
is
essentially
a
PNG,
and
you
need
to
recompute
the
PNG
and
resize
too
and
yeah.
So
we
need
an
event
to
trigger
that.
F
G
A
Yeah
I
have
I,
have
pain,
I
haven't,
dug
it
up
into
these
things,
to
really
have
an
opinion.
So
most
with
informing
myself
at
this
point
and
and
I
guess,
I
guess,
the
question
will
be
will
be
a
look
at
what
what
dependency
chain
that
triggers
for
widgets
in
terms
of
in
terms
of
deployment
and
just
really
depends
in
football.
At
the
moment,
yeah.
F
F
F
Think
you
said,
I
was
next
for
NATO.
Nothing
to
discuss
just
FYI,
Steve
and
I
are
working
a
lot
on
the
Jupiter
lab
notebook
architecture
and
I
think
we'll
be
rolling
out,
essentially
a
huge
update.
That
includes
all
these
updates
for
the
architecture
this
week
so
on.
So
so
that's
when
I'll
update
the
server
extension
and
book
at
people
contestant.
A
F
I
F
M
In
the
notes
not
really
think
to
discuss
so
much
as
when,
when
Stephen
Jason
do
push
out
the
new
notebook
architecture,
it's
going
to
have
console
in
it
too.
So
I'd
really
appreciate
people
playing
with
it.
That's
it
there's
there's
our
there's
already
some
bugs
and
I'm
looking
at
that
and
I'll
be
resolving
those
but
beyond
just
bugs
usability
and
what
you
would
hope
to
see
what
you
hope
to
expect
or
more
useful
things
that
I
can't
really
arrived
at
on
my
own.
Some
more
data
would
be
great,
so
so
this.
A
Is
this
is
going
to
be
also
rolled
into
into
the
server
extension
it'll
become
available
as
part
of
a
server
extension,
so
that
we
can
tell
people
I'm
sort
of
thinking
of
how
we're
going
to
get
testing
beyond
the
people
who
are
willing
to
run
off
master
of
everything
like
we
do?
And
since
the
idea
would
be
to
be
able
to
roll
this
this
out
as
a
as
a
as
a
server
extension
that
we
can
even
micro
release
in
alpha
mode?
A
D
Actually
steep,
but
we're
going
to
down
a
second
I
guess:
I'll,
just
hop
in
there
piggyback
on
what
they
just
said.
Yes,
I
we've
been
working
on
the
plumbing
of
the
architecture
of
documents
and
kernels
and
execution
state
in
in
the
super
lab
application,
consolidating
that,
through
all
the
different
you
repose,
that
we
have
and
that's
an
next
plan
I'll
get
to.
D
But
as
it
stands
right
now,
I
just
completed
the
plugin
that
will
allow
you
to
launch
a
console
with
your
desired
colonel
arm
and
brings
up
a
tab
in
the
Jupiter
lab
environment,
launches
the
console
and
you're
off
and
running,
so
that
is
working
just
at
the
start
of
this
meeting,
so
that
will
be
included
in
the
next
release.
Along
with
adding
thanks
to
Darien's
completion
widget,
we
now
have
completion
in
the
notebook.
D
It's
a
couple
bugs
associated
with
that,
but
working
on
that
to
my
point
about
the
number
of
repose
that
we
have
there's
been
a
lot
of
confusion,
even
amongst
the
members
of
the
team
as
to
what
the
parts
of
Jupiter
lab
are.
Where
issues
to
go.
My
thought
is
that
anything
anything
you
I
related
is
is
the
line.
So,
basically,
we
have
do
purchasing
tools
and
services
that
are
used.
D
Services
as
uses
in
other
contexts
by,
like
the
colonel
gateway,
interact,
uses
it,
but
the
things
like
dick
jsui,
Jupiter,
Jace
notebook
and
cheaper
jets,
plugins
I
recommend
those
all
just
become
whatever
we're
going
to
call
it
cooper,
/,
jupiter
lab,
and
that
includes
this
server
extension,
so
that
there's
only
one
place
when
you're
talking
about
duper
lab
visible
things
that
you
go.
I.
A
A
I
think
it
even
if
it
creates
a
little
bit
of
additional
coupling
and
even
if
things
you
do
carry
a
little
bit
more
flying
around
I
think
the
too
many
repos
begins
creating
from
micromanagement
overhead
that
hurts
everyone
in
the
long
run,
so
I'm
I'm,
very
much
in
favor,
but
but
I,
don't
know
enough
of
the
details
to
saved
in
this
particular
case,
there's
a
there's,
a
good
reason
to
keep
it
that
way.
I
I
lean
in
your
direction.
A
Okay,
so
the
plan
would
be
you
are
you
thinking
of
basically
over
the
next
over
the
course
of
before
you
put
a
release
of
this
consolidating
the
repos?
Is
that
would
you
because
I
was
at
it
at
that?
We
want
to
plan
a
little
bit
for
and
just
make
sure
that
everybody
everybody's
on
the
same
page
forget.
A
D
A
A
Okay,
so
the
main
thing
I
wanted
to
discuss
is
the
idea
that
we've
been
kicking
around
after
multiple
meetings
that
have
been
involved
with
over
the
last
few
weeks
about
having
an
online-only
mini
workshop
about
Jupiter,
hub
and
Jupiter
hub
deployments
and
use
cases
and
whatnot
we're
getting
hit
really
by
too
many
people
with
these
needs,
and
so
I
wanted
to
know.
Basically
just
mentioned
the
idea
to
the
whole
team
just
to
know
now,
but
who's
interested
in
participating
in
something
like
that.
I
think
it's
something
that
we
would
schedule
in
the
morning.
A
West
Coast
ish
like
nine
to
noon
so
that
mean
and
those
in
New
York
can
join
at
least
in
the
in
the
evening
and
not
at
a
reasonable
hour
and
we'll
work
with
an
ax
to
coordinate
a
good
date
for
the
community
poll
who's
interested
in
joining.
My
idea
would
be
to
do
basically
because
we
want
this
to
be
something
that
anyone
can
follow
and
potentially
were.
The
public
can
ask
questions.
I
was
thinking
of
doing,
even
though
we're
not
thrilled
about
Google
Hangouts,
but
for
this
one
time
actually
do
it.
A
A
My
intent
is
really
to
give
people
out
in
the
world
or
coming
and
asking
us
these
questions
about
your
hot
deployment,
a
quick
view
of
the
various
scenarios
and
use
cases
and
how
you
put
together
the
various
pieces
of
the
puzzle,
depending
on
what
you're
trying
to
do,
because
there's
no
one
right
answer
depends
a
lot
of
what
people
are
doing
and
for
us
to
learn
from
those
people.
What
are
the
water
key
pain
points
that
we
may
not
have
already
identified?
I
mean
some
of
them.
A
E
A
A
Yeah
allergan,
okay,
if
you
can
spare
a
clone,
then
we
will
work
with
your
with
your
schedule.
Whatever
it
takes,
hey
and
I
only
have
a
quick
question.
What
are
we
for
Jupiter
lab?
This
is
something
I
forgot
to
ask
on
Friday
folks?
What
are
we,
what
is
going
to
be
the
workflow
for
now
that
we're
really
starting
to
get
more
and
more
feedback
for
tracking
feature
parity?
There
was
that
issue
that
Jason
had
opened
a
while
back.
That
would
like
the
future
parity
issue
as
a
single
issue.
A
M
M
If
the
issue
is
closed
already
and
the
PR
has
been
merged
in
the
assumption-
is
that
we
think
we're
close
to
parody,
if
not
actually
have
it,
then
that
might
require
a
separate
issue,
because
it
might
just
be
an
oversight
or
might
be
above.
So
my
suggestion
is
the
open
issues
there
aren't
that
many,
it's
not
like
a
massive
list
and
you'll
even
be
able
to
see
long,
and
these
are
all
right
right
now.
Sorry.
M
This
is
this
is
where
what
staples
talk
about
comes
in
yeah,
it's
hard
to
know.
What's
what,
unless
you
are
already
familiar
but
yeah,
so
I
think
I
think
this
will
be
a
lot
easier
when
the
when
the
crunch
happens,
and
we
have
one
repo
I,
don't
really
have
a
great
suggestion
for
right
at
this
moment,
but
at
least
you
have
a
solution
for
you
can.
F
Open
them
up
on
Jupiter
Jays
notebook
for
now,
but
hopefully
the
crunch
happens
soon
and
then
we'll
have
a
Jupiter
lab
repo
will
rename
it
to
Jupiter,
lamb
and
and
then
there'll,
be
one
place
to
open
up
issues.
I
think
opening
up
one
issue,
/
major
item,
thanks
a
lot
of
sense,
if
you
have
a
bunch
of
small
items
that
are
all
sort
of
related,
it's
nice
to
keep
the
issue
countdown,
but
I
think
it's
fine
to
track
things
and
separate
issues
instead
of
having
one
huge
main
issue.
Ok,.
A
D
M
If
it's
a,
if
it's
a
notebook
or
a
council
thing?
Yes,
if
it's
all
the
other
plumbing
that
holds
it
together,
then
that's
pretty
JS
plugins
and
no
other
border.
If
you
might
know,
because
don't
really
have
those
well,
we
have
visual
components
that
people
will
be
able
able
to
identify.
Those
are
those
are
building
blocks,
not
actual
pieces
of
functionality.
So
might
still
be
the
case
that
they'll
go
on
plugins,
I,
think
oh
yeah,
but
yeah,
but.
A
Clearer
answer:
this
is
the
product
typical
example
of
why
the
explosion
of
repose
creates
some
difficulties,
especially
for
users
who
are
not
or
folks
who
are
not
like,
really
really
deep
in
the
weeds
of
what
every
line
of
code
and
they're
given
them
products.
But,
okay,
well,
we'll
do
we'll
deal
this.
This
gives
us
enough
to
go
on,
but,
yes
so
sure
so.
G
50,
as
only
seven
issue
open
and
already
for
PRS
I'm,
not
counting
dogs,
that
need
to
be
updated
and
the
blog
post
to
be
written
and
so
I'm
hoping
to
make
avatar
really
soon
and
I
will
think
personally
people
to
know
if
you're,
okay
with
a
longtime
support
schedule,
and
so
the
question
is:
if
we
do
a
50
soon,
do
we
do
a
4.3?
And
if
yes,
do
we
do
it
after
of
the
450.
A
Come
on
come
on
yeah
on
that
on
the
on
the
testing
stuff,
I
think,
if
part
of
the
reason
why
we
made
all
of
those
tests
optionals,
because
the
ecosystem
for
dependency
management
10
years
ago
was
a
what
is
a
disaster
and
so
requiring
any
of
that
whole
just
impossible,
but
I
think
if,
if
it's
viable
to
assume
that
these
things
are
available,
I,
I
think
that's.
That's!
That's!.
G
G
A
E
A
E
G
G
Because
my
type
is
generally
a
place
where
you
can
tell
people
that
it's
there,
it
will
install,
it
will
upgrade
to
attend
to
the
birds,
and
you
can
just
print
on
that
because,
like
five
dot
Oh
with
DVD,
so
you
can
sprint
and
break
things
with
course
and
because
it
says
yes,
I
want
too
long
along
with
a
Korean.
But
if
it's,
if
it
be
enough
time,
yes,
you
can
begin
to
that.
H
And
Nick
I
think
you
get
the
last
word
whoo
all
right
so
had
another
meeting
with
on
last
week,
we
pretty
much
nailed
down
August
13
for
Jupiter
day
Atlanta
2016,
for
setting
up
the
workflow
for
getting
content.
We're
going
to
be
doing
what
the
Mozilla
global
sprint
has
done.
They've
got
a
you
know,
low
barrier,
google
form
to
get
something
proposed,
and
then
they
transform
that
into
an
issue
and
then
we're
going
to
go
beyond
that
and
give
proposers
an
actual
place
within
the
Jupiter
day,
Atlanta
2016
organization.
H
That
will
be
nice
because
then
we
have,
you
know
on-site
get
er
when
we're
there
and
will
you
know,
work
with
folks
at
binder
and
make
sure
that
we've
got
running
stuff
there.
You
know
just
in
previous
it
in
previous
Jupiter
days.
If
you
actually
want
to
get
people
to
wear
their
writing
code
in
the
notebook,
if
you
can
just
dump
them
into
a
blender,
they
can
start
playing
with
stuff
immediately.
That's
that's
a
great
way
to
get
things
going
fast.
H
So
at
the
end
of
that
we
should
have
a
pretty
good
reproducible
approach
for
running
one
of
these
things.
In
as
inclusive
way
as
possible,
that
ends
up
with
some
problem
for
resources
other
than
that,
and
that
and
we're
going
to
take
the
radio
silence
from
from
Fernando
and
Brian
that
there's
nothing
inclusively
wrong
with
our
proposal
about
how
we're
going
to
run
the
structure
of
the
event,
taking
into
account
that
we
want
to.
H
All
these
other
releases
that
are
coming
out
are
going
to
be
exciting
again
the
day
for
the
cutoff
date,
for
that
I
believe
is
jun
16,
so
anything
that
anything
that
drops
before
then
has
a
pretty
good
chance
of
getting
into
the
distribution.
Anything
that
drops
after
that
has
basically
no
chance
of
getting
into
the
distribution,
so
definitely
want
to
make
sure
we
can
assist
in
any
way
and
getting
things
that
people
think
are
really
important
into
that.
Relate
to
that.
H
There's
been
some
talk
over
on
the
feedstock
on
Conda
Forge,
for
the
notebook
which
you
know
will
become
basically
the
way
that
we
build
notebook
and
how
we
want
to
proceed
on
the
testing.
Their
men
raised
some
concerns
about
actually
running
the
JavaScript
tests.
So
if
people
feel
strongly
about
how
we
want
to
be
able
to
do
integration,
testing
on
big
releases
like
that,
that
would
be
a
good
place
to
Chum
it
other
than
that
I'm
pretty
good.