Hi all, we've had discussions since the last dev meeting about organizing the project into more well-defined teams for each major area, since we're well past the point where "everyone does everything" can remotely work.
While we're still settling down on some details, I think on the Notebook/JupyterLab area, the most complex piece of development we have going on right now, we should socialize/finalize this sooner rather than later. I *think* there was reasonable agreement from earlier discussions on the plan that having a joint lead structure with Brian, Jason and Matthias working together would be the best approach here. While Brian and Jason have been focused on Lab, Matthias has kept more of his attention on the "classic" Nb. This effort is large and carries the special challenge of finding what the right "sunset" path is for the classic Nb while Lab matures and becomes a complete, no-compromise replacement. A team of three with overlapping expertise across the two codebases seems like a good solution. In order to help that entire team settle into a good routine for planning and decision making, I think it's key that we come to agreement on this. If anyone has further thoughts, by all mean pitch in (or we can discuss it at the JLab meeting tomorrow). Cheers f -- Fernando Perez (@fperez_org; http://fperez.org) fperez.net-at-gmail: mailing lists only (I ignore this when swamped!) fernando.perez-at-berkeley: contact me here for any direct mail -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAHAreOqvUKGhKxBYKCx04fyDGigJueK59tLx_zZugqbGXH_nQQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
