Jupyter Notebooks are a common type of code used for data-science use cases. With GitLab you can store and version control those notebooks in the same way you store packages and application code.
This page is maintained by the Product Manager for Package, Tim Rizzi (E-mail).
Our next set of priorities for Jupyter Notebooks, are about resolving issues with how notebooks are rendered within Gitlab. Since Jupyter is often used to present data and findings, it's important that we render images and content properly. giltab-#18540 will resolve an issue where images in markdown cells are not displayed.
This category is currently at the "Minimal" maturity level, and our next maturity target is Viable (see our definitions of maturity levels).
Key deliverables to achieve this are:
The top customer success / sales issue is gitlab-#33193, which will improve the Jupyter installation process by giving improved error / success messages.
The top user issue is gitlab-18540, which details a problem with image rendering within Jupyter notebooks.
The top internal customer issue is gitlab-#9427, which will empower the Release team, to utilize Jupyter Notebooks as a runbook to create a checklist/documentation for releases.
The top vision item is gitlab-#22723, which will add support for BinderHub, a dependency manager for Jupyter Notebooks. This will allow users to build notebooks on-demand and provide customized computing environments, built from their Git repo.
