►
From YouTube: JupyterLab Dev Meeting, December 9, 2016
Description
Meeting of the JupyterLab development team, December 9, 2016
Meeting Notes: https://jupyter.hackpad.com/JupyterLabNotebook-Weekly-Meetings-UUJ3gIQ3iBS
A
Hi
everyone
today
is
this
summer.
Ninth,
and
this
is
the
Jupiter
lab
/
notebook
weekly
meeting
I'll
get
things
started
in
the
past
week.
We've
been
trying
to
just
do.
General
cleanup
address
some
of
the
beta
issues
and
the
writing
unit
tests.
The
abstract
editor
is
in
and
it's
proven
to
be
working
well,
there's
a
link
to
a
PR,
adding
Monaco
integration
is
a
couple
concerns
the
way
Monaco
is
structured.
B
B
The
notebook
is
obviously
more
challenging
and
what
I've
been
starting
to
do
as
a
simpler
version
of
that
is
make
a
widget
for
a
chat
box,
so
that
people
can
send
messages
without
having
to
write
it
in
the
actual
working
document
back
and
forth
to
each
other,
the
idea,
they're
being
that
that's
a
synchronized
list
that
has
text
in
it,
but
its
overall
much
simpler,
documented
than
them
than
the
full.
Don't
look
so
that's
about
it.
C
C
There
wasn't
really
much
traction
on
getting
people
to
sort
of
contribute,
but
the
level
of
interest
in
the
actual
project
was
really
high,
and
some
of
the
features
that
are
forthcoming
were
really
well
received.
So
it
was
good
and
now
I'm
working
on
refactoring.
The
state
restoration
features
that
we've
been
releasing
in
the
past
few
weeks,
just
to
try
to
simplify
it,
a
bit
more
for
plug-in
authors
and
to
take
some
of
the
boilerplate
away.
I
have
an
outstanding
PR,
that's
not
complete.
Yet
that
achieved
some
of
that
already.
C
Restoration
of
the
sidebars
so
that
they
actually
reappear
in
the
correct
order,
because
we
do
currently
have
enough
information
to
do
that.
We
don't
need
to
wait
for
the
rehydration
stuff
that
Chris
will
be
building
into
phosphor,
that
that
information
is
already
available,
so
so
yeah
that
those
two
things
are
actually
in
the
same
PR,
because
they
touch
all
the
same
files.
Yeah
and
that's
it.
For
me.
D
Thank
you
all
right,
so
I
just
added
a
quick
note
in
the
hack
pad
we
had
a
short
discussion
on
guitar
yesterday
about
keeping
track
of
the
road
map
on
github.
So
now
that
jupiter
lab
is
its
own
org.
We
have
the
Jupiter
org
with
all
the
sub-project
robots
and
it
so
be
great
to
have
a
distinct
road
map
for
Jupiter
lab
right
now.
D
I
think
a
lot
of
the
Jupiter
lab
work
is
in
the
notebook
roadmap,
but
that's
still
those
are
still
kind
of
separate
efforts
with
different
people
and
please
you
know
if
that
doesn't
sound
right.
Let
me
know,
but
I
think
the
way
that
we're
visualizing,
those
is
like
two
parallel
affair
efforts
and
as
Jupiter
lab
choirs
feature
parity
with
the
notebook
and
then
kind
of
the
functionality
starts
to
you
know,
exceed
what's
in
the
notebook,
the
the
notebook
stuff
will
kind
of
fade
away,
but
that's
going
to
be.
D
A
D
Ok,
cool,
so
that's
work
that
that
still
needs
to
be
done,
but
it's
been
noted,
as
is
it
to
do.
Basically:
yes,
ok,
great,
awesome,
cool
anything
else.
We
have
some
folks
who
are
on
the
call,
but
not
visible,
Chris
and
Carol
I
know
Carol's
just
listening
in
today,
Chris
anything
you
wanted
to
share.