►
From YouTube: JupyterLab Dev Meeting, July 29, 2016
Description
Meeting of the JupyterLab development team.
Meeting Notes: https://jupyter.hackpad.com/JupyterLab-Weekly-Meetings-UUJ3gIQ3iBS
B
Hi
yeah
so
this
week,
most
of
the
things
that
I
would
have
wanted
to
talk
about
actually
already
came
up
in
the
larger
meeting.
The
only
thing
I
want
people
to
think
about
is
I,
put
up
an
issue
with
requests
for
comments
about
how
we're
versioning
things
Steve
and
Jason
and
I
talked
about
this
issue,
and
it
might
be
that
just
the
three
of
us
arriving
at
a
consensus
is
sufficient,
but
I
wanted
to
make
sure
everyone
has
the
opportunity
to
talk
about
if
they
want.
B
Basically,
the
way
we
handle
versioning
makes
makes
us
have
to
be
very
careful
about
the
types
of
semantic
versioning
tokens
that
we
actually
are
allowed
to
use.
We
can't
use
all
semantic
versioning
options,
so,
for
example,
when
you
have
a
zero
point,
one
point:
zero,
that
is
a
normal
thing,
can
be
parsed
and
when
you
have
an
extension
that
relies
on
on
a
specific
range,
it
can
be
used
to
calculate
that
range.
B
But
if
in
between
versions,
we
put
a
hyphen
whatever
hyphen
beta,
iphone,
RC
dot,
one
or
whatever,
all
those
things
it
fails
to
match
and
because
of
the
way
we
currently
need
to
build
a
with
web
pack,
you'll
get
multiple
copies
of
Jupiter
lab,
which
means
there
will
be
a
runtime
error,
but
not
a
build
error,
so
won't
even
show
when
you
check
it
in
it'll
only
show
when
people
try
to
run
it.
So
we
agreed
for
the
time
being
to
just
discontinue
use
of
those
identifiers
that
come
after
the
patch.
B
Once
we
have
a
new
build
system,
we've
discussed
how
we
can
fix
this
and
support
those.
So
we
may
we
may
switch
back
to
it.
But
for
the
time
being,
that's
that's
the
prescription
that
we're
making
I'm
trying
to
remember
okay,
that
issue.
If
anyone
cares
to
weigh
in
is
566
and
put
on
a
Kern.
Oh
great
thanks
a
lot
and
yeah.
So
that's
it!
It's
it's
I!
Think
it's
pretty
exhaustively
written
up
and
I
think
it's
fairly
straightforward.
But
if
somebody
thinks
of
something
that
we
haven't,
that's
the
place
to
bring
it
up.
C
I
guess
I'll
go
next,
there's
a
we
are
about
to
flip
the
switch
to
switch
to
the
mono
repo,
though
I
just
wanted
to
give
a
heads
up,
especially
to
the
Cal
Poly
interns.
At
least
the
the
existing
I
think.
It's
faq
rewrite
PR
we're
going
to
get
that
merged
before
we
push
them
on
a
repo,
so
that
doesn't
disrupt
that.
But
there
will
be
a
transition
period
of
a
couple
days
where
bisque
a
lot
of
the
imports
will
change,
but
hopefully
not
much
else
at
all.
C
So
the
plug-in
semantics
will
change
slightly,
but
we're
going
to
go
through
as
a
team
made
Aaron
and
Cris
and
make
that
change
over.
So
there's
already
PR
against
stupid,
ojs
services
that
switches
things
over
to
phosphor
and
will
merge
that
once
the
once
phosphorus
actually
released
and
then
pull
that
forward
into
Jupiter
lab.
While
we
switch
everything
over
to
the
mono
repo.
D
So
that
kind
of
naturally
transitions
to
me,
which
is
that
we're
about
to
pull
the
trigger
on
the
mono
repo
thanks,
Steve,
first
of
all,
and
was
surprised,
but
basically
there's
a
one
PR
that
I've
got
out
that
I'm
about
about
to
merge
here,
I'm,
giving
it
one
final
once-over.
But
basically
what
that
does
is.
It
brings
all
the
all
the
important
parts
of
phosphide
that's
being
used
by
Jupiter
lab
into
the
mono
repo,
which
gives
us
everything.
D
We
need
to
cut
a
new
version
of
the
motto,
repo
and
start
moving
cheaper
lab
over
to
that.
The
other
big
thing
that
it
brings
in
is
something
that
the
Cal
Poly
people
were
asking
for,
and
it's
a
way
a
simpler
way
to
generate
leaf
contents
and
phosphor,
and
so
we
have
a
basic
bare
bones,
but
sufficient
implementation
of
a
virtual
Dom,
and
for
now
that's
coming
in
with
that
PR,
so
it'll
be
a
much
easier
way
to
basically
rent
our
custom
leaf
contents.
D
So
make
a
couple
of
examples
of
that
and
get
with
you
guys
as
needed
to
show
you
how
to
use
that
as
part
of
that,
it's
already
being
used
to
render
the
content
of
the
tab
bar.
So
there
is
live
examples
of
it
already
being
used
within
within
phosphor
I'll
move
some
more
of
the
other
content
renderers
for
like
menu
and
command
palette,
those
sorts
of
things
over
to
that
system
as
well.
So
it
does
simplify
some
things
when
used
in
moderation.
D
A
E
We
just
wanted
to
point
out
that
we
did
some
of
the
results
from
user
testing.
Okay
till
we
can
start
tackling
some
of
those
issues
that
was
noticed.
In
addition,
I'm
working
on
my
own
little
project
to
file
browser
scroll,
I
was
are
going
to
see
without
I.
Have
a
couple
more
questions
at
all.
In
talk
to
you
about
today.
Can.
E
If,
during
the
selected
item
in
the
file
browser
and
you've
restored-
and
if
the
list
is
longer
than
the
viewing
window,
then
it
should
automatically
scroll
to
whatever
the
selected
item
is,
and
some
are
going
on
right
now:
I,
yeah,
I'm
right
now.
It's
definitely
like
selected
item,
so
I
just
need
to
figure
out.
F
G
To
read,
like
the
user
testing
information,
we
posted
most
of
the
information
on
github
as
issues,
so
you
guys
could
find
us
there.
We
kind
of
collected
a
lot
of
the
data
and
then
formatted
for
each
plug-in
individually,
and
then
we
are
working
with
brian
and
fernando
and
trying
to
actually
upload
all
the
videos
but
the
screencasts
we
took
of
the
user
test
to
it
by
2
32.
Just
so,
we
can
all
have
access
to
them
and
view
them
so
we're
just
waiting
on
login
information,
in
my
permission
to
upload
to
that
channel.