►
From YouTube: Jupyter/IPython Dev Meeting, May 2, 2017
Description
Meeting of the IPython/Jupyter development team, May 2, 2017
Meeting Notes: https://paper.dropbox.com/doc/May-2017-Jupyter-Weekly-Meetings-NaidawTLtrI06iFJzIdwZ
Meeting Archive: http://bit.ly/JupyterTeamMeetings
A
Good
morning,
everyone,
today's
Tuesday
May
2nd.
This
is
the
weekly
Jupiter
def
meeting
and
we'll
start
off
the
meeting
by
looking
at
some
of
our
action
items
from
last
week,
I
should
mention
that
you
can
go
to
the
link
up
in
the
top
header
section,
there's
a
bitly
link
that
will
provide
a
list
of
archived
meeting
notes
from
earlier
this
year
and
soon
we
should
have
our
meeting
notes
that
we've
been
storing
in
hackpad
over
the
tab.
Our
app
bad
meeting
notes
in
there
as
well.
So
great.
Let's
go
down
to
our
action
items.
A
A
A
Next,
we
had
a
goal
for
April,
which
was
to
resolve
50%
of
a
jupiter
notebook
issues,
the
good
ambitious
goal,
I
like
ambitious
goals.
The
target
was
about
270,
open
issues
by
the
end
of
April
and
to
report
on
progress.
There
we
closed
a
little
over
a
hundred
issues
in
April,
which
was
good.
I,
definitely
started
with
the
oldest
issues
that
hadn't
been
commented
on
for
a
while
and
sings
the
originator
of
the
issue
to
see
if
they
were
still
experiencing
the
problem.
A
So
we
closed
about
fifty
issues
through
that
method,
and
then
grants
did
a
number
of
PRS
and
we
call
closed
some
things
that
have
just
been
inactive
for
a
long
time,
making
a
note
on
those
particular
issues
so
we're
going
to
keep
working
on
that
goal.
I
think
it's
a
good
goal
to
have
it's
been.
It
was
a
good
idea
to
go
through
some
of
the
older
stuff
to
see.
You
know
what
we
need
to
to
prioritize
in
the
development
pipeline
and
all
those
issues
that
we
it
looked
like.
A
We
decided
we
needed
to
continue
to
work
on
those
are
in
the
backlog
milestone
in
the
notebook
Rizzo.
There
are
other
milestones
there.
One
is
the
reference
milestone,
so
many
of
those
issues
are
closed
in
the
reference
milestone,
but
they
can
still
be
used
to
to
look
up
questions
and
decisions
on
certain
actions.
There's
also
a
Jupiter
lab,
milestone,
I
believe
those
are
issues
that
that
should
be
solved
in
Jupiter,
lab
and
I.
A
Think
there's
one
other
milestone
in
there
too,
but
the
main
one
for
development
is
the
backlog
milestone
and
within
that
backlog
milestone
you
can
actually
prioritize
issues.
You
can
drag
and
drop
the
issues
in
that
list
and
put
them
in
the
order
that
you'd
like
to
attack
them
in.
So
that
was
fun
and
thanks
grant
for
the
help
on
that
and
anybody
else
do
that.
Pings
well,
I
was
going
through
those
issues.
A
So
next
Jupiter
lab
extension
handling,
underwent
a
major
change
in
the
0.20
relief
there's
the
link
and
they
would
still
like
others
to
go
in
and
kick
the
tires
by.
Writing
extensions.
Vaness
they're,
just
play
extensions
just
to
test
it
out
and
it
looks
like
Matthias,
is
still
looking
for
feedback
on
it
facing
problem
in
implementation
all
right.
Next,
we
have
our
weekly
news
by
organization.
A
So,
let's
see,
of
course,
whenever
I
check
the
number
of
issues
that
we've
been
closing
it
it,
it's
accounts
done
on
a
weekly,
a
rolling
weekly,
a
monthly
basis.
So
every
day
that
passes
the
number
they
go
down.
So
at
the
end
of
April
it
was
a
little
over
100
when
I
checked
yesterday
there
are
about
97
issues
that
were
closed
in
April
and
we
added
around
50.
So
at
some
point
we'll
be
able
to
get
ahead
of
that.
B
And
recently,
with
the
steering
council,
we've
asked
grant
Nestor
to
join
Jason
growl
tonight,
as
the
13
lead
grant
has
done
a
fantastic
job
in
working
on
the
classic
notebook
on
helping
us
get.
The
5-0
version
out
of
that
and
Grant
has
agreed,
so
we're
really
thrilled
to
have
him
joining
us
and
he's
been
working
with
Jamie
a
lot
on
the
helping
us
get
the
issues
on
the
classic
notebook
under
control
and
I.
B
Think
that's
one
of
most
many
steps
that
we'll
be
doing
as
part
of
this
transition
and
I
think
we're
hoping
to
get
as
we
go
through.
Those
issues
get
a
clear
sense
of
what
types
of
things
we'll
still
be
doing
on
the
classic.
Notebooks
are,
you
know,
obviously,
bug
fixes
minor
improvements,
I
think
are
great
and
then
we're
trying
to
sort
through
on
the
bigger
feature
requests
what
things
make
sense
to
do,
both
in
lab
and
classic
notebook,
which
things
make
sense
only
doing
lab
and
I.
B
Suppose
your
could
be
things
that
only
end
up
in
the
classic
notebook
and
so
that
that's
that's
our
vision.
Right
now
for
the
the
team
leads
and
the
team
structure,
I
think
the
thing
to
note
for
the
the
broader
community,
both
of
users
and
our
developers,
is
that
we
have
another
meeting,
another
developer,
meeting
or
team
meeting
on
Friday
mornings
at
9:00
a.m.
B
Pacific
and
our
vision
is
that
would
be
for
both
Jupiter
lab
and
classic
notebook
development
and
so
grants
going
to
start
to
join
that
and
if
there's
topics
that
anyone
wants
to
discuss
about
the
classic
notebook,
we
encourage
you
to
join
that
meeting.
It
tends
to
be
more
technical
discussion
than
this
meeting
in
the
past.
It's
it
has
been
more
focused
on
Jupiter
lab
Jason.
Grout
sometimes
gives
us
updates
on
iPad
widgets
as
it
relates
to
lab
and
notebook
and
overlaps
there.
A
A
A
All
right,
can
you
guys
see
it
and
I
only
see
your
face.
So
can
you
tell
me
if
you
see
the
diagram?
Okay,
thank
you.
So
I
took
the
data
that
you
all
submitted
based
on
this
percent
time,
that
folks
are
working
on
different
sub
projects
within
Jupiter.
So
those
sub
projects
are
the
large
gray
circles
for
Jupiter
lab
and
notebook.
We
have
the
larger
team
with
Jason
Brian
and
grant,
as
leads
and
so
they're
in
orange,
and
then
for
the
folks
who
are
working
mostly
folks,
mostly
full-time
on
those
projects.
A
Those
are
in
the
lighter
gray,
color
and
then
the
white.
Those
are
folks
who
are
working
mostly
part-time
on
those
areas
and
then
I
use
thickness
of
the
line
around
each
of
the
smaller
circles
to
indicate
the
number
of
project
areas
that
folks
were
working
on.
So,
if
you're
on
a
team
with
somebody
who
has
a
really
thick
circle
around
around
their
their
circle,
it
means
they're
working
on
a
number
of
teams.
A
So
you
know
definitely
give
them
some
slack
if
they're
they're
getting
crushed
by
the
multiple
projects,
they're
working
on
and
that's
really
mostly
mint
state
goods
event
and
then
folks
are
working
on
five
to
seven
project
areas.
Those
have
the
medium
thickness
in
their
line
and
that
lesson
point
five
is
just
a
regular
line
and
nothing
wrong
with
working
on
lesson.
Five,
it's
great
to
be
able
to
focus
on
on
something
and
live
it
through
the
pipeline.
A
A
So
we
would
love
to
automate
this
particular
diagram
in
some
way.
So,
as
you
know,
folks
change
their
focus
across
the
projects,
it
would
be
great
to
be
able
to
face
a
data
and
have
a
diagram
reflect
that
the
data.
So
one
of
the
things
that
that
we
talked
about
is
doing
some
sort
of
design
competition
for
our
communities
where
we
would
put
the
percentages.
A
A
That's
where
we're
we'd
like
to
go
once
we
have
just
this
static,
visualization
down
and,
of
course,
before
we
share
it
with
the
community,
we
would
love
feedback
from
the
team,
so
we
get
it
right
before
we
we
share
it
with
the
broader
community,
so
feel
free
to
ask
questions.
You
can
send
me
private
emails
of
you
if
you
want
to,
but
that's
one
thing
that
we
have.
C
A
And
that's
kind
of
such
a
challenge
of
having
a
static
visualization
is
like
I,
have
to
go
in
and
type
in
100%
and
then
take
your
circle
off
of
whatever
and
it'd
be
nice
to
be.
Have
that
automated
so
right
now
we
could
reflect
that
in
the
spreadsheet.
I
could
share
that
spreadsheet
with
folks
and
you
could
update
your
percentages
as
needed,
and
then
we
could
have
a
design
competition
be
announced
and
share
that
spreadsheet
with
with
folks,
and
then
they
could
come
up
with
a
design
that
that
links
to
the
spreadsheet
update
the
visualization.
D
E
E
Think
if
they
did,
they
might
have
had
I,
had
a
question
about
where
to
put
some
particular
work
on
shukur
clients
and
my
pie,
colonel
or
something
and
I
do
know
where
to
put
them
on
the
that
teen
diagram.
But
they're
those
categories
aren't
on
the
the
Dropbox
thing.
I,
don't
know
if
we
want
to
I
still.
A
Anyone
else
feedback
all
right.
So
that's
that's
what
we're
working
on
and,
of
course,
you
know,
have
a
fuller
discussion
at
the
Deaf
meeting
about
it.
When
everybody's
present
it
might
be
actually
more
efficient
to
do
that,
and
let
me
give
all
access
to
on
I
just
got
a
message:
Paul's
join
hey
Paul
and
you
should
have
access
to
the
notes.
Now.
Oh
all,
right,
you're
welcome
ready
one
ain't
next,
so
the
next
section
I
believe
we
do
is.
A
F
I've
just
been
working
on
the
sci-fi
proceedings
getting
so
now,
there's
a
PR
on
the
snipers
using
a
repo
that
will
allow
people
to
submit
notebooks
as
actual
articles.
It
I'm
not
merging
it.
Yes,
because
right
now
it
would
just
be
creating
a
bunch
of
raw
cells
and
then
dumping
in
your
rst
into
those
four
also,
and
that
doesn't
have
much
of
an
advantage
over
writing
an
RSC
document
directly.
So
everything
else
that
I'm
trying
to
do
is
to
figure
out
ways
to
improve
the
general
editing
experience,
while
maintaining
all
of
the
functionality.
A
H
G
No
we're
not
went
through
through
it
all
Italy
six
more
weeks,
yeah
Wow
alrighty.
So
did
you
guys
know
what
we
have
to
do
because
it
really
category
here
that
I
can
talk
all
right,
cool,
so
yeah?
We
started
this
documentation
project
for
the
highlight
december
december
of
last
year's
is
pretty
closing
it
getting
out
there
so
I.
Pretty
much.
Did
the
design
houses
sure
can
help
us
out
putting
some
HTML
via
the
things
you'll
see.
G
G
G
Okay,
so
yeah
our
goals
for
this
project,
starting
out
in
December
words,
build
a
great
documentation,
experience
that
was
both
built
for
desktop
and
mobile.
Most
of
our
users
might
be
looking
on
mobile
and
our
turn
games
doesn't
or
that
we
also
have
to
think
about
the
style
guidelines
that
we
have
in
our
brains.
G
Guideline
book,
along
with
all
the
colors
that
were
using
a
juke,
your
labs,
make
it
all
consistent
across
the
juicer
universe,
and
we
want
to
make
a
user
feel
like
whenever
they're
reading
user
documentation
that
they're
in
one
place,
they're,
not
scattered
between
read
the
docs
and
juku
org
kind
of
redirect
them
all
over
the
place,
so
the
museum
kind
of
brings
all
supplementation's
gathers.
Even
so,
it
is
on
different
pages.
So
thinking
about
that
yeah.
D
G
For
each
one
of
these
files,
they
taught
this
game
kind
of
repose
inside
of
them
and
their
construction
saying
and
as
we
see,
how
can
we
use
the
documentation,
we're
going
to
restructure
for
how
what
make
sense
and
how
people
can
get
to
the
dock
as
quickly
as
possible?
And
so
I
think
you
see
that
this
team
looks
exactly
like
it's
on
the
website
and
I'll
give
you
a
recurring
theme
any
seats
without
these
dog.
I
So
disease
miss
incorporating
things
of
alabaster.
We
built
another
team,
basically,
on
top
of
it,
and
we
incorporated
absolute,
the
navbar
from
the
Jupiter
second
row
of
butter.
There's
a
loop
right
here
across
your
on
super-science
across
and
you
can
go
Laxus
not
usually
as
humble
and
we
are
incorporated
mobile
time.
Are
we
actually
don't?
This
is
a
custom
template
and
what
it
does
it
rebuilds
the
top
tree
each
time
and
it
could
be
yes
I
do
we
do
want.
I
There
is
some
important
firemen.
This
is
mainly
for
Phil,
decide
or
inside
talk
tree.
We
can't
be
using
captions
at
all
before
sidebar
to
work
correctly
at
all
and
for
the
sin
debt
restructure
textile.
We
use
one
contry.
This
is
for
each
documentation.
We
know
that
really
and
it's
been
access
to
either
have
no
such
things
or
just
have
subheadings,
but
have
the
ones
efforts
in
space
templates.
Let
what
do
you
go
to
a
section
of
Gotham
to
issues?
I
G
Community
can
use
the
resents
a
forum
page
how
sweet
they
are
in
the
documentation
because
it
becomes
we.
This
doesn't
just
people
advices
on.
Let's
say
this
create
creating
a
great
designer.
This
is
multiple
subsections.
Do
it
and
they're
just
all
the
H,
not
that
far
that
we
create
some
mobile
really
point
for
flies.
The
difference
of
perfection,
so
the
make
them
into
separate
pages
you'll,
be
able
to
buy
them
and
be
reflected
in
that
neck
bar.
So
you
want
to
pull
it
with
them
again.
B
And
the
main
constraint
with
the
new
dock
theme
is
that
we
use
an
actual
single
talk
tree
hierarchy
to
organize
our
documentation,
rather
than
sort
of
multiple
talk,
trees
with
captions
in
a
more
more
virtual
manner,
and
so
we're
we're
putting
together
documentation
for
the
actual
theme
with
some
of
these
guidelines
that
basically,
how
to
use
this
theme
effectively
for
Jupiter
documentation
in
that
that
it's
already
out,
but
we're
still
working
on
the
content.
For
that
and.
A
H
J
H
I
H
K
G
J
G
G
So
let's
say
we're
in
the
stupid
house
user
guide
section:
let's
go
to
mobile
and
see
what
this
experience
looks
like.
So
it's
a
completely
different
experience.
Well,
looking
pretty
similar,
so
you
can
see
we
just
blast
each
one
of
these
items
in
these
table
of
contents
to
only
show
one
user
actually
wants
for
navigating
to
that
section
of
the
website
and
yeah
it's
get
pretty
straightforward.
G
B
They
think
they're
on
one
website
going
back
and
forth
between
documentation
about
install
and
B
viewer,
but
in
actuality,
they're,
visiting
multiple
different
websites
that
we've
integrated
under
that
one
header,
so
that
that's
sort
of
how
we're
balancing
the
need
to
have
separate
doc,
development
and
and
and
hosting
for
each
repo
or
sub
project
it.
But
integration
with
the
website,
and
we
would
like
to
also
offer
this
unified
site
header
for
some
of
our
other
websites,
like
in
B
viewer,
the
blog
etc,
and
that
that
solves
some
of
the
usability
issues
that
we
found.
G
A
Right
thanks
guys
that
was
beautiful,
so
I'm
going
to
have
to
hand
the
baton
over
to
someone
else.
Ryan
did
you?
Would
you
be
interested
in
continuing
not
eating?
Okay,
great
super?
So
let
me
just
services
is
the
next
one
and
that's
Pete
and
min
usually
and
I'm
going
to
drop
off
so
Steven
thanks,
bye,
bye,.
L
Had
a
couple
notes,
less
mins
got
more,
but
just
some
dr.
sacks
backlog
grooming.
There
were
quite
a
few
issues
open
a
lot
of
them.
Questions
went
through
quoting
that
ones
are
I
told
I
would
clean
it
up
quite
a
bit.
There's
a
handful
enhancement
requests
against
the
sax
there
and
we
had
a
new
contributor
in
the
bean
who's
done,
helping
out
on
just
picking
the
loss.
Less
than
brief
I
think
menu
redeployed,
a
meteor
site
in
the
past
week,
which
had
the
mathjax
e
inserts.
L
We
both
the
main
reason
so
that's
up
and
running,
and
that
tracks
is
so
working
at
least
known
as
it
isn't.
It's
just
and
there's
a
couple
of
years
open
again.
Some
of
you
are
itself
one
for
adding
a
show
haiku
capability
that
Mike
and
I
come
back
and
forth
a
little
bit
on
and
one
from
the
community
about
supporting
iframes
in
books
on
the
interviewer
site,
which
is
going
to
get
pest
failure,
but
I
think
it's
similar.
L
The
right
word
on
the
person
on
that
and
I
think
the
other
service
like
a
couple
weeks
ago,
is
here
so
we're
starting
to
move
toward
the
chrome
gateway
to
will
release
still
give
you
back
on
doing
that.
Our
whirlwind
lever,
or
the
Lisa
I've
yet
actually
been
helping
out
with
pull
requests
on
my
repos.
So
it's
also
good
to
have
work
in
the
back.
E
B
E
E
E
Just
related
to
the
nd
here
to
play,
I
made
some
notes
somewhere.
That
I
should
probably
go
through
with
whoever's
interested.
The
process
of
deploying
and
upgrading.
Things
like
under
gears
make
sure
that
people
other
than
me
can
do
it,
and
so
we
can
try
to
arrange
it
a
time
with
anybody
interested
too,
so
that
I
can
walk
through
some
other
people
to
just
go
through
it
and
make
sure
that
their
permissions
and
everything
need
for
that.
E
E
B
L
B
M
Boy,
all
right,
so
we're
pushing
hard
to
get
a
beta
release
out,
hopefully
by
the
before
the
dev
meeting
at
the
end
of
this
month.
Last
remaining
things
are
getting
the
extension
mechanism
handling
sorted
out,
and
then
we
would
like
to
get
some
major
API
changes
through
before
we
people
start
building
extensions
in
earnest
against
the
band
released.
Ian's
got
some
exciting
work
going
on
with
the
real-time
collaboration.
M
We've
got
most
of
the
pieces
needed
for
that
in
and
he's
already
built
a
a
chat
box
using
that
so
that
so
you
have
a
real-time
chat
associated
with
the
current
doc.
You
were
working
on
and
I
saw
before
dread.
For
me,
it
looks
like
they
snuck
in
the
ability
to
drag
one
of
those
items
into
the
notebook
as
a
markdown
cell,
it's
pretty
nice
and
Brian.
Did
you
want
to
talk
about
your
collapsing
yeah.
B
Good
good
sort
of
cross-project
question,
while
we're
currently
working
on
some
ui/ux
wound
up
booking
cells,
making
small,
visual
design
and
user
experience.
Improvements
to
that,
and
one
of
the
things
we're
doing
along
with
that
is
designing
the
UI
for
both
cell
selection
and
input
and
output
hiding
and
collapsing,
and
our
initial.
B
The
way
we're
picturing
in
and
Jupiter
lab
is
that
that
state
of
input,
being
input
and
output
being
hidden
or
shown
would
be
view.
Information
that
would
not
by
default,
be
persisted
to
the
document
or
the
real
fun
collaborations.
But
then
there
would
be
some
sort
of
command.
The
user
could
run
to
say,
persist
my
clock
state
and
be
convert
metadata
and
or
persistent
to
the
document,
and
so
a
couple
points
of
collaboration
with
the
n
be
convert
team
and
be
viewer.
B
Folks,
one
is
making
sure
that
we're
when
we
do
persist
it
that
we're
persisting
it
in
a
way
that
makes
sense
from
the
metadata
and
document
format
perspective.
The
second
is
to
work
with
any
any
anyone
on
the
MV
viewer
side
to
basically
build
a
unified
UI
for
doing
this
collapsing
and
expanding
stuff.
F
B
But
the
idea
that
there
would
be
a
clickable
din
on
the
left
side
of
the
cell
and
well
on
the
left
side
of
an
input
and
an
output
that
could
do
the
collapsing
action
and
in
the
live
notebook
that
you
I,
would
probably
be
only
shown
on
the
selected
cell
and
then
be
convert.
We
could
show
it
on
hover.
We
could
show
it
on
all
cells
like
there's,
there's
flexibility
but
from
a
conceptual
perspective,
basically
divs
on
the
left
side
of
input
and
output
that
can
be
clicked
to
collapse
and
expand.
It's.
B
C
Comment
you
here,
camera
yeah,
one
comment
is:
maybe
it'd
be
better
to,
instead
of
take
up
more
horizontal
space,
we're
in
Jupiter
lab.
If
you
have
two
notebook
side
by
side
at
horizontal
space,
sounds
pretty
precious
to
make
that
a
collapsing
UI
part
of
the
one,
the
label
for
the
cell,
so
I
command.
You
have
the
bracket
one
and
then
right
underneath
that
you
click
on
the
one
or
something
and
that's
and
the
line
is
going
directly
underneath
the
one
instead
of
taking
another
vertical
column
there,
but
the
key.
B
K
B
The
the
other
thing
that
were
working
on
and
thinking
about
is
rethinking
Jupiter
lab
right
now
in
master,
allows
individual
outputs
and
I
don't
mean
the
entire
outcome
order
itself.
But,
for
example,
if
you
print
10
integers
in
Jupiter
lab,
you
can
drag
one
of
those
integers
out
into
the
dock
panel.
B
And
then
once
you
have
input
and
output
collapsing,
you
know
if
you
want
to
focus
on
just
the
output
dragged
out,
you
just
collect
the
input
or
you
can
work
with
it
that
way,
and
so
we're
trying
to
unify
all
this.
It's
by
no
means
decided
right
now,
we're
refactoring
the
code,
so
we
can
start
to
actually
try
some
of
these
things,
but
that
that's
our
current
thinking
about
how
this
would
interact
with
sort
of
draggable
content.
Moving
into
the
dock
panels.
F
So
one
of
my
reactions
to
the
quick
prototype
which
looks
pretty
cool
is
that
it
might
be
nice
to
have
a
slightly
different
kind
of
UI
to
indicate
on
hover
that
you've
already
collapsed,
something
than
just
the
inverted
arrow
that
you
would
use
to
collapse
it
because
that
can
be
easily
misread
and
it
might
be
hard
to
track
down
lost
cells
and
especially
the
cells,
have
no
borders
anymore.
Yes,.
B
F
I
mean
the
way
that
I'd
sold,
it
was
keeping
an
element
off
to
the
side,
the
and
it
was
either
toggled
on
or
not,
but
one
possibility
would
be
rather
than
having
it
in
line
would
be
to
have
it
just
below
if
so
long,
as
you
have
the
anything
of
the
cell
there,
like
the
cell,
the
prompt
number
or
whatever
you
have
triple
dots
right
below
that
in
that
left
column,
as
opposed
to
having
it
in
line
with
the
rest.
Because
now
it
looks
like
three
quotes:
are
the
output
of
that
cell
or
three
dots?
B
C
Yeah
and
so
we
released
an
alpha
but
instructions
in
the
paper
robots
paper
notes.
We
had
some
new
contributions,
a
new
password
was
it
new
routine
button
on
the
play
widget
we
now
studentized
binary,
widget
state
so
that
you
can
say
for
widget.
Since
we
added
we
had
capability
for
widgets
that
binary
state,
we
need
to
upgrade
the
serialization
for
saving
widget
states,
a
notebook
etcetera.
C
So
we
have
that
and
we
refactored
responsibilities
so
that
widget
managers
are
now
in
charge
of
loading,
the
appropriate
widget
classes,
which
just
cleans
up
the
API
a
little
bit
and
makes
things
it
makes
the
responsibilities
a
lot
clearer,
and
so
we
work.
We
think
we're
about
done
with
major
features
that
we're
planning
on
doing
and
we're
shifting
focus
towards
testing
a
documentation.
There
might
be
some
more
refectory
repo
that
will
do,
but
the
major
focus
now
is
testing
a
documentation.
J
How
about
I'm
going
to
do
one
more
quick,
shout
out?
Thank
you
to
the
Cal
Poly
interns
charm,
create
Cameron
and
Fargo
for
the
great
work
they're
doing
on
the
docks
and
also
making
our
presentations.
Look
beautiful
and
making
the
user
experience.
Awesome
so
congrats,
guys
and
gals,
and
thank
you
again
and
as
far
as
Jupiter
hub
we're
missing
men
and
his
clones.
J
But
we
have
been
pretty
much
doing
triage
and
and
support
configuration,
questions
answering
and
stuff
on
Jupiter
hubs
and
not
a
whole
lot
of
new
development
going
on
currently,
but
there's
some
really
great
work
being
done
on
the
kubernetes
deployment
stuff
and
some
really
good
feedback
from
community
members
that
are
using
the
docs.
And
we
thank
them
for
that
and
that's
about
it
for
Jupiter
hub
right
now.
Unless
man
has
something
I.
E
Put
one
little
thing
in
there:
I
finally
got
around
to
something
we've
been
talking
about
for
a
very
long
time
of
lending
a
methods
we've
got
our
rep
for
HTML
and
whatnot,
and
now
that
now
that
everybody's
talking
about
custom,
mind
types,
we
need
something
that
we
need
a
way
for
people
to
say.
I
can
be
displayed
with
this.
My
type
so
I
put
up
a
proposal
of
one
such
implementation
that
it's
just
a
another
method
that,
instead
of
returning
one
line
type,
it
returns
the
mind,
bundle
itself.
So
it'll
support
ever
carry
mine
types.
B
B
Obviously,
PyCon
is
coming
up
in
Portland
soon
plot
con
is
in
the
Bay
Area
this
week
and
yeah
there's
a
lot
of
other
conferences.
There,
probably
most
importantly,
is
Jupiter
Khan
and,
as
hopefully,
everyone
knows,
and
if
not
Jupiter
Khan.
Our
first
conference
is
going
to
be
this
summer
in
New,
York,
City,
August,
22nd
to
25th
and
registration
is
now
live.
The
the
talks
we
had
submitted
for
the
conference
were
absolutely
spectacular.
B
To
mention
that
there's
a
Riley
with
whom
we're
partnering
for
Jupiter
Khan
has
diversity
scholarships
and
that
covers
both
registration
and
a
good
portion
of
travel
expenses
and
then,
in
conjunction
with
our
funding
agencies
at
Cal,
Poly
and
Berkeley.
We're
also
offering
student
scholarships
as
well.
The
details
of
the
diversity
scholarship
are
on
the
Jupiter
comm
registration
page
and
we're
hoping
to
have
the
student
scholarship
Club
soon
and
so
I
encourage
everyone
to
check
that
out.
B
Next
next
category
is
governance
and
I
guess
Pete.
You
already
mentioned
the
PR
that
you
had
there.
The
only
other
comments
I
have
on
governance
is
that
I'm
I
haven't
unlike
to-do
list,
there's
number
of
PRS
that
I
is
either
started
or
participated
on
the
governance
repo
that
I
can
help
Shepherd
through
the
process
of
being
edited,
approved
and
merged.
B
B
Right,
there's
another
section
there
for
soon
to
be
released,
looks
like
NB,
dime,
0.32,
third
or
lab
0.21,
and
if
there's
any
other
releases
coming
up
with
folks
can
add
those,
and
at
this
point
we
have
reached
the
end
of
our
agenda.
Only
four
minutes
over
is
there
anything
any
other
topics
that
folks
wanted
to
bring
up
before
we
close
the
meeting
out.