Notebook/jupyterlab communication

[Brian Granger]

Hi all!

Great to see notebook 5.0 getting close@ We are probably a bit delayed
on a JupyterLab beta (we originally thought mid/late Feb), but it is
not far off.

I would like to propose a regular time for the notebook/lab devs to
get together to coordinate efforts and communicate. This is especially
true as JupyterLab get close to beta and 1.0, which will officially
begin the transition for our users away from the classic notebook.

Some options:

* Expand the scope of the Friday 9-10am PST meeting to include classic
notebook stuff as well.
* Find a different time for all of us to meet.
* A hybrid - maybe each team separately could meet from 9-10am and
that all of us could meet together from 10:30.
* Other?

I apologize for not initiating this sooner - it is something that
Jason, Matthias and I have talked about for a while.

I would like all of us to meet together at least once before 5.0 of
notebook comes out. Notebook 5.0 will be the basis of both jupyterlab
(beta/1.0) and the first release of the notebook in the nb->lab
transition process. Making that smooth for users is especially
important.

Cheers,

Brian





--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgra...@calpoly.edu and elli...@gmail.com

[Min RK]

On Tuesday, February 7, 2017 at 2:38:32 AM UTC+1, ellisonbg wrote:

Hi all!

Great to see notebook 5.0 getting close@ We are probably a bit delayed
on a JupyterLab beta (we originally thought mid/late Feb), but it is
not far off.

I would like to propose a regular time for the notebook/lab devs to
get together to coordinate efforts and communicate. This is especially
true as JupyterLab get close to beta and 1.0, which will officially
begin the transition for our users away from the classic notebook.

Some options:

* Expand the scope of the Friday 9-10am PST meeting to include classic
notebook stuff as well.
* Find a different time for all of us to meet.
* A hybrid - maybe each team separately could meet from 9-10am and
that all of us could meet together from 10:30.
* Other? 

I apologize for not initiating this sooner - it is something that
Jason, Matthias and I have talked about for a while.

I would like all of us to meet together at least once before 5.0 of
notebook comes out. Notebook 5.0 will be the basis of both jupyterlab
(beta/1.0) and the first release of the notebook in the nb->lab
transition process. Making that smooth for users is especially
important.

I think a few coordination meetings is a great idea while we are working towards releases. Adding it to one or the other of our existing meetings during this time sounds best to me, so we aren't increasing the number of meetings to schedule. In general, I think we should keep as much communication async as possible, so I'd like to avoid adding another regular meeting to the weekly schedule.

-Min