Hi Everyone, hopefully a more timely summary this week. As usual, if this is helpful for you, you are welcome to participate, and edit the DropBox summary before I send it to the mailing list.
See http://bit.ly/JupyterTeamMeetingArchive to see all the notes, the youtube link should soon be available if you want to actullay listen to the meeting. . Weekly news by organization - IPython <https://github.com/willingc/pulse_news/blob/master/2017-09-12_ipython.md> - Jupyter <https://github.com/willingc/pulse_news/blob/master/2017-09-12_jupyter.md> - JupyterLab <https://github.com/willingc/pulse_news/blob/master/2017-09-12_jupyterlab.md> - Jupyter-widgets <https://github.com/willingc/pulse_news/blob/master/2017-09-12_jupyter-widgets.md> - JupyterHub <https://github.com/willingc/pulse_news/blob/master/2017-09-12_jupyterhub.md> Note: weekly news is available via the Dropbox Paper files or stored in this news repo <https://github.com/willingc/pulse_news>. There was a request from Kyle to add nteract <http://Created 2017-09-12_nteract.md> to the weekly news as well. IPython (Matthias) I’m slowly ramping up IPython development again. We haven’t had a release in quite some time, and had a couple of bugfix. I’ll try to cut a 6.2/5.5 in the next few weeks ; with few new features. MrMeeseeks (or bot) is smarter (since yesterday/this morning) and will for the IPython repository, automatically backport PRs that are milestoned 5.whatever, no need to ask him to do so. I plan to work with Chris H. on Friday to try to bring that to the matplotlib org. Feel free to join if you have ideas for the bot. Thomas is suggesting removal of old, unused IPython labels; it will discared some information about old issues. See thread <https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/jupyter/6sBaT4JDWmo/JzpyBsjOEQAJ>, if you want to express your (dis)agreement: - backport-{0.12.2 … 2.1} (We later switched to using milestones to indicate backports) - console (redundant with zmq-console) - emacs - forward_port - hacktoberfest - latex - py3k Governance (Matthias) Please read about the LICENSE guideline discussion, if you haven’t, and are interested in the tricky buisness of doing the right thing (not alway easy): jupyter/governance#37 <https://github.com/jupyter/governance/issues/37> Documentation (Jessica) - Looking for feedback for demo before we present at Strata NYC - Hoping to get feedback from UX studies regarding Jupyterlab FAQ - Would like to share language between docs FAQ and Jupyterlab FAQ https://github.com/jupyterlab/jupyterlab/pull/2954 https://github.com/jupyterlab/jupyterlab/pull/2785 Notebook (Grant) - Grant has returned from Indonesia and will push for 5.1 release this week - 5.1.0rc3 is available for testing. Nbconvert (M) - released 5.3.1 (fixes the license issues to include in Manifest.in) both on pypi and conda-forge - conda-forge build includes a change to noarch <https://github.com/conda-forge/conda-smithy/issues/485> which could(?) mess with entrypoints, if anyone runs into any issues with the conda-forge build (especially if using Windows…) - Honestly, this is less my expertise - noarch means “no architecture”. Usually a package is built separately for each “architecture”, e.g., a build for Windows, a build for Linux, a build for OS X, etc. The noarch flag, possible on packages that are pure python, etc., means that you can build only a single package and it will work across all of the architectures. Nbformat (M) - we now explicitly document cell.metadata.name’s uniqueness & its limitations - doc pr: https://github.com/jupyter/nbformat/pull/117 - summary: we can’t verify uniqueness across cells with the json schema. - we should look into implementing (efficient) checks in our front-ends for name uniqueness - no prs to link - what should the priority of this be? - where this should be implemented? - *Python* in nbformat? - *javascript* in notebook? jupyterlab? nteract? - tags behaviour and conventions - pr (on notebook): https://github.com/jupyter/notebook/issues/2826 - issue should stay on notebook until we come to some kind of an agreement - this explicitly introduces the raises-exception tag as having a jupyter specific meaning (has not been released yet but will be with 5.1) - how should we come to a consensus about the appropriate use of tags? Do we have a mechanism for establishing this? - issues seem to be a bad at establishing consensus… or even getting a general feel for people’s attitudes (as opposed to an ongoing conversation) - How can we implement hooks for people to assign tags to functionality in a live javascript context? - are traitlet (json) config files enough? - do we want to somehow include them with the notebooks themselves (since they otherwise will not be consistent once shared)? - Do we want to use tags in a different way than nbconvert uses them JupyterLab (Steve, Darian) - Continued work towards the beta, nothing significant to report. Jupyter widgets (Jason) - We are working on a 7.0.1 release <https://github.com/jupyter-widgets/ipywidgets/milestone/16> fixing some issues that were reported, adding more documentation, etc. We hope to release 7.0.1 this week. Services (Peter) - There have been many recent PRs in docker-stacks with requests to add and update libraries/languages and support other options ( https://github.com/jupyter/docker-stacks/issues/464, https://github.com/jupyter/docker-stacks/issues/454). - Breakage occurs because of the complexity of software and options now available. - We could start putting more testing around the images ( https://github.com/jupyter/docker-stacks/issues/406) - We’re could also discuss ways of getting these images back to a small “starter kit” set and providing users with a way to build their own ( https://github.com/jupyterhub/binderhub/issues/101#issuecomment-328358104 ) - Kernel Gateway 2.0.1 released upon user request with one bug fix. - It had been a few months since last release and there was nothing else in flight. - A discussion kicked off about shifting some of the KG features back to notebook server ( https://github.com/jupyter/kernel_gateway/issues/259). - conda-forge folks requested that we try *noarch: python.* Looks like it worked: https://github.com/conda-forge/jupyter_kernel_gateway-feedstock/pull/7 - nbviewer has a handful of PRs that I haven’t had time to review JupyterHub (Min, Carol) - Please send any feedback on JupyterHub 0.8 beta #5 (which was released last week - changes from 0.8.0b4 <https://github.com/jupyterhub/jupyterhub/compare/0.8.0b4...0.8.0b5>). Thanks! Conferences and Workshops - PyData Paris Sep 12th. Talk by Maarten on ipyvolume, and Romain Menegaux on bqplot - Strata NYC, September 25 - 28, https://conferences.oreilly.com/strata/strata-ny - Jason Grout and Jessica Forde are talking on JupyterLab <https://conferences.oreilly.com/strata/strata-ny/public/schedule/detail/61260> - Grace Hopper Celebration Oct 4-6 - Open Source Day (Jupyter is one of 8 Humanitarian Projects) https://ghc.anitaborg.org/2017-attend/conference-overview/open-source-day/ - PyCon UK Oct - Carol attending while on vacation - ODSC West, San Francisco, Nov 2-4, https://www.odsc.com/california - Matthias has submitted a talk - PlotCon NYC, Nov 14 - 17 (no website available yet) - PyData NYC Nov 27-30 - PyCon Pune 2018 - Feb 8-11. Keynote by Carol https://pune.pycon.org/2018/ - PyCon Caribbean 2018 - Feb. Keynote by Carol - Strata San Jose March 5-8 2018, San Jose https://conferences.oreilly.com/strata/strata-ca JupyterCon - www.jupytercon.com <https://conferences.oreilly.com/jupyter> - August 21-28, 2018 - NYC Released last week - JupyterHub 0.8.0b5 - Kernel Gateway 2.0.1 - nbconvert 5.3.1 Releases for this week - ipywidgets 7.0.1 Have a good week, and see you next monday. -- Matthias -- 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/89be15fb-a027-492e-8d60-b996f91e94b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
