diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 000000000..62a040faa --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,5 @@ +blank_issues_enabled: false +contact_links: + - name: "\U0001FA90 Questions or issues about one of the tools in Jupyter" + url: https://discourse.jupyter.org + about: Welcome to the Jupyter meta repository! This repository is the home of the Jupyter-wide documentation. However, it is not the best place to ask questions about Jupyter. We recommend asking in the Jupyter community Discourse forum. Thanks! diff --git a/.github/ISSUE_TEMPLATE/doc_suggestion.md b/.github/ISSUE_TEMPLATE/doc_suggestion.md new file mode 100644 index 000000000..7902b45ff --- /dev/null +++ b/.github/ISSUE_TEMPLATE/doc_suggestion.md @@ -0,0 +1,22 @@ +--- +name: "\U0001F4D6 Documentation suggestion" +about: Propose changes to the Jupyter-wide documentation + +--- + + diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml new file mode 100644 index 000000000..b832d42ed --- /dev/null +++ b/.github/workflows/release.yaml @@ -0,0 +1,41 @@ +# Build releases and (on tags) publish to PyPI +name: Release + +# always build releases (to make sure wheel-building works) +# but only publish to PyPI on tags +on: + push: + pull_request: + +jobs: + build-release: + runs-on: ubuntu-24.04 + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-python@v2 + with: + python-version: "3.10" + + - name: install build package + run: | + pip install --upgrade pip + pip install build + pip freeze + + - name: build release + run: | + python -m build --sdist --wheel . + ls -l dist + + - uses: actions/upload-artifact@v4 + with: + name: jupyter-${{ github.sha }} + path: "dist/*" + if-no-files-found: error + + - name: publish to pypi + uses: pypa/gh-action-pypi-publish@v1.5.1 + if: startsWith(github.ref, 'refs/tags/') + with: + user: __token__ + password: ${{ secrets.pypi_password }} diff --git a/.readthedocs.yaml b/.readthedocs.yaml new file mode 100644 index 000000000..c5e99e385 --- /dev/null +++ b/.readthedocs.yaml @@ -0,0 +1,17 @@ +version: 2 + +# Set the OS, Python version and other tools you might need +build: + os: ubuntu-22.04 + tools: + python: "3.11" + apt_packages: + - graphviz + +# Build documentation in the "docs/" directory with Sphinx +sphinx: + configuration: docs/source/conf.py + +python: + install: + - requirements: docs/doc-requirements.txt diff --git a/.travis.yml b/.travis.yml index 6ab2ca283..6551be719 100644 --- a/.travis.yml +++ b/.travis.yml @@ -1,12 +1,48 @@ language: python sudo: false python: - - 3.5 - - 3.4 -install: - - pip install --upgrade pip - - pip install --upgrade sphinx - - pip install jupyter_sphinx_theme - - pip install recommonmark -script: - - cd docs && make html + - 3.7 + +jobs: + include: + - stage: test-docs + install: + - pip install --upgrade pip sphinx + - pip install -r docs/doc-requirements.txt + script: + # Test build of HTML docs and English translation templates + - make -C docs html + - make -C docs gettext + - cd docs && sphinx-intl update -p build/locale -l en + - stage: push-tx + install: + - pip install --upgrade pip sphinx + - pip install -r docs/doc-requirements.txt + script: + - cd docs + # Rebuild HTML again to test for merge problems + - make html + # Regenerate English translation templates + - make gettext + - sphinx-intl update -p build/locale -l en + - git config --global user.email "travis@travis-ci.org" + - git config --global user.name "Travis CI" + # Stage any changes to the english source files + - git checkout master + - git add -A source/locale/en + - git status + # Commit the english templates, exiting early if there are no changes + - git commit -m '[ci skip] Update English source strings' || travis_terminate 0; + # Push the commit to master for Transifex to notice and update its strings for translation + - git remote add origin-tx https://${GH_TOKEN}@github.com/jupyter/jupyter.git + - git push -u origin-tx master + +stages: + - name: test-docs + if: type = pull_request + - name: push-tx + if: type = push AND branch = master + +env: + global: + secure: "xWn2cnWWNgtQEm9MXAIQerigtwkZxMDQYQnlbALvHywy63MVsWwvDSi9AnPm9ty+TuNxu8bWXGP99KNjSgPEkvb5wA/uCGmmD1l6eA8CdxWZeRVEQ88NNQMXvAwxmUEGub0OSBaLC37WHXWrM1BzPV9jXQGS5HKC1icu9en/ScorOnw7Waz1wfVpjZRPLbp/8+M5jadpp6VZfCp4rsAdb6wuBy0JKA383azPE8e87WBqDWCS3zR2esZqwJKkOpkMsTcIs+n6naJXFl9rmM5o+l4vEQ0aUpAzzdE2ZrX9HfwCuOAFGJmlYmdmCbNFty3Dh6vkdtZvp2ptysda6Tb2FFc1+5kWhzfrQoHBhkXQW9557YGjwmIohjCy7pmTxtucnd9JgqOUNH1dnvQ8Z4RMOTcIc1loKe80I903Yw4aFkj36gMWtMfqUghpEn1ZYbtl5k/ZWwTnRKyyg8bkFPU7EyXn+u97ItPMdIpRybXUa2qKWGohXoziDur/7ecJOiCI1ynJlUT8sJRa8fhpRd0/iTC28zECU3wa+G1nx4XcOowNX9tJAV4EpaL/DFNLXlxXfs1JX0Ccn0YTaljo/suOnINzBl1Dn87QDdYlvijFwmRrXWS363wjzp0K9OqqSWkfEAEuSBI6d4Ywc64Ob4+pRoBJIW3sT2LHNvP0yUQL39Y=" diff --git a/LICENSE b/LICENSE index 47abad9c8..295746a56 100644 --- a/LICENSE +++ b/LICENSE @@ -1,4 +1,6 @@ -Copyright (c) 2015, Project Jupyter +BSD 3-Clause License + +Copyright (c) 2017, Project Jupyter Contributors All rights reserved. Redistribution and use in source and binary forms, with or without @@ -11,7 +13,7 @@ modification, are permitted provided that the following conditions are met: this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. -* Neither the name of jupyter nor the names of its +* Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. @@ -24,5 +26,4 @@ DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE -OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - +OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. \ No newline at end of file diff --git a/MANIFEST.in b/MANIFEST.in index dd0245fd4..8392e9d8e 100644 --- a/MANIFEST.in +++ b/MANIFEST.in @@ -4,4 +4,4 @@ prune build prune dist include LICENSE -include README.md \ No newline at end of file +include *.md diff --git a/README.es-ES.md b/README.es-ES.md new file mode 100644 index 000000000..173f7a53d --- /dev/null +++ b/README.es-ES.md @@ -0,0 +1,31 @@ +# Jupyter + +*Leer en otros idiomas: [English](README.md), [Español](README.es-ES.md), [Português](README.pt-BR.md), [Français](README.fr-FR.md)* + +Meta paquete de Jupyter para su instalación y documentación. + +## Ejecutando los documentos localmente +Primero navega al directorio `/docs` y crea un entorno en `conda`: + +```bash +conda env create -f environment.yml +``` + +Activa el entorno: + +```bash +source activate jupyter_docs +``` + +Genera los documentos: + +```bash +make clean +make html +``` + +Los documentos se crearán en `build/html`. Éstos pueden ser vistos abriendo `build/html/index.html` o iniciando un servidor HTTP y navegando hasta `0.0.0.0:8000` en tu explorador web. + +```bash +python3 -m http.server +``` diff --git a/README.fr-FR.md b/README.fr-FR.md new file mode 100644 index 000000000..33a3ad0d3 --- /dev/null +++ b/README.fr-FR.md @@ -0,0 +1,31 @@ +# Jupyter + +*Lire ceci dans d'autres langues: [English](README.md), [Español](README.es-ES.md), [Português](README.pt-BR.md)* + +Jupyter metapackage pour installation et docs. + +## Faire tourner les docs localement +D'abord naviguer dans le répertoire `/docs` et créer un environment `conda` : + +```bash +conda env create -f environment.yml +``` + +Activer l'environment: + +```bash +source activate jupyter_docs +``` + +Construire les docs: + +```bash +make clean +make html +``` + +Les docs seront construit dans `build/html`. Ils peuvent être vus dans `build/html/index.html` ou en démarrant le serveur HTTP puis en naviguant sur `0.0.0.0:8000` dans votre navigateur web. +```bash +python3 -m http.server +``` + diff --git a/README.md b/README.md index c94091340..f5e1fd780 100644 --- a/README.md +++ b/README.md @@ -1,28 +1,107 @@ # Jupyter -Jupyter metapackage for installation and docs. +*Read this in other languages: [English](README.md), [Español](README.es-ES.md), [Português](README.pt-BR.md), [Français](README.fr-FR.md)* -## Running the docs locally -First navigate to the `/docs` directory and create a `conda` environment: +Jupyter metapackage for installation and documents + +## Documentation structure + +This documentation uses the [Sphinx](https://sphinx-doc.org) documentation engine. + +The documentation is located in the `docs/source` folder. When you build the documentation, it will be placed in the `docs/build` folder. +It is written in a combination of [reStructuredText](https://docutils.sourceforge.io/rst.html) and [MyST Markdown](https://myst-parser.readthedocs.io/). + +## Build the documentation locally + +There are a few ways to build the documentation; see below for instructions: + +### Build the documentation automatically with `nox` + +The easiest way to build the documentation locally is by using the [`nox` command line tool](https://nox.thea.codes/). This tool makes it easy to automate commands in a repository, and we have included a `docs` command to quickly install the dependencies and build the documentation. + +To build and preview the site locally, follow these steps: + +1. **Clone this repository**. + + ```console + $ git clone https://github.com/jupyter/jupyter + $ cd jupyter + ``` +2. **Install `nox`** + + ```console + $ pip install nox + ``` +3. **Run the `docs` command** + + ```console + $ nox -s docs + ``` + +This will install the needed dependencies in a virtual environment using `pip`. +It will then place the documentation in the `docs/build/html` folder. +You may explore these HTML files in order to preview the site. + +#### Create a live server to automatically preview changes + +There is another `nox` command that will do the above, and also create a live server that watches your source files for changes, and auto-builds the website any time a change is made. + +To start this live server, use the following `nox` command: + +```console +$ nox -s docs-live +``` + +When the build is finished, go to the URL that is displayed. It should show a live preview of your documentation. + +To stop serving the website, press **`Ctrl`**-`C` in your terminal + +### Build the documentation manually + +To build the documentation manually, follow these steps: + +First, install [the `miniconda` Python distribution](https://conda.io/miniconda.html). + +Next, navigate to the `/docs` directory and create a `conda` environment: ```bash -conda env create -f environment.yml -``` +conda env create -f environment.yml +``` Activate the environment: ```bash -source activate jupyter_docs +source activate jupyter_docs ``` -Build the docs: +**Build the docs** using Sphinx with the following commands: ```bash -make clean +make clean make html ``` -The docs will be built in `build/html`. They can be viewed by starting an HTTP server and navigating to `0.0.0.0:8000` in your web browser. +The docs will be built in `build/html`. They can be viewed by opening `build/html/index.html` or starting an HTTP server and navigating to `0.0.0.0:8000` in your web browser. + ```bash python3 -m http.server ``` + +## Releasing the jupyter metapackage + +Anyone with push access to this repo can make a release +of the Jupyter metapackage (this happens very rarely). +We use [tbump][] to publish releases. + +tbump updates version numbers and publishes the `git tag` of the version. +[Our GitHub Actions](https://github.com/jupyter/jupyter/actions) +then build the releases and publish them to PyPI. + +The steps involved: + +1. Install tbump: `pip install tbump` +2. Tag and publish the release `tbump $NEW_VERSION`. + +That's it! + +[tbump]: https://github.com/your-tools/tbump diff --git a/README.pt-BR.md b/README.pt-BR.md new file mode 100644 index 000000000..f03503b38 --- /dev/null +++ b/README.pt-BR.md @@ -0,0 +1,30 @@ +# Jupyter + +*Ler em outros idiomas: [English](README.md), [Español](README.es-ES.md), [Português](README.pt-BR.md), [Français](README.fr-FR.md)* + +Metapacote de Jupyter para instalação e documentação. + +## Executando os documentos localmente +Primeiro navegue até o diretório `/docs` e crie um ambiente `conda`: + +```bash +conda env create -f environment.yml +``` + +Ative o ambiente: + +```bash +source activate jupyter_docs +``` + +Construa a documentação: + +```bash +make clean +make html +``` + +A documentação será construida em `build/html`. Pode ser vista em `build/html/index.html` ou inicando um servidor HTTP e navegando para `0.0.0.0:8000` no seu navegador web. +```bash +python3 -m http.server +``` diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 000000000..86c88c328 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,10 @@ +# Security Policy + +## Reporting a Vulnerability + +All IPython and Jupyter security are handled via security@ipython.org. +You can find more information on the Jupyter website. https://jupyter.org/security + +## Tidelift + +You can report security concerns for IPython via the [Tidelift platform](https://tidelift.com/security). diff --git a/docs/.tx/config b/docs/.tx/config new file mode 100644 index 000000000..69b372c4d --- /dev/null +++ b/docs/.tx/config @@ -0,0 +1,123 @@ +[main-po--master] +host = https://www.transifex.com + +[jupyter-meta-documentation.contrib_docs-po--master] +file_filter = source/locale//LC_MESSAGES/contrib_docs.po +source_file = source/locale/en/LC_MESSAGES/contrib_docs.po +source_lang = en +type = PO + +[jupyter-meta-documentation.releases-po--master] +file_filter = source/locale//LC_MESSAGES/releases.po +source_file = source/locale/en/LC_MESSAGES/releases.po +source_lang = en +type = PO + +[jupyter-meta-documentation.ipython-po--master] +file_filter = source/locale//LC_MESSAGES/ipython.po +source_file = source/locale/en/LC_MESSAGES/ipython.po +source_lang = en +type = PO + +[jupyter-meta-documentation.community-po--master] +file_filter = source/locale//LC_MESSAGES/community.po +source_file = source/locale/en/LC_MESSAGES/community.po +source_lang = en +type = PO + +[jupyter-meta-documentation.install-kernel-po--master] +file_filter = source/locale//LC_MESSAGES/install-kernel.po +source_file = source/locale/en/LC_MESSAGES/install-kernel.po +source_lang = en +type = PO + +[jupyter-meta-documentation.developer-docs-po--master] +file_filter = source/locale//LC_MESSAGES/developer-docs.po +source_file = source/locale/en/LC_MESSAGES/developer-docs.po +source_lang = en +type = PO + +[jupyter-meta-documentation.contributor-po--master] +file_filter = source/locale//LC_MESSAGES/contributor.po +source_file = source/locale/en/LC_MESSAGES/contributor.po +source_lang = en +type = PO + +[jupyter-meta-documentation.architecture-po--master] +file_filter = source/locale//LC_MESSAGES/architecture.po +source_file = source/locale/en/LC_MESSAGES/architecture.po +source_lang = en +type = PO + +[jupyter-meta-documentation.reference-po--master] +file_filter = source/locale//LC_MESSAGES/reference.po +source_file = source/locale/en/LC_MESSAGES/reference.po +source_lang = en +type = PO + +[jupyter-meta-documentation.install-po--master] +file_filter = source/locale//LC_MESSAGES/install.po +source_file = source/locale/en/LC_MESSAGES/install.po +source_lang = en +type = PO + +[jupyter-meta-documentation.projects-po--master] +file_filter = source/locale//LC_MESSAGES/projects.po +source_file = source/locale/en/LC_MESSAGES/projects.po +source_lang = en +type = PO + +[jupyter-meta-documentation.running-po--master] +file_filter = source/locale//LC_MESSAGES/running.po +source_file = source/locale/en/LC_MESSAGES/running.po +source_lang = en +type = PO + +[jupyter-meta-documentation.glossary-po--master] +file_filter = source/locale//LC_MESSAGES/glossary.po +source_file = source/locale/en/LC_MESSAGES/glossary.po +source_lang = en +type = PO + +[jupyter-meta-documentation.sphinx-po--master] +file_filter = source/locale//LC_MESSAGES/sphinx.po +source_file = source/locale/en/LC_MESSAGES/sphinx.po +source_lang = en +type = PO + +[jupyter-meta-documentation.content-quickstart-po--master] +file_filter = source/locale//LC_MESSAGES/content-quickstart.po +source_file = source/locale/en/LC_MESSAGES/content-quickstart.po +source_lang = en +type = PO + +[jupyter-meta-documentation.contents-po--master] +file_filter = source/locale//LC_MESSAGES/contents.po +source_file = source/locale/en/LC_MESSAGES/contents.po +source_lang = en +type = PO + +[jupyter-meta-documentation.tryjupyter-po--master] +file_filter = source/locale//LC_MESSAGES/tryjupyter.po +source_file = source/locale/en/LC_MESSAGES/tryjupyter.po +source_lang = en +type = PO + +[jupyter-meta-documentation.use-cases-po--master] +file_filter = source/locale//LC_MESSAGES/use-cases.po +source_file = source/locale/en/LC_MESSAGES/use-cases.po +source_lang = en +type = PO + +[jupyter-meta-documentation.development_guide-po--master] +file_filter = source/locale//LC_MESSAGES/development_guide.po +source_file = source/locale/en/LC_MESSAGES/development_guide.po +source_lang = en +type = PO + +[jupyter-meta-documentation.migrating-po--master] +file_filter = source/locale//LC_MESSAGES/migrating.po +source_file = source/locale/en/LC_MESSAGES/migrating.po +source_lang = en +type = PO + diff --git a/docs/doc-requirements.txt b/docs/doc-requirements.txt new file mode 100644 index 000000000..96e0108d5 --- /dev/null +++ b/docs/doc-requirements.txt @@ -0,0 +1,7 @@ +sphinx>=3.1 +sphinx-intl +myst_parser +nbsphinx +pydata-sphinx-theme +sphinxext-rediraffe +sphinx-design diff --git a/docs/environment.yml b/docs/environment.yml index 64da48c01..8357487f9 100644 --- a/docs/environment.yml +++ b/docs/environment.yml @@ -1,8 +1,5 @@ name: jupyter_docs dependencies: -- sphinx_rtd_theme -- pip: - - sphinx - - recommonmark - - nbsphinx - - jupyter_sphinx_theme==0.0.6 + - python=3.11 + - pip: + - -r doc-requirements.txt diff --git a/docs/source/_static/_images/favicon.png b/docs/source/_static/_images/favicon.png new file mode 100644 index 000000000..7d1416e26 Binary files /dev/null and b/docs/source/_static/_images/favicon.png differ diff --git a/docs/source/_static/_images/jupyter_software_diagram_alpha.png b/docs/source/_static/_images/jupyter_software_diagram_alpha.png new file mode 100644 index 000000000..a99a98fa2 Binary files /dev/null and b/docs/source/_static/_images/jupyter_software_diagram_alpha.png differ diff --git a/docs/source/_static/_images/jupytercad-screenshot.jpg b/docs/source/_static/_images/jupytercad-screenshot.jpg new file mode 100644 index 000000000..58f2c4e2a Binary files /dev/null and b/docs/source/_static/_images/jupytercad-screenshot.jpg differ diff --git a/docs/source/_static/_images/jupyterlab.png b/docs/source/_static/_images/jupyterlab.png new file mode 100644 index 000000000..20a34cd2d Binary files /dev/null and b/docs/source/_static/_images/jupyterlab.png differ diff --git a/docs/source/_static/_images/notebook_insulin_lab_small.png b/docs/source/_static/_images/notebook_insulin_lab_small.png new file mode 100644 index 000000000..6eb845d20 Binary files /dev/null and b/docs/source/_static/_images/notebook_insulin_lab_small.png differ diff --git a/docs/source/_static/_images/repos_map.svg b/docs/source/_static/_images/repos_map.svg deleted file mode 100644 index fea7652e5..000000000 --- a/docs/source/_static/_images/repos_map.svg +++ /dev/null @@ -1,1208 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - image/svg+xml - - - - - - - - - ipython - - - - nbformat - - - - traitlets - - - - jupyter_client - - - - notebook - - - - jupyter_core - - - - jupyter_console - - - - qtconsole - - - - ipywidgets - - - - nbgrader - - - - jupyterhub - - - - tmpnb - - - - ipykernel - - - - - - - - - - - - - - - - Everythingdepends on: - Config system andwidget base layer - Python execution,magics, andipython terminal interface Kernel communication machinery - - - jupyter - - - jupyter command, config file handling and filesystem locations Messaging ipynb file loading, saving, format version migration and trust Jupyter terminal application Jupyter Qtconsole application Jupyter notebook application Metapackage and overview docs Notebooks for multiple users with logins Notebooks for multiple users with no logins Notebooks as assignments - creating and grading Interactive widgets - nbconvert - - - - - - - - Convert notebook files to other formats - - - - - nbviewer - - - HTML views of notebooks on the web - diff --git a/docs/source/_static/custom.css b/docs/source/_static/custom.css index 5986288fd..de36bfe24 100644 --- a/docs/source/_static/custom.css +++ b/docs/source/_static/custom.css @@ -1,3 +1,27 @@ +/* -- theme ------------------------------------------------------------ */ + +:root { + /* colors from from https://github.com/jupyter/jupyter.github.io/blob/master/_sass/settings/_colors.scss */ + --color-dark-orange: 197, 84, 11; + --color-dark-grey: 77, 77, 77; + --pst-color-link: var(--color-dark-orange); + + --pst-color-h1: var(--color-dark-grey); + --pst-color-h2: var(--color-dark-grey); + --pst-color-h3: var(--color-dark-grey); + --pst-color-h4: var(--color-dark-grey); + --pst-color-h5: var(--color-dark-grey); + --pst-color-h6: var(--color-dark-grey); + + --pst-color-active-navigation: var(--color-dark-orange); +} + +/* -- navbar ------------------------------------------------------------- */ + +.navbar-brand { + padding: 0.4em; +} + /* -- topics ------------------------------------------------------------- */ div.topic { @@ -20,3 +44,32 @@ p.first.admonition-title { color: #ffffff; } + +/* Front page table styling */ + +.front-page-table td > p { + margin-bottom: 0em; +} + +.front-page-table td > p:last-child { + font-style: italic; +} + +.front-page-table a.reference { + font-size: 1.3em; +} + +.front-page-table.table td, .front-page-table.table th { + border: none; + padding-top: .3em; + padding-bottom: .3em; +} + +div.sd-card ul.simple { + list-style: none; + padding-left: 1em; +} + +.bd-content .sd-card .sd-card-header { + background-color: var(--pst-color-surface); +} diff --git a/docs/source/_templates/index.html b/docs/source/_templates/index.html deleted file mode 100644 index 3562e5e92..000000000 --- a/docs/source/_templates/index.html +++ /dev/null @@ -1,92 +0,0 @@ -{% extends "layout.html" %} -{% set title = _('Overview') %} -{% block body %} -

{{ _('Welcome') }}

- - -

{%trans%}Start Here{%endtrans%}

- - - - - - - - -
-

{%trans%}Jupyter Notebook Quickstart{%endtrans%}
- {%trans%}Try the notebook{%endtrans%}

-

{%trans%}Architecture{%endtrans%}
- {%trans%}What is Jupyter?{%endtrans%}

-

{%trans%}Narratives and Use Cases{%endtrans%}
- {%trans%}Narratives of common deployment scenarios{%endtrans%}

-

{%trans%}IPython{%endtrans%}
- {%trans%}An interactive Python kernel and REPL{%endtrans%}

-

{%trans%}Installation, Configuration, and Usage{%endtrans%}
- {%trans%}Documentation for users{%endtrans%}

- 		-

{%trans%}Community{%endtrans%}
- {%trans%}Sustainability and growth{%endtrans%}

-

{%trans%}Contributor Guides{%endtrans%}
- {%trans%}How to contribute to the projects{%endtrans%}

-

{%trans%}Release Notes{%endtrans%}
- {%trans%}New features, upgrades, deprecation notes, and bug fixes{%endtrans%}

-

{%trans%}Reference{%endtrans%}
- {%trans%}APIs{%endtrans%}

-

{%trans%}Contents{%endtrans%}
- {%trans%}Full table of contents{%endtrans%}

-
- -

{%trans%}Project Documentation{%endtrans%}

- - - -
-

Jupyter User Interfaces

- {%trans%}Jupyter Notebook{%endtrans%}
- {%trans%}Jupyter console{%endtrans%}
- {%trans%}Qt console{%endtrans%}

-

JupyterHub

- {%trans%}JupyterHub{%endtrans%}
- {%trans%}configurable HTTP proxy{%endtrans%}
- {%trans%}dockerspawner{%endtrans%}
- {%trans%}ldapauthenticator{%endtrans%}
- {%trans%}oauthenticator{%endtrans%}
- {%trans%}sudospawner{%endtrans%}

-

Education

- {%trans%}nbgrader{%endtrans%}

-

Conversion and Formatting

- {%trans%}nbconvert{%endtrans%}
- {%trans%}nbformat{%endtrans%}

-

Kernels

- {%trans%}IPython{%endtrans%}
- {%trans%}IRkernel{%endtrans%}
- {%trans%}IJulia{%endtrans%}
- {%trans%}Community maintained kernels{%endtrans%}


- 		-

IPython

- {%trans%}IPython{%endtrans%}
- {%trans%}ipykernel{%endtrans%}
- {%trans%}ipyparallel{%endtrans%}

-

Architecture

- {%trans%}jupyter_client{%endtrans%}
- {%trans%}jupyter_core{%endtrans%}

-

Deployment

- {%trans%}docker-stacks{%endtrans%}
- {%trans%}ipywidgets{%endtrans%}
- {%trans%}jupyter-drive{%endtrans%}
- {%trans%}jupyter-sphinx-theme{%endtrans%}
- {%trans%}kernel_gateway{%endtrans%}
- {%trans%}nbviewer{%endtrans%}
- {%trans%}tmpnb{%endtrans%}
- {%trans%}traitlets{%endtrans%}

-

JupyterLab

- {%trans%}jupyter-js-notebook{%endtrans%}
- {%trans%}jupyter-js-phosphide{%endtrans%}
- {%trans%}jupyter-js-plugins{%endtrans%}
- {%trans%}jupyter-js-services{%endtrans%}
- {%trans%}jupyter-js-ui{%endtrans%}
- {%trans%}jupyter-js-utils{%endtrans%}

-
- -{% endblock %} diff --git a/docs/source/_templates/layout.html b/docs/source/_templates/layout.html deleted file mode 100644 index b7f9cbe70..000000000 --- a/docs/source/_templates/layout.html +++ /dev/null @@ -1,26 +0,0 @@ -{% extends "!layout.html" %} - -{# Custom CSS overrides #} -{% set bootswatch_css_custom = ['_static/custom.css'] %} - -{% block relbar1 %} -
-jupyter -
-{{ super() }} -{% endblock %} - -{% block footer %} -
- -
-{{ super() }} -{% endblock %} \ No newline at end of file diff --git a/docs/source/_templates/navbar.html b/docs/source/_templates/navbar.html deleted file mode 100644 index 981043269..000000000 --- a/docs/source/_templates/navbar.html +++ /dev/null @@ -1,45 +0,0 @@ -
-
-
- - - - {%- block sidebarlogo %} - {%- if logo %}{%- endif %} - {%- endblock %} - {% if theme_navbar_title -%}{{ theme_navbar_title|e }}{%- else -%}{{ project|e }}{%- endif -%} - - {{ version|e }} -
- -
-
    - {% if theme_navbar_links %} - {%- for link in theme_navbar_links %} -
  • {{ link[0] }}
    • - {%- endfor %} - {% endif %} - {% block navbarextra %} - {% endblock %} - {% if theme_source_link_position == "nav" %} - - {% endif %} -
- - {% block navbarsearch %} - {% include "navbarsearchbox.html" %} - {% endblock %} - {% if theme_navbar_sidebarrel %} - {% block sidebarrel %} -
    - {% include "relations.html" %} -
- {% endblock %} - {% endif %} -
-
-
\ No newline at end of file diff --git a/docs/source/_templates/sidebartoc.html b/docs/source/_templates/sidebartoc.html deleted file mode 100644 index b64bec6bb..000000000 --- a/docs/source/_templates/sidebartoc.html +++ /dev/null @@ -1 +0,0 @@ -{{ toctree(maxdepth=2, collapse=True, includehidden=theme_globaltoc_includehidden|tobool) }} \ No newline at end of file diff --git a/docs/source/architecture/content-architecture.rst b/docs/source/architecture/content-architecture.rst deleted file mode 100644 index 20021a8b4..000000000 --- a/docs/source/architecture/content-architecture.rst +++ /dev/null @@ -1,8 +0,0 @@ -Architecture Guides -=================== - -.. toctree:: - :maxdepth: 1 - - how_jupyter_ipython_work - visual_overview \ No newline at end of file diff --git a/docs/source/architecture/figs/notebook_components.png b/docs/source/architecture/figs/notebook_components.png deleted file mode 100644 index 3b010050a..000000000 Binary files a/docs/source/architecture/figs/notebook_components.png and /dev/null differ diff --git a/docs/source/architecture/figs/notebook_components.svg b/docs/source/architecture/figs/notebook_components.svg deleted file mode 100644 index 3b51ed2ed..000000000 --- a/docs/source/architecture/figs/notebook_components.svg +++ /dev/null @@ -1,596 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - image/svg+xml - - - - - - - - - Browser - - - - Notebookserver - - - - Kernel - - - - Notebookfile - - - - - - User - - - - - - - - - - ØMQ - - - - - - - HTTP &Websockets - - - - - - - - - - - - - - - - diff --git a/docs/source/architecture/figs/other_kernels.png b/docs/source/architecture/figs/other_kernels.png deleted file mode 100644 index 067e45d4d..000000000 Binary files a/docs/source/architecture/figs/other_kernels.png and /dev/null differ diff --git a/docs/source/architecture/figs/other_kernels.svg b/docs/source/architecture/figs/other_kernels.svg deleted file mode 100644 index f57da8dd8..000000000 --- a/docs/source/architecture/figs/other_kernels.svg +++ /dev/null @@ -1,332 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - image/svg+xml - - - - - - - - - $LANGUAGEexecution - - - IPythonJSON, ØMQmachinery - WrapperKernel - - - - - - - - - - - - - - - $LANGUAGEexecution&JSON, ØMQmachinery - - - - - - NativeKernel - - diff --git a/docs/source/architecture/how_jupyter_ipython_work.rst b/docs/source/architecture/how_jupyter_ipython_work.rst deleted file mode 100644 index bc760aaff..000000000 --- a/docs/source/architecture/how_jupyter_ipython_work.rst +++ /dev/null @@ -1,124 +0,0 @@ -How IPython and Jupyter Notebook work -===================================== - -.. contents:: Contents - :local: - -Abstract --------- -This section focuses on IPython and Jupyter notebook and how they interact. -When we discuss ``IPython``, we talk about two fundamental roles: - -- Terminal IPython as the familiar REPL -- The IPython kernel that provides computation and communication with the - frontend interfaces, like the notebook - -Jupyter Notebook and its flexible interface extends the notebook beyond code -to visualization, multimedia, collaboration, and more. - -Terminal IPython ----------------- - -When you type ``ipython``, you get the original IPython interface, running in -the terminal. It does something like this:: - - while True: - code = input(">>> ") - exec(code) - -Of course, it's much more complex, because it has to deal with multi-line -code, tab completion using :mod:`readline`, magic commands, and so on. But the -model is like code example: prompt the user for some code, and when they've -entered it, execute it in the same process. This model is often called a -:term:`REPL`, or Read-Eval-Print-Loop. - -The IPython Kernel ------------------- - -All the other interfaces —- the Notebook, the Qt console, ``ipython console`` -in the terminal, and third party interfaces —- use the IPython Kernel. The -IPython Kernel is a separate process which is responsible for running user -code, and things like computing possible completions. Frontends, like the -notebook or the Qt console, communicate with the IPython Kernel using JSON -messages sent over `ZeroMQ `_ sockets; the protocol used -between the frontends and the IPython Kernel is described in -:ref:`jupyterclient:messaging`. - -The core execution machinery for the kernel is shared with terminal IPython: - -.. image:: figs/ipy_kernel_and_terminal.png - -A kernel process can be connected to more than one frontend simultaneously. In -this case, the different frontends will have access to the same variables. - -.. TODO: Diagram illustrating this? - -This design was intended to allow easy development of different frontends -based on the same kernel, but it also made it possible to support new -languages in the same frontends, by developing kernels in those languages, and -we are refining IPython to make that more practical. - -Today, there are two ways to develop a kernel for another language. Wrapper -kernels reuse the communications machinery from IPython, and implement only -the core execution part. Native kernels implement execution and communications -in the target language: - -.. image:: figs/other_kernels.png - -Wrapper kernels are easier to write quickly for languages that have good -Python wrappers, like `octave_kernel `_, -or languages where it's impractical to implement the communications machinery, -like `bash_kernel `_. Native kernels -are likely to be better maintained by the community using them, like -`IJulia `_ or -`IHaskell `_. - -.. seealso:: - - :ref:`jupyterclient:kernels` - - :ref:`Kernels ` - -Notebooks ---------- - -The Notebook frontend does something extra. In addition to running your code, -it stores code and output, together with markdown notes, in an editable -document called a notebook. When you save it, this is sent from your browser -to the notebook server, which saves it on disk as a JSON file with a -``.ipynb`` extension. - -.. image:: figs/notebook_components.png - -The notebook server, not the kernel, is responsible for saving and loading -notebooks, so you can edit notebooks even if you don't have the kernel for -that language—you just won't be able to run code. The kernel doesn't know -anything about the notebook document: it just gets sent cells of code to -execute when the user runs them. - -Exporting notebooks to other formats ------------------------------------- - -The Nbconvert tool in Jupyter converts notebook files to other formats, such -as HTML, LaTeX, or reStructuredText. This conversion goes through a series of -steps: - -.. image:: figs/nbconvert.png - -1. Preprocessors modify the notebook in memory. E.g. ExecutePreprocessor runs - the code in the notebook and updates the output. -2. An exporter converts the notebook to another file format. Most of the - exporters use templates for this. -3. Postprocessors work on the file produced by exporting. - -The `nbviewer `_ website uses nbconvert with the -HTML exporter. When you give it a URL, it fetches the notebook from that URL, -converts it to HTML, and serves that HTML to you. - -IPython.parallel ----------------- - -IPython also includes a parallel computing framework, -`IPython.parallel `_. This -allows you to control many individual engines, which are an extended version -of the IPython kernel described above. diff --git a/docs/source/architecture/visual_overview.rst b/docs/source/architecture/visual_overview.rst deleted file mode 100644 index b83efdfb3..000000000 --- a/docs/source/architecture/visual_overview.rst +++ /dev/null @@ -1,9 +0,0 @@ -A Visual Overview of Projects -============================= - -**A high level visual overview of project relationships** - - -.. image:: ../_static/_images/repos_map.svg - :width: 75% - :alt: Architecture diagram of project relationships \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2019-april.md b/docs/source/community/community-call-notes/2019-april.md new file mode 100644 index 000000000..74c4a83c1 --- /dev/null +++ b/docs/source/community/community-call-notes/2019-april.md @@ -0,0 +1,117 @@ +# All-Jupyter Community Video Call - April 2019 + +**Date:** 30 April 2019 at 9am PST (your [timezome](http://arewemeetingyet.com/Los%20Angeles/2019-04-30/09:00/Jupyter%20Community%20Call)) + +**Video-conference link:** https://calpoly.zoom.us/my/jupyter + + +## Welcome to the Team Meeting + +Hello! + +The purpose of these monthly video conference calls is to share and demonstrate the awesome things happening in Jupyter community. We invite **anyone** to present their work, engage in discussion, or just sit in and listen. Whether you have a new [lab extension](https://github.com/jupyterlab) you've created, a new [jupyterhub deployment](https://github.com/jupyterhub) you're excited about, or an [nteract papermill](https://github.com/nteract) pipeline powering your business, we'd love to hear about it! And, we'll record and publish these calls on YouTube for anyone unable to attend. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make *short* announcements (without a need for discussion). This is also a great place to give shout-outs to contributors! We’ll read through these at the beginning of the meeting. + +* [x] Shout-out to @GrahamDumpleton for continued well-researched improvements to security (e.g., https://github.com/jupyter/docker-stacks/pull/845) [name=Peter Parente] +* [x] Some initial work on enabling Jupyter documentation translation is happening in https://github.com/jupyter/docker-stacks/issues/827. If you would like to contribute a translation, review one in progress, or help document the process itself, please reach out in the issue. Thanks to @michiboo (Micky), @Nico769 (Nicola), and @Allanfs (Allan) for starting translations! [name=Peter Parente] +* [x] [Work](https://discourse.jupyter.org/t/aws-integration-work/864) is being done to use BinderHub fully in AWS (hosted docker registry, ECR, and hosted git repository, CodeCommit are the current areas). [name=Chico Venancio] +* [x] JupyterLab 1.0.0a3 has been released since our last call. There are a ton of updates. One thing I specifically want to give a shout out to is the document search feature that Andrew Schlaepfer built which allows building custom search functionality for different document types. Install the new version to take it for a spin: `pip install --pre jupyterlab` [name=Darian] +* [x] RISE 5.5.0 was released, more info about the release in this blogpost: http://damianavila.github.io/blog/posts/rise-550-is-out.html [name=Damián] +* [x] A big shout-out to Paul Ivanov for helping organize a "Jupyter Open Studio Day" at Bloomberg in SF. Lots of great people came, shared ideas, learned, and generally celebrated open source stuff! [name=Chris H (but I won't be able to attend the meeting)] +* [x] (a few quick shout-outs from Chris) Papermill 1.0 is released! Congrats to the nteract community for releasing papermill 1.0, a tool for parametizing / pipelining notebooks. [See the Discourse for some more links](https://discourse.jupyter.org/t/release-of-papermill-1-0/875). [name=Chris H (but I won't be able to attend the meeting)] +* [x] Many thanks to @KirstieJane and @betatim for improving the contributing documentation in repo2docker ([link to one PR on this](https://github.com/jupyter/repo2docker/pull/655)) [name=Chris H (but I won't be able to attend the meeting)] +* [x] IPython 7.5 out ! (mostly bugfixes) [name=Matthias, at airport so will stay muted] (Shout out to Matthias for this too!) +* [x] Matthias,Paul,Carol... are at PyCon for a tutorial (Thursday), and have Jupyter stickers ! [name=Matthias, at airport so will stay muted] +* [ ] add item here [name=add your name] + +## Agenda Items + +Add your potential agenda item here **24 hours before** the meeting at the latest. We will reorganize the agenda so that it fits in the 60m meeting slot. + +* [x] Updates from the nteract project [name=Safia Abdalla] + - New release of the cross-platform nteract desktop app is out. + - papermill v1.0 is released. +* [x] Jupyter at the University of Edinburgh, a walkthrough of the Noteable service [name=James Slack] + * Overview of what's happening at University of Edinburgh + * Large support teams. + * Very open mindset. + * http://open.ed.ac.uk/ + * How Jupyter came to the University + * Small scale adoption to start + * Students were installing Jupyter on university computers. + * Make Jupyter a shared central service. + * JupyterHub service university wide for use in education. + * Pilot phase of [Noteable](https://noteable.edina.ac.uk/). + * 6 courses with 6 different schools (~600 students). + * Political science, art, computer science... + * Integrated with nbgrader. + * [Jupyter Community Hackathon on NBGrader in Edinburgh](https://thinking.is.ed.ac.uk/noteable/2018/12/07/jupyter-community-workshop-proposal-nbgrader-and-jupyter-in-teaching/). + * Questions and comments: + * Connections or interactions with Canadian group? https://syzygy.ca [name=Lindsey Heagy] + * Is this running in the cloud or university server? [name=Anton Akhmerov] + * University server + * Have you explored Binderhub? [name=Chico Vernancio] + * BinderHub now can run with "auth" and persistent storage, see https://github.com/jupyterhub/binderhub/issues/794 for more details and a live demo (ask @betatim if you have more questions) +* [ ] Introducing the rewrite of [jupyter-sphinx](https://github.com/jupyter-widgets/jupyter-sphinx/) (example [here](https://adaptive.readthedocs.io/en/latest/tutorial/tutorial.Learner2D.html)) and a discussion about markup format in the notebooks (https://github.com/jupyter/nbformat/issues/80) [name=Anton Akhmerov] + * Publishing documents with complex content and computed output. + +- Questions/Comments: + - [name=matthias (can't speak)]: I'd love to merge that with ipython built-in sphinx-ext, /(deprecate sphinx-ext potentially as it's not well maintained ([sphix-ext docs](https://ipython.readthedocs.io/en/stable/sphinxext.html)) + +* [ ] Quantum Chemistry Database exploration with Jupyter through the [QCArchive project](https://qcarchive.molssi.org), [name=Daniel Smith]. + * The Molecular Sciences Software Institute + * NSF funded. + * Designed to serve and enhance software development efforts of broad field of computational molecular science. + * 8 universities represented on Board of Directors + * Github org: https://github.com/MolSSI + * https://molssi.org + * [QCFractal](https://github.com/MolSSI/QCFractal) + * Join our [Slack](https://join.slack.com/t/qcdb/shared_invite/enQtNDIzNTQ2OTExODk0LWM3OTgxN2ExYTlkMTlkZjA0OTExZDlmNGRlY2M4NWJlNDlkZGQyYWUxOTJmMzc3M2VlYzZjMjgxMDRkYzFmOTE) to get involved. + * Questions/comments: + * Is this user created content or hostesd content? + * Completely user created. + * +* [ ] May 13 & 14 [W4A Hackathon on Accessibility of JupyterLab](https://groups.google.com/forum/#!topic/jupyter/trUVgNj0deU) +* [ ] Add your item here [name=and your name] + +## University of Edinburgh materials and contact: + +* Contact james.slack@ed.ac.uk +* Noteable - https://noteable.edina.ac.uk/ +* Blog https://thinking.is.ed.ac.uk/noteable/ +* nbgrader Hackathon - http://edin.ac/2SGmzNu +* Presentation - https://edin.ac/2PBJc1T + +## In Attendance + +Name / Institution / Github Handle + +* Zach / Jupyter Cal Poly / @Zsailer +* Pete / Thorn / @parente +* James Slack / University of Edinburgh / @jamesaslack +* Anton Akhmerov / TU Delft / @akhmerov +* Peter Rose / UC San Diego / @pwrose +* A. T. Darian / Two Sigma / @afshin +* Ward Harold / Google / @wkharold +* Damián Avila / / @damianavila +* Chico Venancio / [BMC Group K.K.](http://www.bmc-group.co.jp/en/home/) / @chicocvenancio +* Eric Lesch / [BMC Group K.K.](http://www.bmc-group.co.jp/en/home/) / @EricLesch +* James Munroe / Memorial University of Newfoundland / @jmunroe +* Lindsey Heagy / UC Berkeley / @lheagy +* Daniel Smith / The Molecular Sciences Software Institute / @dgasmith +* Michael Milligan / U. Minnesota/MSI / @mbmilligan +* Kevin Bates / IBM / @kevin-bates +* Cindy Wu / experiment.com / @cindywu +* Joe Hamman / NCAR / @jhamman +* Nick Bollweg / GTRI / @bollwyvl +* Tom Baldwin / Cascade Data Labs / @baldwint +* Pete Blois / Google Colab / @blois +* Ana Ruvalcaba / Cal Poly, San Luis Obispo/Jupyter / @ruv7 +* Tim Head / Project Binder / Zurich / @betatim +* Matthias Bussonnier / Jupyter Project / @carreau +* Tim George / Cal Poly, San Luis Obispo/Jupyter / @tgeorgeux diff --git a/docs/source/community/community-call-notes/2019-august.md b/docs/source/community/community-call-notes/2019-august.md new file mode 100644 index 000000000..d2c02887e --- /dev/null +++ b/docs/source/community/community-call-notes/2019-august.md @@ -0,0 +1,64 @@ +# Jupyter Community Call + +## August 27th, 2019 + +**Date:** August 27, 2019, at 9am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2019-08-27/09:00/Jupyter%20Community%20Call)) + +**Link:** [Youtube Video](https://youtu.be/k1-1XAML9fc) + +**Welcome!** + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make *short* announcements (without a need for discussion). + +* [x] Tracking Jupyter Newsletter, [22nd edition](https://tinyletter.com/TrackingJupyter/letters/tracking-jupyter-newsletter-the-twenty-second). Thank you, Tony Hirst! +* [x] JupyterLab 1.1.0rc0 is up on PyPI and conda-forge. Please test! JupyterLab 1.1.0 will be released tomorrow. + * `pip install --pre jupyterlab==1.1.0rc0` or + * `conda install -c conda-forge/label/prerelease-jupyterlab jupyterlab=1.1.0rc0` +* [ ] [name=yournamehere] + +## Agenda Items + +Add agenda items here **before** the meeting. We will reorganize the agenda so that it fits in the 60m meeting slot. + +* [x] [name=Jupyter Cal Poly Intern Team] [Rich Text JupyterLab extension](https://github.com/jupytercalpoly/jupyterlab-richtext-mode) +* [x] [name=Jupyter Cal Poly Intern Team] [Python Package Installer JupyterLab extension](https://github.com/jupytercalpoly/jupyterlab-pkginstaller) +* [x] [name=Tony Fast] Gist to Binder + * https://gist.github.com/Zsailer/6da0dc3c97ec873685b7fe58e52d36d7 + * People say reproducibility is hard. + * User mybinder.org to generate a live notebook from a Gist. + * dependencies in requirement.txt lead to a faster build. +* [x] [name=Saul Shanabrook] [JupyterLab Rich Context Extensions](https://discourse.jupyter.org/t/jupyterlab-rich-context-extensions/1350) + * [ ] [Data registry](https://github.com/jupyterlab/jupyterlab-data-explorer) with [HDF5 Viewer](https://github.com/telamonian/jupyterlab-hdf/) + * [ ] It's meant to make it easier to create new extensions in JupyterLab that deal with different data formats. If you have a data viewer extension, you shouldn't care if the data came from a file or from a notebook output or a database, you just want to be able to render a certain format. + * [ ] Able to visualize HDF5 datasets using this extension too! + * [ ] [Metadata/linked data service](https://github.com/jupyterlab/jupyterlab-data-explorer) + +## Attendees + + +If you are joining the Jupyter Community Call, sign in below so we know who was here. + +- Zach | Jupyter Cal Poly | @Zsailer | +- Derek | Jupyter Cal Poly (Intern) | @dLamSlo8 | +- Isabela | Jupyter Cal Poly (Intern) | @isabela-pf | +- Marisa | Jupyter Cal Poly (Intern) | @marisaaquilina | +- Markelle | Jupyter Cal Poly (Intern) | @markellekelly | +- Javier | Jupyter Cal Poly (Intern) | @javag97 | +- Denton | Project Drawdown | @dgentry | +- Tony | Quansight | @tonyfast | +- Chico Venancio| BMC Group K. K.| @chicocvenancio| +- Elizabeth DuPre | McGill University | @emdupre| +- Wayne Decatur | Upstate Medical University | @fomightez| +- Saul Shanabrook | Quansight | @saulshanabrook | +- Joe | Mavenomics | @quigleyj-mavenomics| +- A. T. Darian | Two Sigma | @afshin | +- Erik Sundell | Sandvik | @consideRatio | +- Kevin Bates | IBM | @kevin-bates | diff --git a/docs/source/community/community-call-notes/2019-june.md b/docs/source/community/community-call-notes/2019-june.md new file mode 100644 index 000000000..2fca5b78b --- /dev/null +++ b/docs/source/community/community-call-notes/2019-june.md @@ -0,0 +1,75 @@ + +# Jupyter Community Call + +## June 25th, 2019 + +**Date:** June 25th, 2019, at 9am PST (your [timezome](http://arewemeetingyet.com/Los%20Angeles/2019-06-25/09:00/Jupyter%20Community%20Call)) + +**Link** [Youtube Video](https://youtu.be/27pMFoJd0H4) + +**Welcome!** + + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make *short* announcements (without a need for discussion). + +* [ ] [name=willingc] Congrats again to our [newest BinderHub/JupyterHub team member, Sarah](https://discourse.jupyter.org/t/welcoming-our-new-jupyterhub-team-member-sarah/1416) :tada: +* [ ] [name=Zsailer] Welcome the new Jupyter Cal Poly Intern team. +* [ ] [name=tgeorgeux] Introduction to Rich Context Work: Metadata, Data Registry, Commenting and Annotation, Real-Time Collaboration, Telemetry. + * [Data Registry/Explorer](https://github.com/jupyterlab/jupyterlab-data-explorer) + * [Commenting](https://github.com/jupyterlab/jupyterlab-commenting) + * [Metadata](https://github.com/jupyterlab/jupyterlab-metadata-service) + * [Telemetry](https://github.com/jupyter/telemetry) +* [ ] [name=Erik Sundell] + [repo2docker](https://github.com/jupyter/repo2docker) / MyBinder.org support for git repositories with Pipfile / Pipfile.lock coming up soon I hope ;D + [repo2docker#649](https://github.com/jupyter/repo2docker/pull/649) + +* [ ] [name=yournamehere] + +## Agenda Items + +Add agenda items here **before** the meeting. We will reorganize the agenda so that it fits in the 60m meeting slot. + +* [ ] [name=kbates] Brief overview of Jupyter Enterprise Gateway + * Questions: + * Where can we find information to share with others? + * See this [post](https://blog.jupyter.org/on-demand-notebooks-with-jupyterhub-jupyter-enterprise-gateway-and-kubernetes-e8e423695cbf) + * Comments: + * Add talks to EG docs + * Check if Docker Stacks has a link to the EG docker stacks + * Add link to this demo to the EG docs +* [ ] [name=dgentry] existing system for git commit+push without requiring a forked repo? Similar to submitting homework for grading? + * nbgrader and hubshare mentioned by Zach + * [nbstripout](https://github.com/kynan/nbstripout) / [fastai-nbstripout](https://github.com/fastai/fastai-nbstripout) can play a part of making git merges more reasonable + * Ask the Jupyter education community + * [Jupyter Education Mailing List](https://jupyter.org/community) + * Check out solutions from [Gigantum](https://gigantum.com/), a tech company started out of Johns Hopkins +* [ ] [name=YourNameHere] +* [ ] [name=YourNameHere] + +## Attendees + +If you are joining the Jupyter Community Call, sign in below so we know who was here. + +- Zach | Jupyter Cal Poly | @Zsailer | +- Erik | Sandvik | @consideRatio | +- Denton | individual | @DentonGentry | +- Tim | Jupyter Cal Poly | @tgeorgeux | +- Kevin | IBM | @kevin-bates | +- Wayne | Upstate Medical University| @Fomightez | +- Dav | Gigantum | @davclark | +- Mike Trizna | Smithsonian | @MikeTrizna | +- Anton Akhmerov | TU Delft | @akhmerov | +- Markelle | Jupyter Cal Poly | | +- Carol | Jupyter | @willingc | +- Saul | Quansight | @saulshanabrook | +- Yair | Mavenomics | @YairMarcowMavenomics| +- Joe | Mavenomics | @quigleyj-mavenomics| +- Ruixin | Microsoft | @ruixinxu | \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2019-march.md b/docs/source/community/community-call-notes/2019-march.md new file mode 100644 index 000000000..418033a67 --- /dev/null +++ b/docs/source/community/community-call-notes/2019-march.md @@ -0,0 +1,114 @@ +# All-Jupyter Community Video Call - March 2019 + +**Date:** 26 March 2019 at 9am PST (your [timezome](http://arewemeetingyet.com/Los%20Angeles/2019-03-26/09:00/Jupyter%20Team%20Meeting)) + +**Video-conference link:** https://calpoly.zoom.us/my/jupyter + +[Link to prior meeting's virtual meeting report](https://paper.dropbox.com/doc/February-26-2019-Jupyter-Community-Meetings--AYQW8rw8lRF~M7gNT9WrtW4iAg-6pRznjq5hGOPcJARLFtld) + +## Welcome to the Team Meeting + +Hello! + +The purpose of these monthly video conference calls is to share and demonstrate the awesome things happening in Jupyter community. We invite **anyone** to present their work, engage in discussion, or just sit in and listen. Whether you have a new [lab extension](https://github.com/jupyterlab) you've created, a new [jupyterhub deployment](https://github.com/jupyterhub) you're excited about, or an [nteract papermill](https://github.com/nteract) pipeline powering your business, we'd love to hear about it! And, we'll record and publish these calls on YouTube for anyone unable to attend. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make *short* announcements (without a need for discussion). This is also a great place to give shout-outs to contributors! We’ll read through these at the beginning of the meeting. + +* [x] Shout out to Damian Avila for the second community docker stack: [umsimads/education-notebook](https://github.com/umsi-mads/education-notebook) [Peter Parente, jupyter/docker-stacks] +* [x] Thank you Tony Hirst for your weekly newsletter [*Tracking Jupyter*](https://tinyletter.com/TrackingJupyter) [Carol Willing, JupyterHub] +* [x] Thank you to Professor Lorena Barba at GWU for hosting the recent Jupyter team meeting [Carol Willing, JupyterHub] +* [x] Kudos, Zach Sailer et al, for kicking off the revitalization of this meeting over on the [Jupyter Discourse](https://discourse.jupyter.org/t/reviving-the-all-jupyter-community-meetings/423/11) site [Peter Parente (and everyone in attendance I suspect)] +* [x] Leave your feedback about our new all-Jupyter community call [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-community-meetings/423) +* [x] Come join us on the [Jupyter Discourse Forum](https://discourse.jupyter.org)! (in case you aren't already tired of me telling you this :-) ) + * https://discourse.jupyter.org/t/introduce-yourself/17 + * Turn off add blocker if you want to login with google or github. + +## Agenda Items + +* Let’s collect all potential agenda items here before the start of the meeting (closing time **24h before**). We will then attempt to create a coherent agenda that fits in the 60m meeting slot. If there are similar items try and group them already. + +* [x] Suggested demo: docker-stacks project now posts image build manifests back to the GitHub project wiki for inspection [Peter Parente, https://github.com/jupyter/docker-stacks/wiki, 5 minutes] +* [x] Introduction to mybinder.org, how to make a repository ready for running on mybinder.org [Tim Head, 10minutes] + * https://mybinder.org/ + * https://github.com/betatim/my-first-binder + * Lots of example repositories: https://github.com/binder-examples/ + * Not just notebooks: https://github.com/betatim/vscode-binder + * Documentation on how to specify dependencies and such https://repo2docker.readthedocs.io/en/latest/ + * Questions, comments and support: https://discourse.jupyter.org/c/questions + * Write questions you have here: + * ... + * Is it true that you personally are the only user of https://github.com/Carreau/open-with-binder ? + * If running an event/tutorial type thing with Binder, how many users should we feel comfortable sending to MyBinder vs setting up our own Z2JH infrastructure? + * By default it prevents more than 100 concurrent launches of the same repo. You can ask for more if you are nice. + * fun fact: apparently the reason this launch was slow is because somebody is teaching a "learn java" course on Binder just now and a bunch of people connected all at once https://github.com/santanche/java2learn + * Show the log dashboard :P + * sure thing: https://grafana.mybinder.org/d/fZWsQmnmz/pod-activity?refresh=1m&panelId=1&fullscreen&orgId=1 + * We'd love to figure out a funding model for binder + + +* [x] [10minutes ] Update from the nteract team [Safia]. + * Version 1.0 of papermill, notebook execution and parameterization library, will be released in early April. (https://github.com/nteract/papermill) + * Scrapbook, tool for extracting and assembling generated outputs and data from notebooks, known as scraps, will allow you to host scraps remotely on various cloud providers. (https://github.com/nteract/scrapbook) + * Plan laid out for version 1.0 of the kernel-relay, a GraphQL API for interfacing with Jupyter kernels. (https://github.com/nteract/kernel-relay) + * Effort to modularize the Data Explorer, an automatic visualization library, is underway. + * nteract is participating in Google Summer of Code (https://summerofcode.withgoogle.com/organizations/5447807656263680/) + * Questions: + * How to learn more: + * Nteract slack https://slack.nteract.io/ + * Weekly meeting on Monday Afternoon + * Where is the Data Explorer repo? +* [x] deathbeds stuff [Nick, github.com/deathbeds, 5min]. + * [lintotype](https://github.com/deathbeds/lintotype): interactive linting & formatting + * [wxyz](https://github.com/deathbeds/wxyz): some crazy widgets + * Questions: + * The SVG messed with my eyes. <3 + * Can you expand upon the "cell-id" things? + * [cell id in lintotype](https://github.com/deathbeds/lintotype/blob/4b83f784b56ef12a245c0ca92d48eb95a9b0f7da/packages/ipylintotype/src/ipylintotype/formatter.py#L116) + * [cell id in irobotframework](https://github.com/gtri/irobotframework/blob/865311e0f89e2418e253f60cd7ae50990d4d6e6a/src/irobotframework/kernel.py#L90) + * Are those supposed to be extension ? Built-in ?...? + * ready to be packaged (not yet). Some of the stuff could go into ipywidgets +* [x] IPython releases [Matthias, IPython, https://github.com/ipython/ipython, 2min.] + * Trying to do monthly release close to End Of Month. + * 7.4 has been released ! Thanks to everyone. + * If you want to help with 7.5 subscribe to the following issue. + * https://github.com/ipython/ipython/issues/11657 +* [x] Async Kernels startup : [Matthias, Jupyter Client , https://github.com/jupyter/jupyter_client/pull/428, 4min.] + * https://github.com/jupyter/jupyter_client/pull/428 +* add item here [name, project name/url, estimated time for discussion]. + +Don't get limited to technical discussions ! + +## In Attendance + +Name | Institution | Github Handle + +* Zach | Jupyter Cal Poly | @Zsailer +* Kyle | Netflix | @rgbkrk +* Pete | Valassis Digital | @parente +* Carol | Project Jupyter | @willingc (will miss due to OpenEdX conference) +* Brian | AWS | @ellisonbg +* Darian | Two Sigma | @afshin +* Ward | Google | @wkharold +* Tim | Project Jupyter | @betatim +* Chris | Berkeley/Project Jupyter| @choldgraf +* Pete | Google Colab | @blois +* Matthias | UC Merced | @carreau +* Saul | Quansight | @saulshanabrook +* Vidar | Simula Research | @vidartf +* Lindsey Heagy | UC Berkeley | @lheagy +* Safia ABdalla | Microsoft/nteract | @captainsafia +* Leticia Portella | - | @leportella +* Damián Avila | Project Jupyter | @damianavila +* Craig Citro | Google Colab | @craigcitro +* Nick Bollweg | GTRI | @bollwyvl +* Michael Milligan | U Minnesota / MSI | @mbmilligan +* Liang Bin Hsueh | InfuseAI | @hlb +* Thomas Vander Velde | - | @tomasdelcampo +* Luciano Resende | IBM | @lresende +* Tony Fast | Quansight | @tonyfast +* James Slack | University of Edinburgh | @jamesaslack +* Erik Sundell | Sandvik | @consideratio diff --git a/docs/source/community/community-call-notes/2019-may.md b/docs/source/community/community-call-notes/2019-may.md new file mode 100644 index 000000000..283c3b881 --- /dev/null +++ b/docs/source/community/community-call-notes/2019-may.md @@ -0,0 +1,78 @@ +# Jupyter Community Call + +## May 28th, 2019 + +**Date:** 28 May 2019 at 9am PST (your [timezome](http://arewemeetingyet.com/Los%20Angeles/2019-05-28/09:00/Jupyter%20Community%20Call)) + +**Link:** [Youtube Video](https://youtu.be/mqZCa8j2K4s) + + +## Welcome to the All-Jupyter Community Meeting + +## Purpose + +The purpose of these monthly video conference calls is to share and demonstrate the awesome things happening in Jupyter community. We invite **anyone** to present their work, engage in discussion, or just sit in and listen. Whether you have a new [lab extension](https://github.com/jupyterlab) you've created, a new [jupyterhub deployment](https://github.com/jupyterhub) you're excited about, or an [nteract papermill](https://github.com/nteract) pipeline powering your business, we'd love to hear about it! And, we'll record and publish these calls on YouTube for anyone unable to attend. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make *short* announcements (without a need for discussion). This is also a great place to give shout-outs to contributors! We’ll read through these at the beginning of the meeting. + +* Hello from [The Turing Way](https://github.com/alan-turing-institute/the-turing-way) Book Dash :books::dash::dash: in London. This call is right at the end of a day of 18 people working together to improve the openly developed [Jupyter book](https://github.com/jupyter/jupyter-book/). Our goal is to make "Reproducibility too easy not to do" (:laughing::grimacing::scream_cat:), build a strong and supportive community, and give people the knowledge and confidence they need to contribute to open source projects [name=Kirstie & Turing Way team] + * GitHub repo: https://github.com/alan-turing-institute/the-turing-way + * The book: https://the-turing-way.netlify.com + * Chat room: https://gitter.im/alan-turing-institute/the-turing-way + + +## Agenda Items + +Add your potential agenda item here **24 hours before** the meeting at the latest. We will reorganize the agenda so that it fits in the 60m meeting slot. + +* Feedback and report from Research Software Reactor Sprint [name=Sarah] + * Event website: https://www.microsoftevents.com/profile/form/index.cfm?PKformID=0x6927743abcd + * Project list: https://github.com/research-software-reactor + * New binderhub in the world :baby: :confetti_ball: +* Feedback and report from Jupyter Server Design and Roadmap workshop [name=Luciano] + * sponsored by bloomberg + * thomas, kevin, etc. + * functionality directions, high-level roadmap + * decouple frontend from backend: notebook, lab, nteract, voila + * using the backend functionality, providing different UIs + * how do we accomplish that? jupyter_server extension points + - ui + - backend + - handlers + * roadmap + * phase 1: integrating with existing uis (notebookclassic, lab) + * phase 2: expand functionality + * kernel provider pr (e.g. different kernel managers, like Enterprise Kernel Gateway) + * next steps: + * pr from zak + * blog post (illustration) + * biweekly calls + * timeline: + * 6.0 release of notebook? + * post jupyterlab 1.0? +* Qt(5.6)-based PDF output from JupyterLab (0.35) + Quick demo of using QtWebEngine to load a notebook in lab and make a PDF. $_{n+1}$th time's the charm! [![Launch Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/deathbeds/nbconvert-pdfqt/master?urlpath=lab%2Ftree%2Fnotebooks%2Findex.ipynb) | [issue](https://github.com/jupyter/nbconvert/issues/1031) | [repo](https://github.com/deathbeds/nbconvert-pdfqt) | [name=Nick] + +## Attendees + +If you are joining the All-Jupyter Community video meeting, sign in below so we know who was here. Roll call: + +- | Zach | Jupyter Cal Poly | @Zsailer | +- | Amit | ReviewNB | @amit1rrr | +- | Kirstie | Alan Turing Institute | @KirstieJane | +- | Pete | Thorn | @parente | +- | Tony | Quansight | @tonyfast | +- | Nick | GTRI | @bollwyvl | +- | Luciano | IBM | @lresende | +- | Sarah | The Alan Turing Institute | @sgibson91 | +- | Saul | Quansight | @saulshanabrook | +- | James | MUN | @jmunroe | +- | Darian | Two Sigma | @afshin | +- | Matthias| UC Merced | @carreau | +- | Tania | Microsoft | @trallard | +- | Carol | Project Jupyter | @willingc | +- | Chris | UNC-Chapel Hill | @cbcunc | diff --git a/docs/source/community/community-call-notes/2019-september.md b/docs/source/community/community-call-notes/2019-september.md new file mode 100644 index 000000000..8a805d2cd --- /dev/null +++ b/docs/source/community/community-call-notes/2019-september.md @@ -0,0 +1,54 @@ +# Jupyter Community Call + +## September 24th, 2019 + +**Date:** September 24, 2019, at 9am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2019-09-24/09:00/Jupyter%20Community%20Call)) + +**Link:** [Youtube Video](https://youtu.be/so9F-Ha4q4U) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make *short* announcements (without a need for discussion). + +* [Co-locating a Jupyter Server and Dask Scheduler _By Matthew Rocklin](https://blog.dask.org/2019/09/13/jupyter-on-dask) [name=tonyfast] + +* [Language server protocol](https://github.com/jupyterlab/jupyterlab/issues/2163) + * [current work on jupyterlab-lsp](https://github.com/krassowski/jupyterlab-lsp) [name=krassowski] + * [wip binder](https://mybinder.org/v2/gh/bollwyvl/jupyterlab-lsp/add-traitlets-proxy?urlpath=lab%2Ftree%2Fexamples%2FPython.ipynb) [name=bollwyvl] + +## Agenda Items + +Add agenda items here **before** the meeting. We will reorganize the agenda so that it fits in the 60m meeting slot. + +* **[importing notebooks with `importnb`](https://gist.github.com/tonyfast/15c6ac8f005a5522291f08d95619e085)** [name=tonyfast] + + > _[`importnb`](https://github.com/deathbeds/importnb) provides easy, flexible reuse of IPython notebooks from other notebooks, `.py` scripts and libraries, and even the command line._ + +* **[🤖 RobotLab: a one-click Jupyter and Robot Framework environment](https://github.com/robots-from-jupyter/robotlab)** [name=bollwyvl] + + > _`RobotLab` was built to support a workshop introducing [acceptance-test-driven](https://en.wikipedia.org/wiki/Acceptance_testing) development and robot process automation with [robotkernel](https://github.com/robots-from-jupyter/robotkernel), a [Robot Framework](https://robotframework.org/) kernel, in JupyterLab. It is built with [conda](https://github.com/conda/conda), [constructor](https://github.com/conda/constructor) and [azure pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines). You can use the [installers](https://github.com/robots-from-jupyter/robotlab/releases/tag/v2019.9.0) to learn how you can use Robot Framework and Jupyter, or adapt its pipeline to produce your own, cross-platform installers_ + > + +* **Project Drawdown** [name=dgentry] + > _Project Drawdown is a global research organization that identifies, reviews, and analyzes the most viable solutions to climate change, and shares these findings with the world._ + > _We'll show current state of climate solution models using Voila and JupyterHub, and ask for suggestions about git operation driven from the Notebook._ + + + +## Attendees + + +- Zach | Jupyter Cal Poly | @Zsailer | +- Denton | Project Drawdown | @DentonGentry | +- Nick | GTRI | @nrbgt | +- Chico Venancio | BMC Group K. K. | @chicocvenancio | +- Tony Fast | Quansight | @tonyfast | +- Wayne Decatur | Upstate Medical | @fomightez | +- Kevin Bates | IBM | @kevin-bates | +- Carol | Jupyter | @willingc | diff --git a/docs/source/community/community-call-notes/2020-december.md b/docs/source/community/community-call-notes/2020-december.md new file mode 100644 index 000000000..a4dac6701 --- /dev/null +++ b/docs/source/community/community-call-notes/2020-december.md @@ -0,0 +1,77 @@ +# Jupyter Community Call December 15th, 2020 + +**Date:** December 15, 2020, at time 9am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2020-12-15/9:00/Jupyter%20Community%20Call)) + +[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668) +[YouTube Link](https://youtu.be/IlYP6q2H1M8 ) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs, PR of the month + +This is a place to make short announcements (without a need for discussion). + +* **[Accessibility testing for docs](https://github.com/pandas-dev/pydata-sphinx-theme/pull/294)** - _Nick_ + * WIP PR to show a way forward to establish and maintain an accessibility roadmap for Sphinx-based documentation sites +* **[jupyter-starters](https://github.com/deathbeds/jupyterlab-starters) 0.6.0a0 released** - _Nick_ + * a tool for defining JSON Schema-based workflows in JupyterLab +* Thanks to everyone who gave feedback on last month's call! - _Isabela_ +* Check out @jtp's repos for [Jupyterlab-Classic](https://github.com/jtpio/jupyterlab-classic) and the [p5js notebook](https://github.com/jtpio/p5-notebook). I'm looking forward to sharing with students and teachers at Playfest conference in January. - _Carol_ +* Jupyter survey is now live! [Read more](https://blog.jupyter.org/survey-jupyterlab-and-beyond-88c7fbd27a79) and [take the survey](https://www.surveymonkey.com/r/LCB7GBF). - _Isabela_ + + +## Agenda Items + +> Add agenda items here **before** the meeting. We will reorganize the agenda so that it fits in the 60m meeting slot. + +* **WXYZDVCS** Work-in-progress report on [`wxyz.dvcs`](https://github.com/deathbeds/wxyz), a bridge from Jupyter Widgets to distributed version control - _Nick_ + * _Hopefully_ released this week 🤞, [![Launch Binder]](https://mybinder.org/v2/gh/deathbeds/wxyz/master?urlpath=lab/tree/src/py/wxyz_notebooks/src/wxyz/notebooks/index.ipynb) works though! +* Pierre's notebooks for teaching Python and data science +* [JupyterLab Classic](https://github.com/jtpio/jupyterlab-classic) - *Jeremy* + +[binder]: https://mybinder.org/badge_logo.svg + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. +- [deathbeds/importnb](https://github.com/deathbeds/importnb) +- [mwouts/jupytext](https://github.com/mwouts/jupytext) +- [QuantEcon MATLAB-Python-Julia Cheatsheet](https://cheatsheets.quantecon.org) +- [SQLite Jupyter kernel](https://blog.jupyter.org/a-jupyter-kernel-for-sqlite-9549c5dcf551) +- [2i2c](https://2i2c.org/) (brought up around support for JuptyerHubs in education) +- [p5 notebook example](https://p5-notebook.now.sh) (mentioned when talking about JupyterLab Classic) + +## Attendees + +| Name | Institution | GitHub Handle | +|--------------------|----------------------------------|-----------------------------------| +| Nick Bollweg | Project Jupyter, GTRI, Deathbeds | @bollwyvl @nrbgt | +| Steven Silvester | Apple | @blink1073 | +| Ryan Spencer | GTRI | @ryspnc | +| Simon Li | University of Dundee | @manics | +| Wayne Decatur | Upstate Medical University | @fomightez | +| Pete Blois | Google Colab | @blois | +| Pierre-Olivier Simonard | Quansight | @pierrotsmnrd +| Ryan C. Cooper | University of Connecticut | @cooperrc | +| Raman Tehlan | nteract | [@ramantehlan](https://github.com/ramantehlan) | +| A. T. Darian | Two Sigma | @afshin | +| Jeremy Tuloup | QuantStack | @jtpio +| Damián Avila | UMSI-MADS | @damianavila | +| Tim George | Freelance | @tgeorgeux | +| Gonzalo Peña-Castellanos | Quansight | @goanpeca | +| Zach Sailer | Apple | @Zsailer | +| Carol Willing | Jupyter, noteable| @willingc | +| Sarah Gibson | The Alan Turing Institute | @sgibson91 +| Sharan Foga | None | @sharanf +| Tania Allard | -- | @trallard +| Tony Fast | Quansight | @tonyfast +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf diff --git a/docs/source/community/community-call-notes/2020-november.md b/docs/source/community/community-call-notes/2020-november.md new file mode 100644 index 000000000..a02732175 --- /dev/null +++ b/docs/source/community/community-call-notes/2020-november.md @@ -0,0 +1,47 @@ +# Jupyter Community Call +## November 17th, 2020 + +**Date:** November 17th, 2020, at 9am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2020-11-17/09:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[Youtube Link](https://youtu.be/bko-v1ZZoig)** + +**Please Note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **Zach** Shout out to Isabela for reviving the Jupyter Community Calls :tada: + +## Agenda Items + +Add agenda items here **before** the meeting. We will reorganize the agenda so that it fits in the 60m meeting slot. + +* 🦌 [IPyElk 0.2.0](https://github.com/jupyrdf/ipyelk) [![Launch Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/jupyrdf/ipyelk/42db3e3?urlpath=lab%2Ftree%2Fexamples%2F_index.ipynb) + * > Jupyter Widgets for interactive graphs _at scale_ powered by the [Eclipse Layout Kernel (ELK)](https://github.com/kieler/elkjs), [sprotty](https://github.com/eclipse/sprotty), [networkx](https://networkx.github.io). + +* [dgaf](https://github.com/deathbeds/dgaf) (deathbeds generalized automation framework) + +* **Eric** [What is a Jovyan?](https://jupyter.readthedocs.io/en/latest/community/content-community.html#what-is-a-jovyan) + +## Attendees + +| Name | Institution | GitHub Handle | +|------------------|---------------------------|-----------------------------------| +| Nick Bollweg | Jupyter, Deathbeds, GTRI | @bollwyvl @nrbgt +| tony fast | | @deathbeds +|Eric Charles | Datalayer, Quansight | @echarles | +| Isabela Presedo-Floyd |Quansight |@isabela-pf | +| Zach Sailer | Apple | @Zsailer | +|A. T. Darian | Two Sigma | @afshin | diff --git a/docs/source/community/community-call-notes/2021-april.md b/docs/source/community/community-call-notes/2021-april.md new file mode 100644 index 000000000..3c0b775dc --- /dev/null +++ b/docs/source/community/community-call-notes/2021-april.md @@ -0,0 +1,85 @@ +# April 27, 2021 + +**Date:** April 27, 2021, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2021-04-27/8:00/Jupyter%20Community%20Call)) + +[**Discourse:**](https://discourse.jupyter.org/t/jupyter-community-calls/668) + +[**Youtube Link**](https://youtu.be/k-oaQG459A0) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +- **Loïc Huder** New release of [jupyterlab-h5web](https://github.com/silx-kit/jupyterlab-h5web) that brings HDF5 file exploration and visualization to the notebook. + +- **Isabela Presedo-Floyd** As always, if anyone is interested in hosting, co-hosting, or getting involved with planning a community call, please reach out to me. + +## Agenda Items + +- **Jeremy**: + - [JupyterLite](https://github.com/jtpio/jupyterlite), a JupyterLab distribution that runs entirely in the browser + - Many thanks to Nick! + - Try it online: https://jupyterlite.readthedocs.io/en/latest/_static/lab/index.html + +- **Gonzalo** Internationalization workflow for extension developers + + - Some feedback... :man-facepalming: + - "As I see, there is a delay with the creation and publishing of language packs. We use Jupyter Lab as a base for one of our products and we are interested in using language lacks in it (especially Chinese and Japanese. What is the reason for the delay and is it possible to help the project somehow? We are interested in contributing to the Jupyter Lab project in many domains, for example, sofrware development, testing and translation." + + - Releasing language packages :world_map::card_file_box: + - [Current packages and state](https://crowdin.com/project/jupyterlab) (showing first 10) + ![The top 10 translations by percent completed are Spanish at 100%, Chinese Simplified at 100%, Hebrew at 88%, Turkish at 86%, Brazilian Portuguese at 83%, Ukrainian at 83%, Japanese at 83% French at 83%, Russian at 74%, and Polish at 60%](https://i.imgur.com/vNeRe8s.png) + - Releasing Spanish and Chinese simplified today evening. :eyes: + - Please attend the JLab dev meeting for more information on the internal process for managing the translations and language packs. + + - Resources :books: + 1. [Example PR to internationalize your extension](https://github.com/jupyterlab/jupyterlab-git/pull/888) adding internationalization to [Jupyterlab-Git](https://github.com/jupyterlab/jupyterlab-git) extension. + 1. [Yaml File to update on the language packs centralized repo](https://github.com/jupyterlab/language-packs/blob/master/repository-map.yml) to update on the language packs repository. + 1. [Language packs repository](https://github.com/jupyterlab/language-packs). + 1. [Start translating on Crowdin](https://crowdin.com/project/jupyterlab) + 1. [JupyterCON slides](https://cfp.jupytercon.com/2020/schedule/presentation/239/bienvenido-bienvenue-welcome-jupyterlab-and-language-extensions/) - [[Video]](https://www.youtube.com/watch?v=8-3eo1y5IrA) + +- **David**: + - **Nbterm** + - [Blog: Jupyter Notebooks in the terminal](https://blog.jupyter.org/nbterm-jupyter-notebooks-in-the-terminal-6a2b55d08b70) + - [Github Repository](https://github.com/davidbrochart/nbterm) + ![Notebook cell input and outputs represented in the terminal. The terminal has a black background and syntax coloring. Line numbers appear to the left of each line as "In 1", "In 2" etc. Inputs appear as text within a grey bounding box. Each input line's output appears as grey text below the box.](https://i.imgur.com/kzNyCno.png) + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- https://github.com/jupyterlab/jupyterlab-hdf5 +- https://github.com/jtpio/jupyterlite/issues/41 +- https://deathbeds.github.io/jyve/lab/ +- https://github.com/capytale/capytale + +## Attendees + +| Name | Institution | GitHub Handle | +|------|-------------|---------------| +|A. T. Darian| Two Sigma | @afshin | +|Layne Sadler|AIQC |@aiqc| +|Sylvain Corlay | QuantStack | @SylvainCorlay | +|Loïc Huder|ESRF|@loichuder| +|Claudia Regio |@Microsoft |@claudiaregio +|Joyce Er |@Microsoft |@joyceerhl| +| Jeremy Tuloup | @QuantStack | @jtpio | +| Steven Silvester | @Apple | @blink1073 | +| Zach Sailer | @Apple | @Zsailer | +| Gonzalo Peña-C. | @Quansight | @goanpeca | +| Damián Avila | MADS & 2i2c | @damianavila | +| Pete Blois | Google | @blois | +| Marvin Kastner | Hamburg University of Technology | @1kastner | +| David Brochart | QuantStack | @davidbrochart | +| Tony Fast | Quansight | @tonyfast | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | diff --git a/docs/source/community/community-call-notes/2021-august.md b/docs/source/community/community-call-notes/2021-august.md new file mode 100644 index 000000000..74a7d0669 --- /dev/null +++ b/docs/source/community/community-call-notes/2021-august.md @@ -0,0 +1,61 @@ +# August 31, 2021 + +**Date:** August 31, 2021, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2021-08-31/8:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[YouTube link](https://youtu.be/WQ43ywKDfg8)** + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +* **Rollin** JupyterHub + HPC meeting tomorrow [agenda](https://hackmd.io/r4AuJjSpSoeTw_Br8dgMRA), invite/link on the [community calendar](https://discourse.jupyter.org/t/jupyter-community-calendar/2485) +* **Rollin+Rick** Jupyter Security Meetings, biweekly (Fridays, 9:00 AM PDT) + * Next call Sep 10 + * Trusted CI Jupyter security docs review +* Mike: Translations for JupyterLab + * If you want to contribute translation is happening on https://crowdin.com/project/jupyterlab + +## Agenda Items + +* **Navinn** would like to present the work done by the [MLH Fellowship](https://fellowship.mlh.io/) on the JupyterLab Git Extension. +* **Mike** will introduce early version of [JupyterLab citation manager extension](https://github.com/krassowski/jupyterlab-citation-manager) +* **David** would like to present the latest development in [akernel](https://github.com/davidbrochart/akernel): reactivity. +* **Tony** would like to share [jupyterlab-markup](https://github.com/agoose77/jupyterlab-markup) and [pidgy](https://github.com/deathbeds/pidgy). + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- [Voila on hackernews!](https://news.ycombinator.com/item?id=28364923) +- Some updates on JupyterLab translation based on new strings. Join us in translating on [crowdin](https://crowdin.com/project/jupyterlab)! + +## Attendees + +| Name | Institution | GitHub Handle | +|----------|---------------------------|-----------------------------------| +| Frederic Collonval | QuantStack | @fcollonval | +| David Brochart | QuantStack | @davidbrochart | +| Thorin Tabor | UCSD | @tmtabor | +| Rick Wagner | UCSD | @rpwagner| +| Hamilton Ulmer| Mozilla | @hamilton | +| Rollin Thomas | NERSC | @rcthomas | +| Navinn Ravindaran | MLH Fellowship | @navn-r +| Luciano Resende | IBM | @lresende | +| Nick Bollweg | Georgia Tech | @bollwyvl @nrbgt +| Loïc Huder | ESRF | @loichuder | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | +| Michał Krassowski | U Oxford | @krassowski | +| Jessica Xu | Quansight | @jess-x | + +Plus 7 others. \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2021-february.md b/docs/source/community/community-call-notes/2021-february.md new file mode 100644 index 000000000..93b2d63d1 --- /dev/null +++ b/docs/source/community/community-call-notes/2021-february.md @@ -0,0 +1,125 @@ +# February 23rd, 2021 + +**Date:** February 23, 2021, at 9am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2021-02-23/9:00/Jupyter%20Community%20Call)) + +[**Discourse:**](https://discourse.jupyter.org/t/jupyter-community-calls/668) + +[**Youtube Link**](https://youtu.be/TG0w6WLunTk ) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +* **Nick B**: Are you excited by... **JS license compliance**? Feedback welcome on [lab#9779](https://github.com/jupyterlab/jupyterlab/pull/9779) ([screenshot](https://user-images.githubusercontent.com/45380/108773016-c25f4880-752b-11eb-945c-32a20f2133b3.png))! +* **Nick B**: The latest [Lab RTC PR](https://github.com/jupyterlab/jupyterlab/pull/9785) ([demo](https://mybinder.org/v2/gh/QuantStack/jupyterlab/yjupyter?urlpath=lab-dev)) is 🔥! +* **Isabela Presedo-Floyd**: If you are interested in helping run or host a community call, let me know (you won't have to do it alone :sunflower:)! +* **Mike**: pyls fork [python-ls](https://github.com/python-ls/python-ls) in cooperation with the Spyder team; preview of the changes to come in my [personal fork](https://github.com/krassowski/python-language-server) (**fast** and more clever autocompletion for [jupyterlab-lsp](https://github.com/krassowski/jupyterlab-lsp)!) +* **Matt S**: [testbook](https://testbook.readthedocs.io/) had a talk at PyCascades around unittesting Jupyter Notebooks. + +## Agenda Items + +* **Loic Huder**: short presentation of [jupyter-h5web](https://github.com/silx-kit/jupyterlab-h5web), a JLab extension to explore/visualize HDF5 files +* **Jagane Sundar**: short presentation of InfinStor's free hosted Jupyterhub service (https://infinstor.com), a Cloud hosted free Jupyterhub - our Jupyterhub service is free, you pay for Jupyterlab instance resources consumed +* **Frédéric Collonval**: short presentation of [papermill_report](https://github.com/ariadnext/papermill_report). JupyterHub service to generate report from notebooks combining [papermill](https://papermill.readthedocs.io/en/latest/) and [nbconvert](https://github.com/ariadnext/papermill_report/blob/master/nbconvert.readthedocs.io). +* **Nick B**: [demo](http://mybinder.org/v2/gh/deathbeds/ipydrawio/master?urlpath=lab/tree/docs/Poster.dio.svg) of [ipydrawio](https://github.com/deathbeds/ipydrawio) (🍴 with 💖 of [@quantstack/jupyterlab-drawio](https://github.com/QuantStack/jupyterlab-drawio)), the full [diagrams.net](https://https://www.diagrams.net/) UI (with all plugins, themes, shapes...) for Lab 3. Supports `*.{ipynb,drawio,png,svg}` (plus `.pdf`, sorta) + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- agenda from [1/26 (last time)](https://hackmd.io/l2yBruUATC6yH4F2gOUPgw) +- h5web + - based on same backend as other hd5f extension, will share more code in the future + - other one's based on lumino datagrid + - [merged cells](https://github.com/jupyterlab/lumino/pull/124) would be awesome + - keras: export [neural network weights](https://keras.io/api/models/model_saving_apis/) as hdf5, potential use case + - xray community currently + - viewer should work for all formats + - [drug discovery](https://academic.oup.com/bioinformatics/article/35/8/1427/5094509) + - preventing jlab from sending all the data + - quick fix: filetype `base64` to just send a little data (custom contentsmanager?) + - would prefer basically _no_ data... +- infinistor product + - hub + - custom spawner/authenticator (FOSS tbd) + - didn't want existing spawner (container/k8s) + - vm interface granular enough + - stoppable machines for lower idle cost + - requires infinistor + - aws auth + - token refreshing + - hub runs on infinistor + - spawns in your own aws, shutdown on 15m of idle + - stock Lab, BYO extensions + - custom tool for extensions + - snapshots + - dashboard + - s3 storage + - users + - multicloud (aws, azure) + - customize the python kernel? + - in backend, have transforms, use dockerfile, modify dockerfile + - stock open source distributions (pip, conda) +- [show and tell on discourse](https://discourse.jupyter.org/c/general/show-and-tell/45) +- papermill_report + - speaks python (other libraries could be added) + - install as a service on hub + - pick notebook + - fill out form from papermill + - click button, get report + - shareable url + - if break, get full traceback + - click to get annotated notebook report + - next time: integration testing jupyterlab, screenshots w/ playwright, etc. + - papermill inspect added for this purpose, first example of using in FOSS + - multi-step wizard? + - schedulers + - cylc + - dagster + - prefect + - hiding code? + - nbconvert (use [tags](https://nbconvert.readthedocs.io/en/latest/removing_cells.html#removing-pieces-of-cells-using-cell-tags)?) + - preprocessors + - all standard stuff + +- ipydrawio + - > nb: most important takeaway: write the mimerenderer first, then it's easier to write a widget/document + - More draw.io features available in notebooks + + ## Attendees + +| Name | Institution | GitHub Handle | +|-----------------------|-----------------------------------|-----------------------------------| +| Jagane | InfinStor, Inc. | @jagane-opensource | +| Loïc Huder | ESRF | @loichuder | +| Frédéric Collonval | ARIADNEXT | @fcollonval | +| Layne Sadler | AIQC | @aiqc | +| Nick Bollweg | GTRI, Project Jupyter | @nrbgt @bollwyvl | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | +| M. Krassowski (Mike) | UOxf (on own behalf) | @krassowski | +| Simon Li | University of Dundee | @manics | +| Dan Lester | Ideonate | @danlester | +| Wayne Decatur | Upstate University | @fomightez | +| Michael Milligan | MSI @ U of Minnesota | @mbmilligan | +| Matthew Seal | Noteable, Inc | @mseal | +| Jose Ferro. | EPO (www.epo.org) | @joseberlines | +| Marvin Kastner | Hamburg University of Technology | @1kastner | +| Zach Sailer | Apple | @Zsailer | +| A. T. Darian | Two Sigma | @afshin | +| W Stein | CoCalc | @williamstein | +| Raja Rajendran | InfinStor, Inc. | @software-artisan | +| Adhitya Vadivel | InfinStor, Inc. | @adhityav | +| Jeremy Tuloup | QuantStack | @jtpio | +| Steven Silvester | Apple | @blink1073 | +| Safia Abdalla | Microsoft, nteract | @captainsafia | +| Shelby Sturgis| Netflix | @stormpython +| Pete Blois | Google | @blois | \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2021-january.md b/docs/source/community/community-call-notes/2021-january.md new file mode 100644 index 000000000..1d7ea155f --- /dev/null +++ b/docs/source/community/community-call-notes/2021-january.md @@ -0,0 +1,117 @@ +# Jupyter Community Call +## January 26th, 2021 + +**Date:** January 26, 2021, at 9am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2021-01-26/9:00/Jupyter%20Community%20Call)) + +[**Discourse**](https://discourse.jupyter.org/t/jupyter-community-calls/668) + +[**YouTube Link**](https://youtu.be/DS_J3mzulCw) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **Frédéric Collonval** To improve visibility and group volunteer time on maintenance of popular JupyterLab +extensions, a unofficial GitHub organization has been created: [jupyterlab-contrib](https://github.com/jupyterlab-contrib). +* **Isabela Presedo-Floyd** In case you missed it, [JupyterLab 3.0 is out](https://blog.jupyter.org/jupyterlab-3-0-is-out-4f58385e25bb)! Congrats to the community and thanks for all +the hard work that went into this release. +* **Isabela Presedo-Floyd** I've seen a resurgence of community interest in making multiple Jupyter projects accessible. +This is awesome! We also have a group of people meeting every other week to coordinate JupyterLab accessibility work (and +talk about accessibility in general) that you can join from the [community calendar](https://jupyter.readthedocs.io/en/latest/community/content-community.html#jupyter-community-meetings). +* **Layne Sadler** Plotly updated jupyter-dash labextension for 3.0 and vows to prebuild. [issue](https://github.com/plotly/jupyter-dash/issues/49) + +## Agenda Items + +* **Nick Bollweg** [jupyterlab-lsp 3.2](https://pypi.org/project/jupyterlab-lsp/) on `pypi` & `conda-forge`. JupyterLab +:three:. :eight: _[Language Client](https://langserver.org)_ features. Ju(lia)+Py(thon)+R _Language Servers_+_Kernel_+_Notebook_, +plus [more](https://jupyterlab-lsp.readthedocs.io/en/latest/Language%20Servers.html). [Pre-JEP Issue](https://github.com/jupyter/enhancement-proposals/issues/67) +to move towards an official sub-project 🚀. +* **Nick Bollweg** (_or someone better :muscle:_) [JupyterLab 2.3.0rc0](https://github.com/jupyterlab/jupyterlab/blame/2.3.x/docs/source/getting_started/changelog.rst#L6-L12) +is a performance-focused prerelease, on `pypi`/`conda-forge`, these features will land in 3.1. Ready for +[testing](https://github.com/robots-from-jupyter/robotframework-jupyterlibrary/pull/34)! +* **Frédéric Collonval**: Leverage JupyterLab modularity to customize the UI with a alternative +[launcher](https://github.com/jupyterlab-contrib/jlab-enhanced-launcher) and a [cell toolbar](https://github.com/jupyterlab-contrib/jlab-enhanced-cell-toolbar) - demonstrate easier distribution thanks to JLab3. +* **Corentin Cadiou**: presentation of [ipysphaghetti](https://github.com/cphyc/node_editor) (name not settled yet) a JLab +(3+) extension implementing a node-based approach to interact with your data. +* **Thorin Tabor:** Notebook Projects, a mechanism for encapsulating multiple user environments in a JupyterHub instance + +## Other Links Shared + +- Take the [Jupyter survey](https://blog.jupyter.org/survey-jupyterlab-and-beyond-88c7fbd27a79)! +- some nteract links after @raman's pre-demo: + - https://docs.nteract.io/getting-started-with-nteract/ + - https://github.com/nteract/nteract +- semi-related "instant-on" compute/notebooks + - [jyve](https://deathbeds.github.io/jyve/lab/), static JupyterLab build + - [pyodide](https://github.com/iodide-project/pyodide), full CPython in the browser +- hackmd's FOSS flavor is now [HedgeDoc](https://github.com/hedgedoc/hedgedoc) + - we need a Hub/Lab Extension :hedgehog: +- "run cells with tags" + - from `cell-toolbar` demo + - could this be supported in multiple clients, e.g. _JupyterLab Notebook_ UI and `nbclient`/`nbconvert` CLI +- workflows with (some) Jupyter integration + - [cylc](https://github.com/cylc/cylc-ui/issues/90) + - [dask](https://docs.dask.org/en/latest/graphs.html) + - [dagster](https://github.com/dagster-io/dagster) ([binder](https://gist.github.com/bollwyvl/0fe7a6f89251992ab1a542ac2b4051c4)) + - [openmdao](https://github.com/OpenMDAO/OpenMDAO) + - [prefect](https://stories.dask.org/en/latest/prefect-workflows.html) +- [GenePattern](https://github.com/genepattern) and [GenePatternNotebook](https://notebook.genepattern.org/#gsc.tab=0) +- [Integrative Genetics Viewer](http://software.broadinstitute.org/software/igv/) and their [Jupyter extension](https://github.com/igvteam/igv-jupyter) + + +## Q/A + +> **As a company, how do we start contributing?** +> - @willingc follow the projects that seem most within your team's wheelhouse +> - Visit the Jupyter [Discourse](https://discourse.jupyter.org/) and [community calendar](https://discourse.jupyter.org/t/jupyter-community-calendar/2485)! +> - @jasongrout JupyterLab [4.0 release plans](https://github.com/jupyterlab/jupyterlab/issues/9647) are underway. There may be items there, or things you want to contribute. +> - translations always welcome! Check [CrowdIn](https://crowdin.com/project/jupyterlab) for more info. +> - [corporate guidance](https://github.com/jupyterlab/jupyterlab/blob/master/CORPORATE.md) +> - [team compass](https://github.com/jupyterlab/team-compass) is where many of these larger discussions may happen. +> - @jupyter/notebook is very starved for resources +> - has a weekly meeting just trying to keep the issue count down. +> - many are low-touch to at least get triaged +> - really any help welcome +> - @isabela-pf accessibility on all projects. +> - We have been starting with JupyterLab Components, etc. Notes for our meetings and all current team work live in [this issue](https://github.com/jupyterlab/team-compass/issues/98) +> - And documentation in [pydata-sphinx-theme](https://github.com/pandas-dev/pydata-sphinx-theme/pull/294) (upstream of `jupyter-book`, etc.) + +> **What would you like to see in community calls?** +> - Overview of JupterLab 3 + +## Attendees +| Name | Institution | GitHub Handle | +|--------------------|-------------------------------|-----------------------------------| +| Ross Stokoe | Refinitiv | @RR11WK | +| Julien Hoarau | Refinitiv | @julienhoarau | +| Greg Olmstead | Refinitiv | @maynardflies | +| Josias De Lima | Refinitiv | @JoshDL | +| Loic Huder | ESRF | @loichuder | +| Thorin Tabor | UCSD | @tmtabor | +| Gonzalo Gasca Meza | Google | @gogasca | +| Frédéric Collonval | ARIADNEXT | @fcollonval | +| Layne Sadler | free agent | @aiqc | +| Corentin Cadiou | University College London | @cphyc | +| Nick Bollweg | Proj. Jupyter, GTRI, Deathbeds| @bollwyvl @nrbgt @deathbeds | +| Wayne Decatur | Upstate Medical Universtity | @fomightez | +| Zach Sailer | Apple | @Zsailer | +| Simon Li | University of Dundee | @manics | +| Raman Tehlan | nteract, StockGro | @ramantehlan | +| Pete Blois | Google Colab | @blois | +| Ryan Spencer | GTRI | @ryspnc | +| A. T. Darian | Two Sigma | @afshin | +| Carol Willing | Noteable / Jupyter | @willingc | +| Karla Spuldaro | IBM | @karlaspuldaro | +| Martha Cryan | IBM | @marthacryan | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | diff --git a/docs/source/community/community-call-notes/2021-july.md b/docs/source/community/community-call-notes/2021-july.md new file mode 100644 index 000000000..8503a5f0e --- /dev/null +++ b/docs/source/community/community-call-notes/2021-july.md @@ -0,0 +1,75 @@ +# July 27, 2021 + +**Date:** July 27, 2021, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2021-07-27/8:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[YouTube Link](https://youtu.be/ebUXrmRfkM8)** + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +* **Michael Milligan** For cluster/scheduler users, [batchspawner](https://pypi.org/project/batchspawner/) and related [wrapspawner](https://pypi.org/project/wrapspawner/) had new releases recently +* **Steve** JupyterLab 3.1 release +* **Rick** Globus Groups support in OAuthenticator +* **Simon** mybinder.org no longer blocking public cloud requests (Resolves [this issue](https://github.com/jupyterhub/mybinder.org-deploy/issues/1828).) +* **Nick** [jupyter-videochat](https://github.com/jupyterlab-contrib/jupyter-videochat/tree/develop) 0.6.0 release is coming up, adds support for JupyterLite and RetroLab (needs config :blush:) +* **Nick** [`jupyterlite 0.1.0a6`](https://github.com/jupyterlite/jupyterlite/releases/tag/v0.1.0a6) is out, with some improved support for python kernel parity and deploying in-development lab extensions + +## Agenda Items + +* **Matthias** would like to talk about kernel management and parametrisation. + * You can have a look at [prototype/in progress repo](https://github.com/Quansight/ksmm) – in need of a better name + * I'll point out the work of [Eric Charles and Kevin Bates as well](https://github.com/jupyter/jupyter_client/pull/612#issuecomment-886686237). +* **Matthias** For cluster/scheduler user, show [inplace_restarter](https://pypi.org/project/inplace_restarter/),. +* **Rick** & **Rollin** discuss Jupyter Security [Best Practices Community Workshop old thread](https://discourse.jupyter.org/t/jupyter-security-best-practices-workshop/1496) and [new thread](https://discourse.jupyter.org/t/jupyter-security-workshop-progress/9370) + * **Matthias** Better process for CVE. We'll have two soon. How do we coordinate release, response and co. +* **David** would like to present a new [asynchronous Python Jupyter kernel](https://github.com/davidbrochart/akernel). + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- https://github.com/deathbeds/hourhaus - beefy binder with rtc and jupyter-videochat +- [Textual](https://github.com/willmcgugan/textual) +- [Jupyter community calendar](https://jupyter.readthedocs.io/en/latest/community/content-community.html#jupyter-community-meetings) +- [Enarx](https://github.com/enarx/enarx) +- [NSF Secure and Trustworthy Cyberspace](https://www.nsf.gov/funding/pgm_summ.jsp?pims_id=504709) +- [Jupyter Security Best Practices Workshop (2019)](https://discourse.jupyter.org/t/jupyter-security-best-practices-workshop/1496) +- [Jupyter Security Workshop Progress 2021](https://discourse.jupyter.org/t/jupyter-security-workshop-progress/9370) +- [Google Bug Hunters](https://bughunters.google.com/about/patch-rewards) +- [Eager Award](https://www.nsf.gov/pubs/policydocs/pappguide/nsf09_1/gpg_2.jsp#IID2) +- [ipydrawio](https://github.com/deathbeds/ipydrawio) +- [Exploring and defining UX expectations for a RTC enabled multi-user environment (like JupyterHub)](https://github.com/jupyterlab/jupyterlab/issues/10119) +- [rtc in jupyterlite](https://github.com/jupyterlite/jupyterlite/blob/d0aafc4a697a814c21f9412546a20e1b36ad4e0f/packages/application-extension/src/index.tsx#L44) +- [hedgedoc vs yjs (hackmd is the SaaS hedgedoc)](https://github.com/hedgedoc/hedgedoc/issues/527) + +## Attendees + +If you are joining the Jupyter Community Call, sign in below so we know who was here. + +| Name | Institution | GitHub Handle | +|----------|---------------------------|--------------------| +| Matthias |Quansight/Jupyter | @Carreau +| Thorin |UCSD | @tmtabor +| Anton |TU Delft | @akhmerov +| David |QuantStack | @davidbrochart +| Michael | University of Minnesota | @mbmilligan +| Rick | UCSD | @rpwagner +| Nick | Georgia Tech | @nrbgt @bollwyvl +| Wayne Decatur | Upstate Medical University | @fomightez | +| Simon Li | University of Dundee | @manics | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | +| Tony Fast | Quansight | @tonyfast | + +Plus 9 others \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2021-june.md b/docs/source/community/community-call-notes/2021-june.md new file mode 100644 index 000000000..78d28c382 --- /dev/null +++ b/docs/source/community/community-call-notes/2021-june.md @@ -0,0 +1,65 @@ +# June 29, 2021 + +**Date:** June 29, 2021, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2021-06-29/8:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[Youtube Link](https://youtu.be/-aQFh8rjcdA)** + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +* **Frederic** + * Plotly v5 is out (actually v5.1 has been released yesterday): update to [plotly.js v2](https://github.com/plotly/plotly.js/blob/master/CHANGELOG.md#210----2021-06-18), federated extension, single extension, lazy load plotly.js - [full changelog](https://github.com/plotly/plotly.py/releases/tag/v5.0.0). + * [JupyterLab v3.1 beta 0](https://github.com/jupyterlab/jupyterlab/releases/tag/v3.1.0b0) +* **Isabela** [Scipy Tools Plenary session at SciPy 2021 discussion](https://discourse.jupyter.org/t/scipy-tools-plenary-session-at-scipy-2021/9567) is still available for potential project updates. +* **Nick (or Jeremy :heart:)** `jupyterlite 0.1.0a1` is up [on PyPI](https://pypi.org/project/jupyterlite/0.1.0a1/) for building your own sites with a `doit`-powered [CLI](https://jupyterlite.readthedocs.io/en/latest/cli.html). Works with many `ipywidgets`, including `plotly 5.x` +* **Kevin** [Kernel Provisioning](https://github.com/jupyter/jupyter_client/pull/612) pull request in `jupyter_client` is ready for review +* **Loïc** [jupyterlab-h5web](https://github.com/silx-kit/jupyterlab-h5web) `0.0.8` release landing this week bringing support of HDF5 external link and compression +* **Nick (or Mike :heart:)** [JEP-72: LSP integration](https://github.com/jupyter/enhancement-proposals/pull/72) is in PR +* **Matt Seal**[`nbconvert 6.1.0`](https://nbconvert.readthedocs.io/en/latest/changelog.html) was released last week. [Proposal: Transmit Cell Metadata #70](https://github.com/jupyter/enhancement-proposals/pull/70) + +## Agenda Items +* **Eduardo Blancas** Short introduction to [Ploomber](https://github.com/ploomber/ploomber), an open-source library to build data pipelines with Jupyter +* :bird: [pidgy](https://github.com/deathbeds/pidgy/) demo + +## Other Links Shared +- http://worrydream.com/Tangle/ +- https://dagster.io/ +- https://github.com/deathbeds/XlbsOSh_t +- https://mybinder.org/v2/gh/deathbeds/pidgy/new-parser + +## Attendees + +| Name | Institution | GitHub Handle | +|--------------------|-----------------|-----------------------------------| +| Frederic Collonval | QuantStack | @fcollonval | +| Eduardo Blancas | Ploomber | @edublancas | +| Nick Bollweg | Georgia Tech | @bollwyvl @nrbgt | +| Paige Bailey | Microsoft | @dynamicwebpaige | +| Steven Silvester | Apple | @blink1073 | +| Hamilton Ulmer | Mozilla | @hamilton | +| Carol Willing | Jupyter, Noteable | @willingc | +| Matthew Seal | Noteable | @mseal | +| Claudia Regio | Microsoft | @claudiaregio | +| Ian Huff | Microsoft | | +| Alex Bozarth | IBM | @ajbozarth | +| Ryan Spencer | Georgia Tech | @ryspnc | +| Loic Huder | ESRF | @loichuder | +| A. T. Darian | Two Sigma | @afshin | +| Wayne Decatur | Upstate Medical | @fomightez | +| Michał Krassowski | | @krassowski | +| Luciano Resende | IBM | @lresende | +| Kiersten Stokes | IBM | @kiersten-stokes | +| Tony Fast | Quansight | @tonyfast | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | diff --git a/docs/source/community/community-call-notes/2021-march.md b/docs/source/community/community-call-notes/2021-march.md new file mode 100644 index 000000000..855aac366 --- /dev/null +++ b/docs/source/community/community-call-notes/2021-march.md @@ -0,0 +1,67 @@ +# March 30th, 2021 + +**Date:** March 30, 2021, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2021-03-30/8:00/Jupyter%20Community%20Call)) + +[**Discourse:**](https://discourse.jupyter.org/t/jupyter-community-calls/668) + +[**Youtube Link**](https://youtu.be/8JQoALd9KTo) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +* **Isabela Presedo-Floyd** Congrats to anyone who started the cycle 4 CZI EOSS grant application process! We have several in the community. +* **Nick B** [jupyter-starters 1.0.2](https://pypi.org/project/jupyter-starters/) +* **Carol W** Darian for his work on the Jupyter Distinguished Contributors. + +## Agenda Items + +- **Nick B.** Has anyone done `if this then that` in a JupyterHub? + - General answer is no + - Something like https://github.com/huginn/huginn? + - For background, this is https://ifttt.com/ + - Use cases +- **Tony Fast** schemata library (future traits library that complies more with JSON schema than traitlets) + - Goal of having types being able to describe themselves. This is a work in progress for IPython. + - Creates different types of interactive notebook outputs following JSON standards that can allow them to interact with more backends. +- Favorite notebooks/binders/plugins + - **Simon Li** Unexpected use of binder https://github.com/jupyterhub/jupyter-remote-desktop-proxy/ + - Can you run JupyterHub inside mybinder https://gist.github.com/manics/cd04d42b211dfd6240430ee33349cd49 +- **Tony Fast** https://nbviewer.jupyter.org/github/deathbeds/deathbeds.github.io/blob/master/deathbeds/2018-07-31-Testing-notebooks.ipynb + - https://github.com/jennalandy/notebook-research/blob/master/analysis_notebooks/16_HallOfFame.ipynb +- **Nick B.** https://gist.github.com/bollwyvl/7a128978b8ae89ab02bbd5b84d07a4b7 + - Can we round-trip LaTeX to SymPy https://github.com/bollwyvl/sympy-latex-hypothesis/blob/master/Hypothesize.ipynb +- **Carol Willing** https://github.com/moorepants/pydy-tutorial-human-standing + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- https://w3c.github.io/annotation-aria/ +- http://507movements.com/ +- http://rescience.github.io/ten-years/ +- https://web.mit.edu/music21/ +- https://pockit.ai/ +- https://www.dexterindustries.com/gopigo3/ + +## Attendees + +| Name | Institution | GitHub Handle | +|--------------------|----------------------|------------------------------| +| Frédéric Collonval | ARIADNEXT | @fcollonval | +| Simon Li | University of Dundee | @manics | +| Carol Willing | Jupyter | @willingc | +| Nick Bollweg | Jupyter, GaTech | @bollwyvl @nrbgt | +| Pierre-Olivier Simonard | Quansight | @pierrotsmnrd| +| Fatma Tarlaci | OpenTeams | @ftarlaci | +| Pete Blois | Google Colab | @blois | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2021-may.md b/docs/source/community/community-call-notes/2021-may.md new file mode 100644 index 000000000..da7df315c --- /dev/null +++ b/docs/source/community/community-call-notes/2021-may.md @@ -0,0 +1,67 @@ +# May 25, 2021 + +**Date:** May 25, 2021, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2021-05-25/8:00/Jupyter%20Community%20Call)) + +[**Discourse**](https://discourse.jupyter.org/t/jupyter-community-calls/668) +[**YouTube Link**](https://youtu.be/g9WrS4FlkeM) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +* **Darian** Congratulations to the [2020 cohort of Jupyter Distinguished Contributors](https://blog.jupyter.org/congratulations-distinguished-contributors-149deff3033c)! +* **Nick** [ipydrawio 1.1.0](https://github.com/deathbeds/ipydrawio/releases/tag/v1.1.0) _just_ dropped: now has the `sketch` theme, a _Custom Diagram..._ Launcher which offers all of the (extensible) templates. Also [docs](https://ipydrawio.rtfd.io). +* **Steve** [JupyterLab 3.1.0a9](https://github.com/jupyterlab/jupyterlab/releases/tag/v3.1.0a9) is now available with Real Time Collaboration (RTC)! To use: + * Install + * `pip install -U --pre jupyterlab` or + * `conda install -c conda-forge -c conda-forge/label/jupyterlab_alpha jupyterlab=3.1.0a9` + * Usage + * `jupyter lab --collaborative` or + * Jupyter settings: `{"LabApp": {"collaborative": true, "expose_app_in_browser": true}}` +* **Isabela** Congratulations to all the community members who submitted CZI grant proposals last week! Thank you for your hard work. + +## Agenda Items + +* **Tony Fast** Searching notebooks +* RTC Demo with Live Binder (temporary link given in Zoom Chat, based on [Michał's example](https://mybinder.org/v2/gh/krassowski/jupyterlab-demo/rtc-demo?urlpath=lab)). There is a "Share" top level menu item you can use to create the shareable link. +* **Nick** Learning with flashcards about... stuff? + +## Other Links Shared + +- https://github.com/jupyterlab/jupyterlab/blob/master/binder/start +- https://github.com/davidbrochart/jupyterlab-auth +- https://github.com/jtpio/jupyterlite/pull/89 +- https://github.com/gt-coar/janki + +## Attendees + +| Institution | Name | GitHub Handle | +| --------------------------------- | ------------------ | ----------------- | +| University of Southern California | Dhrithi Deshpande | @dhrithideshpande | +| Openteams | Eskild Eriksen | @iameskild | +| Two Sigma | Afshin T. Darian | @afshin | +| Georgia Tech | Nick Bollweg | @bollwyvl | +| Microsoft | Joyce Er | @joyceerhl | +| Microsoft | Claudia Regio | @claudiaregio | +| Microsoft | Paige Bailey | @dynamicwebpaige | +| UCSD | Thorin Tabor | @tmtabor | +| Alan Turing Institute | Sarah Gibson | @sgibson91 | +| QuantStack | Frederic Collonval | @fcollonval | +| Quansight | Mars Lee | @marsbarlee | +| Jupyter/Noteable | Carol Willing | @willingc | +| QuantStack | Jeremy Tuloup | @jtpio | +| QuantStack | David Brochart | @davidbrochart | +| Apple | Steven Silvester | @blink1073 | +| Apple | Zach Sailer | @Zsailer | +| Quansight | Tony Fast | @tonyfast | +| Quansight Labs | Isabela Presedo-Floyd | @isabela-pf | +| uPlanner | Sebastian Flores | @sebastiandres | diff --git a/docs/source/community/community-call-notes/2021-november.md b/docs/source/community/community-call-notes/2021-november.md new file mode 100644 index 000000000..9478b1262 --- /dev/null +++ b/docs/source/community/community-call-notes/2021-november.md @@ -0,0 +1,84 @@ +# November 30, 2021 + +**Date:** November 30, 2021, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2021-11-30/8:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[YouTube link](https://youtu.be/_YdiFgWUHNI)** + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **@loichuder:** Release 1.0.0 of [jupyterlab-h5web](https://github.com/silx-kit/jupyterlab-h5web) bringing support for JLab3 as prebuilt extension 🎉 +* **@bollwyvl** `jupyterlite 0.1.0a17` speaks self-hosted/custom wheels and MathJax + * [offline pyodide](https://jupyterlite--425.org.readthedocs.build/en/425/_static/lab/index.html) coming + * [jupyter-server-proxy 3.2.0](https://github.com/jupyterhub/jupyter-server-proxy/blob/main/CHANGELOG.md#320---2021-11-29) including full control of request re-writing, sub-paths in Lab launchers + +## Agenda Items + +* **@ltetrel** jupyter book workflow on [NeuroLibre](https://www.neurolibre.org/) + * [NeuroLibre Documentation](https://docs.neurolibre.org/en/latest/) (you are welcome to be an alpha tester!)) + * This is the [pull request for initContainer on binderhub](https://github.com/jupyterhub/binderhub/pull/1081). It should be already possible with [Zero to JupyterHub singleuser.initContainers](https://zero-to-jupyterhub.readthedocs.io/en/latest/resources/reference.html#singleuser-initcontainers) but not optimal (better to do our process once during build). The missing piece is to give that initContainer an environment variable ([as discussed on the github issue](https://github.com/jupyterhub/binderhub/issues/1429) and [Jupyter discourse](https://discourse.jupyter.org/t/feature-idea-jupyterhub-binderhub-jupyter-book-as-a-publishing-platform/8359/8?u=ltetrel)). +* **@fcollonval** [WIP RISE in JupyterLab PR](https://github.com/damianavila/RISE/pull/605) + + To test the PR locally, here are the commands to execute: + ```sh + yarn + yarn build + python3 -m pip install -e . + jupyter server extension enable --sys-prefix rise + jupyter serverextension enable --sys-prefix rise + jupyter labextension develop --overwrite . + ``` + +* **@afshin** `[DRAFT]` Jupyter Enhancement Proposal (JEP) for [Jupyter Notebook version 7](https://github.com/jupyter/enhancement-proposals/pull/79) + * Also mentioned on the [Jupyter Discourse](https://discourse.jupyter.org/t/jep-draft-open-for-the-notebook-v7-transition/11769) + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- [The Journal of Open Source Software](https://joss.theoj.org/) +- [Comment on Jupyter Discourse post Feature Idea: JupyterHub/BinderHub + Jupyter Book as a publishing platform](https://discourse.jupyter.org/t/feature-idea-jupyterhub-binderhub-jupyter-book-as-a-publishing-platform/8359/3) +- [Darian's sweet potato pie recipe](https://food.darian.link/sweet-potato-pie/) +- [Cooking for Engineers](http://www.cookingforengineers.com/) +- [jupyterlab/jupyterlab issue #10207 Side-by-side rendering](https://github.com/jupyterlab/jupyterlab/issues/10207) + +## Comments + +- Gabriel: being able to draw on the slides in Frederic's demo (over the figures, charts) looked very cool to me + +## Attendees + +| Name | Institution | GitHub Handle | +|----------|---------------------------|----------------------------------- +|loic tetrel | SIMEXP (UDEM) | @ltetrel +|jeremy ravenel | Naas | @jupyter-naas +| Frederic Collonval | QuantStack | @fcollonval +| Afshin T. Darian | Two Sigma | @afshin | +| Zach Sailer | Apple | @Zsailer +| Sarah Gibson | 2i2c | @sgibson91 | +| Martha Cryan | IBM | @marthacryan | +| Karla Spuldaro | IBM | @karlaspuldaro | +| Jessica Xu | | @jess-x | +| Nick Bollweg | Georgia Tech | @bollwyvl @nrbgt | +| Wayne Decatur | Upstate Medical Univ. | @fomightez +|Dane Freeman | Georgia Tech | @dfreeman06 +|Gabriel Fouasnon|Quansight Labs|@gabalafou +| Rollin Thomas | NERSC | @rcthomas | +| Loic Huder| ESRF | @loichuder | +|Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | + +Plus 6 more \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2021-october.md b/docs/source/community/community-call-notes/2021-october.md new file mode 100644 index 000000000..38a1dd415 --- /dev/null +++ b/docs/source/community/community-call-notes/2021-october.md @@ -0,0 +1,71 @@ +# October 26, 2021 + +**Date:** October 26, 2021, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2021-10-26/8:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[YouTube link](https://youtu.be/ik2hG10GlE4)** + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +* **Carol** Thank you Zach for getting discussion started about [Classic notebook and maintainer issues on GitHub](https://github.com/jupyter/notebook/issues/6210). :heart: +* **Rollin** Reminder that Jupyter security calls are on every other Friday ([see community calendar](https://jupyter.readthedocs.io/en/latest/community/content-community.html#jupyter-community-meetings)) +* **Many people** Thank you Darian for years of sustained effort on improving governance! + +## Agenda Items + +* **Rollin** Jupyter security group overview and updates +* **Chris** [Executable book project](https://executablebooks.org/en/latest) updates +* **Simon** [BinderHub updates](https://github.com/jupyterhub/jupyterhub/blob/main/docs/source/changelog.md) +* **Tony** exploring a 7-year old notebook +* **Zach** exploring an 8-year old notebook +* **Darian and Fernando** Update on governance refactor - parts that are now active or coming. + * Relevant PR [jupyter/governance #103](https://github.com/jupyter/governance/pull/103) + * [Slides](https://docs.google.com/presentation/d/1Soa1Cm23WmQ6KOUAvLXzXhe2aE7jmf3vdR84oTd7QPs/edit#slide=id.p) + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- [jupyterlab/jupyterlab #11079](https://github.com/jupyterlab/jupyterlab/pull/11079) Settings UI PR +- [myst](https://myst-parser.readthedocs.io/) +- [The Executable Book Project gallery](https://executablebooks.org/en/latest/gallery.html) +- [Sphinx autoapi](https://sphinx-autoapi.readthedocs.io/) +- [2i2c](https://2i2c.org/) +- [San Diego Python Intro to Python](https://github.com/sandiegopython/intro-to-python) +- [Carol's Journey to Jupyter slides](https://www.slideshare.net/willingc/journey-to-jupyter) +- [papyri](https://github.com/Carreau/papyri) +- [Carol's JupyterHub "A Thing Explainer" slides](https://www.slideshare.net/willingc/jupyterhub-a-thing-explainer-overview) +- https://abigayle-mercer.github.io/Jupyter/CH_3-1.html +- [Jupyter governance office hours on the Jupyter Discourse](https://discourse.jupyter.org/t/governance-office-hours-meeting-minutes/1480/161) +- [Notebook Hall of Fame](https://github.com/jennalandy/notebook-research/blob/master/analysis_notebooks/16_HallOfFame.ipynb) + +## Attendees + +| Name | Institution | GitHub Handle | +|----------|---------------------------|-----------------------------------| +| Fernando Pérez | UC Berkeley, Jupyter | fperez +| Simon Li | University of Dundee | @manics +| Rollin Thomas | NERSC | @rcthomas +| Carol Willing | Noteable | @willingc +| Gabriel Fouasnon | Quansight Labs | gabalafou +| Alex Bozarth | IBM | @ajbozarth +| Karla Spuldaro | IBM | @karlaspuldaro | +| Chris Sewell | Executablebooks | @chrisjsewell | +|Jared Thompson|Comcast|@afonit| +| Loic Huder | ESRF | @loichuder | +| tonyfast | quansight | @tonyfast | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | + +Plus 4 more \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2021-september.md b/docs/source/community/community-call-notes/2021-september.md new file mode 100644 index 000000000..3ccadd1b2 --- /dev/null +++ b/docs/source/community/community-call-notes/2021-september.md @@ -0,0 +1,65 @@ +# September 28, 2021 + +**Date:** September 28, 2021, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2021-09-28/8:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[YouTube link](https://youtu.be/BZLM_clyHwo)** + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html). +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +* **Loïc** Extensions for HDF5 files + * Release 1.0.0 for [jupyterlab-hdf5](https://github.com/jupyterlab/jupyterlab-hdf5) bringing support for JupyterLab 3 + * :thumbsup: Thank You!!! + * Release 0.10.0 for [jupyterlab-h5web](https://github.com/silx-kit/jupyterlab-h5web) removing big files limitation + +## Agenda Items + +* **Angus** would like to introduce the prototype [`jupyterlab-imarkdown`](https://github.com/agoose77/jupyterlab-imarkdown/) and discuss its wider implications. +* **Rollin** would like to share Jupyter security documentation review from Trusted CI + * The review doc from Kay Avila at Trusted CI: https://bit.ly/3ED0zbN + * https://discourse.jupyter.org/t/jupyter-security-related-documentation/10921 + * Will be discussed at next few security meetings (every other Friday, see the [Jupyter calendar](https://discourse.jupyter.org/t/jupyter-community-calendar/2485) for event) + * (Background: https://blog.jupyter.org/trusted-ci-cybersecurity-engagement-with-jupyter-859a5f5d7201) +* **Rick** would like to introduce a new extension and get feedback +* **Theodore** looking for links for good jupyter lab widgets dev tutorials and examples + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. +- https://kidpix.app/ + +## Attendees + +| Name | Institution | GitHub Handle | +|----------------|---------------------------|-----------------------------------| +| Angus Hollands | U Birmingham | @agoose77 | +| Rick McGeer | engageLively | @rickmcgeer | +| Chris Sewell | EPFL / EBP | @chrisjsewell | +| Sarah Gibson | 2i2c | @sgibson91 +| Simon Li | University of Dundee | @manics +| Rollin Thomas | NERSC | @rcthomas | +| Wayne Decatur | Upstate Medical University | @fomightez | +| Karla Spuldaro | IBM | @karlaspuldaro | +| Joyce Er | Microsoft | @joyceerhl | +| Pete Blois | Google | @blois | +| Tony Fast | Quansight | @tonyfast | +| Alex Bozarth | IBM | @ajbozarth | +| Theodore Aptekarev | 🚀 | @piiq | +| Loïc Huder | ESRF | @loichuder | +| Luciano Resende | IBM | @lresende | +| Jessica Xu | Quansight | @jess-x | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | + +Plus 5 others. \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2022-april.md b/docs/source/community/community-call-notes/2022-april.md new file mode 100644 index 000000000..797037e79 --- /dev/null +++ b/docs/source/community/community-call-notes/2022-april.md @@ -0,0 +1,91 @@ +# Jupyter Community Call 04/26 + +**Date:** April 26, 2022, at 7am Pacific (in your [timezone](https://arewemeetingyet.com/Los%20Angeles/2022-04-26/7:00/Jupyter%20Community%20Call)) + +[**Discourse**](https://discourse.jupyter.org/t/jupyter-community-calls/668) + +[**YouTube recording**](https://youtu.be/WDkudE2RvRk) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **Sarah** Shout out to everyone who is here for handling time zones! + +## Agenda Items + +* **[JupyterLab-LaTeX UX improvements PR](https://github.com/jupyterlab/jupyterlab-latex/pull/192)** Result of 2 semesters of work by [Junior Design Capstone class](https://techstyle.lmc.gatech.edu/cs-tech-comm-junior-design-sequence/) team from Georgia Tech done for client (Axle Informatics/NIH). Project included a user research section which is summarized in PR. New features highlights: + * Preview button + * Formatting buttons (bold, italic, underlined, subscript, superscript) + * Autocomplete for common LaTeX tags (i.e. `\subsection`) + * tikzplots templates + * Table creation helper + * Suggestion: UX to help with LaTeX install discovery, errors (even as documentation) + +* **JupyterLab-Git usability improvements** 4 features added to [JupyterLab-Git](https://github.com/jupyterlab/jupyterlab-git) as a result of the [12-week Spring 2022 MLH Fellowship Open-Source Program](https://fellowship.mlh.io/programs/open-source). The majority of the work was done by [Dat Quach](https://github.com/quachtridat) and [Zeshan Fayyaz](https://github.com/ZeshanFayyaz) with help and feedback from [Frédéric Collonval](https://github.com/fcollonval). + * [Credential cache](https://github.com/jupyterlab/jupyterlab-git/pull/1099): save Git login credentials temporarily + * [Commit diff](https://github.com/jupyterlab/jupyterlab-git/pull/1108): compare two arbitrary commits in the *History* panel + * [Reset to remote](https://github.com/jupyterlab/jupyterlab-git/pull/1087): force reset a branch to match its remote tracking branch + * [A warning for unsaved staged files](https://github.com/jupyterlab/jupyterlab-git/pull/1075): warn the user when there are unsaved changes on files that are in the staged area + +* **Frederic** + * _Search and Replace across files_ extension (release in the coming week) + * [GitHub repository](https://github.com/jupyterlab-contrib/search-replace) + * Demo + * The extension is using a CLI tool called [Ripgrep](https://github.com/BurntSushi/ripgrep) + * This limits the usage of the extension to contents served from a file system. + * Potential solutions for building index for other needs (like non OS filesystem) (thanks to Nick): + * https://whoosh.readthedocs.io/en/latest/intro.html + * https://pypi.org/project/lunr/ + +* **Gayle** - Jupyter Community Events Manager + * 4th Round of CFP for Jupyter Community Workshop + * Starting interviews for highlighted contributor write up in blog. If interested schedule time on calendar: https://calendly.com/gayle-numfocus/30min?month=2022-04 + +* **Steve** + * New [cookiecutter](https://github.com/jupyter-server/extension-cookiecutter) template for creating Jupyter Server Extensions + * We created it during the weekly Jupyter Server [contributing hour](https://github.com/jupyter-server/team-compass/issues/22) + +* **Jason W** + * Shout out for triage meetings! (Can be found on the [Jupyter Community Calendar](https://docs.jupyter.org/en/latest/community/content-community.html#jupyter-community-meetings)) + * Typically at 10:00 PDT, though not this week + * You can triage on your own: [JupyterLab issues needing triage](https://github.com/jupyterlab/jupyterlab/labels/status%3ANeeds%20Triage) + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- [lyx]https://www.lyx.org/ +- https://github.com/BurntSushi/ripgrep +- https://whoosh.readthedocs.io/en/latest/intro.html +- https://pypi.org/project/lunr/ + +## Attendees + +| Name | Institution | GitHub Handle| +|------------|---------------------------|--------------| +| Konstantin |Axle Informatics/NIH | @ktaletsk | +| Dat Quach | Major League Hacking (MLH) | @quachtridat | +| Jason Weill | AWS | @jweill-aws | +| Sarah Gibson | 2i2c | @sgibson91 | +| A. T. Darian | QuantStack | @afshin | +| Gayle Ollington|NumFOCUS|@gollington | | +| Frederic Collonval | QuantStack | @fcollonval +| Alex Bozarth | IBM | @ajbozarth | +| Steven Silvester | MongoDB | @blink1073 | +| Chris Sewell | EPFL | @chrisjsewell +| Wayne Decatur | Upstate Medical Univ. | @fomightez +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | + +Plus 1 more. \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2022-august.md b/docs/source/community/community-call-notes/2022-august.md new file mode 100644 index 000000000..dcd4eb54d --- /dev/null +++ b/docs/source/community/community-call-notes/2022-august.md @@ -0,0 +1,57 @@ +# Jupyter Community Call 08/30 + +**Date:** August 30, 2022, at 7am Pacific (in your [timezone](https://arewemeetingyet.com/Los%20Angeles/2022-08-30/7:00/Jupyter%20Community%20Call)) + +[**Discourse**](https://discourse.jupyter.org/t/jupyter-community-calls/668) + +[**Youtube**](https://youtu.be/l_Jv-_9Nv1o) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +* **Isabela** Shout out to the different group of people we have today! New faces or not, thanks for taking the initiative to be here. + +## Agenda Items + +* **Naas** Presenting Naas open source framework to create data products from notebook templates. + * [Jupyter Naas GitHub Repo](https://github.com/jupyter-naas) + * Three main repos: [Naas](https://github.com/jupyter-naas/naas), [awesome-notebooks](https://github.com/jupyter-naas/awesome-notebooks), and [drivers](https://github.com/jupyter-naas/drivers). + * Future facing work can be sampled at [nass-content-engine](https://github.com/jupyter-naas/naas-content-engine). The idea is templates as widgets. +* **Linda or Bosco (Frederic as backup)** - Demonstrate new jupyterlab-git features added through the [MLH](https://mlh.io) Summer 22 program. + > New features are already available in v0.39.0, try it with `pip install -U jupyterlab-git` + > [Full changelog is available there](https://github.com/jupyterlab/jupyterlab-git/releases) +* **Darian** + * [Lumino 2](https://github.com/orgs/jupyterlab/projects/4) update leading up to JupyterLab 4 and Notebook 7 ([migrating JupyterLab to Lumino 2](https://github.com/jupyterlab/jupyterlab/pull/12992)) + * Jupyter Governance update + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- [The Tyranny of Structurelessness - Jo Freeman](https://www.jofreeman.com/joreen/tyranny.htm) + +## Attendees + +| Name | Institution | GitHub Handle| +|----------|---------------------------|--------------| +| Jeremy Ravenel | Naas | @jupyter-naas +| Frederic Collonval | QuantStack | @fcollonval | +| AT Darian | QuantStack | @afshin | +| David Brochart | QuantStack | @davidbrochart | +|Maxime Jublou|Naas|@Dr0p42| +| Gabriel Fouasnon | Quansight Labs | @gabalafou | +| Wayne Decatur | Upstate Medical University | @fomightez | +| Alex Bozarth | IBM | @ajbozarth | +| Eric Holscher | Read the Docs | @ericholscher | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | + +Plus 8 more. \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2022-february.md b/docs/source/community/community-call-notes/2022-february.md new file mode 100644 index 000000000..906069794 --- /dev/null +++ b/docs/source/community/community-call-notes/2022-february.md @@ -0,0 +1,72 @@ +# February 22, 2022 + +**Date:** February 22, 2022, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2022-02-22/8:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[YouTube link](https://youtu.be/-_i1JTRnlXc)** + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **Isabela:** Jupyter accessibility workshops are coming up in March. [Sign up for the March 12 event](https://hopin.com/events/jupyter-accessibility-workshop-intro-to-accesibility-and-inclusive-design-with-eric-bailey). [Sign up for the March 19 event](https://hopin.com/events/jupyter-accessibility-workshop-auditing-in-open-source). +* **Tony:** We now have Jupyter triage meetings (on Thursdays). Find them on the [community calendar](https://docs.jupyter.org/en/latest/community/content-community.html#jupyter-community-meetings) +* **Nick:** [`flit 3.7.0`](https://flit.readthedocs.io/en/stable/history.html#version-3-7) released, supports `data_files` for kernelspecs, extensions, etc. +* **@jasongrout:** We are releasing RC prereleases of ipywidgets 8.0 and 7.7 very soon. Will announce on [Jupyter Discourse](https://discourse.jupyter.org/latest) when it happens. + +## Agenda Items + +* **Ana Ruvalcaba/Gayle Ollington** Introduction and welcome to Gayle, Community Events Manager for Project Jupyter. + * [Jupyter Community Building Committee Charter](https://jupyter.org/governance/communitybuildingcommittee.html) + * [December 2021 Jupyter Community Update](https://blog.jupyter.org/jupyter-community-2021-update-84c5cd3c5e75) +* **Frederic Collonval**: WIP [Jupyter styled components](https://jupyterlab-contrib.github.io/jupyter-ui-toolkit) to speed up your dev. + Come as web components or React components and are ARIA compliant thanks to the underlying [FAST Framework](https://explore.fast.design/). + Related [JEP pre-proposal](https://github.com/jupyter/enhancement-proposals/issues/88) + - Question: will these be eventually used for ipywidgets? Answer: There hasn't been a discussion yet, but it is possible to make a new library (like the ones for Vue and Angular) +* **Jeremy Tuloup, Nicholas Bollweg** [An embeddable REPL powered by JupyterLite](https://jupyterlite.readthedocs.io/en/latest/applications/repl.html), various updates (cache busting, slimer app, Pyodide 0.19) +* **Tasko Olevski, Andreas Bleuler** [Amalthea](https://github.com/SwissDataScienceCenter/amalthea) - A Kubernetes operator for Jupyter Servers. Short introduction to the project and its goals. [Link to presentation](https://docs.google.com/presentation/d/18DvgOFoJko2bd9Cvmd7sSLsV0jbacNPoUfpHtbapeMY/edit?usp=sharing) + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- Today's date is an anagram! 22-02-2022) +- [CarpenPi project](https://github.com/CarpenPi) +- [mamba-org/quetz-frontend repository](https://github.com/mamba-org/quetz-frontend/pull/98) +- [ipydrawio in JupyterLite](https://ipydrawio--92.org.readthedocs.build/en/92/_static/lab/index.html) +- [tangle examples notebook in JupyterLite](https://pidgy.readthedocs.io/en/latest/_/retro/notebooks/index.html?path=tangle_examples.ipynb&room=duck-day-wuack) +- [Renku](https://renkulab.io/) + +## Attendees + +| Name | Institution | GitHub Handle| +|----------|---------------------------|--------------| +| Jason Grout | Databricks | @jasongrout +| Frederic Collonval | QuantStack | @fcollonval | +| Sarah Gibson | 2i2c | @sgibson91 +| David Brochart | QuantStack | @davidbrochart | +| Nick Bollweg | Georgia Tech | @bollwyvl @nrbgt | +|Simon Li 🦆 | University of Dundee| @manics | +|tonyfast | quansight | @tonyfast | +|Tasko Olevski| SDSC / ETH Zürich | @olevski | +| Jeremy Tuloup | QuantStack | @jtpio | +| Simon Adorf | EPFL | @csadorf | +| Andreas Bleuler | SDSC / ETH Zürich | @ableuler | +|Zach Sailer | Apple | @Zsailer | +|Isabela Presedo-Floyd 🦆 | Quansight Labs | @isabela-pf | +|Ana Ruvalcaba | California Polytechnic State University | @Ruv7 +|Gayle Ollington | NumFOCUS + +Plus 6 more diff --git a/docs/source/community/community-call-notes/2022-january.md b/docs/source/community/community-call-notes/2022-january.md new file mode 100644 index 000000000..7ef824f2a --- /dev/null +++ b/docs/source/community/community-call-notes/2022-january.md @@ -0,0 +1,61 @@ +# January 25, 2022 + +**Date:** January 25, 2022, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2022-01-25/8:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[YouTube link](https://youtu.be/zMBAEtEygOA)** + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* Zach has a shout out! Hooray for these calls continuing into 2022! +* Tony: congrats to the team who made the first two Jupyter accessibility workshops happen in the last two weeks +* Steve: Shout out to Zach for being an early adopter of the new Jupyter governance process with jupyter-server! +* Tony: Shout out to Darian for sharing the Jupyter governance process changes with the whole community +* Tony: Great work to the Binder team for keeping Binder ready to go for the world. +* Tony: Thanks to everyone attending for keeping community calls running +* Zach: Cool demo on Twitter of MyST in a Jupyter notebook (this is later on the agenda) + +## Agenda Items + +* **MLflow Kernel Demo** by Jitendra Pandey (jitendra@infinstor.com). MLflow Kernel connects to an MLflow service and records all the data science activities in the Jupyter notebook as MLflow artifacts. It is open source at [infinstor/mlflow-kernel](https://github.com/infinstor/mlflow-kernel) and [Infinstor quickstart: mlflow kernel](https://www.infinstor.com/quickstart/mlflow-kernel.) +* Demonstrations of [Jupyter cache](https://jupyter-cache.readthedocs.io), [JupyterLab MyST](https://github.com/executablebooks/jupyterlab-myst) (and maybe [PR to rewrite myst-nb](https://github.com/executablebooks/MyST-NB/pull/380)) + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- [rst-to-myst](https://github.com/executablebooks/rst-to-myst) + +## Attendees + +| Name | Institution | GitHub Handle| +|----------|---------------------------|--------------| +| jitendra | [InfinStor](https://www.infinstor.com/) | InfinStor +| Frederic Collonval | QuantStack | @fcollonval | +| Chris Sewell | EPFL/EBP | @chrisjsewell +| Sarah Gibson | 2i2c | @sgibson91 +| Simon Li | University of Dundee | @manics +| Rollin Thomas | NERSC | @rcthomas +| Zach Sailer | Apple | @Zsailer +| Adhitya Vadivel | [InfinStor](https://www.infinstor.com/) | @adhityav +| Gabriel Fouasnon | Quansight | @gabalafou | +| Wayne Decatur | Upstate Medical University | @fomightez +| tony fast | Quansight | @tonyfast | +| A. T. Darian | Two Sigma | @afshin | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | + +Plus 6 more \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2022-july.md b/docs/source/community/community-call-notes/2022-july.md new file mode 100644 index 000000000..5ae3c59e1 --- /dev/null +++ b/docs/source/community/community-call-notes/2022-july.md @@ -0,0 +1,63 @@ +# Jupyter Community Call 07/26 + +**Date:** July 26, 2022, at 8am Pacific (in your [timezone](https://arewemeetingyet.com/Los%20Angeles/2022-07-26/8:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[YouTube](https://youtu.be/D6HvNONkhlE)** + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **Darian** Governance update: Executive Council, Software Steering Council, Distinguished Contributors +* **Darian** [Lumino 2](https://github.com/jupyterlab/lumino/pull/319) +* **rcthomas** Reminder on Github 2FA for Jupyter Project developers + * https://blog.jupyter.org/requiring-2fa-for-jupyter-github-organizations-ad15507da9b1 +* **nick** [voila-dashboards](https://github.com/voila-dashboards/voila/pull/846) almost works with lab (no more cdnjs/unpkg, etc.) +* **fcollonval** JupyterLab 3.4.4 released - [Changelog](https://github.com/jupyterlab/jupyterlab/releases/tag/v3.4.4) +* **Isabela** JupyterLab accessibility calls are still happening, and everyone is welcome. Our next call is tomorrow at 10:15am Pacific! +* **nick** [ipywidgets latest docs](https://ipywidgets.readthedocs.io/en/latest/) now include jupyterlite demos + +## Agenda Items + +* **Isabela** Favorite community call memories/what you want next + * Demos of work people are building on top of Jupyter (but not sales pitches) + * "Pie" + * Themes for calls! + * Lightning talk length of share (right now we have one minute or ten) + * "live demos are always good even if they're incomplete" + * "I'd like people to report a new thing they learned "today I learned" using a Jupyter notebook recently" + * Sign up sheet to mix up hosts! Good for everyone to get experience and can bring in new energy. + * Recognize testers + * Once a quarter: "here's four ways you can contribute" as a recurring topic so people get reminded and don't have to watch the back catalog to hear it (or a list of projects to contribute to) + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- [The New Soul Vegetarian Cookbook](https://www.amazon.com/New-Soul-Vegetarian-Cookbook/dp/0942683137 https://www.amazon.com/Grit-Cookbook-World-Wise-Down-Home-Recipes/dp/1556526482) + +## Attendees + +| Name | Institution | GitHub Handle| +|----------|---------------------------|--------------| +| Frederic Collonval | QuantStack | @fcollonval | +| Simon Li | University of Dundee | @manics | +| A. T. Darian | QuantStack | @afshin | +| Wayne Decatur | Upstate University | @fomightez | +| Rollin Thomas | NERSC | @rcthomas | +| Jeremy Tuloup | QuantStack | @jtpio | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | + +Plus 4 more. \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2022-june.md b/docs/source/community/community-call-notes/2022-june.md new file mode 100644 index 000000000..8d0e05980 --- /dev/null +++ b/docs/source/community/community-call-notes/2022-june.md @@ -0,0 +1,49 @@ +# Jupyter Community Call June 28 + +**Date:** June 28, 2022, at 3am Pacific (in your [timezone](https://arewemeetingyet.com/Los%20Angeles/2022-06-28/15:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[YouTube Link](https://youtu.be/pyEE4tjsj3U)** + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +- Steve: coming soon - getting rid of ``setuptools`` for extension authors - work is being coordinated on a PR on [JupyterLab](https://github.com/jupyterlab/jupyterlab/pull/12606) +- Nick: [jupyterlite](https://github.com/jupyterlite/jupyterlite/releases/tag/v0.1.0b10) kernels can now access contents directly + +## Agenda Items + +* **Tony** ??? ([how general is the nbformat?](https://gist.github.com/tonyfast/6c236af7dcaa87fc012f31b720575dd7)) + * And where are we going next + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- [My Brainfuck CPU - A simple Processor in Python via MyHDL (part 1)](https://nbviewer.org/github/sandbender/BF_CPU/blob/master/BF_MYHDL_CPU_v2.ipynb) +- [jmshea/digicom-jupyter Digital Communications JupyterLite Site](https://github.com/jmshea/digicom-jupyter) +- [Idea: Binder + JupyterLite = BinderLite? (Jupyter Discourse)](https://discourse.jupyter.org/t/idea-binder-jupyterlite-binderlite/14449) +- [Neal Brennan: 3 Mics](https://www.imdb.com/title/tt6438918/?ref_=nm_flmg_wr_7) +- [Types - Web Assembly](https://webassembly.github.io/spec/core/syntax/types.html) + +## Attendees + +| Name | Institution | GitHub Handle| +|------------------|---------------------------|--------------| +| Steven Silvester | MongoDB | @blink1073 +| Nick Bollweg | Georgia Tech | @bollwyvl +| A. T. Darian| QuantStack | @afshin | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf +| Tony Fast | Quansight | @tonyfast | + +Plus 1 more. \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2022-march.md b/docs/source/community/community-call-notes/2022-march.md new file mode 100644 index 000000000..b9105c4cd --- /dev/null +++ b/docs/source/community/community-call-notes/2022-march.md @@ -0,0 +1,31 @@ +# March 29, 2022 + +**Date:** March 29, 2022, at 8am Pacific (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2022-03-29/8:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +There is no recording for this call. + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **Zach** [voila-gridstack](https://github.com/voila-dashboards/voila-gridstack) is great and Zach can't wait for a release on PyPI sometime soon! + * [viola-dashboards/voila #846 Switch to a lab-based app for the Voila frontend ](https://github.com/voila-dashboards/voila/pull/846) + +## Agenda Items + +With time changes, this meeting was accidentally double-booked with the Jupyter Security meeting! Since we had an open agenda before the community call, our notes overlap with theirs. + +For notes from this call, please refer to the [March 29, 2022 jupyter/security meeting notes!](https://github.com/jupyter/security/tree/main/meetings/2022-03-29.md) \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2022-may.md b/docs/source/community/community-call-notes/2022-may.md new file mode 100644 index 000000000..04129cae2 --- /dev/null +++ b/docs/source/community/community-call-notes/2022-may.md @@ -0,0 +1,72 @@ +# Jupyter Community Call May 31 + +**Date:** May 31, 2022, at 7am Pacific (in your [timezone](https://arewemeetingyet.com/Los%20Angeles/2022-05-31/7:00/Jupyter%20Community%20Call)) + +**[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668)** + +**[YouTube link](https://youtu.be/KzH7yJ07PgQ)** + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +* **Isabela:** Shout out to the security team for rolling out awesome documentation on the [Jupyter Vulnerability Handling Process](https://github.com/jupyter/security/blob/main/docs/vulnerability-handling.md#roles)! + +* **Isabela:** Reminder that the [Jupyter Community Workshops call for proposals](https://blog.jupyter.org/jupyter-community-workshops-c7491a3cca00) has been extended! You can now apply until June 6. + +* **Mike** Organising an internal intermediate/advanced jupyter training at Oxford, anything cool you would like to to share with biomedical researchers? + * Matthias: I would search a bit on the napari side. + * Chris Holdgraf is in Europe and runs [2i2c](https://2i2c.org/), he might be a good person to ask. + * Romeo: reach out about relevant talks + * Deep Learning in biomedical and genomics data + * ...using JuypterLab + * ...using Elyra Pipelines + * Deep Learning based image analysis in Radiology + * An overview and life demo of JupyterLab Extensions for Genomics + * An overview and life demo of JupyterLab Extensions for Life Science +* [Please don’t disable authentication in Jupyter servers- Jupyter blog](https://blog.jupyter.org/please-dont-disable-authentication-in-jupyter-servers-dd197206e7f6) + +* **Matthias**: SciPy draft done! Hooray! +* **Gayle**: Shout out to Sylvain for speaking at the upcoming [PyData London](https://pydata.org/london2022/) + +## Agenda Items + +Add agenda items here **before** the meeting. We will reorganize the agenda so that it fits in the 60m meeting slot. + +* **Name** This is an example of agenda item formatting. + +* **Matthias** And https://github.com/jupyter/jupyter.github.io/pull/696, we'd love to know if some folks want to participate / help handle the process – no need to be be a security expert. +* **Matthias** Question : Anything to organise about SciPy ? + * Gayle: there is interest in organizing, but we need ideas! Reach out if there's something you'd like to organize. + * Isabela: not aware of anything that has developed yet, but can ask around. +* **Isabela** Sharing two cool resources I don't see talked about often: + * [jupyter/surveys](https://github.com/jupyter/surveys) + * [JupyterLab user stories](https://github.com/jupyterlab/jupyterlab/tree/master/design) + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- A curated list of awesome Jupyter projects, libraries and resources at [markusschanta/awesome-jupyter](https://github.com/markusschanta/awesome-jupyter) +- A curated list of awesome JupyterLab extensions and resources at [mauhai/awesome-jupyterlab](https://github.com/mauhai/awesome-jupyterlab) + +## Attendees + +| Name | Institution | GitHub Handle| +|----------|---------------------------|--------------| +| Wayne Decatur | Upstate Medical University | @fomightez +| Michał Krassowski | Oxford | @krassowski +| Gayle Ollington|NumFOCUS|@gollington | | +| Eric Gentry | Anaconda | @ericsnekbytes | +| Romeo Kienzler | IBM (CODAIT) | @romeokienzler | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | + +Plus one more. \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2022-november.md b/docs/source/community/community-call-notes/2022-november.md new file mode 100644 index 000000000..de9188162 --- /dev/null +++ b/docs/source/community/community-call-notes/2022-november.md @@ -0,0 +1,50 @@ +# Jupyter Community Call 11/29 + +**Date:** November 29, 2022, at 7am Pacific (in your [timezone](https://arewemeetingyet.com/Los%20Angeles/2022-11-29/7:00/Jupyter%20Community%20Call)) + +[**Discourse**](https://discourse.jupyter.org/t/jupyter-community-calls/668) +[**Youtube**](https://youtu.be/GsOjIvV7ymY) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +There were no short reports this month. + +## Agenda Items + +* **Gabriela Vives** Present a usability study done on JupyterLab +* **Eric Gao** Jupyter+Apache DolphinsSheduler Demo +* **Nick Bollweg** [jupikchr](https://github.com/deathbeds/jupikchr): pikchr plain-text diagrams for JupyterLab, etc. + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- [jupyter/surveys](https://github.com/jupyter/surveys) +- [Jupyter community building committee](https://jupyter.org/governance/communitybuildingcommittee.html) +- [JupyterLite as a frontend for software forges - Jupyter Discourse](https://github.com/jupyterlite/jupyterlite/discussions/874) + +## Attendees + +| Name | Institution | GitHub Handle| +|----------|---------------------------|--------------| +| Yuze Ma | Alibaba Cloud | bobmayuze | +| Frederic Collonval| QuantStack | @fcollonval +| Gabriela Vives | QuantStack |GabrielaVives +|Matthew Seal|Noteable Inc|MSeal| +| Wayne Decatur|Upstate Medical University|fomightez | +| Eric Gao | Jupyter+Apache DolphinsSheduler Demo | EricGao888 | +|tonyfast | unaffiliated | @tonyfast | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | + +Plus 11 more. \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2022-october.md b/docs/source/community/community-call-notes/2022-october.md new file mode 100644 index 000000000..fb707e22b --- /dev/null +++ b/docs/source/community/community-call-notes/2022-october.md @@ -0,0 +1,58 @@ +# Jupyter Community Call 10/25 + +**Date:** October 25, 2022, at 7am Pacific (in your [timezone](https://arewemeetingyet.com/Los%20Angeles/2022-10-25/7:00/Jupyter%20Community%20Call)) + +[**Discourse**](https://discourse.jupyter.org/t/jupyter-community-calls/668) +[**Youtube**](https://youtu.be/RHGYVTYI1bg) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +* Shout out to all the cats and kittens on the call! +* **Sarah** JupyterHub is participating in Outreachy and has lots of applicants! +* **Isabela** Earlier this month, a group of people met to do [keyboard navigation manual tests on the Jupyter Notebook 7 prerelease](https://github.com/jupyter/notebook/issues/6595). It was great to have people meeting to work on accessibility. +* **Steve** Python 3.11 was released yesterday. + +## Agenda Items + +* **Jan-Hendrik Müller, Ricky Alinsky**: A new perspective on creating example galleries from notebooks. + * Plywood gallery (and its VS Code extension!) + * https://discourse.jupyter.org/t/plywood-gallery-generate-python-documentation-via-notebooks/16510 +* **deathbeds**: a bike shed means blood shed + * "when markdown and python collide" - https://tonyfast.github.io/tonyfast/run/lab/index.html?path=xxii/oct/2022-10-21-markdown-future.ipynb?room=deathbeds-more-like-deft-breads + * https://github.com/tonyfast/midgy + * https://github.com/deathbeds/pidgy + * https://github.com/deathbeds/importnb + * https://github.com/tonyfast/tonyfast + * "Spooky-ber Note-boo-ks" with [jupyterlab-deck](https://github.com/deathbeds/jupyterlab-deck) and a history of presenting in notebooks and a reporting deck (with Robot Framework). +* **Debra Chen, Niko Zeng**: Invitation for joint-holding community meetup + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- [Open Source Design Discourse](https://discourse.opensourcedesign.net/) +- [Jupyter Discourse](https://discourse.jupyter.org/) + +## Attendees + +| Name | Institution | GitHub Handle| +|----------|---------------------------|--------------| +| Jan-Hendrik Müller | University of Göttingen | @kolibril13 +| Ricky M. Alinsky | GUSTO University | @Rickaym +| Steve Silvester | MongoDB | @blink1073 | +| Debra Chen | DolphinScheduler community |@debrachena +| Sarah Gibson | 2i2c | @sgibson91 +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf + +Plus 7 more. diff --git a/docs/source/community/community-call-notes/2022-september.md b/docs/source/community/community-call-notes/2022-september.md new file mode 100644 index 000000000..4da000389 --- /dev/null +++ b/docs/source/community/community-call-notes/2022-september.md @@ -0,0 +1,54 @@ +# Jupyter Community Call 09/27 + +**Date:** September 27, 2022, at 7am Pacific (in your [timezone](https://arewemeetingyet.com/Los%20Angeles/2022-09-27/7:00/Jupyter%20Community%20Call)) + +[**Discourse**](https://discourse.jupyter.org/t/jupyter-community-calls/668) + +[**Youtube**](https://youtu.be/DDdwyQLWnUU) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **[jupyterlite 0.1.0b13](https://github.com/jupyterlite/jupyterlite/blob/main/CHANGELOG.md#010b13)** is released, with support for [ipywidgets 8](https://github.com/jupyter-widgets/ipywidgets/releases/tag/8.0.0) + +## Agenda Items + +* Peter Vidos **[ipyvizzu-story](https://github.com/vizzuhq/ipyvizzu-story)** - A short intro of a new, open-source data storytelling tool for Jupyter Notebook. + * Repo: https://github.com/vizzuhq/ipyvizzu-story + * Example (HTML): https://vizzuhq.github.io/ipyvizzu-story/examples/demo/ipyvizzu-story_example.html +* **Yuze** Questions about Jupyter community in the APAC region + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- [Books by Alberto Cairo](https://en.wikipedia.org/wiki/Alberto_Cairo#Books) +- [Animated charts and story telling with IpyVizzu](https://discourse.holoviz.org/t/animated-charts-and-story-telling-with-ipyvizzu/3622) +- [Charting Data guidelines - Apple Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines/patterns/charting-data) +- [Chartability](https://chartability.fizz.studio/) +- [Join the Vizzu Community Slack](https://join.slack.com/t/vizzu-community/shared_invite/zt-w2nqhq44-2CCWL4o7qn2Ns1EFSf9kEg) +- [JupyterHub team compass](https://github.com/jupyterhub/team-compass/) + +## Attendees + +| Name | Institution | GitHub Handle| +|----------|---------------------------|--------------| +| AT Darian | QuantStack | @afshin | +| Alex Bozarth | IBM | @ajbozarth | +|Yuze Ma |Alibaba Group | @bobmayuze +|Wayne Decatur |Upstate Med. University | @fomightez +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf + +Plus 5 more \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2023-december.md b/docs/source/community/community-call-notes/2023-december.md new file mode 100644 index 000000000..bde1c3232 --- /dev/null +++ b/docs/source/community/community-call-notes/2023-december.md @@ -0,0 +1,109 @@ +# Jupyter Community Call 12/13 + +**Date:** December 13, 2023, at 9:00AM PST (your [timezone](https://arewemeetingyet.com/Los%20Angeles/2023-12-13/9:00/Jupyter%20Community%20Call)) + +[**Discourse**](https://discourse.jupyter.org/t/jupyter-community-calls/668) + +[**Youtube**](https://youtu.be/hUU77BfU-Kk) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **tonyfast** - [dec community call introduction](https://github.com/tonyfast/tonyfast/blob/main/tonyfast/xxiii/2023-12-13-jupyter-community-call.ipynb) +* **Ana Ruvalcaba** Project Jupyter is now active on Mastodon! Follow us there for the latest Jupyter news and announcements. Please note that @mentions are not monitored. https://hachyderm.io/@ProjectJupyter +* **Mike Krassowski** JupyterLab 4.1 beta call for testing. + + +## Agenda Items + +* **Michael Goerz** [A Python local `.venv` kernel](https://github.com/goerz/python-localvenv-kernel) (5 min) +* **Eric Gentry** A new in-development [JupyterLab hex editor](https://github.com/ericsnekbytes/hexlab) +* **Shravan Achar** A "Share" button for Jupyter Notebooks (5 min). +* **Nick Bollweg** [jupyak](https://github.com/deathbeds/jupyak): a pipeline pushing pulls of projects to pages of pixels for people, across the Jupyter stack +* **Kyle Kelley** demoing the Deno TypeScript kernel for jupyter. + * [Deno Kernel Announce Post](https://blog.jupyter.org/bringing-modern-javascript-to-the-jupyter-notebook-fc998095081e) + * [Deno Notebooks](https://github.com/rgbkrk/denotebooks) +* **Mason Williams** demoing [Pieces for Developers](https://pieces.app) and our [JupyterLab extension](https://docs.pieces.app/extensions-plugins/jupyterlab). +* **Andrey Velichkevich** A collaborative notebook training/tuning ML models on GPUs (powered by KubeFlow) (5 min). + * KubeCon 2024 Talk for the full demo - https://youtu.be/sn2qe225E1o + * Be involved into Kubeflow Community - https://www.kubeflow.org/docs/about/community/ +* **Mike Krassowski** Inline completer API and integration with jupyter-ai. + +## Notes and Other Links + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +### Python local-`.venv` kernel + +* Project on Github: https://github.com/goerz/python-localvenv-kernel +* The FAQ: https://github.com/goerz/python-localvenv-kernel/blob/master/FAQ.md. This includes information on how to make the kernel work for something other than a `.venv` folder. For example (as asked during the call), this might be used to support `.jupyter` populated by https://github.com/jupyterlab/jupyterlab-desktop (TBD) +* Notes on the type of Makefile used in the demo: https://github.com/goerz/python-localvenv-kernel/wiki/Project-Makefile-using-Pip-Tools +* "Old" project example with an installable kernel: https://github.com/ARLQCI/2022-04_semiad_paper +* "New" project is not public yet. When published, links to example repos will be added to the `python-localvenv-kernel` README / Wiki + +### Pieces for Developers | AI-Enabled Developer Workflow Assistant + +* Install our JupyterLab Extension: [JupyterLab Extension Documenation page](https://docs.pieces.app/extensions-plugins/jupyterlab) +* Learn more about Pieces: [Pieces Documenation Site](https://docs.pieces.app) +* Check out our Open Source projects: [Pieces Open Source GitHub Repo](https://github.com/pieces-app/opensource) +* Join our Discord Server: [Pieces Discord Server](https://discord.gg/getpieces) + +### Inline completer + +- [Extension point documentation](https://jupyterlab.readthedocs.io/en/latest/extension/extension_points.html#inline-completer) +- [API documentation for `IInlineCompletionProvider`](https://jupyterlab.readthedocs.io/en/latest/api/interfaces/completer.IInlineCompletionProvider.html) +- https://github.com/krassowski/jupyterlab-transformers-completer +- https://github.com/jupyterlab/jupyter-ai/pull/465 (connecting models) +- https://github.com/jupyterlab/jupyterlab/pull/15160 (frontend) + +## Attendees + +| Name | Institution | GitHub Handle | +|----------|---------------------------|-----------------------------------| +| Shravan Achar | Apple | @shravan-achar +| Andrey Velichkevich | Apple | @andreyvelich +| Zach Sailer | Apple | @Zsailer +| [Michael Goerz](https://michaelgoerz.net) | U.S. Army Research Lab | [@goerz](https://github.com/goerz/) +| Philipp Risius | Justus Liebig University Giessen | @philipprisius +| Nick Bollweg | Georgia Tech | @bollwyvl +| Kyle Kelley | Noteable | @rgbkrk +| Amogha Kancharla | WomeninCloudNative | @amoghak-ds +| [Mason Williams](https://masnwilliams.com) | [Pieces for Developers](https://pieces.app) | [@mason-at-pieces](https://github.com/mason-at-pieces) / [@masnwilliams](https://github.com/masnwilliams) +| Mike Krassowski | Quansight | [@krassowski](https://github.com/krassowski) | +| Eric Gentry | Anaconda | @ericsnekbytes | +| Sergey Kukhtichev | IBM | @skukhtichev | +| Ana Ruvalcaba | Project Jupyter | @Ruv7 | +| Luciano Resende | Apple | @lresende | +| Andrii Ieroshenko | AWS | @andrii-i | +| Jason Weill | AWS | @JasonWeill | +| Jeremy Tuloup | QuantStack | @jtpio | +| Simon Li | University of Dundee | @manics | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | +| Jared Thompson|Comcast| | +| Nicolas Brichet | QuantStack | @brichet | +| Rosio Reyes | Anaconda | @RRosio | +| Frederic Collonval | | @fcollonval | +| Carlos Brandt | Constructor University | @chbrandt | +| Rollin Thoams | NERSC | @rcthomas | +| Gabriel Fouasnon | Quansight Labs | @gabalafou | +| Jan-Hendrik Müller | University Göttingen | @kolibril13 | +| Arunav Gupta | AWS | @agupta01 | +| Ian Dong | Apple | @misterfads | +| Mehmet Bektas | Netflix | @mbektas | +| Amola Hinge | Apple | @amolahinge| +| Wayne Decatur | Upstate Medical University | @fomightez | +| Martha Cryan | Mito | @marthacryan | +| R Ely | Bloomberg | @ohrely | +| Jialin Zhang| Apple | @jzhang20133 | diff --git a/docs/source/community/community-call-notes/2023-february.md b/docs/source/community/community-call-notes/2023-february.md new file mode 100644 index 000000000..3bb8aa333 --- /dev/null +++ b/docs/source/community/community-call-notes/2023-february.md @@ -0,0 +1,106 @@ +# Jupyter Community Call 2/28 + +**Date:** February 28, 2023, at 8am Pacific ([your timezone](https://arewemeetingyet.com/Los%20Angeles/2023-02-28/08:00/Jupyter%20Community%20Call)) + +[**Discourse:**](https://discourse.jupyter.org/t/jupyter-community-calls/668) +[**Youtube**](https://youtu.be/718KFe6MMW4) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **Isabela** Many thanks to the Security project team for being flexible and helping community call have this time on the calendar! + * Security calls are now 1st and 3rd Tuesday of every month + * Community call is last Tuesday + * No collisions anymore, can move community call to more friendly time! :) +* **Isabela** Governance update: Software Steering Council is in the process of getting office hours on the calendar and resuming all other duties. + +## Agenda Items + +* @rowanc1 @agoose77 - `jupyterlab-myst` overview and demo https://github.com/executablebooks/jupyterlab-myst + * MyST: Markup language incubated in executable books project, spun out last week + * 10% of Python documentation is written MyST and increasing + * Moving toward Javascript world => better integration with JupyterLab + * See myst-tools.org, new website for the project + * MyST: Support for scientific documents and publications, export to various high-quality PDF formats + * Also rendered static versions of Jupyter notebooks + * What metadata and front-matter needs to be added + * How to bring computational thinkin into publishing + * JupyterLab MyST extension + * Rich metadata as data at the top of document (YAML) + * Executing the metadata cells yields a nice top block for a notebook + * Nicer than custom HTML, parseable, better to edit and view + * Callout blocks: + * Bracketed directives like ":::{important}" + * Also class information like dropdown + * Cross-references + * Inline execution in markdown cells + * Syntax subject to change + * Roles and directives e.g. + ``` + {eval}`1+1` + ``` + * Embed Jupyter widgets directly in markdown, figures, sparklines + * Better weaving of documentation and code + * Ongoing nbformat workshop and MyST + * Discussing the challenges of developing the extension + * In particular, embedding computation in documentation, wasn't originally envisioned + * Input types may need to expand + * Static publishing, see also https://thebe.readthedocs.io/en/stable/ + * Write documents with interactivity + * Publishing mechanisms + * Help promote interactivity and computation experience to the end sharing of documents + * Mixing HTML and MyST and accessibility? + * Keeping these issues in mind during development + * Gets more difficult with widgets + * Efforts to use the same technology pieces as Jupyter + * => as Jupyter improves things upstream in widgets space it propagates here + * Archivability, semantic HTML, paying attention to accessibility scores + * https://myst-tools.org/docs/mystjs/accessibility-and-performance +* Ongoing nbformat workshop discussion @isabela-pf + * We don't have a type of Markdown we specify in notebooks + * This has created some difficulty during user testing + * Would be nice to at least know what kind of Markdown specification we're following + * There are web accessibility guidelines, not clear always how they correlate + * Greater clarity would help because accommodations get hooked in at the HTML level + * At the workshop @rowanc1: + * Split into 3 groups + * Text-based format in addition to standard format (e.g. jupytext) + * Cell types workflow + * Markdown formats inside cells + * The wild west of notebook, cell metadata, how do people use it? + * Noteable example + * Front-end interfaces that don't go through Jupyter/JupyterLab + * Visualization state stored in cell metadata + * Namespaced in noteable + * Are there changes in terms of cell metadata being considered PR/discourse wise? + * Discourse: ??? + * Maybe [Jupyter Discourse: Notebook Metadata UX](https://discourse.jupyter.org/t/notebook-metadata-ux/17507_) + * Simplest use case (kinda) marking cell metadata for special treatment or processing + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +## Attendees + +| Name | Institution | GitHub Handle | +|----------|---------------------------|-----------------------------------| +| Rollin | NERSC | @rcthomas | +| Rowan | Curvenote / ExecutableBooks | @rowanc1 | +| Gabriela Vives |QuantStack |GabrielaVives | +| Wayne Decatur | Upstate Medical Univ. | @fomightez | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | + +Plus 1 more. diff --git a/docs/source/community/community-call-notes/2023-january.md b/docs/source/community/community-call-notes/2023-january.md new file mode 100644 index 000000000..a5f6590c8 --- /dev/null +++ b/docs/source/community/community-call-notes/2023-january.md @@ -0,0 +1,61 @@ +# Jupyter Community Call 1/31 + +**Date:** January 31, 2023 at 7am Pacific (in your [timezone](https://arewemeetingyet.com/Los%20Angeles/2023-01-31/7:00/Jupyter%20Community%20Call)) + +[**Discourse**](https://discourse.jupyter.org/t/jupyter-community-calls/668) +[**Youtube**](https://youtu.be/LjgctsAIubQ) + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-meetings/423). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **Isabela** We've officially hit two years of consecutive Jupyter community calls! Thank you all for supporting our community. +* **Nick** Recent [release of traitlets](https://blog.jupyter.org/announcing-a-new-jupyter-governance-model-and-our-first-executive-council-39b3989dc064) supports tab completion +* **Gayle** [Blog post](https://blog.jupyter.org/announcing-a-new-jupyter-governance-model-and-our-first-executive-council-39b3989dc064) about Jupyter governance launch + +## Agenda Items + +Add agenda items here **before** the meeting. We will reorganize the agenda so that it fits in the 60m meeting slot. + +* **Stephen Macke**: [IPyflow](https://github.com/ipyflow/ipyflow): a dataflow-aware Python kernel for JupyterLab +* **Nick Bollweg**: [jyg](https://github.com/deathbeds/jyg): run JupyterLab commands from the CLI... or other browser windows +* **Gayle**: [Jupytercon](https://www.jupytercon.com/)! How would you promote the event? Reach out at gayle@numfocus.org +* **Kafonek**: Are any Jupyter-collaborative meetings (Y-py, etc) still going on? Have tried to connect to those communities and had trouble. Also would like to push for pypi to host wasm wheels. + +## Other Links Shared + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +* [deathbeds/jupyterlab-starters](https://github.com/deathbeds/jupyterlab-starters) +* [JupyterLab example for adding items to the launcher](https://github.com/jupyterlab/extension-examples/tree/master/launcher) +* [jupyter_app_launcher](https://github.com/trungleduc/jupyter_app_launcher) +* [jupyterlab_commands](https://github.com/timkpaine/jupyterlab_commands) +* [ipylab](https://github.com/jtpio/ipylab) + +## Attendees + +| Name | Institution | GitHub Handle| +|----------|---------------------------|--------------| +| nick bollweg | deathbeds | @bollwyvl | +| stephen macke | meta | [@smacke](https://github.com/smacke) | +| matt kafonek | noteable | [@kafonek](https://github.com/kafonek) | +| Frederic Collonval | QuantStack | @fcollonval | +| Gayle Ollington | NumFOCUS | @gollington | +| Wayne Decatur | Upstate Medical Univ. | @fomightez | +| Carlos Brandt | Constructor Univ. | @chbrandt | +| tonyfast | deathbeds | @tonyfast | +| A. T. Darian | QuantStack | @afshin | +| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf | + +Plus 3 more \ No newline at end of file diff --git a/docs/source/community/community-call-notes/2024-november.md b/docs/source/community/community-call-notes/2024-november.md new file mode 100644 index 000000000..6453dddfc --- /dev/null +++ b/docs/source/community/community-call-notes/2024-november.md @@ -0,0 +1,78 @@ +--- +tags: jupyter +--- +# November 2024 Jupyter Community Call + +**Date:** November 13, 2024, at 9:00 AM PST / 16:00 UTC ([in your timezone](https://arewemeetingyet.com/Los%20Angeles/2024-11-13/9:00/Jupyter%20Community%20Call)) + +**Video-conference link:** https://zoom.us/my/jovyan?pwd=c0JZTHlNdS9Sek9vdzR3aTJ4SzFTQT09 + +**Discourse:** https://discourse.jupyter.org/t/jupyter-community-calls/668 + +**Sign up to present:** Add your name and topic to the Agenda Items in this document. + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +## Attendees + +If you are joining the Jupyter Community Call, sign in below so we know who was here. + +| Name | Institution | GitHub Handle | +|----------|---------------------------|-----------------------------------| +|Darshan Poudel |Pulchowk Campus |@darshan808 | +| Mike Krassowski | Quansight | @krassowski | +|William Stein | CoCalc | @williamstein | +| Zach Sailer | Apple | @Zsailer | +| Gabriel Fouasnon | Quansight Labs | @gabalafou | +| Jason Weill | AWS | @JasonWeill | +| R Ely | Bloomberg | @ohrely | +| Luciano Resende | Apple | @lresende | +| Fernando Pérez| UC Berkeley | @fperez | +| Nick Byrne | Quansight | @nenb | +| Ana Ruvalcaba | Cal Poly | @Ruv7 | +| Ian Thomas | QuantStack | @ianthomas23 | +| Florence Haudin | QuantStack | @HaudinFlorence | +| Simon Li | University of Dundee | @manics | +| Eric Charles | Datalayer | @echarles | +| Rosio Reyes | Anaconda | @RRosio | +| Martha Cryan | Plotly | @marthacryan | + +## Purpose + +Community calls provide a place for Jupyter community members to announce and share fun things that they're doing. We encourage brief (5 minutes or less) presentations with a demo or screen share, as needed. If you have a GitHub repo or demo web site, please share it! We recommend sharing open source or otherwise freely available work. + + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **Jupyter Calendar** — All public community meetings can be found here. You are welcome to join to observe and participate. https://jupyter.org/community#calendar + +## Agenda items + +Add agenda items here **before** the meeting. We will reorganize the agenda so that it fits in the 60-minute meeting slot. + +_Add your talk to the agenda here._ You can include links in `[Markdown format](https://www.example.com)`. + +* **Fernando Pérez:** Governance Update: [Jupyter is now a part of LF Charities](https://blog.jupyter.org/project-jupyter-joins-lf-charities-6daa30a46dab)! +* **Eric Charles**: Elastic Kernels: From Pyodide to GPU. +* **Zach Sailer**: [A new in-cell _intelligence_ feature](https://github.com/Zsailer/jupyterlab-magic-wand) +* **Ian Thomas**: New experimental JupyterLite Terminal. +* **Mike Krassowski** [Nebari][nebari] contributions to extension ecosystem: [jupyterlab-launchpad][launchpad] and [jupyterlab-gallery][gallery] +* **Nick Byrne** Using Jupyterlab [extension-examples][examples] to quickly build extensions. + +[nebari]: https://www.nebari.dev/ +[launchpad]: https://github.com/nebari-dev/jupyterlab-launchpad +[gallery]: https://github.com/nebari-dev/jupyterlab-gallery +[examples]: https://github.com/jupyterlab/extension-examples + +## Notes and other links + +This is a space to store links shared during community call discussions related to or separate from the agenda items. + +- Link to nebari blog post: https://quansight.com/post/a-quick-overview-of-nebari/ + + diff --git a/docs/source/community/community-call-notes/2025-february.md b/docs/source/community/community-call-notes/2025-february.md new file mode 100644 index 000000000..f98fc2cae --- /dev/null +++ b/docs/source/community/community-call-notes/2025-february.md @@ -0,0 +1,81 @@ +# February 2025: Jupyter Community Call + +**Date:** February 19, 2025, at 9am PST / 17:00 UTC; your timezone ([your timezone](https://arewemeetingyet.com/Los%20Angeles/2025-02-19/09:00/Jupyter%20Community%20Call)) + +**Video-conference link:** [Zoom link](https://zoom.us/j/95228013874?pwd=Ep7HIk8t9JP6VToxt1Wj4P7K5PshC0.1) + +**Discourse:** https://discourse.jupyter.org/t/jupyter-community-calls/668/101?u=ruv7 + +**Give feedback or ideas for future calls:** Email the DEI Committee - jupyter-dei@googlegroups.com + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +**Welcome!** + +If you are joining the Jupyter Community Call, sign in below so we know who was here. + +| Name | Institution | GitHub Handle | +|-----------------|---------------------------|-------------------------------------------------| +| Jordan Bradford | Boston College | [jrdnbradford](https://github.com/jrdnbradford) +| Kyle Smith | GitNotebooks | [smith-kyle](https://github.com/smith-kyle)| +| David Qiu | AWS | @dlqqq | +| Arjun Verma | QuantStack | [arjxn-py](https://github.com/arjxn-py)| +| Rosio Reyes | Anaconda | @RRosio | +| Rick Wagner | San Diego Supercomputer Center | @rpwagner | +| Wayne Decatur | Upstate Medical Univeristy | [@fomightez](https://github.com/fomightez) | +| Matt Fisher | Schmidt center for Data Science & Environment @ UC Berkeley | [@mfisher87](https://github.com/mfisher87/) | +| Ana Ruvalcaba | Cal Poly State University | @Ruv7 | +|Johanna Bayer | Donders Institute for Brain Cognition and Behaviour (Netherlands) | [@likeajumprope](https://github.com/likeajumprope) | +| Mike Krassowski | Quansight | @krassowski | +| Michael Chin | AWS | [@michaelnchin](https://github.com/michaelnchin) | +| Kirstie Whitaker | Berkeley Institute for Data Science (California, USA) | @KirstieJane | +| Chris Holdgraf | [2i2c](https://2i2c.org) | [@choldgraf](https://github.com/choldgraf) | +| Jeremy Tuloup | QuantStack | @jtpio | +| Keerthi Swarna| AWS |[@keerthi-swarna](https://github.com/keerthi-swarna) | +| Dan Yeaw | Anaconda | [@danyeaw](https://github.com/danyeaw) | +|Pranav Khandelwal | AWS | [@pranavkhandelwal](https://github.com/pranavkhandelwal) | +| Afshin T. Darian | QuantStack | @afshin | +|Nicolas Brichet | QuantStack | @brichet | +|Florence Haudin | QuantStack | @HaudinFlorence | +|Brian Granger | AWS | @ellisonbg | +|Sylvain Corlay | QuantStack | @SylvainCorlay | + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/jupyter-community-calls/668/101?u=ruv7). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* **Matt Fisher** The [GeoJupyter](https://geojupyter.org) open source community recently [announced its launch](https://geojupyter.org/blog/20250108-introducing-geojupyter/) and [started bi-weekly hackathons](https://geojupyter.org/blog/20250129-announcing-geojupyter-hackathons/). Hope you can join us to enable more people to confidently engage with geospatial data in JupyterLab! GeoJupyter is **NOT** an official Project Jupyter subproject. +* **Mike Krassowski** JupyterLab 4.4 beta will be released today :crossed_fingers: +* **Chris Holdgraf** the Turing Way just upgraded their book to Jupyter Book 2! https://book.the-turing-way.org/ +* **Chris Holdgraf** we figured out a way to run mybinder.org nodes much cheaper! https://2i2c.org/blog/2025/binder-singlenode/ +* **Ana Ruvalcaba** Public meetings are announced on Jupyter Community Calendar: https://jupyter.org/community#calendar + + +## Agenda Items + +Add agenda items here **before** the meeting. We will reorganize the agenda so that it fits in the 60m meeting slot. + +* **Ana Ruvalcaba** Jupyter Governance Check In: Executive Council update + * Project Jupyter governance overview https://jupyter.org/governance/overview.html + * Executive Council introductions, we've recently conducted elections, Rick Wagner, Afshin Darian and Chris Holdgraf were elected. Thanks you to Brian Granger (Jupyter cofounder)who will remain on the Jupyter Foundation governing board. + * Jupyter Foundation governing board activities https://github.com/jupyter-governance/jupyter-foundation-governing-board/issues + * Jupyter Foundation website https://jupyterfoundation.org/ +* **Mehmet Bektas**: [Notebook Intelligence](https://github.com/notebook-intelligence/notebook-intelligence) +* **Kyle Smith**: On building a notebook review tool +* **Arjun Verma**: JupyterCAD - Collaborative CAD in JupyterLab + * Try in browser with JupyterLite: https://jupytercad.github.io/JupyterCAD/ +* **Mike Krassowski** JupyterLab 4.4 demo + + +## Other Links Shared + +Fragment Identification Syntax for Jupyter: https://github.com/jupyter/nbformat/issues/317 \ No newline at end of file diff --git a/docs/source/community/community-call-notes/index.rst b/docs/source/community/community-call-notes/index.rst new file mode 100644 index 000000000..742a6b505 --- /dev/null +++ b/docs/source/community/community-call-notes/index.rst @@ -0,0 +1,46 @@ +.. _community-call-notes: + +==================== +Community Call Notes +==================== + +The Jupyter Community Call is an open video call. Think of this as a "monthly, virtual JupyterCon". It's a place for *anyone* to announce and share fun things happening in the Jupyter community. Everyone is welcome (even if you're not presenting). We record these videos and post them on YouTube. For more information, `read this discourse thread `__. + +.. toctree:: + :maxdepth: 1 + + February 2025 <2025-february.md> + November 2024 <2024-november.md> + December 2023 <2023-december.md> + February 2023 <2023-february.md> + January 2023 <2023-january.md> + November 2022 <2022-november.md> + October 2022 <2022-october.md> + September 2022 <2022-september.md> + August 2022 <2022-august.md> + July 2022 <2022-july.md> + June 2022 <2022-june.md> + May 2022 <2022-may.md> + April 2022 <2022-april.md> + March 2022 <2022-march.md> + February 2022 <2022-february.md> + January 2022 <2022-january.md> + November 2021 <2021-november.md> + October 2021 <2021-october.md> + September 2021 <2021-september.md> + August 2021 <2021-august.md> + July 2021 <2021-july.md> + June 2021 <2021-june.md> + May 2021 <2021-may.md> + April 2021 <2021-april.md> + March 2021 <2021-march.md> + February 2021 <2021-february.md> + January 2021 <2021-january.md> + December 2020 <2020-december.md> + November 2020 <2020-november.md> + September 2019 <2019-september.md> + August 2019 <2019-august.md> + June 2019 <2019-june.md> + May 2019 <2019-may.md> + April 2019 <2019-april.md> + March 2019 <2019-march.md> diff --git a/docs/source/community/content-community.rst b/docs/source/community/content-community.rst index ad36634c9..ea79e8ecf 100644 --- a/docs/source/community/content-community.rst +++ b/docs/source/community/content-community.rst @@ -1,6 +1,8 @@ -================ -Community Guides -================ +.. _community-guide: + +========= +Community +========= Welcome to the Community Guides for Jupyter. These guides are intended to @@ -8,51 +10,155 @@ provide information about the Jupyter community such as background, events, and communication channels. As our community is highly dynamic, information may change, and we will do our best to keep it up to date. -Weekly Dev meeting ------------------- +.. toctree:: + :hidden: + + community-call-notes/index + host-guide + + +Jupyter Community Meetings +========================== + +The Jupyter community often meets (usually on-line) in order to discuss matters in +the Jupyter community, share new ideas and discussions, and connect with one another. +This often happens within specific sub-project (more information below), though +there are also occasional community-wide meetings. + +Some of these meetings are recorded and uploaded to our `YouTube channel `_. +**Please do not record meetings on your own.** Some of our meetings include both +on-the-record and off-the-record segments; off-record segments are not recorded or +published. + +This following calendar shows the various meetings and events from Jupyter sub-projects: + +.. raw:: html + + -The core developers have weekly meetings to discuss and demo what they have -been working on, discuss future plans, and bootstrap conversation. These -meetings are public. The direct link to attend the meeting will be posted to -the `Hackpad `_ before the meeting. Afterwards, -the recording of the meeting will be posted to the `IPython channel -`_ on YouTube. -**Jupyter/IPython meetings:** +Jupyter-wide meetings +--------------------- -- Tuesdays at 9am PST +**All-Jupyter Community Calls** generally happen on the last Tuesday of the month, +and are focused around demonstrations and sharing information across all of the Jupyter projects. -**JupyterLab meetings:** +- Find information on `this Discourse thread `_. +- Watch previous calls on `our YouTube channel `_. +- Read the `notes from previous calls `_. -- Fridays at 9am PST +Jupyter Project meetings +------------------------ -Collaborative notes are taken before/during the meeting on -`Hackpad `_. Hackpads are organized by month. +The core developers of various Jupyter sub-projects have regular meetings to +discuss and demo what they have been working on, discuss future plans, +and bootstrap conversation. These meetings are public and you are welcome to join remotely. -We will ping the `dev-meeting-attendance Gitter channel `_ -1-2 days before each meeting to know who is likely going to attend. +Each team has their own processes around logistics and planning for the team meetings. The +following pages should help you find the information for each. + + +**JupyterHub meetings** happen monthly. For a calendar of future team meetings, see +`the JupyterHub team compass repository `_. + +**JupyterLab meetings** happen weekly. For more information about when these meetings happen, +as well as notes from each meeting, see `the JupyterLab README `_. + +**General meeting conversation and planning** often happens in the +`dev-meeting-attendance Gitter channel `_. +We recommend checking it periodically for new information about when meetings are happening. .. contents:: Contents :local: + Jupyter communications ----------------------- +====================== +As a general rule, most project-wide conversation happens in the +`Jupyter community forum `_. There are also many other +kinds of communication that happens within the community. See below for links and other +relevant information. + +- Community forum ``_ - Blog ``_ - Newsletter ``_ - Website ``_ -- Twitter ``_ +- Gitter ``_ +- Zulip `< https://jupyter.zulipchat.com>`_ - Mailing lists (Jupyter, Jupyter in Education) ``_ + Governance ----------- +========== - Steering council: Information about the steering council and its members - can be found on the `Jupyter website `_. + can be found on the `Jupyter website `_. +- Information about Jupyter's governance process can be found on + `the Jupyter governance website `_. - Jupyter Enhancement Proposal (JEP) process: Details about the process can - be found in the `jupyter/enhancement-proposals GitHub repo `_. + be found in the `enhancement proposals website `_. -Code of conduct ---------------- -Information can be found in the `Jupyter Governance repo on GitHub `_. +Code of conduct +=============== + +Information can be found in the +`Jupyter Code of Conduct page `_. + + +Running Jupyter Events +====================== + +Members of the Jupyter community often get together to share what they're +working on, to work together, and to teach and learn from one another. + +If you're organizing an event with the Jupyter community (whether it's as +small as a JupyterDays meetup, or as large as JupyterCon) you should ensure +that the event follows the values and goals of the Jupyter project - to be a +place where *everyone* feels welcome and supported and that reflects the +diversity of developers and users in the Jupyter community. + +Shoot for having **25% of your participants come from under-represented +groups**. If you're organizing a Jupyter event, +here are some resources to help out. + +* **Mozilla** has a number of excellent resources on hosting open events. + The `Mozilla Open Events guide `_. + This is an excellent resource for planning and running an open, inclusive + event. In particular, `this section on making events more inviting `_ + is a good way to make your event more welcoming, interesting, and accessible + to the Jupyter community. Finally, the `Diversity and Inclusion wiki includes + conference calls related to this topic `_. +* The `NumFocus DISCOVER cookbook `_ + is another collection of resources for making your event more productive, + diverse, and inclusive. +* The `National Center for Women & Information Technology `_ has an excellent + collection of resources for creating a diverse and inclusive environment. In + particular, we recommend their `Inclusive Environment Assessment Guide `_ + and `10 actionable ways to actually increase diversity `_. +* The `PyCascades `_ community has `several efforts in improving diversity and inclusion `_. +* `Write the Docs `_ has a `Welcome Wagon Guide `_ + to help first-time attendees feel welcome and included. + +Ultimately, making events more inclusive is not rocket science and there is +no magic bullet. It requires clear, focused dedication, planning ahead, +and sustained resources and effort over time. However, we believe this effort +is worth it! + + +What is a Jovyan? +================= + +You may see the word **Jovyan** used in Jupyter tools (such as the user ID in the +`Jupyter Docker stacks `_ or referenced in +conversations. But what is a Jovyan? + +In astronomical terms, the word "Jovian" means "like Jupiter". It describes +`several planets that share Jupiter-like properties `_. + +Much like the planet Jupiter and our solar system, the Jupyter community +is large, distributed, and nebulous. We like to use the word **Jovyan** to +describe members of this community. Jovyans are fellow open enthusiasts that use, develop, +promote, teach, learn, and otherwise enjoy tools in Jupyter's orbit. They make up the +Jupyter community. If you're not sure whether you're a Jovyan, you probably are :-) diff --git a/docs/source/community/host-guide.md b/docs/source/community/host-guide.md new file mode 100644 index 000000000..10f748075 --- /dev/null +++ b/docs/source/community/host-guide.md @@ -0,0 +1,162 @@ +# **Host Guide** + +Welcome to the Host Guide, a place for call hosts to get help, info, advice and best practices for conducting engaging and effective meetings. + +Check the [Suggested Meeting Script section](#meeting-script-and-checklist) if you want more info for running a great meeting, and peruse the other sections for basic info and additional context. This documentation can be used as a template, the host can duplicate the guide and update the links to reflect their individual meeting or simply use it as a reference point in planning. + +## ⏰ Basic Meeting Event Info + +You can check the [Jupyter Community Meetings calendar](https://jupyter.org/community#calendar) for the exact time of each meeting in your time zone. + +Each meeting should have a collaborative public agenda document (for example on HackMD). The agenda link should be included in the event’s description in the shared Google Calendar. + +## 🎯 Meeting Purpose/Goals + +Meetings are a way to connect members of our community. All participants should feel welcome and be heard. In line with that: + +Meetings should be… + +* Positive and friendly +* Welcoming and open to people from diverse backgrounds +* Newcomers in particular should be welcomed and encouraged to chime in, discuss, participate, or to simply observe if that is their preference. + +## 💬 Topics + +Each meeting should have a list of topics that are generally discussed. Contributors can propose topics before or during the meeting. + +(If using this document as a template, replace this section with a list of topics that are discussed at your meeting.) + +## **Before the Meeting** + +* Select date (at least 4 weeks in advance) and time + * In the past we’ve taken over JupyterLab weekly time slot. This encourages participation from subproject that is accustomed to meeting during a particular time. See example [email](sample_scripts.md#meeting-time-slot-request). +* Create HackMD + * Create HackMD account + * Start a new note + * Use template [here](sample_scripts.md#hackmd-note-template) + * Set permissions (Edit mode, Read: Everyone, Write: Signed in Users\] + * Generate a link to use in announcements +* Announce date on public Jupyter channels + * Blog: [https://blog.jupyter.org/november-2024-jupyter-community-call-f5d0761c67a1](https://blog.jupyter.org/november-2024-jupyter-community-call-f5d0761c67a1) + * [Sample blog post](sample_scripts.md#blog-post) + * Get permissions + * Create an account on Medium + * Ask Jupyter Media Strategy (JMS) working group for permissions to be a writer on the [Jupyter blog](https://blog.jupyter.org/) by sending them an email: [jupyter-media-strategy@googlegroups.com](mailto:jupyter-media-strategy@googlegroups.com) + * Write blog post \+ social media posts + * Use draft as a template ([samples for blog and social media posts](sample_scripts.md#sample-scripts)) + * Submit for JMS review + * See instructions here: [https://jupyter.org/social](https://jupyter.org/social) + * Email [jupyter-media-strategy@googlegroups.com](mailto:jupyter-media-strategy@googlegroups.com) requesting their review on the blog post and requesting they post on all social media channels + * Discourse: [https://discourse.jupyter.org/c/meta/community-building/49](https://discourse.jupyter.org/c/meta/community-building/49) + * Write post and post directly + * Zulip: [https://jupyter.zulipchat.com/](https://jupyter.zulipchat.com/) + * Write post and post directly + * Open an issue on Governance repo: [https://github.com/jupyter/governance/issues/241](https://github.com/jupyter/governance/issues/241) + * Write post and post directly + * Send email to EC and SSC + * Invite them to speak + * Contact info EC: [https://executive-council-team-compass.readthedocs.io/en/latest/](https://executive-council-team-compass.readthedocs.io/en/latest/) + * Contact info SSC (scroll to bottom): [https://jupyter.org/governance/software\_steering\_council.html](https://jupyter.org/governance/software_steering_council.html) + * Join subproject meetings to promote call + +## 💪 Host Responsibilities + +The host should facilitate the flow of a meeting. That means: + +* Soliciting topics for the agenda: + * *Share the agenda document in the chat multiple times. On Zoom, for example, new participants do not see previous chat messages.* +* Curate agenda topics + * Is the proposed speaker’s topic appropriate for this call? + * Is there enough time for all speakers? + * Any other measure that host deems is important as a public reflection of Project Jupyter +* Going through the agenda: + * *Do time checks/pause \+ move on to hit all items when there are time concerns* +* Guiding discussion: + * *Read chats aloud for participants \+ the recording* +* Maintaining order / Making sure everyone has a chance to speak: + * *Interject when someone has their hand raised* +* Mention/link to the [Jupyter Code of Conduct](https://jupyter.org/conduct) and how everyone is bound to it (including the host) + +Partner with another contributor (who has recording privileges) to do the following: + +* Record the meeting. The contributor you’re partnering with can start and stop the recording following your verbal cue. These are posted to YouTube. +* Remove unwelcome recording bots: + * Per the Jupyter community page, participants should not record meetings on their own. The host should ask participants that look like AI recording bots: + * To identify themselves and state whether they’re recording + * If they get no response from the account, the host should assume it’s recording, and remove it from the meeting. + +## ✏ Meeting Checklist and Script + +### ⏳ Prior to meeting start + +* Make sure you have a solid tech environment that will allow you to focus on your hosting duties. This includes a stable internet connection, a good quality microphone, and a quiet environment. Ideally, the ability to share your camera may support your ability to connect with the participants in the call. +* Share the agenda in the Zoom chat the \[meeting agenda\](insert agenda) + * *The agenda is a collaboratively created document made by the participants.Ensure a section for today’s meeting is created, with today’s date and a table for participants to record their names (which can be copied/pasted from lower entries). The agenda will also be used as meeting minutes.* + +### 🔗 *Links to copy/paste into the meeting chat:* + +* Weekly Meeting Notes: \[Insert HackMD here\] +* Jupyter Code of Conduct: [https://jupyter.org/governance/conduct/code\_of\_conduct.html](https://jupyter.org/governance/conduct/code_of_conduct.html) + +### 🎙 Start the Meeting! + +Create a script from these talking points *or* use the script below if you want\! + +* Inform people when you’re about to start recording +* Introduce yourself +* Describe what the call is +* Welcome all newcomers +* Point people to the code of conduct: [jupyter.org/conduct](http://jupyter.org/conduct) (send link to chat) +* Encourage attendees to add discussion points to the agenda + +Sample script + +Before we start the recording, does anyone have anything they’d like to say off the record? (Remember to say “We will now begin recording/The recording has ended” before starting/stopping recording :) + + > Hello and welcome to our \[full date\] Jupyter Community call. I’m \[host name\] and I’ll be your host today. This is a place for all contributors to connect with each other and the community about any exciting work happening in the Jupyter Community. A special highlight and welcome to all first time participants\! We want all newcomers to feel welcome, we invite you to join in on discussions, introduce yourself, or add items to the agenda. + +> Please keep in mind that this call will be recorded and posted to YouTube for the community to view. This call is a part of the Jupyter community; we follow the Jupyter Code of Conduct, which you can read about at jupyter.org/conduct\[Meeting host insert link in the meeting minutes template\] + +> If you have a topic you’d like to discuss, please add it to the agenda. (Share agenda link in the chat) + +### 🎺 Closing message + +Create a script from these talking points *or* use the script below if you want\! + +* Thank attendees for joining +* Ask for feedback on running the call to be posted to [Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668/101) +* Announce date of next call and send link to Hackmd to submit topics +* The community is welcome to join public meetings\! Send link to meeting chat: [Jupyter community calendar](https://jupyter.org/community#calendar) +* Encourage people to reach out if they want to host +* After ending the recording, ask if anyone wants to say anything off the record + +Sample Script + +> Thank you to everyone for joining\! I’m happy to have you all as a part of the Jupyter community. If you have any feedback, please direct it to [Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668/103). We’d love to hear what you think about the call or how to improve future meetings. Our next call will be \[day, month\]. Check out the [Jupyter community calendar](https://jupyter.org/community#calendar) to see what other types of meetings are happening in between. + +The following message is recommended for Community Calls or similar events that engage with the broader contributor community: + +> If you have any interest in sharing in future \[title\] calls, please do\! It doesn’t have to be a big share, a polished share, or a technical share, just show off what you do with Jupyter that excites you. Submit topics here \[platform/link\]. If you’re interested in hosting a community call, feel free to reach out. It would be great to get different people interacting with the community. + +After the recording ends: + +> If you have anything you would like to add off the record, please feel free to discuss that now. + +### 🎉 After the Meeting + +*Congratulations 🚀 on a finished meeting. Pat yourself on the back. Contributions like yours help to make the Jupyter community better\!* + +A few post-meeting items for either the host or meeting-facilitator to complete: + +* Finalize meeting minutes: Go back to the notes and make any needed additions, corrections and formatting needed in order to make the notes easy to understand by someone who did not participate in the meeting. +* Publish the minutes: + 1. Copy the contents of the minutes into a markdown file in this folder: [https://github.com/jupyter/jupyter/tree/master/docs/source/community/community-call-notes](https://github.com/jupyter/jupyter/tree/master/docs/source/community/community-call-notes). + 2. **You’ll also have to add a table of contents entry [here](https://github.com/jupyter/jupyter/blob/master/docs/source/community/community-call-notes/index.rst) once you add the actual file.** +* ***Upload video to YouTube***: You can share the link to the recording along with the thumbnail image for the video, with someone who has access to upload to the Project Jupyter YouTube channel. The thumbnail can be created from the slide here: [Video title slide](https://docs.google.com/presentation/d/1E32UwXA81kqZG2Ruo8vBFYFSNPBLjh3PUYVHYiRhCBQ/edit?usp=drive_link) +* Post recording on the following [thread on Discourse](%20https://discourse.jupyter.org/t/jupyter-community-calls/668/102?u=ruv7) (this link lives in the HackMD and should be kept up to date). + +🌅 The Jupyter community depends on volunteers like you, so again we would like to thank you for helping Jupyter bring open source tools for interactive computing to the world. + +## Current System for Zoom Host Priviledges + +To get the recording afterwards, you will need to have a person with host privileges request the recording from Linux Foundation. diff --git a/docs/source/community/sample_scripts.md b/docs/source/community/sample_scripts.md new file mode 100644 index 000000000..7fe72e2a1 --- /dev/null +++ b/docs/source/community/sample_scripts.md @@ -0,0 +1,153 @@ +# Sample Scripts +The following are example scripts for each of the communication tasks in the community call host guide. +You can use and teak to fit your needs. + +## Social Media Posts +### Short Version +You’re invited to join the next Jupyter Community Call on [DATE]! Get updates from across the Jupyter ecosystem, hear talks from community members, and learn how you can get involved. It’s a great way to connect, contribute, and stay in the loop. Learn more on our blog [HYPERLINK_TO_BLOG_POST] + +### Long Version + Join the Jupyter Community Call – [DATE] +Whether you're a contributor, educator, researcher, or curious newcomer you're invited to our next Jupyter Community Call. + Date: [DATE] + Time: [TIME] Pacific / [TIME] Eastern / [TIME] UTC + Learn more on our blog [HYPERLINK_TO_BLOG_POST] +Get updates from across the Jupyter ecosystem, hear talks from community members, and learn how you can get involved. +It’s a great way to connect, contribute, and stay in the loop! + +## Meeting Time Slot Request +Hey team, + +My name is [NAME] and I am volunteering to lead the Jupyter Community call on [DATE]. In order to encourage attendance, would the team be OK with giving up the weekly subproject meeting on [DATE] in favor of the community call? + +## JMS Email Request +Hi JMS team, + +I have submitted a blog post to promote the upcoming Jupyter Community Call on [DATE]. I would appreciate your review! +The promotional social media posts are here[LINK_SAMPLE_SCRIPTS] + +Thank you! +[NAME] + +## JMS Social Media Promotion Requests +Hi JMS team, + +I’d like to request some additional promotion for the upcoming Jupyter Community Call on [DATE]. If feasible, it would be great to have two posts: one encouraging sign-ups in advance, and another as a reminder during the week of the call. + +Post 1 ([DATE_TO_POST]) +ICYMI: Sign up to speak at the upcoming Jupyter Community Call on [DATE]! We’d love to hear what you’re working on. Check out the blog post[EMBEDDED_BLOG_LINK] for more details. + + +Post 2 ([DATE_TO_POST]) +Join us this [CALL_DAY] for the Jupyter Community Call! We’re excited to hear from the community. See the full details in the blog post[EMBEDDED_BLOG_LINK]. + +Thank you for your help! +[NAME] + + +## EC Email + +Hi Executive Council, + +The DEI Committee is hosting a Jupyter Community call on [DATE] at [TIME] PST ([TIME] UTC) and we would like to invite members of the EC to attend! You're welcome to present updates to the community as well (agenda/sign-ups). + +If you would like to help promote the community call on social media, that would be greatly appreciated. Here’s a sample post you’re welcome to use: + +Join us for the upcoming Jupyter Community Call on [DATE]! Get updates from across the Jupyter ecosystem, hear talks from community members, and learn how you can get involved. It’s a great way to connect, contribute, and stay in the loop. Learn more on our blog[EMBEDDED_BLOG_LINK]. + +Thank you, +[NAME] + + +## SSC Email +Hi Software Steering Council, + +The DEI Committee is hosting a Jupyter Community call on [DATE] at [TIME] PST ([TIME] UTC) and we would like to invite members of the SSC to attend! You're welcome to present updates to the community as well (agenda/sign-ups). + +If you would like to help promote the community call to your subprojects and on social media, that would be greatly appreciated. Here’s a sample post you’re welcome to use: + +Join us for the upcoming Jupyter Community Call on [DATE]! Get updates from across the Jupyter ecosystem, hear talks from community members, and learn how you can get involved. It’s a great way to connect, contribute, and stay in the loop. Learn more on our blog. + +Thank you, +[NAME] + + +## Blog Post +Hey Jovyans, we want to learn about the great things you’re doing with Jupyter! The Diversity, Equity, and Inclusion (DEI) standing committee is holding an open call with the community for people to discuss and share their work. Think of it as a “virtual JupyterCon”: It’s a place to announce and share new things happening in the Jupyter ecosystem. +We encourage brief (5 minutes or less) presentations with a demo or screen share, as needed. If you have a GitHub repo or demo web site, please remember to share it. +Anyone can attend, for free! Anyone can present; add yourself to the HackMD agenda. Anyone can sit in on the call. Presenters will lead a demo and may leave time to answer questions. Topics should be targeted to broad and global audience. Keep things simple and remember not every listener will be a software engineer. +Event details: +[DATE], at [TIME] AM PST ([TIME] UTC [AREWEMEETINGYET.COM_LINK]) +Agenda (add yourself!) on HackMD +Meeting channel: (LINK) +Meeting ID: [ID] / Meeting Passcode: [PASSCODE] +Or connect via phone: +US: [PHONE_NUMBERS] +International numbers: [LINK] +Watch previous calls in our [YouTube playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP). + + +## HackMD Template + +### Instructions +Copy template below and paste into HackMD note. +Test all links +Update the arewemeetingyet.com link with proper date. +If needed, update the Discourse link to a more recent post. + +### HackMD Note Template + +--- +tags: jupyter +--- +# Jupyter Community Call + +**Date:** [MONTH DAY, YEAR], at [TIME] PST / [TIME] UTC; your timezone ([YOUR TIMEZONE](https://arewemeetingyet.com/Los%20Angeles/2025-01-01/09:00/Call%20Community%20Call)) + +**Video-conference link:** [Zoom link](https://zoom.us/j/95228013874?pwd=Ep7HIk8t9JP6VToxt1Wj4P7K5PshC0.1) + +**Feedback or questions?** You can either post publicly on the following thread on +[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668/103) or email the DEI Committee - jupyter-dei@googlegroups.com + +**Please note:** +- Community calls are recorded and posted to this [playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP) +- These notes will be recorded and posted [here](https://jupyter.readthedocs.io/en/latest/community/community-call-notes/index.html) +- Everyone present is held to the [Jupyter Code of Conduct](https://jupyter.org/conduct) + +**Welcome!** + +If you are joining the Jupyter Community Call, we ask that you sign in below at the start of the call so that we know who was here. + +| Name | Institution | GitHub Handle | +| ---- | ----------- | ------------- | +| | | | +| | | | +| | | | +| | | | +| | | | + + +## Purpose + +Think of it as a monthly, virtual JupyterCon. It’s a place to announce and share fun things happening in the Jupyter community. + +For more discussion on the format of these calls, see the thread [here](https://discourse.jupyter.org/t/jupyter-community-calls/668/103). + +## Short reports, celebrations, shout-outs + +This is a place to make short announcements (without a need for discussion). + +* + + +## Agenda Items + +Add agenda items here **before** the meeting. The event host will reorganize the agenda so that it fits in the 60m meeting slot. + +* + + + +## Other Links Shared +* + diff --git a/docs/source/conf.py b/docs/source/conf.py index 7009ad747..df718d167 100755 --- a/docs/source/conf.py +++ b/docs/source/conf.py @@ -9,10 +9,6 @@ import sys import os import shlex -import recommonmark.parser - -from jupyter_sphinx_theme import * -init_theme() # If extensions (or modules to document with autodoc) are in another directory, # add these directories to sys.path here. If the directory is relative to the @@ -21,8 +17,9 @@ # -- General configuration ------------------------------------------------ -# If your documentation needs a minimal Sphinx version, state it here. -#needs_sphinx = '1.0' +html_theme = 'pydata_sphinx_theme' +html_logo = '_static/_images/jupyter.svg' +html_favicon = '_static/_images/favicon.png' # Add any Sphinx extension module names here, as strings. They can be # extensions coming with Sphinx (named 'sphinx.ext.*') or your custom @@ -32,15 +29,16 @@ 'sphinx.ext.doctest', 'sphinx.ext.intersphinx', 'sphinx.ext.graphviz', # Add the graphviz extension + 'sphinxext.rediraffe', + 'myst_parser', + 'sphinx_design', ] +panels_add_bootstrap_css = False + # Add any paths that contain templates here, relative to this directory. templates_path = ['_templates'] -source_parsers = { - '.md': 'recommonmark.parser.CommonMarkParser', -} - # The suffix(es) of source filenames. # You can specify multiple suffix as a list of string: source_suffix = ['.rst', '.md'] @@ -49,7 +47,7 @@ #source_encoding = 'utf-8-sig' # The master toctree document. -master_doc = 'contents' +master_doc = 'index' # General information about the project. project = 'Jupyter Documentation' @@ -89,6 +87,39 @@ # so a file named "default.css" will overwrite the builtin "default.css". html_static_path = ['_static'] +html_context = { + # "github_url": "https://github.com", # or your GitHub Enterprise interprise + "github_user": "jupyter", + "github_repo": "jupyter", + "github_version": "master", + "doc_path": "docs/source", +} + +html_theme_options = { + "icon_links": [ + { + "name": "GitHub", + "url": "https://github.com/jupyter/jupyter", + "icon": "fab fa-github-square", + }, + { + "name": "Discourse", + "url": "https://discourse.jupyter.org", + "icon": "fab fa-discourse", + }, + ], + "external_links": [ + {"name": "jupyter.org", "url": "https://jupyter.org"}, + ], + "use_edit_page_button": True, +} + +# Re-directs for pages that were moved +rediraffe_redirects = { + "content-quickstart.rst": "start/index.md", + "tryjupyter.rst": "start/index.md", +} + # If not '', a 'Last updated on:' timestamp is inserted at every page bottom, # using the given strftime format. html_last_updated_fmt = '%Y-%m-%d' @@ -98,7 +129,7 @@ # Additional templates that should be rendered to pages, maps page names to # template names. -html_additional_pages = {'index': 'index.html'} +html_additional_pages = {} # Output file base name for HTML help builder. htmlhelp_basename = 'Jupyter' @@ -151,6 +182,11 @@ 'jupyterclient': ('https://jupyter-client.readthedocs.io/en/latest/', None), 'qtconsole': ('https://jupyter.org/qtconsole/dev/', None), 'jupytercore': ('https://jupyter-core.readthedocs.io/en/latest/', None), + 'hub': ('https://jupyterhub.readthedocs.io/en/latest/', None), + 'z2jh': ('https://zero-to-jupyterhub.readthedocs.io/en/latest/', None), + 'tljh': ('https://tljh.jupyter.org/en/latest/', None), + 'bhub': ('https://binderhub.readthedocs.io/en/latest/', None), + 'lab': ('https://jupyterlab.readthedocs.io/en/latest/', None), } intersphinx_cache_limit = 5 @@ -167,6 +203,15 @@ # if calling sphinx-build directly - if using the make.bat file first do: # set SPHINXOPTS=-D graphviz_dot="C:\Program Files (x86)\Graphviz2.38\bin\dot.exe" # or similar, if all else fails, something like: -# graphviz_dot=r'c:\Program Files (x86)\Graphviz2.38\bin\dot.exe' +# graphviz_dot=r'c:\Program Files (x86)\Graphviz2.38\bin\dot.exe' # with your path to graphviz in should work if added to this file. # BUT Please do not commit with the path on your computer in place. + +# -- Translation ---------------------------------------------------------- + +gettext_uuid = True +locale_dirs = ['locale/'] + + +def setup(app): + app.add_css_file("custom.css") diff --git a/docs/source/content-quickstart.rst b/docs/source/content-quickstart.rst deleted file mode 100644 index 2ab9f5bca..000000000 --- a/docs/source/content-quickstart.rst +++ /dev/null @@ -1,11 +0,0 @@ -Jupyter Notebook Quickstart -=========================== - -.. toctree:: - :maxdepth: 1 - - tryjupyter.rst - install.rst - install-kernel.rst - running.rst - migrating.rst diff --git a/docs/source/contents.rst b/docs/source/contents.rst deleted file mode 100644 index e8633c398..000000000 --- a/docs/source/contents.rst +++ /dev/null @@ -1,86 +0,0 @@ -=========================== -Project Jupyter and IPython -=========================== - -**Table of Contents** - -.. _user-docs: - -.. toctree:: - :maxdepth: 2 - - content-quickstart - -.. _tech-overview: - -.. toctree:: - :maxdepth: 1 - - architecture/content-architecture.rst - -.. _about-docs: - -.. toctree:: - :maxdepth: 2 - - use-cases/content-user.rst - -.. _about-ipython: - -.. toctree:: - :maxdepth: 2 - - ipython/content-ipython.rst - -.. _jupyter-subprojects: - -.. toctree:: - :maxdepth: 2 - - projects/content-projects - -.. toctree:: - :maxdepth: 2 - - community/content-community - -.. _dev-docs: - -.. toctree:: - :maxdepth: 2 - - contributor/content-contributor - -.. toctree:: - :maxdepth: 2 - - releases/content-releases - -.. toctree:: - :maxdepth: 2 - - reference/content-reference - - - -Indices and tables -================== - -- :ref:`genindex` -- :ref:`glossary` -- :ref:`search` - - -**Resources:** - -.. csv-table:: - :header: "Site", "Description" - :widths: 18, 35 - - `Jupyter website `_, Keep up to date on Jupyter - `IPython website `_, Learn more about IPython - `jupyter/help repo `_, Start here for help and support questions - `Jupyter mailing list `_, General discussion of Jupyter's use - `Jupyter in Education group `_, Discussion of Jupyter's use in education - `NumFocus `_, "Promotes world-class, innovative, open source scientific software" - `Donate to Project Jupyter `_, Please contribute to open science collaboration and sustainability diff --git a/docs/source/contrib_docs/doc-bugs.rst b/docs/source/contrib_docs/doc-bugs.rst deleted file mode 100644 index d6f7b2842..000000000 --- a/docs/source/contrib_docs/doc-bugs.rst +++ /dev/null @@ -1,2 +0,0 @@ -Correcting bugs -=============== diff --git a/docs/source/contrib_docs/doc-build.rst b/docs/source/contrib_docs/doc-build.rst deleted file mode 100644 index 5894be0c3..000000000 --- a/docs/source/contrib_docs/doc-build.rst +++ /dev/null @@ -1,2 +0,0 @@ -Building the docs -================= \ No newline at end of file diff --git a/docs/source/contrib_docs/doc-style.rst b/docs/source/contrib_docs/doc-style.rst deleted file mode 100644 index bd2e5869a..000000000 --- a/docs/source/contrib_docs/doc-style.rst +++ /dev/null @@ -1,2 +0,0 @@ -Style guidelines -================ \ No newline at end of file diff --git a/docs/source/contrib_docs/doc-tracking.rst b/docs/source/contrib_docs/doc-tracking.rst deleted file mode 100644 index 9abd1ea5e..000000000 --- a/docs/source/contrib_docs/doc-tracking.rst +++ /dev/null @@ -1,7 +0,0 @@ -Tracking and metrics -==================== - -We have created a site to monitor the build status of our documentation. See -http://doc_helper.iheartjupyterdocs.org. - -.. image:: static/doc_helper.png \ No newline at end of file diff --git a/docs/source/contributor/contrib_guide_blog.rst b/docs/source/contributing/communication-contributions.rst similarity index 96% rename from docs/source/contributor/contrib_guide_blog.rst rename to docs/source/contributing/communication-contributions.rst index 84800acec..4104187cc 100644 --- a/docs/source/contributor/contrib_guide_blog.rst +++ b/docs/source/contributing/communication-contributions.rst @@ -44,7 +44,7 @@ Creating a draft Title and metadata ~~~~~~~~~~~~~~~~~~ -Alway check in the metadata fields that a blog post has a title and a canonical +Always check in the metadata fields that a blog post has a title and a canonical URL. It is possible to put the date in the canonical URL, in particular for events like jupyter-day, that can occur several times. The date of the event can differ from the date of the blog post. @@ -64,7 +64,7 @@ Working with images Try not to link to external images. If you want to put an image in the post, insert ``![]()`` in the editor view and drag and drop an image from your -desktop into the newly created field in in the preview. External images can +desktop into the newly created field in the preview. External images can change, and can break the blog post if they are taken down. This cannot append if you drag and drop images. Moreover, these images will be served from the same CDN (Content Delivery Network) as the blog, which will insure the best @@ -122,7 +122,7 @@ depending on importance) with the Date/Time of the update. If the information in the body of the blog is wrong, try not to replace it, and just use strike-through to mark it as obsolete. This would help reader determine which information is correct when dealing with multiple source giving different -informations. +information. Newsletter ========== @@ -134,4 +134,3 @@ Website ======= Documentation in progress. - diff --git a/docs/source/contributing/content-contributor.rst b/docs/source/contributing/content-contributor.rst new file mode 100644 index 000000000..472484028 --- /dev/null +++ b/docs/source/contributing/content-contributor.rst @@ -0,0 +1,88 @@ +Contributing +============ + +.. toctree:: + :maxdepth: 1 + + + start-contributing + dev-contributions/index + docs-contributions/index + communication-contributions + ipython-dev-guide/index + +Whether you are a new, returning, or current contributor to Project +Jupyter's subprojects or IPython, **we welcome you**. + +Project Jupyter has seen steady growth over the past several years, and it is +wonderful to see the many ways people are using these projects. As a result of +this rapid expansion, our project maintainers are balancing many requirements, +needs, and resources. We ask contributors to take some time to become familiar +with our contribution guides and spend some time learning about our project +communication and workflow. + +The Contributor Guides and individual project documentation offer +guidance. If you have a question, please ask us. `Community Resources +`_ provides information on our commonly +used communication methods. + +We are very pleased to have you as a contributor, and we hope you +will find valuable your impact on the projects. **Thank you** for +sharing your interests, ideas, and skills with us. + +Do I really have something to contribute to Jupyter? +---------------------------------------------------- + +Absolutely ✅. There are always ways to contribute to this community! Whether it +is is contributing code, improving documentation and communications, teaching others, +or participating in conversations in the community, we welcome and value your contribution! + + +What kinds of contributions can I make? +--------------------------------------- + +The following sections try to provide inspirations for different ways that you can +contribute to the Jupyter ecosystem. They're non-complete - if you can think up any way to +make an improvement, we appreciate it! + +Improving documentation +``````````````````````` + +One of the most important parts of the Jupyter ecosystem is its documentation. Good +documentation makes it easier for users to learn how to use the tools. It also makes +it easier to teach others, and to maintain and improve the code itself. There are many +ways to improve documentation, such as **reading tutorials and reporting confusing parts**, +**finding type-os and minor errors in docs**, **writing your own guides and tutorials**, +**improving docstrings within the code**, and **improving documentation style and design**. + +If you'd like to improve documentation in the Jupyter community, check out the :ref:`documentation-guide`. + +Improving code +`````````````` + +There are many different codebases that make up the tools in the Jupyter ecosystem. These are +split across many repositories in several GitHub organizations. They cover many +different parts of interactive computing, such as **user interfaces**, **kernels**, +**shared infrastructure**, **interactive widgets**, or **structured documents**. + +We recommend checking out the :ref:`developer-guide` for more information about how +you can find the right project to contribute to, and where to go next. + +Participating in the community +`````````````````````````````` + +The most important part of Jupyter is its community - this is a large and diverse group of +people spread across the globe. One of the best ways to contribute to Jupyter is to simply +be a positive and helpful member of this community. Whether it **participating in online conversations**, +**offering to help others**, **coming to community meetings**, or **teaching others about Jupyter**, +there are many ways to improve the Jupyter community. For more information about this, we +recommend starting with the :ref:`community-guide`. + +Getting Access to Jupyter Managed Accounts +------------------------------------------ + +As a contributor, you may need to access accounts managed by Jupyter, for instance, +to write a blog post or update information posted to a Jupyter site. + +To request access, email the security group at `security@ipython.org`, or make +an issue on the `Jupyter Security subproject repo `_. diff --git a/docs/source/contributing/dev-contributions/contrib_guide.md b/docs/source/contributing/dev-contributions/contrib_guide.md new file mode 100644 index 000000000..0fb8a58af --- /dev/null +++ b/docs/source/contributing/dev-contributions/contrib_guide.md @@ -0,0 +1,226 @@ +# How can I help? + +```{contents} Contents +:local: +``` + +Contributing to open source can be a nerve-wrecking process, but don't worry +everyone on the Jupyter team is dedicated to making sure that your open source +experience is as fun as possible. At any time during the process described +below, you can reach out to the Jupyter team on Gitter or the mailing list for +assistance. If you are nervous about asking questions in public, you can also +reach out to one of the Jupyter developers in private. You can use the public +Gitter to find someone who has the best knowledge about the code you are +working with and interact with them in a personal chat. + +As you begin your open source journey, remember that it's OK if you don't +understand something, it's OK to make mistakes, and it's OK to only contribute +a small amount of the code necessary to fix the issue you are tackling. Any and +all help is welcome and any and all people are encouraged to contribute. + + +## Submitting Pull Requests + +Individuals are welcome, and encouraged, to submit pull requests and contribute +to the Jupyter source. If you are a first-time contributor looking to get +involved with Jupyter, you can use the following query in a GitHub search to +find beginner-friendly issues to tackle across the Jupyter codebase. This query +is particularly useful because the Jupyter codebase is scattered across several +repositories within the jupyter organization, as opposed to a single +repository. You can click the link below to find sprint-friendly issues. + +```{button-link} https://github.com/search?q=is%3Aissue+is%3Aopen+is%3Asprint-friendly+user%3Ajupyter&type=Issues&ref=searchresults +is:issue is:open is:sprint-friendly user:jupyter +``` + +Once you've found an issue that you are eager to solve, you can use the guide +below to get started. If you experience any problems while working on the +issue, leave a comment on the issue page in GitHub and someone on the core team +will be able to lend you assistance. + +Please keep in mind that what follows are guidelines. If you work through the +steps and have questions or run into time constraints, please submit what you +already have worked on as a pull request and ask questions on it. Your effort, +including partial or in-progress work, is appreciated. + +1. Fork the repository associated with the issue you are addressing and clone + it to a local directory on your machine. +2. `cd` into the directory and create a new branch using `git checkout -b insert-branch-name-here`. + + Pick a branch name that gives some insight into + what the issue you are fixing is. For example, if you are updating the text + that is logged out by the program when a certain error happens you might + name your branch `update-error-text`. + +3. Refer to the repository's README and documentation for details on + configuring your system for development. + +4. Identify the module or class where the code change you will make will + reside and leave a comment in the file describing what issue you are trying + to address. + +5. Open a pull request to the repository with `[WIP]` appended to the front + so that the core team is aware that you are actively pursuing the issue. + When creating a pull request, make sure that the title clearly and concisely + describes what your code does. For example, we might use the title "Updated + error message on ExampleException". In the body of the pull request, make + sure that you include the phrase "Closes #issue-number-here", where the + issue number is the issue number of the issue that you are addressing in + this PR. + + Feel free to open a PR as early as possible. Getting early feedback on your + approach will save you time and prevent the need for an extensive refactor + later. + +6. Run the test suite locally in order to ensure that everything is properly + configured on your system. Refer to the repository's README for information + on how to run the test suite. This will typically require that you run the + `nosetests` command on the commandline. Alternatively, you may submit a + pull request. Our Continuous Integration system will test your code and + report test results. + +7. Find the test file associated with the module that you will be changing. + In the test file, add some tests that outline what you expect the behavior + of the change should be. If we continue with our example of updating the + text that is logged on error, we might write test cases that check to see + if the exception raised when you induce the error contains the appropriate + string. When writing test cases, make sure that you test for the following + things. + + * What is the simplest test case I can write for this issue? + * What will happen if your code is given messy inputs? + * What will happen if your code is given no inputs? + * What will happen if your code is given too few inputs? + * What will happen if your code is given too many inputs? + + If you need assistance writing test cases, you can place a comment on the + pull request that was opened earlier and one of the core team members will + be able to help you. + +8. Go back to the file that you are updating and begin adding the code for your + pull request. + +9. Run the test suite again to see if your changes have caused any of the test + cases to pass. If any of the test cases have failed, go back to your code + and make the updates necessary to have them pass. + +10. Once all of your test cases have passed, commit both the test cases and the + updated module and push the updates to the branch on your forked repository. + +11. Once you are ready for your pull request to be reviewed, remove the [WIP] + tag from the front of issue, a project reviewer will review your code for + quality. You can expect the reviewer to check for the documentation + provided in the changes you made, how thorough the test cases you provided + are, and how efficient your code is. Your reviewer will provide feedback on + your code and you will have the chance to edit your code and apply fixes. + +12. Once your PR is ready to become a part of the code base, it will be merged + by a member of the core team. + +## Contribution Workflow + +```{image} ../../_static/_images/contribution_workflow.png +:alt: A flow chart listing the steps of contributing code to Jupyter with 14 labeled boxes linked by arrows. The chart is uni-directional. At each step, arrows point forward to one or more boxes and back to the previous box or boxes. Refer to the link below the image for full text. +``` + +Full Contribution Workflow description.[^f1] + +## Core Developer Workflow + +To help you understand our review process by core developers after you submit a +pull request, here's a guide that outlines the general process (specifics may +vary a bit across our repositories). Here is an example for Jupyter notebook +`4.x`: + +In general, Pull Requests are against `master` unless they only affect a +backport branch. If a PR affects master and should be backported, the general +flow is: + +1. mark the PR with milestone for the next backport release (4.3) +2. merge into master +3. backport to 4.x +4. push updated 4.x branch + +Backports can be done in a variety of ways, but we have [a script](https://github.com/ipython/ipython/blob/master/tools/backport_pr.py) for +automating the common process to: + +1. download the patch ` e.g. ` +2. checkout the 4.x branch +3. apply the patch +4. make a commit + +which works for simple cases, at least. + +In this case, it would be: + +``` +python /path/to/ipython-repo/tools/backport_pr.py jupyter/notebook 4.x 1645 +``` + +## Submitting a Bug + +While using the Notebook, you might experience a bug that manifests itself in +unexpected behavior. If so, we encourage you to open issues on GitHub. To +make the navigating issues easier for both developers and users, we ask that +you take the following steps before submitting an issue. + +1. Search through StackOverflow and existing GitHub issues to ensure that + the issue has not already been reported by another user. If so, provide + your input on the existing issue if you think it would be valuable. + +2. Prepare a small, self-contained snippet of code that will allow others + to reproduce the issue that you are experiencing. + +3. Prepare information about the environment that you are executing the code + in, in order to aid in the debugging of the issue. You will need to provide + information about the Python version, Jupyter version, operating system, + and browser that you are using when submitting bugs. You can also use + `pip list` or `conda list` and `grep` in order to identify the + versions of the libraries that are relevant to the issue that you are + submitting. + +4. Prepare a simple test that outlines the expected behavior of the code + or a description of the what the expected behavior should be. + +5. Prepare an explanation of why the current behavior is not desired and + what it should be. + +## Reporting a Vulnerability + +If you believe you've found a security vulnerability in a Jupyter project, +please report it to [`security@ipython.org`](mailto:security@ipython.org). +If you prefer to encrypt your security reports, you can use [this PGP public key](https://jupyter-notebook.readthedocs.io/en/stable/_downloads/1d303a645f2505a8fd283826fafc9908/ipython_security.asc). + +[^f1]: A flow chart with 14 labeled boxes linked by arrows. + + The chart is uni-directional. At each step, arrows point forward to one or more boxes and back to the previous box or boxes. Here the flow chart is described as lists in which the possible next steps are listed beneath each box label. + + 1. Start + 1a. forward to 'Find an issue to address' + 2. Find an issue to address + 2a. forward to 'Identify the relevant section of the codebase' + 3. Identify the relevant section of the codebase + 3a. forward to 'Write simple test cases to verify that your fix or enhancement works.' + 4. Write simple test cases to verify that your fix or enhancement works. + 4a. forward to 'Implement the bug fix or enhancement in the appropriate location' + 5. Implement the bug fix or enhancement in the appropriate location. + 5a. Forward to 'Run the test suite and verify that the updated code works appropriately.' + 6. Run the test suite and verify that the updated code works appropriately. + 6a. forward to 'Test suit passes!' + 6b. forward to 'Test suit fails!' + 7. Test suit fails + 7a. forward to 'Identify and fix any issues in the new code that might be causing errors. Refer to the mailing list or Gitter channel for help.' + 8. Identify and fix any issues in the new code that might be causing errors. Refer to the mailing list or Gitter channel for help. + 8a. back to 'Run the test suite and verify that the updated code works appropriately' + 9. Test suit passes! + 9a. forward to 'Submit a pull request to the appropriate repository with your awesome code!' + 10. Submit a pull request to the appropriate repository with your awesome code! + 10a. forward to 'Reviewer approves and merges the PR' + 10b. forward to 'Reviewer responds with changes you should make to the PR' + 11. Reviewer responds with changes you should make to the PR + 11a. forward to 'Apply the necessary fixes or updates to the pull request' + 12. Apply the necessary fixes or updates to the pull request' + 12a. back to 'Submit a pull request to the appropriate repository with your awesome code!' + 13. Reviewer approves and merges the PR' + 13a. forward to 'Rejoice and repeat!' + 14. 'Rejoice and repeat!' diff --git a/docs/source/developer-docs/index.rst b/docs/source/contributing/dev-contributions/index.rst similarity index 63% rename from docs/source/developer-docs/index.rst rename to docs/source/contributing/dev-contributions/index.rst index dbf54dee7..f0b7d0bb4 100644 --- a/docs/source/developer-docs/index.rst +++ b/docs/source/contributing/dev-contributions/index.rst @@ -1,3 +1,5 @@ +.. _developer-guide: + =============== Developer Guide =============== @@ -7,19 +9,17 @@ Developer Guide .. toctree:: :maxdepth: 1 - contrib_guide_code.rst - contrib_guide_bugs_enh.rst + contrib_guide.rst jupyter_enhancement_proposals.rst releasing.rst - ../development_guide/index.rst Whether you are a new contributor or a seasoned developer, we're pleased that -you are working on Jupyter. We hope you find the Developer Guide is useful. -Please suggest changes or ask questions about the contents. Thanks! +you are working on Jupyter. We hope you find the Developer Guide useful. +Please feel free to suggest changes or ask questions about the content. Thanks for your contribution! If you are interested in installing a specific project from source, each project has documentation on ReadTheDocs. For example, IPython documentation -can be found on `ReadTheDocs `_. +can be found on `ReadTheDocs `_. Most of our packages can be installed from the source directory like any other Python package, by running: @@ -28,4 +28,4 @@ Python package, by running: pip install . The Jupyter notebook needs some extra pieces to build Javascript components; -the information about that is in the `notebook contributor documentation `_. +the information about that is in the `notebook contributor documentation `_. diff --git a/docs/source/developer-docs/jupyter_enhancement_proposals.rst b/docs/source/contributing/dev-contributions/jupyter_enhancement_proposals.rst similarity index 100% rename from docs/source/developer-docs/jupyter_enhancement_proposals.rst rename to docs/source/contributing/dev-contributions/jupyter_enhancement_proposals.rst diff --git a/docs/source/developer-docs/releasing.rst b/docs/source/contributing/dev-contributions/releasing.rst similarity index 93% rename from docs/source/developer-docs/releasing.rst rename to docs/source/contributing/dev-contributions/releasing.rst index 21303b3dd..b697eed70 100644 --- a/docs/source/developer-docs/releasing.rst +++ b/docs/source/contributing/dev-contributions/releasing.rst @@ -1,4 +1,4 @@ -.. _releasing: +.. _releasing-Jupyter-Project: ============================================== Basic template for releasing a Jupyter project @@ -34,7 +34,7 @@ A release may be ready to go when it has zero open issues or pull requests. Release notes ============= -Once all of the issues and pull requests are dealt with, +Once all the issues and pull requests are dealt with, it's time to make release notes. The smaller projects generally have a :file:`changelog.rst` in the docs directory, where you can add a section for the new release. @@ -80,7 +80,7 @@ Tag the commit:: git tag -am "release $V" $V -And finally, publish everything, to github and PyPI using `twine `_:: +And finally, publish everything, to GitHub and PyPI using `twine `_:: twine upload dist/* git push origin @@ -95,4 +95,4 @@ by editing :file:`/_version.py` (or similar) again, and commit:: .. note:: The pushes assume that `origin` points to the main jupyter/ipython repo. - Depending how you use git, this could be `upstream` or something else. + Depending on how you use git, this could be `upstream` or something else. diff --git a/docs/source/contrib_docs/doc-future-index.rst b/docs/source/contributing/docs-contributions/doc-future-index.rst similarity index 93% rename from docs/source/contrib_docs/doc-future-index.rst rename to docs/source/contributing/docs-contributions/doc-future-index.rst index 7fd9ba9b0..a99494af2 100644 --- a/docs/source/contrib_docs/doc-future-index.rst +++ b/docs/source/contributing/docs-contributions/doc-future-index.rst @@ -9,6 +9,7 @@ Contents: repo-structure.md doc-new-repos.md doc-new-build.md + doc-new-translation.md This section helps a contributor set up the documentation infrastructure for a new project or an existing project without Sphinx documentation. \ No newline at end of file diff --git a/docs/source/contributing/docs-contributions/doc-issues-hub.md b/docs/source/contributing/docs-contributions/doc-issues-hub.md new file mode 100644 index 000000000..c70dc65a9 --- /dev/null +++ b/docs/source/contributing/docs-contributions/doc-issues-hub.md @@ -0,0 +1,13 @@ +# Documentation Issue Hub + +Each subproject has its own documentation. This page provides quick links +to documentation issues for Jupyter subprojects. + +## Docs Issues Per-Subproject + +- [Jupyter.org (meta-project) issues](https://github.com/jupyter/jupyter/labels/documentation) (`documentation` label) +- [Jupyter Notebook issues](https://github.com/jupyter/notebook/labels/documentation) (`documentation` label) +- [JupyterLab issues](https://github.com/jupyterlab/jupyterlab/labels/documentation) (`documentation` label) +- [Jupyter Server issues](https://github.com/jupyter-server/jupyter_server/labels/documentation) (`documentation` label) +- [JupyterHub issues](https://github.com/jupyterhub/jupyterhub/labels/documentation) (`documentation` label) +- [ipywidgets issues](https://github.com/jupyter-widgets/ipywidgets/labels/documentation) (`documentation` label) diff --git a/docs/source/contrib_docs/doc-new-build.md b/docs/source/contributing/docs-contributions/doc-new-build.md similarity index 60% rename from docs/source/contrib_docs/doc-new-build.md rename to docs/source/contributing/docs-contributions/doc-new-build.md index 0e8d4054f..d9940ab5c 100644 --- a/docs/source/contrib_docs/doc-new-build.md +++ b/docs/source/contributing/docs-contributions/doc-new-build.md @@ -13,7 +13,7 @@ project documentation whenever a pull request is merged into the GitHub repo. Each GitHub repo has a Settings tab at the far right of the repo menubar. Navigate to Settings and then the **Webhooks & services** submenu tab. -![Settings and Webhooks & services submenu](static/gh-webhooks-services.png "Screenshot of GitHub repo settings") +![The ipywidgets GitHub repository's "Settings" tab has been opened, with the "Add service" submenu expanded. The "ReadTheDocs" menu item is highlighted to indicate where on the page this setting can be found.](static/gh-webhooks-services.png) ### Add the ReadTheDocs service @@ -21,13 +21,13 @@ Select **Add service** and enter *ReadTheDocs* in the **Available Services** inp The Services/Add ReadTheDocs window will open. Press the green **Add service** button to activate the ReadTheDocs service. -![Add ReadTheDocs service](static/gh-add-rtd.png "Screenshot of adding ReadTheDocs service") +![In GitHub, the "Settings" tab of the ipywidgets repository shows that the "ReadTheDocs" service was successfully added to the project. A checkbox with the label "Active" indicates that the service is currently running.](static/gh-add-rtd.png) ### Success The ReadTheDocs service is added successfully. The service will take effect on the next merged pull request to the project repo. -![Service successfully added](static/gh-rtd-hook-success.png "Screenshot of service successfully added") +![In GitHub, the ipywidgets repository page is open. A banner notification at the top of the page is displayed, reading "Okay, that hook was successfully created."](static/gh-rtd-hook-success.png) *Created: 01-07-2016* diff --git a/docs/source/contrib_docs/doc-new-repos.md b/docs/source/contributing/docs-contributions/doc-new-repos.md similarity index 71% rename from docs/source/contrib_docs/doc-new-repos.md rename to docs/source/contributing/docs-contributions/doc-new-repos.md index 55928f1e0..fd3a3c535 100644 --- a/docs/source/contrib_docs/doc-new-repos.md +++ b/docs/source/contributing/docs-contributions/doc-new-repos.md @@ -11,14 +11,14 @@ On a larger scope, having the Jupyter name appear prominently in a repo's ### Link in repo description Please include a link to the documentation in the repo's description. -![Repo description and documentation link](static/repo-description.png "Screenshot of documentation link in GitHub repo description") +![Documentation link in GitHub jupyter/notebook repo description annotated with a red speech bubble reading "Add link to documentation (usually a link to Read the Docs.)")](static/repo-description.png) ### Badges in README One common way that individuals find documentation is to look for and click on the doc badge that commonly is found right after the title. Another benefit is an easy visual indication if the docs are not rendering properly. -![Badges in README.md](static/repo-badges.png "Screenshot of badges displayed under the repo title in the README file") +![The GitHub-rendered view of the README.md file for the Jupyter Notebook project is annotated with a red speech bubble reading "Add badge for Docs."](static/repo-badges.png) ### Resources section in README @@ -27,9 +27,8 @@ information to users about the individual project and the larger Project Jupyter organization. Make sure to include any links to the individual project's demo notebooks, if available. -The *Resources* section includes: +For example, here is the [Resources section from jupyter/notebook]:(https://github.com/jupyter/notebook/blob/master/README.md#resources) -![Resources section in `README.md`](static/repo-resources.png "Screenshot of resource list at end of README file") ## Checklist adding docs to a new or existing GitHub Repo diff --git a/docs/source/contributing/docs-contributions/doc-new-translation.md b/docs/source/contributing/docs-contributions/doc-new-translation.md new file mode 100644 index 000000000..13f5f4ebe --- /dev/null +++ b/docs/source/contributing/docs-contributions/doc-new-translation.md @@ -0,0 +1,382 @@ +# Supporting translations of documentation + +We support and encourage the translation of Jupyter documentation to other languages as one way of +making our community more inclusive and diverse. We are working toward having a consistent model for +translation of [Sphinx](https://www.sphinx-doc.org/) documentation across Jupyter projects based on +prior work in the [Python](https://python.org) and [Django](https://www.djangoproject.com/) +communities. This project (https://jupyter.readthedocs.io) and the +[Jupyter Docker Stacks project](https://jupyter-docker-stacks.readthedocs.io/) are early adopters, +meant to prove out the workflows described on this page. + +## Overview + +After initial project setup, changes to Sphinx documentation and its translations follow a +continuous integration (CI) and continuous deployment (CD), much like project source code. + +## Who is involved in translating documentation + +Anyone is welcome to participate in writing and translating Jupyter documentation by participating +in the workflow described below. This workflow has a handful of actors and components: + +- A person who makes changes to the English project documentation +- A person who translates snippets of text in the English documentations into another language + (locale) +- [Portable object files (`.po`)](https://en.wikipedia.org/wiki/Gettext) for the source + documentation language (e.g., U.S. English, `en-US`) and for other locales (e.g., Brazilian + Portuguese, `pt-BR`; Moroccan Arabic, `ar-MA`) +- A continuous integration system like TravisCI, CircleCI, or GitHub Actions, responsible for +- [ReadTheDocs](https:/readthedocs.org), our preferred service for building and hosting + documentation +- [Transifex](https://transifex.com), a localization platform with free plans for open source + projects, a friendly web interface, and support for `.po` files + +### The translation process + +![](static/translation-ci-cd.png) + + + +1. A user creates or edits reStructuredText (`.rst`) or Markdown (`.md`) documents written in U.S. + English. +2. The user submits a pull request on GitHub. +3. A project maintainer reviews and merges the pull request. +4. ReadTheDocs runs Sphinx to convert U.S. English source documents into HTML (e.g., + https://jupyter.readthedocs.io/en/latest/architecture/how_jupyter_ipython_work.html) +5. Meanwhile, the CI service runs Sphinx commands to extract translatable _messages_ from U.S. + English documents into `en-US` portable object (`.po`) files. For example: + +``` +# 5164fcd91a8a4700ac734562245773ad +#: ../../source/architecture/how_jupyter_ipython_work.rst:13 +#: f68a21b0bc884dad9021c276e6490e6d +msgid "" +"The IPython kernel that provides computation and communication with the " +"frontend interfaces, like the notebook" +msgstr "" +``` + +6. The CI service commits the English `.po` files to the project on GitHub. (e.g., + https://github.com/jupyter/jupyter/commit/1330bc409842d8b8a7bbb3a1c63259c34a543be0) +7. Transifex makes the messages in the English `.po` files available for translation in all + configured languages. +8. Over time, translation teams use the Transifex web application to create, review, and update + translations for those languages (e.g., + https://docs.transifex.com/translation/translating-with-the-web-editor) +9. Transifex submits a pull request to the GitHub project containing a localized `.po` file when all + of the English messages have been translated, and optionally reviewed, for a given language + (e.g., https://github.com/jupyter/jupyter/pull/485). For example: + +``` +# 5164fcd91a8a4700ac734562245773ad +#: ../../source/architecture/how_jupyter_ipython_work.rst:13 +msgid "" +"The IPython kernel that provides computation and communication with the " +"frontend interfaces, like the notebook" +msgstr "" +"The IPython kernel que fornece o cálculo e a comunicação com as interfaces " +"de frontend como o notebook" +``` + +10. A project maintainer reviews and merges the pull request. +11. ReadTheDocs once again runs Sphinx to convert U.S. English source documents into HTML. +12. ReadTheDocs also runs Sphinx to load localized `.po` files, substitute translations into the + original English text, and convert those translated documents into HTML (e.g., + https://jupyter.readthedocs.io/pt_BR/latest/architecture/how_jupyter_ipython_work.html) + +Note: We recognize this flow assumes documentation starts life written in U.S. English. We should +look into removing this assumption in the future if it becomes a significant barrier to new +contributions. + +(translator-workflows)= +## Community translator workflows + +We are delighted when members of the Jupyter community want to help translate documentation. We use +[Transifex](https://transifex.com) to on-board translators in a friendly web interface without +requiring knowledge of git, GitHub, Sphinx, or other software developer tools. + +### Creating translations + +[Getting Started as a Translator](https://docs.transifex.com/getting-started-1/translators) is an +excellent on-boarding guide for new Transifex users. Follow the instructions to create an account. +When prompted to join a team, look for _jupyter-meta-documentation_ to start contributing +translations to this documentation site. Alternatively, visit +https://www.transifex.com/project-jupyter/jupyter-meta-documentation/ after creating your account +and request to join the project. A project maintainer or language team coordinator will review and +approve your request. + +### Reviewing translations + +Transifex supports +[Reviewing Translations](https://docs.transifex.com/translation/reviewing-strings), peer review by +members of a language team, to ensure translation quality. Project maintainers can choose whether +Transifex should immediately send a pull request when translations of all text in a document are +available or delay submitting a pull request until after all of those translations are also reviewed +(the +[current setting for this project](https://github.com/jupyter/jupyter/issues/430#issuecomment-552138547)). + +### Coordinating translation teams + +Project maintainers can also grant Transfex team members the role of +[language coordinator](https://docs.transifex.com/teams/understanding-user-roles#organization-administrator). +Language coordinators have permission to invite users to language teams, approve or deny join +requests, assign language team roles, and perform other administrative actions for a particular +project language. Empowering trusted members of the community as coordinators can help grow +translation teams without software developer involvement. + +## Administrator workflows + +The translation CI/CD workflow described above requires configuration in GitHub and in Transifex to +function. Project maintainers can follow the instructions below to enable translations for their +Sphinx documentation. + +### Creating a Transifex organization + +Transifex organizes translation projects under organizations that mirror organizations and +repositories on GitHub. At present, only the https://github.com/jupyter organization has a +corresponding org on Transifex (https://www.transifex.com/project-jupyter/public/) with the +following +[organization administrators](https://docs.transifex.com/teams/understanding-user-roles#organization-administrator): + +- @choldgraf +- @parente +- @willingc + +GitHub users with permissions to install applications in a GitHub org can follow these instructions +to create a new Transifex-GitHub organization link (e.g., for https://github.com/jupyterhub, +https://github.com/jupyterlab). + +1. Create a new user account at https://transifex.com. +2. Complete the sign-up wizard. +3. Create and name a new organization. +4. Click the organization drop down in the top right of the Transifex dashboard page and select + _Organization Settings_. +5. Click _Details_ in the left sidebar. +6. Click _inviting administrators_ in the _Management_ section to add additional admins to the + Transifex org. +7. Click _Manage integrations_ in the left sidebar. +8. Click _Install the Transifex app_ in the GitHub section. +9. Select the GitHub organization to associate with the new Transifex organization. +10. Select the repositories that Transifex will have permission to access. +11. Return to the tab where you clicked _Install the Transifex app_ and click _authorize Transifex_ + in the GitHub section. +12. Choose the GitHub organization you just configured in the popup dialog. + +Note that you can revise the GitHub-Transifex integration at any time by visiting +https://github.com/settings/installations. + +### Creating a Transifex project + +Transifex +[organization administrators](https://docs.transifex.com/teams/understanding-user-roles#organization-administrator) +can follow the instructions below to configure new translation projects for GitHub projects in the +GitHub org corresponding to the one on Transifex. + +1. Visit https://www.transifex.com. +2. Sign in with the appropriate admin user account for the organization. +3. Click the organization drop down in the top right of the Transifex dashboard page and select + _Organization Settings_. +4. Click _Create new project_ in the lower left sidebar. +5. Name the translation project after the project on GitHub. +6. Select _Public_ as the privacy type, indicate that the project is open source, and provide the + GitHub URL for the repository. +7. Select a file-based project. +8. Create a new team for the project. +9. Select _English (en)_ as the source language. +10. Select known target languages. (You can add these later as well.) +11. Click _Create project_. +12. Click _Settings_ under the project name in the left sidebar. +13. Click the _Maintainers_ tab. +14. Invite additional + [project maintainers](https://docs.transifex.com/teams/understanding-user-roles#project-maintainers), + typically software developers who will be responsible for maintaining the continuous integration + and bootstrapping language teams. + +### Configuring languages and teams + +Transifex organization admins and project managers can add translation languages to a project. + +1. Visit https://www.transifex.com. +2. Sign in with the appropriate admin user account for the organization. +3. Click _Languages_ under the project name in the left sidebar. +4. Click _Edit languages_. +5. Add or remove target translation languages. +6. Click _Apply_. + +Organization admins, project maintainers, and +[team managers](https://docs.transifex.com/teams/understanding-user-roles#team-managers) can add +users to translation teams with the roles of language coordinator, reviewer, or translator. + +1. Click _Teams_ in the top nav bar. +2. Click the _Invite Collaborators_ button in the top right. +3. Enter the username, email address, or full name of a person to add to the project. Note that the + autocomplete in this field does not always display a popup for the user you wish to invite. + Confirm you've entered the correct value and move on. +4. Select [the role](https://docs.transifex.com/teams/understanding-user-roles) to assign to the + user. +5. If the role applies to a specific team, select the team. +6. If the role applies to a specific language, select the language. +7. Click _Invite more_ to enter additional users or _Send invitation_. + +### Configuring Transifex-GitHub integration + +After configuring organization and project resources on Transifex, project developers can: + +- configure Sphinx to produce `.po` files for the source language and read `.po` files containing + translations +- configure Transifex to watch for source language `.po` file changes +- configure the project CI service to update source language `.po` files when contributors make + changes to the source documentation + +The instructions in this section assume a git repository already contains Sphinx documentation in +the following directory structure: + +``` +my-project/ + docs/ + build/ # built sphinx artifacts go here + source/ # documentation source is in here + conf.py # sphinx config file + index.rst # root of the documentation + requirements.txt # sphinx, sphinx-intl, etc. +``` + +Project developers can do the following to configure Sphinx to seed source `.po` files and +recognization translation `.po` files. + +1. Add `sphinx-intl` to your Sphinx project `requirements.txt` or `environment.yaml` if it does not + already exist. +2. Run `sphinx-intl create-txconfig` in the `docs/` directory. +3. Add the following to the Sphinx `source/conf.py` file. + +```python +# -- Translation ------------------------------------------------------------- + +gettext_uuid = True +locale_dirs = ["locale/"] +``` + +3. Run `make gettext` to extract all strings from the English source documentation. +4. Run `sphinx-intl update -l en` to generate the English source `.po` files. +5. Submit, review, and merge a pull request with the changes and generated `.po` files. + +After merging the pull request, link to the Transifex project to the GitHub repository. + +1. Visit https://www.transifex.com. +2. Click _Settings_ under the project name in the left sidebar. +3. Click the _Integrations_ tab. +4. Click _Link Repository_ in the GitHub section. +5. Select the appropriate GitHub repository and integration branch. Then click _Next_. +6. Copy and paste the following configuration into the dialog, adjusting the commented values as + appropriate, and then click _Next_. + +```yaml +filters: + - filter_type: dir + file_format: PO + source_file_extension: po + # Change this if you selected a different source language during project setup + source_language: en + # The path in the GitHub repository where the source .po files reside + source_file_dir: "docs/source/locale/en/LC_MESSAGES" + # The path in the GitHub repository where translation .po files reside + translation_files_expression: "docs/source/locale//LC_MESSAGES" +``` + +7. Select when Transifex will submit translations a back to the repository. Then click _Save & + Sync_. +8. Click _Close_. +9. Watch the sync status progress. +10. Click _Resources_ in the left sidebar. +11. Click one of the `.po` files to see translation progress by language. +12. Click one of the languages to see details about translation progress, translate text, and review + translations. See the [Community translator workflows](#translator-workflows) section above for details. + +After confirming the initial English `.po` files have reached Transifex, set up continuous +integration to ensure source strings are kept up-to-date in Transifex whenever the English +documentation changes. The steps to accomplish this end vary depending on the CI provider. The +following describes how what to do when using GitHub Actions. + +1. Create a new GitHub actions workflow file `.github/workflows/gettext.yml` in the project. +2. Add the following content to the file. Note that `secrets.GITHUB_TOKEN` is a built-in secret, not + something you need to configure ahead of time. + +```yaml +name: Extract Translatable Strings + +# Run on all branch pushes +on: + push: + paths: + - "docs/source/**" + - "!docs/source/locale/**" + - ".github/workflows/gettext.yml" + +jobs: + gettext: + runs-on: ubuntu-latest + steps: + - name: Checkout Code + uses: actions/checkout@master + - name: Set up Python + uses: actions/setup-python@v2 + with: + python-version: "3.x" + - name: Install dependencies + working-directory: docs + run: pip install -r requirements.txt + - name: Extract source strings + working-directory: docs + run: | + make gettext + sphinx-intl update -l en + - name: Push to master + # Only commit changes to master if master just changed + if: github.ref == 'refs/heads/master' + uses: mikeal/publish-to-github-action@master + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} +``` + +3. Submit, review, and merge a pull request containing the workflow YAML. + +Once you complete the steps in this section, any changes to the source English documentation on the +master branch are pulled into Transifex for translation. Likewise, any translations completed on +Transifex are submitted as pull requests back to the project on GitHub. + +### Hosting translations on ReadTheDocs + +ReadTheDocs supports building HTML documentation sites from a single GitHub project and its +translations. Administrators of the source language documentation project on ReadTheDocs can +following these instructions to enable builds for other languages. + +1. Visit https://readthedocs.org/dashboard/ +2. Note the name of existing ReadTheDocs project containing your source language (e.g., `jupyter`). +3. Click `Import a Project`. +4. Click `Import Manually`. +5. Enter the project name you noted above suffixed with a target language locale (e.g., + `jupyter-es`, `jupyter-pt-br`). +6. Enter the GitHub URL of the project. +7. Check _Edit advanced project options_. +8. Click _Next_. +9. Select the name of the target language from the _Language_ drop down (e.g. `es` -> _Spanish_, + `es-mx` -> _Mexican Spanish_, `pt-br` -> _Brazillian Portuguese_). +10. Click `Finish`. +11. Return to the list of projects at https://readthedocs.org/dashboard/ +12. Click the project containing the source language. +13. Click _Admin_. +14. Click _Translations_. +15. Choose the name of the translation project created in step 5 from the _Project_ drop down. +16. Click _Add_. +17. Repeat these steps for all other languages the project supports. + +Now, any time you merge a pull request from Transifex containing `.po` translation file updates, +ReadTheDocs will build both the source documentation site as well as sites for all supported +languages. ReadTheDocs will associate the sites with one another and make them accessible via +language links in a popup. + +![Project Jupyter documentation site with the ReadTheDocs popup open on the right, showing links to the documentation in other languages.](static/translation-rtd-popup.png) + +## Reference + +https://github.com/parente/helloworld-transifex-rtd is a mini-project configured to support the +entire workflow described in this document. diff --git a/docs/source/contrib_docs/doc-tools.rst b/docs/source/contributing/docs-contributions/doc-tools.rst similarity index 95% rename from docs/source/contrib_docs/doc-tools.rst rename to docs/source/contributing/docs-contributions/doc-tools.rst index 30eda7a92..ae3f699a7 100644 --- a/docs/source/contrib_docs/doc-tools.rst +++ b/docs/source/contributing/docs-contributions/doc-tools.rst @@ -9,7 +9,7 @@ Packages For user documentation, contributor guides, and communications content, we use: -- `Sphinx `_ +- `Sphinx `_ For developer API documentation (especially for JupyterLab js repos), we use: diff --git a/docs/source/contrib_docs/doc-workflow.rst b/docs/source/contributing/docs-contributions/doc-workflow.rst similarity index 100% rename from docs/source/contrib_docs/doc-workflow.rst rename to docs/source/contributing/docs-contributions/doc-workflow.rst diff --git a/docs/source/contrib_docs/getting-started.rst b/docs/source/contributing/docs-contributions/getting-started.rst similarity index 77% rename from docs/source/contrib_docs/getting-started.rst rename to docs/source/contributing/docs-contributions/getting-started.rst index 928fb5b43..2a5e05257 100644 --- a/docs/source/contrib_docs/getting-started.rst +++ b/docs/source/contributing/docs-contributions/getting-started.rst @@ -6,16 +6,19 @@ Getting started Preparing for your first contribution ------------------------------------- -1. Our documentation uses reStructured Text as well as Jupyter notebooks. +1. Our documentation uses reStructured Text, Markdown, and Jupyter notebooks. 2. We use Sphinx extensively to build documentation. -3. We host our documentation on Read the Docs. +3. We use Transifex to help translate documentation to multiple languages. +4. We host our documentation on Read the Docs. Developing your contribution ---------------------------- +Jupyter's documentation is split across several projects, listed on the `Jupyter documentation home page `_. These instructions apply to all Jupyter projects, though some projects have further contribution guidelines. + Clone the repository ~~~~~~~~~~~~~~~~~~~~ -1. Fork the project repository found on GitHub. +1. Fork the appropriate project repository on GitHub, depending on which project's documentation you want to contribute to. 2. Clone the repository to your system. Edit the documentation source file @@ -41,7 +44,7 @@ we recommend that you install the stable development version Sphinx (``pip install git+https://github.com/sphinx-doc/sphinx@stable``) or the current released version of Sphinx (``pip install sphinx``). -In addition, you may need the following packages: sphinxcontrib-spelling, sphinx_rtd_theme, nbsphinx and pyenchant, which can be installed via ``pip install sphinxcontrib-spelling sphinx_rtd_theme nbsphinx pyenchant``. +In addition, you may need the following packages: sphinxcontrib-spelling, sphinx_rtd_theme, nbsphinx, pyenchant, recommonmark 0.4.0 and jupyter_sphinx_theme, which can be installed via ``pip install sphinxcontrib-spelling sphinx_rtd_theme nbsphinx pyenchant recommonmark==0.4.0 jupyter_sphinx_theme``. If you are on Linux, you may also need to install the Enchant C library by running ``sudo apt-get install enchant``. diff --git a/docs/source/contrib_docs/index.rst b/docs/source/contributing/docs-contributions/index.rst similarity index 86% rename from docs/source/contrib_docs/index.rst rename to docs/source/contributing/docs-contributions/index.rst index f231c6305..b38263464 100644 --- a/docs/source/contrib_docs/index.rst +++ b/docs/source/contributing/docs-contributions/index.rst @@ -1,3 +1,5 @@ +.. _documentation-guide: + =================== Documentation Guide =================== @@ -10,11 +12,8 @@ Documentation Guide getting-started.rst doc-workflow.rst doc-tools.rst - doc-style.rst - doc-bugs.rst - doc-build.rst - doc-tracking.rst doc-future-index.rst + doc-issues-hub.md Documentation helps guide new users, fosters communication between developers, and shares tips and best practices with other community members. That's why diff --git a/docs/source/contrib_docs/repo-structure.md b/docs/source/contributing/docs-contributions/repo-structure.md similarity index 51% rename from docs/source/contrib_docs/repo-structure.md rename to docs/source/contributing/docs-contributions/repo-structure.md index 64f57582d..d315209e1 100644 --- a/docs/source/contrib_docs/repo-structure.md +++ b/docs/source/contributing/docs-contributions/repo-structure.md @@ -7,7 +7,7 @@ - ``readthedocs.yml`` : configuration file for readthedocs to build using conda -![Repo root directory](static/repo-root.png "Screenshot of GitHub repo root") +![The root level of the jupyter kernel_gateway repo. There are orange boxes surrounding two elements in the directory structure: the docs folder and the readthedocs.yml file. The docs folder is the first element in the directory. The readthedocs.yml file is the 12th item in the directory.](static/repo-root.png) ## Inside the docs directory @@ -16,7 +16,7 @@ - ``makefile`` : used by Sphinx to build the docs - ``environment.yml`` : conda build instructions -![``docs`` directory](static/docs-directory.png "Screenshot of docs directory") +![The docs directory in the jupyter kernel_gateway repo (path: jupyter/kernel_gateway/docs). The first two elements in the directory are folders that have blue boxes surrounding them: `_static` and `source`. The third and forth elements in the directory are files with orange boxes surrounding them: `Makefile` and `environment.yml`. There are two more files in the directory, which have no visual emphasis.](static/docs-directory.png) ## Sphinx diff --git a/docs/source/contrib_docs/static/doc_helper.png b/docs/source/contributing/docs-contributions/static/doc_helper.png similarity index 100% rename from docs/source/contrib_docs/static/doc_helper.png rename to docs/source/contributing/docs-contributions/static/doc_helper.png diff --git a/docs/source/contrib_docs/static/docs-directory.png b/docs/source/contributing/docs-contributions/static/docs-directory.png similarity index 100% rename from docs/source/contrib_docs/static/docs-directory.png rename to docs/source/contributing/docs-contributions/static/docs-directory.png diff --git a/docs/source/contrib_docs/static/gh-add-rtd.png b/docs/source/contributing/docs-contributions/static/gh-add-rtd.png similarity index 100% rename from docs/source/contrib_docs/static/gh-add-rtd.png rename to docs/source/contributing/docs-contributions/static/gh-add-rtd.png diff --git a/docs/source/contrib_docs/static/gh-rtd-hook-success.png b/docs/source/contributing/docs-contributions/static/gh-rtd-hook-success.png similarity index 100% rename from docs/source/contrib_docs/static/gh-rtd-hook-success.png rename to docs/source/contributing/docs-contributions/static/gh-rtd-hook-success.png diff --git a/docs/source/contrib_docs/static/gh-webhooks-services.png b/docs/source/contributing/docs-contributions/static/gh-webhooks-services.png similarity index 100% rename from docs/source/contrib_docs/static/gh-webhooks-services.png rename to docs/source/contributing/docs-contributions/static/gh-webhooks-services.png diff --git a/docs/source/contrib_docs/static/repo-badges.png b/docs/source/contributing/docs-contributions/static/repo-badges.png similarity index 100% rename from docs/source/contrib_docs/static/repo-badges.png rename to docs/source/contributing/docs-contributions/static/repo-badges.png diff --git a/docs/source/contrib_docs/static/repo-description.png b/docs/source/contributing/docs-contributions/static/repo-description.png similarity index 100% rename from docs/source/contrib_docs/static/repo-description.png rename to docs/source/contributing/docs-contributions/static/repo-description.png diff --git a/docs/source/contrib_docs/static/repo-resources.png b/docs/source/contributing/docs-contributions/static/repo-resources.png similarity index 100% rename from docs/source/contrib_docs/static/repo-resources.png rename to docs/source/contributing/docs-contributions/static/repo-resources.png diff --git a/docs/source/contrib_docs/static/repo-root.png b/docs/source/contributing/docs-contributions/static/repo-root.png similarity index 100% rename from docs/source/contrib_docs/static/repo-root.png rename to docs/source/contributing/docs-contributions/static/repo-root.png diff --git a/docs/source/contributing/docs-contributions/static/translation-ci-cd.png b/docs/source/contributing/docs-contributions/static/translation-ci-cd.png new file mode 100644 index 000000000..5b00b9c82 Binary files /dev/null and b/docs/source/contributing/docs-contributions/static/translation-ci-cd.png differ diff --git a/docs/source/contributing/docs-contributions/static/translation-ci-cd.svg b/docs/source/contributing/docs-contributions/static/translation-ci-cd.svg new file mode 100644 index 000000000..2b6963cd8 --- /dev/null +++ b/docs/source/contributing/docs-contributions/static/translation-ci-cd.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/docs/source/contributing/docs-contributions/static/translation-rtd-popup.png b/docs/source/contributing/docs-contributions/static/translation-rtd-popup.png new file mode 100644 index 000000000..e52cc06e3 Binary files /dev/null and b/docs/source/contributing/docs-contributions/static/translation-rtd-popup.png differ diff --git a/docs/source/development_guide/boot2docker.rst b/docs/source/contributing/ipython-dev-guide/boot2docker.rst similarity index 100% rename from docs/source/development_guide/boot2docker.rst rename to docs/source/contributing/ipython-dev-guide/boot2docker.rst diff --git a/docs/source/development_guide/closing_prs.rst b/docs/source/contributing/ipython-dev-guide/closing_prs.rst similarity index 97% rename from docs/source/development_guide/closing_prs.rst rename to docs/source/contributing/ipython-dev-guide/closing_prs.rst index 5577f5969..65dc3fa81 100644 --- a/docs/source/development_guide/closing_prs.rst +++ b/docs/source/contributing/ipython-dev-guide/closing_prs.rst @@ -57,5 +57,5 @@ Example Message: Thanks for contributing. - see https://github.com/ipython/ipython/wiki/Dev%3A-Closing-pull-requests/ for - our policies on closing pull request. + see https://github.com/ipython/ipython/wiki/Dev%3A-Closing-pull-requests/ for + our policies on closing pull requests. diff --git a/docs/source/development_guide/coding_style.rst b/docs/source/contributing/ipython-dev-guide/coding_style.rst similarity index 98% rename from docs/source/development_guide/coding_style.rst rename to docs/source/contributing/ipython-dev-guide/coding_style.rst index d33bde8bb..8855b3605 100644 --- a/docs/source/development_guide/coding_style.rst +++ b/docs/source/contributing/ipython-dev-guide/coding_style.rst @@ -78,7 +78,7 @@ code harder to read and requires methods to constantly use checks with hasattr() or try/except calls. By declaring all attributes of the object in the class header, there is a single place one can refer to for understanding the object's data interface, where comments can explain -the role of each variable and when possible, sensible deafaults can be +the role of each variable and when possible, sensible defaults can be assigned. If an attribute is meant to contain a mutable object, it should be set @@ -99,7 +99,7 @@ A simple example: y = None # z starts as an empty list, must be set in constructor z = None - + def __init__(self, y): self.y = y self.z = [] diff --git a/docs/source/development_guide/documenting_ipython.rst b/docs/source/contributing/ipython-dev-guide/documenting_ipython.rst similarity index 100% rename from docs/source/development_guide/documenting_ipython.rst rename to docs/source/contributing/ipython-dev-guide/documenting_ipython.rst diff --git a/docs/source/development_guide/github_workflow.rst b/docs/source/contributing/ipython-dev-guide/github_workflow.rst similarity index 100% rename from docs/source/development_guide/github_workflow.rst rename to docs/source/contributing/ipython-dev-guide/github_workflow.rst diff --git a/docs/source/development_guide/index.rst b/docs/source/contributing/ipython-dev-guide/index.rst similarity index 100% rename from docs/source/development_guide/index.rst rename to docs/source/contributing/ipython-dev-guide/index.rst diff --git a/docs/source/development_guide/js_events.rst b/docs/source/contributing/ipython-dev-guide/js_events.rst similarity index 97% rename from docs/source/development_guide/js_events.rst rename to docs/source/contributing/ipython-dev-guide/js_events.rst index a30c59405..3111ea2fa 100644 --- a/docs/source/development_guide/js_events.rst +++ b/docs/source/contributing/ipython-dev-guide/js_events.rst @@ -6,7 +6,7 @@ JavaScript Events .. attention:: This is copied verbatim from the old IPython wiki and is currently under development. Much of the information in this part of the development guide is out of date. -(Note: this page is not currently consistent with IPython master) +(Note: this page is not currently consistent with IPython/Jupyter master) Javascript events are used to notify unrelated parts of the notebook interface when something happens. For example, if the kernel is busy @@ -43,10 +43,10 @@ Dashboard-related events app\_initialized.DashboardApp ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -When the iPython Notebook browser window opens for the first time and +When the Jupyter Notebook browser window opens for the first time and initializes the Dashboard App. The Dashboard App lists the files and notebooks in the current directory. Additionally, it lets you create and -open new iPython Notebooks. +open new Jupyter Notebooks. Kernel-related events --------------------- diff --git a/docs/source/development_guide/lab_meetings.rst b/docs/source/contributing/ipython-dev-guide/lab_meetings.rst similarity index 100% rename from docs/source/development_guide/lab_meetings.rst rename to docs/source/contributing/ipython-dev-guide/lab_meetings.rst diff --git a/docs/source/development_guide/less.rst b/docs/source/contributing/ipython-dev-guide/less.rst similarity index 100% rename from docs/source/development_guide/less.rst rename to docs/source/contributing/ipython-dev-guide/less.rst diff --git a/docs/source/development_guide/pull_request.rst b/docs/source/contributing/ipython-dev-guide/pull_request.rst similarity index 84% rename from docs/source/development_guide/pull_request.rst rename to docs/source/contributing/ipython-dev-guide/pull_request.rst index 47b468e9e..2e54b4efe 100644 --- a/docs/source/development_guide/pull_request.rst +++ b/docs/source/contributing/ipython-dev-guide/pull_request.rst @@ -26,7 +26,7 @@ IPython has to work on: Much of our code base deals with strings and unicode. This needs to be done in a manner that is unicode aware and works on Python 2 and 3. -[This article] (http://www.joelonsoftware.com/articles/Unicode.html) is +`This article `__ is a good intro to unicode. 4. Adheres to our coding style @@ -34,7 +34,7 @@ a good intro to unicode. Coding style refers to how source code is formatted and how variables, functions, methods and classes are named. Your code should follow our -coding style, which is described [[here\|Dev: Coding style]]. +coding style, which is described `here `__. 5. Clean & commented -------------------- @@ -51,14 +51,13 @@ If it fixes a bug, the pull request should ideally add an automated test that fails without the fix, and passes with it. Normally it should be sufficient to copy an existing test and tweak it. New functionality should come with its own tests as well. Details about testing IPython -can be found [[here\|Dev: Testing]]. +can be found `here `__. 7. Well documented ------------------ Don't forget to update docstrings, and any relevant parts of `the official -documentation `__. New +documentation `__. New features or significant changes warrant an entry in the *What's New* -section too. Details about documenting IPython can be found [[here\|Dev: -Documenting IPython]]. +section too. Details about documenting IPython can be found `here `__. \ No newline at end of file diff --git a/docs/source/development_guide/py3compat.rst b/docs/source/contributing/ipython-dev-guide/py3compat.rst similarity index 100% rename from docs/source/development_guide/py3compat.rst rename to docs/source/contributing/ipython-dev-guide/py3compat.rst diff --git a/docs/source/development_guide/releasing.rst b/docs/source/contributing/ipython-dev-guide/releasing.rst similarity index 99% rename from docs/source/development_guide/releasing.rst rename to docs/source/contributing/ipython-dev-guide/releasing.rst index 232b14df0..d8d41e700 100644 --- a/docs/source/development_guide/releasing.rst +++ b/docs/source/contributing/ipython-dev-guide/releasing.rst @@ -1,4 +1,4 @@ -.. _releasing: +.. _releasing-IPython: Steps for Releasing IPython =========================== diff --git a/docs/source/development_guide/rest_api.rst b/docs/source/contributing/ipython-dev-guide/rest_api.rst similarity index 98% rename from docs/source/development_guide/rest_api.rst rename to docs/source/contributing/ipython-dev-guide/rest_api.rst index 1c8022970..5c433dfa2 100644 --- a/docs/source/development_guide/rest_api.rst +++ b/docs/source/contributing/ipython-dev-guide/rest_api.rst @@ -145,12 +145,12 @@ Sessions API | HTTP | URL | Action | | verb | | | +============+=================+========================================+ -| ``GET`` | /api/sesions | Return model of active sessions. | +| ``GET`` | /api/sessions | Return model of active sessions. | +------------+-----------------+----------------------------------------+ | ``POST`` | /api/sessions | If session does not already exist, | | | | create a new session with given | | | | notebook name and path and given | -| | | kernel name. Return active sesssion. | +| | | kernel name. Return active session. | +------------+-----------------+----------------------------------------+ | ``GET`` | /api/sessions | Return model of active session with | | | / | given session id. | @@ -219,10 +219,10 @@ This chart shows the architecture for the IPython notebook website. +------------+-----------------+----------------------------------------+ | ``GET`` | /new | creates a new notebook with profile | | | | (or default, if no profile exists) | -| | | setings | +| | | settings | +------------+-----------------+----------------------------------------+ | ``GET`` | / | opens a duplicate copy or the notebook | -| | /copy | with the given ID in a a new tab | +| | /copy | with the given ID in a new tab | +------------+-----------------+----------------------------------------+ | ``GET`` | / | prints the notebook with the given ID; | | | /print | if notebook doesn't exist, displays | diff --git a/docs/source/development_guide/sphinx_directive.rst b/docs/source/contributing/ipython-dev-guide/sphinx_directive.rst similarity index 99% rename from docs/source/development_guide/sphinx_directive.rst rename to docs/source/contributing/ipython-dev-guide/sphinx_directive.rst index 051760c0b..94a0edf53 100644 --- a/docs/source/development_guide/sphinx_directive.rst +++ b/docs/source/contributing/ipython-dev-guide/sphinx_directive.rst @@ -177,7 +177,7 @@ the inputs:: Likewise, you can set ``:doctest:`` or ``:verbatim:`` to apply these settings to the entire block. For example, -.. code:: python3 +.. code:: bash In [9]: cd mpl/examples/ /home/jdhunter/mpl/examples @@ -340,7 +340,7 @@ And persist across sessions print square(3) print square(-2) -Pretty much anything you can do with the ipython code, you can do with +Pretty much anything you can do with the ipython code, you can do with a simple python script. Obviously, though it doesn't make sense to use the doctest option. diff --git a/docs/source/development_guide/template.py b/docs/source/contributing/ipython-dev-guide/template.py similarity index 95% rename from docs/source/development_guide/template.py rename to docs/source/contributing/ipython-dev-guide/template.py index 3fe20468b..91a05c82e 100644 --- a/docs/source/development_guide/template.py +++ b/docs/source/contributing/ipython-dev-guide/template.py @@ -22,7 +22,7 @@ # # If a file is large and has many sections, you may want to use broad section # headers like this one that make it easier to navigate the file, -# with descriptive titles. For complex classes, simliar (but indented) +# with descriptive titles. For complex classes, similar (but indented) # headers are useful to organize the internal class structure. #----------------------------------------------------------------------------- @@ -32,4 +32,3 @@ #----------------------------------------------------------------------------- # Local utilities #----------------------------------------------------------------------------- - diff --git a/docs/source/development_guide/testing.rst b/docs/source/contributing/ipython-dev-guide/testing.rst similarity index 99% rename from docs/source/development_guide/testing.rst rename to docs/source/contributing/ipython-dev-guide/testing.rst index d343d382b..57b95b7d6 100644 --- a/docs/source/development_guide/testing.rst +++ b/docs/source/contributing/ipython-dev-guide/testing.rst @@ -48,7 +48,7 @@ terminal: python2 -c "import IPython; IPython.start_ipython();" -To start the webbased notebook you can use: +To start the web-based notebook you can use: .. code:: bash @@ -425,7 +425,7 @@ Testing system design notes This section is a set of notes on the key points of the IPython testing needs, that were used when writing the system and should be kept for -reference as it eveolves. +reference as it evolves. Testing IPython in full requires modifications to the default behavior of nose and doctest, because the IPython prompt is not recognized to diff --git a/docs/source/development_guide/testing_kernels.rst b/docs/source/contributing/ipython-dev-guide/testing_kernels.rst similarity index 100% rename from docs/source/development_guide/testing_kernels.rst rename to docs/source/contributing/ipython-dev-guide/testing_kernels.rst diff --git a/docs/source/contributing/start-contributing.rst b/docs/source/contributing/start-contributing.rst new file mode 100644 index 000000000..cec945324 --- /dev/null +++ b/docs/source/contributing/start-contributing.rst @@ -0,0 +1,88 @@ +============================ +Getting Started Contributing +============================ + +.. contents:: Contents + :local: + +Welcome fellow contributor! We appreciate your help. + +We typically label issues appropriate for new contributors as ``good first +issue`` or ``help wanted``. To start an issue, you may comment to let everyone +know that you'll be working on it. Our repos typically provide development +installation instructions in each repo's ``CONTRIBUTING.md`` or ``README.md``. +**Should you find an issue with our development installation instructions please +let us know in our issues.** We want to ensure that our documentation for +development installation is accurate. Additionally, other contributors are +often available to answer questions about fixing the issue on the issue number +or on the repo's gitter channel. + +We strive to have a inclusive, welcoming community. Please read our `code of +conduct `__ +to learn more. + +Major Repos and Issue Types +=========================== + +Python +------ + +IPython, nbgrader, JupyterHub, repo2docker, and Binder are major repos written primarily in Python. + +* `IPython `__ + * `Notable Issues `__ + * `Development Installation `__ + * `Gitter Channel `__ +* `nbgrader `__ + * `Notable Issues `__ + * `Development Installation `__ +* `JupyterHub `__ + * `Notable Issues `__ + * `Development Installation `__ + * `Gitter Channel `__ +* `repo2docker `__ + * `Notable Issues `__ + * `Development Installation `__ + * `Gitter Channel `__ +* `Binder `__ + * `Notable Issues `__ + * `Development Installation `__ + * `Gitter Channel `__ + +Documentation +------------- + +All our repos have documentation issues that are relevant for new contributors. For example, the source +for the documentation you are reading right now can be found in the `jupyter/jupyter repository on GitHub `__. + +JavaScript/TypeScript +--------------------- + +Jupyter Notebook, JupyterLab, and IPyWidgets use JavaScript and TypeScript. + +* `Jupyter Notebook `__ + * `Notable Issues `__ + * `Development Installation `__ + * `Gitter Channel `__ +* `JupyterLab `__ + * `Notable Issues `__ + * `Development Installation `__ + * `Gitter Channel `__ +* `IPyWidgets `__ + * `Notable Issues `__ + * `Development Installation `__ + * `Gitter Channel `__ + +DevOps +------ + +JupyterHub, repo2docker, and Binder have many issues related to devops. See the links above. + +Web Development +--------------- + +We have issues related to the website. + +* `Project Jupyter's Website `__ + * `Notable Issues `__ + * `Developer Installation `__ diff --git a/docs/source/contributor/content-contributor.rst b/docs/source/contributor/content-contributor.rst deleted file mode 100644 index b665d0af4..000000000 --- a/docs/source/contributor/content-contributor.rst +++ /dev/null @@ -1,29 +0,0 @@ -Contributor Guides -================== - -.. toctree:: - :maxdepth: 1 - - ../developer-docs/index - ../development_guide/index - ../contrib_docs/index - contrib_guide_blog - -Whether you are a new, returning, or current contributor to Project -Jupyter's subprojects or IPython, **we welcome you**. - -Project Jupyter has seen steady growth over the past several years, and it is -wonderful to see the many ways people are using these projects. As a result of -this rapid expansion, our project maintainers are balancing many requirements, -needs, and resources. We ask contributors to take some time to become familiar -with our contribution guides and spend some time learning about our project -communication and workflow. - -The Contributor Guides and individual project documentation offer -guidance. If you have a question, please ask us. `Community Resources -`_ provides information on our commonly -used communication methods. - -We are very pleased to have you as a contributor, and we hope you -will find valuable your impact on the projects. **Thank you** for -sharing your interests, ideas, and skills with us. \ No newline at end of file diff --git a/docs/source/developer-docs/contrib_guide_bugs_enh.rst b/docs/source/developer-docs/contrib_guide_bugs_enh.rst deleted file mode 100644 index e406c7d18..000000000 --- a/docs/source/developer-docs/contrib_guide_bugs_enh.rst +++ /dev/null @@ -1,28 +0,0 @@ -================= -Submitting a Bug -================= -While using the Notebook, you might experience a bug that manifests itself in -unexpected behavior. If so, we encourage you to open issues on GitHub. To -make the navigating issues easier for both developers and users, we ask that -you take the following steps before submitting an issue. - -1. Search through StackOverflow and existing GitHub issues to ensure that - the issue has not already been reported by another user. If so, provide - your input on the existing issue if you think it would be valuable. - -2. Prepare a small, self-contained snippet of code that will allow others - to reproduce the issue that you are experiencing. - -3. Prepare information about the environment that you are executing the code - in, in order to aid in the debugging of the issue. You will need to provide - information about the Python version, Jupyter version, operating system, - and browser that you are using when submitting bugs. You can also use - ``pip list`` or ``conda list`` and ``grep`` in order to identify the - versions of the libraries that are relevant to the issue that you are - submitting. - -4. Prepare a simple test that outlines the expected behavior of the code - or a description of the what the expected behavior should be. - -5. Prepare an explanation of why the current behavior is not desired and - what it should be. \ No newline at end of file diff --git a/docs/source/developer-docs/contrib_guide_code.rst b/docs/source/developer-docs/contrib_guide_code.rst deleted file mode 100644 index e3b4d852e..000000000 --- a/docs/source/developer-docs/contrib_guide_code.rst +++ /dev/null @@ -1,162 +0,0 @@ -=============== -Developer Guide -=============== - -.. contents:: Contents - :local: - -A Note on Contributing to Open Source -------------------------------------- - -Contributing to open source can be a nerve-wrecking process, but don't worry -everyone on the Jupyter team is dedicated to making sure that your open source -experience is as fun as possible. At any time during the process described -below, you can reach out to the Jupyter team on Gitter or the mailing list for -assistance. If you are nervous about asking questions in public, you can also -reach out to one of the Jupyter developers in private. You can use the public -Gitter to find someone who has the best knowledge about the code you are -working with and interact with the in a personal chat. - -As you begin your open source journey, remember that it's OK if you don't -understand something, it's OK to make mistakes, and it's OK to only contribute -a small amount of the code necessary to fix the issue you are tackling. Any and -all help is welcome and any and all people are encouraged to contribute. - -How can I help? ---------------- - -Individuals are welcome, and encouraged, to submit pull requests and contribute -to the Jupyter source. If you are a first-time contributor looking to get -involved with Jupyter, you can use the following query in a GitHub search to -find beginner-friendly issues to tackle across the Jupyter codebase. This query -is particularly useful because the Jupyter codebase is scattered across several -repositories within the jupyter organization, as opposed to a single -repository. You can click the link below to find sprint-friendly issues. - -`is:issue is:open is:sprint-friendly user:jupyter -`_ - -Once you've found an issue that you are eager to solve, you can use the guide -below to get started. If you experience any problems while working on the -issue, leave a comment on the issue page in GitHub and someone on the core team -will be able to lend you assistance. - -Please keep in mind that what follows are guidelines. If you work through the -steps and have questions or run into time constraints, please submit what you -already have worked on as a pull request and ask questions on it. Your effort, -including partial or in-progress work, is appreciated. - -1. Fork the repository associated with the issue you are addressing and clone - it to a local directory on your machine. - -2. ``cd`` into the directory and create a new branch using ``git checkout -b - insert-branch-name-here``. Pick a branch name that gives some insight into - what the issue you are fixing is. For example, if you are updating the text - that is logged out by the program when a certain error happens you might - name your branch `update-error-text`. - -3. Refer to the repository's README and documentation for details on - configuring your system for development. - -4. Identify the module or class where the code change you will make will - reside and leave a comment in the file describing what issue you are trying - to address. - -5. Open a pull request to the repository with ``[WIP]`` appended to the front - so that the core team is aware that you are actively pursuing the issue. - When creating a pull request, make sure that the title clearly and concisely - described what your code does. For example, we might use the title "Updated - error message on ExampleException". In the body of the pull request, make - sure that you include the phrase "Closes #issue-number-here", where the - issue number is the issue number of the issue that you are addressing in - this PR. - - Feel free to open a PR as early as possible. Getting early feedback on your - approach will save you time and prevent the need for an extensive refactor - later. - -6. Run the test suite locally in order to ensure that everything is properly - configured on your system. Refer to the repository's README for information - on how to run the test suite. This will typically require that you run the - ``nosetests`` command on the commandline. Alternatively, you may submit a - pull request. Our Continuous Integration system will test your code and - report test results. - -7. Find the test file associated with the module that you will be changing. - In the test file, add some tests that outline what you expect the behavior - of the change should be. If we continue with our example of updating the - text that is logged on error, we might write test cases that check to see - if the exception raised when you induce the error contains the appropriate - string. When writing test cases, make sure that you test for the following - things. - - * What is the simplest test case I can write for this issue? - * What will happen if your code is given messy inputs? - * What will happen if your code is given no inputs? - * What will happen if your code is given too few inputs? - * What will happen if your code is given too many inputs? - - If you need assistance writing test cases, you can place a comment on the - pull request that was opened earlier and one of the core team members will - be able to help you. - -8. Go back to the file that you are updating and begin adding the code for your - pull request. - -9. Run the test suite again to see if your changes have caused any of the test - cases to pass. If any of the test cases have failed, go back to your code - and make the updates necessary to have them pass. - -10. Once all of your test cases have passed, commit both the test cases and the - updated module and push the updates to the branch on your forked repository. - -11. Once you are ready for your pull request to be reviewed, remove the [WIP] - tag from the front of issue, a project reviewer will review your code for - quality. You can expect the reviewer to check for the documentation - provided in the changes you made, how thorough the test cases you provided - are, and how efficient your code is. Your reviewer will provide feedback on - your code and you will have the chance to edit your code and apply fixes. - -12. Once your PR is ready to become a part of the code base, it will be merged - by a member of the core team. - -Contribution Workflow ---------------------- -.. image:: ../_static/_images/contribution_workflow.png - - - -Core Developer Workflow ------------------------ - -To help you understand our review process by core developers after you submit a -pull request, here's a guide that outlines the general process (specifics may -vary a bit across our repositories). Here is an example for Jupyter notebook -4.x: - - - -In general, Pull Requests are against ``master`` unless they only affect a -backport branch. If a PR affects master and should be backported, the general -flow is: - - 0. mark the PR with milestone for the next backport release (4.3) - 1. merge into master - 2. backport to 4.x - 3. push updated 4.x branch - -Backports can be done in a variety of ways, but we have `a script -`_ for -automating the common process to: - - 1. download the patch ` e.g. ` - 2. checkout the 4.x branch - 3. apply the patch - 4. make a commit - -which works for simple cases, at least. - -In this case, it would be: - - python /path/to/ipython-repo/tools/backport_pr.py jupyter/notebook 4.x 1645 - diff --git a/docs/source/glossary.rst b/docs/source/glossary.rst index 40ea78d78..4cffe6004 100644 --- a/docs/source/glossary.rst +++ b/docs/source/glossary.rst @@ -6,27 +6,110 @@ Glossary .. glossary:: + `client-server-architecture `_ + A `software design pattern `_ used by + Jupyter applications like **JupyterLab**. With this pattern, a server program (running + on a user's computer or on a server that can be accessed over a business or public + network) provides access to stored information (in JupyterLab's case, documents in + a folder such as notebooks and other data files), and a client program (the web + application and editing interface for JupyterLab in this case) connects to the + server program to view and interact with that data. + + console + In modern times, a `console `_ refers to a simple text-based program where you type commands for your + computer to run, also commonly called a `terminal `_. + command line - The terminal or console window where you type commands. + A simple text-based program where you type commands for your computer to run, also + called a `terminal `_ or `console `_. Command Prompt On Windows, this is the application where commands are typed into - a window for execution. + a window for execution. Also see `console `_, + **command line**, or `terminal `_. conda - The package manager for Anaconda. + The package management tool for Anaconda, which allows for easy + installation of Python libraries and other tools into an **environment**. config - Refers to the configuration files and process. + Refers to the configuration files, and related processes that affect how + Jupyter behaves. + + environment + The name for the installed software, configurations, tools, and + `environment variables `_ + that collectively define what capabilities a computer system has and how + it behaves. Missing or incorrect software, configurations or environment variables + can cause software to malfunction, or software development processes to fail. See + `this link `_ + for more information. + + environment variable + See `this wiki link `_ for for information. + + ipynb + The file extension (.ipynb) for saved notebook files, commonly + authored and edited with Jupyter web applications such as + JupyterLab or Jupyter Notebook. It stands for "IPython Notebook". + + IPython + The earliest ancestor of **Project Jupyter**. It began as an improved + interactive Python **REPL**, then expanded to also contain a stored + notebook document format (.ipynb) and related tools, a web based + document authoring and editing tool (IPython Notebook), and more. + After the project became large enough, IPython was split into many + separate projects under the **Project Jupyter** umbrella through + **The Big Split.** + + IPython Notebook + An early ancestor of the Jupyter Notebook application, this was one of + the first web-based applications for authoring and editing computational + notebook documents. + + ipywidgets + A `python package for Jupyter `_ + that allows Notebook applications to create and embed interface components + like sliders or buttons in their notebooks. + + Jovyan + A term for fans of Jupyter and members of the Jupyter community. This term + is `derived from `_ + the astronomical term "Jovian", meaning "Like Jupiter". + + Jupyter + See **Project Jupyter**. Also occasionally used to refer to one of the Jupyter + frontend notebook editing applications (**Jupyter Notebook** or **JupyterLab**) + based on the context it's used in (this ambiguous usage can lead to + confusion, it's better to use the actual name of the application). + + Jupyter Notebook (Application) + A simplified web application for authoring and editing computational + notebooks in the **.ipynb** format (a notebook file is also commonly referred + to as a Jupyter Notebook). + + Jupyter Notebook (File Format) + A common name for a saved **.ipynb** Notebook file. For instance, + "I just made a Jupyter Notebook summarizing our lab results, I can + send it to you later today." + + JupyterLab + A modern web application for authoring and editing interactive + computational notebooks. kernel - A kernel provides programming language support in Jupyter. IPython is + A kernel provides programming language support in Jupyter. **IPython** is the default kernel. Additional kernels include R, Julia, and many more. + Notebook + The generic name for a computational notebook document, such as a saved + .ipynb file format created by JupyterLab. Also sometimes used as a shorthand + to refer to Jupyter Notebook, the notebook editing application. + Notebook Dashboard - The notebook user interface which shows a list of the notebooks, files, - and subdirectories in the directory where the notebook server is - started. + The notebook user interface in the **Jupyter Notebook Application** (see above) + which shows a list of the notebooks, files, and subdirectories in the directory + where the notebook server is started. pip Python package manager. @@ -35,12 +118,26 @@ Glossary Not available in Jupyter. In IPython 3, profiles are collections of configuration and runtime files. + Project Jupyter + The umbrella project for many related tools for interactive computing + with interactive notebooks + REPL - read-eval-print-loop. + Stands for "read-eval-print-loop". An `REPL `_ + is a program that reads user commands and inputs, evaluates them, and prints results for the user to view. + These steps run in a perpetual loop, allowing the user to prototype code, + interact with data, and view results on-the-fly, since the data and code + stay open in memory after evaluation while the REPL is running. terminal - A window used to type in commands to be executed (Linux and OS X). + In modern times, a `terminal `_ refers to a simple text-based program where you type commands for your + computer to run, also commonly called a `console `_. + + The Big Split + An event and effort undertaken around 2015 by **IPython** developers to split up + the then-massive IPython project into a series of smaller, more focused + sub-projects under the Project Jupyter umbrella. widget - A user interface component, similar to a plugin, that allows customized - input, such as a slider. \ No newline at end of file + A user interface component from `ipywidgets `_, + similar to a plugin, that allows customized input, such as a slider. diff --git a/docs/source/index.md b/docs/source/index.md new file mode 100644 index 000000000..ae17b4dba --- /dev/null +++ b/docs/source/index.md @@ -0,0 +1,248 @@ +# Project Jupyter Documentation + +Welcome to the Project Jupyter documentation site. Jupyter is a large umbrella +project that covers many different software offerings and tools, including the +popular [Jupyter Notebook](https://jupyter-notebook.readthedocs.io/en/latest/) +and [JupyterLab](https://jupyterlab.readthedocs.io/en/latest/) web-based +notebook authoring and editing applications. The Jupyter project and its +subprojects all center around providing tools (and [standards](https://docs.jupyter.org/en/latest/#sub-project-documentation)) +for interactive computing with [computational notebooks](#what-is-a-notebook). + +(what-is-a-notebook)= +## What is a Notebook? + +![jupyterlab.png](_static/_images/jupyterlab.png) + +**Pictured:** *A computational notebook document, shown inside JupyterLab* + +> 📘 **Note:** Read [What is Jupyter?](what_is_jupyter) for a detailed look at Jupyter and notebooks. + +A notebook is a shareable document that combines computer code, plain language +descriptions, data, rich visualizations like 3D models, charts, graphs and +figures, and interactive controls. A notebook, along with an editor (like +JupyterLab), provides a fast interactive environment for prototyping and +explaining code, exploring and visualizing data, and sharing ideas with +others. + +## Where do I start? + +Most people begin with Jupyter by installing an editing application that fits +their preferences, like [JupyterLab](https://jupyterlab.readthedocs.io/en/latest/) +or [Jupyter Notebook](https://jupyter-notebook.readthedocs.io/en/latest/), +and making their first notebook document: + +- Jupyter Notebook offers a simplified, lightweight notebook authoring experience +- JupyterLab offers a feature-rich, tabbed multi-notebook editing environment + with additional tools like a customizable interface layout and system console +- And more... read about additional notebook interfaces [here](projects/user-interfaces)! + +You can also develop your own extensions or applications on top of existing Jupyter +software. Check out the subproject sites below for more information. + +## More information + +These are a few high-level topics to help you learn more about the Jupyter community and ecosystem. + +```{list-table} +:class: front_page_table + +* - {doc}`Get started with Jupyter Notebook ` + + Try the notebook + + - {doc}`Community ` + + Sustainability and growth + +* - {doc}`Architecture ` + + What is Jupyter? + + - {doc}`Contributor Guides ` + + How to contribute to the projects + +* - {doc}`Narratives and Use Cases ` + + Narratives of common deployment scenarios + + - {doc}`Release Notes ` + + New features, upgrades, deprecation notes, and bug fixes + +* - {doc}`IPython ` + + An interactive Python kernel and REPL + + - {doc}`Reference ` + + APIs + +* - {doc}`Installation, Configuration, and Usage ` + + Documentation for users + + - {doc}`Advanced ` + + Documentation for advanced use-cases +``` + +## Sub-project documentation + +Individual sub-projects are typically organized around a key feature of the +Jupyter ecosystem, and have their own community, documentation and governance. +Below is a list of documentation for major parts of the Jupyter ecosystem. + +````{grid} 1 1 2 2 +:gutter: 3 + +```{grid-item-card} +User Interfaces +^^^^^^ +* [JupyterLab](https://github.com/jupyterlab/jupyterlab) +* [Jupyter Notebook](https://jupyter-notebook.readthedocs.io/en/latest/) +* [nbclassic](https://github.com/jupyterlab/nbclassic) +* [Jupyter Console](https://jupyter-console.readthedocs.io/en/latest) +* [Qt console](https://qtconsole.readthedocs.io/en/stable) +* [Voilà](https://voila.readthedocs.io/) +``` + +```{grid-item-card} +JupyterHub +^^^^^^ +* [JupyterHub](https://jupyterhub.readthedocs.io/en/latest) +* [Configurable HTTP proxy](https://github.com/jupyterhub/configurable-http-proxy) +* Authenticators: [LDAP](https://github.com/jupyterhub/ldapauthenticator), [OAuth](https://oauthenticator.readthedocs.io/en/latest/), [Native](https://native-authenticator.readthedocs.io/en/latest/), [LTI](https://ltiauthenticator.readthedocs.io/en/latest/) +* Spawners: [sudo](https://github.com/jupyterhub/sudospawner), [Docker](https://jupyterhub-dockerspawner.readthedocs.io/en/latest/), [Kubernetes](https://jupyterhub-kubespawner.readthedocs.io/en/latest/) +* [Zero to JupyterHub](https://zero-to-jupyterhub.readthedocs.io/en/latest/) +* [All JupyterHub Projects...](https://github.com/jupyterhub) +``` + +```{grid-item-card} +Working with Notebooks +^^^^^^ +* [nbclient](https://nbclient.readthedocs.io/en/latest/) - execution +* [nbconvert](https://nbconvert.readthedocs.io/en/latest/) - conversion +* [nbviewer](https://github.com/jupyter/nbviewer/) - viewing +* [nbdime](https://nbdime.readthedocs.io/) - comparing and merging +* [nbgrader](https://nbgrader.readthedocs.io/en/latest/) - grading +* [nbformat](https://nbformat.readthedocs.io/en/latest/) - modification and validation +``` + +```{grid-item-card} +Kernels +^^^^^^ +* [IPython](https://ipython.readthedocs.io/en/stable/) +* [IRkernel](https://irkernel.github.io) +* [IJulia](https://github.com/JuliaLang/IJulia.jl) +* [Xeus kernels](https://xeus.readthedocs.io/en/latest/) +* [Community maintained kernels](https://github.com/jupyter/jupyter/wiki/Jupyter-kernels) +``` + +```{grid-item-card} +IPython +^^^^^^ +* [IPython](https://ipython.readthedocs.io/en/stable/) +* [ipykernel](https://ipython.readthedocs.io/en/stable/) +* [ipyparallel](https://ipyparallel.readthedocs.io/en/latest/) +* [traitlets](https://traitlets.readthedocs.io/en/stable/) +``` + +```{grid-item-card} +Architecture and Specification +^^^^^^ +* [nbformat](https://nbformat.readthedocs.io/en/latest/api.html) - Jupyter Notebook Format +* [jupyter-client](https://jupyter-client.readthedocs.io/en/latest/) - Jupyter Messaging Protocol +* [jupyter-core](https://jupyter-core.readthedocs.io/en/latest/) +* [jupyter-server](https://jupyter-server.readthedocs.io/) +* [jupyterlab-server](https://jupyterlab-server.readthedocs.io/en/stable/) +``` + +```{grid-item-card} +Deployment +^^^^^^ +* [Docker Stacks](https://jupyter-docker-stacks.readthedocs.io/en/latest/) +* [Kernel Gateway](https://jupyter-kernel-gateway.readthedocs.io/en/latest/) +* [Enterprise Gateway](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/) +``` + +```{grid-item-card} +Widgets +^^^^^^ +* [ipywidgets](https://ipywidgets.readthedocs.io/) +* [widget-cookiecutter](https://github.com/jupyter-widgets/widget-cookiecutter/) +* [All Widget Projects...](https://github.com/jupyter-widgets) +``` +```` + +## Table of Contents + +The rest of the documentation on this site covers major use-cases of the Jupyter ecosystem, as well as topics that will help you navigate the various parts of the Jupyter community. +For more in-depth documentation about a specific tool, we recommend checking out that tool's documentation (see the list above). + +(user-docs)= + +```{toctree} +:maxdepth: 2 + +start/index +``` + +(jupyter-using)= + +```{toctree} +:maxdepth: 2 + +use/using +``` + +(jupyter-subprojects)= + +```{toctree} +:maxdepth: 2 + +projects/content-projects +``` + +```{toctree} +:maxdepth: 2 + +community/content-community +``` + +(dev-docs)= + +```{toctree} +:maxdepth: 2 + +contributing/content-contributor +``` + +```{toctree} +:maxdepth: 2 + +reference/content-reference +``` + +## Resources + +```{csv-table} +:header: Site, Description +:widths: 18, 35 + +[Jupyter website](https://jupyter.org), Keep up to date on Jupyter +[IPython website](https://ipython.org), Learn more about IPython +[Jupyter Discourse forum](https://discourse.jupyter.org/), Start here for help and support questions +[Jupyter Accessibility](https://jupyter-accessibility.readthedocs.io/), Accessibility sub-project documentation +[Jupyter mailing list](https://groups.google.com/forum/#!forum/jupyter), General discussion of Jupyter's use +[Jupyter in Education group](https://groups.google.com/forum/#!forum/jupyter-education), Discussion of Jupyter's use in education +[NumFocus](https://www.numfocus.org), "Promotes world-class, innovative, open source scientific software" +[Donate to Project Jupyter](https://jupyter.org/about#donate), Please contribute to open science collaboration and sustainability +``` + + +## Indices and tables + +- {ref}`genindex` +- {ref}`glossary` +- {ref}`search` diff --git a/docs/source/install.rst b/docs/source/install.rst index b0490dea7..50d51f97c 100644 --- a/docs/source/install.rst +++ b/docs/source/install.rst @@ -1,83 +1,77 @@ .. _install: -=========================== -Installing Jupyter Notebook -=========================== +=============== +Install and Use +=============== -.. contents:: Contents - :local: - :depth: 2 +.. NOTE: some links below must have double-underscores to be anonymous if they have the same text -This information explains how to install the Jupyter Notebook and the IPython -kernel. +This page contains information and links about installing and using tools across +the Jupyter ecosystem. Generally speaking, the documentation of each tool is the +place to learn about the best-practices for how to install and use the tool. -Prerequisite: Python --------------------- +Jupyter Notebook Interface +========================== -While Jupyter runs code in many programming languages, **Python** is -a requirement (Python 3.3 or greater, or Python 2.7) for installing -the Jupyter Notebook. +The **Jupyter Notebook interface** is a Web-based application for authoring documents that combine +live-code with narrative text, equations and visualizations. -We recommend using the `Anaconda `_ -distribution to install Python and Jupyter. We'll go through its installation -in the next section. -.. _new-to-python-and-jupyter: +* `GitHub Repo `__ +* `Docs `_ -Installing Jupyter using Anaconda and conda -------------------------------------------- +.. toctree:: + :maxdepth: 1 -For new users, we **highly recommend** `installing Anaconda -`_. Anaconda conveniently -installs Python, the Jupyter Notebook, and other commonly used packages for -scientific computing and data science. + /install/notebook-classic + /use/upgrade-notebook -Use the following installation steps: -1. Download `Anaconda `_. We recommend - downloading Anaconda's latest Python 3 version (currently Python 3.5). +JupyterLab +========== -2. Install the version of Anaconda which you downloaded, following the - instructions on the download page. +**JupyterLab** is a next-generation web-based user interface for Project Jupyter. -3. Congratulations, you have installed Jupyter Notebook. To run the notebook: +* `GitHub Repo `__ +* `Docs `__ +* `Install instructions `__ - .. code-block:: bash - jupyter notebook +JupyterHub +========== - See :ref:`Running the Notebook ` for more details. +**JupyterHub** is a multi-user hub for interactive computing sessions, made for teams and +organizations, and with pluggable authentication and scalability. -.. _existing-python-new-jupyter: +* `GitHub Repo `__ +* `Docs `__ +* `Install instructions `__ -*Alternative for experienced Python users:* Installing Jupyter with pip ------------------------------------------------------------------------ -.. important:: +Jupyter Console +=============== - Jupyter installation requires Python 3.3 or greater, or - Python 2.7. IPython 1.x, which included the parts that later became Jupyter, - was the last version to support Python 3.2 and 2.6. +The **Jupyter Console** is a terminal-based console for interactive computing. -As an existing Python user, you may wish to install Jupyter using Python's -package manager, :term:`pip`, instead of Anaconda. +* `GitHub Repo `__ +* `Docs and Install instructions `_ -.. _python-using-pip: -First, ensure that you have the latest pip; -older versions may have trouble with some dependencies: +Jupyter QtConsole +================= -.. code-block:: bash +The **Jupyter QtConsole** is a Qt application for interactive computing with rich output. - pip3 install --upgrade pip +* `GitHub Repo `__ +* `Docs `__ +* `Install instructions `__ -Then install the Jupyter Notebook using: -.. code-block:: bash +Jupyter Kernels +=============== - pip3 install jupyter +You can install **Jupyter Kernels** to add support for new languages and code behavior. -(Use ``pip`` if using legacy Python 2.) +.. toctree:: -Congratulations. You have installed Jupyter Notebook. See -:ref:`Running the Notebook ` for more details. + /install/kernels diff --git a/docs/source/install-kernel.rst b/docs/source/install/kernels.rst similarity index 73% rename from docs/source/install-kernel.rst rename to docs/source/install/kernels.rst index 9f4e8e0eb..31fab00c9 100644 --- a/docs/source/install-kernel.rst +++ b/docs/source/install/kernels.rst @@ -1,30 +1,28 @@ -============================== -*Optional:* Installing Kernels -============================== - -.. contents:: Contents - :local: - :depth: 2 +================== +Installing Kernels +================== This information gives a high-level view of using Jupyter Notebook with different programming languages (kernels). Are any languages pre-installed? --------------------------------- +================================ Yes, installing the Jupyter Notebook will also install the `IPython `_ :term:`kernel`. This allows working on notebooks using the Python programming language. + How do I install Python 2 and Python 3? ---------------------------------------- +======================================= To install an additional version of Python, i.e. to have both Python 2 and 3 available, see the IPython docs on `installing kernels `_. + How do I install other languages like R or Julia? -------------------------------------------------- +================================================= To run notebooks in languages other than Python, such as R or Julia, you will need to install additional kernels. For more information, see the full @@ -32,7 +30,7 @@ need to install additional kernels. For more information, see the full .. seealso:: - :ref:`Jupyter Projects ` + :doc:`Jupyter Projects ` Detailed installation instructions for individual Jupyter or IPython projects. @@ -42,4 +40,4 @@ need to install additional kernels. For more information, see the full :ref:`Kernels documentation for Jupyter client ` Technical information about kernels. -.. _`list of available kernels`: https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages \ No newline at end of file +.. _`list of available kernels`: https://github.com/jupyter/jupyter/wiki/Jupyter-kernels diff --git a/docs/source/install/notebook-classic.rst b/docs/source/install/notebook-classic.rst new file mode 100644 index 000000000..0304c1d07 --- /dev/null +++ b/docs/source/install/notebook-classic.rst @@ -0,0 +1,83 @@ +================================================= +Installing the classic Jupyter Notebook interface +================================================= + +This section includes instructions on how to get started with **Jupyter Notebook**. +But there are multiple Jupyter user interfaces one can use, based on their needs. +Please checkout the list and links below for additional information and instructions about +how to get started with each of them. + +This information explains how to install the Jupyter Notebook and the IPython +kernel. + +Prerequisite: Python +-------------------- + +While Jupyter runs code in many programming languages, **Python** +is a requirement for installing the Jupyter Notebook. The Python version required +differs between Jupyter Notebook releases (e.g. Python 3.6+ for Notebook v6.3, +and Python 3.7+ for Notebook v7) . + +We recommend using the `Anaconda `_ +distribution to install Python and Jupyter. We'll go through its installation +in the next section. + +.. _new-to-python-and-jupyter: + +Installing Jupyter using Anaconda and conda +------------------------------------------- + +For new users, we **highly recommend** `installing Anaconda +`_. Anaconda conveniently +installs Python, the Jupyter Notebook, and other commonly used packages for +scientific computing and data science. + +Use the following installation steps: + +1. Download `Anaconda `_. We recommend + downloading Anaconda's latest Python 3 version (currently Python 3.9). + +2. Install the version of Anaconda which you downloaded, following the + instructions on the download page. + +3. Congratulations, you have installed Jupyter Notebook. To run the notebook: + + .. code-block:: bash + + jupyter notebook + + See :ref:`Running the Notebook ` for more details. + +.. _existing-python-new-jupyter: + +*Alternative for experienced Python users:* Installing Jupyter with pip +----------------------------------------------------------------------- + +.. important:: + + Jupyter installation requires Python 3.3 or greater, or + Python 2.7. IPython 1.x, which included the parts that later became Jupyter, + was the last version to support Python 3.2 and 2.6. + +As an existing Python user, you may wish to install Jupyter using Python's +package manager, :term:`pip`, instead of Anaconda. + +.. _python-using-pip: + +First, ensure that you have the latest pip; +older versions may have trouble with some dependencies: + +.. code-block:: bash + + pip3 install --upgrade pip + +Then install the Jupyter Notebook using: + +.. code-block:: bash + + pip3 install jupyter + +(Use ``pip`` if using legacy Python 2.) + +Congratulations. You have installed Jupyter Notebook. See +:ref:`Running the Notebook ` for more details. diff --git a/docs/source/locale/en/LC_MESSAGES/architecture.po b/docs/source/locale/en/LC_MESSAGES/architecture.po new file mode 100644 index 000000000..8ce84dd7f --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/architecture.po @@ -0,0 +1,286 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-07-06 16:40+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.8.0\n" + +#: ../../source/architecture/content-architecture.rst:3 +#: ec6ef6528d7a4d5a9e8afbb96f7e0ff2 +msgid "Architecture" +msgstr "" + +# cc1b649f66b949ebb3984ea361c9ee45 +#: ../../source/architecture/content-architecture.rst:5 +#: 5dff249b734d4781bd740d49e81f989d +msgid "**A high level visual overview of project relationships**" +msgstr "" + +# 8ce5c1bb3b244604b361cd2384066f68 +#: ../../source/architecture/content-architecture.rst:15 +#: c6ca719d9a27496ea866661e20f36ca2 +msgid "How IPython and Jupyter Notebook work" +msgstr "" + +# 242c15d658d64a13a2b8b13502845298 +#: ../../source/architecture/content-architecture.rst:18 +#: 7994f223f78e4a908cda70a3084be5eb +msgid "Contents" +msgstr "" + +# a7b9fc6771f845528e8f7135c51754fa +#: ../../source/architecture/content-architecture.rst:21 +#: 5c2a67c9df3841df8cbadacaf8eea24b +msgid "Abstract" +msgstr "" + +# 3b9b38491da4493b95225b77bcd32438 +#: ../../source/architecture/content-architecture.rst:22 +#: b982fc7cf3ca4774afad6cbb3194f0df +msgid "" +"This section focuses on IPython and Jupyter notebook and how they " +"interact. When we discuss ``IPython``, we talk about two fundamental " +"roles:" +msgstr "" + +# 676993980a9e4a9082f9f313e09af108 +#: ../../source/architecture/content-architecture.rst:25 +#: 07c6da067ceb4475b93c18fe91352903 +msgid "Terminal IPython as the familiar REPL" +msgstr "" + +# 5164fcd91a8a4700ac734562245773ad +#: ../../source/architecture/content-architecture.rst:26 +#: 00e503be44f941ef906f17278580f866 +msgid "" +"The IPython kernel that provides computation and communication with the " +"frontend interfaces, like the notebook" +msgstr "" + +# e79b4b9cf0d4461e8c91e35c54941346 +#: ../../source/architecture/content-architecture.rst:29 +#: 8186366605cb484a999a75c3cc8a868d +msgid "" +"Jupyter Notebook and its flexible interface extends the notebook beyond " +"code to visualization, multimedia, collaboration, and more." +msgstr "" + +# f0e8484a13374e5ba11bc5673feecc30 +#: ../../source/architecture/content-architecture.rst:33 +#: b00f6803e5ab45138afd47655a1d14cd +msgid "Terminal IPython" +msgstr "" + +# d52946417b8a4a04a551622ce78e0c78 +#: ../../source/architecture/content-architecture.rst:35 +#: 4c678061b44a46f1a9a5103cb5983bf0 +msgid "" +"When you type ``ipython``, you get the original IPython interface, " +"running in the terminal. It does something like this::" +msgstr "" + +# 9c51878d67554820815080da49295cb3 +#: ../../source/architecture/content-architecture.rst:42 +#: f8c7332f2e27480c9a30db59fe5f35e7 +msgid "" +"Of course, it's much more complex, because it has to deal with multi-line" +" code, tab completion using :mod:`readline`, magic commands, and so on. " +"But the model is like code example: prompt the user for some code, and " +"when they've entered it, execute it in the same process. This model is " +"often called a :term:`REPL`, or Read-Eval-Print-Loop." +msgstr "" + +# 6948d86fd4fd47a1a4ca54d29e72d46e +#: ../../source/architecture/content-architecture.rst:49 +#: b762294ac7bd43c28c3a5db8b92dceae +msgid "The IPython Kernel" +msgstr "" + +# 61f9b43b0f3148a1b6c8c770dbe95970 +#: ../../source/architecture/content-architecture.rst:51 +#: 863961ccd061429e8f19a6e5074808ad +msgid "" +"All the other interfaces —- the Notebook, the Qt console, ``ipython " +"console`` in the terminal, and third party interfaces —- use the IPython " +"Kernel. The IPython Kernel is a separate process which is responsible for" +" running user code, and things like computing possible completions. " +"Frontends, like the notebook or the Qt console, communicate with the " +"IPython Kernel using JSON messages sent over `ZeroMQ " +"`_ sockets; the protocol used between the frontends " +"and the IPython Kernel is described in :ref:`jupyterclient:messaging`." +msgstr "" + +# 6560f963da914c78b12c61e8795a9852 +#: ../../source/architecture/content-architecture.rst:60 +#: 1c4f192d64474b68ab0dd36ba1808af5 +msgid "" +"The core execution machinery for the kernel is shared with terminal " +"IPython:" +msgstr "" + +# b5bd0a2f608542fe92f8b57ddcb9ea7b +#: ../../source/architecture/content-architecture.rst:64 +#: 738c770480274d05931c2739c47a1161 +msgid "" +"A kernel process can be connected to more than one frontend " +"simultaneously. In this case, the different frontends will have access to" +" the same variables." +msgstr "" + +# 59dd6f3fbb4a46008c898b307aec5a25 +#: ../../source/architecture/content-architecture.rst:69 +#: b955aaa8d0c84f6196f56b6ca5cd91ab +msgid "" +"This design was intended to allow easy development of different frontends" +" based on the same kernel, but it also made it possible to support new " +"languages in the same frontends, by developing kernels in those " +"languages, and we are refining IPython to make that more practical." +msgstr "" + +# e35918a2fb124784a83c135812faf800 +#: ../../source/architecture/content-architecture.rst:74 +#: fea7ae3d8abe4570bfe8b08851c97a46 +msgid "" +"Today, there are two ways to develop a kernel for another language. " +"Wrapper kernels reuse the communications machinery from IPython, and " +"implement only the core execution part. Native kernels implement " +"execution and communications in the target language:" +msgstr "" + +# 3395f44193b54f5cb9b9d380fa4a16bd +#: ../../source/architecture/content-architecture.rst:81 +#: 8bc10d77503c4406a2c52559db662207 +msgid "" +"Wrapper kernels are easier to write quickly for languages that have good " +"Python wrappers, like `octave_kernel " +"`_, or languages where it's " +"impractical to implement the communications machinery, like `bash_kernel " +"`_. Native kernels are likely " +"to be better maintained by the community using them, like `IJulia " +"`_ or `IHaskell " +"`_." +msgstr "" + +# 59d8323c382a4adeb3d622424943b708 +#: ../../source/architecture/content-architecture.rst:91 +#: bafbf88b8f384a6da2f55bad481691bb +msgid ":ref:`jupyterclient:kernels`" +msgstr "" + +# 3418914ee39240879155089a0b29a69e +#: ../../source/architecture/content-architecture.rst:93 +#: b37db92f50fd411facaa691f43e2b01a +msgid ":ref:`Kernels `" +msgstr "" + +# 4866548d799b4cfc95159d7494d66afb +#: ../../source/architecture/content-architecture.rst:96 +#: 0a31ea6c9fa04484a22762a82f7ee84b +msgid "Notebooks" +msgstr "" + +# f414110d9cde4b048d6d4d0c65f274dd +#: ../../source/architecture/content-architecture.rst:98 +#: 039af9e76a8f4426bb7e86c0dd4c6b0a +msgid "" +"The Notebook frontend does something extra. In addition to running your " +"code, it stores code and output, together with markdown notes, in an " +"editable document called a notebook. When you save it, this is sent from " +"your browser to the notebook server, which saves it on disk as a JSON " +"file with a ``.ipynb`` extension." +msgstr "" + +# ce4a6fb377344df295e9512b1d36743c +#: ../../source/architecture/content-architecture.rst:106 +#: b45edaf8b20f4e3b985b0cfbffbd3842 +msgid "" +"The notebook server, not the kernel, is responsible for saving and " +"loading notebooks, so you can edit notebooks even if you don't have the " +"kernel for that language—you just won't be able to run code. The kernel " +"doesn't know anything about the notebook document: it just gets sent " +"cells of code to execute when the user runs them." +msgstr "" + +# 9041dc2c7e0b46e19e1694f6bb081592 +#: ../../source/architecture/content-architecture.rst:113 +#: 3ad3abba24b34dd786857f47b2260e67 +msgid "Exporting notebooks to other formats" +msgstr "" + +# dedd7458edfc44a99f423e2a9b8e1d93 +#: ../../source/architecture/content-architecture.rst:115 +#: 183a5c0a19b24ab381bb94185982dbca +msgid "" +"The Nbconvert tool in Jupyter converts notebook files to other formats, " +"such as HTML, LaTeX, or reStructuredText. This conversion goes through a " +"series of steps:" +msgstr "" + +# 082ebb9d5777479da8f71672f538c484 +#: ../../source/architecture/content-architecture.rst:121 +#: 736107be7a364e268222ade192c0330e +msgid "" +"Preprocessors modify the notebook in memory. E.g. ExecutePreprocessor " +"runs the code in the notebook and updates the output." +msgstr "" + +# c6be8db7ca164f379d97800723004956 +#: ../../source/architecture/content-architecture.rst:123 +#: 40fda823ef8242f298c4477e5b46689b +msgid "" +"An exporter converts the notebook to another file format. Most of the " +"exporters use templates for this." +msgstr "" + +# 9de2fa198489488fa316b950d1228fa3 +#: ../../source/architecture/content-architecture.rst:125 +#: d3a245f8328e42698ed632da34773808 +msgid "Postprocessors work on the file produced by exporting." +msgstr "" + +# e00d7f3b870a40879882ee53ed417463 +#: ../../source/architecture/content-architecture.rst:127 +#: 5d8438de7e8c4df9b2f180886a010a7a +msgid "" +"The `nbviewer `_ website uses nbconvert " +"with the HTML exporter. When you give it a URL, it fetches the notebook " +"from that URL, converts it to HTML, and serves that HTML to you." +msgstr "" + +# e30efeea3614465f95ff49220796d182 +#: ../../source/architecture/content-architecture.rst:132 +#: c20c615c0a8048d9b784e60545a2d163 +msgid "IPython.parallel" +msgstr "" + +# 074d0dac254c44b58ea96c7b4a451d27 +#: ../../source/architecture/content-architecture.rst:134 +#: 8a275f1d59d742449a681c8dfed6ebca +msgid "" +"IPython also includes a parallel computing framework, `IPython.parallel " +"`_. This allows you to " +"control many individual engines, which are an extended version of the " +"IPython kernel described above." +msgstr "" + +# 0bc823304e0d4ab39f2774b29044df9b +#~ msgid "Architecture Guides" +#~ msgstr "" + +# 0118a72a2b1e4c14800c1c3dd77b6c4e +#~ msgid "A Visual Overview of Projects" +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/community.po b/docs/source/locale/en/LC_MESSAGES/community.po new file mode 100644 index 000000000..8a25b959a --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/community.po @@ -0,0 +1,6660 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2021-05-03 22:07+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.9.1\n" + +#: ../../source/community/community-call-notes/2019-april.md:1 +#: f6b13568005a48d296b6a09003bdf685 +msgid "All-Jupyter Community Video Call - April 2019" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:3 +#: a8de79b2ea2049fa8ee1482c6b151f8b +msgid "" +"**Date:** 30 April 2019 at 9am PST (your " +"[timezome](http://arewemeetingyet.com/Los%20Angeles/2019-04-30/09:00/Jupyter%20Community%20Call))" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:5 +#: ../../source/community/community-call-notes/2019-march.md:5 +#: 38d1854a612b4402992054958c5ffcc7 5d0a134ca0c2403f8ccb7677771b3e5d +msgid "**Video-conference link:** https://calpoly.zoom.us/my/jupyter" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:8 +#: ../../source/community/community-call-notes/2019-march.md:9 +#: 2004a16179d14cb39f617a58c0a35088 77408fbd8dad4ff684552e5f279b9a98 +msgid "Welcome to the Team Meeting" +msgstr "" + +# 04d5ac5c03974dc3ad3024b473dd04b9 +# f796eb5b94c1489a9a5078a95e84a502 +# 678a64e0a30e4d9e8e37391ffb59c761 +#: ../../source/community/community-call-notes/2019-april.md:10 +#: ../../source/community/community-call-notes/2019-march.md:11 +#: 1c5bbdb39bca44559ea664543eb04b83 5511264bbe9045039d7e78ec5ea03cf0 +msgid "Hello!" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:12 +#: ../../source/community/community-call-notes/2019-march.md:13 +#: ../../source/community/community-call-notes/2019-may.md:14 +#: 1f7a774cabe648da8e30ed1c426fe15b 26ca44ebd9e7441686fbc29cc936dd80 +#: 5c8f76514ee6482e82150520b555c7aa +msgid "" +"The purpose of these monthly video conference calls is to share and " +"demonstrate the awesome things happening in Jupyter community. We invite " +"**anyone** to present their work, engage in discussion, or just sit in " +"and listen. Whether you have a new [lab " +"extension](https://github.com/jupyterlab) you've created, a new " +"[jupyterhub deployment](https://github.com/jupyterhub) you're excited " +"about, or an [nteract papermill](https://github.com/nteract) pipeline " +"powering your business, we'd love to hear about it! And, we'll record " +"and publish these calls on YouTube for anyone unable to attend." +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:14 +#: ../../source/community/community-call-notes/2019-august.md:15 +#: ../../source/community/community-call-notes/2019-june.md:17 +#: ../../source/community/community-call-notes/2019-march.md:15 +#: ../../source/community/community-call-notes/2019-may.md:16 +#: ../../source/community/community-call-notes/2019-september.md:13 +#: ../../source/community/community-call-notes/2020-december.md:17 +#: ../../source/community/community-call-notes/2020-november.md:19 +#: ../../source/community/community-call-notes/2021-april.md:18 +#: ../../source/community/community-call-notes/2021-february.md:18 +#: ../../source/community/community-call-notes/2021-january.md:19 +#: ../../source/community/community-call-notes/2021-march.md:18 +#: 0480118c832449bbbcbcc21bdbad898b 091902f7c75249829a9520f7847c548c +#: 196fa5ff82bc410683dffae863f71866 1da2877e0ebd4846a365d6b6b33ba667 +#: 1e922a13d09f4382b4f8257c67658b24 365c9acb7f7c4791b0e4166088cc4b04 +#: 709dc6725f954189ad981726d78b475b 7d122a8978eb4c14a802fd159349f616 +#: b853496e3e4b4645add91d5591223a1f cd2eaa84e6a84cbdbdaccbd09cf81144 +#: e90f3ac22a6548faadb41ba2ebd25963 fd8cfa7a9e1244dda8cc0cf28b246a0a +msgid "" +"For more discussion on the format of these calls, see the thread " +"[here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-team-" +"meetings/423)." +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:16 +#: ../../source/community/community-call-notes/2019-august.md:17 +#: ../../source/community/community-call-notes/2019-june.md:19 +#: ../../source/community/community-call-notes/2019-march.md:17 +#: ../../source/community/community-call-notes/2019-may.md:18 +#: ../../source/community/community-call-notes/2019-september.md:15 +#: ../../source/community/community-call-notes/2020-november.md:21 +#: ../../source/community/community-call-notes/2021-april.md:20 +#: ../../source/community/community-call-notes/2021-february.md:20 +#: ../../source/community/community-call-notes/2021-january.md:21 +#: ../../source/community/community-call-notes/2021-march.md:20 +#: 240b82a3b4034c8099e70d74ae936306 52cfabdbf6694249850159afe6ac8745 +#: 5a411b67a0cf481d8a05aec445eb7d78 6715339e794748c9b3ba17f7673ef144 +#: 6e37484af5f3499584da337251eb6189 8d2e53cf33b54baf9adfb4c1aa90a54e +#: a8478c97b18d4b4e804fe445b26d461f b32ca60d17cf4ed6b3d2e3381a2dc6a0 +#: c341a64acb894c678ac973ea4c8b72b6 fa10d7dee44c4ee9b60bdedc4c3a5a72 +#: ff026d284b464c11bef99f2ee06ab5b9 +msgid "Short reports, celebrations, shout-outs" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:18 +#: ../../source/community/community-call-notes/2019-march.md:19 +#: ../../source/community/community-call-notes/2019-may.md:20 +#: 18ca25b54eb04d2cb21dd5878cdf21b4 623982a0f476414fb0d00bdd8ebd137a +#: f7df621f8484475c905fac6dd3ea7bcb +msgid "" +"This is a place to make *short* announcements (without a need for " +"discussion). This is also a great place to give shout-outs to " +"contributors! We’ll read through these at the beginning of the meeting." +msgstr "" + +# f56b988ddfe8483d9fb92075e202af10 +#: ../../source/community/community-call-notes/2019-april.md:20 +#: b2bb8417f1b543a18901500552b3985b +msgid "" +"[x] Shout-out to @GrahamDumpleton for continued well-researched " +"improvements to security (e.g., https://github.com/jupyter/docker-" +"stacks/pull/845) [name=Peter Parente]" +msgstr "" + +# 342129d844b54290a52b48c17b0b4ee8 +#: ../../source/community/community-call-notes/2019-april.md:21 +#: 731cf8fe2c4d49cab48f321a3a8cd4cb +msgid "" +"[x] Some initial work on enabling Jupyter documentation translation is " +"happening in https://github.com/jupyter/docker-stacks/issues/827. If you " +"would like to contribute a translation, review one in progress, or help " +"document the process itself, please reach out in the issue. Thanks to " +"@michiboo (Micky), @Nico769 (Nicola), and @Allanfs (Allan) for starting " +"translations! [name=Peter Parente]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:22 +#: df9b858f6c50474195a84bf9d2177d42 +msgid "" +"[x] [Work](https://discourse.jupyter.org/t/aws-integration-work/864) is " +"being done to use BinderHub fully in AWS (hosted docker registry, ECR, " +"and hosted git repository, CodeCommit are the current areas). [name=Chico" +" Venancio]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:23 +#: 338e2ae845654a1e98747cdbec8cb377 +msgid "" +"[x] JupyterLab 1.0.0a3 has been released since our last call. There are a" +" ton of updates. One thing I specifically want to give a shout out to is " +"the document search feature that Andrew Schlaepfer built which allows " +"building custom search functionality for different document types. " +"Install the new version to take it for a spin: `pip install --pre " +"jupyterlab` [name=Darian]" +msgstr "" + +# 1b353e5d8b4543e597ddbea86d2c2f1a +#: ../../source/community/community-call-notes/2019-april.md:24 +#: 4054d8dbae114fdf9de4afe796cac0e7 +msgid "" +"[x] RISE 5.5.0 was released, more info about the release in this " +"blogpost: http://damianavila.github.io/blog/posts/rise-550-is-out.html " +"[name=Damián]" +msgstr "" + +# e287ac4ceadf460a8f58ee7d52ff0d60 +#: ../../source/community/community-call-notes/2019-april.md:25 +#: 04b5079e47c44d899793aa05aac7f313 +msgid "" +"[x] A big shout-out to Paul Ivanov for helping organize a \"Jupyter Open " +"Studio Day\" at Bloomberg in SF. Lots of great people came, shared ideas," +" learned, and generally celebrated open source stuff! [name=Chris H (but " +"I won't be able to attend the meeting)]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:26 +#: 6877e6c058c04052b2e12fff7d67b11c +msgid "" +"[x] (a few quick shout-outs from Chris) Papermill 1.0 is released! " +"Congrats to the nteract community for releasing papermill 1.0, a tool for" +" parametizing / pipelining notebooks. [See the Discourse for some more " +"links](https://discourse.jupyter.org/t/release-of-papermill-1-0/875). " +"[name=Chris H (but I won't be able to attend the meeting)]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:27 +#: 026e765fd2e0491ea480867ca24ce70b +msgid "" +"[x] Many thanks to @KirstieJane and @betatim for improving the " +"contributing documentation in repo2docker ([link to one PR on " +"this](https://github.com/jupyter/repo2docker/pull/655)) [name=Chris H " +"(but I won't be able to attend the meeting)]" +msgstr "" + +# ea2c2e8e179b42b9801baf7ef40246e8 +#: ../../source/community/community-call-notes/2019-april.md:28 +#: 918ad7e515b4432094c2f4ace1c75c00 +msgid "" +"[x] IPython 7.5 out ! (mostly bugfixes) [name=Matthias, at airport so " +"will stay muted] (Shout out to Matthias for this too!)" +msgstr "" + +# 28ff4aa780564751a428ff478f2ab1b8 +#: ../../source/community/community-call-notes/2019-april.md:29 +#: 091a6b610bdd4f3cb6118ba63ba54bef +msgid "" +"[x] Matthias,Paul,Carol... are at PyCon for a tutorial (Thursday), and " +"have Jupyter stickers ! [name=Matthias, at airport so will stay muted]" +msgstr "" + +# 27ac1fb35460431682dceb89c631762b +#: ../../source/community/community-call-notes/2019-april.md:30 +#: 2d93f8a77f47443c889e65aa3dcfa334 +msgid "[ ] add item here [name=add your name]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:32 +#: ../../source/community/community-call-notes/2019-august.md:27 +#: ../../source/community/community-call-notes/2019-june.md:36 +#: ../../source/community/community-call-notes/2019-march.md:30 +#: ../../source/community/community-call-notes/2019-may.md:28 +#: ../../source/community/community-call-notes/2019-september.md:25 +#: ../../source/community/community-call-notes/2020-december.md:32 +#: ../../source/community/community-call-notes/2020-november.md:27 +#: ../../source/community/community-call-notes/2021-april.md:26 +#: ../../source/community/community-call-notes/2021-february.md:28 +#: ../../source/community/community-call-notes/2021-january.md:34 +#: ../../source/community/community-call-notes/2021-march.md:26 +#: 06589dee1a03449186d27d6f8cd60022 0ea1c897c8304d03aee2afeee2411509 +#: 295f8f33fb1b4d5a97d0c6d0e3a8b32c 34269274c23241269697dcde2460a1a5 +#: 617f7279286e44ca80561d96a25b5403 773007bb78324c0f843ad37ddda554bf +#: 9e0174bf1fb4473faf0f3f1184828e4c a2d647a33a304d5a983b8cba1236d217 +#: b36faebdac4f423f960abcbfe646e832 b7dffa08645d48a4954aafe88e27c877 +#: d3281602f5984beda4d0312b6afc74fa f39df02613ef4fe5b52f503005ee643d +msgid "Agenda Items" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:34 +#: ../../source/community/community-call-notes/2019-may.md:30 +#: 31630cd94204455e86d9f22e9f7e367b 559b81303a5442d5829fc5c259a90e57 +msgid "" +"Add your potential agenda item here **24 hours before** the meeting at " +"the latest. We will reorganize the agenda so that it fits in the 60m " +"meeting slot." +msgstr "" + +# 41fe758403a54a7d9e589ea9a0083169 +#: ../../source/community/community-call-notes/2019-april.md:36 +#: 93c457244cbf47858dc4c54b2c14354d +msgid "[x] Updates from the nteract project [name=Safia Abdalla]" +msgstr "" + +# 06fa470ac82f40eb808455fae428d51d +#: ../../source/community/community-call-notes/2019-april.md:37 +#: a9dea372615243f590db3b9638609eb1 +msgid "New release of the cross-platform nteract desktop app is out." +msgstr "" + +# e8fd51d1b3924fe9bb344b5c2dcf9afc +#: ../../source/community/community-call-notes/2019-april.md:38 +#: 3cdfc17abd69483d8f58abc970f6671a +msgid "papermill v1.0 is released." +msgstr "" + +# 7d625dd6e5f84dc58b42d77493039790 +#: ../../source/community/community-call-notes/2019-april.md:39 +#: 833ff77a5b04431994aa03e64e919c6d +msgid "" +"[x] Jupyter at the University of Edinburgh, a walkthrough of the Noteable" +" service [name=James Slack]" +msgstr "" + +# 9d5bb4cbc8b24cd785c0c8daf9818472 +#: ../../source/community/community-call-notes/2019-april.md:40 +#: 93bc53e7f2c948c8b1a4061abc4aac1d +msgid "Overview of what's happening at University of Edinburgh" +msgstr "" + +# 0c8d73e860a3443b9486206bb2c56814 +#: ../../source/community/community-call-notes/2019-april.md:41 +#: 6e0a6aba66c14e479d1d40e236ab29ce +msgid "Large support teams." +msgstr "" + +# a314be8356e2421a979988b289a33f6c +#: ../../source/community/community-call-notes/2019-april.md:42 +#: 902e860efd394fa694a1bf2c3dd08077 +msgid "Very open mindset." +msgstr "" + +# 94f5bfff31c34f848386b41a3fb763ae +#: ../../source/community/community-call-notes/2019-april.md:43 +#: 8b47130ea77e41c9bbd32a364f2159ec +msgid "http://open.ed.ac.uk/" +msgstr "" + +# 9501a1c240b6400a9b3bf92f6ae0dc29 +#: ../../source/community/community-call-notes/2019-april.md:44 +#: 7322d7db33804ff39830a594e55deb25 +msgid "How Jupyter came to the University" +msgstr "" + +# 6804ebef6d9943d0b6f237e86f010b3a +#: ../../source/community/community-call-notes/2019-april.md:45 +#: 020da4a358074cda963919c3234d55be +msgid "Small scale adoption to start" +msgstr "" + +# cb445feb597649daad29ef6a17eba633 +#: ../../source/community/community-call-notes/2019-april.md:46 +#: 2abf7831446b4a2bbbbd1117ffe62a24 +msgid "Students were installing Jupyter on university computers." +msgstr "" + +# db381499ea9a4bd09e7f37a1f42f4ddc +#: ../../source/community/community-call-notes/2019-april.md:47 +#: 58ebbb1968a94c07be4246a1e889443d +msgid "Make Jupyter a shared central service." +msgstr "" + +# aa926fa3cf8a485e8b15457069062686 +#: ../../source/community/community-call-notes/2019-april.md:48 +#: dcdceb182b8f48ef8c20116541e92559 +msgid "JupyterHub service university wide for use in education." +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:49 +#: d4de7cafd6d04e518a8b9537c22b844b +msgid "Pilot phase of [Noteable](https://noteable.edina.ac.uk/)." +msgstr "" + +# 7c466276d697401d98bc9915ec546e7f +#: ../../source/community/community-call-notes/2019-april.md:50 +#: cc04f5a1dc5d443cbe90491a7b42af5d +msgid "6 courses with 6 different schools (~600 students)." +msgstr "" + +# 18f0783d9cf54a60a2073ed2a5812aaa +#: ../../source/community/community-call-notes/2019-april.md:51 +#: e1ab8a8992394a2baf8f26021266e7ea +msgid "Political science, art, computer science..." +msgstr "" + +# f77898eab2664628b6681b7952a5ba87 +#: ../../source/community/community-call-notes/2019-april.md:52 +#: cf83e9ae75be4684ac28847173fe97c7 +msgid "Integrated with nbgrader." +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:53 +#: 75207649f7724730944135eced65c12c +msgid "" +"[Jupyter Community Hackathon on NBGrader in " +"Edinburgh](https://thinking.is.ed.ac.uk/noteable/2018/12/07/jupyter-" +"community-workshop-proposal-nbgrader-and-jupyter-in-teaching/)." +msgstr "" + +# da7b6708b6424495947e1379778d2cd1 +#: ../../source/community/community-call-notes/2019-april.md:54 +#: d6778174ca2c4b9788fe7673b932a9a3 +msgid "Questions and comments:" +msgstr "" + +# aaba393bb774486f81ce54c99487da09 +#: ../../source/community/community-call-notes/2019-april.md:55 +#: 3a61df280dd84e40b7f45c094960fb80 +msgid "" +"Connections or interactions with Canadian group? https://syzygy.ca " +"[name=Lindsey Heagy]" +msgstr "" + +# a24cd6437e3b40d1bebe68f79791f705 +#: ../../source/community/community-call-notes/2019-april.md:56 +#: d6c28af8d1cc4a43abdf2a1f4eb70bd5 +msgid "Is this running in the cloud or university server? [name=Anton Akhmerov]" +msgstr "" + +# 1a55b9feb09647a5b322a4ac52b1c77a +#: ../../source/community/community-call-notes/2019-april.md:57 +#: 8ef8d6fb70994b72a836a8d8e4a08c46 +msgid "University server" +msgstr "" + +# c92677aeebe3404099c7a6d5099efd1a +#: ../../source/community/community-call-notes/2019-april.md:58 +#: 2fb211642b2d4dc1ae261dc8b08c4bc5 +msgid "Have you explored Binderhub? [name=Chico Vernancio]" +msgstr "" + +# 43fd1f8f66b34ed285a4098b2dd76bcf +#: ../../source/community/community-call-notes/2019-april.md:59 +#: 13add84d938e4b388c8a71241c6f77ff +msgid "" +"BinderHub now can run with \"auth\" and persistent storage, see " +"https://github.com/jupyterhub/binderhub/issues/794 for more details and a" +" live demo (ask @betatim if you have more questions)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:60 +#: 785428f94cba448db5bda8742cc31a80 +msgid "" +"[ ] Introducing the rewrite of [jupyter-sphinx](https://github.com" +"/jupyter-widgets/jupyter-sphinx/) (example " +"[here](https://adaptive.readthedocs.io/en/latest/tutorial/tutorial.Learner2D.html))" +" and a discussion about markup format in the notebooks " +"(https://github.com/jupyter/nbformat/issues/80) [name=Anton Akhmerov]" +msgstr "" + +# 5a69fd142cc74281a51d934287eb223d +#: ../../source/community/community-call-notes/2019-april.md:61 +#: 492f70ea71cc43d7a37b18933d295d98 +msgid "Publishing documents with complex content and computed output." +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:63 +#: 2a6919649eb64bdf852120f7c9a3af04 +msgid "" +"Questions/Comments: - [name=matthias (can't speak)]: I'd love to " +"merge that with ipython built-in sphinx-ext, /(deprecate sphinx-ext " +"potentially as it's not well maintained ([sphix-ext " +"docs](https://ipython.readthedocs.io/en/stable/sphinxext.html))" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:66 +#: 53fad81131694c148581ecc7b6dad5b4 +msgid "" +"[ ] Quantum Chemistry Database exploration with Jupyter through the " +"[QCArchive project](https://qcarchive.molssi.org), [name=Daniel Smith]." +msgstr "" + +# fba7c56c8b914ed9b43b5da90ea9ed61 +#: ../../source/community/community-call-notes/2019-april.md:67 +#: 98a7456b38f644fd806a6d00b00fb3e0 +msgid "The Molecular Sciences Software Institute" +msgstr "" + +# 706fd60e9f4a49a1bd39dba670195b24 +#: ../../source/community/community-call-notes/2019-april.md:68 +#: c5ac9582c5bf4b16aaaec5af10a02844 +msgid "NSF funded." +msgstr "" + +# 0014fb3a1de94a3bb3f32f1d8c1ddff8 +#: ../../source/community/community-call-notes/2019-april.md:69 +#: ea926eb928784575b6f125341eeec7db +msgid "" +"Designed to serve and enhance software development efforts of broad field" +" of computational molecular science." +msgstr "" + +# beee5940e94347c79137c16f548d9198 +#: ../../source/community/community-call-notes/2019-april.md:70 +#: d3731a0effff488da013ec6bd54a15ee +msgid "8 universities represented on Board of Directors" +msgstr "" + +# c1d969e8856e4171af4793fb45ca342a +#: ../../source/community/community-call-notes/2019-april.md:71 +#: 9037bcd3fb08464cabfeb1293b1620b2 +msgid "Github org: https://github.com/MolSSI" +msgstr "" + +# 2b1e1636b7af499ab63139437e2fe6c0 +#: ../../source/community/community-call-notes/2019-april.md:72 +#: c90822cde57e49bcbb18f44dc6e09290 +msgid "https://molssi.org" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:73 +#: e8d2e95467324aa288e1e6f3a5a57bf8 +msgid "[QCFractal](https://github.com/MolSSI/QCFractal)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:74 +#: 3dbe4f582e7946d6b19c0c27c328103e +msgid "" +"Join our " +"[Slack](https://join.slack.com/t/qcdb/shared_invite/enQtNDIzNTQ2OTExODk0LWM3OTgxN2ExYTlkMTlkZjA0OTExZDlmNGRlY2M4NWJlNDlkZGQyYWUxOTJmMzc3M2VlYzZjMjgxMDRkYzFmOTE)" +" to get involved." +msgstr "" + +# 65d936b5b5a546c89af03964b32af243 +#: ../../source/community/community-call-notes/2019-april.md:75 +#: 14fc6ddcfe794a6fb5b876855f5ff76a +msgid "Questions/comments:" +msgstr "" + +# f85773a2fed94fd991a59fdd19bdfa73 +#: ../../source/community/community-call-notes/2019-april.md:76 +#: ae852a0cb6894e2c80604a19ee7f152b +msgid "Is this user created content or hostesd content?" +msgstr "" + +# 4aa7080662664070b2e65614c6546305 +#: ../../source/community/community-call-notes/2019-april.md:77 +#: e39ba0a212f84084b35899f98bd1503b +msgid "Completely user created." +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:79 +#: 8cad47ea7c0f48a9aea88c5ab5651647 +msgid "" +"[ ] May 13 & 14 [W4A Hackathon on Accessibility of " +"JupyterLab](https://groups.google.com/forum/#!topic/jupyter/trUVgNj0deU)" +msgstr "" + +# 2f177e7a343c43f5bcb6dcc312ec9f8f +#: ../../source/community/community-call-notes/2019-april.md:80 +#: 77d0c97408374622a3a3b477f31d4ff5 +msgid "[ ] Add your item here [name=and your name]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:82 +#: c5261dbf5d0e4d8d88acdd433057aaa4 +msgid "University of Edinburgh materials and contact:" +msgstr "" + +# 9a571f3c56554fc7b30eb83326ced2d7 +#: ../../source/community/community-call-notes/2019-april.md:84 +#: a8b3d74966f2462fa8ca154844dc9cee +msgid "Contact james.slack@ed.ac.uk" +msgstr "" + +# 7b188d49f40445a691eebb5287c9560a +#: ../../source/community/community-call-notes/2019-april.md:85 +#: 309fb8f84df9410faacfcde07db9538f +msgid "Noteable - https://noteable.edina.ac.uk/" +msgstr "" + +# f154c819041f4459a541d165a0d61497 +#: ../../source/community/community-call-notes/2019-april.md:86 +#: a1aeb4751c854f78b2225cfb26e212fb +msgid "Blog https://thinking.is.ed.ac.uk/noteable/" +msgstr "" + +# d5f1193dadf44db29f8e5e9a0756ffbd +#: ../../source/community/community-call-notes/2019-april.md:87 +#: 0ec70e41d8de4c9c847959cef9caf36b +msgid "nbgrader Hackathon - http://edin.ac/2SGmzNu" +msgstr "" + +# 0335a1ec922147428bcc1c61208a6cd4 +#: ../../source/community/community-call-notes/2019-april.md:88 +#: 564acd1aedf843afb627871deb217959 +msgid "Presentation - https://edin.ac/2PBJc1T" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:90 +#: ../../source/community/community-call-notes/2019-march.md:85 +#: 0fcee0b7528f428e8ed68331b84fee99 e4d202d0285d436980e7763645c365b7 +msgid "In Attendance" +msgstr "" + +# 42562fcb34704715bff217a5180cd439 +#: ../../source/community/community-call-notes/2019-april.md:92 +#: 0054a00d082344369c3de31c1900cc22 +msgid "Name / Institution / Github Handle" +msgstr "" + +# d09bd84909e94d15ab95533d4d7562ba +#: ../../source/community/community-call-notes/2019-april.md:94 +#: 975f7f97a06f4a85bf1a17a57435de8b +msgid "Zach / Jupyter Cal Poly / @Zsailer" +msgstr "" + +# be287aa0663642cea613afb34c63e192 +#: ../../source/community/community-call-notes/2019-april.md:95 +#: e8c953ea484d40f18b27d6f01b077408 +msgid "Pete / Thorn / @parente" +msgstr "" + +# c51c4c8e0e0e4c028df48691f7291065 +#: ../../source/community/community-call-notes/2019-april.md:96 +#: 51867cfe62fc483ca1ea943ce2369c1b +msgid "James Slack / University of Edinburgh / @jamesaslack" +msgstr "" + +# 55f5f19a346a4db2a9bc86b3e1e3dcc4 +#: ../../source/community/community-call-notes/2019-april.md:97 +#: 7d44ed1c5f4f41ffb3e7aec2e996227c +msgid "Anton Akhmerov / TU Delft / @akhmerov" +msgstr "" + +# 01c974ff81914cb281bb1dc5231e77dc +#: ../../source/community/community-call-notes/2019-april.md:98 +#: 4294fbdf67cc4718a1101d82b3e2b2fc +msgid "Peter Rose / UC San Diego / @pwrose" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:99 +#: 6aa6eb9d79aa4bec86f213629ced039f +msgid "A. T. Darian / Two Sigma / @afshin" +msgstr "" + +# 10d504db7f2d49ad9a6e5ab57b41fab5 +#: ../../source/community/community-call-notes/2019-april.md:100 +#: 992ae61fb9514ac0b365aaf1c30abbf7 +msgid "Ward Harold / Google / @wkharold" +msgstr "" + +# b14ce8eed0054e22b4c191df113909ac +#: ../../source/community/community-call-notes/2019-april.md:101 +#: 3ca7f5b85b894e6a83b7f282955d79ed +msgid "Damián Avila / / @damianavila" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:102 +#: 0163d6d1c14f424eba7cb76f42101d23 +msgid "" +"Chico Venancio / [BMC Group K.K.](http://www.bmc-group.co.jp/en/home/) / " +"@chicocvenancio" +msgstr "" + +#: ../../source/community/community-call-notes/2019-april.md:103 +#: 67ab54c1a8dc46ac85428891b5814478 +msgid "" +"Eric Lesch / [BMC Group K.K.](http://www.bmc-group.co.jp/en/home/) / " +"@EricLesch" +msgstr "" + +# ca568c83d79b4accb50b60680bd427c9 +#: ../../source/community/community-call-notes/2019-april.md:104 +#: c6c11b7028a24d1b8c42ee4fc2dfe13b +msgid "James Munroe / Memorial University of Newfoundland / @jmunroe" +msgstr "" + +# b26134512ca34ecca3fa2dffbe8d5860 +#: ../../source/community/community-call-notes/2019-april.md:105 +#: 8a5d8fc53ab14963be605159ed14da87 +msgid "Lindsey Heagy / UC Berkeley / @lheagy" +msgstr "" + +# 3952552d27f34fa098fcbbb6f713db7e +#: ../../source/community/community-call-notes/2019-april.md:106 +#: 44f754675a36400790023e269ea2da07 +msgid "Daniel Smith / The Molecular Sciences Software Institute / @dgasmith" +msgstr "" + +# 9d06cf89baca4dfd86bfc95cd9b80d5c +#: ../../source/community/community-call-notes/2019-april.md:107 +#: 45ab83557af441658edfd893a5eb3729 +msgid "Michael Milligan / U. Minnesota/MSI / @mbmilligan" +msgstr "" + +# 1467c37f42cb4c4cb4119a3dd29f3135 +#: ../../source/community/community-call-notes/2019-april.md:108 +#: ed42806b37b64770b9dd7ec381d46c14 +msgid "Kevin Bates / IBM / @kevin-bates" +msgstr "" + +# 25e45067de3f4262bbfbf0df2747321b +#: ../../source/community/community-call-notes/2019-april.md:109 +#: 0aa8d58a449844d69431722e99519948 +msgid "Cindy Wu / experiment.com / @cindywu" +msgstr "" + +# ab1d2ec08ce64f1c85e9154f51aab5b1 +#: ../../source/community/community-call-notes/2019-april.md:110 +#: 5efa438403e841cda99cce572bcb3ec2 +msgid "Joe Hamman / NCAR / @jhamman" +msgstr "" + +# 7077e51fe5884829ba4fd74741f61f0b +#: ../../source/community/community-call-notes/2019-april.md:111 +#: 89cfaeab5832407ca8a403cca4258c56 +msgid "Nick Bollweg / GTRI / @bollwyvl" +msgstr "" + +# aa19dbcc9b1642c89061c85e6d5a9a7b +#: ../../source/community/community-call-notes/2019-april.md:112 +#: a3c0caf891a840c8812eb159357b6c9f +msgid "Tom Baldwin / Cascade Data Labs / @baldwint" +msgstr "" + +# e914ee8e583840018ec681c69a4ba6d5 +#: ../../source/community/community-call-notes/2019-april.md:113 +#: aa1803f9a09c4e3fa81d3c8197d5c20d +msgid "Pete Blois / Google Colab / @blois" +msgstr "" + +# 8509e33906204614b41b177da02dd9dd +#: ../../source/community/community-call-notes/2019-april.md:114 +#: 06a333cc65524fac96d6824f8396ebe5 +msgid "Ana Ruvalcaba / Cal Poly, San Luis Obispo/Jupyter / @ruv7" +msgstr "" + +# 877bd91b3d324c49a569507fa672e423 +#: ../../source/community/community-call-notes/2019-april.md:115 +#: 5ca4351e792943e4b744a7fc7ec24c30 +msgid "Tim Head / Project Binder / Zurich / @betatim" +msgstr "" + +# e052dedf8ee8467a940fcacedfdadae6 +#: ../../source/community/community-call-notes/2019-april.md:116 +#: e83a3c9e052a4ae9a952ae1f83cad10d +msgid "Matthias Bussonnier / Jupyter Project / @carreau" +msgstr "" + +# 9ca6d660e28a4f8e942cc19ef4ede306 +#: ../../source/community/community-call-notes/2019-april.md:117 +#: a4027df4ef974bf98fa619d10ac4082c +msgid "Tim George / Cal Poly, San Luis Obispo/Jupyter / @tgeorgeux" +msgstr "" + +# 67d530ac592947f79ea603b5ff446c15 +# b17fcf6338a54b82a41b9406cba398cb +#: ../../source/community/community-call-notes/2019-august.md:1 +#: ../../source/community/community-call-notes/2019-june.md:2 +#: ../../source/community/community-call-notes/2019-may.md:1 +#: ../../source/community/community-call-notes/2019-september.md:1 +#: ../../source/community/community-call-notes/2020-november.md:1 +#: ../../source/community/community-call-notes/2021-january.md:1 +#: 141d768513994eee901bb2851c923926 5b830a84cd6a40f7aa6c0dd6770c0e00 +#: 78459ce58ed14d91b64f645ed12dd29f 8af94f9e90914192b83c1199f89f6dd1 +#: a585019e1ad94cf2b775ce6dcb1b7e5e ce3c8e5dec7d4995a11298c8519cd746 +msgid "Jupyter Community Call" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:3 +#: f300a89d0ae5482abc52c42fb40412a6 +msgid "August 27th, 2019" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:5 +#: 91313f1ae551482991d523a9e2247f46 +msgid "" +"**Date:** August 27, 2019, at 9am Pacific (your " +"[timezone](https://arewemeetingyet.com/Los%20Angeles/2019-08-27/09:00/Jupyter%20Community%20Call))" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:7 +#: 0fa0adb0bcf8404c901530adf7716fd2 +msgid "**Link:** [Youtube Video](https://youtu.be/k1-1XAML9fc)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:9 +#: ../../source/community/community-call-notes/2019-june.md:10 +#: 3bf02c26da414dc9b5cc5e830d2b7abf b673409fc4e94c42ab6f11b613cf7229 +msgid "**Welcome!**" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:11 +#: ../../source/community/community-call-notes/2019-june.md:13 +#: ../../source/community/community-call-notes/2019-may.md:12 +#: ../../source/community/community-call-notes/2019-september.md:9 +#: ../../source/community/community-call-notes/2020-december.md:13 +#: ../../source/community/community-call-notes/2020-november.md:15 +#: ../../source/community/community-call-notes/2021-april.md:14 +#: ../../source/community/community-call-notes/2021-february.md:14 +#: ../../source/community/community-call-notes/2021-january.md:15 +#: ../../source/community/community-call-notes/2021-march.md:14 +#: 146b9792fb4a4fefb44d8356095eacb9 18a052be16ce462da221fa136b8c4394 +#: 42f1a2a23a6341d69a7fbd2729e832d0 4d686025a53749189729e2d48f2157f5 +#: 5d109e3616a149189ecd56c70adc895f 703d20560a8a4783a2cf73f24058943f +#: 7118538dc0f44da6a42f7a9dcd2f8163 845ed6c2efd647a9ab113a6f4a7f7a70 +#: 88ae12e9076047faa6ac3323aa6185b0 d54bbebdf5a74a0ca23a82c922681ae4 +msgid "Purpose" +msgstr "" + +# 3dfb78f319a54af3a5566b5e90b8f227 +# df5d8e5baf5349e5b4a772ba51aa9db5 +#: ../../source/community/community-call-notes/2019-august.md:13 +#: ../../source/community/community-call-notes/2019-june.md:15 +#: ../../source/community/community-call-notes/2019-september.md:11 +#: ../../source/community/community-call-notes/2020-december.md:15 +#: ../../source/community/community-call-notes/2020-november.md:17 +#: ../../source/community/community-call-notes/2021-april.md:16 +#: ../../source/community/community-call-notes/2021-february.md:16 +#: ../../source/community/community-call-notes/2021-january.md:17 +#: ../../source/community/community-call-notes/2021-march.md:16 +#: 150d9ff048b5478ca3bfaee31c0e1639 28e2d784d6e8487a8b1b3df778f74644 +#: 4dac50ca5c1f45019e6281f1edfb27e9 9331e8861d1049de8ce7ea7c9110b9ef +#: ba08dbda096f4e6f99d0c9d17c201490 bb959e1703a54d82a884cbe70d86f8af +#: be99710fab3c440da70e84cd5bd51476 e7745043c424440096c5f9a411819e9c +#: ef8f8b352436454bb9b218f1cb25bef7 +msgid "" +"Think of it as a monthly, virtual JupyterCon. It’s a place to announce " +"and share fun things happening in the Jupyter community." +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:19 +#: ../../source/community/community-call-notes/2019-june.md:21 +#: ../../source/community/community-call-notes/2019-september.md:17 +#: 6319fd38c1404293b1666ba3b55e5817 b61dc50f38d84665b732d09828018b30 +#: ca22df6b9fb744f0bc2e186ab0ec44fe +msgid "" +"This is a place to make *short* announcements (without a need for " +"discussion)." +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:21 +#: b8cd14436d124ab2bb360c934c2a128b +msgid "" +"[x] Tracking Jupyter Newsletter, [22nd " +"edition](https://tinyletter.com/TrackingJupyter/letters/tracking-jupyter-" +"newsletter-the-twenty-second). Thank you, Tony Hirst!" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:22 +#: 385fe656392b47d886c56abc156b49c3 +msgid "" +"[x] JupyterLab 1.1.0rc0 is up on PyPI and conda-forge. Please test! " +"JupyterLab 1.1.0 will be released tomorrow." +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:23 +#: 4bf7678efd8742c58b1f07b3cf65c8d5 +msgid "`pip install --pre jupyterlab==1.1.0rc0` or" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:24 +#: 5ebd81d4ec8b46e89a98204641ea8481 +msgid "" +"`conda install -c conda-forge/label/prerelease-jupyterlab " +"jupyterlab=1.1.0rc0`" +msgstr "" + +# abf588a009c94510a22039358ab65a36 +# da313b5119cb433090c8c0735c863485 +#: ../../source/community/community-call-notes/2019-august.md:25 +#: ../../source/community/community-call-notes/2019-june.md:34 +#: 5b64186e7ebb4329ac1fa7eddabaa24d 7f226e740f7e445eacfd0f18faa885b4 +msgid "[ ] [name=yournamehere]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:29 +#: ../../source/community/community-call-notes/2019-june.md:38 +#: ../../source/community/community-call-notes/2019-september.md:27 +#: ../../source/community/community-call-notes/2020-december.md:34 +#: ../../source/community/community-call-notes/2020-november.md:29 +#: 75ad16e09d234d05a86ab0e6d7ae1241 82c17154e5904082a883f2f209cb22d3 +#: 91b6960a675c47e8b60cb4edea818af7 affbb3b062ff436cbf8562b539d46adc +#: cc32cc4a463d4a66b09129e3f1411bbf +msgid "" +"Add agenda items here **before** the meeting. We will reorganize the " +"agenda so that it fits in the 60m meeting slot." +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:31 +#: 327d53e25f0141949c321cbe70751302 +msgid "" +"[x] [name=Jupyter Cal Poly Intern Team] [Rich Text JupyterLab " +"extension](https://github.com/jupytercalpoly/jupyterlab-richtext-mode)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:32 +#: facea6292f274af1bdc669bd12293796 +msgid "" +"[x] [name=Jupyter Cal Poly Intern Team] [Python Package Installer " +"JupyterLab extension](https://github.com/jupytercalpoly/jupyterlab-" +"pkginstaller)" +msgstr "" + +# bd3a96cb5b9c42ce9f23a1b210c43e0c +#: ../../source/community/community-call-notes/2019-august.md:33 +#: 13ab7a9b64be459c8d92d205854595c4 +msgid "[x] [name=Tony Fast] Gist to Binder" +msgstr "" + +# f60290d0faf24437bae7f8cd84d4dcee +#: ../../source/community/community-call-notes/2019-august.md:34 +#: 9273843590344d96a59f0e13150dd750 +msgid "https://gist.github.com/Zsailer/6da0dc3c97ec873685b7fe58e52d36d7" +msgstr "" + +# 3aa54d82bd4242268b4fa5cdcdfed27c +#: ../../source/community/community-call-notes/2019-august.md:35 +#: e1152f401a3f42dba5b8cecf6067df73 +msgid "People say reproducibility is hard." +msgstr "" + +# 73e3a2adef1d4816802d822e55e8ad45 +#: ../../source/community/community-call-notes/2019-august.md:36 +#: d6f9831c49874c3a814e30d85d3b3f06 +msgid "User mybinder.org to generate a live notebook from a Gist." +msgstr "" + +# cc2bc565c6d14abca6512edb0dd25da5 +#: ../../source/community/community-call-notes/2019-august.md:37 +#: df33f0e4e72f4a5fb87ddadded9c854f +msgid "dependencies in requirement.txt lead to a faster build." +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:38 +#: eeae428e0da54323b0889a0727377391 +msgid "" +"[x] [name=Saul Shanabrook] [JupyterLab Rich Context " +"Extensions](https://discourse.jupyter.org/t/jupyterlab-rich-context-" +"extensions/1350)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:39 +#: 4fca12542a54437aad8d718b6d442537 +msgid "" +"[ ] [Data registry](https://github.com/jupyterlab/jupyterlab-data-" +"explorer) with [HDF5 Viewer](https://github.com/telamonian/jupyterlab-" +"hdf/)" +msgstr "" + +# 2a0b448dced4418398535add43652f6e +#: ../../source/community/community-call-notes/2019-august.md:40 +#: b2a80af92c8249ebafd86b76a7a136c3 +msgid "" +"[ ] It's meant to make it easier to create new extensions in JupyterLab " +"that deal with different data formats. If you have a data viewer " +"extension, you shouldn't care if the data came from a file or from a " +"notebook output or a database, you just want to be able to render a " +"certain format." +msgstr "" + +# fe52e076c5664572980df5677f546b1d +#: ../../source/community/community-call-notes/2019-august.md:41 +#: aebcd121903246e9a5040ef3e6be6f8a +msgid "[ ] Able to visualize HDF5 datasets using this extension too!" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:42 +#: 8328b27a14b745119235365c3c2a20ef +msgid "" +"[ ] [Metadata/linked data service](https://github.com/jupyterlab" +"/jupyterlab-data-explorer)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:44 +#: ../../source/community/community-call-notes/2019-june.md:57 +#: ../../source/community/community-call-notes/2019-may.md:60 +#: ../../source/community/community-call-notes/2019-september.md:44 +#: ../../source/community/community-call-notes/2020-december.md:53 +#: ../../source/community/community-call-notes/2020-november.md:38 +#: ../../source/community/community-call-notes/2021-april.md:66 +#: ../../source/community/community-call-notes/2021-february.md:98 +#: ../../source/community/community-call-notes/2021-january.md:93 +#: ../../source/community/community-call-notes/2021-march.md:56 +#: 022d2be3e78344e3b9a4bc46b0e4b603 08962f6873e44c1d82286114f42a4972 +#: 0cfc617007b14f30a82f4591256fc32d 7745b5401af1442a94fde53b392c839c +#: 8349689b30134ce09554b94580c6cd0d 84a8fa1d62854b6f9a21e8c2f64d8d41 +#: a57fae0b952c42d8b7609417db903f71 b080882709b045b3a4cb01751b7e06fd +#: c6c0408f761042d2aeb0bbf39c8a9df1 e5bfe21017184bdaa050327229c1e248 +msgid "Attendees" +msgstr "" + +# fc3e63f82fab46e4a57484fe9d8ca1fb +# a14aafdd62bb43c9be74b86f40987627 +#: ../../source/community/community-call-notes/2019-august.md:47 +#: ../../source/community/community-call-notes/2019-june.md:59 +#: 5766c67bd03947589c5cf100fe555791 5dd0b83762b94a869899c3b3c74eccb1 +msgid "" +"If you are joining the Jupyter Community Call, sign in below so we know " +"who was here." +msgstr "" + +# 214b40c5d407492aac8cf210fa49f089 +#: ../../source/community/community-call-notes/2019-august.md:49 +#: ../../source/community/community-call-notes/2019-september.md:47 +#: 40e7f7c41cf94edca9563c02e2491252 fcc74f0920774636bb7d2a4c8e216386 +msgid "Zach | Jupyter Cal Poly | @Zsailer |" +msgstr "" + +# c850262dfa8241afa4a195575fa7a9c9 +#: ../../source/community/community-call-notes/2019-august.md:50 +#: 90e76e9aa9b4474289b1ab958ff15416 +msgid "Derek | Jupyter Cal Poly (Intern) | @dLamSlo8 |" +msgstr "" + +# 86a650b3d5754ec4b0616654b382f7d8 +#: ../../source/community/community-call-notes/2019-august.md:51 +#: ca963fc5bb6a443d8d6c87b87783b580 +msgid "Isabela | Jupyter Cal Poly (Intern) | @isabela-pf |" +msgstr "" + +# 06b2e175880e4744a899b364f9cb89b4 +#: ../../source/community/community-call-notes/2019-august.md:52 +#: d24d08f946324c659ca75ef85fb6ec21 +msgid "Marisa | Jupyter Cal Poly (Intern) | @marisaaquilina |" +msgstr "" + +# 7fd569b0b2124ca6b72091c959788a71 +#: ../../source/community/community-call-notes/2019-august.md:53 +#: 0e70e9f99f274d8db835baaab1fec936 +msgid "Markelle | Jupyter Cal Poly (Intern) | @markellekelly |" +msgstr "" + +# 632ce11b167a450d9313f3b1b228a56b +#: ../../source/community/community-call-notes/2019-august.md:54 +#: 1b1e354287534667b10e741794a80bda +msgid "Javier | Jupyter Cal Poly (Intern) | @javag97 |" +msgstr "" + +# 056f27ff12a4459c95058f9205312b29 +#: ../../source/community/community-call-notes/2019-august.md:55 +#: 03aad899b81f44758c085921f40fdb28 +msgid "Denton | Project Drawdown | @dgentry |" +msgstr "" + +# 168efabbb3f6425dabbfb42e6600ec6c +#: ../../source/community/community-call-notes/2019-august.md:56 +#: 8a587acb9dcc42ab83881218be98765a +msgid "Tony | Quansight | @tonyfast |" +msgstr "" + +# 732d6b7583074b7ca3c2c71d8b36bf14 +#: ../../source/community/community-call-notes/2019-august.md:57 +#: 8599bc3d0d9f4ae8a4b9b658ccfbe978 +msgid "Chico Venancio| BMC Group K. K.| @chicocvenancio|" +msgstr "" + +# d20eaa785647473faabd23be9c0744c1 +#: ../../source/community/community-call-notes/2019-august.md:58 +#: 2972828a7a16482a95d5636b06f1e7bf +msgid "Elizabeth DuPre | McGill University | @emdupre|" +msgstr "" + +# 7d6d2cd4ce384e4aadec978d60ff97b5 +#: ../../source/community/community-call-notes/2019-august.md:59 +#: 1a129130487c4832821357eab1125a96 +msgid "Wayne Decatur | Upstate Medical University | @fomightez|" +msgstr "" + +# 5998deb954d442e08d3798744b992751 +#: ../../source/community/community-call-notes/2019-august.md:60 +#: d271fa58205e4837b91de04089c5682f +msgid "Saul Shanabrook | Quansight | @saulshanabrook |" +msgstr "" + +# 4d57c62f1600466bb92f277d422eb292 +#: ../../source/community/community-call-notes/2019-august.md:61 +#: ee02b218390849ecbf72e3832bebe93c +msgid "Joe | Mavenomics | @quigleyj-mavenomics|" +msgstr "" + +#: ../../source/community/community-call-notes/2019-august.md:62 +#: 4fff3d3b23ae4223aae3a4cf9e3a0347 +msgid "A. T. Darian | Two Sigma | @afshin |" +msgstr "" + +# 8fa7f9222d5f4ea48e62b0c77cc7e0a9 +#: ../../source/community/community-call-notes/2019-august.md:63 +#: 22a507f48e274ff39dc0d25540b4b842 +msgid "Erik Sundell | Sandvik | @consideRatio |" +msgstr "" + +# 534b69b41eb8461a8fb8d14486cce85e +#: ../../source/community/community-call-notes/2019-august.md:64 +#: fb985f8b8294412b896a786e98ab25cb +msgid "Kevin Bates | IBM | @kevin-bates |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:4 +#: 2eafed696c204ad3b499272132bc8af4 +msgid "June 25th, 2019" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:6 +#: c7d9fec800614249829e1bc6ed115112 +msgid "" +"**Date:** June 25th, 2019, at 9am PST (your " +"[timezome](http://arewemeetingyet.com/Los%20Angeles/2019-06-25/09:00/Jupyter%20Community%20Call))" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:8 +#: a07254a6c0b44d918df99f90e5eefd71 +msgid "**Link** [Youtube Video](https://youtu.be/27pMFoJd0H4)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:23 +#: 3927dcc44a294e1f9dea3d552d5825f3 +msgid "" +"[ ] [name=willingc] Congrats again to our [newest BinderHub/JupyterHub " +"team member, Sarah](https://discourse.jupyter.org/t/welcoming-our-new-" +"jupyterhub-team-member-sarah/1416) :tada:" +msgstr "" + +# fb23b23b3e684ca28874402cb265a324 +#: ../../source/community/community-call-notes/2019-june.md:24 +#: 57fab2d961a8463e8305342d5b22b9a1 +msgid "[ ] [name=Zsailer] Welcome the new Jupyter Cal Poly Intern team." +msgstr "" + +# 7072df0cf9f648f387a4d7ca6fda3f51 +#: ../../source/community/community-call-notes/2019-june.md:25 +#: 0afef5bec0f7490082c0d2c5f6da1ba3 +msgid "" +"[ ] [name=tgeorgeux] Introduction to Rich Context Work: Metadata, Data " +"Registry, Commenting and Annotation, Real-Time Collaboration, Telemetry." +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:26 +#: 3de120e5980f401aaa4146c94cdc0573 +msgid "" +"[Data Registry/Explorer](https://github.com/jupyterlab/jupyterlab-data-" +"explorer)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:27 +#: 79781338e7654ac998ed47801b14b2f9 +msgid "[Commenting](https://github.com/jupyterlab/jupyterlab-commenting)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:28 +#: c37679687cf4442e8981a185c8ce7d05 +msgid "[Metadata](https://github.com/jupyterlab/jupyterlab-metadata-service)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:29 +#: ffc724983e4f4c31882b5e6e88f0837f +msgid "[Telemetry](https://github.com/jupyter/telemetry)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:30 +#: 7cf2b801e533487999421b7759c7e096 +msgid "" +"[ ] [name=Erik Sundell] " +"[repo2docker](https://github.com/jupyter/repo2docker) / MyBinder.org " +"support for git repositories with Pipfile / Pipfile.lock coming up soon I" +" hope ;D " +"[repo2docker#649](https://github.com/jupyter/repo2docker/pull/649)" +msgstr "" + +# 545fa94a22bb4e17bed6be059eb02fcc +#: ../../source/community/community-call-notes/2019-june.md:40 +#: 71aa1a85d4ce4892b53324458d75b43a +msgid "[ ] [name=kbates] Brief overview of Jupyter Enterprise Gateway" +msgstr "" + +# 575e8f96475e44279b48500c3d7a6036 +# 95b92a12b5fc4eae9bd0b5b6c98ee364 +#: ../../source/community/community-call-notes/2019-june.md:41 +#: ../../source/community/community-call-notes/2019-march.md:59 +#: ../../source/community/community-call-notes/2019-march.md:67 +#: 03729d3ece9c488faaae07578fcee4bb 05dc70257a4e45dcb9be21a1b9fd037a +#: ffa176da0ef34018b379181c9f11aa73 +msgid "Questions:" +msgstr "" + +# 5cef67cb787b469bac11ff11bd25ee48 +#: ../../source/community/community-call-notes/2019-june.md:42 +#: f4436232f91c413cb494ac4cc0fd61b3 +msgid "Where can we find information to share with others?" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:43 +#: a85cbea0a1ef48778c41cb5da8d5557d +msgid "" +"See this [post](https://blog.jupyter.org/on-demand-notebooks-with-" +"jupyterhub-jupyter-enterprise-gateway-and-kubernetes-e8e423695cbf)" +msgstr "" + +# a109573ad06f4685833b3f789b231cc9 +#: ../../source/community/community-call-notes/2019-june.md:44 +#: 408a5ddc90cb464e80c70d7d3c62ff50 +msgid "Comments:" +msgstr "" + +# af5bd56782184f5c8eb920cfbc79cae1 +#: ../../source/community/community-call-notes/2019-june.md:45 +#: ca53bfac019c47a0912ea45d3c8f4aac +msgid "Add talks to EG docs" +msgstr "" + +# b95d9e06395c4b09a9a807d4df0b8cef +#: ../../source/community/community-call-notes/2019-june.md:46 +#: ca71b1bc57f0409a93bf3ded9b500902 +msgid "Check if Docker Stacks has a link to the EG docker stacks" +msgstr "" + +# ac9542a7f10d4905bd45ebab1b57fef8 +#: ../../source/community/community-call-notes/2019-june.md:47 +#: 5d3fe1063621491484523172390999ad +msgid "Add link to this demo to the EG docs" +msgstr "" + +# 7beec91928de4ac890222116506e783f +#: ../../source/community/community-call-notes/2019-june.md:48 +#: 040e5ae07b0a4eeeabb237626227670b +msgid "" +"[ ] [name=dgentry] existing system for git commit+push without requiring " +"a forked repo? Similar to submitting homework for grading?" +msgstr "" + +# 948e4c278e1e4594b53418a21f3775eb +#: ../../source/community/community-call-notes/2019-june.md:49 +#: 560d094dccfb4d179317e9625ba27a3b +msgid "nbgrader and hubshare mentioned by Zach" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:50 +#: 3312ba8d4d2d436596f150cbe694aae0 +msgid "" +"[nbstripout](https://github.com/kynan/nbstripout) / [fastai-" +"nbstripout](https://github.com/fastai/fastai-nbstripout) can play a part " +"of making git merges more reasonable" +msgstr "" + +# 2941d97b294c49d9a44399b539e453e1 +#: ../../source/community/community-call-notes/2019-june.md:51 +#: 8cea08f7d2ab4b4e9389c910e62d0e24 +msgid "Ask the Jupyter education community" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:52 +#: f4865d5f78ee4b44b0720ffe5b59b4d7 +msgid "[Jupyter Education Mailing List](https://jupyter.org/community)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-june.md:53 +#: 0a4187f6e11741629c594c165e3c488b +msgid "" +"Check out solutions from [Gigantum](https://gigantum.com/), a tech " +"company started out of Johns Hopkins" +msgstr "" + +# 6b470078de6c4d56a9b5147113c298d7 +# 09beb5999f2d4600838e4c855a626b3c +#: ../../source/community/community-call-notes/2019-june.md:54 +#: ../../source/community/community-call-notes/2019-june.md:55 +#: 574454e0549749f09f4fa9da358e1ca6 bc428e23289f4ccc8d9c8074cace6308 +msgid "[ ] [name=YourNameHere]" +msgstr "" + +# a5f40f6e13b84808b0e6bd80ca4faf86 +#: ../../source/community/community-call-notes/2019-june.md:61 +#: cd6598818fad451b91aa0767a2fdf94e +msgid "Zach | Jupyter Cal Poly | @Zsailer |" +msgstr "" + +# 35dbce6660f44c5c8762b79815f37321 +#: ../../source/community/community-call-notes/2019-june.md:62 +#: f962191439134516bbaabf78041ea3af +msgid "Erik | Sandvik | @consideRatio |" +msgstr "" + +# e2f6d95bb87044588a7538e22290595e +#: ../../source/community/community-call-notes/2019-june.md:63 +#: cf9a29445c5e42fc8547e5db4b205056 +msgid "Denton | individual | @DentonGentry |" +msgstr "" + +# 849f5928bcf2488d9994bbfbf3d59d99 +#: ../../source/community/community-call-notes/2019-june.md:64 +#: 4862be8f9df0479fbf2c1a9d8e3d6257 +msgid "Tim | Jupyter Cal Poly | @tgeorgeux |" +msgstr "" + +# 9eba765b73cf4901baab7c3d71a10c47 +#: ../../source/community/community-call-notes/2019-june.md:65 +#: 684ed907c6f4465c9b951e140bcc3052 +msgid "Kevin | IBM | @kevin-bates |" +msgstr "" + +# bd580edd7a1147fa993c941637857709 +#: ../../source/community/community-call-notes/2019-june.md:66 +#: 3fa11a113afa49efbe63184025ca20bb +msgid "Wayne | Upstate Medical University| @Fomightez |" +msgstr "" + +# 39788dc41fef46bba8335b5a2444706a +#: ../../source/community/community-call-notes/2019-june.md:67 +#: f36b355ed3c84627840d05cf8c12edcd +msgid "Dav | Gigantum | @davclark |" +msgstr "" + +# ab23397c870944cd91406099afd69b33 +#: ../../source/community/community-call-notes/2019-june.md:68 +#: 5920d65076714124a1abe93dd7a70496 +msgid "Mike Trizna | Smithsonian | @MikeTrizna |" +msgstr "" + +# be0a7274e1c34e5988d69e1342a03b4d +#: ../../source/community/community-call-notes/2019-june.md:69 +#: d86f06381701481ea6d7b9930b8e73bd +msgid "Anton Akhmerov | TU Delft | @akhmerov |" +msgstr "" + +# c574adb76c22402cbb55ff254f36314b +#: ../../source/community/community-call-notes/2019-june.md:70 +#: 0631174c30414e76845e28777f615553 +msgid "Markelle | Jupyter Cal Poly | |" +msgstr "" + +# 52a39c930c1640b99d87580de77ec9b0 +#: ../../source/community/community-call-notes/2019-june.md:71 +#: 96bc03c1acf040c0b2116adde21d998c +msgid "Carol | Jupyter | @willingc |" +msgstr "" + +# 8a3445588709466d9a3a073153961fa4 +#: ../../source/community/community-call-notes/2019-june.md:72 +#: 5a842714a5624695a758b5529bc8c705 +msgid "Saul | Quansight | @saulshanabrook |" +msgstr "" + +# a0800aa51b3c4d24b9de0ac8e61a5be8 +#: ../../source/community/community-call-notes/2019-june.md:73 +#: 9ec31a1906c642d88274e5498fd65997 +msgid "Yair | Mavenomics | @YairMarcowMavenomics|" +msgstr "" + +# 5f9eee8502ba4832a9c63f46d2e4cf5c +#: ../../source/community/community-call-notes/2019-june.md:74 +#: 728f2667b25743079a66a9c4f1096855 +msgid "Joe | Mavenomics | @quigleyj-mavenomics|" +msgstr "" + +# 148ee6b6bf234785952cddae2ac7ede3 +#: ../../source/community/community-call-notes/2019-june.md:75 +#: 0d172b7611c24e4bb6461ce626aa74aa +msgid "Ruixin | Microsoft | @ruixinxu |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:1 +#: 733729e17ae34c729cd0bedd330d504b +msgid "All-Jupyter Community Video Call - March 2019" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:3 +#: 55d23f4328de43d78f91dfc2feaddbef +msgid "" +"**Date:** 26 March 2019 at 9am PST (your " +"[timezome](http://arewemeetingyet.com/Los%20Angeles/2019-03-26/09:00/Jupyter%20Team%20Meeting))" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:7 +#: 6e5cd84c45ff4cf1a9e3fc9f9280bb48 +msgid "" +"[Link to prior meeting's virtual meeting " +"report](https://paper.dropbox.com/doc/February-26-2019-Jupyter-Community-" +"Meetings--AYQW8rw8lRF~M7gNT9WrtW4iAg-6pRznjq5hGOPcJARLFtld)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:21 +#: 3867abd0bf6f4cd4918efab2424f27fa +msgid "" +"[x] Shout out to Damian Avila for the second community docker stack: " +"[umsimads/education-notebook](https://github.com/umsi-mads/education-" +"notebook) [Peter Parente, jupyter/docker-stacks]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:22 +#: d70a6a526ee341f49d878ee72ebfad50 +msgid "" +"[x] Thank you Tony Hirst for your weekly newsletter [*Tracking " +"Jupyter*](https://tinyletter.com/TrackingJupyter) [Carol Willing, " +"JupyterHub]" +msgstr "" + +# 4ea07ce04b3040449deb6931e15aa9a0 +#: ../../source/community/community-call-notes/2019-march.md:23 +#: 377c6d76422c4d4db70d6695c6a1382b +msgid "" +"[x] Thank you to Professor Lorena Barba at GWU for hosting the recent " +"Jupyter team meeting [Carol Willing, JupyterHub]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:24 +#: 54395a6af66b4095b324973e073e35e4 +msgid "" +"[x] Kudos, Zach Sailer et al, for kicking off the revitalization of this " +"meeting over on the [Jupyter Discourse](https://discourse.jupyter.org/t" +"/reviving-the-all-jupyter-community-meetings/423/11) site [Peter Parente " +"(and everyone in attendance I suspect)]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:25 +#: e5e74320ba004f549b3e23be2788edc5 +msgid "" +"[x] Leave your feedback about our new all-Jupyter community call " +"[here](https://discourse.jupyter.org/t/reviving-the-all-jupyter-" +"community-meetings/423)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:26 +#: f4b7cbd5bb184d54a35d276db5a50afd +msgid "" +"[x] Come join us on the [Jupyter Discourse " +"Forum](https://discourse.jupyter.org)! (in case you aren't already tired " +"of me telling you this :-) )" +msgstr "" + +# 095d4c78eef24cbbbf17ad5f69877f49 +#: ../../source/community/community-call-notes/2019-march.md:27 +#: eb5569c506cf4480b1749a4c3011839c +msgid "https://discourse.jupyter.org/t/introduce-yourself/17" +msgstr "" + +# 8b6f8a96f6224c2783617b279ad16d8f +#: ../../source/community/community-call-notes/2019-march.md:28 +#: b13631342b21441fb8e2360d01c88364 +msgid "Turn off add blocker if you want to login with google or github." +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:32 +#: cd3b5e5cee624e4fbb9e53d4ac5f351a +msgid "" +"Let’s collect all potential agenda items here before the start of the " +"meeting (closing time **24h before**). We will then attempt to create a " +"coherent agenda that fits in the 60m meeting slot. If there are similar " +"items try and group them already." +msgstr "" + +# 37e673b044fb4eaea7a3106c4e309772 +#: ../../source/community/community-call-notes/2019-march.md:34 +#: 8456fb2a96b24605a4ba3883e6d20372 +msgid "" +"[x] Suggested demo: docker-stacks project now posts image build manifests" +" back to the GitHub project wiki for inspection [Peter Parente, " +"https://github.com/jupyter/docker-stacks/wiki, 5 minutes]" +msgstr "" + +# 42265e1f00e546ddbd81db0bba6eb88c +#: ../../source/community/community-call-notes/2019-march.md:35 +#: 81927acafbbf475482104fea014efca8 +msgid "" +"[x] Introduction to mybinder.org, how to make a repository ready for " +"running on mybinder.org [Tim Head, 10minutes]" +msgstr "" + +# 24d5c9e1a338498ebda6a798cb3364f1 +#: ../../source/community/community-call-notes/2019-march.md:36 +#: 4ab9f84e080543b7b78fa7ca6b76e975 +msgid "https://mybinder.org/" +msgstr "" + +# 854f973f06d14ee28b19b00fedec7b61 +#: ../../source/community/community-call-notes/2019-march.md:37 +#: e2737e5dd3b545f08612bb3a33a3cbf0 +msgid "https://github.com/betatim/my-first-binder" +msgstr "" + +# e0de2e1622b246638188033646a13f6a +#: ../../source/community/community-call-notes/2019-march.md:38 +#: 399c9fe8837e4c908078f82d4e82d9db +msgid "Lots of example repositories: https://github.com/binder-examples/" +msgstr "" + +# b084dbfe6bd7455db583202d55e66ff8 +#: ../../source/community/community-call-notes/2019-march.md:39 +#: de5019bb5b424b8f8f4056902e595d9d +msgid "Not just notebooks: https://github.com/betatim/vscode-binder" +msgstr "" + +# f115663b207842d08e7f50c26bf8ea84 +#: ../../source/community/community-call-notes/2019-march.md:40 +#: 112ba3c693054222b1aa2633c0d580be +msgid "" +"Documentation on how to specify dependencies and such " +"https://repo2docker.readthedocs.io/en/latest/" +msgstr "" + +# bb63324fe45a433babf0f6ed99d90d5a +#: ../../source/community/community-call-notes/2019-march.md:41 +#: 8e35ac8a0587498db4d111222e2fa54a +msgid "Questions, comments and support: https://discourse.jupyter.org/c/questions" +msgstr "" + +# 85738a54e439443386fa6379f01e21cf +#: ../../source/community/community-call-notes/2019-march.md:42 +#: 8e21adc7e3f34ac293f63e2e7b88bf26 +msgid "Write questions you have here:" +msgstr "" + +# 8f6656c371754cf890fbf0ec645c129f +#: ../../source/community/community-call-notes/2019-march.md:43 +#: a403a2066f324043b98f415e166b461e +msgid "..." +msgstr "" + +# 1809dc99df1840eea5a3ba67e4a8293b +#: ../../source/community/community-call-notes/2019-march.md:44 +#: 4bc9f41cbd814298ae3d1b707f90bde4 +msgid "" +"Is it true that you personally are the only user of " +"https://github.com/Carreau/open-with-binder ?" +msgstr "" + +# 7fd9ece1b20c4b08bbdd623ad539370f +#: ../../source/community/community-call-notes/2019-march.md:45 +#: bd55334db7e3433b909e348bbc5d3768 +msgid "" +"If running an event/tutorial type thing with Binder, how many users " +"should we feel comfortable sending to MyBinder vs setting up our own Z2JH" +" infrastructure?" +msgstr "" + +# d584ca69a41c438d88c2d0e0d1cd8db5 +#: ../../source/community/community-call-notes/2019-march.md:46 +#: 3b9b884e349a407bb19f245df07e84d7 +msgid "" +"By default it prevents more than 100 concurrent launches of the same repo." +" You can ask for more if you are nice." +msgstr "" + +# 0ecf242c9bec4cfa8f0f1173b255bd3b +#: ../../source/community/community-call-notes/2019-march.md:47 +#: c28515ff71ec4d88b7c5973e1b377c5b +msgid "" +"fun fact: apparently the reason this launch was slow is because somebody " +"is teaching a \"learn java\" course on Binder just now and a bunch of " +"people connected all at once https://github.com/santanche/java2learn" +msgstr "" + +# b310fceed5d14b7fbd7ff7f3aea1380f +#: ../../source/community/community-call-notes/2019-march.md:48 +#: d5ba7516fec04c61a9b0ef99357ee1a4 +msgid "Show the log dashboard :P" +msgstr "" + +# 53813024a5e74f90af276c84a1eced67 +#: ../../source/community/community-call-notes/2019-march.md:49 +#: 4f9e348cc3bd4a7abbec85483ed91fd1 +msgid "" +"sure thing: https://grafana.mybinder.org/d/fZWsQmnmz/pod-" +"activity?refresh=1m&panelId=1&fullscreen&orgId=1" +msgstr "" + +# ce5df9e9ff06483fa666e1ef54087f24 +#: ../../source/community/community-call-notes/2019-march.md:50 +#: f8a8a97b5e4b48359cd682193723dcc3 +msgid "We'd love to figure out a funding model for binder" +msgstr "" + +# 926b6a913747478baa9bae2c0338b473 +#: ../../source/community/community-call-notes/2019-march.md:53 +#: 9a0232942beb4ee9a510b851150ba6c8 +msgid "[x] [10minutes ] Update from the nteract team [Safia]." +msgstr "" + +# be841d1862024767b49b29fcfaee94c1 +#: ../../source/community/community-call-notes/2019-march.md:54 +#: 7b872a41d4254314bd40021fca9e3ddf +msgid "" +"Version 1.0 of papermill, notebook execution and parameterization " +"library, will be released in early April. " +"(https://github.com/nteract/papermill)" +msgstr "" + +# 5eb198cfcaa045029021da8b1d31697d +#: ../../source/community/community-call-notes/2019-march.md:55 +#: 345b54374a8646d79718bca11a59c8d2 +msgid "" +"Scrapbook, tool for extracting and assembling generated outputs and data " +"from notebooks, known as scraps, will allow you to host scraps remotely " +"on various cloud providers. (https://github.com/nteract/scrapbook)" +msgstr "" + +# 801440793f0e425aa2defa145970d24e +#: ../../source/community/community-call-notes/2019-march.md:56 +#: 8ba667e832c74f8498a745822bf10f15 +msgid "" +"Plan laid out for version 1.0 of the kernel-relay, a GraphQL API for " +"interfacing with Jupyter kernels. (https://github.com/nteract/kernel-" +"relay)" +msgstr "" + +# c23623786e5b4dd9acd259a455dfa7e2 +#: ../../source/community/community-call-notes/2019-march.md:57 +#: 9c2b5cb75d814302a7c73b6480aed085 +msgid "" +"Effort to modularize the Data Explorer, an automatic visualization " +"library, is underway." +msgstr "" + +# bab4d7361bae4ae9b2ff585598fa5ebd +#: ../../source/community/community-call-notes/2019-march.md:58 +#: f8bbfe3d20144684abac94248bb20f7d +msgid "" +"nteract is participating in Google Summer of Code " +"(https://summerofcode.withgoogle.com/organizations/5447807656263680/)" +msgstr "" + +# 23bb0f9e952c4f21aab28e692da49187 +#: ../../source/community/community-call-notes/2019-march.md:60 +#: afb423659107451f8df363db364324a7 +msgid "How to learn more:" +msgstr "" + +# 390b8f9c2d78493e99d76710077fb4ce +#: ../../source/community/community-call-notes/2019-march.md:61 +#: fa2e7bc796894f319e0ffc201d71f5ae +msgid "Nteract slack https://slack.nteract.io/" +msgstr "" + +# d88c460c30f1414fa878ce41d8d9e4f2 +#: ../../source/community/community-call-notes/2019-march.md:62 +#: 05639e66c4774223b3c82eb56d543b44 +msgid "Weekly meeting on Monday Afternoon" +msgstr "" + +# 578b2e5b5c7d4302b6ac9e2b2375fcf6 +#: ../../source/community/community-call-notes/2019-march.md:63 +#: 534a86e9e31d48f6a317616952536f61 +msgid "Where is the Data Explorer repo?" +msgstr "" + +# ebef350151214f508f0d6729916dd744 +#: ../../source/community/community-call-notes/2019-march.md:64 +#: 1f5ab59b74614c248d9d3e4508841398 +msgid "[x] deathbeds stuff [Nick, github.com/deathbeds, 5min]." +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:65 +#: a7dcaef3e98e44b696b823d1c84be22a +msgid "" +"[lintotype](https://github.com/deathbeds/lintotype): interactive linting " +"& formatting" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:66 +#: 6d700068f7e44f93aed9d8c2a5a428db +msgid "[wxyz](https://github.com/deathbeds/wxyz): some crazy widgets" +msgstr "" + +# 1c89c48468524b7baec0c063e9789dfd +#: ../../source/community/community-call-notes/2019-march.md:68 +#: 92272727425544d79fbd6c6efabe0b5e +msgid "The SVG messed with my eyes. <3" +msgstr "" + +# 67555afea1fe46fbabfb35ef2daf0f3a +#: ../../source/community/community-call-notes/2019-march.md:69 +#: 4c6a45752d544833901d4024c3c30f5c +msgid "Can you expand upon the \"cell-id\" things?" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:70 +#: 209a10305d324622bfa25004a7601fc9 +msgid "" +"[cell id in " +"lintotype](https://github.com/deathbeds/lintotype/blob/4b83f784b56ef12a245c0ca92d48eb95a9b0f7da/packages/ipylintotype/src/ipylintotype/formatter.py#L116)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:71 +#: f16846f260f94f94a3e32dfaae0919c5 +msgid "" +"[cell id in " +"irobotframework](https://github.com/gtri/irobotframework/blob/865311e0f89e2418e253f60cd7ae50990d4d6e6a/src/irobotframework/kernel.py#L90)" +msgstr "" + +# 6e2574521fe94e9ebb42406d92ce0894 +#: ../../source/community/community-call-notes/2019-march.md:72 +#: 0c3cfc00cd1a490fb08d942765c33e04 +msgid "Are those supposed to be extension ? Built-in ?...?" +msgstr "" + +# 012c1ebe05084778a57c646dc99871f8 +#: ../../source/community/community-call-notes/2019-march.md:73 +#: ff89e002324c436ea303da15514ebaf6 +msgid "ready to be packaged (not yet). Some of the stuff could go into ipywidgets" +msgstr "" + +# 248321ccf26d44aaa70813dcb24dc8f5 +#: ../../source/community/community-call-notes/2019-march.md:74 +#: dd261d0b36a7483e9038205ea964906f +msgid "" +"[x] IPython releases [Matthias, IPython, " +"https://github.com/ipython/ipython, 2min.]" +msgstr "" + +# 86328c25f6a440b18498fd75aa70a47f +#: ../../source/community/community-call-notes/2019-march.md:75 +#: c546f01f0856483db0d7f148f768671a +msgid "Trying to do monthly release close to End Of Month." +msgstr "" + +# a3bff58397d14548b0a589b6ed34b746 +#: ../../source/community/community-call-notes/2019-march.md:76 +#: 8f4f3d64290b4cc7ab14e6cd098cb7cb +msgid "7.4 has been released ! Thanks to everyone." +msgstr "" + +# 10cf7fd1b78140f586b0e030906d86d3 +#: ../../source/community/community-call-notes/2019-march.md:77 +#: 42041a4c808a4dde90be2646d5b3a586 +msgid "If you want to help with 7.5 subscribe to the following issue." +msgstr "" + +# 3cdd82e3aae0483390d52d067996ba29 +#: ../../source/community/community-call-notes/2019-march.md:78 +#: 8f17bf89f90848de85020e29c7481b4e +msgid "https://github.com/ipython/ipython/issues/11657" +msgstr "" + +#: ../../source/community/community-call-notes/2019-march.md:79 +#: fe9af32265374dfabdd56bb4fbd5979f +msgid "" +"[x] Async Kernels startup : [Matthias, Jupyter Client , " +"https://github.com/jupyter/jupyter_client/pull/428, 4min.]" +msgstr "" + +# 78e107a4d23e404f9e0894820a18b989 +#: ../../source/community/community-call-notes/2019-march.md:80 +#: 27a9f04725ac40de9b5d381db2ca1af2 +msgid "https://github.com/jupyter/jupyter_client/pull/428" +msgstr "" + +# ba575c52f6614673ba74d5a26511c9b7 +#: ../../source/community/community-call-notes/2019-march.md:81 +#: bd440e51dad94f53a474f20769a57237 +msgid "add item here [name, project name/url, estimated time for discussion]." +msgstr "" + +# 9a919edea46042fda80ad5719ba42c25 +#: ../../source/community/community-call-notes/2019-march.md:83 +#: feb3053e773948d688e91464db171806 +msgid "Don't get limited to technical discussions !" +msgstr "" + +# 6a1d536f3f6c46b2b79fcdecd6491c4c +#: ../../source/community/community-call-notes/2019-march.md:87 +#: a5b07294b3324e228d4b08e60031144d +msgid "Name | Institution | Github Handle" +msgstr "" + +# 1732e5aff57b4c4da3bb50f28c6b0c62 +#: ../../source/community/community-call-notes/2019-march.md:89 +#: e60e43ed33e14d43acd980a57e799870 +msgid "Zach | Jupyter Cal Poly | @Zsailer" +msgstr "" + +# b11a95084ddf4b2c9a29a2b4aab7f7d6 +#: ../../source/community/community-call-notes/2019-march.md:90 +#: 9cfbceaf43e247388a078165459ecddb +msgid "Kyle | Netflix | @rgbkrk" +msgstr "" + +# 98e54a5ef37643a7bd3ed27fd9a631c1 +#: ../../source/community/community-call-notes/2019-march.md:91 +#: 85573c2bf86a4d0a84622dbcf73a478e +msgid "Pete | Valassis Digital | @parente" +msgstr "" + +# 65a7b3e76af0494dbcd380b916cb375b +#: ../../source/community/community-call-notes/2019-march.md:92 +#: 38f900a851bc4036a20053679bf552f3 +msgid "" +"Carol | Project Jupyter | @willingc (will miss due to" +" OpenEdX conference)" +msgstr "" + +# 35546464a79a4d67a9291c47c369554f +#: ../../source/community/community-call-notes/2019-march.md:93 +#: 60ffde26919343ed9f3ae3c5f7823525 +msgid "Brian | AWS | @ellisonbg" +msgstr "" + +# 0440aca017e645d19de2bc481c5a797c +#: ../../source/community/community-call-notes/2019-march.md:94 +#: e347a3a1d532426eac92a3fb5bc66df7 +msgid "Darian | Two Sigma | @afshin" +msgstr "" + +# 77b9417cf46e46a38c0a47d5f29bf3fc +#: ../../source/community/community-call-notes/2019-march.md:95 +#: 90f6acbfcbfb49dc9dafbcdffa2e6f94 +msgid "Ward | Google | @wkharold" +msgstr "" + +# c50cf028579347d7a55a83faa4bd3382 +#: ../../source/community/community-call-notes/2019-march.md:96 +#: 50350a048fe84bc8b265c9f4f669a893 +msgid "Tim | Project Jupyter | @betatim" +msgstr "" + +# 49103926264a459291e15f49e7e5ed2e +#: ../../source/community/community-call-notes/2019-march.md:97 +#: 0374292a1c274dcca5747e85051539d0 +msgid "Chris | Berkeley/Project Jupyter| @choldgraf" +msgstr "" + +# 58a1958fa38b419eb6a9ed4b8ce60478 +#: ../../source/community/community-call-notes/2019-march.md:98 +#: 6ce407e7773c4e17a30c0ac46cec679d +msgid "Pete | Google Colab | @blois" +msgstr "" + +# 140b0f78582045b8b0d61a860a292a36 +#: ../../source/community/community-call-notes/2019-march.md:99 +#: c6f5d8bc84d7466ba29cb960435ce02e +msgid "Matthias | UC Merced | @carreau" +msgstr "" + +# e2831caffe3643739d2f2e1654fea586 +#: ../../source/community/community-call-notes/2019-march.md:100 +#: 084e8602285c4b96bb3383019cde64ea +msgid "Saul | Quansight | @saulshanabrook" +msgstr "" + +# c21bc34a60b244fd8d82e4c60736f7d6 +#: ../../source/community/community-call-notes/2019-march.md:101 +#: b8c09b798e8d4002a947d6d6164d50a9 +msgid "Vidar | Simula Research | @vidartf" +msgstr "" + +# 9559e6b327a544f0a342ad6957843444 +#: ../../source/community/community-call-notes/2019-march.md:102 +#: fab7a7c862454d1cb79f5a6dc8bffe82 +msgid "Lindsey Heagy | UC Berkeley | @lheagy" +msgstr "" + +# fcabe7d6182c4feaa5c68e2c1e7c2716 +#: ../../source/community/community-call-notes/2019-march.md:103 +#: c2f120c76f6a4d1b9451f70e342a0d9e +msgid "Safia ABdalla | Microsoft/nteract | @captainsafia" +msgstr "" + +# 24577687e8a2477cb670afb803a4dd0f +#: ../../source/community/community-call-notes/2019-march.md:104 +#: c348ba12002c4e9fb88402b8f0209c35 +msgid "Leticia Portella | - | @leportella" +msgstr "" + +# 7e4960f551e248e4970b53f55e895d1c +#: ../../source/community/community-call-notes/2019-march.md:105 +#: a45b2dfd6db74b26af50c05e826f8715 +msgid "Damián Avila | Project Jupyter | @damianavila" +msgstr "" + +# 6ff0836b9600403b94a196469214e269 +#: ../../source/community/community-call-notes/2019-march.md:106 +#: 25ce9b4401a04862b0009faaa1bba2b2 +msgid "Craig Citro | Google Colab | @craigcitro" +msgstr "" + +# 2b083f8a972240e9ac40611b77004932 +#: ../../source/community/community-call-notes/2019-march.md:107 +#: 2bfcf99198814cdcbf012ec4437b7135 +msgid "Nick Bollweg | GTRI | @bollwyvl" +msgstr "" + +# c512ec8cf1514a138acb0e2e071d4c5b +#: ../../source/community/community-call-notes/2019-march.md:108 +#: 2cdbfb20b7c54f8bbe98ac9294ee5a40 +msgid "Michael Milligan | U Minnesota / MSI | @mbmilligan" +msgstr "" + +# 18f7ee76c90f48a5969d057a6d9bd8b0 +#: ../../source/community/community-call-notes/2019-march.md:109 +#: bb4236c2d8ed48aa8ee230545f20c0f3 +msgid "Liang Bin Hsueh | InfuseAI | @hlb" +msgstr "" + +# 78fdf3bcb4d44055830b378dd73c452a +#: ../../source/community/community-call-notes/2019-march.md:110 +#: 8adec3ec8832469a94f6e3bffc3dbdc7 +msgid "Thomas Vander Velde | - | @tomasdelcampo" +msgstr "" + +# 161172282fa048429a2c2e24595ccdb1 +#: ../../source/community/community-call-notes/2019-march.md:111 +#: f545461682a746cf96c20ce63d030058 +msgid "Luciano Resende | IBM | @lresende" +msgstr "" + +# 8866787cffa8479d90cebf2e4e093ddb +#: ../../source/community/community-call-notes/2019-march.md:112 +#: ae22fa26bcf24ffbb396fa86d98405d3 +msgid "Tony Fast | Quansight | @tonyfast" +msgstr "" + +# c1a675c15f0e405abb5451925bcdfca2 +#: ../../source/community/community-call-notes/2019-march.md:113 +#: 5f4623d2c9d145b9905b1beed74ab881 +msgid "James Slack | University of Edinburgh | @jamesaslack" +msgstr "" + +# b2706534998848e79d847b02b2505493 +#: ../../source/community/community-call-notes/2019-march.md:114 +#: 9a8e73a8ef0e4de59fa66846d08285e9 +msgid "Erik Sundell | Sandvik | @consideratio" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:3 +#: ef96257bce034620b8b34e6a72d368b7 +msgid "May 28th, 2019" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:5 +#: fc4c8aa5509245b4ac692fb2b6c1b5ac +msgid "" +"**Date:** 28 May 2019 at 9am PST (your " +"[timezome](http://arewemeetingyet.com/Los%20Angeles/2019-05-28/09:00/Jupyter%20Community%20Call))" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:7 +#: 1e78dca1d70544809d52ed78e6c4c1bd +msgid "**Link:** [Youtube Video](https://youtu.be/mqZCa8j2K4s)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:10 +#: 76ca52a8ec724a94b4e6a0a30b86819c +msgid "Welcome to the All-Jupyter Community Meeting" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:22 +#: 6782b88588d9408283e5be1967997763 +msgid "" +"Hello from [The Turing Way](https://github.com/alan-turing-institute/the-" +"turing-way) Book Dash :books::dash::dash: in London. This call is right " +"at the end of a day of 18 people working together to improve the openly " +"developed [Jupyter book](https://github.com/jupyter/jupyter-book/). Our " +"goal is to make \"Reproducibility too easy not to do\" " +"(:laughing::grimacing::scream_cat:), build a strong and supportive " +"community, and give people the knowledge and confidence they need to " +"contribute to open source projects [name=Kirstie & Turing Way team]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:23 +#: 68cca030baf54e388fd3981b961323c7 +msgid "GitHub repo: https://github.com/alan-turing-institute/the-turing-way" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:24 +#: a15b0f889e594cfdacd4bed66ed7a297 +msgid "The book: https://the-turing-way.netlify.com" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:25 +#: 9805667c390b4168bfd09b4fabfe88fd +msgid "Chat room: https://gitter.im/alan-turing-institute/the-turing-way" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:32 +#: 6f84eb30685f4aee81c2809d8388e896 +msgid "Feedback and report from Research Software Reactor Sprint [name=Sarah]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:33 +#: c0679b1270ce40aaa4ac90d9e5508e13 +msgid "" +"Event website: " +"https://www.microsoftevents.com/profile/form/index.cfm?PKformID=0x6927743abcd" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:34 +#: 637384c4e2294cbeacfc9b0f15effb0f +msgid "Project list: https://github.com/research-software-reactor" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:35 +#: 0c93328bbe024ec29899fae6d0b11d15 +msgid "" +"New binderhub in the world :baby: :confetti_ball: " +msgstr "" + +# cb3cf9c7532e4eefafef21622f5e5ee3 +#: ../../source/community/community-call-notes/2019-may.md:36 +#: eb5114fafbf24913b293b355fbc2d2c2 +msgid "" +"Feedback and report from Jupyter Server Design and Roadmap workshop " +"[name=Luciano]" +msgstr "" + +# cf170dce042a4fa9af4aa3c97080a854 +#: ../../source/community/community-call-notes/2019-may.md:37 +#: 02485a78fcd54e39be8abb2b60f0212d +msgid "sponsored by bloomberg" +msgstr "" + +# dfc0167e90054f48a87ca906289e5aae +#: ../../source/community/community-call-notes/2019-may.md:38 +#: 9e5f0ac32fbb4f7fa3ba73b9a2cad644 +msgid "thomas, kevin, etc." +msgstr "" + +# db8c534028974a04b8cca41a4635a4ff +#: ../../source/community/community-call-notes/2019-may.md:39 +#: 5624a6bc5f5242f89878fb38d9f69974 +msgid "functionality directions, high-level roadmap" +msgstr "" + +# 45971081706749199a95955a04941bc9 +#: ../../source/community/community-call-notes/2019-may.md:40 +#: fd0fc23589a94272ba2f45b101d492f9 +msgid "decouple frontend from backend: notebook, lab, nteract, voila" +msgstr "" + +# 8aab688ea9044652812de80acf7c4c4e +#: ../../source/community/community-call-notes/2019-may.md:41 +#: b5d533b6d8834002a41e70a2016ae46b +msgid "using the backend functionality, providing different UIs" +msgstr "" + +# ecdc0515ad3943ae97090a26a85c22f5 +#: ../../source/community/community-call-notes/2019-may.md:42 +#: d261ea2c797e410c83515cd6ce3a6963 +msgid "how do we accomplish that? jupyter_server extension points" +msgstr "" + +# ee80afd9ea044c49bbb6cec9742a3c90 +#: ../../source/community/community-call-notes/2019-may.md:43 +#: d2d441452e0641e4902c74bba6022bf6 +msgid "ui" +msgstr "" + +# ce36561a4e624c489f77ec0508c37264 +#: ../../source/community/community-call-notes/2019-may.md:44 +#: b4669cf8468a442881aa05132e2c6558 +msgid "backend" +msgstr "" + +# c67c120c090f4978a8fe171269f0c269 +#: ../../source/community/community-call-notes/2019-may.md:45 +#: ae3912c42e7c408db51806e29f68f4c0 +msgid "handlers" +msgstr "" + +# cf7a63882a10418fa6eda0ed55f9a59c +#: ../../source/community/community-call-notes/2019-may.md:46 +#: d55fd3eeeb8f443b8d3c06305b00cb35 +msgid "roadmap" +msgstr "" + +# ad54ad19c71741e1bd1b5c099f7bd084 +#: ../../source/community/community-call-notes/2019-may.md:47 +#: f0e46f44700d42ef922dd631616207b3 +msgid "phase 1: integrating with existing uis (notebookclassic, lab)" +msgstr "" + +# 54edb5a787fa43028b0eccc811ed2222 +#: ../../source/community/community-call-notes/2019-may.md:48 +#: 4ccfab3b474543bea55397da7724992f +msgid "phase 2: expand functionality" +msgstr "" + +# 82642dd5ee114d6c8d96581165506242 +#: ../../source/community/community-call-notes/2019-may.md:49 +#: b8e517d78386451a8bb192cabd1fc805 +msgid "" +"kernel provider pr (e.g. different kernel managers, like Enterprise " +"Kernel Gateway)" +msgstr "" + +# 37fa4b509f17412cb5196f304f3fd903 +#: ../../source/community/community-call-notes/2019-may.md:50 +#: 3aa278295f1342ffb71e27c68bab9519 +msgid "next steps:" +msgstr "" + +# 0a7f05066f404c538534e1f60d6355fa +#: ../../source/community/community-call-notes/2019-may.md:51 +#: f7638a4571854e7f881fa799b45b1162 +msgid "pr from zak" +msgstr "" + +# cd233eff74d549d79448285aa6e25862 +#: ../../source/community/community-call-notes/2019-may.md:52 +#: 29c482781ed94f249cdc9906d511ddcd +msgid "blog post (illustration)" +msgstr "" + +# b249ab49156e44e7904ea94a0cf0c3ea +#: ../../source/community/community-call-notes/2019-may.md:53 +#: 6d2e4aac0bea4ca7876091f1c8375283 +msgid "biweekly calls" +msgstr "" + +# 97d3aa18a57e4580a09ae4293ebd813e +#: ../../source/community/community-call-notes/2019-may.md:54 +#: 8a1bdd685f8142c1b3c1840786094550 +msgid "timeline:" +msgstr "" + +# e0ffef45c88f42cca859c993d36753b8 +#: ../../source/community/community-call-notes/2019-may.md:55 +#: caca55f02c88488aa11ef60a70ddf300 +msgid "6.0 release of notebook?" +msgstr "" + +# adffe082166f4c5f89c55f67f4b41e6f +#: ../../source/community/community-call-notes/2019-may.md:56 +#: 9434409f29744be8953e2c0be3c4240d +msgid "post jupyterlab 1.0?" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:57 +#: 271a32f9162a4efda317569f321b2a72 +#, python-format +msgid "" +"Qt(5.6)-based PDF output from JupyterLab (0.35) Quick demo of using " +"QtWebEngine to load a notebook in lab and make a PDF. $_{n+1}$th time's " +"the charm! " +"[![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/deathbeds" +"/nbconvert-pdfqt/master?urlpath=lab%2Ftree%2Fnotebooks%2Findex.ipynb) | " +"[issue](https://github.com/jupyter/nbconvert/issues/1031) | " +"[repo](https://github.com/deathbeds/nbconvert-pdfqt) | [name=Nick]" +msgstr "" + +# 1ba7041adbf8498ebcaf7bfa6b1be2ed +#: ../../source/community/community-call-notes/2019-may.md:62 +#: c334a58748314d63bcc8e34064de34d8 +msgid "" +"If you are joining the All-Jupyter Community video meeting, sign in below" +" so we know who was here. Roll call:" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:64 +#: 20609c1a7439486dbe7b15941a98606d +msgid "| Zach | Jupyter Cal Poly | @Zsailer |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:65 +#: 40bc982c318a43c6b5946004f63e9e15 +msgid "| Amit | ReviewNB | @amit1rrr |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:66 +#: 1407c78e4e494d62bff69d8da2954adc +msgid "| Kirstie | Alan Turing Institute | @KirstieJane |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:67 +#: 7832eb6a653840f780cf4fa6bb286c11 +msgid "| Pete | Thorn | @parente |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:68 +#: 65f5790bef3640f288ce4866cbc52398 +msgid "| Tony | Quansight | @tonyfast |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:69 +#: f52fff01833c473ea3b6dfc61f6d9b72 +msgid "| Nick | GTRI | @bollwyvl |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:70 +#: 218d8e3fc3af4bb7a0a3256c60f213c6 +msgid "| Luciano | IBM | @lresende |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:71 +#: db65d82103a949fdba6a022cfc253014 +msgid "| Sarah | The Alan Turing Institute | @sgibson91 |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:72 +#: 2030c5483bd649f7ba44b9367c4a115f +msgid "| Saul | Quansight | @saulshanabrook |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:73 +#: 8d939a88d69c4452887e4f401d32aaae +msgid "| James | MUN | @jmunroe |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:74 +#: aca4273e6b43465499d0c6c973cf1645 +msgid "| Darian | Two Sigma | @afshin |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:75 +#: 53965252be9b415683d52429a70b404b +msgid "| Matthias| UC Merced | @carreau |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:76 +#: c05558ce32b74afb98afeb7a6642bb36 +msgid "| Tania | Microsoft | @trallard |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:77 +#: 6539ef46a2d54497a097ce87cd091852 +msgid "| Carol | Project Jupyter | @willingc |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-may.md:78 +#: 6be42f08b5254317ac896e3ce0fb349b +msgid "| Chris | UNC-Chapel Hill | @cbcunc |" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:3 +#: 0c4d308d015c47c8b08bbdb2e9162e20 +msgid "September 24th, 2019" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:5 +#: d520a885caf3480ca093e9c9dba23cd7 +msgid "" +"**Date:** September 24, 2019, at 9am Pacific (your " +"[timezone](https://arewemeetingyet.com/Los%20Angeles/2019-09-24/09:00/Jupyter%20Community%20Call))" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:7 +#: f6745ee9b0144ab497d4558370ad10dd +msgid "**Link:** [Youtube Video](https://youtu.be/so9F-Ha4q4U)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:19 +#: 19630c88252d400fa920c028add875e5 +msgid "" +"[Co-locating a Jupyter Server and Dask Scheduler _By Matthew " +"Rocklin](https://blog.dask.org/2019/09/13/jupyter-on-dask) " +"[name=tonyfast]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:21 +#: f5a7c0ef7875421f9204c13da50f7931 +msgid "" +"[Language server " +"protocol](https://github.com/jupyterlab/jupyterlab/issues/2163)" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:22 +#: 852c6aebd411407692c8f4790d28da45 +msgid "" +"[current work on jupyterlab-lsp](https://github.com/krassowski" +"/jupyterlab-lsp) [name=krassowski]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:23 +#: 57f045a8d95042539fabf4f610f53624 +#, python-format +msgid "" +"[wip binder](https://mybinder.org/v2/gh/bollwyvl/jupyterlab-lsp/add-" +"traitlets-proxy?urlpath=lab%2Ftree%2Fexamples%2FPython.ipynb) " +"[name=bollwyvl]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:29 +#: f98899d66f52431bb6cabefb6afa72ca +msgid "" +"**[importing notebooks with " +"`importnb`](https://gist.github.com/tonyfast/15c6ac8f005a5522291f08d95619e085)**" +" [name=tonyfast]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:31 +#: 7201ad1d33164bd3a10959d0ffee50bf +msgid "" +"_[`importnb`](https://github.com/deathbeds/importnb) provides easy, " +"flexible reuse of IPython notebooks from other notebooks, `.py` scripts " +"and libraries, and even the command line._" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:33 +#: 83adc6d412c24c2393ed1e3e823993af +msgid "" +"**[🤖 RobotLab: a one-click Jupyter and Robot Framework " +"environment](https://github.com/robots-from-jupyter/robotlab)** " +"[name=bollwyvl]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:35 +#: 76a7a112b2cd4fdca12bb2c6ae0ef8c9 +msgid "" +"_`RobotLab` was built to support a workshop introducing [acceptance-test-" +"driven](https://en.wikipedia.org/wiki/Acceptance_testing) development and" +" robot process automation with [robotkernel](https://github.com/robots-" +"from-jupyter/robotkernel), a [Robot " +"Framework](https://robotframework.org/) kernel, in JupyterLab. It is " +"built with [conda](https://github.com/conda/conda), " +"[constructor](https://github.com/conda/constructor) and [azure " +"pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines). " +"You can use the [installers](https://github.com/robots-from-" +"jupyter/robotlab/releases/tag/v2019.9.0) to learn how you can use Robot " +"Framework and Jupyter, or adapt its pipeline to produce your own, cross-" +"platform installers_" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:38 +#: 031b109121874d98b7c765815db82116 +msgid "**Project Drawdown** [name=dgentry]" +msgstr "" + +#: ../../source/community/community-call-notes/2019-september.md:39 +#: e386ab28d7f34ceaa9e1e6517b3d5599 +msgid "" +"_Project Drawdown is a global research organization that identifies, " +"reviews, and analyzes the most viable solutions to climate change, and " +"shares these findings with the world._ _We'll show current state of " +"climate solution models using Voila and JupyterHub, and ask for " +"suggestions about git operation driven from the Notebook._" +msgstr "" + +# 56a88190763a4b149eaea8fc6eaf3d8d +#: ../../source/community/community-call-notes/2019-september.md:48 +#: aa940d0bee0c4049abeaf8e3ad6644a6 +msgid "Denton | Project Drawdown | @DentonGentry |" +msgstr "" + +# 09a6d7c4ff3d4ee5b3d73e9eab227531 +#: ../../source/community/community-call-notes/2019-september.md:49 +#: 0d0ee777b6f8426bb97f67a5886d29b9 +msgid "Nick | GTRI | @nrbgt |" +msgstr "" + +# 2aea07b7205241f68da015e495e392fe +#: ../../source/community/community-call-notes/2019-september.md:50 +#: 765eeda542114356843fe60f1519ade5 +msgid "Chico Venancio | BMC Group K. K. | @chicocvenancio |" +msgstr "" + +# 2ae4c693876a4d6db1252ced76c5a611 +#: ../../source/community/community-call-notes/2019-september.md:51 +#: c9635a8fb5be4c30bb7b30d295d7b351 +msgid "Tony Fast | Quansight | @tonyfast |" +msgstr "" + +# 2e782ce8de7a492984bc64cdd2b084f6 +#: ../../source/community/community-call-notes/2019-september.md:52 +#: 7930c162d9b34f1cb3305a754b15257e +msgid "Wayne Decatur | Upstate Medical | @fomightez |" +msgstr "" + +# 74fc5744ec6642d483b911cb4b1e031b +#: ../../source/community/community-call-notes/2019-september.md:53 +#: 54d1eb0a30dc4613a1fb7d06dd3f7f0c +msgid "Kevin Bates | IBM | @kevin-bates |" +msgstr "" + +# 6bd6bb6774b1433f8f1bf98b08d6725f +#: ../../source/community/community-call-notes/2019-september.md:54 +#: bd337ee87cae428fb45d85a42941cac5 +msgid "Carol | Jupyter | @willingc |" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:1 +#: 5253776937394a8ba73a3a43d92b9485 +msgid "Jupyter Community Call December 15th, 2020" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:3 +#: 8cbacd2006b54b6bb6cb3fc7ec0a52f5 +msgid "" +"**Date:** December 15, 2020, at time 9am Pacific (your " +"[timezone](https://arewemeetingyet.com/Los%20Angeles/2020-12-15/9:00/Jupyter%20Community%20Call))" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:5 +#: a4b51861585447e5a023c08b4f87d173 +msgid "" +"[Discourse](https://discourse.jupyter.org/t/jupyter-community-calls/668) " +"[YouTube Link](https://youtu.be/IlYP6q2H1M8 )" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:8 +#: ../../source/community/community-call-notes/2021-april.md:9 +#: ../../source/community/community-call-notes/2021-february.md:9 +#: ../../source/community/community-call-notes/2021-january.md:10 +#: ../../source/community/community-call-notes/2021-march.md:9 +#: 3bde8c99b1184f11853e31bdddd7b58d 83e56f32c77b4eb396a05d53d3e12217 +#: 8ee82791a16b4d6892bfb510c35c6f36 bcf93861a87c4786aa5c905e3c407c18 +#: cf73fbe5cc6f49edae25f3018424bb6c +msgid "**Please note:**" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:9 +#: ../../source/community/community-call-notes/2020-november.md:11 +#: ../../source/community/community-call-notes/2021-april.md:10 +#: ../../source/community/community-call-notes/2021-february.md:10 +#: ../../source/community/community-call-notes/2021-january.md:11 +#: ../../source/community/community-call-notes/2021-march.md:10 +#: 2fe47c6de6cb450fb547f76774e17523 5492da1a5a6743319d23dbd3c6e63d02 +#: 91c60902a7624736955b87057a6eb1eb 962bab134b70416ca8df19a0db33b2d8 +#: 977a1d8ce3c64ca597d9b9252b58783d b64a4f0b42be408f90345549366b6f0d +msgid "" +"Community calls are recorded and posted to this " +"[playlist](https://www.youtube.com/playlist?list=PLUrHeD2K9Cmkoamm4NjLmvXC4Y6E1o8SP)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:10 +#: ../../source/community/community-call-notes/2020-november.md:12 +#: ../../source/community/community-call-notes/2021-april.md:11 +#: ../../source/community/community-call-notes/2021-february.md:11 +#: ../../source/community/community-call-notes/2021-january.md:12 +#: ../../source/community/community-call-notes/2021-march.md:11 +#: 15864878c83e4cc1a890ceff059a4d02 4f8aa83ff36747519c525780a30a382a +#: 79cf1d6f86ed49c6af7841a2a759a3d0 7d22795a84bd4163b06cdfc9433acd1a +#: b55c1e916e99421f9b93bbd6b55dfa10 d7eac30d41a7436fb35c4059a4353e98 +msgid "" +"These notes will be recorded and posted " +"[here](https://jupyter.readthedocs.io/en/latest/community/community-call-" +"notes/index.html)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:11 +#: ../../source/community/community-call-notes/2020-november.md:13 +#: ../../source/community/community-call-notes/2021-april.md:12 +#: ../../source/community/community-call-notes/2021-february.md:12 +#: ../../source/community/community-call-notes/2021-january.md:13 +#: ../../source/community/community-call-notes/2021-march.md:12 +#: 19408e9c12eb417dbc86fdaf71275503 34e96a33b1914a6e82c944b280a03208 +#: 60410c0042cb4dc383ee98119e9d2b82 6acb81cbce504d5890c3c98bd62d1118 +#: 8ad3060569084dfba6fa0a8a1242148a e13fc8065f114eeba236627d2cfa9215 +msgid "" +"Everyone present is held to the [Jupyter Code of " +"Conduct](https://jupyter.org/conduct)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:19 +#: 7c899239445f4ab69173c0cd93ff8eaf +msgid "Short reports, celebrations, shout-outs, PR of the month" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:21 +#: ../../source/community/community-call-notes/2020-november.md:23 +#: ../../source/community/community-call-notes/2021-january.md:23 +#: 1f3ef01cfd13470eb283fde46e4547a7 47e3671deb524abf9b8129f411d0cd5c +#: cdafd0299e95400bbd3b0679b997d8a8 +msgid "" +"This is a place to make short announcements (without a need for " +"discussion)." +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:23 +#: 2246fcdca12d4bf6bdb96de735d7b412 +msgid "" +"**[Accessibility testing for docs](https://github.com/pandas-dev/pydata-" +"sphinx-theme/pull/294)** - _Nick_" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:24 +#: b0efd153179d4b509419d0db973c0751 +msgid "" +"WIP PR to show a way forward to establish and maintain an accessibility " +"roadmap for Sphinx-based documentation sites" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:25 +#: 8a040dc6cb764ea698b523a745a714c1 +msgid "" +"**[jupyter-starters](https://github.com/deathbeds/jupyterlab-starters) " +"0.6.0a0 released** - _Nick_" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:26 +#: b8f0020e3ea5490b8cce32e3e317b84c +msgid "a tool for defining JSON Schema-based workflows in JupyterLab" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:27 +#: e9f146a30ca54a18a4036ef23e88e5c4 +msgid "Thanks to everyone who gave feedback on last month's call! - _Isabela_" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:28 +#: 3e56c8c845a143c497231e23436b7cc3 +msgid "" +"Check out @jtp's repos for [Jupyterlab-Classic](https://github.com/jtpio" +"/jupyterlab-classic) and the [p5js " +"notebook](https://github.com/jtpio/p5-notebook). I'm looking forward to " +"sharing with students and teachers at Playfest conference in January. - " +"_Carol_" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:29 +#: cf47485e752d4b93b277d445ff39252c +msgid "" +"Jupyter survey is now live! [Read more](https://blog.jupyter.org/survey-" +"jupyterlab-and-beyond-88c7fbd27a79) and [take the " +"survey](https://www.surveymonkey.com/r/LCB7GBF). - _Isabela_" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:36 +#: e15e3610d69d47cf8d9a021c80460400 +msgid "" +"**WXYZDVCS** Work-in-progress report on " +"[`wxyz.dvcs`](https://github.com/deathbeds/wxyz), a bridge from Jupyter " +"Widgets to distributed version control - _Nick_" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:37 +#: efb3bdbf280b4e42ae3bae9c5aaa3299 +msgid "" +"_Hopefully_ released this week 🤞, " +"[![][binder]](https://mybinder.org/v2/gh/deathbeds/wxyz/master?urlpath=lab/tree/src/py/wxyz_notebooks/src/wxyz/notebooks/index.ipynb)" +" works though!" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:38 +#: 3782986f6b6b491a8d14bdd4f21d9baf +msgid "Pierre's notebooks for teaching Python and data science" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:39 +#: 0c25bf75594e40b0a8c71e250941a74a +msgid "" +"[JupyterLab Classic](https://github.com/jtpio/jupyterlab-classic) - " +"*Jeremy*" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:43 +#: ../../source/community/community-call-notes/2021-april.md:57 +#: ../../source/community/community-call-notes/2021-february.md:35 +#: ../../source/community/community-call-notes/2021-january.md:49 +#: ../../source/community/community-call-notes/2021-march.md:45 +#: 16fbff2f4a5c4c598439fa8d8f6c9a0f 2ea3eb8059d844aaab972edeb88fa79c +#: 376e22fe63324fb189fb51f0e325377d 90479d2cc7f240629d709112e01b7639 +#: e73f27b767b44e96b40af83795ca0850 +msgid "Other Links Shared" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:45 +#: ../../source/community/community-call-notes/2021-april.md:59 +#: ../../source/community/community-call-notes/2021-february.md:37 +#: ../../source/community/community-call-notes/2021-march.md:47 +#: 6861aaea8154446985cf3f021cea0f9f 6a208fc0d5f54323b51e67b3966f18d7 +#: 9412960304694599a7bdc8c76984ebf4 d202213bb1f345e3ad154d328c664f01 +msgid "" +"This is a space to store links shared during community call discussions " +"related to or separate from the agenda items." +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:46 +#: 0bf97fb0cb0247e8af28a19fec9542f5 +msgid "[deathbeds/importnb](https://github.com/deathbeds/importnb)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:47 +#: 183328a3a0ae4c44a188e51d1d7a7045 +msgid "[mwouts/jupytext](https://github.com/mwouts/jupytext)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:48 +#: c7bad48a67fb442e8779140fc4883516 +msgid "" +"[QuantEcon MATLAB-Python-Julia " +"Cheatsheet](https://cheatsheets.quantecon.org)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:49 +#: 251bd6ae03714a44a91009f62c38129a +msgid "" +"[SQLite Jupyter kernel](https://blog.jupyter.org/a-jupyter-kernel-for-" +"sqlite-9549c5dcf551)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:50 +#: 44e06699e3de46f2807e6569c355a697 +msgid "" +"[2i2c](https://2i2c.org/) (brought up around support for JuptyerHubs in " +"education)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md:51 +#: f90f769daf9f488b996019b17968135b +msgid "" +"[p5 notebook example](https://p5-notebook.now.sh) (mentioned when talking" +" about JupyterLab Classic)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 18a7c1a78b7d417dbf21bca23241c9db 2c12eb27931d47fa96a69940cf8d53df +#: 6940ebdd26404d1b9150f92af2e7659c b5a51aa89e054fee843c935786aa870e +#: d64ea86dad0544d0999dba54a03f493a dd6d111a5cb84d96a3098a76dfd176a6 +msgid "Name" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 19b68a0fa6564d4d9df18a329973ec21 41aaf57aa9294198a0bc51bf754330f9 +#: 423b593b4d9840b797f4237d4d1eecab d6003ffdfb344198896af0e267cd0da6 +#: da8e46f9a0614d998baf423763269e58 fca0bef5137442b9a27474c1f79b6b4b +msgid "Institution" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 0ea599e4e83e43b09a77b162697ee632 6280586dfd994a79a430a8dd532f811b +#: a54af1487aa548ffaaec3ca00bbc4df0 b818f76c71ec4ce48f0a5e60c3b17ab2 +#: ea3d44e703af4f068afde5e6b26ece43 f0025da21fc34f3d8a7d7fe39b29dab3 +msgid "GitHub Handle" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 07ddb3c6dd1b4bacb312eb4f96fb9925 3c2cc1a4fef84dc9bdfad823d26d78f2 +#: 5556f532186c4c2986aef0581da33014 6d36f72534fa44a39f39fde0c3b6a924 +#: c77218c0c9684ebd841c702d69c914f1 +msgid "Nick Bollweg" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: a30f9261be474341b00521eb2478996c +msgid "Project Jupyter, GTRI, Deathbeds" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-march.md +#: 5d289acebd06451eb656256d3b724e85 a97f7ae073d946b3add1b55e4571e84d +#: eb87df0dd77a46b993d7b387e5b808be +msgid "@bollwyvl @nrbgt" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: 013caec9a2d44855bbae85de792cb6bb 20c1561274e741209e5af528c42b12ca +#: 466b5b73a9444859bb56de24891c243c +msgid "Steven Silvester" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 06b36c31a39d4a9aab90f52891df8271 746ef3241aa740878130ff312f6cace9 +#: 7dc749308910419dad7dbc71d3db81f1 a9ade143ba3849ea921634b31c3709b5 +#: af24b5fe8384491cb73de7ca5778ca42 f0551b824f024f099f21a050bf67dd69 +msgid "Apple" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: 4cf3be386da64aa297596c9d61e3c961 5ca2af90971e46909ed34f6ed0a98f0e +#: e50b66ca768b40bb8a717474338bfd7b +msgid "@blink1073" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-january.md +#: 4a3df5ced38644dc9e5244bd1eb736f9 6cc3146aae984b729578405ade71fb80 +msgid "Ryan Spencer" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-january.md +#: 1611d68504114a699142ac075f9dab9b df08d5e1808d4ac4b0d8d7d0c5b2e76b +msgid "GTRI" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-january.md +#: 232e060322634e12bd39cfbf0719511b e391756f2ef042e9a0fa915110b4b1fe +msgid "@ryspnc" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 0c93c0a692fb412981019881f04b7153 6d88292c20664b7cbfb9a9a1f4638ca6 +#: 96bf02a908c94964a7203ddd178e3568 c7fcd606a44d45da9dda8e0583a2c8ea +msgid "Simon Li" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 728c05106d404bcb992b3ed6ff25f1f0 be2fa8e080d1457ab5781c77f1eeecba +#: d2ea0099dfb846308b2b960138739729 fbdb635719d645eeb6df69707e909359 +msgid "University of Dundee" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 28131244f67a4978b31d27e5b32963b4 3dc4adb365bd40a59cfed0662d598312 +#: bb0c7909b54f498698b9bb8a0936ea1e e818874d1ded46d58ff5b64b2bb32f31 +msgid "@manics" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 57b8d57a1da147b695dced1f662837c2 e989f298f0234053a87208b805bd2af1 +#: edee461cc5424b36b9ffb8523a7e4ad0 +msgid "Wayne Decatur" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 634b215acdfa497a88f8b62797b24854 +msgid "Upstate Medical University" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 933403ce7cac4cb4b6f6bdaf8aa56706 bfeb0c709eed48c38d7f0b05b008bae6 +#: d99e3070c762461d95e746e5ce281119 +msgid "@fomightez" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 248ec8d9757148bf87c15c52f9308bad 2e27e3b254ac40be83b850ced3f8d5b4 +#: 69f4cefec0014487b24dbf1fafc7d331 c3b3f61d2f804a48b28b6d333070e713 +#: d3dc13b247c84f6dbddf40ed8adc70d2 +msgid "Pete Blois" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 00136f9e7ac444dc9a64a4870ae7ab72 748e28da6d924d83af126bbc27a7c75d +#: a14293f609794d78b11e00e12d4cef42 +msgid "Google Colab" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 3ec935a711f84a67b0a797306fce34a5 689b5fdcdcfa4844a2d3e5b075536e10 +#: 80c1f185d9804258847f6cc61cf562ee a8837b7ed9d94a9c9df224943ed7f291 +#: b47721d585a44afda516b6b35c881913 +msgid "@blois" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-march.md +#: 1317434808dc4c2295d741b1643abccc 4f3ac3fcfd9d493fa908f9ad224b37fb +msgid "Pierre-Olivier Simonard" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-march.md +#: 1b904ac7931b4560826e0acc9fc1aca9 3ce741163da641de866997e09176a50c +#: 4ffc4564eaa545f58a78e6dc46750071 55c8af7222294b3588c67d27844303da +#: d872c6135bff4b7ab2abc1b27efeaedf e06ebe0931fd4f249e79dbd6c0de4925 +msgid "Quansight" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-march.md +#: cdfb8c5801204ed790a43a5953c0472b de116a2e0ae7496abda99e9d8478d39d +msgid "@pierrotsmnrd" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 63ca63a68c6a42c18147531a562ebe1d +msgid "Ryan C. Cooper" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 279d920e1cfc44d5979d11103ec7f438 +msgid "University of Connecticut" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 00905c34d78548208f66c892a418ba6c +msgid "@cooperrc" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-january.md +#: 0ce5254641e14f78b37fe58aec29a415 da05a38632fb4e698e6a6b0e4887e22f +msgid "Raman Tehlan" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 6237b419dbb54bcca951e5acfba60bab +msgid "nteract" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: cdd987de7c7f4e6e9093cc7d5251dfc6 +msgid "[@ramantehlan](https://github.com/ramantehlan)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 54444c5feeb645fcb455c872fe974ee4 60895653160d4ed7a33e47cbe94b3ca7 +#: 91e53af8e63a422e9d056f71ed7ba613 b5af318b40b440329e11ef5d602e0697 +#: e7dee5a45686405ab8b41cdad7931ea4 +msgid "A. T. Darian" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 3c38075bc9fb4291ad2695792b57e40f 4a6c91e6388a4d4b914f714256fb9f97 +#: b36ae48a67b84a10bc60be775f1055a0 cd46472828f946b0a7a8ad3ffb95b516 +#: fa789e66b7274292a42470acef6c0440 +msgid "Two Sigma" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 699573aca8d14cb49a6f4609fe02b025 969eb7c732a84e4a8d9779c6c80313f4 +#: b19910971ab748b0ba7241b882bd48f8 c1dd407f7e3d4a908b6dd9ee9385f5f8 +#: cf1af6d6f69b46c684ddc619be6450f0 +msgid "@afshin" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: 144e3a2c3bc14aff83dc37dabea4781b 1f272102c60a4d7caa71fd38f2ab6ff7 +#: d18df4daf11e4a1ca9a96acafb3e16bf +msgid "Jeremy Tuloup" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: 44f5492009684c04bc02645bfce643dc 4d05ffa550b04547baf4e2e6790bf6d6 +#: c72adcd664fa4df29f766d65e26f3139 d92b5c85a9e84db68b535a32e86bee88 +msgid "QuantStack" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: 64738975ffc04b2b97549c2f2bd9b1ba 6c6d9095cc8d41619a3c5a10600ed7fc +#: ac57e7dcd6f74a1ab5fb1470b7b5ffb5 +msgid "@jtpio" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: 4e0da656314b4ec282a5e1851a57b570 8ae44f7b79c848cc932848f662204dd5 +msgid "Damián Avila" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 0f91bea329354e988899de10c71ef791 +msgid "UMSI-MADS" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: 153876c058354b61aa36fac95b31491c 48787deaa9c347ccb016593b69f63142 +msgid "@damianavila" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 6ed5ed7b17fe4e438c4c850d0d6d81fa +msgid "Tim George" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: fdeccdceb9724debac866a6d425a0194 +msgid "Freelance" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 4486b63d5789468598ef274dcb7b9bd2 +msgid "@tgeorgeux" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: d0f6303f22854238bc24a8e5fb3792bd +msgid "Gonzalo Peña-Castellanos" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: 1900bd24037740ea9d87d2595b272f4c 79d19bf0f0aa48b0ae5e1782c0096956 +msgid "@goanpeca" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 2bfdea3aa8394a82b64225340b93d34d 402e105a61534555ae1d87b549378c8a +#: 9be60ec9bad54b0781e3a1f8aedee4df e14b96639e274cf2b0ba31d101686906 +#: fdba89e48e3f43dba9022eed0d75d201 +msgid "Zach Sailer" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 02696f87044042d7b825af7d9b54ee1f 3600118e00954e81ba669760b37e4448 +#: 763a696fa5be463198ec6de793228998 938747cf5f2b42619808ba750f49aa19 +#: de2111e3a27747f49a51baa74b758565 +msgid "@Zsailer" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 29c77f024ac04448ab6450776393caf3 57b3ce9ea7964f0888f9aa6188e7885a +#: a5ea27d733a04bb5b07e5ad13ea58120 +msgid "Carol Willing" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: efd5efca4b20403f91e7bc6b5341ae2d +msgid "Jupyter, noteable" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 025eb6f08f874abdb7bc61c85df74717 4b6a01ac3d2b44f386f2db4e79592164 +#: 8d06cb2740ff4dac8090f10cc907152a +msgid "@willingc" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 819b93b7cdd04e4db48022eceb48fb76 +msgid "Sarah Gibson" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: d0df2d7d16e14c5184f0bc989fc39d60 +msgid "The Alan Turing Institute" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 07435982563a4deda973bd2fa35a5d8f +msgid "@sgibson91" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 8487bf242fad46ec8fe211777fa40e23 +msgid "Sharan Foga" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 4b064a15bf4c42b4a0cd8df9aaf18493 +msgid "None" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: 8098da2a3ae642a3b9da11968e8d9d38 +msgid "@sharanf" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: bfb2d1669a264d8e9487a508c5216b59 +msgid "Tania Allard" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: b40da8e839c64aaebca9bcc8d0666ee1 +msgid "--" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: a104c57d32db4838898574232349e7bb +msgid "@trallard" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: 9b1a260805cb4af4919928d406a8214f baa700ef2a9f41c395826c9e7cd9c44e +msgid "Tony Fast" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: 441489e508424ed1b9770de5d6cbaca6 6def4b2821044092b122f28889bda4e0 +msgid "@tonyfast" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 2af2b70044324cf3b16935b69f9c84ec 77ae10c65e9246bf8009894be2313fc1 +#: afa4c243bd0749f8a4b51a34b7a3b475 b5cb0f8d80f34f748362588554945ee9 +#: cc26a4b2b1634ae9a2cf1d2d1f1c6341 fd2de76631764efeaa29d5578e96960e +msgid "Isabela Presedo-Floyd" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 25ebfd7432d841eb9d6157b2959a0e89 93d14c3cd4fe460d8a6a0f071ba0dd91 +#: c7694fa77fc244408e16144bb75b5b3d caef43056fb24f69b26506c6b904e49c +#: de958822f9da407f881a80790c169adb +msgid "Quansight Labs" +msgstr "" + +#: ../../source/community/community-call-notes/2020-december.md +#: ../../source/community/community-call-notes/2020-november.md +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 599a4a5142664694b05e39dd2187907e 7859a9d6c60c4bc0815d9f004355ecf5 +#: 857e00e6cad84a88ab64698fda406d9c 973e0df3e97a4aba9ef65c0d101e4d0c +#: ce52ab5dd8f64706bcce38e90d6452ff f4c5a7a3e16e4e1997888329ddaac3ea +msgid "@isabela-pf" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md:2 +#: 7fdf80378fb3426cae32d1080de0a6b1 +msgid "November 17th, 2020" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md:4 +#: 3c1ed3bd86e248678bef3b0f44ad9731 +msgid "" +"**Date:** November 17th, 2020, at 9am Pacific (your " +"[timezone](https://arewemeetingyet.com/Los%20Angeles/2020-11-17/09:00/Jupyter%20Community%20Call))" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md:6 +#: 18347d3adf4d41ec9055d6afe9b871a4 +msgid "" +"**[Discourse](https://discourse.jupyter.org/t/jupyter-community-" +"calls/668)**" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md:8 +#: 3e4f9a4faf6d48318af3946968b72849 +msgid "**[Youtube Link](https://youtu.be/bko-v1ZZoig)**" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md:10 +#: 7635bcc41cdb4ef3bc74883f5482bad4 +msgid "**Please Note:**" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md:25 +#: 9c098a81dd9d470aac92fd625b7002c6 +msgid "" +"**Zach** Shout out to Isabela for reviving the Jupyter Community Calls " +":tada:" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md:31 +#: e660c925ab7a46058ffd9cd61fe67d7e +#, python-format +msgid "" +"🦌 [IPyElk 0.2.0](https://github.com/jupyrdf/ipyelk) [![binder-" +"badge](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/jupyrdf/ipyelk/42db3e3?urlpath=lab%2Ftree%2Fexamples%2F_index.ipynb)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md:32 +#: abd56c9a81ef47f9beba296dfff040b4 +msgid "" +"Jupyter Widgets for interactive graphs _at scale_ powered by the [Eclipse" +" Layout Kernel (ELK)](https://github.com/kieler/elkjs), " +"[sprotty](https://github.com/eclipse/sprotty), " +"[networkx](https://networkx.github.io)." +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md:34 +#: b43e62ca069343f2b906261354b9f4f1 +msgid "" +"[dgaf](https://github.com/deathbeds/dgaf) (deathbeds generalized " +"automation framework)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md:36 +#: 1ec1b5b7643a402e9373ef9e13fe374b +msgid "" +"**Eric** [What is a " +"Jovyan?](https://jupyter.readthedocs.io/en/latest/community/content-" +"community.html#what-is-a-jovyan)" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md +#: cb21bf0e7d184333af02a294732c1ee1 +msgid "Jupyter, Deathbeds, GTRI" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md +#: 381aa741897f4bb4b0ea4afea694ea40 +msgid "tony fast" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md +#: e56194cc76934569849fccc0746a51db +msgid "@deathbeds" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md +#: 632af7ebc5b34e9aa24f901a581261bc +msgid "Eric Charles" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md +#: fbef85797bbb4b7b8c1d715f3beb6654 +msgid "Datalayer, Quansight" +msgstr "" + +#: ../../source/community/community-call-notes/2020-november.md +#: e83db0421701402eb9734b87185e2912 +msgid "@echarles" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:1 +#: 20e33bbbe2454ead9039b22d283b0dcb +msgid "April 27, 2021" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:3 +#: 2325941547b346639f0c2a4e1ea87222 +msgid "" +"**Date:** April 27, 2021, at 8am Pacific (your " +"[timezone](https://arewemeetingyet.com/Los%20Angeles/2021-04-27/8:00/Jupyter%20Community%20Call))" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:5 +#: ../../source/community/community-call-notes/2021-february.md:5 +#: ../../source/community/community-call-notes/2021-march.md:5 +#: 2cd0b68fb7da43daba92c2bfc09c0f28 7f61d6c5ddce49e9bfd641e0518fe4cd +#: a5f026f1d9c8454796c2d75357d85a37 +msgid "" +"[**Discourse:**](https://discourse.jupyter.org/t/jupyter-community-" +"calls/668)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:7 +#: 51d413762bac42309c725e8be4eb011f +msgid "[**Youtube Link**](https://youtu.be/k-oaQG459A0)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:22 +#: 78f897d964814971aa74d6c3a62bb699 +msgid "" +"**Loïc Huder** New release of [jupyterlab-h5web](https://github.com/silx-" +"kit/jupyterlab-h5web) that brings HDF5 file exploration and visualization" +" to the notebook." +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:24 +#: 0c4aa769cbe74c9eb3104bc2a5ab293e +msgid "" +"**Isabela Presedo-Floyd** As always, if anyone is interested in hosting, " +"co-hosting, or getting involved with planning a community call, please " +"reach out to me." +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:28 +#: fffd02c6382a41a7a05ea08c203c91d3 +msgid "**Jeremy**:" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:29 +#: 46fe1960f24a40e69830f2e4a129ea0e +msgid "" +"[JupyterLite](https://github.com/jtpio/jupyterlite), a JupyterLab " +"distribution that runs entirely in the browser" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:30 +#: 589d8b2e34c143a68b983363b97672bf +msgid "Many thanks to Nick!" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:31 +#: 8da48c198d4841b8b1ee1eb2174bd99b +msgid "" +"Try it online: " +"https://jupyterlite.readthedocs.io/en/latest/_static/lab/index.html" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:33 +#: 83a327bb685c4ffd91cecedf6b1f35ca +msgid "**Gonzalo** Internationalization workflow for extension developers" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:35 +#: 945788c30eb54e479987927ec80fc248 +msgid "Some feedback... :man-facepalming:" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:36 +#: 2e6d1204404746578e3611b0df761b54 +msgid "" +"![Text asking why there is a delay for publishing the language packs " +"needed for internationalization](https://i.imgur.com/mho6Ka9.png)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:38 +#: f2028c5b1e3844708538a1a5ef1573c7 +msgid "Releasing language packages :world_map::card_file_box:" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:39 +#: 7263e03fb9124fc7ab53fa351f4b4a3e +#, python-format +msgid "" +"[Current packages and state](https://crowdin.com/project/jupyterlab) " +"(showing first 10) ![The top 10 translations by percent completed are " +"Spanish at 100%, Chinese Simplified at 100%, Hebrew at 88%, Turkish at " +"86%, Brazilian Portuguese at 83%, Ukrainian at 83%, Japanese at 83% French" +" at 83%, Russian at 74%, and Polish at " +"60%](https://i.imgur.com/vNeRe8s.png)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:41 +#: eba3e041df1e4fe3bbab5519fe87f8b2 +msgid "Releasing Spanish and Chinese simplified today evening. :eyes:" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:42 +#: 6f90b19b9167465e92104d914ad9dcd5 +msgid "" +"Please attend the JLab dev meeting for more information on the internal " +"process for managing the translations and language packs." +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:44 +#: 659c4e8d6baa4b7e93ee75e9b6c22880 +msgid "Resources :books:" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:45 +#: e72e0ef5d8364d7c9dad0284196eb1a5 +msgid "" +"[Example PR to internationalize your " +"extension](https://github.com/jupyterlab/jupyterlab-git/pull/888) adding " +"internationalization to [Jupyterlab-Git](https://github.com/jupyterlab" +"/jupyterlab-git) extension." +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:46 +#: 9e66b1fa2f4046be940eca34775d20f6 +msgid "" +"[Yaml File to update on the language packs centralized " +"repo](https://github.com/jupyterlab/language-packs/blob/master" +"/repository-map.yml) to update on the language packs repository." +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:47 +#: c45a786a323c43089b3763e73d1932bb +msgid "[Language packs repository](https://github.com/jupyterlab/language-packs)." +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:48 +#: adef7253d5744a49a6ac5c471688406f +msgid "[Start translating on Crowdin](https://crowdin.com/project/jupyterlab)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:49 +#: eb3b520dfc5d4928813c96be71b40932 +msgid "" +"[JupyterCON " +"slides](https://cfp.jupytercon.com/2020/schedule/presentation/239" +"/bienvenido-bienvenue-welcome-jupyterlab-and-language-extensions/) - " +"[[Video]](https://www.youtube.com/watch?v=8-3eo1y5IrA)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:51 +#: ceee0b66f269445d8ca074098145b9f9 +msgid "**David**:" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:52 +#: ba20fc2eb929415f98756c2b79ca2587 +msgid "**Nbterm**" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:53 +#: f293b9df9c194a0e914916f49f3c90c6 +msgid "" +"[Blog: Jupyter Notebooks in the terminal](https://blog.jupyter.org" +"/nbterm-jupyter-notebooks-in-the-terminal-6a2b55d08b70)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:54 +#: 4c9f14cfb0eb4ef5b855f6355435c165 +msgid "" +"[Github Repository](https://github.com/davidbrochart/nbterm) ![Notebook " +"cell input and outputs represented in the " +"terminal](https://i.imgur.com/kzNyCno.png)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:61 +#: 9ed810bf874a44f9aa57edace90d5303 +msgid "https://github.com/jupyterlab/jupyterlab-hdf5" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:62 +#: 036dad91fd6e47aba503993a8e66509d +msgid "https://github.com/jtpio/jupyterlite/issues/41" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:63 +#: 69abc0d0a0d64f989f0e6b548aa2ba05 +msgid "https://deathbeds.github.io/jyve/lab/" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md:64 +#: 1b4682d212024509bc7bb6a9d4099bb4 +msgid "https://github.com/capytale/capytale" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 3e5d2c7dc47f412c86028786dad03412 3e8625e79038413e9a9365004e22cca3 +#: cae5ff2ac26741a09117113dd1c26847 +msgid "Layne Sadler" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: 2b8fca639fde4c9ea3dab47586de383b 88b0e919bf9a4d1a8fd32159ff1a5bc2 +msgid "AIQC" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 84e7a2e428454b5da0a9b7ea80d6f5e5 8f45d20792d54f12b41b00373676c778 +#: 99275305e7cc4273b2c7c13e768b38b8 +msgid "@aiqc" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: 2b881294df3b406a97bd0a929cdf3198 +msgid "Sylvain Corlay" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: 55f7cc53e356455f90241c52ad0d80dc +msgid "@SylvainCorlay" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: c31536c97dc04222a7e4c2e424c724cc d8e15ea722f4443f9a2e82c434d133f4 +msgid "Loïc Huder" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 473fc39706b04d559207d8be79bd99ca 60717e523b864d7f81171cc6106eeeb5 +#: e533506fb74042c2b0d633a0a1edf7d3 +msgid "ESRF" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 6a1e49b3e9a64d96b53336da8d8ed36e 8dc3e249ecfe48f6ab26939f5e90631f +#: ece0717fb39b4a5abaceb858653be3bc +msgid "@loichuder" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: c06004b238c140f78f48e91c1d036d15 +msgid "Claudia Regio" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: 39aee4b03dca45569d7bb6c94d80ce76 c3f176c7fc6643f6a4506b790032e6ab +msgid "@Microsoft" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: 264936b8e4c540adbd2d3846065a7c91 +msgid "@claudiaregio" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: e36f37fc31cd4c8f951e136d2b412869 +msgid "Joyce Er" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: 6f45528e62a44d2f8bc1bb4d2813a3b9 +msgid "@joyceerhl" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: 166b83f987784bac8af76372d4af94f0 +msgid "@QuantStack" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: 4bc349000a4e4507b660bb4e42d11445 78fd65c7107e4db8a477ba62507ed56a +msgid "@Apple" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: 29f7dda88fcc466eb55fbccb4df2b7d8 +msgid "Gonzalo Peña-C." +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: 6d13c8d0de944fa19bf066869e694882 +msgid "@Quansight" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: b43b6406e55c428bb2deee08ecf0153c +msgid "MADS & 2i2c" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: 334fa98ef53a4726b4466bdef7b3c990 5270f0bcdaaf4176b7ffe4c0a45f4647 +#: d178e9e20f134b989fbe663270c1600a +msgid "Google" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: 818403dd25b642238055f6059188fcd2 ec72db6f354540de828f105976b96c0e +msgid "Marvin Kastner" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: b2aa8379867f47429173e68f51b3f17e b9b3a7c4f1c4436fb8f267a1087b0de8 +msgid "Hamburg University of Technology" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: ../../source/community/community-call-notes/2021-february.md +#: 2bb4e02a2ad44a21902927191fc1bee1 52b30f06a38a4bb0b07d69fc6d661db7 +msgid "@1kastner" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: 3b51591e407d45d7976a384db2ad892a +msgid "David Brochart" +msgstr "" + +#: ../../source/community/community-call-notes/2021-april.md +#: 11992128b4bf48f08cf46dbe0e632db8 +msgid "@davidbrochart" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:1 +#: 3ac3c2207eef4f0ab1d72ef44ec614bb +msgid "February 23rd, 2021" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:3 +#: a45518b9076743059e0e1e8bcf41417b +msgid "" +"**Date:** February 23, 2021, at 9am Pacific (your " +"[timezone](https://arewemeetingyet.com/Los%20Angeles/2021-02-23/9:00/Jupyter%20Community%20Call))" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:7 +#: 2ee3bc8d7d474c1a87bce54253d82f69 +msgid "[**Youtube Link**](https://youtu.be/TG0w6WLunTk )" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:22 +#: f4b31fad29f7466ba8595afcb6db3b1d +msgid "" +"**Nick B**: Are you excited by... **JS license compliance**? Feedback " +"welcome on [lab#9779](https://github.com/jupyterlab/jupyterlab/pull/9779)" +" ([screenshot](https://user-" +"images.githubusercontent.com/45380/108773016-c25f4880-752b-11eb-945c-" +"32a20f2133b3.png))!" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:23 +#: 337a2de68d154a25955835f120a0a2c9 +msgid "" +"**Nick B**: The latest [Lab RTC " +"PR](https://github.com/jupyterlab/jupyterlab/pull/9785) " +"([demo](https://mybinder.org/v2/gh/QuantStack/jupyterlab/yjupyter?urlpath" +"=lab-dev)) is 🔥!" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:24 +#: 022df597d6f946d8927133b3ce1787b9 +msgid "" +"**Isabela Presedo-Floyd**: If you are interested in helping run or host a" +" community call, let me know (you won't have to do it alone :sunflower:)!" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:25 +#: 859f3d68261e4e97adee1fe32a0d52ac +msgid "" +"**Mike**: pyls fork [python-ls](https://github.com/python-ls/python-ls) " +"in cooperation with the Spyder team; preview of the changes to come in my" +" [personal fork](https://github.com/krassowski/python-language-server) " +"(**fast** and more clever autocompletion for [jupyterlab-" +"lsp](https://github.com/krassowski/jupyterlab-lsp)!)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:26 +#: b1e528beebf04b8d89581d6ff6e9b354 +msgid "" +"**Matt S**: [testbook](https://testbook.readthedocs.io/) had a talk at " +"PyCascades around unittesting Jupyter Notebooks." +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:30 +#: 0224bb9b2eb544b7abc9860587a756df +msgid "" +"**Loic Huder**: short presentation of [jupyter-h5web](https://github.com" +"/silx-kit/jupyterlab-h5web), a JLab extension to explore/visualize HDF5 " +"files" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:31 +#: 5f80828b68674f91b568fd3b351115db +msgid "" +"**Jagane Sundar**: short presentation of InfinStor's free hosted " +"Jupyterhub service (https://infinstor.com), a Cloud hosted free " +"Jupyterhub - our Jupyterhub service is free, you pay for Jupyterlab " +"instance resources consumed" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:32 +#: 594aa65a96f34ea8ac642d9ecacf9112 +msgid "" +"**Frédéric Collonval**: short presentation of " +"[papermill_report](https://github.com/ariadnext/papermill_report). " +"JupyterHub service to generate report from notebooks combining " +"[papermill](https://papermill.readthedocs.io/en/latest/) and " +"[nbconvert](https://github.com/ariadnext/papermill_report/blob/master/nbconvert.readthedocs.io)." +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:33 +#: fbec69054760408f9452c6280fe11ddc +msgid "" +"**Nick B**: " +"[demo](http://mybinder.org/v2/gh/deathbeds/ipydrawio/master?urlpath=lab/tree/docs/Poster.dio.svg)" +" of [ipydrawio](https://github.com/deathbeds/ipydrawio) (🍴 with 💖 of " +"[@quantstack/jupyterlab-drawio](https://github.com/QuantStack/jupyterlab-" +"drawio)), the full [diagrams.net](https://https://www.diagrams.net/) UI " +"(with all plugins, themes, shapes...) for Lab 3. Supports " +"`*.{ipynb,drawio,png,svg}` (plus `.pdf`, sorta)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:39 +#: 2da4d0c05fe54ed3a05c74bb2d700ac4 +msgid "agenda from [1/26 (last time)](https://hackmd.io/l2yBruUATC6yH4F2gOUPgw)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:40 +#: aee2de873e8b48a890fbf390c7f43dd8 +msgid "h5web" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:41 +#: 666451880ec5494ab2b4aed0fe556565 +msgid "" +"based on same backend as other hd5f extension, will share more code in " +"the future" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:42 +#: fe21fe56bd514ab89674445b538ab294 +msgid "other one's based on lumino datagrid" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:43 +#: 7c8d8c11691b40eb9168e1980cf75876 +msgid "" +"[merged cells](https://github.com/jupyterlab/lumino/pull/124) would be " +"awesome" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:44 +#: 2ea9bcf3ade747b894cb37ecb156f2dd +msgid "" +"keras: export [neural network " +"weights](https://keras.io/api/models/model_saving_apis/) as hdf5, " +"potential use case" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:45 +#: f0bcd623dbd54a91a8ac499c945fa0c0 +msgid "xray community currently" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:46 +#: 04d6628726b944aca23b12697919a4fc +msgid "viewer should work for all formats" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:47 +#: 21f766568fbe4201abde487362c249f4 +msgid "" +"[drug " +"discovery](https://academic.oup.com/bioinformatics/article/35/8/1427/5094509)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:48 +#: 1291020e13114b57b708f6e8238d47f1 +msgid "preventing jlab from sending all the data" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:49 +#: 2c7835b50af045ffa83cfc38eeb7ce46 +msgid "" +"quick fix: filetype `base64` to just send a little data (custom " +"contentsmanager?)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:50 +#: d5e7a095bb5245e2b862e60c7de77989 +msgid "would prefer basically _no_ data..." +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:51 +#: 0864e9a28a0e43acb88f2dcf7494669b +msgid "infinistor product" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:52 +#: 3332083254fd4237adcd9ea5d6074968 +msgid "hub" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:53 +#: 4e0fd57d221f4d2f9869503e830e14fe +msgid "custom spawner/authenticator (FOSS tbd)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:54 +#: 0ab122a84aee49d7915b9d78ed8302e9 +msgid "didn't want existing spawner (container/k8s)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:55 +#: c0bfc4c8cfef4f3f8dfa151d4cbd4b85 +msgid "vm interface granular enough" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:56 +#: 7310ddf566224dc8aef82862d5f36c1e +msgid "stoppable machines for lower idle cost" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:57 +#: b68d84d8e7de4b728b1f4dd97240ea73 +msgid "requires infinistor" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:58 +#: a73609f3982a4467b24826cf67bdac93 +msgid "aws auth" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:59 +#: 4e1813201101408c80d99ecf408f3076 +msgid "token refreshing" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:60 +#: 0f0b80e6357e487cb0db502bb7cd2d39 +msgid "hub runs on infinistor" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:61 +#: b11edf22ef744a258dfd0d5d0f06b80f +msgid "spawns in your own aws, shutdown on 15m of idle" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:62 +#: 9d408403a3a0479f853d32a9a7ea076e +msgid "stock Lab, BYO extensions" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:63 +#: daf7d610dad54e78a055eeac73cf9011 +msgid "custom tool for extensions" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:64 +#: d5bf787392ff4173ad0b01baa85d1fac +msgid "snapshots" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:65 +#: 6b9d1aae9eb549da9993b9c4ba688077 +msgid "dashboard" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:66 +#: e666794b841e46eca62d2ef34f2c3a3b +msgid "s3 storage" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:67 +#: 5653100aaa7d45dd8e5b7ece7bdef78a +msgid "users" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:68 +#: 85b4d935221b4200b5802e3c3483e0e9 +msgid "multicloud (aws, azure)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:69 +#: a7107dca348c4af69667480a8305605a +msgid "customize the python kernel?" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:70 +#: 16d0594afd574ddcb03a7f56a6680e13 +msgid "in backend, have transforms, use dockerfile, modify dockerfile" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:71 +#: 858e32e6cac94d7c891baceb0072f34c +msgid "stock open source distributions (pip, conda)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:72 +#: 547b5d17b7ea4ede92ffed4151f9ec0b +msgid "" +"[show and tell on discourse](https://discourse.jupyter.org/c/general" +"/show-and-tell/45)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:73 +#: 3280e480660243758b18e5f81923aacd +msgid "papermill_report" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:74 +#: b891a77417e34f63a75365ba212e944e +msgid "speaks python (other libraries could be added)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:75 +#: 0781e9210a72438c9101dc36269895e6 +msgid "install as a service on hub" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:76 +#: 3cc8d155692d4ea48d569e61dae8edc5 +msgid "pick notebook" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:77 +#: cfc0e3a69b7946659f92f2f44eea34af +msgid "fill out form from papermill" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:78 +#: 829ca315c2a94a3b9ee1e1ec0b3ec20c +msgid "click button, get report" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:79 +#: d9b5ff1655694e54baf66dd7a89a96b7 +msgid "shareable url" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:80 +#: 8de0b326d9b8492da2dc4676b8d2d3af +msgid "if break, get full traceback" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:81 +#: 62dac9af75db47f189cbe87dbf698331 +msgid "click to get annotated notebook report" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:82 +#: 03329378b7ed4c9bbe29ff24f47ff243 +msgid "next time: integration testing jupyterlab, screenshots w/ playwright, etc." +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:83 +#: 14a55b8002264e018b58867b1654572f +msgid "papermill inspect added for this purpose, first example of using in FOSS" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:84 +#: e9b6d116c6d74effaa75a3f745783bbd +msgid "multi-step wizard?" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:85 +#: dc02ebb9b11d41ce879277399988aa59 +msgid "schedulers" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:86 +#: 94fb45f35a1d49ec8201b32bed7c77c5 +msgid "cylc" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:87 +#: fa5578dac08844f0b2d4515c71e3147e +msgid "dagster" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:88 +#: 35f573b8e449433799f856d548ab6617 +msgid "prefect" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:89 +#: 4ebcf976c3684d5baf4289139d8c2d39 +msgid "hiding code?" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:90 +#: e0b0eabd97544278a68986e277431b22 +msgid "" +"nbconvert (use " +"[tags](https://nbconvert.readthedocs.io/en/latest/removing_cells.html" +"#removing-pieces-of-cells-using-cell-tags)?)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:91 +#: 97fcb450041d4113a65faef33cec09a0 +msgid "preprocessors" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:92 +#: 70ac7a4dbf4f43a2a4a24c8ce653ca19 +msgid "all standard stuff" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:94 +#: 89c037348ed141dab33e86a450da2ae3 +msgid "ipydrawio" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:95 +#: f55247d02aaa4e7f882d83fad01d7898 +msgid "" +"nb: most important takeaway: write the mimerenderer first, then it's " +"easier to write a widget/document" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md:96 +#: 2391deb61896499fafabf1d8e5a7cfc8 +msgid "More draw.io features available in notebooks" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: b314dce3560a4d60afefefa4028aea3d +msgid "Jagane" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 17880137193948379a065c30dc5dca57 82e4e69167a142bbb36e97f375a0a328 +#: 927293bbb8714f99bde725cd3db57c4c +msgid "InfinStor, Inc." +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 3094f59d30b84e0fa2712066b64cf7c6 +msgid "@jagane-opensource" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 550ddd89212942fa80215b8045683c33 7a96a90a9765499aab75a045af6b8d5e +#: c3dec3eaa7b349eeb4631fda9c05bc53 +msgid "Frédéric Collonval" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 2d59c658d07b44f6b0edba6dc9783c5f 2e402dc0be424aa78e62715fcd976c40 +#: e18bd70acfaa4b2fbe2cde53b0551cff +msgid "ARIADNEXT" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: ../../source/community/community-call-notes/2021-january.md +#: ../../source/community/community-call-notes/2021-march.md +#: 7fe66676d6814e798cbc27911b3cb92c 87cad068894b425dbec9aade2f83d3bb +#: 9fa048569eeb46b6b1808daacc1cf6ee +msgid "@fcollonval" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: aeac90cadb4945a4bc04daa30555c5e1 +msgid "GTRI, Project Jupyter" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 0a25b44c065444b58fd8b2eaca3cf9c2 +msgid "@nrbgt @bollwyvl" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: bf9e53015077401aa64795efce7bbbcd +msgid "M. Krassowski (Mike)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 866732ca4828425d9b9b21ccfb0ce633 +msgid "UOxf (on own behalf)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: e0565d56ab274c4ba70fc36a94329db0 +msgid "@krassowski" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 91423e6fc8ac45da85cecb4d14aa15aa +msgid "Dan Lester" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: a9d10dd7cc5f4c449993ea0790dc003b +msgid "Ideonate" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: ce44b0c6db384558909758d072463e13 +msgid "@danlester" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 3f8732794eb4414b982795701946f579 +msgid "Upstate University" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 6511ea2366bc47f1a4ccfc30510633dd +msgid "Michael Milligan" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 7d017b184f0c45b0846941b2f89d13da +msgid "MSI @ U of Minnesota" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 4acbd5e893fa4d679d7e916e5f43cf0b +msgid "@mbmilligan" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 2cb5a37687634979bb77e10e751932af +msgid "Matthew Seal" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 406943649a324aeb9c44798bcd7dbdd3 +msgid "Noteable, Inc" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 3744930dc9e04e52932e3e1aa0f06626 +msgid "@mseal" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: acdfdd4ed21140d7933db88e26ef2891 +msgid "Jose Ferro." +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 903b91832db54ec096a9163bef04bcb1 +msgid "EPO (www.epo.org)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: bf44720b9d1d48cdaa31e2272174befc +msgid "@joseberlines" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: e2d9ea7d0beb43479f12b44dfb438f6a +msgid "W Stein" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 416da09a84934047aab498e147f65dd7 +msgid "CoCalc" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 8cccf6fa75a24afcbd1244c47668a15b +msgid "@williamstein" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: a46e955fa67b4d7f8e7cf61bdca24cb8 +msgid "Raja Rajendran" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: f7839bdeefa949d6a357cde0f0b24782 +msgid "@software-artisan" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: c59aea0b16e34232be32c3164ab87c5f +msgid "Adhitya Vadivel" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 03fa8673407e4c25b76a7797a5233dcf +msgid "@adhityav" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: d5a72679ce1d402faea04c6b671364eb +msgid "Safia Abdalla" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 424d681e4b1b40be8b51c1d7f05854d0 +msgid "Microsoft, nteract" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 17289513930f4c96889bb6078caa65aa +msgid "@captainsafia" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 48697a32c0af42c4a6713e55dc4b5f01 +msgid "Shelby Sturgis" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 456822e4bc114ac4983072c9f6ec1f11 +msgid "Netflix" +msgstr "" + +#: ../../source/community/community-call-notes/2021-february.md +#: 1fb24cac5da942fa8e13a956e465ca23 +msgid "@stormpython" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:2 +#: 1881caeb74ab4c65bf34d20f1fc5f4c0 +msgid "January 26th, 2021" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:4 +#: 8740a4e51f3e45baaac006ccb50d18b4 +msgid "" +"**Date:** January 26, 2021, at 9am Pacific (your " +"[timezone](https://arewemeetingyet.com/Los%20Angeles/2021-01-26/9:00/Jupyter%20Community%20Call))" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:6 +#: 88e785393fd746a48e7182714a1d68ad +msgid "" +"[**Discourse**](https://discourse.jupyter.org/t/jupyter-community-" +"calls/668)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:8 +#: 1c4f73f3ce4b442e9b21d31aa46b821e +msgid "[**YouTube Link**](https://youtu.be/DS_J3mzulCw)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:25 +#: 71d3fbb534c14a0c87de2a216c63f45c +msgid "" +"**Frédéric Collonval** To improve visibility and group volunteer time on " +"maintenance of popular JupyterLab extensions, a unofficial GitHub " +"organization has been created: [jupyterlab-contrib](https://github.com" +"/jupyterlab-contrib)." +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:27 +#: ec46ffdbf41e4fe0a1ab484386b499b7 +msgid "" +"**Isabela Presedo-Floyd** In case you missed it, [JupyterLab 3.0 is " +"out](https://blog.jupyter.org/jupyterlab-3-0-is-out-4f58385e25bb)! " +"Congrats to the community and thanks for all the hard work that went " +"into this release." +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:29 +#: 266a37b8180e4d29874c4b91e20173cc +msgid "" +"**Isabela Presedo-Floyd** I've seen a resurgence of community interest in" +" making multiple Jupyter projects accessible. This is awesome! We also " +"have a group of people meeting every other week to coordinate JupyterLab " +"accessibility work (and talk about accessibility in general) that you " +"can join from the [community " +"calendar](https://jupyter.readthedocs.io/en/latest/community/content-" +"community.html#jupyter-community-meetings)." +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:32 +#: 4dfd2e672f224de494eb5246516d19ef +msgid "" +"**Layne Sadler** Plotly updated jupyter-dash labextension for 3.0 and " +"vows to prebuild. [issue](https://github.com/plotly/jupyter-" +"dash/issues/49)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:36 +#: 303e2441c6bf48a6aedf8315189d5945 +msgid "" +"**Nick Bollweg** [jupyterlab-lsp 3.2](https://pypi.org/project" +"/jupyterlab-lsp/) on `pypi` & `conda-forge`. JupyterLab :three:. :eight: " +"_[Language Client](https://langserver.org)_ features. Ju(lia)+Py(thon)+R " +"_Language Servers_+_Kernel_+_Notebook_, plus [more](https://jupyterlab-" +"lsp.readthedocs.io/en/latest/Language%20Servers.html). [Pre-JEP " +"Issue](https://github.com/jupyter/enhancement-proposals/issues/67) to " +"move towards an official sub-project 🚀." +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:40 +#: d093572d5e024b7982b8cf6d9c225317 +msgid "" +"**Nick Bollweg** (_or someone better :muscle:_) [JupyterLab " +"2.3.0rc0](https://github.com/jupyterlab/jupyterlab/blame/2.3.x/docs/source/getting_started/changelog.rst#L6-L12)" +" is a performance-focused prerelease, on `pypi`/`conda-forge`, these " +"features will land in 3.1. Ready for [testing](https://github.com/robots-" +"from-jupyter/robotframework-jupyterlibrary/pull/34)!" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:43 +#: 844c70f06f7745e7a56552f5a6729a9e +msgid "" +"**Frédéric Collonval**: Leverage JupyterLab modularity to customize the " +"UI with a alternative [launcher](https://github.com/jupyterlab-contrib" +"/jlab-enhanced-launcher) and a [cell toolbar](https://github.com" +"/jupyterlab-contrib/jlab-enhanced-cell-toolbar) - demonstrate easier " +"distribution thanks to JLab3." +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:45 +#: 6c3295d01633446ea1f6f2f0c47f5b25 +msgid "" +"**Corentin Cadiou**: presentation of " +"[ipysphaghetti](https://github.com/cphyc/node_editor) (name not settled " +"yet) a JLab (3+) extension implementing a node-based approach to " +"interact with your data." +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:47 +#: ed2c8c3d4a6d4eddb365a62e075d9b32 +msgid "" +"**Thorin Tabor:** Notebook Projects, a mechanism for encapsulating " +"multiple user environments in a JupyterHub instance" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:51 +#: d75a53fa48214e5798271af8b3bf6acd +msgid "" +"Take the [Jupyter survey](https://blog.jupyter.org/survey-jupyterlab-and-" +"beyond-88c7fbd27a79)!" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:52 +#: 2be2b0e560e4466280910c920b733fa7 +msgid "some nteract links after @raman's pre-demo:" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:53 +#: 071ef9625f14427da8ba85da9cec95c4 +msgid "https://docs.nteract.io/getting-started-with-nteract/" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:54 +#: 514a7193bdda4b49b6b3a81b0186378c +msgid "https://github.com/nteract/nteract" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:55 +#: 3602aeb857b4490cb59d793c142034a9 +msgid "semi-related \"instant-on\" compute/notebooks" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:56 +#: 36634fd105ff4e8a82f478b786aabc5c +msgid "[jyve](https://deathbeds.github.io/jyve/lab/), static JupyterLab build" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:57 +#: f29b62f1b4844bf7a9a705a5aa2fb966 +msgid "" +"[pyodide](https://github.com/iodide-project/pyodide), full CPython in the" +" browser" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:58 +#: 1b54b4663123464eb41e5eb4bfc95ea9 +msgid "" +"hackmd's FOSS flavor is now " +"[HedgeDoc](https://github.com/hedgedoc/hedgedoc)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:59 +#: d2234eae15d34276af87e7ae462edd4d +msgid "we need a Hub/Lab Extension :hedgehog:" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:60 +#: d426f8896e4e43f88ba7dc13c6c49154 +msgid "\"run cells with tags\"" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:61 +#: a57db7db78e24a96a2dc3b9c75379330 +msgid "from `cell-toolbar` demo" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:62 +#: 4ea74af9d7d344f694e8baed538c7931 +msgid "" +"could this be supported in multiple clients, e.g. _JupyterLab Notebook_ " +"UI and `nbclient`/`nbconvert` CLI" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:63 +#: dabb849a12194cd1a0b95c35511b6ece +msgid "workflows with (some) Jupyter integration" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:64 +#: 267b2ac39ab947a4bfab0f69d540e77f +msgid "[cylc](https://github.com/cylc/cylc-ui/issues/90)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:65 +#: 35b2955f583347058a64cf486790344d +msgid "[dask](https://docs.dask.org/en/latest/graphs.html)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:66 +#: ea8f373dc1a44bfa9eb817581401fd90 +msgid "" +"[dagster](https://github.com/dagster-io/dagster) " +"([binder](https://gist.github.com/bollwyvl/0fe7a6f89251992ab1a542ac2b4051c4))" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:67 +#: f7923c87278242569c94f4cbf88f52aa +msgid "[openmdao](https://github.com/OpenMDAO/OpenMDAO)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:68 +#: 88e6a000ed6a418ca788d5353cf8ca49 +msgid "[prefect](https://stories.dask.org/en/latest/prefect-workflows.html)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:69 +#: 9ae4fbbd4a344c1baa87d01ad454bf25 +msgid "" +"[GenePattern](https://github.com/genepattern) and " +"[GenePatternNotebook](https://notebook.genepattern.org/#gsc.tab=0)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:70 +#: a26e73ec01ef429f85fd32ec70b098e8 +msgid "" +"[Integrative Genetics " +"Viewer](http://software.broadinstitute.org/software/igv/) and their " +"[Jupyter extension](https://github.com/igvteam/igv-jupyter)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:73 +#: b6ca8f5a9ae748fd9e739d3e7974add6 +msgid "Q/A" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:75 +#: 5bfcd125caa848fba305b5cee0fbbfb9 +msgid "**As a company, how do we start contributing?**" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:76 +#: 908339ed13a84364a107b9b3dfa3fb98 +msgid "@willingc follow the projects that seem most within your team's wheelhouse" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:77 +#: 547a104333d9488482a96d2b1e99872e +msgid "" +"Visit the Jupyter [Discourse](https://discourse.jupyter.org/) and " +"[community calendar](https://discourse.jupyter.org/t/jupyter-community-" +"calendar/2485)!" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:78 +#: f2d93ca61a5e46d4b1e968d2c860c4a2 +msgid "" +"@jasongrout JupyterLab [4.0 release " +"plans](https://github.com/jupyterlab/jupyterlab/issues/9647) are " +"underway. There may be items there, or things you want to contribute." +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:79 +#: 4d25021a54ca45f7b841d66679fce119 +msgid "" +"translations always welcome! Check " +"[CrowdIn](https://crowdin.com/project/jupyterlab) for more info." +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:80 +#: 5511d81a4d6241c6beb2b0ba1075b47b +msgid "" +"[corporate " +"guidance](https://github.com/jupyterlab/jupyterlab/blob/master/CORPORATE.md)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:81 +#: f0da4d024da4499a9e0418396e7366d9 +msgid "" +"[team compass](https://github.com/jupyterlab/team-compass) is where many " +"of these larger discussions may happen." +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:82 +#: b84637d184f240f496cd5f34cd4f2eb1 +msgid "@jupyter/notebook is very starved for resources" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:83 +#: 06cd48f6e34141b88d41b0f19fc63bec +msgid "has a weekly meeting just trying to keep the issue count down." +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:84 +#: 0ef84ca862144048a6643968e686f0bf +msgid "many are low-touch to at least get triaged" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:85 +#: b0e8d2f6450a49eba9fb4134ce8a407d +msgid "really any help welcome" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:86 +#: 944d4580345a4cd2ad752a5ad1a5e48b +msgid "@isabela-pf accessibility on all projects." +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:87 +#: b7487bdf11f54a4eabd86a21a95498d0 +msgid "" +"We have been starting with JupyterLab Components, etc. Notes for our " +"meetings and all current team work live in [this " +"issue](https://github.com/jupyterlab/team-compass/issues/98)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:88 +#: c6c077f828bb4c67b81ae997fc55e04a +msgid "" +"And documentation in [pydata-sphinx-theme](https://github.com/pandas-dev" +"/pydata-sphinx-theme/pull/294) (upstream of `jupyter-book`, etc.)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:90 +#: 603e62b81049426eab84d75dc7e892cc +msgid "**What would you like to see in community calls?**" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md:91 +#: ba4c94b676994a2e9a92ea58257f73bc +msgid "Overview of JupterLab 3" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 30eac68b87084dc5829c4d5d03e92709 +msgid "Ross Stokoe" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 317f5b02a853406a83ada2a47a391a45 5ae181107942449ebff5fa4ed9febb21 +#: a4e76bac57d447dfb85a81c893670a53 f66b67f053cb4b7589e95329478250da +msgid "Refinitiv" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: d55643792e6a41e891d59066965ff48c +msgid "@RR11WK" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 35ba7ca459724c3f9ce2a44151d511d2 +msgid "Julien Hoarau" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 65bba2c24f4045728a48ffc4b509eb52 +msgid "@julienhoarau" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: f669285ab5b14441b65d4b50501391be +msgid "Greg Olmstead" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 6706e7f2aa424194bcad3779e5415f83 +msgid "@maynardflies" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: fb08294a464f417d9918275cd77bce45 +msgid "Josias De Lima" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: e4649fc48f3c4aa8bd9f50d0bda7f711 +msgid "@JoshDL" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 2ba3bc3f3b5046bcab3cfca1c7a5f1a1 +msgid "Loic Huder" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: bcadd80ab09d4fd780ed2405184d40d5 +msgid "Thorin Tabor" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 1871bba8d99d40caa5c802b146f3a75e +msgid "UCSD" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: f88f522d9e4747d1a6fd77c1b310b899 +msgid "@tmtabor" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: f1a826992f594708bd46c7ea1ba64218 +msgid "Gonzalo Gasca Meza" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 209e286e47db4adca05bfe135b5ea43e +msgid "@gogasca" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 55d7891bfeda4766a605d1e8d65cdeb0 +msgid "free agent" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 37ee7d4ee93342faa99071e7335763ca +msgid "Corentin Cadiou" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: ab27826875d9420c8069f0a3b596524d +msgid "University College London" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 5e7c49ffc7f9441daa00f65b59dba442 +msgid "@cphyc" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 67e5f5e696aa463a8b53e76f45a3a2be +msgid "Proj. Jupyter, GTRI, Deathbeds" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: ab8306695ab94d86bebaa8d2e4ec0fb3 +msgid "@bollwyvl @nrbgt @deathbeds" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 5525f043a40d4b50bf7474fccd1a83cb +msgid "Upstate Medical Universtity" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 54b233de463542c88ce0e41d4a776555 +msgid "nteract, StockGro" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: e521ceff4b3141a7bd515c42af4c91f9 +msgid "@ramantehlan" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 1f21cc6356b14cc2a2b0637da210bf1f +msgid "Noteable / Jupyter" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 483c89daa5c4494f95294757be7a4b1c +msgid "Karla Spuldaro" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 11a541938e3c433899d9db38fbe39da3 813a73484c974718af908a51649159ed +msgid "IBM" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: db2bac6785e946b39c67ced08dfb1b7a +msgid "@karlaspuldaro" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 64bdadeef1474e3788c7a2df22b269de +msgid "Martha Cryan" +msgstr "" + +#: ../../source/community/community-call-notes/2021-january.md +#: 2d64c7e56b9146c1a4b32e2ba7d10028 +msgid "@marthacryan" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:1 +#: 35bf153abe5b4804ba232ea466c80fec +msgid "March 30th, 2021" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:3 +#: 51d4285f400e4b608c19880c1c8df8ca +msgid "" +"**Date:** March 30, 2021, at 8am Pacific (your " +"[timezone](https://arewemeetingyet.com/Los%20Angeles/2021-03-30/8:00/Jupyter%20Community%20Call))" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:7 +#: 7bb38edaa65f4f99bcd26d201e3a9526 +msgid "[**Youtube Link**](https://youtu.be/8JQoALd9KTo)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:22 +#: 55414b8104ca428f8c43efe1c566db8d +msgid "" +"**Isabela Presedo-Floyd** Congrats to anyone who started the cycle 4 CZI " +"EOSS grant application process! We have several in the community." +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:23 +#: 228b415a0be34218bf4971fd7b97c287 +msgid "" +"**Nick B** [jupyter-starters 1.0.2](https://pypi.org/project/jupyter-" +"starters/)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:24 +#: 62481d2db62b4d2c9c2c0f29041b3937 +msgid "**Carol W** Darian for his work on the Jupyter Distinguished Contributors." +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:28 +#: e4a2cd3dc461475bbafd0ee1fed255b4 +msgid "**Nick B.** Has anyone done `if this then that` in a JupyterHub?" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:29 +#: 7d986a5d05b14cf6b7cc17cce4e5b5b6 +msgid "General answer is no" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:30 +#: 8ee74bb2dd264bc8a67ab7505518df08 +msgid "Something like https://github.com/huginn/huginn?" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:31 +#: 26ff9eeea4f84c349a5d00981e5542c5 +msgid "For background, this is https://ifttt.com/" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:32 +#: 4acd8cc3e70b453e8eadf4637d1a723c +msgid "Use cases" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:33 +#: 5b1e9f81dc024e80bb12cc99af0d9075 +msgid "" +"**Tony Fast** schemata library (future traits library that complies more " +"with JSON schema than traitlets)" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:34 +#: b32bac63bc964a3e8c620f0188d050b3 +msgid "" +"Goal of having types being able to describe themselves. This is a work in" +" progress for IPython." +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:35 +#: 7b891f504add4297822ec1cf7a4698fd +msgid "" +"Creates different types of interactive notebook outputs following JSON " +"standards that can allow them to interact with more backends." +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:36 +#: 4cebe56a590f44ba9dcf858d20476db4 +msgid "Favorite notebooks/binders/plugins" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:37 +#: 4c8270dde21b4b77b29a8c3f22ad395a +msgid "" +"**Simon Li** Unexpected use of binder https://github.com/jupyterhub" +"/jupyter-remote-desktop-proxy/" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:38 +#: 830a75eb92af4d8b87248e68e487b7cf +msgid "" +"Can you run JupyterHub inside mybinder " +"https://gist.github.com/manics/cd04d42b211dfd6240430ee33349cd49" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:39 +#: 84cbcce7e5d54873ab8d56d0a4efc6e7 +msgid "" +"**Tony Fast** " +"https://nbviewer.jupyter.org/github/deathbeds/deathbeds.github.io/blob/master/deathbeds/2018-07-31" +"-Testing-notebooks.ipynb" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:40 +#: 286b4884eed843208a0f40ce606077c8 +msgid "" +"https://github.com/jennalandy/notebook-" +"research/blob/master/analysis_notebooks/16_HallOfFame.ipynb" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:41 +#: a93c47bc9f4a4fe88d0c4036f326ea66 +msgid "" +"**Nick B.** " +"https://gist.github.com/bollwyvl/7a128978b8ae89ab02bbd5b84d07a4b7" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:42 +#: e5208b1bb8094b7d824f84b27ba6cc00 +msgid "" +"Can we round-trip LaTeX to SymPy https://github.com/bollwyvl/sympy-latex-" +"hypothesis/blob/master/Hypothesize.ipynb" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:43 +#: 46b010daa5e7429486712d915fdd98d4 +msgid "" +"**Carol Willing** https://github.com/moorepants/pydy-tutorial-human-" +"standing" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:49 +#: afac93366dd5450c98401eb8709d8665 +msgid "https://w3c.github.io/annotation-aria/" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:50 +#: 947f9a14405e43c08457cc2d9b3fa2c5 +msgid "http://507movements.com/" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:51 +#: 51f228a680ff4b9d85b3a7903beeaf98 +msgid "http://rescience.github.io/ten-years/" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:52 +#: b645ff36c38c4d548f8df47c5556a45e +msgid "https://web.mit.edu/music21/" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:53 +#: 519470494dd246f78d19c3a81710b530 +msgid "https://pockit.ai/" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md:54 +#: 677566bb25064829ad5f7a2a3ac48b4f +msgid "https://www.dexterindustries.com/gopigo3/" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md +#: 2a0fdb9a86544108bb122d8e17077c56 +msgid "Jupyter" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md +#: a33f855870de41b39aa3d8f4d8ffe005 +msgid "Jupyter, GaTech" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md +#: 245d4ac38e004e5cbdc5f3bad6372b48 +msgid "Fatma Tarlaci" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md +#: e5f45bdb3abf4cc991f3d86e9fb1216e +msgid "OpenTeams" +msgstr "" + +#: ../../source/community/community-call-notes/2021-march.md +#: 63e2d8463d9a46a49496730dc041862a +msgid "@ftarlaci" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "April 2021" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "March 2021" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "February 2021" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "January 2021" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "December 2020" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "November 2020" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "September 2019" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "August 2019" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "June 2019" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "May 2019" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "April 2019" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:9 +msgid "March 2019" +msgstr "" + +#: ../../source/community/community-call-notes/index.rst:5 +#: 97e6a64065c24c969000f87a8b9b15b4 +msgid "Community Call Notes" +msgstr "" + +# 2bdfad80e4bc4c62a0f6f6a24e0fd7f2 +#: ../../source/community/community-call-notes/index.rst:7 +#: c1f11d5d261a4eb1a72b640e25681ffc +msgid "" +"The Jupyter Community Call is an open video call. Think of this as a " +"\"monthly, virtual JupyterCon\". It's a place for *anyone* to announce " +"and share fun things happening in the Jupyter community. Everyone is " +"welcome (even if you're not presenting). We record these videos and post " +"them on YouTube. For more information, `read this discourse thread " +"`__." +msgstr "" + +#: ../../source/community/content-community.rst:5 +#: 777a1bb056864437958c0413c9cd462e +msgid "Community" +msgstr "" + +# d54af2f83db8471499576db794d43eb0 +#: ../../source/community/content-community.rst:8 +#: 1fd74eb4ec604380a8003fd31bae6568 +msgid "" +"Welcome to the Community Guides for Jupyter. These guides are intended to" +" provide information about the Jupyter community such as background, " +"events, and communication channels. As our community is highly dynamic, " +"information may change, and we will do our best to keep it up to date." +msgstr "" + +#: ../../source/community/content-community.rst:21 +#: 21e67ad117dd49cda0e1b077291c3cf9 +msgid "Jupyter Community Meetings" +msgstr "" + +#: ../../source/community/content-community.rst:23 +#: 7c49149ebdd84db2be0913c0bc878081 +msgid "" +"The Jupyter community often meets (usually on-line) in order to discuss " +"matters in the Jupyter community, share new ideas and discussions, and " +"connect with one another. This often happens within specific sub-project " +"(more information below), though there are also occasional community-wide" +" meetings." +msgstr "" + +# 6baa512bd6c34089936b8ec1cfabb762 +#: ../../source/community/content-community.rst:28 +#: 5146ad9b4f6d4bd09986be1800ccadce +msgid "" +"This following calendar shows the various meetings and events from " +"Jupyter sub-projects:" +msgstr "" + +#: ../../source/community/content-community.rst:36 +#: bb90eec5a9394673a19e1fe963a7d86c +msgid "Jupyter-wide meetings" +msgstr "" + +#: ../../source/community/content-community.rst:38 +#: abf3b7d8ce5f49beaf6ca35c5d2c2fa0 +msgid "" +"**All-Jupyter Community Calls** generally happen on the last Tuesday of " +"the month, and are focused around demonstrations and sharing information " +"across all of the Jupyter projects." +msgstr "" + +# bab41d17142c4f01a84e8931031ef15b +#: ../../source/community/content-community.rst:41 +#: ab5f60121393414785832e86bd99fe7b +msgid "" +"Find information on `this Discourse thread " +"`_." +msgstr "" + +# b14012ac8c7d4f7d9b1fa40ad998d8a5 +#: ../../source/community/content-community.rst:42 +#: 8e6f8c55c5bb4e1698f5c7cdbfd5d0f5 +msgid "" +"Watch previous calls on `our YouTube channel " +"`_." +msgstr "" + +# 94fd509d19b04c98ac0e82a0aa3003aa +#: ../../source/community/content-community.rst:43 +#: bca5b2be809e42b58b37dec82c3107b5 +msgid "Read the `notes from previous calls `_." +msgstr "" + +#: ../../source/community/content-community.rst:45 +#: 889ba359c6044905a3c8310621fe3f11 +msgid "" +"In addition, you can find the notes from previous community meetings " +"below." +msgstr "" + +#: ../../source/community/content-community.rst:52 +#: a56eb297687248f39c8e043236d346f3 +msgid "Jupyter Project meetings" +msgstr "" + +# 1619503c14774902b78d65ca9b79d141 +#: ../../source/community/content-community.rst:54 +#: 1752982df2ba47b5af580985823dac5b +msgid "" +"The core developers of various Jupyter sub-projects have regular meetings" +" to discuss and demo what they have been working on, discuss future " +"plans, and bootstrap conversation. These meetings are public and you are " +"welcome to join remotely." +msgstr "" + +# f34a0721b4874356a8ac819e93fef795 +#: ../../source/community/content-community.rst:58 +#: ba3b341948144cf897656035f4d0b222 +msgid "" +"Each team has their own processes around logistics and planning for the " +"team meetings. The following pages should help you find the information " +"for each." +msgstr "" + +# b6c188f529e043bb8740f19fad6db3a2 +#: ../../source/community/content-community.rst:62 +#: c13e9e795f004b7f98ec2f41a3d34bd3 +msgid "" +"**JupyterHub meetings** happen monthly. For a calendar of future team " +"meetings, see `the JupyterHub team compass repository `_." +msgstr "" + +# d87217c537f04a3e94fee9b03871ddb8 +#: ../../source/community/content-community.rst:65 +#: 73aed6462dd94db0bfb082432d0d548f +msgid "" +"**JupyterLab meetings** happen weekly. For more information about when " +"these meetings happen, as well as notes from each meeting, see `the " +"JupyterLab README `_." +msgstr "" + +# 5cb8eb65c5d342cb82cd6e06b515c4bb +#: ../../source/community/content-community.rst:68 +#: 2337779382d1409e914f6da247d66115 +msgid "" +"**General meeting conversation and planning** often happens in the `dev-" +"meeting-attendance Gitter channel `_. We recommend checking it periodically for new information " +"about when meetings are happening." +msgstr "" + +# 85d662482e654ca8a60eb03ea3c16a49 +#: ../../source/community/content-community.rst:77 +#: abbb79c177f64ea9ae3cd0889e967f7a +msgid "Jupyter communications" +msgstr "" + +# af1931399f504fde9b5c379ab97c3788 +#: ../../source/community/content-community.rst:79 +#: cfe37eddf10a4a0cb1002f61e941e522 +msgid "" +"As a general rule, most project-wide conversation happens in the `Jupyter" +" community forum `_. There are also many " +"other kinds of communication that happens within the community. See below" +" for links and other relevant information." +msgstr "" + +# 2c02c8ede4514562b849edfba6bcc50e +#: ../../source/community/content-community.rst:84 +#: c20e4cf9435c4ffbbaa17c519ee2750e +msgid "Community forum ``_" +msgstr "" + +# fb525140606947bebc38796903ee7659 +#: ../../source/community/content-community.rst:85 +#: a615955fe9c647278dbb0fd5bdd976bb +msgid "Blog ``_" +msgstr "" + +# 64fab8ffafb24a7bb060d4359ec04feb +#: ../../source/community/content-community.rst:86 +#: 07719e4ff6a04531b338fc46f62f170d +msgid "Newsletter ``_" +msgstr "" + +# ef8f773e0424467eb83e939805663888 +#: ../../source/community/content-community.rst:87 +#: f90cee718323443e8b83581326421e90 +msgid "Website ``_" +msgstr "" + +# 80103b709d94489da4c958855044ce23 +#: ../../source/community/content-community.rst:89 +#: 4c17016b385c4851843b96ef217158d9 +msgid "Gitter ``_" +msgstr "" + +# dd12e64a1c6242688e11b1e72d4b7d17 +#: ../../source/community/content-community.rst:90 +#: 30b433a0a0ef436fbc246490f1955ed2 +msgid "" +"Mailing lists (Jupyter, Jupyter in Education) " +"``_" +msgstr "" + +# d8926bc097014aa68efb0246f0e69e7e +#: ../../source/community/content-community.rst:94 +#: 58a909ef8ef44173a714be9a481e0e17 +msgid "Governance" +msgstr "" + +#: ../../source/community/content-community.rst:96 +#: 7f444ee4ac194d7ba346c629fbd891b7 +msgid "" +"Steering council: Information about the steering council and its members " +"can be found on the `Jupyter website `_." +msgstr "" + +#: ../../source/community/content-community.rst:98 +#: 7e6033403cd248afae34e3e3fbd2c5b9 +msgid "" +"Information about Jupyter's governance process can be found on `the " +"Jupyter governance website `_." +msgstr "" + +#: ../../source/community/content-community.rst:100 +#: dc45eb6418d74078a7e25bee5fd1a307 +msgid "" +"Jupyter Enhancement Proposal (JEP) process: Details about the process can" +" be found in the `enhancement proposals website `_." +msgstr "" + +# 03da538fdae3452f9e7fa72740db23a8 +#: ../../source/community/content-community.rst:105 +#: a1d2498122994fee855c46e77f7e694f +msgid "Code of conduct" +msgstr "" + +#: ../../source/community/content-community.rst:107 +#: 7f8752bc0d2d4aaea527ed00b41669af +msgid "" +"Information can be found in the `Jupyter Code of Conduct page " +"`_." +msgstr "" + +# 8631493f520c4c5d9aa3b82c61b18697 +#: ../../source/community/content-community.rst:112 +#: 65f70bd6d22745d9bd18133b54c563cc +msgid "Running Jupyter Events" +msgstr "" + +# 137649fb2f5245deafef6be8d2c45f67 +#: ../../source/community/content-community.rst:114 +#: b73a510ff3b94cdebadc8d3c118b9e36 +msgid "" +"Members of the Jupyter community often get together to share what they're" +" working on, to work together, and to teach and learn from one another." +msgstr "" + +# 18ab4d3d9f3740539a0ea04a1434ae48 +#: ../../source/community/content-community.rst:117 +#: 0bc2d2daf71f41179bfa194586d591a2 +msgid "" +"If you're organizing an event with the Jupyter community (whether it's as" +" small as a JupyterDays meetup, or as large as JupyterCon) you should " +"ensure that the event follows the values and goals of the Jupyter project" +" - to be a place where *everyone* feels welcome and supported and that " +"reflects the diversity of developers and users in the Jupyter community." +msgstr "" + +# da3a24e3be164ae5acc14cc40b89efa7 +#: ../../source/community/content-community.rst:123 +#: 2deefb47bca44905bde9f0df2b7aec95 +#, python-format +msgid "" +"Shoot for having **25% of your participants come from under-represented " +"groups**. If you're organizing a Jupyter event, here are some resources " +"to help out." +msgstr "" + +# c2b3b009069d47a68b80607d72c3aac3 +#: ../../source/community/content-community.rst:127 +#: 9e769dc4e87b45a5bb996cb925d3527a +msgid "" +"**Mozilla** has a number of excellent resources on hosting open events. " +"The `Mozilla Open Events guide " +"`_. " +"This is an excellent resource for planning and running an open, inclusive" +" event. In particular, `this section on making events more inviting " +"`_ is a good way to make your event more welcoming, " +"interesting, and accessible to the Jupyter community. Finally, the " +"`Diversity and Inclusion wiki includes conference calls related to this " +"topic " +"`_." +msgstr "" + +# caf59581a04945b19d2b984c39c0568b +#: ../../source/community/content-community.rst:134 +#: b79968fed28a40e597b96926c25d7ea0 +msgid "" +"The `NumFocus DISCOVER cookbook `_ is another collection of resources for making " +"your event more productive, diverse, and inclusive." +msgstr "" + +# f5d3e95f70224993a8ee5b6f06c1c366 +#: ../../source/community/content-community.rst:137 +#: 28ba267637494e0b859f39c7521cf082 +msgid "" +"The `National Center for Women & Information Technology " +"`_ has an excellent collection of resources for " +"creating a diverse and inclusive environment. In particular, we recommend" +" their `Inclusive Environment Assessment Guide " +"`_" +" and `10 actionable ways to actually increase diversity " +"`_." +msgstr "" + +# 3bc67786253a4cb4b32b9832fa2adb7f +#: ../../source/community/content-community.rst:141 +#: 2123d44b1ca248e8a39ea21d6928f4d6 +msgid "" +"The `PyCascades `_ community has `several efforts" +" in improving diversity and inclusion `_." +msgstr "" + +# d7ff8abd9f234f10889c38cb7f961992 +#: ../../source/community/content-community.rst:142 +#: 37a3cb9242404dd0aeef7f44ce4c43c3 +msgid "" +"`Write the Docs `_ has a `Welcome Wagon " +"Guide `_ to help first-time attendees feel welcome and included." +msgstr "" + +# f06cd4cad8664f3eb2130b00c6e909e2 +#: ../../source/community/content-community.rst:145 +#: 43b72b5e637042f292a72198bff413c1 +msgid "" +"Ultimately, making events more inclusive is not rocket science and there " +"is no magic bullet. It requires clear, focused dedication, planning " +"ahead, and sustained resources and effort over time. However, we believe " +"this effort is worth it!" +msgstr "" + +# 4546949c9a144a1298252a5bd089279d +#: ../../source/community/content-community.rst:152 +#: f5365aefc747448ba651ba57bc902d22 +msgid "What is a Jovyan?" +msgstr "" + +# b38815a36fd840c69333c684d44fc01e +#: ../../source/community/content-community.rst:154 +#: 071119b041cd4c5996178b9183287e9c +msgid "" +"You may see the word **Jovyan** used in Jupyter tools (such as the user " +"ID in the `Jupyter Docker stacks `_ or referenced in conversations. But what is a Jovyan?" +msgstr "" + +#: ../../source/community/content-community.rst:158 +#: 2c3ef4f1effe4c299223a44f9198eec5 +msgid "" +"In astronomical terms, the word \"Jovian\" means \"like Jupiter\". It " +"describes `several planets that share Jupiter-like properties " +"`_." +msgstr "" + +# 5f92f3a419da4e1aa815eb1ce1929306 +#: ../../source/community/content-community.rst:161 +#: 72418d1b31db42f19d68d204ecb9c9b3 +msgid "" +"Much like the planet Jupiter and our solar system, the Jupyter community " +"is large, distributed, and nebulous. We like to use the word **Jovyan** " +"to describe members of this community. Jovyans are fellow open " +"enthusiasts that use, develop, promote, teach, learn, and otherwise enjoy" +" tools in Jupyter's orbit. They make up the Jupyter community. If you're " +"not sure whether you're a Jovyan, you probably are :-)" +msgstr "" + +# c1508a5151854f74bf4c8deb7fde2c73 +#~ msgid "" +#~ "You may see the word **Jovyan** " +#~ "used in Jupyter tools (such as the" +#~ " user ID in the `Jupyter Docker " +#~ "stacks _[`importnb`](https://github.com/deathbeds/importnb) " +#~ "provides easy, flexible reuse of IPython" +#~ " notebooks from other notebooks, `.py` " +#~ "scripts and libraries, and even the " +#~ "command line._" +#~ msgstr "" + +#~ msgid "" +#~ "**[🤖 RobotLab: a one-click Jupyter " +#~ "and Robot Framework environment](https://github.com" +#~ "/robots-from-jupyter/robotlab)** [name=bollwyvl]" +#~ msgstr "" + +#~ msgid "" +#~ "> _`RobotLab` was built to support " +#~ "a workshop introducing [acceptance-test-" +#~ "driven](https://en.wikipedia.org/wiki/Acceptance_testing) " +#~ "development and robot process automation " +#~ "with [robotkernel](https://github.com/robots-from-" +#~ "jupyter/robotkernel), a [Robot " +#~ "Framework](https://robotframework.org/) kernel, in " +#~ "JupyterLab. It is built with " +#~ "[conda](https://github.com/conda/conda), " +#~ "[constructor](https://github.com/conda/constructor) and " +#~ "[azure pipelines](https://azure.microsoft.com/en-" +#~ "us/services/devops/pipelines). You can use the" +#~ " [installers](https://github.com/robots-from-" +#~ "jupyter/robotlab/releases/tag/v2019.9.0) to learn " +#~ "how you can use Robot Framework " +#~ "and Jupyter, or adapt its pipeline " +#~ "to produce your own, cross-platform " +#~ "installers_ >" +#~ msgstr "" + +#~ msgid "" +#~ "**Project Drawdown** [name=dgentry] > _Project" +#~ " Drawdown is a global research " +#~ "organization that identifies, reviews, and " +#~ "analyzes the most viable solutions to" +#~ " climate change, and shares these " +#~ "findings with the world._ > _We'll " +#~ "show current state of climate solution" +#~ " models using Voila and JupyterHub, " +#~ "and ask for suggestions about git " +#~ "operation driven from the Notebook._" +#~ msgstr "" + +# 1267e686bd0d4b039cedfdb4f29dd262 +#~ msgid "**Previous Community Calls**" +#~ msgstr "" + +# ddb34dc7214346588c43db31dd75a02c +#~ msgid "Monthly Meetings" +#~ msgstr "" + +# e191ff6ab041422b94c082b8194f1bb5 +#~ msgid "" +#~ "**All-Jupyter Community Calls** happen " +#~ "on the last Tuesday of every " +#~ "month, and are focused around " +#~ "demonstrations and sharing information across" +#~ " all of the Jupyter projects." +#~ msgstr "" + +# 415a23b6140845c1b39b127b61a35e6e +#~ msgid "" +#~ "Steering council: Information about the " +#~ "steering council and its members can " +#~ "be found on the `Jupyter website " +#~ "`_." +#~ msgstr "" + +# 9849b1d2be9949b790f8d9cb251e7531 +#~ msgid "" +#~ "Jupyter Enhancement Proposal (JEP) process:" +#~ " Details about the process can be " +#~ "found in the `jupyter/enhancement-proposals" +#~ " GitHub repo `_." +#~ msgstr "" + +# b6254391831147a4afcef3c22844e45c +#~ msgid "" +#~ "Information can be found in the " +#~ "`Jupyter Governance repo on GitHub " +#~ "`_." +#~ msgstr "" + +# 7a43f41ad815452bb5df25efb5a039bb +#~ msgid "" +#~ "In astronomical terms, the word " +#~ "\"Jovian\" means \"like Jupiter\". It " +#~ "describes `several planets that share " +#~ "Jupyter-like properties " +#~ "`_." +#~ msgstr "" + +#~ msgid "" +#~ "Qt(5.6)-based PDF output from JupyterLab " +#~ "(0.35) Quick demo of using QtWebEngine" +#~ " to load a notebook in lab and" +#~ " make a PDF. _{n+1}th time's the " +#~ "charm! Binder | issue | repo | " +#~ "[name=Nick]" +#~ msgstr "" + +#~ msgid "Date: December 15, 2020, at time 9am Pacific (your timezone)" +#~ msgstr "" + +#~ msgid "Discourse YouTube Link" +#~ msgstr "" + +#~ msgid "Please note:" +#~ msgstr "" + +#~ msgid "Community calls are recorded and posted to this playlist" +#~ msgstr "" + +#~ msgid "These notes will be recorded and posted here" +#~ msgstr "" + +#~ msgid "Everyone present is held to the Jupyter Code of Conduct" +#~ msgstr "" + +#~ msgid "Accessibility testing for docs - Nick" +#~ msgstr "" + +#~ msgid "jupyter-starters 0.6.0a0 released - Nick" +#~ msgstr "" + +#~ msgid "Thanks to everyone who gave feedback on last month's call! - Isabela" +#~ msgstr "" + +#~ msgid "" +#~ "Check out @jtp's repos for " +#~ "Jupyterlab-Classic and the p5js notebook." +#~ " I'm looking forward to sharing with" +#~ " students and teachers at Playfest " +#~ "conference in January. - Carol" +#~ msgstr "" + +#~ msgid "Jupyter survey is now live! Read more and take the survey. - Isabela" +#~ msgstr "" + +#~ msgid "" +#~ "WXYZDVCS Work-in-progress report on " +#~ "wxyz.dvcs, a bridge from Jupyter Widgets" +#~ " to distributed version control - " +#~ "Nick" +#~ msgstr "" + +#~ msgid "Hopefully released this week 🤞, works though!" +#~ msgstr "" + +#~ msgid "JupyterLab Classic - Jeremy" +#~ msgstr "" + +#~ msgid "deathbeds/importnb" +#~ msgstr "" + +#~ msgid "mwouts/jupytext" +#~ msgstr "" + +#~ msgid "QuantEcon MATLAB-Python-Julia Cheatsheet" +#~ msgstr "" + +#~ msgid "SQLite Jupyter kernel" +#~ msgstr "" + +#~ msgid "2i2c (brought up around support for JuptyerHubs in education)" +#~ msgstr "" + +#~ msgid "p5 notebook example (mentioned when talking about JupyterLab Classic)" +#~ msgstr "" + +#~ msgid "Date: November 17th, 2020, at 9am Pacific (your timezone)" +#~ msgstr "" + +#~ msgid "Discourse" +#~ msgstr "" + +#~ msgid "Youtube Link" +#~ msgstr "" + +#~ msgid "Please Note:" +#~ msgstr "" + +#~ msgid "" +#~ "Zach Shout out to Isabela for " +#~ "reviving the Jupyter Community Calls " +#~ ":tada:" +#~ msgstr "" + +#~ msgid "🦌 IPyElk 0.2.0 binder-badge" +#~ msgstr "" + +#~ msgid "" +#~ "Jupyter Widgets for interactive graphs " +#~ "at scale powered by the Eclipse " +#~ "Layout Kernel (ELK), sprotty, networkx." +#~ msgstr "" + +#~ msgid "dgaf (deathbeds generalized automation framework)" +#~ msgstr "" + +#~ msgid "Eric What is a Jovyan?" +#~ msgstr "" + +#~ msgid "Date: January 26, 2021, at 9am Pacific (your timezone)" +#~ msgstr "" + +#~ msgid "YouTube Link" +#~ msgstr "" + +#~ msgid "" +#~ "Frédéric Collonval To improve visibility " +#~ "and group volunteer time on maintenance" +#~ " of popular JupyterLab extensions, a " +#~ "unofficial GitHub organization has been " +#~ "created: jupyterlab-contrib." +#~ msgstr "" + +#~ msgid "" +#~ "Isabela Presedo-Floyd In case you " +#~ "missed it, JupyterLab 3.0 is out! " +#~ "Congrats to the community and thanks " +#~ "for all the hard work that went" +#~ " into this release." +#~ msgstr "" + +#~ msgid "" +#~ "Isabela Presedo-Floyd I've seen a " +#~ "resurgence of community interest in " +#~ "making multiple Jupyter projects accessible." +#~ " This is awesome! We also have " +#~ "a group of people meeting every " +#~ "other week to coordinate JupyterLab " +#~ "accessibility work (and talk about " +#~ "accessibility in general) that you can" +#~ " join from the community calendar." +#~ msgstr "" + +#~ msgid "" +#~ "Layne Sadler Plotly updated jupyter-dash" +#~ " labextension for 3.0 and vows to " +#~ "prebuild. issue" +#~ msgstr "" + +#~ msgid "" +#~ "Nick Bollweg jupyterlab-lsp 3.2 on " +#~ "pypi & conda-forge. JupyterLab :three:." +#~ " :eight: Language Client features. " +#~ "Ju(lia)+Py(thon)+R Language Servers+Kernel+Notebook, " +#~ "plus more. Pre-JEP Issue to move" +#~ " towards an official sub-project 🚀." +#~ msgstr "" + +#~ msgid "" +#~ "Nick Bollweg (or someone better " +#~ ":muscle:) JupyterLab 2.3.0rc0 is a " +#~ "performance-focused prerelease, on pypi/conda-" +#~ "forge, these features will land in " +#~ "3.1. Ready for testing!" +#~ msgstr "" + +#~ msgid "" +#~ "Frédéric Collonval: Leverage JupyterLab " +#~ "modularity to customize the UI with " +#~ "a alternative launcher and a cell " +#~ "toolbar - demonstrate easier distribution " +#~ "thanks to JLab3." +#~ msgstr "" + +#~ msgid "" +#~ "Corentin Cadiou: presentation of ipysphaghetti" +#~ " (name not settled yet) a JLab " +#~ "(3+) extension implementing a node-based" +#~ " approach to interact with your data." +#~ msgstr "" + +#~ msgid "" +#~ "Thorin Tabor: Notebook Projects, a " +#~ "mechanism for encapsulating multiple user " +#~ "environments in a JupyterHub instance" +#~ msgstr "" + +#~ msgid "Take the Jupyter survey!" +#~ msgstr "" + +#~ msgid "jyve, static JupyterLab build" +#~ msgstr "" + +#~ msgid "pyodide, full CPython in the browser" +#~ msgstr "" + +#~ msgid "hackmd's FOSS flavor is now HedgeDoc" +#~ msgstr "" + +#~ msgid "from cell-toolbar demo" +#~ msgstr "" + +#~ msgid "" +#~ "could this be supported in multiple " +#~ "clients, e.g. JupyterLab Notebook UI and" +#~ " nbclient/nbconvert CLI" +#~ msgstr "" + +#~ msgid "dask" +#~ msgstr "" + +#~ msgid "dagster (binder)" +#~ msgstr "" + +#~ msgid "openmdao" +#~ msgstr "" + +#~ msgid "GenePattern and GenePatternNotebook" +#~ msgstr "" + +#~ msgid "Integrative Genetics Viewer and their Jupyter extension" +#~ msgstr "" + +#~ msgid "As a company, how do we start contributing?" +#~ msgstr "" + +#~ msgid "Visit the Jupyter Discourse and community calendar!" +#~ msgstr "" + +#~ msgid "" +#~ "@jasongrout JupyterLab 4.0 release plans " +#~ "are underway. There may be items " +#~ "there, or things you want to " +#~ "contribute." +#~ msgstr "" + +#~ msgid "translations always welcome! Check CrowdIn for more info." +#~ msgstr "" + +#~ msgid "corporate guidance" +#~ msgstr "" + +#~ msgid "team compass is where many of these larger discussions may happen." +#~ msgstr "" + +#~ msgid "" +#~ "We have been starting with JupyterLab" +#~ " Components, etc. Notes for our " +#~ "meetings and all current team work " +#~ "live in this issue" +#~ msgstr "" + +#~ msgid "" +#~ "And documentation in pydata-sphinx-theme" +#~ " (upstream of jupyter-book, etc.)" +#~ msgstr "" + +#~ msgid "What would you like to see in community calls?" +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/content-quickstart.po b/docs/source/locale/en/LC_MESSAGES/content-quickstart.po new file mode 100644 index 000000000..a8b5d0f2f --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/content-quickstart.po @@ -0,0 +1,31 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-07-01 16:01+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.8.0\n" + +#: ../../source/content-quickstart.rst:2 589c33c63605431e98df6ffa3d7faec0 +msgid "Get Started" +msgstr "" + +# 313dee758bfc43d485397132ce7413a0 +#~ msgid "Jupyter Notebook Quickstart" +#~ msgstr "" + +#~ msgid "Quickstart" +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/contents.po b/docs/source/locale/en/LC_MESSAGES/contents.po new file mode 100644 index 000000000..914ab1134 --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/contents.po @@ -0,0 +1,142 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-06-09 19:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.8.0\n" + +# 33435e4f8e8e4d108f3ee03172fbca55 +#: ../../source/contents.rst:3 a349bc1c8c794f27a6b0869d75530e54 +msgid "Project Jupyter and IPython" +msgstr "" + +# a8847d2993b84d8a80a23f7807c1aff3 +#: ../../source/contents.rst:5 be504faaf8524a169e603dfd17398e9c +msgid "**Table of Contents**" +msgstr "" + +# 7d38cf5fdf954c39a2fe68592724bc41 +#: ../../source/contents.rst:62 84185ed36088452488af6ac76153dfa8 +msgid "Indices and tables" +msgstr "" + +# 289ae6113b3f4c9eb1d29b8e2c8fb24d +#: ../../source/contents.rst:64 d2d5cf98d8e343f3bcc973adfe86701d +msgid ":ref:`genindex`" +msgstr "" + +# 6421140cb92e40758c79f76b99f3e96f +#: ../../source/contents.rst:65 62642eea58e84f63b510ba08a541951f +msgid ":ref:`glossary`" +msgstr "" + +# a18e0af2c678400f9984da4463c144d0 +#: ../../source/contents.rst:66 b2c79dcd70e5413d81f08e73fac30f97 +msgid ":ref:`search`" +msgstr "" + +# 03b4d1007ed14d4d910b6c03fd6fd9f2 +#: ../../source/contents.rst:69 b0ecabc98fe947a49a40a4e599e28d7a +msgid "**Resources:**" +msgstr "" + +# 548ecdd6f5484efa80f8a2b05e4ef451 +#: ../../source/contents.rst:1 cca7fbfeea6443d8ba54fc35821cca75 +msgid "Site" +msgstr "" + +# 0ff92b1d24764e81957e7d1fc8ff8d9f +#: ../../source/contents.rst:1 0909ec3dd75d4b6dbd38bc3ca0ce5d40 +msgid "Description" +msgstr "" + +# 83e11f238d834561af6f97697b27f6fb +#: ../../source/contents.rst:1 ae0be1d422554801998a089b9327d361 +msgid "`Jupyter website `_" +msgstr "" + +# 920fa49c6db7411983595935f7e92f3e +#: ../../source/contents.rst:1 615d91bb975d48c0bb81c696cad32d4c +msgid "Keep up to date on Jupyter" +msgstr "" + +# 30a274f35cf2474797945a935da85cb4 +#: ../../source/contents.rst:1 60ff2651eff94a3894f2004f8e26c6dd +msgid "`IPython website `_" +msgstr "" + +# 88231b674ec542179be7c7445ec8583b +#: ../../source/contents.rst:1 3c6e59ce3d53440ea1ef94f26eaaee7f +msgid "Learn more about IPython" +msgstr "" + +# b8c70c9438f644118a68109f5eba874e +#: ../../source/contents.rst:1 c05c5b9300a24e49b44609d54664d750 +msgid "`jupyter/help repo `_" +msgstr "" + +# 72da60819619401b9a96f5504ba59c97 +#: ../../source/contents.rst:1 93298447265a4489aeff7d655e308437 +msgid "Start here for help and support questions" +msgstr "" + +# 0dc8121fb6244c189d0104edd3a0ad5d +#: ../../source/contents.rst:1 81e16684cf314696a58570a6bcb8f23a +msgid "`Jupyter mailing list `_" +msgstr "" + +# cbdb33adaed94934807dd96aad51d04c +#: ../../source/contents.rst:1 4fee8a0021d2486eb0a15f848c5d93d1 +msgid "General discussion of Jupyter's use" +msgstr "" + +# 90cd4bd7587a41baaa4fe9b254e06b73 +#: ../../source/contents.rst:1 4a9185b7b5564c9eb4f0c3aab7ac75cf +msgid "" +"`Jupyter in Education group `_" +msgstr "" + +# a53a7f1c3e0542529b17ea18db13af07 +#: ../../source/contents.rst:1 e6593a838e374634ad0b291b5d082271 +msgid "Discussion of Jupyter's use in education" +msgstr "" + +# be4502efd1b8405f9006fcc3b8d830f7 +#: ../../source/contents.rst:1 4a705b686cd64646bcf465e041a1f6c0 +msgid "`NumFocus `_" +msgstr "" + +# aad8855017f4495b9d094b28d9a17a7c +#: ../../source/contents.rst:1 97cda491b8874123aa1b99f344b91d8b +msgid "Promotes world-class, innovative, open source scientific software" +msgstr "" + +#: ../../source/contents.rst:1 d7252f4b088a46088a0dcc2c34d639dd +msgid "" +"`Donate to Project Jupyter `_" +msgstr "" + +# 46564fbd685543a9a25fb09fe204970a +#: ../../source/contents.rst:1 043e348e050f4b05b9b3dba4b61c6bff +msgid "Please contribute to open science collaboration and sustainability" +msgstr "" + +# af4b1ede6ede498c982e94e44261c974 +#~ msgid "`Donate to Project Jupyter `_" +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/contrib_docs.po b/docs/source/locale/en/LC_MESSAGES/contrib_docs.po new file mode 100644 index 000000000..b54f23f50 --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/contrib_docs.po @@ -0,0 +1,1792 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-07-06 03:44+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.8.0\n" + +#: ../../source/contrib_docs/doc-new-translation.md:1 +#: 83dcb74dbf914bb88014266e318dec91 +msgid "Supporting translations of documentation" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:3 +#: ec12f9c3c03746ef8e73887823ed4aa9 +msgid "" +"We support and encourage the translation of Jupyter documentation to " +"other languages as one way of making our community more inclusive and " +"diverse. We are working toward having a consistent model for translation " +"of Sphinx documentation across Jupyter projects based on prior work in " +"the Python and Django communities. This project " +"(https://jupyter.readthedocs.io) and the Jupyter Docker Stacks project " +"are early adopters, meant to prove out the workflows described on this " +"page." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:11 +#: 3aba6612a8bd4e728b1d47cb950fd7bb +msgid "Overview" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:13 +#: 305f57701883465a813a288875500e48 +msgid "" +"After initial project setup, changes to Sphinx documentation and its " +"translations follow a continuous integration (CI) and continuous " +"deployment (CD), much like project source code." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:16 +#: 6f99c57e47bc4bc8a61c2d2005cc1add +msgid "Who is involved in translating documentation" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:18 +#: 9e32aa58c86c4e1e87acce537b4e9141 +msgid "" +"Anyone is welcome to participate in writing and translating Jupyter " +"documentation by participating in the workflow described below. This " +"workflow has a handful of actors and components:" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:21 +#: c1fd70abb5db4978bb6f87a126c91ddd +msgid "A person who makes changes to the English project documentation" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:22 +#: 38ca9bdd22d04832bff8540641d259ce +msgid "" +"A person who translates snippets of text in the English documentations " +"into another language (locale)" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:24 +#: 6a71e8cc8ee446938fdf5534737344d3 +msgid "" +"Portable object files (.po) for the source documentation language (e.g., " +"U.S. English, en-US) and for other locales (e.g., Brazilian Portuguese, " +"pt-BR; Moroccan Arabic, ar-MA)" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:27 +#: 2bcde874b9da4373b0fa4a72506c968c +msgid "" +"A continuous integration system like TravisCI, CircleCI, or GitHub " +"Actions, responsible for" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:28 +#: 4b8dd0d33a80444e814901c3fafbc240 +msgid "ReadTheDocs, our preferred service for building and hosting documentation" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:30 +#: 10e77befcaf04997a83dae6a6f050afc +msgid "" +"Transifex, a localization platform with free plans for open source " +"projects, a friendly web interface, and support for .po files" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:33 +#: 4366c58cd7014526b2d76066f19a1ebb +msgid "The translation process" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:35 +#: 49cbe43111f848cbab48e2f9d27f329d +msgid "Translation CI/CD" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:38 +#: e40e38f4ac7b43329392f49004cdb30e +msgid "" +"A user creates or edits reStructuredText (.rst) or Markdown (.md) " +"documents written in U.S. English." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:40 +#: 55be5a89c5de454a9a54de363f58722a +msgid "The user submits a pull request on GitHub." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:41 +#: ../../source/contrib_docs/doc-new-translation.md:79 +#: 2ce7c28ffacc42379de0fd7d0c5ba28e 8e8d043b7e184b73ac1cd169f3320680 +msgid "A project maintainer reviews and merges the pull request." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:42 +#: 39c73568b6fc49ee941e900f0674668d +msgid "" +"ReadTheDocs runs Sphinx to convert U.S. English source documents into " +"HTML (e.g., " +"https://jupyter.readthedocs.io/en/latest/architecture/how_jupyter_ipython_work.html)" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:44 +#: 5011f264e6d940eb806781d5e898c2b1 +msgid "" +"Meanwhile, the CI service runs Sphinx commands to extract translatable " +"messages from U.S. English documents into en-US portable object (.po) " +"files. For example:" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:57 +#: 5be878b27245469680bea51a3f531349 +msgid "" +"The CI service commits the English .po files to the project on GitHub. " +"(e.g., " +"https://github.com/jupyter/jupyter/commit/1330bc409842d8b8a7bbb3a1c63259c34a543be0)" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:59 +#: d9c670ae026f42b0ad2508f4d71c35a5 +msgid "" +"Transifex makes the messages in the English .po files available for " +"translation in all configured languages." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:61 +#: e510379f66804ed1a0f2801711bb5bea +msgid "" +"Over time, translation teams use the Transifex web application to create," +" review, and update translations for those languages (e.g., " +"https://docs.transifex.com/translation/translating-with-the-web-editor)" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:64 +#: 6174abe41d5c4d7795242abef32239d3 +msgid "" +"Transifex submits a pull request to the GitHub project containing a " +"localized .po file when all of the English messages have been translated," +" and optionally reviewed, for a given language (e.g., " +"https://github.com/jupyter/jupyter/pull/485). For example:" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:80 +#: 0a08b3347d144ed19c17335afd20115b +msgid "" +"ReadTheDocs once again runs Sphinx to convert U.S. English source " +"documents into HTML." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:81 +#: 2e111e7e2b174acf862b2ffb12e45c22 +msgid "" +"ReadTheDocs also runs Sphinx to load localized .po files, substitute " +"translations into the original English text, and convert those translated" +" documents into HTML (e.g., " +"https://jupyter.readthedocs.io/pt_BR/latest/architecture/how_jupyter_ipython_work.html)" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:85 +#: bc585e732baa4b6992a25b6993e25dd8 +msgid "" +"Note: We recognize this flow assumes documentation starts life written in" +" U.S. English. We should look into removing this assumption in the future" +" if it becomes a significant barrier to new contributions." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:89 +#: 3e9e370a7bdc4cabbf887ea69806aa86 +msgid "Community translator workflows" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:91 +#: c12ef7e15a144dafb95e5914bcd646b9 +msgid "" +"We are delighted when members of the Jupyter community want to help " +"translate documentation. We use Transifex to on-board translators in a " +"friendly web interface without requiring knowledge of git, GitHub, " +"Sphinx, or other software developer tools." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:95 +#: 5dd0808463494a3eac7c14e73639e60e +msgid "Creating translations" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:97 +#: cb9b094433724fdbb065c7832594e4cc +msgid "" +"Getting Started as a Translator is an excellent on-boarding guide for new" +" Transifex users. Follow the instructions to create an account. When " +"prompted to join a team, look for jupyter-meta-documentation to start " +"contributing translations to this documentation site. Alternatively, " +"visit https://www.transifex.com/project-jupyter/jupyter-meta-" +"documentation/ after creating your account and request to join the " +"project. A project maintainer or language team coordinator will review " +"and approve your request." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:105 +#: 4cf1828fcbb849189627604d1d6e34a7 +msgid "Reviewing translations" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:107 +#: 76235156fd8141c2af5a461591b88dd1 +msgid "" +"Transifex supports Reviewing Translations, peer review by members of a " +"language team, to ensure translation quality. Project maintainers can " +"choose whether Transifex should immediately send a pull request when " +"translations of all text in a document are available or delay submitting " +"a pull request until after all of those translations are also reviewed " +"(the current setting for this project)." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:115 +#: 5d8c452c038f491289e674d65bb11fb9 +msgid "Coordinating translation teams" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:117 +#: 19a86f1b36114c36a37def6363bb6895 +msgid "" +"Project maintainers can also grant Transfex team members the role of " +"language coordinator. Language coordinators have permission to invite " +"users to language teams, approve or deny join requests, assign language " +"team roles, and perform other administrative actions for a particular " +"project language. Empowering trusted members of the community as " +"coordinators can help grow translation teams without software developer " +"involvement." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:124 +#: 8ca54a7752004aa0b4e1a42449d5b062 +msgid "Administrator workflows" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:126 +#: 76e5a1008ba94b7d9701021e4f97711a +msgid "" +"The translation CI/CD workflow described above requires configuration in " +"GitHub and in Transifex to function. Project maintainers can follow the " +"instructions below to enable translations for their Sphinx documentation." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:130 +#: 8f45c7e651224412b4b24ff8388cb6b1 +msgid "Creating a Transifex organization" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:132 +#: beca542f8d1f471e9c6150d80076908a +msgid "" +"Transifex organizes translation projects under organizations that mirror " +"organizations and repositories on GitHub. At present, only the " +"https://github.com/jupyter organization has a corresponding org on " +"Transifex (https://www.transifex.com/project-jupyter/public/) with the " +"following organization administrators:" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:138 +#: 6adb516ed8b8484e8070693e914befab +msgid "@choldgraf" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:139 +#: 238b081612514e9db2e466ed22842164 +msgid "@parente" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:140 +#: 0dcc769631b046e48fe4e1d69a2394b7 +msgid "@willingc" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:142 +#: d997583d0132479487e936dd79eac52f +msgid "" +"GitHub users with permissions to install applications in a GitHub org can" +" follow these instructions to create a new Transifex-GitHub organization " +"link (e.g., for https://github.com/jupyterhub, " +"https://github.com/jupyterlab)." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:146 +#: 61ea7ff28dc74699b18c9d3ee7587084 +msgid "Create a new user account at https://transifex.com." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:147 +#: a4adabca2ad04d90b55bfac74bb14049 +msgid "Complete the sign-up wizard." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:148 +#: de414c90f8ff42b8a8c3974d7b81915b +msgid "Create and name a new organization." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:149 +#: ../../source/contrib_docs/doc-new-translation.md:174 +#: 3bca157b324944429951c01d27d82c54 52d429f723524b13a5ac5f4f8075a5ed +msgid "" +"Click the organization drop down in the top right of the Transifex " +"dashboard page and select Organization Settings." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:151 +#: a759030fc91b4c70be4bc79d4a814270 +msgid "Click Details in the left sidebar." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:152 +#: b25a3567d6ed48d0b7c8f8127935aef4 +msgid "" +"Click inviting administrators in the Management section to add additional" +" admins to the Transifex org." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:154 +#: 25cd4974116748799af4446ebf060fae +msgid "Click Manage integrations in the left sidebar." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:155 +#: d69b0e9e70e14592badc41a8710dbd88 +msgid "Click Install the Transifex app in the GitHub section." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:156 +#: ed00798627a04a50adc5c39e6e4a3c2f +msgid "" +"Select the GitHub organization to associate with the new Transifex " +"organization." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:157 +#: 23425c03f37646fbbfd7c8bde594b235 +msgid "Select the repositories that Transifex will have permission to access." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:158 +#: 7c130a2f92794124bb02f1d2b2abd5a5 +msgid "" +"Return to the tab where you clicked Install the Transifex app and click " +"authorize Transifex in the GitHub section." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:160 +#: 4181a124907147fe9b8577417ad483a2 +msgid "Choose the GitHub organization you just configured in the popup dialog." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:162 +#: 4865e6e8dac348fd9c009ac4648499de +msgid "" +"Note that you can revise the GitHub-Transifex integration at any time by " +"visiting https://github.com/settings/installations." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:165 +#: 31c1ec878e0d47c79603997458d46458 +msgid "Creating a Transifex project" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:167 +#: 31556ba4ae614e078768aedb1360a5ca +msgid "" +"Transifex organization administrators can follow the instructions below " +"to configure new translation projects for GitHub projects in the GitHub " +"org corresponding to the one on Transifex." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:172 +#: ../../source/contrib_docs/doc-new-translation.md:196 +#: ../../source/contrib_docs/doc-new-translation.md:262 +#: 5a677a855a014c9d88299fb9cbfa7241 a16656f9277241fead989ebd90ee4732 +#: f8160c7c509541ef92a17f2e5089e9e9 +msgid "Visit https://www.transifex.com." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:173 +#: ../../source/contrib_docs/doc-new-translation.md:197 +#: 20840c94ad6b420c9d537b5c9b492c10 31c31a1bd2594ea48349318bd2625c13 +msgid "Sign in with the appropriate admin user account for the organization." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:176 +#: 03e618f033bd4e1dae7fead5edb48453 +msgid "Click Create new project in the lower left sidebar." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:177 +#: 83a95765de984a2388feef602f407167 +msgid "Name the translation project after the project on GitHub." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:178 +#: 21ca7a2a6c76459cbbd7a1cfac35f305 +msgid "" +"Select Public as the privacy type, indicate that the project is open " +"source, and provide the GitHub URL for the repository." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:180 +#: c8f71fe953994940b044fbd19cbd5ca8 +msgid "Select a file-based project." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:181 +#: 1e79fcfa639d439e89272a03bf30d4fe +msgid "Create a new team for the project." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:182 +#: 4ae9b8ff68fa4744a8794f8327359dc9 +msgid "Select English (en) as the source language." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:183 +#: 995ad94ef47447678a668b162f49a2c3 +msgid "Select known target languages. (You can add these later as well.)" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:184 +#: b34de8d21d474ae4a5e7fd69de1112fa +msgid "Click Create project." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:185 +#: ../../source/contrib_docs/doc-new-translation.md:263 +#: 19f8b437b1eb4235a262d27d4cab4266 1e5a091401a54bb0a8b3e5893be8c7ed +msgid "Click Settings under the project name in the left sidebar." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:186 +#: b63c38ee6f8b46759fd4ebf731cf0b38 +msgid "Click the Maintainers tab." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:187 +#: 939b7d24a8c6496a911bafddf6289fee +msgid "" +"Invite additional project maintainers, typically software developers who " +"will be responsible for maintaining the continuous integration and " +"bootstrapping language teams." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:192 +#: 7afc96952d334f3e90474afb33a92a20 +msgid "Configuring languages and teams" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:194 +#: 80d5d1f0f4744e1c8858234bf07b19c2 +msgid "" +"Transifex organization admins and project managers can add translation " +"languages to a project." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:198 +#: 301ff7c37fcb4af39e99638df75a18b3 +msgid "Click Languages under the project name in the left sidebar." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:199 +#: 1d666d9f354d4599a063555eb9fcf9bd +msgid "Click Edit languages." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:200 +#: eaa78ff1afcd485a86fe045b53a4ca6e +msgid "Add or remove target translation languages." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:201 +#: 673f2d2771794285a9626e3443b56b71 +msgid "Click Apply." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:203 +#: be8d6973cc2746ee84f5ce296c029a19 +msgid "" +"Organization admins, project maintainers, and team managers can add users" +" to translation teams with the roles of language coordinator, reviewer, " +"or translator." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:207 +#: ac29aaa93fe1479287f1e1139c20f014 +msgid "Click Teams in the top nav bar." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:208 +#: 00a036500f234510bbb7285d8633fc8a +msgid "Click the Invite Collaborators button in the top right." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:209 +#: 15b7607b8be746148a267864b5fb9ffb +msgid "" +"Enter the username, email address, or full name of a person to add to the" +" project. Note that the autocomplete in this field does not always " +"display a popup for the user you wish to invite. Confirm you've entered " +"the correct value and move on." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:212 +#: 0e2bf3414b7f49b1ad29c42390473f17 +msgid "Select the role to assign to the user." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:214 +#: 0fa16edb8b914c00b07ba81c59f67d05 +msgid "If the role applies to a specific team, select the team." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:215 +#: 2efee3042ddb4a0c9c50f7eece38445f +msgid "If the role applies to a specific language, select the language." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:216 +#: 7a3a615c268243b09e963becf0b4baca +msgid "Click Invite more to enter additional users or Send invitation." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:218 +#: b0a32a910f9342e38e48dfaae31d5026 +msgid "Configuring Transifex-GitHub integration" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:220 +#: 73c4ccd5a3cf4ea1ac1b5ca575d91e9c +msgid "" +"After configuring organization and project resources on Transifex, " +"project developers can:" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:222 +#: 5529961b4d414b89a6a83aea36c10d4d +msgid "" +"configure Sphinx to produce .po files for the source language and read " +".po files containing translations" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:224 +#: 89811c7946a543a681aed4610cdb7880 +msgid "configure Transifex to watch for source language .po file changes" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:225 +#: c58981eba95a421b974cda787eb4efbe +msgid "" +"configure the project CI service to update source language .po files when" +" contributors make changes to the source documentation" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:228 +#: 565847ca29bd4c468484155eaab2d4d4 +msgid "" +"The instructions in this section assume a git repository already contains" +" Sphinx documentation in the following directory structure:" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:241 +#: 552f9a54e3d54abd94de3b756678fcbc +msgid "" +"Project developers can do the following to configure Sphinx to seed " +"source .po files and recognization translation .po files." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:244 +#: 4fae6dfcf11d41218e98788a56123e11 +msgid "" +"Add sphinx-intl to your Sphinx project requirements.txt or " +"environment.yaml if it does not already exist." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:246 +#: d0aa4e0a35df456c87efd7ba5ab19ca3 +msgid "Run sphinx-intl create-txconfig in the docs/ directory." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:247 +#: 377afdd91f6341fea53fa860f9c27b6c +msgid "Add the following to the Sphinx source/conf.py file." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:256 +#: 44bef80bb89a4cbfb4f0a5735c2b9f31 +msgid "" +"Run make gettext to extract all strings from the English source " +"documentation." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:257 +#: 6f79fd45baad4fb781b9deccb0555c7e +msgid "Run sphinx-intl update -l en to generate the English source .po files." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:258 +#: 7c8ff647407a4b12bc3668565177bf18 +msgid "" +"Submit, review, and merge a pull request with the changes and generated " +".po files." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:260 +#: 892960d17c6b48afbbec21bc9df3c62a +msgid "" +"After merging the pull request, link to the Transifex project to the " +"GitHub repository." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:264 +#: c7aafffe93f1478a8923a367e1b7db72 +msgid "Click the Integrations tab." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:265 +#: 49a28f9db0574372923754362e2fb8df +msgid "Click Link Repository in the GitHub section." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:266 +#: 55be52bb344a482895b1c74b98ba3ce9 +msgid "" +"Select the appropriate GitHub repository and integration branch. Then " +"click Next." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:267 +#: 8eacf43753164453b87379ffc35e26e6 +msgid "" +"Copy and paste the following configuration into the dialog, adjusting the" +" commented values as appropriate, and then click Next." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:283 +#: ab9e6aede0ab4fb28833c55ce8d09c96 +msgid "" +"Select when Transifex will submit translations a back to the repository. " +"Then click Save & Sync." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:285 +#: 19911c4504504d3fa9598845a2353de4 +msgid "Click Close." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:286 +#: c9bb0d2367f04277b4b909166a238be0 +msgid "Watch the sync status progress." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:287 +#: fcfea529dc7b487093c3e60cfcbb680e +msgid "Click Resources in the left sidebar." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:288 +#: 65067827bb064f0abac66349fdc50019 +msgid "Click one of the .po files to see translation progress by language." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:289 +#: 2853c5167189464484010da1a0f7b14f +msgid "" +"Click one of the languages to see details about translation progress, " +"translate text, and review translations. See the Translator workflows " +"section above for details." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:292 +#: b2f4ece2cdfa4cf497923ec6d33dd2e2 +msgid "" +"After confirming the initial English .po files have reached Transifex, " +"set up continuous integration to ensure source strings are kept up-to-" +"date in Transifex whenever the English documentation changes. The steps " +"to accomplish this end vary depending on the CI provider. The following " +"describes how what to do when using GitHub Actions." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:297 +#: 401b9776c20947998bfcfab3d6a272c4 +msgid "" +"Create a new GitHub actions workflow file .github/workflows/gettext.yml " +"in the project." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:298 +#: 8db8ac76d1a34b58a5ea756f5f141ed2 +msgid "" +"Add the following content to the file. Note that secrets.GITHUB_TOKEN is " +"a built-in secret, not something you need to configure ahead of time." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:338 +#: 095478744919497da6d4ed941dc10c61 +msgid "Submit, review, and merge a pull request containing the workflow YAML." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:340 +#: 984be12bd3114c3c81742f35caf11ace +msgid "" +"Once you complete the steps in this section, any changes to the source " +"English documentation on the master branch are pulled into Transifex for " +"translation. Likewise, any translations completed on Transifex are " +"submitted as pull requests back to the project on GitHub." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:344 +#: 5ddb754a6a0b4809abe7c332b1718139 +msgid "Hosting translations on ReadTheDocs" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:346 +#: bce275e70ba846509248816353c12b45 +msgid "" +"ReadTheDocs supports building HTML documentation sites from a single " +"GitHub project and its translations. Administrators of the source " +"language documentation project on ReadTheDocs can following these " +"instructions to enable builds for other languages." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:350 +#: 25f9e37d7ad84053a0a4f4ece04ac89f +msgid "Visit https://readthedocs.org/dashboard/" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:351 +#: 0e525ae2a12b493aa1d1d609f6e8397d +msgid "" +"Note the name of existing ReadTheDocs project containing your source " +"language (e.g., jupyter)." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:352 +#: 431f72d042b7413e8459835c8e5ed90f +msgid "Click Import a Project." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:353 +#: d48db15517df4337a37602955290a5b1 +msgid "Click Import Manually." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:354 +#: de053c2c225545c0ad67b26c5411e8de +msgid "" +"Enter the project name you noted above suffixed with a target language " +"locale (e.g., jupyter-es, jupyter-pt-br)." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:356 +#: 8637b0dc4674437bbaa633312a61ada7 +msgid "Enter the GitHub URL of the project." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:357 +#: 3ff7979a1b44499c83309d7b48f8ab4d +msgid "Check Edit advanced project options." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:358 +#: d739deb9817c472f88e3514c8186bda2 +msgid "Click Next." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:359 +#: 7223bc91a6354627bad6750fdeabbbd4 +msgid "" +"Select the name of the target language from the Language drop down (e.g. " +"es -> Spanish, es-mx -> Mexican Spanish, pt-br -> Brazilian Portuguese)." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:361 +#: d49e063e1d214cf988c36b6073798936 +msgid "Click Finish." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:362 +#: 955e9b41433847098b2ac2189e503aa1 +msgid "Return to the list of projects at https://readthedocs.org/dashboard/" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:363 +#: 5174e3df0aad4ba1bb2d6d57557377ab +msgid "Click the project containing the source language." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:364 +#: d51dcf3ce28746908625b6e5665bf9b5 +msgid "Click Admin." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:365 +#: 77f0f83ae0a84e328d938c6c7c166a94 +msgid "Click Translations." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:366 +#: cd38e98295e24b859977c3fb3214dbf1 +msgid "" +"Choose the name of the translation project created in step 5 from the " +"Project drop down." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:367 +#: 69bb2b1f0dc3485baae7b2ccead4a3a0 +msgid "Click Add." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:368 +#: f2f6ce82ac15414fab385f6f67a8d5af +msgid "Repeat these steps for all other languages the project supports." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:370 +#: 394edf33bc20429bb9a6fcb8c054efa6 +msgid "" +"Now, any time you merge a pull request from Transifex containing .po " +"translation file updates, ReadTheDocs will build both the source " +"documentation site as well as sites for all supported languages. " +"ReadTheDocs will associate the sites with one another and make them " +"accessible via language links in a popup." +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:375 +#: de9eedbb5db54965a6367e19dd1e4d97 +msgid "ReadTheDocs popup" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:378 +#: f41c253875ee480385e34553076c782d +msgid "Reference" +msgstr "" + +#: ../../source/contrib_docs/doc-new-translation.md:380 +#: 4ce4968e8b984d77b6754afc80ec43c9 +msgid "" +"https://github.com/parente/helloworld-transifex-rtd is a mini-project " +"configured to support the entire workflow described in this document." +msgstr "" + +# bbd10f86669b4c6fb425b08981536b35 +#~ msgid "Resources section in" +#~ msgstr "" + +# 60e584f8cf344d5cbc1bd44ddb579f91 +#~ msgid "directory" +#~ msgstr "" + +# 521e95671d3349b79075277e3822bc61 +#~ msgid "" +#~ "In addition, you may need the " +#~ "following packages: sphinxcontrib-spelling, " +#~ "sphinx_rtd_theme, nbsphinx, pyenchant, recommonmark" +#~ " and jupyter_sphinx_theme, which can be " +#~ "installed via ``pip install sphinxcontrib-" +#~ "spelling sphinx_rtd_theme nbsphinx pyenchant " +#~ "recommonmark jupyter_sphinx_theme``." +#~ msgstr "" + +# e4db7b119bc747ab932bd5b9475de798 +#~ msgid "`Sphinx `_" +#~ msgstr "" + +# 232486a6287c412b99f0022d6d84e90a +#~ msgid "Building automatically on ReadTheDocs" +#~ msgstr "" + +# 27905f3382e1420588048c37cb32d617 +#~ msgid "Using the ReadTheDocs service" +#~ msgstr "" + +# 1ff476bad0cf4c0bab9ba8c06d1af401 +#~ msgid "Navigate to Settings" +#~ msgstr "" + +# c3fb69257cb4414f8c0b7af8054e4811 +#~ msgid "" +#~ "Each GitHub repo has a Settings " +#~ "tab at the far right of the " +#~ "repo menubar. Navigate to Settings and" +#~ " then the Webhooks & services submenu" +#~ " tab." +#~ msgstr "" + +# 3dedea5f462f482580216a01d0730972 +#~ msgid "Settings and Webhooks & services submenu" +#~ msgstr "" + +# e1791743951046f796933c3014462134 +#~ msgid "Add the ReadTheDocs service" +#~ msgstr "" + +# b492918cb93240ed8719e6876a9ef1d9 +#~ msgid "" +#~ "Select Add service and enter ReadTheDocs" +#~ " in the Available Services input box." +#~ msgstr "" + +# 55a4fff635a5445fb6d765c4e40ce046 +#~ msgid "" +#~ "The Services/Add ReadTheDocs window will " +#~ "open. Press the green Add service " +#~ "button to activate the ReadTheDocs " +#~ "service." +#~ msgstr "" + +# 505867437b214d4f812e8fb9b70ca0d9 +#~ msgid "Add ReadTheDocs service" +#~ msgstr "" + +# 112b55c373134049a1fc640695b3799e +#~ msgid "Success" +#~ msgstr "" + +# 4012a2bd5b4a452aa2bc78013a0ae401 +#~ msgid "Service successfully added" +#~ msgstr "" + +# c03788a9bdba433c9198fb72eaf07450 +#~ msgid "Created: 01-07-2016" +#~ msgstr "" + +# 64bec8ddf86a46e3be1010335ab3b857 +#~ msgid "Setting up a README" +#~ msgstr "" + +# f3c2890b764d4be989a58f23591ac8f4 +#~ msgid "" +#~ "On a larger scope, having the " +#~ "Jupyter name appear prominently in a " +#~ "repo's README.md file improves the " +#~ "project's name awareness." +#~ msgstr "" + +# 36da1d4b745446a184f24d86860ee5cf +#~ msgid "Recommended elements in Jupyter project repos" +#~ msgstr "" + +# d7ed0a7e260844f3929c586a5bcec7d6 +#~ msgid "Link in repo description" +#~ msgstr "" + +# 3188a81d5e804531bc59f4fc56d45db5 +#~ msgid "Please include a link to the documentation in the repo's description." +#~ msgstr "" + +# 7077cfb8652645adb68f9d5bf15d8c2b +#~ msgid "Repo description and documentation link" +#~ msgstr "" + +# 362deb326ee04287888a851b40b75f26 +#~ msgid "Badges in README" +#~ msgstr "" + +# ac386bdd61694670af3624cef2c354fa +#~ msgid "" +#~ "One common way that individuals find " +#~ "documentation is to look for and " +#~ "click on the doc badge that " +#~ "commonly is found right after the " +#~ "title. Another benefit is an easy " +#~ "visual indication if the docs are " +#~ "not rendering properly." +#~ msgstr "" + +# b7335017aa17487d8a3e44cbdc89d333 +#~ msgid "Badges in README.md" +#~ msgstr "" + +# 16fc8f66cf7b406b8c2876ba146d5761 +#~ msgid "Resources section in README" +#~ msgstr "" + +# 85c29f39bd9e4b7b9148b6d98300bf75 +#~ msgid "" +#~ "A Resources section at the end of" +#~ " the README.md gives useful links and" +#~ " information to users about the " +#~ "individual project and the larger " +#~ "Project Jupyter organization. Make sure " +#~ "to include any links to the " +#~ "individual project's demo notebooks, if " +#~ "available." +#~ msgstr "" + +# e3415ff12b4b44e49f2851fb583115a4 +#~ msgid "The Resources section includes:" +#~ msgstr "" + +# 1b42fb1633d64f88b651ae5509fc2bea +#~ msgid "Resources section in README.md" +#~ msgstr "" + +# 49575d164ce8451592d3bc3717307aa3 +#~ msgid "Checklist adding docs to a new or existing GitHub Repo" +#~ msgstr "" + +# f07c40e2f2e647e8b825d52f3563785e +#~ msgid "[ ] Add badges to README (Edit README.md and submit pull request)" +#~ msgstr "" + +# bf01c15439204d35b9a4a91ffc86f239 +#~ msgid "" +#~ "[ ] Add resources section to " +#~ "README (Edit README.md and submit pull" +#~ " request)" +#~ msgstr "" + +# 335e33a3a2ec4b8994a769c697be5039 +#~ msgid "Dated: 1-4-2016 Revised: 1-7-2016" +#~ msgstr "" + +# 785e0d441719499ab42d427cbc7d6247 +#~ msgid "Structuring a repo for docs" +#~ msgstr "" + +# 90d5b35701d841f49957792e24da870a +#~ msgid "Root level of the repo" +#~ msgstr "" + +# d0b32743c3ad4a5886315590d3892ea0 +#~ msgid "docs directory : All source files for documentation go here." +#~ msgstr "" + +# d57907b568b343cca47c18ffaeb3671e +#~ msgid "" +#~ "readthedocs.yml : configuration file for " +#~ "readthedocs to build using conda" +#~ msgstr "" + +# 7367f9983e43442b8e2e72da5ed51518 +#~ msgid "Repo root directory" +#~ msgstr "" + +# 98dae640b1424bad968989a88f0bbbac +#~ msgid "Inside the docs directory" +#~ msgstr "" + +# 777d45f1bb1646df8b6ad7aad5debcb9 +#~ msgid "" +#~ "source directory : contains all content" +#~ " source files in .rst, .md, or " +#~ ".ipynb" +#~ msgstr "" + +# eecddf6ec78e476da0f09fa9a5ca6ffa +#~ msgid "makefile : used by Sphinx to build the docs" +#~ msgstr "" + +# 28bc9914229b4259b586741106d9d7a3 +#~ msgid "environment.yml : conda build instructions" +#~ msgstr "" + +# cf9eb215541d434c85b47db86d4444d9 +#~ msgid "docs directory" +#~ msgstr "" + +# 18b0121e5dbd4d0cbfdc139f2087f09c +#~ msgid "Sphinx" +#~ msgstr "" + +# a3e4b0243ffd4bf5bddada96c44151e6 +#~ msgid "conf.py : Sphinx configuration file" +#~ msgstr "" + +# c9f4d0451fdc454fb3f359696e241f9a +#~ msgid "index.rst of contents.rst : Sphinx master table of contents file" +#~ msgstr "" + +# dc22bda3587e4032942c8c8e4474a2c6 +#~ msgid "_static directory : contains images, drawings, icons" +#~ msgstr "" + +# 9c91324873de4da996554cd0d18ec4a9 +#~ msgid "_templates directory: overrides theme templates and layouts" +#~ msgstr "" + +# ca1c2a5b5670489ebfb0fcabba566457 +#~ msgid "" +#~ "build directory : html files generated" +#~ " by Sphinx (do not check this " +#~ "directory into GitHub)" +#~ msgstr "" + +# 8951f6f4ecb1413bbb04b398218015c5 +#~ msgid "Setting up a project's documentation infrastructure" +#~ msgstr "" + +# 7cdfc8fab5b84b2a888d19fbfe55aa37 +#~ msgid "Contents:" +#~ msgstr "" + +# 1bde3a53c29249958887df3f45554bdf +#~ msgid "" +#~ "This section helps a contributor set " +#~ "up the documentation infrastructure for " +#~ "a new project or an existing " +#~ "project without Sphinx documentation." +#~ msgstr "" + +#~ msgid "# Building automatically on ReadTheDocs" +#~ msgstr "" + +# fbc01acaa56d459985a5988de5128194 +#~ msgid "" +#~ "This explains how to automatically " +#~ "rebuild documentation on ReadtheDocs every " +#~ "time a pull request is merged into" +#~ " its corresponding GitHub repo." +#~ msgstr "" + +#~ msgid "## Using the ReadTheDocs service" +#~ msgstr "" + +# 548f76347eeb494da8083cb3c13d39f2 +#~ msgid "" +#~ "Webhooks and services can be enabled " +#~ "in GitHub repo settings to allow " +#~ "third party services such as " +#~ "ReadTheDocs. The ReadTheDocs service rebuilds" +#~ " the project documentation whenever a " +#~ "pull request is merged into the " +#~ "GitHub repo." +#~ msgstr "" + +#~ msgid "### Navigate to Settings" +#~ msgstr "" + +#~ msgid "" +#~ "Each GitHub repo has a Settings " +#~ "tab at the far right of the " +#~ "repo menubar. Navigate to Settings and" +#~ " then the **Webhooks & services** " +#~ "submenu tab." +#~ msgstr "" + +#~ msgid "" +#~ "![Settings and Webhooks & services " +#~ "submenu](static/gh-webhooks-services.png " +#~ "\"Screenshot of GitHub repo settings\")" +#~ msgstr "" + +#~ msgid "### Add the ReadTheDocs service" +#~ msgstr "" + +#~ msgid "" +#~ "Select **Add service** and enter " +#~ "*ReadTheDocs* in the **Available Services**" +#~ " input box." +#~ msgstr "" + +#~ msgid "" +#~ "The Services/Add ReadTheDocs window will " +#~ "open. Press the green **Add service**" +#~ " button to activate the ReadTheDocs " +#~ "service." +#~ msgstr "" + +#~ msgid "" +#~ "![Add ReadTheDocs service](static/gh-add-" +#~ "rtd.png \"Screenshot of adding ReadTheDocs " +#~ "service\")" +#~ msgstr "" + +#~ msgid "### Success" +#~ msgstr "" + +# f38a664a1d164422ae6a4aa7b3d5bb50 +#~ msgid "" +#~ "The ReadTheDocs service is added " +#~ "successfully. The service will take " +#~ "effect on the next merged pull " +#~ "request to the project repo." +#~ msgstr "" + +#~ msgid "" +#~ "![Service successfully added](static/gh-rtd-" +#~ "hook-success.png \"Screenshot of service " +#~ "successfully added\")" +#~ msgstr "" + +#~ msgid "*Created: 01-07-2016*" +#~ msgstr "" + +#~ msgid "# Setting up a README" +#~ msgstr "" + +# d22ac7f8b0574e0493a17b325c369177 +#~ msgid "" +#~ "Providing users and developers consistency " +#~ "across repos is a valuable time " +#~ "saver and improves user productivity." +#~ msgstr "" + +#~ msgid "" +#~ "On a larger scope, having the " +#~ "Jupyter name appear prominently in a " +#~ "repo's `README.md` file improves the " +#~ "project's name awareness." +#~ msgstr "" + +#~ msgid "## Recommended elements in Jupyter project repos" +#~ msgstr "" + +#~ msgid "" +#~ "### Link in repo description Please " +#~ "include a link to the documentation " +#~ "in the repo's description." +#~ msgstr "" + +#~ msgid "" +#~ "![Repo description and documentation " +#~ "link](static/repo-description.png \"Screenshot of" +#~ " documentation link in GitHub repo " +#~ "description\")" +#~ msgstr "" + +#~ msgid "" +#~ "### Badges in README One common " +#~ "way that individuals find documentation " +#~ "is to look for and click on " +#~ "the doc badge that commonly is " +#~ "found right after the title. Another " +#~ "benefit is an easy visual indication " +#~ "if the docs are not rendering " +#~ "properly." +#~ msgstr "" + +#~ msgid "" +#~ "![Badges in README.md](static/repo-badges.png " +#~ "\"Screenshot of badges displayed under " +#~ "the repo title in the README " +#~ "file\")" +#~ msgstr "" + +#~ msgid "### Resources section in README" +#~ msgstr "" + +#~ msgid "" +#~ "A *Resources* section at the end " +#~ "of the `README.md` gives useful links" +#~ " and information to users about the" +#~ " individual project and the larger " +#~ "Project Jupyter organization. Make sure " +#~ "to include any links to the " +#~ "individual project's demo notebooks, if " +#~ "available." +#~ msgstr "" + +#~ msgid "The *Resources* section includes:" +#~ msgstr "" + +#~ msgid "" +#~ "![Resources section in `README.md`](static/repo-" +#~ "resources.png \"Screenshot of resource list" +#~ " at end of README file\")" +#~ msgstr "" + +#~ msgid "## Checklist adding docs to a new or existing GitHub Repo" +#~ msgstr "" + +# 4843875169d544fca6173c7f5221420c +#~ msgid "" +#~ "[ ] Add a link to documentation" +#~ " in repo description (requires GitHub " +#~ "repo privileges)" +#~ msgstr "" + +#~ msgid "[ ] Add badges to README (Edit `README.md` and submit pull request)" +#~ msgstr "" + +#~ msgid "" +#~ "[ ] Add resources section to " +#~ "README (Edit `README.md` and submit pull" +#~ " request)" +#~ msgstr "" + +#~ msgid "*Dated: 1-4-2016* *Revised: 1-7-2016*" +#~ msgstr "" + +# 7f017745d5c34b3f91c54f653b2793d1 +#~ msgid "Tools for documentation" +#~ msgstr "" + +# f82aa18212984518ac1371f956fc5f12 +# 0e6a4fd1bdd7427dbc0d45d78f5cd710 +#~ msgid "Contents" +#~ msgstr "" + +# 70ea135c1ab44fbba9a46a8f7992d014 +#~ msgid "Packages" +#~ msgstr "" + +# 0cd99c51dc1344f2a28d229978446fdb +#~ msgid "" +#~ "For user documentation, contributor guides," +#~ " and communications content, we use:" +#~ msgstr "" + +#~ msgid "`Sphinx `_" +#~ msgstr "" + +# 89cb08a083b7405b899da55da2c386dc +#~ msgid "" +#~ "For developer API documentation (especially" +#~ " for JupyterLab js repos), we use:" +#~ msgstr "" + +# 66229f6c114e4652b13bd066643cae2a +#~ msgid "`swagger `_" +#~ msgstr "" + +# 4241f08f75b745cc91401487dfb43473 +#~ msgid "Source file formats" +#~ msgstr "" + +# 0e502ec731f24f729b096c7ef2aac637 +#~ msgid "" +#~ "We use the following input source " +#~ "file formats when developing Sphinx " +#~ "documentation:" +#~ msgstr "" + +# c35638daf71349ab94f174d9c40088fa +#~ msgid "reStructuredText (``.rst``)" +#~ msgstr "" + +# 31a7dcfa85f545308ff3c24f7f5fa6da +#~ msgid "Markdown (``.md``)" +#~ msgstr "" + +# 99f22d7ed28e4ec6b6739ab4d3b0fca1 +#~ msgid "Notebook (``.ipynb``)" +#~ msgstr "" + +# 6bc8c61685c94741b9a52990ac840a31 +#~ msgid "" +#~ "A modern code editor should be " +#~ "used. Many are available including Atom," +#~ " SublimeText, gedit, vim, emacs. `Atom " +#~ "`_ is a good choice " +#~ "for new contributors." +#~ msgstr "" + +# 36d19549dd2e4365a6c5e8e035cd54c6 +#~ msgid "Sphinx themes" +#~ msgstr "" + +# 1eb43a99bb26411382f63038cc477cee +#~ msgid "Our projects use the following themes:" +#~ msgstr "" + +# 29670e07c5044935b15456980e34fae1 +#~ msgid "sphinx_rtd_theme (currently used by Jupyter projects)" +#~ msgstr "" + +# f9cd1912e9bc4bd79e22274b5ce9acdf +#~ msgid "jupyter_sphinx_theme (used by ipywidgets)" +#~ msgstr "" + +# d987578c0b164c1ba1296f4b300cac54 +#~ msgid "Git and Github Resources" +#~ msgstr "" + +# 50b964b050404597b31edeb7431ffb85 +#~ msgid "" +#~ "If this is your first time working" +#~ " with Github or git, you can " +#~ "leverage the following resources to " +#~ "learn about the tools." +#~ msgstr "" + +# 0b58d8ea7318429ba17fb25d493dbe11 +#~ msgid "`Try Git `_" +#~ msgstr "" + +# 319d5b76f66a42d3894269987178b99c +#~ msgid "`Github Guides `_" +#~ msgstr "" + +# 3b0ab86be2604595be117b97ae517309 +#~ msgid "`Git Real `_" +#~ msgstr "" + +# 9bf487d7abfc44c3ab65fc60610916db +#~ msgid "`Git Documentation `_" +#~ msgstr "" + +# 6f130c2608c74cd481206a5302ce6ab4 +#~ msgid "" +#~ "`Git Rebase `_" +#~ msgstr "" + +# 73369309d0264c91801dadff4096eda3 +#~ msgid "Understanding our workflow" +#~ msgstr "" + +# 3ad46563bdea4c718af906b06996645d +#~ msgid "**High level documentation workflow**" +#~ msgstr "" + +# bea011364bb5447f9a5ee2e0a1813bb7 +#~ msgid "Identify a documentation change." +#~ msgstr "" + +# 0ecc5172dfa9449bb3fd7ddee5ab7a8f +#~ msgid "*Typos:* please go ahead and fix it (or report as a bug)." +#~ msgstr "" + +# d2eec42d01aa43c49c9f599c56cf67f7 +#~ msgid "" +#~ "*Open issues:* leave a note in the" +#~ " issue comments that you are working" +#~ " on the issue." +#~ msgstr "" + +# 5594fd91be4844ba8361a65dfea30f57 +#~ msgid "" +#~ "*New documentation:* open an issue with" +#~ " your idea or suggestion. We'll " +#~ "review the issue and work with you" +#~ " to identify next steps." +#~ msgstr "" + +# df7b4d15c41f4003b695a2e4ba5f9257 +#~ msgid "Update the source file." +#~ msgstr "" + +# 0a600b26d0214280b77a6ae44f71294f +#~ msgid "Commit the change." +#~ msgstr "" + +# 241782c238de4ebeb594ebe6cc2fe7a6 +#~ msgid "Test changes locally." +#~ msgstr "" + +# b8f4ff91d74f453e8e4c680f537967de +#~ msgid "Open a pull request." +#~ msgstr "" + +# e943c50580c64ecaa32dd38a2ac2f8e2 +#~ msgid "Check response of automated tests." +#~ msgstr "" + +# 47edb06fb3c0469f87b591aa0e30925c +#~ msgid "" +#~ "If tests pass: Nice job. Wait for" +#~ " reviewer feedback and/ or your pull" +#~ " request to be merged." +#~ msgstr "" + +# 6b9c7c1cbd7d4772a778cc9c2f33a0d4 +#~ msgid "" +#~ "If tests show an error: Revise and" +#~ " resubmit your pull request. You do" +#~ " not need to open a new pull" +#~ " request. If needed, please ask for" +#~ " assistance." +#~ msgstr "" + +# 6c100a83bc8547909df09e2de4fa16f2 +#~ msgid "Celebrate your documentation contribution." +#~ msgstr "" + +# 7f491e4696da4e01af2e68b97352a3f4 +#~ msgid "" +#~ "Repeat. If you would like suggestions" +#~ " for a new documentation issue to " +#~ "work on, please ask." +#~ msgstr "" + +# 4837ec4c20d84023875b77de40950374 +#~ msgid "Thanks for contributing!" +#~ msgstr "" + +# 96f8c8d5bd6b48b79a6fbfdadfe293b9 +#~ msgid "Getting started" +#~ msgstr "" + +# 41b8445aaef14b0f9277132ef8f7c64d +#~ msgid "Preparing for your first contribution" +#~ msgstr "" + +# 5ff1615eb97f4322bc6b824fe2975e78 +#~ msgid "Our documentation uses reStructured Text as well as Jupyter notebooks." +#~ msgstr "" + +# 4f862af8ce2648e6a6f36a65f166c17a +#~ msgid "We use Sphinx extensively to build documentation." +#~ msgstr "" + +# 074f79e5aada4cf48e49e75da9a6f2e4 +#~ msgid "We host our documentation on Read the Docs." +#~ msgstr "" + +# 273c21f2f4c64cdc905c4b9c65df07e6 +#~ msgid "Developing your contribution" +#~ msgstr "" + +# d34708a450ae4c98b03feb4ff944a1cc +#~ msgid "" +#~ "Jupyter's documentation is split across " +#~ "several projects, listed on the `Jupyter" +#~ " documentation home page " +#~ "`_. These " +#~ "instructions apply to all Jupyter " +#~ "projects, though some projects have " +#~ "further contribution guidelines." +#~ msgstr "" + +# 583255d870384645b0b076e657c2e763 +#~ msgid "Clone the repository" +#~ msgstr "" + +# 024a7bc45f3a45fab5500b2d1904d9bc +#~ msgid "" +#~ "Fork the appropriate project repository " +#~ "on GitHub, depending on which project's" +#~ " documentation you want to contribute " +#~ "to." +#~ msgstr "" + +# 7e9da73cdb4c469db3dce5d160b5208a +#~ msgid "Clone the repository to your system." +#~ msgstr "" + +# 9e4c1b704e594ce19b00ef8075748237 +#~ msgid "Edit the documentation source file" +#~ msgstr "" + +# a6b8f285170c4f8eb6aecdd1cbfdb7b9 +#~ msgid "" +#~ "Source files for projects are typically" +#~ " found in the project's ``docs/source`` " +#~ "directory. The reStructured text filenames " +#~ "end with ``.rst``, and Jupyter notebook" +#~ " files end with ``.ipynb``." +#~ msgstr "" + +# 8b7b25fa65204498b0a9266c8541311e +#~ msgid "" +#~ "In your favorite text editor, make " +#~ "desired changes to the ``.rst`` file " +#~ "when working with a reStructured text" +#~ " source file." +#~ msgstr "" + +# 28f854c4861346b09d69499d50d03dd4 +#~ msgid "" +#~ "If a notebook file requires editing, " +#~ "you will need to install Jupyter " +#~ "notebook according to the :ref:`Installation" +#~ " ` document. Then, run the " +#~ "Jupyter notebook and edit the desired" +#~ " file. Before saving the Jupyter " +#~ "``.ipynb`` file, please clear the output" +#~ " cells. Save the file and test " +#~ "your change." +#~ msgstr "" + +# 41995af34a5046bca276d62634ae3b10 +#~ msgid "Testing changes" +#~ msgstr "" + +# 65e377a9fbe04a0b8775881db9467ab8 +#~ msgid "" +#~ "Sphinx should be installed to test " +#~ "your documentation changes. For best " +#~ "results, we recommend that you install" +#~ " the stable development version Sphinx " +#~ "(``pip install git+https://github.com/sphinx-" +#~ "doc/sphinx@stable``) or the current released" +#~ " version of Sphinx (``pip install " +#~ "sphinx``)." +#~ msgstr "" + +# 5d5be81cd19e45f5acc196516a7aa1ec +#~ msgid "" +#~ "In addition, you may need the " +#~ "following packages: sphinxcontrib-spelling, " +#~ "sphinx_rtd_theme, nbsphinx, pyenchant, recommonmark" +#~ " 0.4.0 and jupyter_sphinx_theme, which can" +#~ " be installed via ``pip install " +#~ "sphinxcontrib-spelling sphinx_rtd_theme nbsphinx " +#~ "pyenchant recommonmark==0.4.0 jupyter_sphinx_theme``." +#~ msgstr "" + +# 1140b74d6bd547d2923b29eb2c769293 +#~ msgid "" +#~ "If you are on Linux, you may " +#~ "also need to install the Enchant C" +#~ " library by running ``sudo apt-get" +#~ " install enchant``." +#~ msgstr "" + +# 710e465eeb7d49f8bcf3279361e211ea +#~ msgid "" +#~ "Once everything is installed, the " +#~ "following commands should be executed " +#~ "using the Terminal/command line from the" +#~ " ``docs`` directory:" +#~ msgstr "" + +# 874edec47dfe41aab09ca2dc976ac9be +#~ msgid "" +#~ "``make html`` builds a local html " +#~ "version of the documentation. The output" +#~ " message will either display errors " +#~ "or provide the location of the " +#~ "html documents. For example, the " +#~ "location provided may be ``build/html`` " +#~ "and to view these documents in " +#~ "your browser enter ``open " +#~ "build/html/index.html``." +#~ msgstr "" + +# 3c47075546064151940cfddaa6b97e97 +#~ msgid "" +#~ "``make linkcheck`` will check whether " +#~ "the external links in the documentation" +#~ " are valid or if they are not" +#~ " longer current (i.e. cause a 500 " +#~ "not found error)." +#~ msgstr "" + +# 3b5e8519815b43ab82350bed26580555 +#~ msgid "" +#~ "Note: We recommend using Python 3.4+ " +#~ "for building the documentation. If you" +#~ " are editing the documentation, you " +#~ "can use Python 2.7.9+ or the " +#~ "Github editor." +#~ msgstr "" + +# 3a598ce6355d49589108ebb8b3584478 +#~ msgid "Creating a pull request" +#~ msgstr "" + +# c5b5c1b181a54762a10f3d97ce5d19e8 +#~ msgid "" +#~ "Once you are satisfied with your " +#~ "changes, submit a GitHub pull request," +#~ " per the instructions above. If the" +#~ " documentation change is related to " +#~ "an open GitHub issue, please mention " +#~ "the issue number in the pull " +#~ "request message." +#~ msgstr "" + +# 4ae44c0cf02a45b99d0c7f14640c4f6e +#~ msgid "" +#~ "A project reviewer will look over " +#~ "your changes and provide feedback or " +#~ "merge your changes into the " +#~ "documentation." +#~ msgstr "" + +# baccae949fb54e6491856084b68e4827 +#~ msgid "Asking questions" +#~ msgstr "" + +# 990c9e57e8fc4e9c9da2ea3980ddebac +#~ msgid "" +#~ "Feel free to ask questions in the" +#~ " Google Group for Jupyter or on " +#~ "an open issue on GitHub." +#~ msgstr "" + +# 6ad43967c19843df85781d3ee0ba0658 +#~ msgid "Documentation Guide" +#~ msgstr "" + +# e53cdb8f3ebb4f9d97c7824dfd462fef +#~ msgid "**Contents**" +#~ msgstr "" + +# 8710f55c2e51435881a40b68457010b8 +#~ msgid "" +#~ "Documentation helps guide new users, " +#~ "fosters communication between developers, and" +#~ " shares tips and best practices with" +#~ " other community members. That's why " +#~ "the Jupyter project is focused on " +#~ "documenting new features and to keeping" +#~ " the documentation up-to-date." +#~ msgstr "" + +#~ msgid "# Structuring a repo for docs" +#~ msgstr "" + +#~ msgid "## Root level of the repo" +#~ msgstr "" + +#~ msgid "``docs`` directory : All source files for documentation go here." +#~ msgstr "" + +#~ msgid "" +#~ "``readthedocs.yml`` : configuration file for" +#~ " readthedocs to build using conda" +#~ msgstr "" + +#~ msgid "" +#~ "![Repo root directory](static/repo-root.png " +#~ "\"Screenshot of GitHub repo root\")" +#~ msgstr "" + +#~ msgid "## Inside the docs directory" +#~ msgstr "" + +#~ msgid "" +#~ "``source`` directory : contains all " +#~ "content source files in ``.rst``, " +#~ "``.md``, or ``.ipynb``" +#~ msgstr "" + +#~ msgid "``makefile`` : used by Sphinx to build the docs" +#~ msgstr "" + +#~ msgid "``environment.yml`` : conda build instructions" +#~ msgstr "" + +#~ msgid "" +#~ "![``docs`` directory](static/docs-directory.png " +#~ "\"Screenshot of docs directory\")" +#~ msgstr "" + +#~ msgid "## Sphinx" +#~ msgstr "" + +#~ msgid "``conf.py`` : Sphinx configuration file" +#~ msgstr "" + +#~ msgid "" +#~ "``index.rst`` of ``contents.rst`` : Sphinx " +#~ "master table of contents file" +#~ msgstr "" + +#~ msgid "``_static`` directory : contains images, drawings, icons" +#~ msgstr "" + +#~ msgid "``_templates`` directory: overrides theme templates and layouts" +#~ msgstr "" + +#~ msgid "" +#~ "``build`` directory : html files " +#~ "generated by Sphinx (do not check " +#~ "this directory into GitHub)" +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/contributing.po b/docs/source/locale/en/LC_MESSAGES/contributing.po new file mode 100644 index 000000000..08330be2a --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/contributing.po @@ -0,0 +1,7606 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2020. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2021-02-28 00:41+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.9.0\n" + +#: ../../source/contributing/communication-contributions.rst:3 +#: 3a48728f7bca4c35a3ffcba8d0a17ccf +msgid "Communications Guide" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:6 +#: ../../source/contributing/dev-contributions/contrib_guide.rst:6 +#: ../../source/contributing/docs-contributions/doc-tools.rst:5 +#: ../../source/contributing/docs-contributions/getting-started.rst:5 +#: ../../source/contributing/start-contributing.rst:6 +#: 073374d1502549b7878ed1961ecfe9e2 27a67c8134a64053af215f0e0fe85475 +#: 46a85edb1b5747d99529da69fd0558dd fcb56ef4731d402f9c94a204e73091f8 +#: fd8a6b5a7e934142bff69f7244c22834 +msgid "Contents" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:9 +#: bd99471ba84444fe925d271b8e727ffb +msgid "Blog" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:11 +#: 4d1eb01f0d574d7885ddd429590456b3 +msgid "" +"We publish our blog at ``_. We welcome ideas " +"for posts or guest posts to the Jupyter blog. If you have a suggestion " +"for a future post, please feel free to share your idea with us. We would " +"like to discuss the idea with you." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:16 +#: ee59eae250014360b7eb425c3a1c3d77 +msgid "" +"Do you enjoy writing? Please contact us about becoming a guest blogger. " +"We can help guide you through the process of creating a post." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:20 +#: b30de3bc4c524ed1ba5f1b0c5d0298f3 +msgid "Technical overview" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:22 +#: b92614e7b6284d6e865cb59854292a2b +msgid "" +"Jupyter's blog uses the Ghost blog platform for its contributor " +"flexibility and ease of use. Jupyter's blog is deployed at " +"``_." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:26 +#: 892d40217212430180a29c99b4acfbcf +msgid "Basic workflow from blog idea to published post" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:28 +#: 45e9e12f5274452eb91e5571129a1e02 +msgid "" +"There are several major steps in the workflow from blog idea to a " +"published post including:" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:31 +#: baed0ed084954f4692b6aeedb34b846d +msgid "Be inspired to write a post" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:32 +#: 970403a7ed1f42249119226089f02b49 +msgid "" +"Send us a message on the Jupyter mailing list and ask us for an author " +"account on our blog" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:33 +#: ../../source/contributing/communication-contributions.rst:42 +#: 34f132326872472399492b713c2fec78 67a284a2432b4034b58303faacee8247 +msgid "Creating a draft" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:34 +#: 057010aafc914fec90bf739bc5a9182f +msgid "Draft Review" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:35 +#: ../../source/contributing/communication-contributions.rst:99 +#: 5bc661048d184d62abf853746b67a037 60afc776a22041a5b949fa0e1b007238 +msgid "Editorial acceptance" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:36 +#: ../../source/contributing/communication-contributions.rst:102 +#: 55d61cc2f1814f9aaab93a65361c6772 a86d78ecb86247b0ad42eb42c47e37ed +msgid "Publishing the post" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:38 +#: cfc77f2441af4b5bb7ed67a32222439f +msgid "" +"We'll cover each of these as well as how to update a post once it has " +"been published." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:45 +#: 7a1b8a979d4246328ca46da770c2f717 +msgid "Title and metadata" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:47 +#: c8e7bc7057b24f8d9554020875627fb4 +msgid "" +"Always check in the metadata fields that a blog post has a title and a " +"canonical URL. It is possible to put the date in the canonical URL, in " +"particular for events like jupyter-day, that can occur several times. The" +" date of the event can differ from the date of the blog post." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:52 +#: 3bbf7eabc55e41d99ac459bb6c751c70 +msgid "" +"Once a post is published, **never** change the post's title or the url. " +"These changes will break links of tweets and RSS feeds that have already " +"referenced the existing, published URL. Keep in mind that when publishing" +" some platforms cache the url immediately; as a result changing the title" +" will direct people to a 404 page." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:58 +#: 7a37b89bc53d47d0ac300fe533fb5d23 +msgid "" +"Title and metadata can always be refined after the actual content of the " +"blog is written, but should not be changed after publication. As a guest " +"you do not have to worry about metadata, the editor or admins will take " +"care of that." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:63 +#: 5a6e6e35bb764fa8a027ae7e8d07bce0 +msgid "Working with images" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:65 +#: dc87867e48ff4041bc6865af2f1c7e65 +msgid "" +"Try not to link to external images. If you want to put an image in the " +"post, insert ``![]()`` in the editor view and drag and drop an image from" +" your desktop into the newly created field in the preview. External " +"images can change, and can break the blog post if they are taken down. " +"This cannot append if you drag and drop images. Moreover, these images " +"will be served from the same CDN (Content Delivery Network) as the blog, " +"which will insure the best overall experience for our readers." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:73 +#: 18f1a29c1ca2400e980d7bc78ae434a6 +msgid "" +"The featured image you see at the top of a blog posts is set from within " +"the metadata field, not using the `![]()`. The featured image is treated " +"differently than inlined images by many feedreaders (especially on " +"mobile) and allows a user on a slow connection to read the content of the" +" blog earlier, which is a much better experience for the user than " +"waiting for the featured image to render." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:80 +#: bd9891ed006441d59322812923f0ed0e +msgid "Links" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:82 +#: 9c3dba1548654201b9f793ab6ea124e7 +msgid "" +"Do not use minified links when possible. The multiple redirects of " +"minified links degrades the mobile browsing experience. If you need " +"analytics of the number of page views, this information is tracked by " +"Google Analytics." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:87 +#: 12539f1dac324801a4b79d1c266f7834 +msgid "Draft review" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:90 +#: 2ea273e90bdc4f449f1f24e4e88b9f9d +msgid "Ask for a review" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:92 +#: 5727f3a922b54b6eafc94baf87463614 +msgid "" +"Once you think you are done, ask someone else to reread your post, and " +"check the various parameters that you might have forgotten before " +"publishing. You are not on your own, this is teamwork, we are here to " +"help you. If we do things in a hurry you will probably spend more time " +"fixing mistakes that actually doing things right in a first place." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:104 +#: 24846c8891a247cabaaf61e416ea9721 +msgid "" +"Usually an editor or admin will take care of publishing the post. The " +"task of the Editor/Admin is to check all metadata are correctly set, that" +" no external images are used, as well as all other quality check describe" +" before." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:108 +#: 8402165c9f78492f9ef430d086753e9d +msgid "It is then just a matter of making th post visible to everyone." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:111 +#: 7263302f62024139a9bf87a67281bf0b +msgid "Changing an existing post" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:114 +#: fe137941910740c5b331fda039e4d085 +msgid "Posts Updates" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:116 +#: ff5a3d9a7c974a6b9692cb8f10dfd570 +msgid "" +"Blog subscribers may receive notification at every update. So use updates" +" and fixes parsimoniously. It is OK to wait a few hours to fix a typo." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:119 +#: 035aa79dcb804bee9234db146f8e5d7d +msgid "" +"If some substantial updates have to be made, like change of location, " +"time etc, please insert an `[Update]` section at top (or bottom of the " +"blog post depending on importance) with the Date/Time of the update. If " +"the information in the body of the blog is wrong, try not to replace it, " +"and just use strike-through to mark it as obsolete. This would help " +"reader determine which information is correct when dealing with multiple " +"source giving different information." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:128 +#: 05095693d7034bc3b846fa04f8965b17 +msgid "Newsletter" +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:130 +#: ../../source/contributing/communication-contributions.rst:136 +#: 10bce39530c848b4803a2ec8b5b7b68c 7bb00732a60346c0aa11c15c22272b3b +msgid "Documentation in progress." +msgstr "" + +#: ../../source/contributing/communication-contributions.rst:134 +#: bc37472c89a54d8b8a5ec6ae20a53889 +msgid "Website" +msgstr "" + +#: ../../source/contributing/content-contributor.rst:2 +#: 8f0601935d4d4e008e37c7d5cd60babd +msgid "Contributing" +msgstr "" + +#: ../../source/contributing/content-contributor.rst:14 +#: 8245ccdb14ec4b47a6f716db031a03cb +msgid "" +"Whether you are a new, returning, or current contributor to Project " +"Jupyter's subprojects or IPython, **we welcome you**." +msgstr "" + +#: ../../source/contributing/content-contributor.rst:17 +#: 82e19741d87a42529be4a34749e9e612 +msgid "" +"Project Jupyter has seen steady growth over the past several years, and " +"it is wonderful to see the many ways people are using these projects. As " +"a result of this rapid expansion, our project maintainers are balancing " +"many requirements, needs, and resources. We ask contributors to take some" +" time to become familiar with our contribution guides and spend some time" +" learning about our project communication and workflow." +msgstr "" + +#: ../../source/contributing/content-contributor.rst:24 +#: b88e133f5cee4caa9e6bb5b2ee6b0da4 +msgid "" +"The Contributor Guides and individual project documentation offer " +"guidance. If you have a question, please ask us. `Community Resources " +"`_ provides information on our " +"commonly used communication methods." +msgstr "" + +#: ../../source/contributing/content-contributor.rst:29 +#: 04d38c68fdd64bbe8d6340d5ee64c40a +msgid "" +"We are very pleased to have you as a contributor, and we hope you will " +"find valuable your impact on the projects. **Thank you** for sharing your" +" interests, ideas, and skills with us." +msgstr "" + +#: ../../source/contributing/content-contributor.rst:34 +#: a34c9e08cd624f4b8bf47687c95fdee8 +msgid "Do I really have something to contribute to Jupyter?" +msgstr "" + +#: ../../source/contributing/content-contributor.rst:36 +#: 2b3f4b8cad0f4305975910e603644182 +msgid "" +"Absolutely ✅. There are always ways to contribute to this community! " +"Whether it is is contributing code, improving documentation and " +"communications, teaching others, or participating in conversations in the" +" community, we welcome and value your contribution!" +msgstr "" + +#: ../../source/contributing/content-contributor.rst:42 +#: 800ce4ae20a140589f772ceb5663417a +msgid "What kinds of contributions can I make?" +msgstr "" + +#: ../../source/contributing/content-contributor.rst:44 +#: 4cede984f525459ca6d8119e8e94f8c8 +msgid "" +"The following sections try to provide inspirations for different ways " +"that you can contribute to the Jupyter ecosystem. They're non-complete - " +"if you can think up any way to make an improvement, we appreciate it!" +msgstr "" + +#: ../../source/contributing/content-contributor.rst:49 +#: 8d8387d5e7cf40ee85d4491e54852274 +msgid "Improving documentation" +msgstr "" + +#: ../../source/contributing/content-contributor.rst:51 +#: 1c71f4af2db142d9bf50d440d8ff96cd +msgid "" +"One of the most important parts of the Jupyter ecosystem is its " +"documentation. Good documentation makes it easier for users to learn how " +"to use the tools. It also makes it easier to teach others, and to " +"maintain and improve the code itself. There are many ways to improve " +"documentation, such as **reading tutorials and reporting confusing " +"parts**, **finding type-os and minor errors in docs**, **writing your own" +" guides and tutorials**, **improving docstrings within the code**, and " +"**improving documentation style and design**." +msgstr "" + +#: ../../source/contributing/content-contributor.rst:58 +#: 253021b9205c4727b634287929a4d47d +msgid "" +"If you'd like to improve documentation in the Jupyter community, check " +"out the :ref:`documentation-guide`." +msgstr "" + +#: ../../source/contributing/content-contributor.rst:61 +#: 059f1789bc3c4b0f8affc8723cc351d5 +msgid "Improving code" +msgstr "" + +#: ../../source/contributing/content-contributor.rst:63 +#: e6ffcd01e785483b8e74cd35916fe7cd +msgid "" +"There are many different codebases that make up the tools in the Jupyter " +"ecosystem. These are split across many repositories in several GitHub " +"organizations. They cover many different parts of interactive computing, " +"such as **user interfaces**, **kernels**, **shared infrastructure**, " +"**interactive widgets**, or **structured documents**." +msgstr "" + +#: ../../source/contributing/content-contributor.rst:68 +#: 040ce73d2d1e46bfbbe1c2ef16ed6893 +msgid "" +"We recommend checking out the :ref:`developer-guide` for more information" +" about how you can find the right project to contribute to, and where to " +"go next." +msgstr "" + +#: ../../source/contributing/content-contributor.rst:72 +#: 3d23b3320445470ba6f3429aaf1adaeb +msgid "Participating in the community" +msgstr "" + +#: ../../source/contributing/content-contributor.rst:74 +#: bed5fbe3f4ee4ff7a77a9a4e178acdae +msgid "" +"The most important part of Jupyter is its community - this is a large and" +" diverse group of people spread across the globe. One of the best ways to" +" contribute to Jupyter is to simply be a positive and helpful member of " +"this community. Whether it **participating in online conversations**, " +"**offering to help others**, **coming to community meetings**, or " +"**teaching others about Jupyter**, there are many ways to improve the " +"Jupyter community. For more information about this, we recommend starting" +" with the :ref:`community-guide`." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:3 +#: 304ab885d4f44411839e0449ce70df93 +msgid "How can I help?" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:8 +#: c556ab27189a49afb226bf41b20c4317 +msgid "" +"Contributing to open source can be a nerve-wrecking process, but don't " +"worry everyone on the Jupyter team is dedicated to making sure that your " +"open source experience is as fun as possible. At any time during the " +"process described below, you can reach out to the Jupyter team on Gitter " +"or the mailing list for assistance. If you are nervous about asking " +"questions in public, you can also reach out to one of the Jupyter " +"developers in private. You can use the public Gitter to find someone who " +"has the best knowledge about the code you are working with and interact " +"with the in a personal chat." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:17 +#: 4b17047e40534a7fb616858d5c55359b +msgid "" +"As you begin your open source journey, remember that it's OK if you don't" +" understand something, it's OK to make mistakes, and it's OK to only " +"contribute a small amount of the code necessary to fix the issue you are " +"tackling. Any and all help is welcome and any and all people are " +"encouraged to contribute." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:24 +#: a0d19f6b78c24827a32d37a436a653fb +msgid "Submitting Pull Requests" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:26 +#: 1d295b603e604b938f2f2eefe21e6ec0 +msgid "" +"Individuals are welcome, and encouraged, to submit pull requests and " +"contribute to the Jupyter source. If you are a first-time contributor " +"looking to get involved with Jupyter, you can use the following query in " +"a GitHub search to find beginner-friendly issues to tackle across the " +"Jupyter codebase. This query is particularly useful because the Jupyter " +"codebase is scattered across several repositories within the jupyter " +"organization, as opposed to a single repository. You can click the link " +"below to find sprint-friendly issues." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:34 +#: 0844b56ac4324e2690e0585a27df745d +msgid "" +"`is:issue is:open is:sprint-friendly user:jupyter " +"`_" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:37 +#: f5220427ba7944ed9fea76cb545b3aac +msgid "" +"Once you've found an issue that you are eager to solve, you can use the " +"guide below to get started. If you experience any problems while working " +"on the issue, leave a comment on the issue page in GitHub and someone on " +"the core team will be able to lend you assistance." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:42 +#: 21ea586c4346444c9227e7c11982ee3e +msgid "" +"Please keep in mind that what follows are guidelines. If you work through" +" the steps and have questions or run into time constraints, please submit" +" what you already have worked on as a pull request and ask questions on " +"it. Your effort, including partial or in-progress work, is appreciated." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:47 +#: 187dd0e76b5b4f2793727a2a6fdbe849 +msgid "" +"Fork the repository associated with the issue you are addressing and " +"clone it to a local directory on your machine." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:50 +#: bd83f9d413b84c10ac147a0c76e8a35e +msgid "" +"``cd`` into the directory and create a new branch using ``git checkout -b" +" insert-branch-name-here``. Pick a branch name that gives some insight " +"into what the issue you are fixing is. For example, if you are updating " +"the text that is logged out by the program when a certain error happens " +"you might name your branch `update-error-text`." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:56 +#: 9cb9a6352dd1400592ba68f435a7e581 +msgid "" +"Refer to the repository's README and documentation for details on " +"configuring your system for development." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:59 +#: 146e44c1f03d4d0eb3f6004c148c830f +msgid "" +"Identify the module or class where the code change you will make will " +"reside and leave a comment in the file describing what issue you are " +"trying to address." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:63 +#: 3af626c8ae004b61adc7f3531cc5493b +msgid "" +"Open a pull request to the repository with ``[WIP]`` appended to the " +"front so that the core team is aware that you are actively pursuing the " +"issue. When creating a pull request, make sure that the title clearly and" +" concisely described what your code does. For example, we might use the " +"title \"Updated error message on ExampleException\". In the body of the " +"pull request, make sure that you include the phrase \"Closes #issue-" +"number-here\", where the issue number is the issue number of the issue " +"that you are addressing in this PR." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:72 +#: 7624a4b5b1ee463aa4c1180591d7f595 +msgid "" +"Feel free to open a PR as early as possible. Getting early feedback on " +"your approach will save you time and prevent the need for an extensive " +"refactor later." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:76 +#: 5c38a6cdf3de41529860712963b52977 +msgid "" +"Run the test suite locally in order to ensure that everything is properly" +" configured on your system. Refer to the repository's README for " +"information on how to run the test suite. This will typically require " +"that you run the ``nosetests`` command on the commandline. Alternatively," +" you may submit a pull request. Our Continuous Integration system will " +"test your code and report test results." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:83 +#: 3901a11b764c4676827234595c771db5 +msgid "" +"Find the test file associated with the module that you will be changing. " +"In the test file, add some tests that outline what you expect the " +"behavior of the change should be. If we continue with our example of " +"updating the text that is logged on error, we might write test cases that" +" check to see if the exception raised when you induce the error contains " +"the appropriate string. When writing test cases, make sure that you test " +"for the following things." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:91 +#: b70076254ce644f2a9e3691059cac4f6 +msgid "What is the simplest test case I can write for this issue?" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:92 +#: c6a108daf91b46e8a3f3176011bcb5c2 +msgid "What will happen if your code is given messy inputs?" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:93 +#: e7c71a176ae240ca9ff9ab23d1519e9a +msgid "What will happen if your code is given no inputs?" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:94 +#: 6509e8e4e16c49c2b741c3ffe6c727b8 +msgid "What will happen if your code is given too few inputs?" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:95 +#: 5de551c92eca4ac3aefee4ddd640bfde +msgid "What will happen if your code is given too many inputs?" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:97 +#: cbb78fcc84104c04a6b41ce39a9d5d2c +msgid "" +"If you need assistance writing test cases, you can place a comment on the" +" pull request that was opened earlier and one of the core team members " +"will be able to help you." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:101 +#: 2b2b02f7147d4224a5c738f0df2d8238 +msgid "" +"Go back to the file that you are updating and begin adding the code for " +"your pull request." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:104 +#: e980e66a860d4d68a5cf7442143baa9c +msgid "" +"Run the test suite again to see if your changes have caused any of the " +"test cases to pass. If any of the test cases have failed, go back to your" +" code and make the updates necessary to have them pass." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:108 +#: 80219b2a8820441ebdf0c639242b8474 +msgid "" +"Once all of your test cases have passed, commit both the test cases and " +"the updated module and push the updates to the branch on your forked " +"repository." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:111 +#: 2c11a89867f94dabb3c3288afe835712 +msgid "" +"Once you are ready for your pull request to be reviewed, remove the [WIP]" +" tag from the front of issue, a project reviewer will review your code " +"for quality. You can expect the reviewer to check for the documentation " +"provided in the changes you made, how thorough the test cases you " +"provided are, and how efficient your code is. Your reviewer will provide " +"feedback on your code and you will have the chance to edit your code and " +"apply fixes." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:118 +#: 5b742c77773e4490bb9e990d281a9ff3 +msgid "" +"Once your PR is ready to become a part of the code base, it will be " +"merged by a member of the core team." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:122 +#: aebf26e740a646df8b76fca476de6aea +msgid "Contribution Workflow" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:128 +#: bc810b0e18f348589cf5075e3dd63775 +msgid "Core Developer Workflow" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:130 +#: 0e5526f2088e4c85b1357485d61b03bb +msgid "" +"To help you understand our review process by core developers after you " +"submit a pull request, here's a guide that outlines the general process " +"(specifics may vary a bit across our repositories). Here is an example " +"for Jupyter notebook 4.x:" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:137 +#: 10c45e7ff4a3467a9d0bd6cec08c95c0 +msgid "" +"In general, Pull Requests are against ``master`` unless they only affect " +"a backport branch. If a PR affects master and should be backported, the " +"general flow is:" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:141 +#: 9ee999496ce14fc4ac5a28b46f871839 +msgid "mark the PR with milestone for the next backport release (4.3)" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:142 +#: 044fc9a14ee34c3493008a79d0a54f7a +msgid "merge into master" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:143 +#: 55bfe6ca5e294a0a8ad68364941fc5dd +msgid "backport to 4.x" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:144 +#: b9cab57c889b43ddaa282bbf3be7ad0d +msgid "push updated 4.x branch" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:146 +#: 10e5f4e9c6154693ac29121a27652987 +msgid "" +"Backports can be done in a variety of ways, but we have `a script " +"`_ " +"for automating the common process to:" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:150 +#: c6e5bcc4e796450c8b73f8fec558f608 +msgid "" +"download the patch ` e.g. `" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:151 +#: 4ad12f7e5f0d44d3bfbf5d34aac52ae8 +msgid "checkout the 4.x branch" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:152 +#: caef8e474c92484ba26d830b588d1b41 +msgid "apply the patch" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:153 +#: c7f960d689e2484f91825860906d3f75 +msgid "make a commit" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:155 +#: 5b61df074ca74353b3d15b35e76bf37d +msgid "which works for simple cases, at least." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:157 +#: 617f166feb3c4007a2e3cd937bfb4d4d +msgid "In this case, it would be:" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:159 +#: 197ba05f14c24c98a167bd401a00a8b2 +msgid "" +"python /path/to/ipython-repo/tools/backport_pr.py jupyter/notebook 4.x " +"1645" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:163 +#: 3ece006658e143ecba31e4a5f9986ec8 +msgid "Submitting a Bug" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:165 +#: 3800293c8b4940ceabda60603e08db80 +msgid "" +"While using the Notebook, you might experience a bug that manifests " +"itself in unexpected behavior. If so, we encourage you to open issues " +"on GitHub. To make the navigating issues easier for both developers and " +"users, we ask that you take the following steps before submitting an " +"issue." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:170 +#: b9ff45938ce94bc08532f3c70b7effd0 +msgid "" +"Search through StackOverflow and existing GitHub issues to ensure that " +"the issue has not already been reported by another user. If so, provide " +"your input on the existing issue if you think it would be valuable." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:174 +#: a3128a8468954aafb65fc4601a6c73ee +msgid "" +"Prepare a small, self-contained snippet of code that will allow others to" +" reproduce the issue that you are experiencing." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:177 +#: 4bbabecbd1a849668f649f73b749a322 +msgid "" +"Prepare information about the environment that you are executing the code" +" in, in order to aid in the debugging of the issue. You will need to " +"provide information about the Python version, Jupyter version, operating " +"system, and browser that you are using when submitting bugs. You can also" +" use ``pip list`` or ``conda list`` and ``grep`` in order to identify " +"the versions of the libraries that are relevant to the issue that you are" +" submitting." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:185 +#: 7778452a7a184ee095f20b82f401e27e +msgid "" +"Prepare a simple test that outlines the expected behavior of the code or " +"a description of the what the expected behavior should be." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:188 +#: 45dfa845fbe14a5f9c8e8e3253ba64d0 +msgid "" +"Prepare an explanation of why the current behavior is not desired and " +"what it should be." +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:192 +#: a0d21dce01fc4a61baf2446737852109 +msgid "Reporting a Vulnerability" +msgstr "" + +#: ../../source/contributing/dev-contributions/contrib_guide.rst:194 +#: 69c9e1cfcf744ced9348647503e470c3 +msgid "" +"If you believe you've found a security vulnerability in a Jupyter " +"project, please report it to `security@ipython.org " +"`_. If you prefer to encrypt your security " +"reports, you can use `this PGP public key `_." +msgstr "" + +#: ../../source/contributing/dev-contributions/index.rst:5 +#: cb2bd7024d2d41b29b28d2397edff251 +msgid "Developer Guide" +msgstr "" + +#: ../../source/contributing/dev-contributions/index.rst:7 +#: ../../source/contributing/docs-contributions/index.rst:7 +#: 739b45dec6ca44ff838a88caad114266 a711ea6d544c458599070f4ec317b4f6 +msgid "**Contents**" +msgstr "" + +#: ../../source/contributing/dev-contributions/index.rst:16 +#: e5118134caaf4d02b8b036b60a4624b3 +msgid "" +"Whether you are a new contributor or a seasoned developer, we're pleased " +"that you are working on Jupyter. We hope you find the Developer Guide is " +"useful. Please suggest changes or ask questions about the contents. " +"Thanks!" +msgstr "" + +#: ../../source/contributing/dev-contributions/index.rst:20 +#: 86f67544f89342708addd825b19083ed +msgid "" +"If you are interested in installing a specific project from source, each " +"project has documentation on ReadTheDocs. For example, IPython " +"documentation can be found on `ReadTheDocs " +"`_. Most of our packages can be installed from " +"the source directory like any other Python package, by running:" +msgstr "" + +#: ../../source/contributing/dev-contributions/index.rst:30 +#: 2a214a8b2a1f4027bbc22d24b8fdf05d +msgid "" +"The Jupyter notebook needs some extra pieces to build Javascript " +"components; the information about that is in the `notebook contributor " +"documentation `_." +msgstr "" + +#: ../../source/contributing/dev-contributions/jupyter_enhancement_proposals.rst:2 +#: 45c861930123442e8df169de8e1c5929 +msgid "Jupyter Enhancement Proposals" +msgstr "" + +#: ../../source/contributing/dev-contributions/jupyter_enhancement_proposals.rst:5 +#: 3e2cf0df503f44dea0cdb2858d6ffa6e +msgid "Submitting an Enhancement Proposal" +msgstr "" + +#: ../../source/contributing/dev-contributions/jupyter_enhancement_proposals.rst:6 +#: 67b1eac7cf454b35ac2fd8a00f82e1c5 +msgid "" +"While using the Notebook, you might discover opportunities for growth and" +" ideas for useful new features. If so, feel free to submit an enhancement" +" proposal. The process for submitting enhancements is as follows:" +msgstr "" + +#: ../../source/contributing/dev-contributions/jupyter_enhancement_proposals.rst:10 +#: abd85316fcf44f12b1e536da22544a8c +msgid "" +"Identify the scope of the enhancement. Is it a change that affects only " +"on part of the codebase? Is the enhancement, to the best of your " +"knowledge, fairly trivial to implement? If the scope of the enhancement " +"is small, it should be be submitted as an issue in the project's " +"repository. If the scope of your enhancement is large, it should be " +"submitted to the official `Jupyter Enhancement Proposals repository " +"`_." +msgstr "" + +#: ../../source/contributing/dev-contributions/jupyter_enhancement_proposals.rst:17 +#: f2c2929abc8e45abb270a86185edb174 +msgid "" +"Prepare a brief write-up of the problem that your enhancement will " +"address." +msgstr "" + +#: ../../source/contributing/dev-contributions/jupyter_enhancement_proposals.rst:19 +#: 3249ea435b1e4e01875a52f0de15808d +msgid "Prepare a brief write-up of the proposed enhancement itself." +msgstr "" + +#: ../../source/contributing/dev-contributions/jupyter_enhancement_proposals.rst:21 +#: 656f801a8b8c46a0b4f72597cf2aa7c4 +msgid "" +"If the scope of your enhancement (as defined in step 1) is large, then " +"prepare a detailed write-up of how your enhancement can be potentially " +"implemented." +msgstr "" + +#: ../../source/contributing/dev-contributions/jupyter_enhancement_proposals.rst:24 +#: c4df9ccfebdb4cc58da01d25a436a4e1 +msgid "" +"Identify a brief list of the pros and cons associated with implementing " +"the enhancement that you propose." +msgstr "" + +#: ../../source/contributing/dev-contributions/jupyter_enhancement_proposals.rst:27 +#: dcd5ed43b2664ee1ba51adc3642ea93c +msgid "" +"Identify the individuals who might be interested in implementing the " +"enhancement." +msgstr "" + +#: ../../source/contributing/dev-contributions/jupyter_enhancement_proposals.rst:29 +#: b06b6c0f06ea42e0a5db3f9bdefc6776 +msgid "" +"Depending on the scope of your enhancement, submit it either as an issue " +"to the appropriate repository or as a Jupyter Enhancement Proposal." +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:5 +#: fb6a5aa8e03a45a3b715aec5d6750e5e +msgid "Basic template for releasing a Jupyter project" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:7 +#: b548743fb3054cde9d8ef02b74ac223b +msgid "" +"Jupyter consists of a bunch of small projects, and a few larger ones. " +"This lays out the basic process of releasing a smaller project, which " +"should also apply to larger projects, though they may have some added " +"steps." +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:14 +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:14 +#: 1789ea5c5d16469890cf2bd5b91bf5b7 e7ae4caea1d74057995ee81c48979b64 +msgid "Milestones" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:16 +#: 5e12dade53ea4a2aa6b0e083847983ed +msgid "" +"Most Jupyter projects use a GitHub milestone system for marking issues " +"and pull requests in releases. Each release should have a milestone " +"associated with it. The first step in preparing for a release is to make " +"sure that every issue and pull request has the right milestone." +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:20 +#: 36e1887c1d84456e9cc556c6dd5ec585 +msgid "" +"Go through any **open** Issues and Pull Requests marked with the current " +"milestone. If there are any, they need to be resolved or bumped to the " +"next milestone. It's fine to bump issues - they are typically marked with" +" the earliest feasible milestone, but many such optimistically marked " +"tasks aren't complete when it's time to release. There's always next " +"time!" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:25 +#: 8f8956de93f44c6d8a355eab30ea6b02 +msgid "" +"Check **closed** Issues and Pull Requests, using the milestone filter " +"\"Issues with no milestone\". There should never be any closed issues or " +"pull requests without a milestone. If you find any, go through and mark " +"them with the current milestone or \"no action\" as appropriate." +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:31 +#: 1363770e32d5422facbf815e86d924e8 +msgid "" +"A release may be ready to go when it has zero open issues or pull " +"requests." +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:35 +#: ed097c4e02c64c8aa1900b1cbb4c2fb5 +msgid "Release notes" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:37 +#: 5abf8e1561f14d11a03b9d2171436f9f +msgid "" +"Once all of the issues and pull requests are dealt with, it's time to " +"make release notes. The smaller projects generally have a " +":file:`changelog.rst` in the docs directory, where you can add a section " +"for the new release. Look through the pull requests merged for the " +"current milestone (this is why we use milestones), and write a short " +"summary of the highlights of the changes in this release. There should " +"generally be a link to the milestone itself for more details." +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:45 +#: a3a3a5f212254a1c8e3e5ef34eb29374 +msgid "" +"Make a pull requests with these notes. It's a good idea to cc @willingc " +"for review of this PR. Make sure to mark this PR with your release's " +"milestone!" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:51 +#: 0540aea494784ab3b048a70c0b31a345 +msgid "Making the release" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:53 +#: 2941c1a01aaf46ab9110f906677ddf00 +msgid "" +"Now that your changelog is merged, we can actually build and publish the " +"release. We'll assume that ``V`` has been declared as a shell variable " +"containing the release version::" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:58 +#: 9d8a2a184b524256b0a69dc2a4649c3c +msgid "" +"Start by making sure you have a clean checkout of master, with no extra " +"files::" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:63 +#: 1ffcdd20c39347ff8a5c80f3f5e587f9 +msgid "" +"First, update the version of the package, often in the file " +":file:`/_version.py` or similar." +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:65 +#: 3d10ef5ff51844488fcbdb10845dd4aa +msgid "Commit that change::" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:71 +#: 701291bda6b14ae4b9c50a95c25cdaea +msgid "" +"At this point, I like to run the tests just to be sure that setting the " +"version didn't confuse anything." +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:74 +#: 6cfd7bf5306043ada4f14320534d5315 +msgid "Build the distributions::" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:79 +#: a33e3cbce2f240f99a5cfc819203cbff +msgid "Tag the commit::" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:83 +#: a753ead605ae47a2a6c57a43b4373d63 +msgid "" +"And finally, publish everything, to github and PyPI using `twine " +"`_::" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:89 +#: 6abb3a55faf9470abf557d02cb79f6f7 +msgid "" +"We have a release! You can now bump the version to the next '.dev' " +"version, by editing :file:`/_version.py` (or similar) again, and " +"commit::" +msgstr "" + +#: ../../source/contributing/dev-contributions/releasing.rst:97 +#: 639e020047414b878ad8389f506061d2 +msgid "" +"The pushes assume that `origin` points to the main jupyter/ipython repo. " +"Depending how you use git, this could be `upstream` or something else." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-future-index.rst:2 +#: fea98a6b70964c19963e38adf8caff2c +msgid "Setting up a project's documentation infrastructure" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-future-index.rst:4 +#: 97d789258af44dc2b5fd01e6d8de6947 +msgid "Contents:" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-future-index.rst:14 +#: 8a44a9d68f814886bbfa53b1834efa95 +msgid "" +"This section helps a contributor set up the documentation infrastructure " +"for a new project or an existing project without Sphinx documentation." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:1 +#: 6b4b783dd68b44be9ae9b97a99fecc70 +msgid "Building automatically on ReadTheDocs" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:3 +#: 18ef0ea1ca1c4937b848a0078c927579 +msgid "" +"This explains how to automatically rebuild documentation on ReadtheDocs " +"every time a pull request is merged into its corresponding GitHub repo." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:6 +#: b6bbf76d2c4844c7815c7c65a67ac4c4 +msgid "Using the ReadTheDocs service" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:8 +#: 628092cfca7e430ebab8d94d37b08970 +msgid "" +"Webhooks and services can be enabled in GitHub repo settings to allow " +"third party services such as ReadTheDocs. The ReadTheDocs service " +"rebuilds the project documentation whenever a pull request is merged into" +" the GitHub repo." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:12 +#: b2809bf2243946cbbfda7f09822c79ac +msgid "Navigate to Settings" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:14 +#: 52ea0bb2fc9e4d01b0c0bc4a12c9df8e +msgid "" +"Each GitHub repo has a Settings tab at the far right of the repo menubar." +" Navigate to Settings and then the **Webhooks & services** submenu tab." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:16 +#: ccc2632460864b4abf18b4368747e4a0 +msgid "" +"![Settings and Webhooks & services submenu](static/gh-webhooks-" +"services.png \"Screenshot of GitHub repo settings\")" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:18 +#: 0cf14b4f68de498b8d23ed631a6d74e6 +msgid "Add the ReadTheDocs service" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:20 +#: 256deb59d5c0474a8c9f980aa993c174 +msgid "" +"Select **Add service** and enter *ReadTheDocs* in the **Available " +"Services** input box." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:22 +#: c51a8843686c41e49d58061a04cdc998 +msgid "" +"The Services/Add ReadTheDocs window will open. Press the green **Add " +"service** button to activate the ReadTheDocs service." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:24 +#: 2c97122128fc4204b22ee4bea97eb259 +msgid "" +"![Add ReadTheDocs service](static/gh-add-rtd.png \"Screenshot of adding " +"ReadTheDocs service\")" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:26 +#: 539ec58c517643e7bcd3120cf7749560 +msgid "Success" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:28 +#: f70d31a5dfcc405dbc059363e3a9bbd1 +msgid "" +"The ReadTheDocs service is added successfully. The service will take " +"effect on the next merged pull request to the project repo." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:30 +#: 802fb6a5b3484e11a49316cbd0bbe45d +msgid "" +"![Service successfully added](static/gh-rtd-hook-success.png \"Screenshot" +" of service successfully added\")" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-build.md:33 +#: 1f77cb953a664e7c89900e2350833072 +msgid "*Created: 01-07-2016*" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:1 +#: ff6fa5fb8ac74448a6eddebab72a90b6 +msgid "Setting up a README" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:3 +#: f5a25bc48b0140a1b05d2f9ad6565b52 +msgid "" +"Providing users and developers consistency across repos is a valuable " +"time saver and improves user productivity." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:6 +#: e85f978a62f640488670fa69cfa75039 +msgid "" +"On a larger scope, having the Jupyter name appear prominently in a repo's" +" `README.md` file improves the project's name awareness." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:9 +#: 9bc3c6611dbe47a78367416e16e36305 +msgid "Recommended elements in Jupyter project repos" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:11 +#: e1e2b8a8c7b9413da8ecd4cd3a6277ab +msgid "Link in repo description" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:12 +#: 337fb9055ed740bc80c4a785b450ea7d +msgid "Please include a link to the documentation in the repo's description." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:14 +#: d8a2b5e8fbae411b8728dc8a8e884ca8 +msgid "" +"![Repo description and documentation link](static/repo-description.png " +"\"Screenshot of documentation link in GitHub repo description\")" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:16 +#: 101573b73b464f6bb3d8fca855a0520b +msgid "Badges in README" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:17 +#: 8070f4a4ba38473a9f20ae20c1d3b166 +msgid "" +"One common way that individuals find documentation is to look for and " +"click on the doc badge that commonly is found right after the title. " +"Another benefit is an easy visual indication if the docs are not " +"rendering properly." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:21 +#: 7d29b0975a6340bf88cd942f4badd3f4 +msgid "" +"![Badges in README.md](static/repo-badges.png \"Screenshot of badges " +"displayed under the repo title in the README file\")" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:23 +#: 591fa4ba1caf42a08412cd1c93e26c54 +msgid "Resources section in README" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:25 +#: 33162f5977ac49b398caccd90b405565 +msgid "" +"A *Resources* section at the end of the `README.md` gives useful links " +"and information to users about the individual project and the larger " +"Project Jupyter organization. Make sure to include any links to the " +"individual project's demo notebooks, if available." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:30 +#: bb8fa53a16bc4e1089a84a37b5a5308b +msgid "The *Resources* section includes:" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:32 +#: d8bef17bd33e4727be9555325169ddf4 +msgid "" +"![Resources section in `README.md`](static/repo-resources.png " +"\"Screenshot of resource list at end of README file\")" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:35 +#: b4885f52b09244d1b23c754350fbed7c +msgid "Checklist adding docs to a new or existing GitHub Repo" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:37 +#: 1b36055fa35842a7aa12772c34804540 +msgid "" +"[ ] Add a link to documentation in repo description (requires GitHub repo" +" privileges)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:38 +#: 1f1f53ee19ed4087a31f56064ec86054 +msgid "[ ] Add badges to README (Edit `README.md` and submit pull request)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:39 +#: 163e17f2e36440cc8cdb56011d88df51 +msgid "" +"[ ] Add resources section to README (Edit `README.md` and submit pull " +"request)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-repos.md:42 +#: d23c7fe0d15c4f968530903efc0e3748 +msgid "*Dated: 1-4-2016* *Revised: 1-7-2016*" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:1 +#: 179271c7e8ad4f5d98fb50521b1a324e +msgid "Supporting translations of documentation" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:3 +#: f8ad7b4cd1f948f29c08b19acca296ec +msgid "" +"We support and encourage the translation of Jupyter documentation to " +"other languages as one way of making our community more inclusive and " +"diverse. We are working toward having a consistent model for translation " +"of [Sphinx](https://www.sphinx-doc.org/) documentation across Jupyter " +"projects based on prior work in the [Python](https://python.org) and " +"[Django](https://www.djangoproject.com/) communities. This project " +"(https://jupyter.readthedocs.io) and the [Jupyter Docker Stacks " +"project](https://jupyter-docker-stacks.readthedocs.io/) are early " +"adopters, meant to prove out the workflows described on this page." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:11 +#: ../../source/contributing/ipython-dev-guide/testing.rst:10 +#: 3b81f989eb7c47668cb62993155cd497 46ac0ec44fff4ae98117a1f730b4628e +msgid "Overview" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:13 +#: aed9f4dc2ab44b95a42dca203dbf203e +msgid "" +"After initial project setup, changes to Sphinx documentation and its " +"translations follow a continuous integration (CI) and continuous " +"deployment (CD), much like project source code." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:16 +#: 5b29d2efd05545edb306615560eb8abd +msgid "Who is involved in translating documentation" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:18 +#: ab58ebc2f7454db98e427a252d80e2a6 +msgid "" +"Anyone is welcome to participate in writing and translating Jupyter " +"documentation by participating in the workflow described below. This " +"workflow has a handful of actors and components:" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:21 +#: 28e0e58540f147deb5f637ef8f04c2a9 +msgid "A person who makes changes to the English project documentation" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:22 +#: 0ca9f85fe4da4734af21b9efa279e2e6 +msgid "" +"A person who translates snippets of text in the English documentations " +"into another language (locale)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:24 +#: 939805472b6b41e39fb1b25fd28ae77f +msgid "" +"[Portable object files (`.po`)](https://en.wikipedia.org/wiki/Gettext) " +"for the source documentation language (e.g., U.S. English, `en-US`) and " +"for other locales (e.g., Brazilian Portuguese, `pt-BR`; Moroccan Arabic, " +"`ar-MA`)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:27 +#: 1421b1c9e9c940f1a569cc39e8fd7146 +msgid "" +"A continuous integration system like TravisCI, CircleCI, or GitHub " +"Actions, responsible for" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:28 +#: 1e19fd0861d447d8893fc132f8720bc7 +msgid "" +"[ReadTheDocs](https:/readthedocs.org), our preferred service for building" +" and hosting documentation" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:30 +#: 1622611494854c9d9ce02783038943a0 +msgid "" +"[Transifex](https://transifex.com), a localization platform with free " +"plans for open source projects, a friendly web interface, and support for" +" `.po` files" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:33 +#: a1ed9ab794f94c4d802c12adabfdfeec +msgid "The translation process" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:35 +#: a85e4481a94e4f94bd3692cdda100cee +msgid "" +"![Translation CI/CD](static/translation-ci-cd.png \"Diagram of the " +"translation continuous integration and deployment flow\")" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:38 +#: d49871ad852841cf8db58d74cbe77361 +msgid "" +"A user creates or edits reStructuredText (`.rst`) or Markdown (`.md`) " +"documents written in U.S. English." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:40 +#: b4f369e43b4d422c91f680b8184dfce7 +msgid "The user submits a pull request on GitHub." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:41 +#: ../../source/contributing/docs-contributions/doc-new-translation.md:79 +#: 1918ee71d65b4870b1577d08ab77b52f aea0d1ceaa7f403ab5e41cb6b96d9be6 +msgid "A project maintainer reviews and merges the pull request." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:42 +#: 4cc5da05b80a4c0b90ec08027d2d3636 +msgid "" +"ReadTheDocs runs Sphinx to convert U.S. English source documents into " +"HTML (e.g., " +"https://jupyter.readthedocs.io/en/latest/architecture/how_jupyter_ipython_work.html)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:44 +#: 38406183a1d845c0bea1272c8ce476d9 +msgid "" +"Meanwhile, the CI service runs Sphinx commands to extract translatable " +"_messages_ from U.S. English documents into `en-US` portable object " +"(`.po`) files. For example:" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:57 +#: 7bc80c6f4cb041b1b8ab5f329264d911 +msgid "" +"The CI service commits the English `.po` files to the project on GitHub. " +"(e.g., " +"https://github.com/jupyter/jupyter/commit/1330bc409842d8b8a7bbb3a1c63259c34a543be0)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:59 +#: e72a9992e4b743e08f2145778aa0f353 +msgid "" +"Transifex makes the messages in the English `.po` files available for " +"translation in all configured languages." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:61 +#: 6e9170d95bf648d291b7b159f6ecdcaa +msgid "" +"Over time, translation teams use the Transifex web application to create," +" review, and update translations for those languages (e.g., " +"https://docs.transifex.com/translation/translating-with-the-web-editor)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:64 +#: 66c4f3cee4b0475d8628c310c9134ece +msgid "" +"Transifex submits a pull request to the GitHub project containing a " +"localized `.po` file when all of the English messages have been " +"translated, and optionally reviewed, for a given language (e.g., " +"https://github.com/jupyter/jupyter/pull/485). For example:" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:80 +#: 8a7737f0d23549c49b3a62074a9c6164 +msgid "" +"ReadTheDocs once again runs Sphinx to convert U.S. English source " +"documents into HTML." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:81 +#: 8f66dc9f43ba4f4abccf8b45d94a8d80 +msgid "" +"ReadTheDocs also runs Sphinx to load localized `.po` files, substitute " +"translations into the original English text, and convert those translated" +" documents into HTML (e.g., " +"https://jupyter.readthedocs.io/pt_BR/latest/architecture/how_jupyter_ipython_work.html)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:85 +#: 3ef0da657a2949f2b2dc7ea7a0532740 +msgid "" +"Note: We recognize this flow assumes documentation starts life written in" +" U.S. English. We should look into removing this assumption in the future" +" if it becomes a significant barrier to new contributions." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:89 +#: f3655db9f43b45baa8d463937993fcfd +msgid "Community translator workflows" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:91 +#: ee088359a91e41bc8b120e2dda7932cd +msgid "" +"We are delighted when members of the Jupyter community want to help " +"translate documentation. We use [Transifex](https://transifex.com) to on-" +"board translators in a friendly web interface without requiring knowledge" +" of git, GitHub, Sphinx, or other software developer tools." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:95 +#: e85c591c48ab44c994bac16e92edd3c6 +msgid "Creating translations" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:97 +#: 430fdc05f67e40de8a7a8b95a259236f +msgid "" +"[Getting Started as a Translator](https://docs.transifex.com/getting-" +"started-1/translators) is an excellent on-boarding guide for new " +"Transifex users. Follow the instructions to create an account. When " +"prompted to join a team, look for _jupyter-meta-documentation_ to start " +"contributing translations to this documentation site. Alternatively, " +"visit https://www.transifex.com/project-jupyter/jupyter-meta-" +"documentation/ after creating your account and request to join the " +"project. A project maintainer or language team coordinator will review " +"and approve your request." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:105 +#: 7c641ec9efdc4cbd8693f51aabb12cd6 +msgid "Reviewing translations" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:107 +#: 3a4520bfb4154c9d98a9da26debb2006 +msgid "" +"Transifex supports [Reviewing " +"Translations](https://docs.transifex.com/translation/reviewing-strings), " +"peer review by members of a language team, to ensure translation quality." +" Project maintainers can choose whether Transifex should immediately send" +" a pull request when translations of all text in a document are available" +" or delay submitting a pull request until after all of those translations" +" are also reviewed (the [current setting for this " +"project](https://github.com/jupyter/jupyter/issues/430#issuecomment-552138547))." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:115 +#: 0eff3cdff37a4064a8b51d31bc4aa8ab +msgid "Coordinating translation teams" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:117 +#: 453c06a9eed74c7ea56b51c29a3729d9 +msgid "" +"Project maintainers can also grant Transfex team members the role of " +"[language coordinator](https://docs.transifex.com/teams/understanding-" +"user-roles#organization-administrator). Language coordinators have " +"permission to invite users to language teams, approve or deny join " +"requests, assign language team roles, and perform other administrative " +"actions for a particular project language. Empowering trusted members of " +"the community as coordinators can help grow translation teams without " +"software developer involvement." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:124 +#: d4da4522f1404dcebc82fb0fdb446fab +msgid "Administrator workflows" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:126 +#: 13f13c07792145228b2688628e28cf59 +msgid "" +"The translation CI/CD workflow described above requires configuration in " +"GitHub and in Transifex to function. Project maintainers can follow the " +"instructions below to enable translations for their Sphinx documentation." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:130 +#: f44038761e8e46b19f7973dc91d79867 +msgid "Creating a Transifex organization" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:132 +#: 6719fdfe424d4af4bec7ee3f0b4e97a9 +msgid "" +"Transifex organizes translation projects under organizations that mirror " +"organizations and repositories on GitHub. At present, only the " +"https://github.com/jupyter organization has a corresponding org on " +"Transifex (https://www.transifex.com/project-jupyter/public/) with the " +"following [organization administrators](https://docs.transifex.com/teams" +"/understanding-user-roles#organization-administrator):" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:138 +#: ab8fd7bf3d954ac88402e45b010d1529 +msgid "@choldgraf" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:139 +#: f3bb2ad6fbf24bb8a233cf53e8b24f2c +msgid "@parente" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:140 +#: aa1680938be34b1ab89113068426436c +msgid "@willingc" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:142 +#: 6be4bd47b48a41feb1b2d0819e413e29 +msgid "" +"GitHub users with permissions to install applications in a GitHub org can" +" follow these instructions to create a new Transifex-GitHub organization " +"link (e.g., for https://github.com/jupyterhub, " +"https://github.com/jupyterlab)." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:146 +#: 6215439cd23d4af381cbc1fec6dea217 +msgid "Create a new user account at https://transifex.com." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:147 +#: bed3dfbf112c4eddbc977722bbfa775c +msgid "Complete the sign-up wizard." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:148 +#: 061a94189cba4cc5baa3bfb065a44577 +msgid "Create and name a new organization." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:149 +#: ../../source/contributing/docs-contributions/doc-new-translation.md:174 +#: 20ee8ebd6ba949508ce369c97f655eb0 a048e26f20a549e48d8921c6a3830296 +msgid "" +"Click the organization drop down in the top right of the Transifex " +"dashboard page and select _Organization Settings_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:151 +#: 6e6c1708f06d44328aae9500c4f06391 +msgid "Click _Details_ in the left sidebar." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:152 +#: 55ac5a129900454a8bd39dbf813ab666 +msgid "" +"Click _inviting administrators_ in the _Management_ section to add " +"additional admins to the Transifex org." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:154 +#: 728b2a92b7c44a81b9dd8802c2212edc +msgid "Click _Manage integrations_ in the left sidebar." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:155 +#: af52c0d6c0d5475fb51d2f82e7dfb44b +msgid "Click _Install the Transifex app_ in the GitHub section." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:156 +#: 783675ae774547e7b672336f0030e938 +msgid "" +"Select the GitHub organization to associate with the new Transifex " +"organization." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:157 +#: c2ccf5ea41de4d69b672b7ab66dc7d2f +msgid "Select the repositories that Transifex will have permission to access." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:158 +#: 138218fbc77646c7a88a15de77f6bd35 +msgid "" +"Return to the tab where you clicked _Install the Transifex app_ and click" +" _authorize Transifex_ in the GitHub section." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:160 +#: d48d4b20cba84ed98f87b7cfe005f3e6 +msgid "Choose the GitHub organization you just configured in the popup dialog." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:162 +#: cfba854de46f4dbc9dc984268f01bb71 +msgid "" +"Note that you can revise the GitHub-Transifex integration at any time by " +"visiting https://github.com/settings/installations." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:165 +#: 62f649f77633428b8cafcd98d9bc077b +msgid "Creating a Transifex project" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:167 +#: 5d0a49ff892342d99a277f2bba1ea2d0 +msgid "" +"Transifex [organization administrators](https://docs.transifex.com/teams" +"/understanding-user-roles#organization-administrator) can follow the " +"instructions below to configure new translation projects for GitHub " +"projects in the GitHub org corresponding to the one on Transifex." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:172 +#: ../../source/contributing/docs-contributions/doc-new-translation.md:196 +#: ../../source/contributing/docs-contributions/doc-new-translation.md:262 +#: 59399440440d434d815f3d70eb130e7c 8f70a185628a4550afe05500dec25467 +#: d7c92dcafedd41509e5bbef4afc0d20d +msgid "Visit https://www.transifex.com." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:173 +#: ../../source/contributing/docs-contributions/doc-new-translation.md:197 +#: 12afc6fc8cfa4fd3ae41529df57b603b 12bcae1f8d364cefb59c6cb566cda423 +msgid "Sign in with the appropriate admin user account for the organization." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:176 +#: 8ac4026db0634af6ac1ca030a95a08e2 +msgid "Click _Create new project_ in the lower left sidebar." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:177 +#: 8208b08ba1354734ac033d1b8b23ae8f +msgid "Name the translation project after the project on GitHub." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:178 +#: 0f302e9304744518b12253f4e3226671 +msgid "" +"Select _Public_ as the privacy type, indicate that the project is open " +"source, and provide the GitHub URL for the repository." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:180 +#: 14b642e501b14f129b3b7e6ba68812df +msgid "Select a file-based project." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:181 +#: c1124e271ee04f0cbb86e1bc7cf68765 +msgid "Create a new team for the project." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:182 +#: b9e3ab3a9dce40809ea58803b1b5530c +msgid "Select _English (en)_ as the source language." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:183 +#: 8072a84a41804fffa4097d8137dce894 +msgid "Select known target languages. (You can add these later as well.)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:184 +#: 35283be38a6e407392dade701d00a24f +msgid "Click _Create project_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:185 +#: ../../source/contributing/docs-contributions/doc-new-translation.md:263 +#: 4ea630b863fd48dc8d6a75e74baefe3e cc2469b077fb40e1b1d6b56b11acffaa +msgid "Click _Settings_ under the project name in the left sidebar." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:186 +#: c9c963fa13dc4ee58c2f085e9ae71230 +msgid "Click the _Maintainers_ tab." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:187 +#: bac3d78e6fea4831b317c91c1b864c34 +msgid "" +"Invite additional [project maintainers](https://docs.transifex.com/teams" +"/understanding-user-roles#project-maintainers), typically software " +"developers who will be responsible for maintaining the continuous " +"integration and bootstrapping language teams." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:192 +#: ec7ac8ce1a27459d9ce3c39db1c31145 +msgid "Configuring languages and teams" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:194 +#: 2ffb477fea0a41b6817b6647665b907a +msgid "" +"Transifex organization admins and project managers can add translation " +"languages to a project." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:198 +#: 3d0fbe4d4f044562b509eaa6991a503a +msgid "Click _Languages_ under the project name in the left sidebar." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:199 +#: 363969f3e5cf4ac08455199c36b160b6 +msgid "Click _Edit languages_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:200 +#: d0d62a5eb30c4f7ab8910729599ec2e3 +msgid "Add or remove target translation languages." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:201 +#: 8b21b95738964b04823e4f33931b99e1 +msgid "Click _Apply_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:203 +#: 6e1d53e93fa845659900ab751bcaa6c1 +msgid "" +"Organization admins, project maintainers, and [team " +"managers](https://docs.transifex.com/teams/understanding-user-roles#team-" +"managers) can add users to translation teams with the roles of language " +"coordinator, reviewer, or translator." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:207 +#: 60ab837b4b03484f89d9e71d5f3dc7a1 +msgid "Click _Teams_ in the top nav bar." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:208 +#: 7dfe61305e7a4ae3a279b0387699a241 +msgid "Click the _Invite Collaborators_ button in the top right." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:209 +#: 142b89777a43486eaa28e741d6c9fe60 +msgid "" +"Enter the username, email address, or full name of a person to add to the" +" project. Note that the autocomplete in this field does not always " +"display a popup for the user you wish to invite. Confirm you've entered " +"the correct value and move on." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:212 +#: 1c8004312c094cfebb1608ea74013b68 +msgid "" +"Select [the role](https://docs.transifex.com/teams/understanding-user-" +"roles) to assign to the user." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:214 +#: 546ccec00a68479687f49a1da9888747 +msgid "If the role applies to a specific team, select the team." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:215 +#: 6a9d55d18e844e4f8631125041e5701d +msgid "If the role applies to a specific language, select the language." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:216 +#: 515b77d2525d40cf94a00d1492b46c06 +msgid "Click _Invite more_ to enter additional users or _Send invitation_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:218 +#: 12b51c23f8e74a4aa90d63f75f2b41f2 +msgid "Configuring Transifex-GitHub integration" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:220 +#: 4133a4f906294e50b64bdec51ebea3f2 +msgid "" +"After configuring organization and project resources on Transifex, " +"project developers can:" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:222 +#: ed07e4f42ea642cead8706623c7f5d42 +msgid "" +"configure Sphinx to produce `.po` files for the source language and read " +"`.po` files containing translations" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:224 +#: 079158d74aa1494b8a0b9a17941faa21 +msgid "configure Transifex to watch for source language `.po` file changes" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:225 +#: 7000d4f9d7b743468fc4bfb10a875b9c +msgid "" +"configure the project CI service to update source language `.po` files " +"when contributors make changes to the source documentation" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:228 +#: 4ad6f05deb60443ca4f446da5110fda3 +msgid "" +"The instructions in this section assume a git repository already contains" +" Sphinx documentation in the following directory structure:" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:241 +#: e28043879122403b8dec79362b39efe7 +msgid "" +"Project developers can do the following to configure Sphinx to seed " +"source `.po` files and recognization translation `.po` files." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:244 +#: cd3146dc4ed648b7aa82ce588f45ef76 +msgid "" +"Add `sphinx-intl` to your Sphinx project `requirements.txt` or " +"`environment.yaml` if it does not already exist." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:246 +#: 123f6cb3c0c142db87ade925feb17bee +msgid "Run `sphinx-intl create-txconfig` in the `docs/` directory." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:247 +#: 96a05f04652c41508ab2d8ec793db7fd +msgid "Add the following to the Sphinx `source/conf.py` file." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:256 +#: 19cc9423e80743d2b32467e30c22f47f +msgid "" +"Run `make gettext` to extract all strings from the English source " +"documentation." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:257 +#: 55024a59110741a894233a6d55fd4ebb +msgid "Run `sphinx-intl update -l en` to generate the English source `.po` files." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:258 +#: 4dd12494841f4f32bbc76a0b3816055f +msgid "" +"Submit, review, and merge a pull request with the changes and generated " +"`.po` files." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:260 +#: 945fea75836744ce83383cc73a732a71 +msgid "" +"After merging the pull request, link to the Transifex project to the " +"GitHub repository." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:264 +#: fbd33c2c31744a24a3f46b2060b55939 +msgid "Click the _Integrations_ tab." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:265 +#: 9d9ab1e8950a42378a3154fe44865d26 +msgid "Click _Link Repository_ in the GitHub section." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:266 +#: 101c4235819c4abbb2d889988e5b0a36 +msgid "" +"Select the appropriate GitHub repository and integration branch. Then " +"click _Next_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:267 +#: 937aedb9eac946fab4b0314ff34e18e5 +msgid "" +"Copy and paste the following configuration into the dialog, adjusting the" +" commented values as appropriate, and then click _Next_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:283 +#: c6993d1e3bfe473aa964305a1c14b128 +msgid "" +"Select when Transifex will submit translations a back to the repository. " +"Then click _Save & Sync_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:285 +#: 2eeec3b154af4106aa047bc19a975fa3 +msgid "Click _Close_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:286 +#: 3a8e28e8a5e64842af891463a6a39734 +msgid "Watch the sync status progress." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:287 +#: 1981b3d769464d4e8fceb19b9b5aa350 +msgid "Click _Resources_ in the left sidebar." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:288 +#: 204e63b5ca87400ca447e9f46f1f813c +msgid "Click one of the `.po` files to see translation progress by language." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:289 +#: 2bfded1ec9114585a2f2d51eedde5bc0 +msgid "" +"Click one of the languages to see details about translation progress, " +"translate text, and review translations. See the [Translator workflows" +"](#translator-workflows) section above for details." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:292 +#: acd1a604251040309b442ea07ed6666b +msgid "" +"After confirming the initial English `.po` files have reached Transifex, " +"set up continuous integration to ensure source strings are kept up-to-" +"date in Transifex whenever the English documentation changes. The steps " +"to accomplish this end vary depending on the CI provider. The following " +"describes how what to do when using GitHub Actions." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:297 +#: a3dc6cb0376549cd9fccb71809e0b8cb +msgid "" +"Create a new GitHub actions workflow file `.github/workflows/gettext.yml`" +" in the project." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:298 +#: 78265fb56baf481da81be774d01bf4c2 +msgid "" +"Add the following content to the file. Note that `secrets.GITHUB_TOKEN` " +"is a built-in secret, not something you need to configure ahead of time." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:338 +#: 6bda1f481509461fbcb0d4c7b44fd785 +msgid "Submit, review, and merge a pull request containing the workflow YAML." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:340 +#: 275919297d9b404984e1a400c7c725dc +msgid "" +"Once you complete the steps in this section, any changes to the source " +"English documentation on the master branch are pulled into Transifex for " +"translation. Likewise, any translations completed on Transifex are " +"submitted as pull requests back to the project on GitHub." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:344 +#: b091151be190458e82a05f2b549c694f +msgid "Hosting translations on ReadTheDocs" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:346 +#: 5e30121435a94db49f8c1f5ee1a319d2 +msgid "" +"ReadTheDocs supports building HTML documentation sites from a single " +"GitHub project and its translations. Administrators of the source " +"language documentation project on ReadTheDocs can following these " +"instructions to enable builds for other languages." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:350 +#: 1ecbfc7cddfa45e8a56ec08c250bce5c +msgid "Visit https://readthedocs.org/dashboard/" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:351 +#: cae52b8517c840be87acb36246b51330 +msgid "" +"Note the name of existing ReadTheDocs project containing your source " +"language (e.g., `jupyter`)." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:352 +#: 13a64c8a417b4c36af889899b6a82866 +msgid "Click `Import a Project`." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:353 +#: 25560f4406a247b191328b71eb7f49c1 +msgid "Click `Import Manually`." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:354 +#: fe14fa6cf10f4b94854e3ac44c50d190 +msgid "" +"Enter the project name you noted above suffixed with a target language " +"locale (e.g., `jupyter-es`, `jupyter-pt-br`)." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:356 +#: 39eab265916d4faea999451cb6097c90 +msgid "Enter the GitHub URL of the project." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:357 +#: 6327ba17f465463097f62fd9b30e3d53 +msgid "Check _Edit advanced project options_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:358 +#: 1e7261e0079646d19f7f0805c549b08f +msgid "Click _Next_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:359 +#: c0377d8c02ae45759f66775eef482a6d +msgid "" +"Select the name of the target language from the _Language_ drop down " +"(e.g. `es` -> _Spanish_, `es-mx` -> _Mexican Spanish_, `pt-br` -> " +"_Brazillian Portuguese_)." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:361 +#: 4e7076a1ca5647829f8f006a8d836e32 +msgid "Click `Finish`." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:362 +#: 61893eae617b47dcb9f23b4a9d08443e +msgid "Return to the list of projects at https://readthedocs.org/dashboard/" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:363 +#: 332b0ff68088429bb61b568c5e7d4f20 +msgid "Click the project containing the source language." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:364 +#: 9acb0e625d5d4d308a12e212949059d0 +msgid "Click _Admin_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:365 +#: 35f076bf7bde408c8fe9d07587fb62bc +msgid "Click _Translations_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:366 +#: b8054334dea844d1bcfdcf87148175ca +msgid "" +"Choose the name of the translation project created in step 5 from the " +"_Project_ drop down." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:367 +#: c4eab1f361f34afd804daca14121667b +msgid "Click _Add_." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:368 +#: 172f7198362f4445b6ecb35d9f03b60f +msgid "Repeat these steps for all other languages the project supports." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:370 +#: 890349f4f34c428f8c42bff26d40b902 +msgid "" +"Now, any time you merge a pull request from Transifex containing `.po` " +"translation file updates, ReadTheDocs will build both the source " +"documentation site as well as sites for all supported languages. " +"ReadTheDocs will associate the sites with one another and make them " +"accessible via language links in a popup." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:375 +#: 55742d32c7d647a2a1d79a335e75c3c6 +msgid "" +"![ReadTheDocs popup](static/translation-rtd-popup.png \"Screenshot of the" +" ReadTheDocs popup that allows a user to view documentation in a " +"different language\")" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:378 +#: db980506d349459f9a50c6b3d29bac5f +msgid "Reference" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-new-translation.md:380 +#: 929547d58a304154bb4209dc2a497fbd +msgid "" +"https://github.com/parente/helloworld-transifex-rtd is a mini-project " +"configured to support the entire workflow described in this document." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:2 +#: 7674c668a64745bb9f2b0a689b1b9733 +msgid "Tools for documentation" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:8 +#: 4bf1880bbd634bacbff0040b9112f27b +msgid "Packages" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:9 +#: ec91db3759444beab4f8cf417620fd28 +msgid "" +"For user documentation, contributor guides, and communications content, " +"we use:" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:12 +#: 345e9ae0d64045e0a1e683ac67604225 +msgid "`Sphinx `_" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:14 +#: 57e62c568d3b43d5b28f8fc633590f2b +msgid "" +"For developer API documentation (especially for JupyterLab js repos), we " +"use:" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:16 +#: a4485bbe319b409d96a23e6e6dfacb95 +msgid "`swagger `_" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:19 +#: 75ca44fb8d81432c99c9196fa9700545 +msgid "Source file formats" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:20 +#: b0e65aea21e6402894f9f9ec61a22729 +msgid "" +"We use the following input source file formats when developing Sphinx " +"documentation:" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:23 +#: 8036a07505f942b3a813de8faeda5804 +msgid "reStructuredText (``.rst``)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:24 +#: 39956708b5b34c99b91dc50c9febd35c +msgid "Markdown (``.md``)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:25 +#: ba20899851aa434b8dc80280841b767c +msgid "Notebook (``.ipynb``)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:27 +#: 5d2871aa6cfc4973a0dcbb039e003180 +msgid "" +"A modern code editor should be used. Many are available including Atom, " +"SublimeText, gedit, vim, emacs. `Atom `_ is a good " +"choice for new contributors." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:32 +#: 0b8b6424ad5047b5bfb28ce2bd77e875 +msgid "Sphinx themes" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:33 +#: 5ca282cfa6b14836bdc5910a2a2abcc8 +msgid "Our projects use the following themes:" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:35 +#: 1037205a2c5c49a399b9018e3b18cbe4 +msgid "sphinx_rtd_theme (currently used by Jupyter projects)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:36 +#: d084dea65fef48bbbef16a48b74514af +msgid "jupyter_sphinx_theme (used by ipywidgets)" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:39 +#: 4b2b07b5adb6430294c8803c6c7ee7a8 +msgid "Git and Github Resources" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:40 +#: 4a4a5ed771d246cf95352f00b7adc81e +msgid "" +"If this is your first time working with Github or git, you can leverage " +"the following resources to learn about the tools." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:43 +#: 23ec14cafe4b4723885d8abc441910c6 +msgid "`Try Git `_" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:44 +#: 697f21690e9846a18f7f801c86fc5649 +msgid "`Github Guides `_" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:45 +#: 1e91aaad93c846bd8ed8ed445aeb880c +msgid "`Git Real `_" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:46 +#: e0752dfaec414fdd89a7e73241e77120 +msgid "`Git Documentation `_" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-tools.rst:47 +#: e54b9cc2ac034a368bc9f6618e48806d +msgid "" +"`Git Rebase `_" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:2 +#: 5a83327e952c4ca4bfb606bc29b91b0b +msgid "Understanding our workflow" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:4 +#: 7c2bc51e7d5541739d2569544d85157f +msgid "**High level documentation workflow**" +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:6 +#: f6e991d463cc4576b1d3db6ec5887188 +msgid "Identify a documentation change." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:8 +#: 23c7cf8e23884365b8282ae34d1a5663 +msgid "*Typos:* please go ahead and fix it (or report as a bug)." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:9 +#: e0244ab26da94acbb2cba3376fcd0da5 +msgid "" +"*Open issues:* leave a note in the issue comments that you are working on" +" the issue." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:11 +#: a16c3794aa034fc3bf8084b2a45dce57 +msgid "" +"*New documentation:* open an issue with your idea or suggestion. We'll " +"review the issue and work with you to identify next steps." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:14 +#: 4eb5a3f1817341d9980d0094712d4511 +msgid "Update the source file." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:16 +#: 497cc300c62c4f429711312fdb65c411 +msgid "Commit the change." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:18 +#: 0fc7b72a721a4d919e63dd2701704189 +msgid "Test changes locally." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:20 +#: c9fef1506c414b78bd4669791fb77618 +msgid "Open a pull request." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:22 +#: 569c8ecbcb59445d9f7d231dd7c156d1 +msgid "Check response of automated tests." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:24 +#: 567d09178cde40bda3e2aa8f9787b476 +msgid "" +"If tests pass: Nice job. Wait for reviewer feedback and/ or your pull " +"request to be merged." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:27 +#: db63534ae6514744b321a439b578c48f +msgid "" +"If tests show an error: Revise and resubmit your pull request. You do not" +" need to open a new pull request. If needed, please ask for assistance." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:31 +#: 923e8a8f4c7a49289188f658c0f16fdf +msgid "Celebrate your documentation contribution." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:33 +#: 9888fb4ff2a34bb7889f775be7b417ba +msgid "" +"Repeat. If you would like suggestions for a new documentation issue to " +"work on, please ask." +msgstr "" + +#: ../../source/contributing/docs-contributions/doc-workflow.rst:37 +#: 79714dd419454e9f99cfc2fcc68ed14a +msgid "Thanks for contributing!" +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:2 +#: 682672fd7cb946689c07456fe4808337 +msgid "Getting started" +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:8 +#: 4ed4b223ce11431089595e4673fba176 +msgid "Preparing for your first contribution" +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:9 +#: 5a4bc40fb4bc4100bb2a4f50252a6bd4 +msgid "Our documentation uses reStructured Text, Markdown, and Jupyter notebooks." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:10 +#: 210c40c2d1cc4e648c22e86578b654d7 +msgid "We use Sphinx extensively to build documentation." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:11 +#: ce80b03dd18644679c6f18757459de3c +msgid "We use Transifex to help translate documentation to multiple languages." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:12 +#: a322619f953b4a3cb4289b5caa4705f8 +msgid "We host our documentation on Read the Docs." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:15 +#: 1607ad3491fb4d2fbb18c59646668a1e +msgid "Developing your contribution" +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:17 +#: f3473aaf2e0c4816a995596adddb919e +msgid "" +"Jupyter's documentation is split across several projects, listed on the " +"`Jupyter documentation home page " +"`_. These instructions apply " +"to all Jupyter projects, though some projects have further contribution " +"guidelines." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:20 +#: d5e22056150e458f9ebdbc598c7e4577 +msgid "Clone the repository" +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:21 +#: c6d953e9dd444de9a69cb1920c879451 +msgid "" +"Fork the appropriate project repository on GitHub, depending on which " +"project's documentation you want to contribute to." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:22 +#: b58e42b81cfc465c8956d2983c2e8799 +msgid "Clone the repository to your system." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:25 +#: ba4a564b665d4e35a2376b5d54ad5d6b +msgid "Edit the documentation source file" +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:27 +#: f49da90745c645e5b57bb79820c2211d +msgid "" +"Source files for projects are typically found in the project's " +"``docs/source`` directory. The reStructured text filenames end with " +"``.rst``, and Jupyter notebook files end with ``.ipynb``." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:31 +#: 871a6a92291a4db0ace38adf221b892d +msgid "" +"In your favorite text editor, make desired changes to the ``.rst`` file " +"when working with a reStructured text source file." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:33 +#: f1e3aae88c4d4a4b979d98d1128aa530 +msgid "" +"If a notebook file requires editing, you will need to install Jupyter " +"notebook according to the :ref:`Installation ` document. Then, " +"run the Jupyter notebook and edit the desired file. Before saving the " +"Jupyter ``.ipynb`` file, please clear the output cells. Save the file and" +" test your change." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:40 +#: 32623049fe5e4c1b8e2090e5b2b2eeda +msgid "Testing changes" +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:42 +#: ac0fe1f59e6d4c4ea79cb0dd2631830b +msgid "" +"Sphinx should be installed to test your documentation changes. For best " +"results, we recommend that you install the stable development version " +"Sphinx (``pip install git+https://github.com/sphinx-doc/sphinx@stable``) " +"or the current released version of Sphinx (``pip install sphinx``)." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:47 +#: e37ddcd09a5a4c39b592f26d38d274ab +msgid "" +"In addition, you may need the following packages: sphinxcontrib-spelling," +" sphinx_rtd_theme, nbsphinx, pyenchant, recommonmark 0.4.0 and " +"jupyter_sphinx_theme, which can be installed via ``pip install " +"sphinxcontrib-spelling sphinx_rtd_theme nbsphinx pyenchant " +"recommonmark==0.4.0 jupyter_sphinx_theme``." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:49 +#: 4a4098e09b904a35b278a5e7297056c9 +msgid "" +"If you are on Linux, you may also need to install the Enchant C library " +"by running ``sudo apt-get install enchant``." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:51 +#: 2091e3eda7a3499dbc5907f1ee9befda +msgid "" +"Once everything is installed, the following commands should be executed " +"using the Terminal/command line from the ``docs`` directory:" +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:54 +#: ddc4b749fe1a47e699d3f39f69078232 +msgid "" +"``make html`` builds a local html version of the documentation. The " +"output message will either display errors or provide the location of the " +"html documents. For example, the location provided may be ``build/html`` " +"and to view these documents in your browser enter ``open " +"build/html/index.html``." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:59 +#: c39b69cf069c4796b0f9831b04bbebe9 +msgid "" +"``make linkcheck`` will check whether the external links in the " +"documentation are valid or if they are not longer current (i.e. cause a " +"500 not found error)." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:63 +#: cb938808091746c79c94c1d8ed5f1976 +msgid "" +"Note: We recommend using Python 3.4+ for building the documentation. If " +"you are editing the documentation, you can use Python 2.7.9+ or the " +"Github editor." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:66 +#: e6331a5c435e4f0e868c16f2961ed7cb +msgid "Creating a pull request" +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:67 +#: 3c8897d67b5a49ca9098fde73c696cee +msgid "" +"Once you are satisfied with your changes, submit a GitHub pull request, " +"per the instructions above. If the documentation change is related to an " +"open GitHub issue, please mention the issue number in the pull request " +"message." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:71 +#: e81b032f01034b6784349dfb80d581d9 +msgid "" +"A project reviewer will look over your changes and provide feedback or " +"merge your changes into the documentation." +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:75 +#: 515ea81f03204990aaaf8187530832bd +msgid "Asking questions" +msgstr "" + +#: ../../source/contributing/docs-contributions/getting-started.rst:76 +#: d99e0f981c064a8bbaa11b9a740e6295 +msgid "" +"Feel free to ask questions in the Google Group for Jupyter or on an open " +"issue on GitHub." +msgstr "" + +#: ../../source/contributing/docs-contributions/index.rst:5 +#: 2f8edade1bc046afb5f28e575f0bd68c +msgid "Documentation Guide" +msgstr "" + +#: ../../source/contributing/docs-contributions/index.rst:17 +#: 9b8265cb8b6e477292ec8d73c8c88162 +msgid "" +"Documentation helps guide new users, fosters communication between " +"developers, and shares tips and best practices with other community " +"members. That's why the Jupyter project is focused on documenting new " +"features and to keeping the documentation up-to-date." +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:1 +#: 9c2b0eb70f3d4e89a6f03dd9d5de900d +msgid "Structuring a repo for docs" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:4 +#: f541558c579547b5bafd40882689335a +msgid "Root level of the repo" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:6 +#: cc04471f78e847a8aa9ec57e5487ed61 +msgid "``docs`` directory : All source files for documentation go here." +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:7 +#: 992894b9d7d64cdf93ac686ff0f145e6 +msgid "" +"``readthedocs.yml`` : configuration file for readthedocs to build using " +"conda" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:10 +#: 8906b5fe94e24cdc89ee6ab89b1728db +msgid "" +"![Repo root directory](static/repo-root.png \"Screenshot of GitHub repo " +"root\")" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:12 +#: da546f3b25b545b2a60256c20e4f9d00 +msgid "Inside the docs directory" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:14 +#: a2f70c8185374f548a7d353f5356e592 +msgid "" +"``source`` directory : contains all content source files in ``.rst``, " +"``.md``, or ``.ipynb``" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:16 +#: 6d85a7374b984f35b2da01b73777093e +msgid "``makefile`` : used by Sphinx to build the docs" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:17 +#: b656b685e5f841f48a2deeab5a4066ac +msgid "``environment.yml`` : conda build instructions" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:19 +#: 2dedf50e3fcc4874b951a477b3136315 +msgid "" +"![``docs`` directory](static/docs-directory.png \"Screenshot of docs " +"directory\")" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:22 +#: 82d903c8592e4bea88802bc20f2c91cb +msgid "Sphinx" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:24 +#: 2479b066231a43d7b82d691ef5ebf216 +msgid "``conf.py`` : Sphinx configuration file" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:25 +#: 21899618746a4cda9ab38ebbf0cc51a6 +msgid "``index.rst`` of ``contents.rst`` : Sphinx master table of contents file" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:26 +#: e7c2cd0bd32e469e99ce8ffd51cf99a1 +msgid "``_static`` directory : contains images, drawings, icons" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:27 +#: f51203d3af124741b398bdc6963bba7c +msgid "``_templates`` directory: overrides theme templates and layouts" +msgstr "" + +#: ../../source/contributing/docs-contributions/repo-structure.md:28 +#: 105e384b0c3141139967988ca863f70a +msgid "" +"``build`` directory : html files generated by Sphinx (do not check this " +"directory into GitHub)" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:4 +#: c140323e4d4f4fdd9c5d24d657876f2f +msgid "Setup IPython development environment using boot2docker" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:7 +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:7 +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:7 +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:7 +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:7 +#: ../../source/contributing/ipython-dev-guide/index.rst:7 +#: ../../source/contributing/ipython-dev-guide/js_events.rst:7 +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:7 +#: ../../source/contributing/ipython-dev-guide/less.rst:7 +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:7 +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:7 +#: ../../source/contributing/ipython-dev-guide/releasing.rst:7 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:7 +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:7 +#: ../../source/contributing/ipython-dev-guide/testing.rst:7 +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:7 +#: 0d5e2f4a8f054ac3a622e9d3c8c9ee93 3c7bc86c71b448daab950e3e78634623 +#: 411d4ece8bf5448bbb629e8c39cb0bd9 52631f0a693a486d99869c03b275a88a +#: 6bd491ef455d466abb71920df6b790df 7b203d3464ae49bf90ba7f84f0a1d39f +#: 80c375c7170c494d9ebfd4715788607f 823adb3b4b7d4b608d8322e6e83fca5d +#: 83355318ea3c43fcac853e78a4982f5f a101417b4a7148c69e950e9cc5a854ab +#: b5dd6b1078f84e4f8f0fc0e677ba4ebc b671103e46f349bebf5eaf68ca40cb90 +#: bc8e5531412c4e7f89470db1eba80fa2 e04dea07292e4178a7c0eceaeb8908f6 +#: e1e3ef18f3f24ae99d57b8801caaa3f6 f3f26423f5e94f6f963189e406f2223e +msgid "" +"This is copied verbatim from the old IPython wiki and is currently under " +"development. Much of the information in this part of the development " +"guide is out of date." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:9 +#: 54cb55a3bc4049418e8b32b172e0dbc7 +msgid "" +"The following are instructions on how to get an IPython development " +"environment up and running without having to install anything on your " +"host machine, other than ```boot2docker`` " +"`__ and ```docker`` " +"`__." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:16 +#: 8628ed43b0bb47a98149fab3ea6a476d +msgid "Install ``boot2docker``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:18 +#: d7cb922850b0453c90680423a0f1c50e +msgid "" +"Install `boot2docker `__. " +"There are multiple ways to install, depending on your environment. See " +"the `boot2docker docs `__." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:24 +#: feed9647e192490ba361a26beb570b31 +msgid "Mac OS X" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:26 +#: 2dd5da64ead14694ae4e2993abbceb9e +msgid "On a Mac OS X host with `Homebrew `__ installed:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:33 +#: 99461fdb5f494c7fa0a3cca8c0fd011a +msgid "Initialize ``boot2docker`` VM" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:40 +#: 8caf76ffdacc4503a8f14373609e7352 +msgid "Start VM" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:46 +#: dfc0900168ee46ce967a57717fd5c7be +msgid "" +"The ``boot2docker`` CLI communicates with the docker daemon on the " +"``boot2docker`` VM. To do this, we must set some environment variables, " +"e.g. ``DOCKER_HOST``," +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:54 +#: e54d471e7ea940eabdd51bd8e7f63706 +msgid "To view the IP address of the VM:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:62 +#: 8b78e40a434945b4922e73380d4e9a53 +msgid "Install ``ipython`` from Development Branch" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:69 +#: 26b530e4f20f46de8e22d8111f736429 +msgid "Build Docker Image" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:71 +#: 20e776e136384cf7aa3528ced1849c6d +msgid "" +"Use the Dockerfile in the cloned ``ipython`` directory to build a Docker " +"image." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:80 +#: 0ee96f15dcfe4b9aab94da7b70692cf2 +msgid "Run Docker Container" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:82 +#: 87d967c7cbfa45a58449f10a3643f1fa +msgid "" +"Run a container using the new image. We mount the entire ``ipython`` " +"source tree on the host into the container at ``/srv/ipython`` to enable " +"changes we make to the source on the host immediately reflected in the " +"container." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:93 +#: f8fca82516ff4f56a04575d472006a9c +msgid "To list the running container from another shell on the host:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:103 +#: a0267609e9564e3cb16349e0273108f5 +msgid "Install IPython in Editable Mode" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:105 +#: 7f8c6e0ea6a94b27a778a174777b160f +msgid "" +"Once in the container, you'll need to uninstall the ``ipython`` package " +"and re-install in editable mode to enable your dev changes to be " +"reflected in your environment." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:120 +#: 5bda56f3cb6249aa9bb6d48252e4caf3 +msgid "Run Notebook Server" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:127 +#: f15e19cfd9824fdc886b83fed4566376 +msgid "Visit Notebook Server" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:129 +#: 8c6510aaa7c9475492725f6661c8fb49 +msgid "" +"On your host, run the following command to get the IP of the boot2docker " +"VM if you forgot:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:138 +#: a54975f3efb4416b975ca175ea10d162 +msgid "Then visit it in your browser:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/boot2docker.rst:145 +#: 37ee3200d0384adda4b0970a283b6a68 +msgid "" +"As a shortcut on a Mac, you can run the following in a terminal window " +"(or make it a bash alias):" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:4 +#: 4dfb9d2e93ab452781afa3d774292185 +msgid "Policy on Closing Pull Requests" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:9 +#: e52f393cea0242f4b6ec899334e01d11 +msgid "" +"IPython has the following policy on closing pull requests. The goal of " +"this policy is to keep our pull request queue small and allow us to focus" +" on code that is being actively developed and has a strong chance of " +"being merged in master soon." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:14 +#: 5e94c7bae9b04de1b5ab77586088f38b +msgid "A pull request will be closed when:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:16 +#: 3e126952cde148a5ac8867ed5705b41a +msgid "" +"It has been reviewed, but has sat for a month or more waiting for the " +"submitter to commit more code to address the comments." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:18 +#: b7474b7ebfa943c3a329a792a6af3d71 +msgid "" +"The review process has uncovered larger design or technical issues that " +"extend beyond the details of the specific pull request." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:21 +#: 35d276888850428194e9fca273290b3c +msgid "" +"In particular, we do not accept whole large \"cleanup\" changes which do " +"not address any specific bug. This includes trailing whitespace, PEP8, " +"etc. One of the reasons is that such massive cleanup provide plenty of " +"opportunities to introduce new and subtle bugs." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:27 +#: ada3d033e17647869d810c9aa781384f +msgid "" +"In general we will not close pull requests because of a lack of review. " +"If a pull request has sat for a month or more without review, we need to " +"kick ourselves and get to reviewing it." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:31 +#: e49f37c9349c40e488fea149c45ebddf +msgid "When a pull request is closed we will do the following:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:33 +#: 19d1191d188d4022a25a34e200dd2351 +msgid "" +"Post a github message to the pull request to confirm that everyone is " +"fine with closing the pull request. This message should cite this policy." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:36 +#: e9fdacf79ba44aadb223b09934581109 +msgid "" +"Open an issue to track the pull request. This issue should describe what " +"would be needed in order to reopen the pull request." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:38 +#: cd21baa45d0845e98f15b04d997ef077 +msgid "" +"Post a github message to the pull request encouraging the submitter to " +"continue with the work and detail what issues need to be addressed in " +"order for the pull request to be reopened." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:42 +#: d20bfbd9d2414fb0b1c9de460f772834 +msgid "This policy was discussed in the following thread:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:44 +#: ba848bd1bd8949bdbbb20d057439cdba +msgid "https://mail.scipy.org/pipermail/ipython-dev/2012-August/010025.html" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/closing_prs.rst:47 +#: 733d6d63937744188e0d3e39accfba11 +msgid "Example Message:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:4 +#: 346948f45bbd4cb3bb66290f13f9cef1 +msgid "Coding Style" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:9 +#: ad6f1325cbd34a719273c2a90cc80b8c +msgid "" +"This document describes our coding style. Coding style refers to the " +"following:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:12 +#: 9ec8b2d64fec4eb89369317a905ef9f3 +msgid "How source code is formatted (indentation, spacing, etc.)" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:13 +#: 0468e31698db4300b893cb18ff7296c9 +msgid "How things are named (variables, functions, classes, modules, etc.)" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:16 +#: d7e5c8742a4741969a1a8d7328b3e7a9 +msgid "General coding conventions" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:18 +#: b2ddeefffb434f03bacae9617eba69f3 +msgid "" +"In general, we follow the standard Python style conventions as described " +"in Python's `PEP 8 `__, the " +"official Python Style Guide." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:22 +#: 5e55ff1bc2264d9ea40e5ee3abfcfb2d +msgid "Other general comments:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:24 +#: 0f92d11125944d1bb28087efa3de672c +msgid "" +"In a large file, top level classes and functions should be separated by 2" +" lines to make it easier to separate them visually." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:27 +#: 02e9d598955d45a79df5583c425b779b +msgid "Use 4 spaces for indentation, **never** use hard tabs." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:29 +#: c068f29111ea41eab6c55b140142ac4c +msgid "" +"Keep the ordering of methods the same in classes that have the same " +"methods. This is particularly true for classes that implement similar " +"interfaces and for interfaces that are similar." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:34 +#: 7e0f97db851e42748491a2bffa22cc1d +msgid "Naming conventions" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:36 +#: 311087d241e046e99a54a4cdc89e2b98 +msgid "" +"For naming conventions, we also follow the guidelines of `PEP 8 " +"`__. Some of the existing code" +" doesn't honor this perfectly, but for all new and refactored IPython " +"code, we'll use:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:41 +#: 4ef82fb500e745f69a4dab98b23d2aa0 +msgid "" +"All ``lowercase`` module names. Long module names can have words " +"separated by underscores (``really_long_module_name.py``), but this is " +"not required. Try to use the convention of nearby files." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:45 +#: 69855bc5dc694cc8a5b65887247ec4fd +msgid "``CamelCase`` for class names." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:47 +#: 7a123055a2954f00af0291977d7c9274 +msgid "" +"``lowercase_with_underscores`` for methods, functions, variables and " +"attributes." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:50 +#: e2e592ed44ed4c3fad084ffa8d7baa89 +msgid "" +"Implementation-specific *private* methods will use " +"``_single_underscore_prefix``. Names with a leading double underscore " +"will *only* be used in special cases, as they makes subclassing difficult" +" (such names are not easily seen by child classes)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:55 +#: abdd869acd764f23b30647e8233f0fde +msgid "" +"Occasionally some run-in lowercase names are used, but mostly for very " +"short names or where we are implementing methods very similar to existing" +" ones in a base class (like ``runlines()`` where ``runsource()`` and " +"``runcode()`` had established precedent)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:60 +#: 7801f8a3e6bb43f2993df7eb0e08a95d +msgid "" +"The old IPython codebase has a big mix of classes and modules prefixed " +"with an explicit ``IP`` of ``ip``. This is not necessary and all new code" +" should not use this prefix. The only case where this approach is " +"justified is for classes or functions which are expected to be imported " +"into external namespaces and a very generic name (like Shell) that is " +"likely to clash with something else. However, if a prefix seems " +"absolutely necessary the more specific ``IPY`` or ``ipy`` are preferred." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:69 +#: 2208befd9df642af8d0731844a074cc9 +msgid "All JavaScript code should follow these naming conventions as well." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:72 +#: be63adb2a988460f8963d69f72d4a1ea +msgid "Attribute declarations for objects" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:74 +#: 5189fc0d34ee4721bcfa8a882db911f6 +msgid "" +"In general, objects should declare, in their *class*, all attributes the " +"object is meant to hold throughout its life. While Python allows you to " +"add an attribute to an instance at any point in time, this makes the code" +" harder to read and requires methods to constantly use checks with " +"hasattr() or try/except calls. By declaring all attributes of the object " +"in the class header, there is a single place one can refer to for " +"understanding the object's data interface, where comments can explain the" +" role of each variable and when possible, sensible defaults can be " +"assigned." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:84 +#: cf2eaafb32a64c46a632d71413ec0774 +msgid "" +"If an attribute is meant to contain a mutable object, it should be set to" +" ``None`` in the class and its mutable value should be set in the " +"object's constructor. Since class attributes are shared by all instances," +" failure to do this can lead to difficult to track bugs. But you should " +"still set it in the class declaration so the interface specification is " +"complete and documented in one place." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:91 +#: 99efdfb5a2a84182a02fe5ac3aebccde +msgid "A simple example:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:108 +#: 64ff2e07b3b6425bb87a02cf8e26793a +msgid "New files" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/coding_style.rst:110 +#: 12495e2205fe40f9ad109c54e3b276bd +msgid "" +"When starting a new Python file for IPython, you can use the `following " +"template <./template.py>`__ as a starting point that has a few common " +"things pre-written for you." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:4 +#: 63fb027f476d49f7ae535d02fec75ac4 +msgid "Documenting IPython" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:9 +#: c22cb1f4e9e145899ae1933818a8f8d6 +msgid "" +"When contributing code to IPython, you should strive for clarity and " +"consistency, without falling prey to a style straitjacket. Basically, " +"'document everything, try to be consistent, do what makes sense.'" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:13 +#: 63138515f6204be7bbba47bfb88978e9 +msgid "" +"By and large we follow existing Python practices in major projects like " +"Python itself or NumPy, this document provides some additional detail for" +" IPython." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:18 +#: 83092ba804224fa1b06974604282208e +msgid "Standalone documentation" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:20 +#: 79b92f286b594b59a723ce3c281d8839 +msgid "" +"All standalone documentation should be written in plain text (``.txt``) " +"files using reStructuredText [reStructuredText]\\_ for markup and " +"formatting. All such documentation should be placed in the directory " +"docs/source of the IPython source tree. Or, when appropriate, a suitably " +"named subdirectory should be used. The documentation in this location " +"will serve as the main source for IPython documentation." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:27 +#: 7fd4d03f575b4c308d3082a13ac3a2a1 +msgid "" +"The actual HTML and PDF docs are built using the Sphinx [Sphinx]\\_ " +"documentation generation tool. Once you have Sphinx installed, you can " +"build the html docs yourself by doing:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:36 +#: 665231896f5949c0a6fc3fe79306ecae +msgid "" +"Our usage of Sphinx follows that of matplotlib [Matplotlib]\\_ closely. " +"We are using a number of Sphinx tools and extensions written by the " +"matplotlib team and will mostly follow their conventions, which are " +"nicely spelled out in their documentation guide [MatplotlibDocGuide]\\_. " +"What follows is thus a abridged version of the matplotlib documentation " +"guide, taken with permission from the matplotlib team." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:43 +#: 12a7ca751446453ea6d70077354e91e9 +msgid "" +"If you are reading this in a web browser, you can click on the \"Show " +"Source\" link to see the original reStricturedText for the following " +"examples." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:47 +#: 1cb20a82f1d640a4917df7602d01e474 +msgid "A bit of Python code:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:55 +#: b2bbabfcf02146089195856258bab800 +msgid "An interactive Python session:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:63 +#: 80d465cb64e244d18536e99a498badb7 +msgid "An IPython session:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:75 +#: 25072428da6c46ba9c5458a0105589b3 +msgid "A bit of shell code:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:84 +#: a91500cc041c476fb1841c8dfbe02042 +msgid "Docstring format" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:86 +#: 4e9432648fc04e2190b091964bda32ac +msgid "" +"Good docstrings are very important. Unfortunately, Python itself only " +"provides a rather loose standard for docstrings [PEP257]\\_, and there is" +" no universally accepted convention for all the different parts of a " +"complete docstring. However, the NumPy project has established a very " +"reasonable standard, and has developed some tools to support the smooth " +"inclusion of such docstrings in Sphinx-generated manuals. Rather than " +"inventing yet another pseudo-standard, IPython will be henceforth " +"documented using the NumPy conventions; we carry copies of some of the " +"NumPy support tools to remain self-contained, but share back upstream " +"with NumPy any improvements or fixes we may make to the tools." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:97 +#: bb8e768f8df243d7a21e0d092b6420f4 +msgid "" +"The NumPy documentation guidelines [NumPyDocGuide]\\_ contain detailed " +"information on this standard, and for a quick overview, the NumPy example" +" docstring [NumPyExampleDocstring]\\_ is a useful read." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:101 +#: 2779b0cf5d054671943aef1b833023df +msgid "" +"For user-facing APIs, we try to be fairly strict about following the " +"above standards (even though they mean more verbose and detailed " +"docstrings). Wherever you can reasonably expect people to do " +"introspection with:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:110 +#: 4eca534668754040b95a972a2e450e59 +msgid "the docstring should follow the NumPy style and be fairly detailed." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:112 +#: 184e0770a22c425f817c381c05855846 +msgid "" +"For purely internal methods that are only likely to be read by others " +"extending IPython itself we are a bit more relaxed, especially for " +"small/short methods and functions whose intent is reasonably obvious. We " +"still expect docstrings to be written, but they can be simpler. For very " +"short functions with a single-line docstring you can use something like:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:125 +#: f226699b235b4146a7c7656603ca8a49 +msgid "and for longer multiline strings:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:136 +#: f4a49ae230a04a218640498c0601d034 +msgid "" +"Here are two additional PEPs of interest regarding documentation of code." +" While both of these were rejected, the ideas therein form much of the " +"basis of docutils (the machinery to process reStructuredText):" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:140 +#: 659c16196ebf4574ace5058c5d5814da +msgid "" +"`Docstring Processing System Framework " +"`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:142 +#: 7c3b17b44a8e4a6babd908c6c2153feb +msgid "" +"`Docutils Design Specification " +"`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:145 +#: 6f957565106b4f29950044fb03f04ca0 +msgid "**note**" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:147 +#: f46c97866bcd4285823aecfbca0b01fb +msgid "" +"In the past IPython used epydoc so currently many docstrings still use " +"epydoc conventions. We will update them as we go, but all new code should" +" be documented using the NumPy standard." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:152 +#: 73258e34e93946c69563d8d957804dfe +msgid "Building and uploading" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:154 +#: 4677ba9408ce4dab93f81d27fbde1828 +msgid "" +"The built docs are stored in a separate repository. Through some github " +"magic, they're automatically exposed as a website. It works like this:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:157 +#: c83830983fe14c078d164c3ed41f0306 +msgid "" +"You will need to have sphinx and latex installed. In Ubuntu, install " +"``texlive-latex-recommended texlive-latex-extra texlive-fonts-" +"recommended``. Install the latest version of sphinx from PyPI (``pip " +"install sphinx``)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:161 +#: 2c19b0484cbe4d3780138d01cb680836 +msgid "" +"Ensure that the development version of IPython is the first in your " +"system path. You can either use a virtualenv, or modify your PYTHONPATH." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:164 +#: 078eb126470e420780b06f2d5a540adf +msgid "" +"Switch into the docs directory, and run ``make gh-pages``. This will " +"build your updated docs as html and pdf, then automatically check out the" +" latest version of the docs repository, copy the built docs into it, and " +"commit your changes." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:168 +#: a8a75de9fe614b08a98a58f975df72be +msgid "Open the built docs in a web browser, and check that they're as expected." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:170 +#: 30707409abff4244bd024338995f36d7 +msgid "" +"(When building the docs for a new tagged release, you will have to add " +"its link to index.rst, then run ``python build_index.py`` to update " +"index.html. Commit the change.)" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:173 +#: 8eab53df139c43d39235f98305d5a31d +msgid "" +"Upload the docs with ``git push``. This only works if you have write " +"access to the docs repository." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/documenting_ipython.rst:175 +#: 129a0f86590b4b99bc1b047adf0b6d19 +msgid "" +"If you are building a version that is not the current dev branch, nor a " +"tagged release, then you must run gh-pages.py directly with ``python gh-" +"pages.py ``, and *not* with ``make gh-pages``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:4 +#: 299d8ad7a5c441fbbea4bfde35fbc002 +msgid "IPython on GitHub" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:9 +#: 37fad670de6140b9a64e0643d58d5cfd +msgid "Notes on working with GitHub" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:16 +#: 5d24f3b25f3a40b28d96c56f4582b7b0 +#, python-format +msgid "100% of confirmed issues should have a milestone." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:17 +#: f1979ad04b8c4655bd2ce0d8b55047d9 +msgid "An issue should never be closed without a milestone." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:18 +#: de0202ae003a4851a6f551e5b15a88e4 +msgid "All pull requests should have a milestone." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:19 +#: bf3e6677fba24b3e9ea8aafc715d426e +msgid "" +"All issues closed should be marked with the next release milestone, next " +"backport milestone, or **no action**." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:21 +#: 3dc1a857d68c4e01b26beb55fa49c081 +msgid "Open issues should only lack a milestone if:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:23 +#: dd23a19011f24f8797ca80f9da1a1b26 +msgid "more clarification is required (label: ``needs-info``)" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:25 +#: 51940ea22b584bad8ac674c429616ace +msgid "In general, there will be four milestones with open issues:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:27 +#: aba751e221ad4265870ee49bc939e27c +msgid "" +"**next minor release**. This milestone contains issues that should be " +"backported for the next minor release. See `below <#backporting>`__ for " +"information on backporting." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:30 +#: 4075bbf76d924a44b34caa0e100b69c2 +msgid "" +"**next major release**. This should be the default milestone of all " +"issues. As the release approaches, issues can be explicitly bumped to " +"next release + 1." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:33 +#: 18f44fb1700b4e70a6d1c65d827f879c +msgid "" +"**next major release + 1**. Only issues that we are confident will *not* " +"be included in the next release go here. This milestone should be mostly " +"empty until relatively close to release." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:36 +#: 00b233ad6c064b9ca9c1b17d8a932018 +msgid "" +"**wishlist**. This is the milestone for issues that we have no immediate " +"plans to address." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:39 +#: d9609a46331349d3ae6967229babb28f +msgid "" +"The remaining milestone is **no action** for open or closed issues that " +"require no action:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:42 +#: 7213d15bccc94280820cf752e958210a +msgid "Not actually an issue (e.g. questions, discussion, etc.)" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:43 +#: 8d27013401ae454bb8ed4dc640c118df +msgid "Duplicate of an existing Issue" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:44 +#: de45304279c24157a5caf53257b4b2ae +msgid "Closed because we won't fix it" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:45 +#: dd3d93b328b6401683f7f9dc538b2532 +msgid "" +"When an issue is closed with **no action**, it means that the issue will " +"not be fixed, or it was not an issue at all." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:48 +#: aacc5373e42c4f65b8bf3964c3cf86b2 +msgid "When closing an issue, it should always have one of these milestones:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:50 +#: 65f820dadd4c45f6a855b9c98a84d2fe +msgid "**next minor release** because the issue has been addressed" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:51 +#: 0b7c37fe2be44156ad2ed7350096580a +msgid "**next major release** because the issue has been addressed" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:52 +#: aa3e34f55acc45aeb13f654acc285c7a +msgid "" +"**no action** because the issue *will not* be addressed, or it is a " +"duplicate/non-issue." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:55 +#: 47c18d9a4059434980a1d2f546cb9212 +msgid "" +"In general: When in doubt, mark with **next release**. We can always push" +" back when we get closer to a given release." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:59 +#: 2fa2aaa3111e4a8894630a2a246bd91b +msgid "Labels and issues" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:61 +#: 1b48ef44ae784cd782676bd1357e1101 +msgid "" +"Issues should always be labeled once they are confirmed (not necessary " +"for issues that are still being clarified, or may be duplicates or not " +"issues at all)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:65 +#: b44525579f41421995671dd3aec20383 +msgid "Some significant labels:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:67 +#: f223982e318c4bd1b8254dbaf2b7b34b +msgid "" +"``needs-info``: issue needs more information from submitter before " +"progress can be made" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:69 +#: 3ddd55768b164b50980b048cfa5a03c7 +msgid "``bug``: errors are raised, or unintended behavior occurs" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:70 +#: 9017abab2e704649bc4b6bb520fc1b03 +msgid "``enhancement``: improvements that are not bugs" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:77 +#: cd461c4473084484a8e892f26aaab74e +msgid "" +"backport-X.Y.Z: Any fix for this issue should be backported to the " +"maintenance branch. backports are expressed with milestones, starting " +"with 2.1." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:80 +#: f127f07d960e41d0848b00a3b902f5b4 +msgid "" +"``prio-foo``: a priority level for ranking issues - nonessential, but " +"prio-high/low are useful for explicitly promoting/demoting issues, " +"particularly when nearing release." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:83 +#: 445f1c07afa84ec3805764cef81dff09 +msgid "" +"``ClosedPR``: This issue is a reminder for a PR that was closed for going" +" stale." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:85 +#: e2e269db996643ce9347ad23f9f9741d +msgid "``sprint-friendly``: Obvious or easy fixes, where" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:87 +#: c10161d28be34f95bc2141525679f258 +msgid "" +"All confirmed issues should at least have a ``bug`` or ``enhancement`` " +"label, and be marked with any affected components (e.g ``parallel``, " +"``qtconsole``, ``htmlnotebook``), or particular sources of error (e.g. " +"``py3k`` or ``unicode``) if we have appropriate labels." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:92 +#: 59731c86d2914a17990c5f4168c9c0dd +msgid "" +"The ``sprint-friendly`` label is probably the best place for new " +"contributors to start." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:96 +#: f74fde18d79b45edba4cbced65fc5e03 +msgid "Pull Requests" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:98 +#: 50b967fabae345fb8f4ddb2ad7f763fc +msgid "All work is submitted via Pull Requests." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:99 +#: 762f4d269a0a42f4a19388315a88d4c1 +msgid "" +"Pull Requests can be submitted as soon as there is code worth discussing." +" Pull Requests track the branch, so you can continue to work after the PR" +" is submitted. Review and discussion can begin well before the work is " +"complete, and the more discussion the better. The worst case is that the " +"PR is closed." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:104 +#: b6fc11ed4c8e4195a818bb5627864ed2 +msgid "" +"Pull Requests that have stalled should be closed (see [[our policy on " +"closing PRs\\|Dev: Closing Pull Requests]])" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:106 +#: 25f1dcbdcfab43d8b9b3cf775397fbc4 +msgid "" +"Pull Requests should always be made against master (backporting PRs is " +"described below)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:108 +#: 8cbf00642b324d43ace3fbfc0c33690b +msgid "Pull Requests should be tested, if feasible:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:110 +#: a4ad8679c5de4c6c890385da6c5879e6 +msgid "bugfixes should include regression tests" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:111 +#: dec77406bb5645f1bb23fcb09e3869f3 +msgid "new behavior should at least get minimal exercise" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:113 +#: 8ee3f5b6c1ed4531a66cc7791a48ff01 +msgid "" +"`Travis `__ does a pretty good job" +" testing IPython and Pull Requests, but it may make sense to manually " +"perform tests (possibly with our ``test_pr`` script), particularly for " +"PRs that affect ``IPython.parallel`` or Windows." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:119 +#: 5517d9f6aacd49ee811271221de6423f +msgid "Opening an Issue" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:121 +#: d7d1f727e0a748c884634a654bb969f9 +msgid "When opening a new issue, please take the following steps:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:123 +#: 69ea872f0dc0456b86c4ab96147547da +msgid "" +"Search GitHub and/or Google for your issue to avoid duplicate reports. " +"Keyword searches for your error messages are most helpful." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:125 +#: 47f172581d634af0abfed9f70011fea7 +msgid "" +"If possible, try updating to master and reproducing your issue, because " +"we may have already fixed it." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:127 +#: 287dd2b6c2ad49f9924c73ab42a1cf1d +msgid "Try to include a minimal reproducible test case" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:128 +#: 8eb7315f58354cb1ab5fc776b0708315 +msgid "Include relevant system information. Start with the output of:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:134 +#: eb90284ac4bc43e5a6552cd82d2e6420 +msgid "" +"And include any relevant package versions, depending on the issue, such " +"as matplotlib, numpy, Qt, Qt bindings (PyQt/PySide), tornado, web " +"browser, etc." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:139 +#: 4ef15ae94d004f9983f87435f8b7f5c4 +msgid "Backporting" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:141 +#: 44153b4dd5db4a25a521e334e1e69c90 +msgid "" +"We should keep an ``A.x`` maintenance branch for backporting fixes from " +"master." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:143 +#: 31cb704136a841a6a4bb2b9b146e1c19 +msgid "" +"That branch shall be called ``A.x``, e.g. ``2.x``, not ``2.1``. This way," +" there is only one maintenance branch per release series." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:145 +#: dd3b958dd360438ea3a7a855e5b19a7f +msgid "" +"When an Issue is determined to be appropriate for backporting, it should " +"be marked with the ``A.B`` milestone." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:147 +#: 2cf9406eada24d94afb076aee29d554b +msgid "" +"Any Pull Request which addresses a backport issue should also receive the" +" same milestone." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/github_workflow.rst:149 +#: 500fbea5eb314bb1bbe9ee3786c96a49 +msgid "" +"Patches are backported to the maintenance branch by applying the pull " +"request patch to the maintenance branch (currently with the " +"`backport\\_pr " +"`__ " +"script)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/index.rst:14 +#: 38a902ac7491485eadc53107287c8234 +msgid "Core Documents" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/index.rst:23 +#: 8f52b71a952b42f4976d227401dcb870 +msgid "Lab Meetings" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/index.rst:29 +#: c3f50d264e0d4e99b5b04525948d36fc +msgid "Development Policies" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/index.rst:35 +#: 2ab40139f0374a4e8897a5d26dd77ae8 +msgid "Other Information" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/index.rst:4 +#: dbfbb15c334343c38079e949c884326f +msgid "IPython Development Guide (source: old IPython wiki)" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/index.rst:9 +#: 21721286f4d14beb8d5c38395bb68d06 +msgid "" +"IPython does all of its development using GitHub. All of our development " +"information is hosted on this GitHub wiki. This page indexes all of that " +"information. Developers interested in getting involved with IPython " +"development should start here." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/index.rst:49 +#: 8808c0ab0ff24a89876444f4e16bc46f +msgid "" +"A template for new Python files in IPython: `template.py " +"<./template.py>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:4 +#: 12eac4be1953427bbe90bcc8e567d866 +msgid "JavaScript Events" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:9 +#: 930541cf50af4da7a134c932c5ac412c +msgid "(Note: this page is not currently consistent with IPython/Jupyter master)" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:11 +#: e841fcb3131940f891fcde0e292f600d +msgid "" +"Javascript events are used to notify unrelated parts of the notebook " +"interface when something happens. For example, if the kernel is busy " +"executing code, it may send an event announcing as such, which can then " +"be picked up by other services, like the notification area. For details " +"on how the events themselves work, see the `JQuery documentation " +"`__." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:18 +#: 96e06005de4d4e45b3e5f6f84ca9e1fd +msgid "" +"This page documents the core set of events, and explains when and why " +"they are triggered." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:22 +#: 6886a44c4e9345bcb491a652548a4a94 +msgid "Cell-related events" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:24 +#: 7156cb4067ad403ba217fe010d24b7a3 +msgid "`command\\_mode.Cell <#command_modecell>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:25 +#: 73c5ca4c41c9438889a644f60116fb2f +msgid "`create.Cell <#createcell>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:26 +#: 5548ca1142a1428886163215c6a74f2f +msgid "`delete.Cell <#deletecell>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:27 +#: 308f296e0b154d49ab6f956a9d1124d7 +msgid "`edit\\_mode.Cell <#edit_modecell>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:28 +#: 272c5cda82ec4c6b8bad73d88e1706bd +msgid "`select.Cell <#selectcell>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:29 +#: 6a66b9271d0942d48ca10ee603b08d23 +msgid "`output\\_appended.OutputArea <#output_appendedoutputarea>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:32 +#: 23b7b71918a84d67bda255bdc681b687 +msgid "CellToolbar-related events" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:34 +#: 1f54c0b1da014495b5323a598912db2f +msgid "`preset\\_activated.CellToolbar <#preset_activatedcelltoolbar>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:35 +#: 9f9fa5dde119497ab2fc39c097d65c08 +msgid "`preset\\_added.CellToolbar <#preset_addedcelltoolbar>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:38 +#: 0d4b4df394484c4d81876be52dff5058 +msgid "Dashboard-related events" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:40 +#: e9b4db3eb2984ac5937b5dd89b692046 +msgid "`app\\_initialized.DashboardApp <#app_initializeddashboardapp>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:41 +#: 4d914bb79f2f4f48bd582aaab4b4a844 +msgid "`sessions\\_loaded.Dashboard <#sessions_loadeddashboard>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:44 +#: 1d58d37f01374b0399769286826b32ec +msgid "app\\_initialized.DashboardApp" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:46 +#: baaeb912728441b6b3b9e4223d6db50f +msgid "" +"When the Jupyter Notebook browser window opens for the first time and " +"initializes the Dashboard App. The Dashboard App lists the files and " +"notebooks in the current directory. Additionally, it lets you create and " +"open new Jupyter Notebooks." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:52 +#: 89eb9ad67b244308910574cb55c87967 +msgid "Kernel-related events" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:54 +#: 6fa5db3b64d3418c810762a7a1de7deb +msgid "`execution\\_request.Kernel <#execution_requestkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:55 +#: 4576d28234c842f4a3395853a392dff1 +msgid "`input\\_reply.Kernel <#input_replykernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:56 +#: 0db8674cc9d0452f9b049a9c2f182e57 +msgid "`kernel\\_autorestarting.Kernel <#kernel_autorestartingkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:57 +#: 7d3e414e2ccc40a196d1ae88bb504b0d +msgid "`kernel\\_busy.Kernel <#kernel_busykernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:58 +#: 20a9107c6b354c3b8768f98115357269 +msgid "`kernel\\_connected.Kernel <#kernel_connectedkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:59 +#: c6ed7fa4f51f4b00b301633ca6508368 +msgid "`kernel\\_connection\\_failed.Kernel <#kernel_connection_failedkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:60 +#: 1e494eb7e5bc4ca8a450460aec5cf2f0 +msgid "`kernel\\_created.Kernel <#kernel_createdkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:61 +#: a7ebd8f6d2fa4a05abb31ace9f48bc53 +msgid "`kernel\\_created.Session <#kernel_createdsession>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:62 +#: f36f97d2e2994f6da0d2cf822a059ced +msgid "`kernel\\_dead.Kernel <#kernel_deadkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:63 +#: f3d36814e34e4e09967bd1097d4a6b95 +msgid "`kernel\\_dead.Session <#kernel_deadsession>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:64 +#: 88d18eb1d12f4438b8097491b230689e +msgid "`kernel\\_disconnected.Kernel <#kernel_disconnectedkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:65 +#: 3e15171f93184051bfc32c8725654afd +msgid "`kernel\\_idle.Kernel <#kernel_idlekernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:66 +#: 56f0f3e7f3ba46e5bc0b4433959f66d1 +msgid "`kernel\\_interrupting.Kernel <#kernel_interruptingkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:67 +#: 9c32dbe056c74d7ca12d06fdac4a98d2 +msgid "`kernel\\_killed.Kernel <#kernel_killedkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:68 +#: 1f94d12d3212408281feb5603473c1a6 +msgid "`kernel\\_killed.Session <#kernel_killedsession>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:69 +#: 856b1b8fe049473ba0fb645f707efeae +msgid "`kernel\\_ready.Kernel <#kernel_readykernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:70 +#: d7a0c77ec18c429290e1a0537514ae24 +msgid "`kernel\\_reconnecting.Kernel <#kernel_reconnectingkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:71 +#: f2cf450497e54bdda65002f7082e6937 +msgid "`kernel\\_restarting.Kernel <#kernel_restartingkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:72 +#: 4e7a953c3b59449e82207955f44dba55 +msgid "`kernel\\_starting.Kernel <#kernel_startingkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:73 +#: 12d039a2869e481bbe590d56b8c4a702 +msgid "`send\\_input\\_reply.Kernel <#send_input_replykernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:74 +#: 6bf7f2fdce4c41e8939d7daa30110f70 +msgid "`shell\\_reply.Kernel <#shell_replykernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:75 +#: 91045c387ebf4633aef2e315cae121cc +msgid "`spec\\_changed.Kernel <#spec_changedkernel>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:78 +#: e221b2bf5eb94319800b0f61f9230a87 +msgid "kernel\\_created.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:80 +#: f8041b4223a14e1fbc0c39c5384ceab3 +msgid "" +"The kernel has been successfully created or re-created through " +"``/api/kernels``, but a connection to it has not necessarily been " +"established yet." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:85 +#: a4ac49fbefe3421d898b00a8eb68ebb9 +msgid "kernel\\_created.Session" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:87 +#: 10c6872ebe6c44f29cd3e771a9549e5b +msgid "" +"The kernel has been successfully created or re-created through " +"``/api/sessions``, but a connection to it has not necessarily been " +"established yet." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:92 +#: da3466d2f10d4f76bda63e999b08641b +msgid "kernel\\_reconnecting.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:94 +#: ad3bbed201304e2c8ba98b9448de5585 +msgid "" +"An attempt is being made to reconnect (via websockets) to the kernel " +"after having been disconnected." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:98 +#: cab422bc96ee46afbe55a08997f581f2 +msgid "kernel\\_connected.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:100 +#: ec73ddc1b7b14d50bcb9165e58132351 +msgid "" +"A connection has been established to the kernel. This is triggered as " +"soon as all websockets (e.g. to the shell, iopub, and stdin channels) " +"have been opened. This does not necessarily mean that the kernel is ready" +" to do anything yet, though." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:106 +#: c0f4e60d66814b9d86d7a0e328bdf466 +msgid "kernel\\_starting.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:108 +#: ccdc1b915102440d805854bad8f33827 +msgid "" +"The kernel is starting. This is triggered once when the kernel process is" +" starting up, and can be sent as a message by the kernel, or may be " +"triggered by the frontend if it knows the kernel is starting (e.g., it " +"created the kernel and is connected to it, but hasn't been able to " +"communicate with it yet)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:115 +#: 6eccbde5c0d0412aaa7d320c3880ac69 +msgid "kernel\\_ready.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:117 +#: 413d1ce830014341a3b67b1693f5efa2 +msgid "" +"Like kernel\\_idle.Kernel, but triggered after the kernel has fully " +"started up." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:121 +#: 099a754a33eb47f08a76a0521eb80da8 +msgid "kernel\\_restarting.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:123 +#: d02ce6e0406e4f64bc7c8d523fa17f3c +msgid "" +"The kernel is restarting. This is triggered at the beginning of an " +"restart call to ``/api/kernels``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:127 +#: 129fb9835fe34ee1a0465e97c91fd0d9 +msgid "kernel\\_autorestarting.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:129 +#: 1463637585fe4fe7abbbbb13ecd522e8 +msgid "" +"The kernel is restarting on its own, which probably also means that " +"something happened to cause the kernel to die. For example, running the " +"following code in the notebook would cause the kernel to autorestart:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:139 +#: 0574a1735f6b4b2ba9e2872f47e7e09f +msgid "kernel\\_interrupting.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:141 +#: 2ae7b46ecc554a2db55119b39c56534a +msgid "" +"The kernel is being interrupted. This is triggered at the beginning of a " +"interrupt call to ``/api/kernels``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:145 +#: 11999de0bdf34236ab2a059d2d8e4112 +msgid "kernel\\_disconnected.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:147 +#: dd812e97ae624dd895872cff6643a2b2 +msgid "The connection to the kernel has been lost." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:150 +#: 1a7c697e1b314d7ba8e4e27aa1f77319 +msgid "kernel\\_connection\\_failed.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:152 +#: a64c18354a45409cb3cf11b0914270ac +msgid "" +"Not only was the connection lost, but it was lost due to an error (i.e., " +"we did not tell the websockets to close)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:156 +#: 4188adddcd684b72a10bc9ff020781bc +msgid "kernel\\_idle.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:158 +#: ec3c8daab18a4fad83e9d684fad1ae88 +msgid "The kernel's execution state is 'idle'." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:161 +#: 4903daed0f66496faaa1599260d2d96f +msgid "kernel\\_busy.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:163 +#: b8323a1d6dcb4b76bfd35263c65c4666 +msgid "The kernel's execution state is 'busy'." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:166 +#: d3ede50bc09f4939bfaee884995cf9d3 +msgid "kernel\\_killed.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:168 +#: e8406c290fc74c7196b4efc2d543ea5c +msgid "The kernel has been manually killed through ``/api/kernels``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:171 +#: 03d5c63f86ea44f986201454695987a9 +msgid "kernel\\_killed.Session" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:173 +#: 3a75c2a4eb09424fbb4653094d5ae796 +msgid "The kernel has been manually killed through ``/api/sessions``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:176 +#: db09406450344e799342afe12013ba74 +msgid "kernel\\_dead.Kernel" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:178 +#: 9abbeb7e88b340ce8aafb37c34d5f2d5 +msgid "" +"This is triggered if the kernel dies, and the kernel manager attempts to " +"restart it, but is unable to. For example, the following code run in the " +"notebook will cause the kernel to die and for the kernel manager to be " +"unable to restart it:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:192 +#: dac25fd1c8b3410b89625b25db327df9 +msgid "kernel\\_dead.Session" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:194 +#: 5e1ba16cdabb49a18631848accb9e733 +msgid "" +"The kernel could not be started through ``/api/sessions``. This might be " +"because the requested kernel type isn't installed. Another reason for " +"this message is that the kernel died or was killed, but the session " +"wasn't." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:200 +#: b6eb125cd3a34cd4b8dc55c3bcf0cdbe +msgid "Notebook-related events" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:202 +#: 30e10ff242464f8f922281c798ca1413 +msgid "`app\\_initialized.NotebookApp <#app_initializednotebookapp>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:203 +#: 9bf4ca7760fe44afab3e2b95efbca54b +msgid "`autosave\\_disabled.Notebook <#autosave_disablednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:204 +#: 7961d9e84b2341fe97ba748fee01dbdc +msgid "`autosave\\_enabled.Notebook <#autosave_enablednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:205 +#: f6e98dd179754a0584128b6487cebc94 +msgid "`checkpoint\\_created.Notebook <#checkpoint_creatednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:206 +#: f897a664a9314ebaa9e8456ff5897453 +msgid "" +"`checkpoint\\_delete\\_failed.Notebook " +"<#checkpoint_delete_failednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:207 +#: bb986fa00ad04e449dc7ed25f78a11e3 +msgid "`checkpoint\\_deleted.Notebook <#checkpoint_deletednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:208 +#: 3eec24f8dbe944c8b59da21f4cb5c470 +msgid "`checkpoint\\_failed.Notebook <#checkpoint_failednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:209 +#: e606e74e117345a4b30317c8dbd99fd3 +msgid "" +"`checkpoint\\_restore\\_failed.Notebook " +"<#checkpoint_restore_failednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:210 +#: 4b76a34c908040119889da6671ac6a2d +msgid "`checkpoint\\_restored.Notebook <#checkpoint_restorednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:211 +#: 2b7fbb64d48943bcb6ca6d2304483bab +msgid "`checkpoints\\_listed.Notebook <#checkpoints_listednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:212 +#: f73b758d9088483286021a937acc2d26 +msgid "`command\\_mode.Notebook <#command_modenotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:213 +#: 72afa358c9474157b31e141f0fb612f7 +msgid "`edit\\_mode.Notebook <#edit_modenotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:214 +#: cbb305a30c864a0da359ecb17a1363c6 +msgid "" +"`list\\_checkpoints\\_failed.Notebook " +"<#list_checkpoints_failednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:215 +#: 24cdf3b9f0174cdc97fbbf7044896347 +msgid "`notebook\\_load\\_failed.Notebook <#notebook_load_failednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:216 +#: aa196de6b3de4fc785c2693a175f3987 +msgid "`notebook\\_loaded.Notebook <#notebook_loadednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:217 +#: 903d2498a8f54f2dbd8c292575936b57 +msgid "`notebook\\_loading.Notebook <#notebook_loadingnotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:218 +#: f3fcb30204e04eb1bbcfa4222c74150a +msgid "`notebook\\_rename\\_failed.Notebook <#notebook_rename_failednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:219 +#: a9211d30582e4901926eabb2272d71ae +msgid "`notebook\\_renamed.Notebook <#notebook_renamednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:220 +#: dd643f6ecf124eb184c8a18dd68f4497 +msgid "`notebook\\_restoring.Notebook <#notebook_restoringnotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:221 +#: b7b53bbc8d9e4dd195507f53e1a160ff +msgid "`notebook\\_save\\_failed.Notebook <#notebook_save_failednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:222 +#: 9f14b1e00bca4c96a1527c2eb45d248f +msgid "`notebook\\_saved.Notebook <#notebook_savednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:223 +#: 5ee51d8080e84c84a41cb670deb1d265 +msgid "`notebook\\_saving.Notebook <#notebook_savingnotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:224 +#: 98b66bb36cc543a289bdb13b9bde7cf6 +msgid "`rename\\_notebook.Notebook <#rename_notebooknotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:225 +#: 73586be7987e4d6c91526ac18956896e +msgid "" +"`selected\\_cell\\_type\\_changed.Notebook " +"<#selected_cell_type_changednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:226 +#: 47d6bb6c7b134119a1b430509bfee21d +msgid "`set\\_dirty.Notebook <#set_dirtynotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:227 +#: c5c312cf295d472385293d2640af3af5 +msgid "`set\\_next\\_input.Notebook <#set_next_inputnotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:228 +#: d6b6775efa6e4b14a8f519abd25806af +msgid "`trust\\_changed.Notebook <#trust_changednotebook>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:231 +#: de3142404f1e4135870eb5ab504ac07e +msgid "Other" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:233 +#: 4b73c650019a4cbb8bcc01817956c0f3 +msgid "`open\\_with\\_text.Pager <#open_with_textpager>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/js_events.rst:234 +#: f05e735dafde420291698bb1a1d464c3 +msgid "`rebuild.QuickHelp <#rebuildquickhelp>`__" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:4 +#: a50067b434754e41b8d6c473c1c48103 +msgid "Lab Meetings on Air" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:9 +#: 8fee303e13ad4a26ad54e01da97302da +msgid "" +"Academic labs have long had the tradition of the weekly lab meeting, " +"where all topics of interest to the lab are discussed. IPython has strong" +" roots in academia, but it is also an open source project that needs to " +"engage an active international community. So while our goal with IPython " +"is not to publish the next paper, we've been thinking about the value " +"these regular discussions bring to how teams work on sustained efforts " +"involving difficult problems, and wanted to bring that bit of academic " +"practice into the open source workflow. So we have decided to conduct " +"weekly \"lab meetings\" for IPython, that will be held publicly using a " +"Google Hangout on Air." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:21 +#: 74717f1cfe44459e909a66186d02dac1 +msgid "Logistics" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:23 +#: bd0d5f399e764ecf93c56141e9d73f3e +msgid "" +"We are trying to keep things simple and with a minimum of new moving " +"parts:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:26 +#: 2155f2d3a494425e977bbe9a93f6e69c +msgid "" +"Meetings happen on Tuesdays at 10am California time (i.e. UTC-8 or -7 " +"depending on the time of year)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:28 +#: 3163793eb46048e08162d624430b3aad +msgid "" +"We broadcast the meeting as it happens via G+ and leave the public " +"YouTube link afterwards." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:30 +#: 1ec3a71c315b4f4e9f773d25c921a099 +msgid "" +"During the meeting, all chat that needs to happen by typing can be done " +"on our `Gitter chat room `__." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:33 +#: e16c4874c5244de09302a49d60c7a3ea +msgid "" +"We keep a running document with `minutes of the meeting on HackPad " +"`__ where we summarize main points. (`2015 " +"part 1 `__)" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:37 +#: 4c79599a3236424881e4715ac420392e +msgid "" +"We welcome and encourage help from others in updating these minutes " +"during the meeting, but we'll make no major effort in ensuring that they " +"are a detailed and accurate record of the whole discussion. We simply " +"don't have the time for that." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:43 +#: cd07019147764d1f93240205327d2909 +msgid "Prior meetings" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/lab_meetings.rst:45 +#: fffb91a98b4a4c3eb183ec6d3f53bf9e +msgid "" +"You can find a list of the videos on the `ipythondev YouTube user page " +"`__." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/less.rst:4 +#: 7b76ec58440b4d3da9c9f02691ef3936 +msgid "How to Compile .less Files" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/less.rst:9 +#: fb751ceab04346aeb3ec76b78e1a5a52 +msgid "" +"For testing your development work in CSS, you'll need to compile the " +".less files to CSS. Make sure you have dependencies that LESS requires, " +"including fabric, node, and lessc. Follow the below steps to compile the " +".less files:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/less.rst:18 +#: 618f0cce130a4b4dbcd2ab96bd678df2 +msgid "Alternatively, you can:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:4 +#: 965e93d753f748329c423901980c9e86 +msgid "The Perfect Pull Request" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:9 +#: 94c0bed369b34bbb93fc3bd40084de85 +msgid "A brief guide to making and reviewing pull requests." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:12 +#: ea3ce79a446a47c88007c49822c1c2aa +msgid "1. It works" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:14 +#: c15d2f1fcec1480f85621f0210934e66 +msgid "The code does what it's supposed to!" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:17 +#: 731d8fc210314c1eae68a3e5248d8d95 +msgid "2. It works on all of the platforms that IPython officially supports" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:19 +#: 131922db44da4eb09554df888e92261d +msgid "IPython has to work on:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:21 +#: f49c853347644fcbb5188e292009eca9 +msgid "Linux of various kinds, Windows & Mac" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:22 +#: 73918beb0d0a4278ac3815cdc279f9d5 +msgid "Python 2 & 3" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:25 +#: 268cd49ef6de4fe1ae805dae3a03abd2 +msgid "3. Handles unicode issues properly" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:27 +#: 7eb86ea3510e4d8c8ad6082750a23a12 +msgid "" +"Much of our code base deals with strings and unicode. This needs to be " +"done in a manner that is unicode aware and works on Python 2 and 3. [This" +" article] (http://www.joelonsoftware.com/articles/Unicode.html) is a good" +" intro to unicode." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:33 +#: 8ebf077c4367412f8b6f07de3bc73cd1 +msgid "4. Adheres to our coding style" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:35 +#: d43586a6e403489e91bfb83ba0ce4044 +msgid "" +"Coding style refers to how source code is formatted and how variables, " +"functions, methods and classes are named. Your code should follow our " +"coding style, which is described [[here\\|Dev: Coding style]]." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:40 +#: ec8172329526419c8294f14fec27c63d +msgid "5. Clean & commented" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:42 +#: 790898753f614c699dd9b5d5f845f955 +msgid "" +"The code should be well organized, and have inline comments where " +"appropriate. When we look at the code, it should be clear what it's doing" +" and why. It should not break abstractions that we have established in " +"the project." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:48 +#: 939e47bb4e444316ac430e7cefac638d +msgid "6. Tested" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:50 +#: d550c0493ce34f54b6d634393ad62e80 +msgid "" +"If it fixes a bug, the pull request should ideally add an automated test " +"that fails without the fix, and passes with it. Normally it should be " +"sufficient to copy an existing test and tweak it. New functionality " +"should come with its own tests as well. Details about testing IPython can" +" be found [[here\\|Dev: Testing]]." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:57 +#: 73023d3c0ac44592a5b2716bd58b59aa +msgid "7. Well documented" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/pull_request.rst:59 +#: cc0fec5482bc4d56a0b196f262423daa +msgid "" +"Don't forget to update docstrings, and any relevant parts of `the " +"official documentation `__. " +"New features or significant changes warrant an entry in the *What's New* " +"section too. Details about documenting IPython can be found [[here\\|Dev:" +" Documenting IPython]]." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:4 +#: 2241671799624631b314084dcfeba8c4 +msgid "Python 3 Compatibility Module" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:9 +#: 965808c0426c4068bcc1acbbe1346ef9 +msgid "" +"The ``IPython.utils.py3compat`` module provides a number of functions to " +"make it easier to write code for Python 2 and 3. We also use 2to3 in the " +"setup process to change syntax, and the ``io.open()`` function, which is " +"essentially the built in open function from Python 3." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:11 +#: 31d884dcab7e4ad78d3bf80f84c9f36a +msgid "The names provided are:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:13 +#: eca585e3905b4057962c602a9655be62 +msgid "**PY3**: True in Python 3, False in Python 2." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:16 +#: 34bbdc8ad7104cf6b38ee383505f0cb2 +msgid "Unicode related" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:17 +#: d443889e4c884e579806ca38bf360f3e +msgid "" +"**decode**, **encode**: Shortcuts to decode or encode strings, using " +"``sys.stdin.encoding`` by default, and using replacement characters on " +"errors." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:18 +#: 70edfc3d27184489a33f7c63879d3856 +msgid "" +"**str_to_unicode**, **unicode_to_str**, **str_to_bytes**, " +"**bytes_to_str**: Convert to/from the platform's standard ``str`` type " +"(bytes in Python 2, unicode in Python 3). Each function is a no-op on one" +" of the two platforms." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:19 +#: 7335c7f6b8c84a9c8c090f8ace7a602d +msgid "" +"**cast_unicode**, **cast_bytes**: Accept unknown unicode or byte strings," +" and convert them accordingly." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:20 +#: a5d62bf10fba4f8da90710883c1baf55 +msgid "" +"**cast_bytes_py2**: Casts unicode to byte strings on Python 2, but " +"doesn't do anything on Python 3." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:23 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:20 +#: 0950a45b3bf149b8b7b1468ba6a2e92e 6283e3e0086749b5aca5cd9108520583 +msgid "Miscellaneous" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:24 +#: 3d842709175149ce8c8379d6a84f54a7 +msgid "" +"**input**: Refers to ``raw_input`` on Python 2, ``input`` on Python 3 " +"(needed because 2to3 only converts calls to raw_input, not assignments to" +" other names)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:25 +#: 7908097dce1c4fe8940b2e96ffd03762 +msgid "" +"**builtin_mod_name**: The string name you import to get the builtins " +"(``__builtin__`` --> ``builtins``)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:26 +#: 82370719f3b548a49cd71b1683b93b2a +msgid "**isidentifier**: Checks if a string is a valid Python identifier." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:27 +#: 9ebe685583254b42ac120798fe27102d +msgid "" +"**open**: Simple wrapper for Python 3 unicode-enabled open. Similar to " +"``codecs.open``, but allows universal newlines. The current " +"implementation only supports the very simplest use." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:28 +#: dc16c4e1720b4d22a1da77c0921dac70 +msgid "" +"**MethodType**: ``types.MethodType`` from Python 3. Takes only two " +"arguments: function, instance. The class argument for Python 2 is filled " +"automatically." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:29 +#: f7f2baba95514a9db5267ca84d33b899 +msgid "" +"**doctest_refactor_print**: Can be called on a string or a function (or " +"used as a decorator). In Python 3, it converts print statements in " +"doctests to print() calls. 2to3 does this for real doctests, but we need " +"it in several other places. It simply uses a regex, which is good enough " +"for the current cases." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:30 +#: 341a8fcf2f5b4523b35dd64e42f9a690 +msgid "" +"**u_format**: Where tests use the repr() of a unicode string, it should " +"be written ``'{u}\"thestring\"'``, and fed to this function, which will " +"produce ``'u\"thestring\"'`` for Python 2, and ``'\"thestring\"'`` for " +"Python 3. Can also be used as a decorator, to work on a docstring." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/py3compat.rst:31 +#: ea158fe6b8ba4312ab84611b8dcbfab3 +msgid "" +"**execfile**: Makes a return on Python 3 (where it's no longer a " +"builtin), and upgraded to handle Unicode filenames on Python 2." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:4 +#: 014d0c39373c4afbb8fa56c3e41f5cf9 +msgid "Steps for Releasing IPython" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:9 +#: 6dbdb1993bb24cd48be68612259b6aad +msgid "" +"This document contains notes about the process that is used to release " +"IPython. Our release process is currently not very formal and could be " +"improved." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:13 +#: 80e9b1b34b1c49e894adc29f59efc0c5 +msgid "" +"Most of the release process is automated by the ``release`` script in the" +" ``tools`` directory of our main repository. This document is just a " +"handy reminder for the release manager." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:18 +#: d943db6a7daa412ab45c73b8906f5108 +msgid "0. Environment variables" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:20 +#: 63774855e1e14aa6a59bcaf1b414a1fe +msgid "" +"You can set some env variables to note previous release tag and current " +"release milestone, version, and git tag:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:31 +#: 54dd6b017a654c2988a558402b4edb28 +msgid "" +"These will be used later if you want to copy/paste, or you can just type " +"the appropriate command when the time comes. These variables are not used" +" by scripts (hence no ``export``)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:36 +#: ef38fd381c854dfe957126871b470ffc +msgid "1. Finish release notes" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:38 +#: 8f7dd48d4eb94b57a6a635fc5be18725 +msgid "If a major release:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:40 +#: 76a8a5ee9779481a966574ec866d3202 +msgid "merge any pull request notes into what's new:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:46 +#: b7b62f57f9b045c095784ba16b70382b +msgid "" +"update ``docs/source/whatsnew/development.rst``, to ensure it covers the " +"major points." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:48 +#: 4af4ba8dec3a47d68f6973d140646553 +msgid "move the contents of ``development.rst`` to ``versionX.rst``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:49 +#: 81da28abe2be4079bbc2cf897b8a5a64 +msgid "generate summary of GitHub contributions, which can be done with:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:55 +#: bd5b51c9cd00410b84d2f972658f8bde +msgid "" +"which may need some manual cleanup. Add the cleaned up result and add it " +"to ``docs/source/whatsnew/github-stats-X.rst`` (make a new file, or add " +"it to the top, depending on whether it is a major release). You can use:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:63 +#: c161e072c3044fac827983850d2a8c2a +msgid "" +"to find duplicates and update ``.mailmap``. Before generating the GitHub " +"stats, verify that all closed issues and pull requests :ref:`have " +"appropriate milestones `. `This search " +"`__" +" should return no results." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:71 +#: 4385d3c02f74449dba98d812fe7a7edf +msgid "2. Run the ``tools/build_release`` script" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:73 +#: 3502b9cfe3ba4154a64ef9ce0e77ced9 +msgid "" +"This does all the file checking and building that the real release script" +" will do. This will let you do test installations, check that the build " +"procedure runs OK, etc. You may want to also do a test build of the docs." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:79 +#: 53e0536ea65b42f5b817dace09f038d3 +msgid "3. Create and push the new tag" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:81 +#: 6f1bcb5361394ac69a197760852fbb1c +msgid "Edit ``IPython/core/release.py`` to have the current version." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:83 +#: f59151b5c3ab47669ad0335d9ff9a335 +msgid "Commit the changes to release.py and jsversion:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:90 +#: c284717259914f9e8fc67661ba77fc15 +msgid "Create and push the tag:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:97 +#: 81193b2cc8814d24bf008d753e484860 +msgid "Update release.py back to ``x.y-dev`` or ``x.y-maint``, and push:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:105 +#: f02efff268b34520936661ace689013f +msgid "4. Get a fresh clone of the tag for building the release:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:113 +#: 41ca63fccbb04708a0d08c6166d6e389 +msgid "5. Run the ``release`` script" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:119 +#: 5d90754b1ea14be4bf1e9ae0522c3993 +msgid "" +"This makes the tarballs, zipfiles, and wheels. It posts them to " +"archive.ipython.org and registers the release with PyPI." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:122 +#: b9a8229176b344758142783d496590ae +msgid "This will require that you have current wheel, Python 3.4 and Python 2.7." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:126 +#: 1f994d07c1d040d29dd72dabd3ccd1bc +msgid "7. Update the IPython website" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:128 +#: 53dbb2fe69b34a4981e58eb11ada0966 +msgid "release announcement (news, announcements)" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:129 +#: 3e209bb7490447f69768e32f04663cc9 +msgid "update current version and download links" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:130 +#: 5558ff7d13d94060870d0ccabbe76d33 +msgid "(If major release) update links on the documentation page" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:133 +#: db97ec6df7824fa2a46b2162a18f529f +msgid "8. Drafting a short release announcement" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:135 +#: de8b51dfde3b42d485a29e72d03477a2 +msgid "" +"This should include i) highlights and ii) a link to the html version of " +"the *What's new* section of the documentation." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:138 +#: 4d0e98d8ee604291965ac0a598d9349b +msgid "Post to mailing list, and link from Twitter." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:141 +#: 7513e7438b5e4bf6a3d6024287d1a128 +msgid "9. Update milestones on GitHub" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:143 +#: fe763311c61f44a09b4e75d4c7348f86 +msgid "close the milestone you just released" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:144 +#: 8a224ee2405e46f5a0408bccebf56df4 +msgid "open new milestone for (x, y+1), if it doesn't exist already" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/releasing.rst:147 +#: fbd0c7a2dc294bf1876ce0b07cbfcab8 +msgid "10. Celebrate!" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:4 +#: 36840a5604bd4e30ac5ec6dfb138b7a2 +msgid "Architecture of IPython notebook's Dashboard" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:9 +#: 0b87ec7675e447aeb315c21d26bdc11d +msgid "" +"The tables below show the current RESTful web service architecture " +"implemented in IPython notebook. The listed URL's use the HTTP verbs to " +"return representations of the desired resource." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:13 +#: 07914de32f0047419e774a960341a383 +msgid "" +"We are in the process of creating a new dashboard architecture for the " +"IPython notebook, which will allow the user to navigate through multiple " +"directory files to find desired notebooks." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:18 +#: 7a1d111b89994d32b8015209014ef295 +msgid "Current Architecture" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:23 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:38 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:112 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:145 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:169 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:189 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:212 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:242 +#: 108764fe60e3461c87939f1aa31dafce 2ac9a0cd686942038aff8a84294deb5b +#: 62f7cd4ddeea4e888531c19aed455674 6fb856b95bc4499cac61eb9a9b61b2bc +#: 71f00f1ab5594001aa34710ab9fb798e 9409082c70924a47a11c7b6232decb1e +#: af649f918c974642a59a1051431be3a3 c97ccb36fc184c15808974baa4ba1930 +msgid "HTTP verb" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:23 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:38 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:145 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:169 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:189 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:212 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:242 +#: 0c20a2bac7344c7d932e320cda7e47ec 343032433b614cd492bcd2fecb23ddc6 +#: cd66dc21a78b4d709e71021d8ce58fb0 ce6afd04a8a14a8e868122aca847c992 +#: d6e6a8cfaf0a47c6a8e767d87b24a320 e886e15858e541539a4f8d7004bf9a9c +#: fc8f721e32aa4c7181645c9fe3980e66 +msgid "URL" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:23 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:38 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:112 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:145 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:169 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:189 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:212 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:242 +#: 0173b4249b7243e29809a49cdc06a9b9 049a3be56f544a4dad6b6bf97688c0fb +#: 299dea5ca90b4cd6b0439766cb3c3d24 754ee359198449cc906dfaec7755e0ac +#: 8040598737ad4f779797e3930d4aea48 a2f6677bb9354d15be2bbf9bf21eeb82 +#: aeaa2a33c64c4d30bfbc4ab294cf084d bf8bf25f8c2a45348e6145c0bed6b397 +msgid "Action" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:26 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:28 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:32 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:41 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:44 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:48 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:88 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:115 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:117 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:134 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:137 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:148 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:155 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:172 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:174 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:192 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:199 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:215 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:218 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:220 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:224 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:227 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:231 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:235 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:245 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:248 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:251 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:255 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:259 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:263 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:266 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:268 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:276 +#: 0227ea879a5144a9a3aef08bae4c0d85 02e93feebcb84dc187e483aeba8c1ca1 +#: 03a54302ccc64f59b1dacd1b43e2b989 12f1595bc689463ea3b510caa121f73f +#: 173634557a5241f19c764721d42fb293 1ccfcc41b028430fbb8a24c490292def +#: 1f068d42a1c74ff3ae1a38c05d630e00 1feee400f99640eea70ccb4b998b4fe9 +#: 22157d759fab4491b52a9420241d922d 2f9277b56fc246879761a637cc22d820 +#: 3abc69b43eb047fab8f11d114883861f 4844c50fcdbf4b368666b6abdf0c7e30 +#: 4f75d64a18c64218b01dafe002327e97 5ee1d9ecd71e4ab49b3a6dc33735e91b +#: 5fbb96ac2a064c4d9ed8169a110bda30 6678b2ba73114b63a1463f58caaf0439 +#: 6860df49342a4a58a527f383b2a5e245 6a335330ab644be1bc972fdd924a1b8c +#: 6b7e05e8a3e84795b4448b11d6c73003 7573d4720a974f6c9bdd18f8c15dd380 +#: 7887c24c2cb446efb9ceb9f97cd758d8 7e7b7afdb5cf4163b6bff0f0fa31ea80 +#: 8313bc8df63842c78b645cb1b3d993c3 a2e91beba76044769ec6f629e6b464cd +#: b72a67cd4fa54f27920ba6d7595536b5 be2807a5b3a448739db238fdb3b81e46 +#: ca0382559e2a486380ec519a3036c52b d38c2589d1154f63a6e8e20e59596d33 +#: d5c31cd17b284d8b9d59261f89e9ae31 d66fc6a2daa440abb69e488d70d73098 +#: d982f362dccd42a5a92413226707c72a e256b1ea79cc4a259680a946f7efafd8 +#: e2b342ad5d614c149d79c04e4938f3ce +msgid "``GET``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:26 +#: 41e4dad553174a6d94f0c89ad503c3dd +msgid "/.\\*/\\" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:26 +#: 76b94360d81047d3bf3aa444712a1635 +msgid "Strips trailing slashes." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:28 +#: ae7d69e286e945b494e002a00f2fa397 +msgid "\\/api\\" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:28 +#: af0bbfdd5b5d4c928193b9a10eae1782 +msgid "Returns api version information." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:30 +#: 097a806884aa4a658da18ce5dc3db321 +msgid "``*``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:30 +#: 94b261585b984229b688f0dc4d3c7e5d +msgid "\\/api/notebooks" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:30 +#: 80a37c13d79943fd80d151cf2d395055 +msgid "Deprecated: redirect to /api/contents" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:32 +#: e6b669cd663e4b1e9edc20f15880e591 +msgid "\\/api/nbconvert" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:35 +#: e4c6a60e12484924892cf832223ba63c +msgid "Notebook contents API." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:41 +#: 7e631c4e4dd7416b8da081fe493e804d +msgid "/api/contents" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:41 +#: ddd03f10502d475c9e16a266f80adfbc +msgid "Return a model for the base directory. See /api/contents//." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:44 +#: 11a8643be4544c39980e82d3cce5842b +msgid "/api/contents/ " +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:44 +#: 9659cfdf10d14e8cbcffbdccd286c14d +msgid "" +"Return a model for the given file in the base directory. See " +"/api/contents//." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:48 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:53 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:70 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:73 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:85 +#: 42f24e5e418c40ca8584ba42ff27c41f 6904e86e195c4b6c9f23f77846a3d3a2 +#: 93467ade7c904fcd9f023660b2c5108d 9c5e6a68881e4849aa8c324393a12599 +#: fcc38a149fd046d68ea2c31f4c7fc10f +msgid "/api/contents/ /" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:48 +#: 1ab58e24ec1a4c96a792c41e2fb556b9 +msgid "" +"Return a model for a file or directory. A directory model contains a list" +" of models (without content) of the files and directories it contains." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:53 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:202 +#: 5d9e0e4a830a475288e93f37f02f9af3 85944679bba64fdf84974cf6af2f866a +msgid "``PUT``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:53 +#: b5cebb33e65d49f383f5bbb0549cf847 +msgid "" +"Saves the file in the location specified by name and path. PUT is very " +"similar to POST, but the requester specifies the name, where as with " +"POST, the server picks the name. PUT /api/contents/path/Name.ipynb Save " +"notebook at ``path/Name.ipynb``. Notebook structure is specified in " +"``content`` key of JSON request body. If content is not specified, create" +" a new empty notebook. PUT /api/contents/path/Name.ipynb with JSON body " +"{\"copy\\_from\" : \"[path/to/] OtherNotebook.ipynb\"} Copy OtherNotebook" +" to Name" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:70 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:158 +#: 8c0e0d6c0c5d45bab7b3301429720ff6 92edf36f575f42d4991e1e07f181ffee +msgid "``PATCH``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:70 +#: afee33ba88af4f70ab677cedf4bfd4bc +msgid "Renames a notebook without re-uploading content." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:73 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:92 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:96 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:120 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:126 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:150 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:177 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:195 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:271 +#: 148dab03d0cb4e0c93fd370697ea1845 161c1d823ddb49499a8b7e6d49b2e5f0 +#: 2c1c466ae33146899917997e4d1577f8 3de2284649bd4a119060452d71ae60d6 +#: 877293a12b204b2b8edf78b05f000fdd 975f0a56f63448b2a995622d7f4bcfba +#: a6a0256eb97544cfa051ba751b46a35d bde83325329c4dc8b5b9f3e9ccf25ff1 +#: ffa6c57ef4fe4650ae9ce6b634b86345 +msgid "``POST``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:73 +#: 13c7e29c1b6a4785bb2aa871ad4e07f4 +msgid "" +"Creates a new file or directory in the specified path. POST creates new " +"files or directories. The server always decides on the name. POST " +"/api/contents/path New untitled notebook in path. If content specified, " +"upload a notebook, otherwise start empty. POST /api/contents/path with " +"body {\"copy\\_from\":\"OtherNotebook.ipynb\"} New copy of OtherNotebook " +"in path" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:85 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:102 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:123 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:162 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:205 +#: 11a688582fc640d1b156935328800091 b619c6eedc9a44978df12a262150570c +#: c63acc16c4bd47fc93461099e9c3c2f6 d2a4917d0ff8414b8d27e75ac3005991 +#: fb98a1821a2549fc92d179b35afb2052 +msgid "``DELETE``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:85 +#: 322aa686dae641c28e3e2d3f2715c029 +msgid "delete a file in the given path." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:88 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:92 +#: a137190b365446449e52125125e54b60 b58543a5993448e48a79e5fb6dee24d5 +msgid "/api/contents/ / /checkpoints" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:88 +#: bf57bf246ba34029bba9598c222c8918 +msgid "get lists checkpoint for a file." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:92 +#: c5aa36e7649a42c1961d605d70a70905 +msgid "post creates a new checkpoint." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:96 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:102 +#: 4dbe00412f7446e0a4545808a3d8bffa 6f2c438f52da4b7294b7676d972969d8 +msgid "/api/contents/ / /checkpoints/ " +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:96 +#: 9ac6e7c4a84f43ce916f1e0c13cf2192 +msgid "post restores a file from a checkpoint." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:102 +#: 9b290c927fb545f6830125b89803a9dc +msgid "delete clears a checkpoint for a given file." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:109 +#: f9ee85758003456abe2eaef97768de96 +msgid "Kernel API" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:112 +#: 2dfd8d0f3b7f4f26bf2bbe05d5622117 +msgid "URI" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:115 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:120 +#: 025111c110fa4db1baa2517028268b57 b138fdad48714b5781335dae1f13eb3f +msgid "/api/kernels" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:115 +#: ed18d0178b7f43c08d698020818c581d +msgid "Return a model of all kernels." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:117 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:123 +#: 005a6add2aea470da7443242b7c6e215 bc5ced58f9b24ba8933290fb3b23933f +msgid "/api/kernels /" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:117 +#: 264fa092fbf740828db346f80aebfb8b +msgid "Return a model of kernel with given kernel id." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:120 +#: f662e79f05bb436bb2fc98ae334068de +msgid "Start a new kernel with default or given name." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:123 +#: 66136d2ea0974b17ae3a247d44ceaf37 +msgid "Shutdown the given kernel." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:126 +#: 6e042623c90047ccb2fc03d04604e9a1 +msgid "/api/kernels / /" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:126 +#: b88f4c04c3804e41a1d2c9b3f15c4094 +msgid "" +"Perform action on kernel with given kernel id. Actions can be " +"\"interrupt\" or \"restart\"." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:130 +#: cebf3372c80e45cd81429b6518d4a31d +msgid "``WS``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:130 +#: c68add2ef4a54853917760e9d49bd814 +msgid "/api/kernels / /channels" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:130 +#: 2d62bb4411e648839c8b0282df8ae571 +msgid "Websocket stream" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:134 +#: 3197d2efa52a4e0dbf1ea82a53c7e75f +msgid "/api/kernel specs" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:134 +#: 542496a6c9eb4436b8ad2d601095359f +msgid "Return a spec model of all available kernels." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:137 +#: a67b6bf154954fe19b5d0868dcb00368 +msgid "/api/kernel specs/ " +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:137 +#: 6821a89284a44a8889f01e12ce784091 +msgid "Return a spec model of all available kernels with a given kernel name." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:142 +#: 836532dbe49143fa8b81ea57e333b1a2 +msgid "Sessions API" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:148 +#: 0b6b02fafd1a477c8d4ed22f5d276d9b +msgid "/api/sessions" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:148 +#: ec6d574902b84ddcaaaa100479149f9f +msgid "Return model of active sessions." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:150 +#: 9b9a7727fed24a888c1a956706248403 +msgid "/api/sessions" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:150 +#: 230612fad0534830bc508b1a034b8694 +msgid "" +"If session does not already exist, create a new session with given " +"notebook name and path and given kernel name. Return active session." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:155 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:158 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:162 +#: 64054d69906940bcad0c4041c88d21b2 922408cdde21480b9da4d180575cf0f2 +#: f6ed38a2665c4e669cefc8472bb90e16 +msgid "/api/sessions /" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:155 +#: 4244560785f74fc3bc68cd69e237f8e9 +msgid "Return model of active session with given session id." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:158 +#: f5f9a9fe926f4395b0e422519ee72e36 +msgid "" +"Return model of active session with notebook name or path of session with" +" given session id." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:162 +#: 01ab012e707345869fc18dbe557cb357 +msgid "Delete model of active session with given session id." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:166 +#: 4e7712c6ec8f465e9988a083f7687c88 +msgid "Clusters API" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:172 +#: bc0893670f8149b1b1ee49ebe2b22f3a +msgid "/api/clusters" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:172 +#: 628d0d76df7f41aa836981ec7754c417 +msgid "Return model of clusters." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:174 +#: 09f5bde88c2c4cf29b5f67e3a7f74a0e +msgid "/api/clusters " +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:174 +#: 5f984a1766424d368d788a80e4fee0c2 +msgid "Return model of given cluster." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:177 +#: e21ebb4ad8f74be89ad9c82da3b4fcf3 +msgid "/api/clusters " +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:177 +#: 90d05bf3a97a4bbfb133a426af9e5d86 +msgid "" +"Perform action with given clusters. Valid actions are \"start\" and " +"\"stop\"" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:183 +#: ccd098c1fdb94de595182d3a50bc85d2 +msgid "Old Architecture" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:185 +#: 4d15d9cb360d44a6a9ba086bb8fb6bc3 +msgid "" +"This chart shows the web-services in the single directory IPython " +"notebook." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:192 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:195 +#: ab6e9c5325a949a6888e099997439fa5 f9fb0efb65404a1e92bcabcb92d3f2a8 +msgid "/notebooks" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:192 +#: 8233b36dc53d4e14bf73298017bbdf32 +msgid "return list of dicts with each notebook's info" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:195 +#: 6259b493cda24fda870412b3a578560d +msgid "" +"if sending a body, saving that body as a new notebook; if no body, create" +" a a new notebook." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:199 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:202 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:205 +#: 13a93f0fa35241e2b64a9ffe945b0c66 4eabccf2d3c7499da857ea707c92ebfa +#: b0c160e65f5d4c89b8442477dcf11e9b +msgid "/notebooks /" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:199 +#: 16f023689c2d46de8014d270511e8d68 +msgid "get JSON data for notebook" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:202 +#: 1156eafff44e40cd814b2ebf966da6d3 +msgid "saves an existing notebook with body data" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:205 +#: 1ff3baa28229458993d13e5a227a4c08 +msgid "deletes the notebook with the given ID" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:209 +#: 629edc7b7d0f46fa896ae1d89622dc4d +msgid "This chart shows the architecture for the IPython notebook website." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:215 +#: 7595476515cc42499e07e33bf4d0ea23 +msgid "/" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:215 +#: 5c8de3083f594ac185e7a4d47f0ae7e1 +msgid "navigates user to dashboard of notebooks and clusters." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:218 +#: 5ddb3a2e8a284b78b25805e93b8d0e47 +msgid "/" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:218 +#: fff4ea825d8f4e2da2c244336b95773f +msgid "go to wepage for that notebook" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:220 +#: 2caf16f0ef4545e58af042c2a895d4ed +msgid "/new" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:220 +#: c675d65e6b244f109ca45c19aff7f5aa +msgid "" +"creates a new notebook with profile (or default, if no profile exists) " +"settings" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:224 +#: d235d8b938fb43bfa5eab7444b1c2174 +msgid "/ /copy" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:224 +#: 34d5aa1c6b0546c48fe0a5f76f72e5d2 +msgid "opens a duplicate copy or the notebook with the given ID in a new tab" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:227 +#: 33b951ea336c49b582b81e2d21dcc97d +msgid "/ /print" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:227 +#: 9b8c74efcb7a4f78a97f4122d4607f45 +msgid "" +"prints the notebook with the given ID; if notebook doesn't exist, " +"displays error message" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:231 +#: 035ebd8d5f1d43c1a8757d1cbbce8fcf +msgid "/login" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:231 +#: e2690900437e4b33886b258208411207 +msgid "" +"navigates to login page; if no user profile is defined, it navigates user" +" to dashboard" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:235 +#: 0c3561f3d84e45bb916e2ab7aab27ce3 +msgid "/logout" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:235 +#: f1ba78a9cd874faab6035b349484d693 +msgid "logs out of current profile, and navigates user to login page" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:239 +#: 1370639b2c1749748a6d997b78228ff8 +msgid "This chart shows the Web services that act on the kernels and clusters." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:245 +#: 6c5031d1ce7845248532db18a3fd6d00 +msgid "/kernels" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:245 +#: 1f167ed1ac1842ff8fe33099a21fc907 +msgid "return the list of kernel IDs currently running" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:248 +#: 8bf107229be144d98a8ebe8630a5b828 +msgid "/kernels /" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:248 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:255 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:259 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:263 +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:266 +#: 094957566dff4754af4412e4481b9304 580c3a2a24754add99d9ff9f4218aec5 +#: b9409ce5ac2542e4abe085ec9adecedb dbe8e23bd2794890a6e25d9457af3ca3 +#: f32f062674a247009d430f4df3455c17 +msgid "---" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:251 +#: 23cdf571b1364fee9aaf975479000b78 +msgid "/kernels / " +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:251 +#: 9060d54a7bdb4b9e962b834e7906ae4a +msgid "performs action (restart/kill) kernel with given ID" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:255 +#: 25dc8dd742d94ca892e3e26fdda56ff3 +msgid "/kernels / /iopub" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:259 +#: 33111f4432684fefac4cc89809d690c6 +msgid "/kernels / /shell" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:263 +#: 820ec5a34f8743ffb108fd1c9e77f2d0 +msgid "/rstservice/ render" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:266 +#: 1667831c8d2c4a00b704cd7f1458aecc +msgid "/files/(.\\*)" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:268 +#: d20795068cc0463cb2575d020e58fb8c +msgid "/clusters" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:268 +#: 2e7d100b9e634fb59a81adfa6085aeb9 +msgid "returns a list of dicts with each cluster's information" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:271 +#: ac91a08e11f3418dbc76654b03fa2f20 +msgid "/clusters / /" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:271 +#: 9e50631006584f2d8fc99b11e153d6cd +msgid "performs action (start/stop) on cluster with given profile ID" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:276 +#: 3a304c9f06764d96b3c072701f8b8052 +msgid "/clusters /" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/rest_api.rst:276 +#: 288b0ea059f54249b968d0532d879bf0 +msgid "returns the JSON data for cluster with given profile ID" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:4 +#: cfc3a7a7751945f7a511e6a102ad9d24 +msgid "IPython Sphinx Directive" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:9 +#: d9e8bc8f529c4ab8b2f821928e78ae5d +msgid "" +"The ipython directive is a stateful ipython shell for embedding in sphinx" +" documents. It knows about standard ipython prompts, and extracts the " +"input and output lines. These prompts will be renumbered starting at " +"``1``. The inputs will be fed to an embedded ipython interpreter and the" +" outputs from that interpreter will be inserted as well. For example, " +"code blocks like the following::" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:23 +#: 9bff7a8f5b1a4c00ba784be854a48755 +msgid "will be rendered as" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:34 +#: 82e347e66783425fb7de02914d26d05e +msgid "" +"This tutorial should be read side-by-side with the Sphinx source for this" +" document because otherwise you will see only the rendered output and not" +" the code that generated it. Excepting the example above, we will not in" +" general be showing the literal ReST in this document that generates the " +"rendered output." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:41 +#: 8688b7c183324a2d8f9cf293437ecc29 +msgid "" +"The state from previous sessions is stored, and standard error is " +"trapped. At doc build time, ipython's output and std err will be " +"inserted, and prompts will be renumbered. So the prompt below should be " +"renumbered in the rendered docs, and pick up where the block above left " +"off." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:66 +#: e517a152252d4b12adfff0fbb5234114 +msgid "" +"The embedded interpreter supports some limited markup. For example, you " +"can put comments in your ipython sessions, which are reported verbatim. " +"There are some handy \"pseudo-decorators\" that let you doctest the " +"output. The inputs are fed to an embedded ipython session and the " +"outputs from the ipython session are inserted into your doc. If the " +"output in your doc and in the ipython session don't match on a doctest " +"assertion, an error will be" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:92 +#: d93d5e8d479440a1bb88a17b60bb7c4c +msgid "Multi-line input is supported." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:103 +#: e027e2bdd07249d99343302fa9885821 +msgid "" +"You can do doctesting on multi-line output as well. Just be careful when" +" using non-deterministic inputs like random numbers in the ipython " +"directive, because your inputs are ruin through a live interpreter, so if" +" you are doctesting random output you will get an error. Here we " +"\"seed\" the random number generator for deterministic output, and we " +"suppress the seed line so it doesn't show up in the rendered output" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:132 +#: c70120b9a3cd4c479fc437f386f0808b +msgid "Another demonstration of multi-line input and output" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:156 +#: 13ad36b3b3a4499992739c3dbf755313 +msgid "" +"Most of the \"pseudo-decorators\" can be used an options to ipython mode." +" For example, to setup matplotlib pylab but suppress the output, you can" +" do. When using the matplotlib ``use`` directive, it should occur before" +" any import of pylab. This will not show up in the rendered docs, but " +"the commands will be executed in the embedded interpreter and subsequent " +"line numbers will be incremented to reflect the inputs::" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:177 +#: 2adc486893344c838ff4baa8d53fcd23 +msgid "" +"Likewise, you can set ``:doctest:`` or ``:verbatim:`` to apply these " +"settings to the entire block. For example," +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:211 +#: fbc6ed7268464574b0f543f5d51c9799 +msgid "" +"You can create one or more pyplot plots and insert them with the " +"``@savefig`` decorator." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:223 +#: f1083d495784478faa0ce9ee97a70aa4 +msgid "" +"In a subsequent session, we can update the current figure with some text," +" and then resave" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:236 +#: 2c72a84ef96945bdab3ecf69f69b5f89 +msgid "You can also have function definitions included in the source." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:250 +#: 89db3eccfa0748708140fc9cd2cf388d +msgid "Then call it from a subsequent section." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:262 +#: 210e116dc7e74855abf3827d96f7ad59 +msgid "Writing Pure Python Code" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:264 +#: 5e512833665e425992fbc48a39755d98 +msgid "" +"Pure python code is supported by the optional argument `python`. In this " +"pure python syntax you do not include the output from the python " +"interpreter. The following markup::" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:275 +#: d0dbe4ffc2bb4ccf8fe2611f88641f47 +msgid "Renders as" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:284 +#: 7d87f7bc23ae42c6b3c1f14c8afa6c94 +msgid "" +"We can even plot from python, using the savefig decorator, as well as, " +"suppress output with a semicolon" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:292 +#: a315990e128d4e73a20f28736041c6ec +msgid "Similarly, std err is inserted" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:299 +#: 581ff2edc1d4476a909e45cf15127ee6 +msgid "Comments are handled and state is preserved" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:306 +#: daca03cf7c4a417a9657fd7202499599 +msgid "If you don't see the next code block then the options work." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:313 +#: cf45b89d4c6b40539b8228404670e656 +msgid "Multi-line input is handled." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:323 +#: 79a7a5aa379b4b5cb77a08a0c1b1ec9c +msgid "Functions definitions are correctly parsed" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:336 +#: 96abc78be90949eeaea82d07d1199cae +msgid "And persist across sessions" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:343 +#: 3aae69235c474e57bc1aa0de46e4d91e +msgid "" +"Pretty much anything you can do with the ipython code, you can do with a " +"simple python script. Obviously, though it doesn't make sense to use the " +"doctest option." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:348 +#: 15df4ed7f6974ea19dfbfa073aba1643 +msgid "Pseudo-Decorators" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:350 +#: cef84a507b144cd685d5440fe74a57d1 +msgid "" +"Here are the supported decorators, and any optional arguments they take." +" Some of the decorators can be used as options to the entire block (eg " +"``verbatim`` and ``suppress``), and some only apply to the line just " +"below them (eg ``savefig``)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:355 +#: aeb8e409257b40bbad9126e0998e2109 +msgid "@suppress" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:357 +#: 448a1e209eb148f7b9ffa177c22045bc +msgid "" +"execute the ipython input block, but suppress the input and output block " +"from the rendered output. Also, can be applied to the entire " +"``..ipython`` block as a directive option with ``:suppress:``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:361 +#: 225ef37c79904f71908199e5e28fcdc4 +msgid "@verbatim" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:363 +#: 56a21cc31bb848a999edc602e9adc6d2 +msgid "" +"insert the input and output block in verbatim, but auto-increment the " +"line numbers. Internally, the interpreter will be fed an empty string, so" +" it is a no-op that keeps line numbering consistent. Also, can be applied" +" to the entire ``..ipython`` block as a directive option with " +"``:verbatim:``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:369 +#: 5a56f7eab9a441918e516a63c3ab2b3f +msgid "@savefig OUTFILE [IMAGE_OPTIONS]" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:371 +#: 9f7ce5645f8c4985841647d9889398f4 +msgid "" +"save the figure to the static directory and insert it into the document, " +"possibly binding it into a minipage and/or putting code/figure " +"label/references to associate the code and the figure. Takes args to pass" +" to the image directive (*scale*, *width*, etc can be kwargs); see `image" +" options " +"`_ " +"for details." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:379 +#: d84ca3a078964592a01b67f1b5d2e3e9 +msgid "@doctest" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:381 +#: 45aa63cfadf848cfa9b7f9d561e8ccf5 +msgid "" +"Compare the pasted in output in the ipython block with the output " +"generated at doc build time, and raise errors if they don’t match. " +"Also, can be applied to the entire ``..ipython`` block as a directive " +"option with ``:doctest:``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:387 +#: e3bbf38fdb804ff29cfcaf94a00c628f +msgid "Configuration Options" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:389 +#: 3bfc233da3c54e78b39a3766a6afc130 +msgid "ipython_savefig_dir" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:391 +#: 4340f7d2991c4dcea2729bd1754f0faf +msgid "" +"The directory in which to save the figures. This is relative to the " +"Sphinx source directory. The default is `html_static_path`." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:394 +#: f70f315fe2a24dcfb00a74028f76c6f3 +msgid "ipython_rgxin" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:396 +#: febb8c280e7a4887a0edb4234dec78ce +msgid "" +"The compiled regular expression to denote the start of IPython input " +"lines. The default is re.compile('In \\[(\\d+)\\]:\\s?(.*)\\s*'). You " +"shouldn't need to change this." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:400 +#: a9581d9054554f4fb6d052756cf53154 +msgid "ipython_rgxout" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:402 +#: 561c809ace3f4f238ae24b8da6352c14 +msgid "" +"The compiled regular expression to denote the start of IPython output " +"lines. The default is re.compile('Out\\[(\\d+)\\]:\\s?(.*)\\s*'). You " +"shouldn't need to change this." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:407 +#: 0d2ed9e8fe47432c8fabf4229c55a1d6 +msgid "ipython_promptin" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:409 +#: c755d676920a4e888264bb1c11fcdd3e +#, python-format +msgid "" +"The string to represent the IPython input prompt in the generated ReST. " +"The default is 'In [%d]:'. This expects that the line numbers are used in" +" the prompt." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:413 +#: f9eca0d065c24047aed11bd16d7713bf +msgid "ipython_promptout" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/sphinx_directive.rst:415 +#: fde6fa69eedc4f9b88cb25c8acf0052f +#, python-format +msgid "" +"The string to represent the IPython prompt in the generated ReST. The " +"default is 'Out [%d]:'. This expects that the line numbers are used in " +"the prompt." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:4 +#: 847b01ed0f4f4ce8aff060a21e64fab2 +msgid "Testing IPython for users and developers" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:12 +#: 3127ab43e7ef449ba06cb900cc59d407 +msgid "" +"It is extremely important that all code contributed to IPython has tests." +" Tests should be written as unittests, doctests or other entities that " +"the IPython test system can detect. See below for more details on this." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:17 +#: 1f03cd34df6844b1bef9f8a6dc90ec7f +msgid "" +"Each subpackage in IPython should have its own ``tests`` directory that " +"contains all of the tests for that subpackage. All of the files in the " +"``tests`` directory should have the word \"tests\" in them to enable the " +"testing framework to find them." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:22 +#: 622a8ce424f9483496e6b333976fa130 +msgid "" +"In docstrings, examples (either using IPython prompts like ``In [1]:`` or" +" 'classic' python ``>>>`` ones) can and should be included. The testing " +"system will detect them as doctests and will run them; it offers control " +"to skip parts or all of a specific doctest if the example is meant to be " +"informative but shows non-reproducible information (like filesystem " +"data)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:29 +#: 9a8d86cf16c4479c83dae159d78cbe2d +msgid "" +"If a subpackage has any dependencies beyond the Python standard library, " +"the tests for that subpackage should be skipped if the dependencies are " +"not found. This is very important so users don't get tests failing simply" +" because they don't have dependencies." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:34 +#: 4197144e45014516ba85a49a74d27daf +msgid "" +"The testing system we use is an extension of the `nose " +"`__ test runner. In " +"particular we've developed a nose plugin that allows us to paste verbatim" +" IPython sessions and test them as doctests, which is extremely important" +" for us." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:41 +#: de8c752f83df43a78a21d2fb8803ead2 +msgid "Running the test suite" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:43 +#: 0c0edf770fc349b19efd2a16dafd7293 +msgid "" +"You can run IPython from the source download directory without even " +"installing it system-wide or having configure anything, by typing at the " +"terminal:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:51 +#: 02e44e402c5d43d4905fa6f75ca39ba9 +msgid "To start the web-based notebook you can use:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:57 +#: a1c5b07280b141bfa221eacf2121e5d1 +msgid "" +"In order to run the test suite, you must at least be able to import " +"IPython, even if you haven't fully installed the user-facing scripts yet " +"(common in a development environment). You can then run the tests with:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:65 +#: a1e7475dba9f4d97b4663fad23679e9f +msgid "Once you have installed IPython either via a full install or using:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:71 +#: 70afad929da547b298653cd5e0325b97 +msgid "" +"you will have available a system-wide script called ``iptest`` that runs " +"the full test suite. You can then run the suite with:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:78 +#: e04ae7ffc9a047fbba3ba6cdeff6b53d +msgid "" +"By default, this excludes the relatively slow tests for " +"``IPython.parallel``. To run these, use ``iptest --all``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:81 +#: e1545c93f4fb4c3fb8cf0c4799208119 +msgid "" +"Please note that the iptest tool will run tests against the code imported" +" by the Python interpreter. If the command ``python setup.py symlink`` " +"has been previously run then this will always be the test code in the " +"local directory via a symlink. However, if this command has not been run " +"for the version of Python being tested, there is the possibility that " +"iptest will run the tests against an installed version of IPython." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:89 +#: 9df9cd3d7b6a47b796f7095c6d152716 +msgid "" +"Regardless of how you run things, you should eventually see something " +"like:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:114 +#: 635777f465f441aab9fa3e6c93a06036 +msgid "" +"If not, there will be a message indicating which test group failed and " +"how to rerun that group individually. For example, this tests the " +"``IPython.utils`` subpackage, the ``-v`` option shows progress " +"indicators:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:129 +#: 070a2b832b4c448690198492d2c92ff4 +msgid "" +"Because the IPython test machinery is based on nose, you can use all nose" +" syntax. Options after ``--`` are passed to nose. For example, this lets " +"you run the specific test ``test_rehashx`` inside the ``test_magic`` " +"module:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:145 +#: 4a74f297fe704199a1a7b80b83373329 +msgid "" +"When developing, the ``--pdb`` and ``--pdb-failures`` of nose are " +"particularly useful, these drop you into an interactive pdb session at " +"the point of the error or failure respectively: ``iptest mymodule -- " +"--pdb``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:150 +#: 66f5f2de1a63432e964d6bb28f4425ef +msgid "" +"The system information summary printed above is accessible from the top " +"level package. If you encounter a problem with IPython, it's useful to " +"include this information when reporting on the mailing list; use::" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:156 +#: 95e638ddf3b14690a03ba2200d040a9d +msgid "from IPython import sys_info print sys_info()" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:159 +#: 0f4716f44e08414b9fca8124ba1e3bfa +msgid "and include the resulting information in your query." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:162 +#: da07445f0c5746c58497b1962b379e0d +msgid "Testing pull requests" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:164 +#: c9c93038543e4f8d9beb691e018a3d47 +msgid "" +"We have a script that fetches a pull request from Github, merges it with " +"master, and runs the test suite on different versions of Python. This " +"uses a separate copy of the repository, so you can keep working on the " +"code while it runs. To run it:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:173 +#: 3ad9d2cfd4414d4a8b0aa928237bf5a1 +msgid "" +"The number is the pull request number from Github; the ``-p`` flag makes " +"it post the results to a comment on the pull request. Any further " +"arguments are passed to ``iptest``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:177 +#: c0336dd89c964d7b81aed1ed9d434ce0 +msgid "" +"This requires the `requests `__ " +"and `keyring `__ packages." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:181 +#: d07ff432afa84f3d8ff4f6696bdb657b +msgid "For developers: writing tests" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:183 +#: 48a0015fced04df695a7dab642de86f6 +msgid "" +"By now IPython has a reasonable test suite, so the best way to see what's" +" available is to look at the ``tests`` directory in most subpackages. But" +" here are a few pointers to make the process easier." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:188 +#: ff7924e93f8d4ffaa9ee191fa4faaa73 +msgid "Main tools: ``IPython.testing``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:190 +#: a3d135a6f5984ca4ba522f490a321c9b +msgid "" +"The ``IPython.testing`` package is where all of the machinery to test " +"IPython (rather than the tests for its various parts) lives. In " +"particular, the ``iptest`` module in there has all the smarts to control " +"the test process. In there, the ``make_exclude`` function is used to " +"build a blacklist of exclusions, these are modules that do not get even " +"imported for tests. This is important so that things that would fail to " +"even import because of missing dependencies don't give errors to end " +"users, as we stated above." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:199 +#: a9110fd6905b400a80341fcf534c7854 +msgid "" +"The ``decorators`` module contains a lot of useful decorators, especially" +" useful to mark individual tests that should be skipped under certain " +"conditions (rather than blacklisting the package altogether because of a " +"missing major dependency)." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:205 +#: cf63867beeef47d79fa05d02c15571f4 +msgid "Our nose plugin for doctests" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:207 +#: 1d909d2a5ffe462288b80455ea9172ff +msgid "" +"The ``plugin`` subpackage in testing contains a nose plugin called " +"``ipdoctest`` that teaches nose about IPython syntax, so you can write " +"doctests with IPython prompts. You can also mark doctest output with ``# " +"random`` for the output corresponding to a single input to be ignored " +"(stronger than using ellipsis and useful to keep it as an example). If " +"you want the entire docstring to be executed but none of the output from " +"any input to be checked, you can use the ``# all-random`` marker. The " +"``IPython.testing.plugin.dtexample`` module contains examples of how to " +"use these; for reference here is how to use ``# random``:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:249 +#: d86697439ac84ca1ade313c656b164e1 +msgid "and an example of ``# all-random``:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:279 +#: 1e91125fe09145d89810f4cfbbdaed06 +msgid "" +"When writing docstrings, you can use the ``@skip_doctest`` decorator to " +"indicate that a docstring should *not* be treated as a doctest at all. " +"The difference between ``# all-random`` and ``@skip_doctest`` is that the" +" former executes the example but ignores output, while the latter doesn't" +" execute any code. ``@skip_doctest`` should be used for docstrings whose " +"examples are purely informational." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:286 +#: 035b075465ca4b1eb360b0b7a17a2c70 +msgid "" +"If a given docstring fails under certain conditions but otherwise is a " +"good doctest, you can use code like the following, that relies on the " +"'null' decorator to leave the docstring intact where it works as a test:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:304 +#: 2198ee7b9f574af9a9cf93e9f34decd1 +msgid "" +"With our nose plugin that understands IPython syntax, an extremely " +"effective way to write tests is to simply copy and paste an interactive " +"session into a docstring. You can writing this type of test, where your " +"docstring is meant *only* as a test, by prefixing the function name with " +"``doctest_`` and leaving its body *absolutely empty* other than the " +"docstring. In ``IPython.core.tests.test_magic`` you can find several " +"examples of this, but for completeness sake, your code should look like " +"this (a simple case):" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:322 +#: 12479d043e134d44b7665a668117cbc0 +msgid "" +"This function is only analyzed for its docstring but it is not considered" +" a separate test, which is why its body should be empty." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:326 +#: e71e338da68242568f17b3af822f3e6b +msgid "JavaScript Tests" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:328 +#: 44f78aa840b84278a34ca2989b2ae993 +msgid "" +"We currently use `casperjs `__ for testing the " +"notebook javascript user interface." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:331 +#: 413daed52ddb4d4bb81a300c45411fd6 +msgid "" +"To run the JS test suite by itself, you can either use ``iptest js``, " +"which will start up a new notebook server and test against it, or you can" +" open up a notebook server yourself, and then:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:340 +#: 917755529a984363a719d24f5c121427 +msgid "" +"If your testing notebook server uses something other than the default " +"port (8888), you will have to pass that as a parameter to the test suite " +"as well." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:349 +#: d49615a1ae5a4a91b5fdb44f9dd82849 +msgid "Running individual tests" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:351 +#: 16a48057c5da45fab11a3395c3e92c58 +msgid "" +"To speed up development, you usually are working on getting one test " +"passing at a time. To do this, just pass the filename directly to the " +"``casperjs test`` command like so:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:360 +#: a5d26f334d704c07b6cb09bb677bd804 +msgid "Wrapping your head around the javascript within javascript:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:362 +#: 6391357958c6450d9f4bca6168ca9385 +msgid "" +"CasperJS is a browser that's written in javascript, so we write " +"javascript code to drive it. The Casper browser itself also has a " +"javascript implementation (like the ones that come with Firefox and " +"Chrome), and in the test suite we get access to those using " +"``this.evaluate``, and it's cousins (``this.theEvaluate``, etc). " +"Additionally, because of the asynchronous / callback nature of " +"everything, there are plenty of ``this.then`` calls which define steps in" +" test suite. Part of the reason for this is that each step has a timeout " +"(default of 5 or 10 seconds). Additionally, there are already convenience" +" functions in ``util.js`` to help you wait for output in a given cell, " +"etc. In our javascript tests, if you see functions which " +"``look_like_pep8_naming_convention``, those are probably coming from " +"``util.js``, whereas functions that come with casper " +"``haveCamelCaseNamingConvention``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:377 +#: 305432aa34944a2fa2505c41e6305e45 +msgid "" +"Each file in ``test_cases`` looks something like this (this is " +"``test_cases/check_interrupt.js``):" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:419 +#: 6bfa48d9623d44f9b015145e37a16738 +msgid "" +"For an example of how to pass parameters to the client-side javascript " +"from casper test suite, see the ``casper.wait_for_output`` implementation" +" in ``IPython/html/tests/casperjs/util.js``" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:424 +#: 2746300b37664c069e5ef71252ff3ab2 +msgid "Testing system design notes" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:426 +#: 87916b79573c492e8fd6a19e635b3086 +msgid "" +"This section is a set of notes on the key points of the IPython testing " +"needs, that were used when writing the system and should be kept for " +"reference as it evolves." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:430 +#: c873b64165024579ba58b151b89e9d1d +msgid "" +"Testing IPython in full requires modifications to the default behavior of" +" nose and doctest, because the IPython prompt is not recognized to " +"determine Python input, and because IPython admits user input that is not" +" valid Python (things like ``%magics`` and ``!system commands``." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:435 +#: c1d5724791b6429aa6ce57e427c186eb +msgid "We basically need to be able to test the following types of code:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:439 +#: 530e2c3adc9f407696b8c00dad69f7af +msgid "" +"Pure Python files containing normal tests. These are not a problem, since" +" Nose will pick them up as long as they conform to the (flexible) " +"conventions used by nose to recognize tests." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:445 +#: 206a450f055a473987cab013bebd85c8 +msgid "Python files containing doctests. Here, we have two possibilities:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:448 +#: 35fc15bb464f4a60b45977c3ee447990 +msgid "The prompts are the usual ``>>>`` and the input is pure Python." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:449 +#: da7671def23f4622a2a5bec833c312fa +msgid "" +"The prompts are of the form ``In [1]:`` and the input can contain " +"extended IPython expressions." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:452 +#: c38d144256c84530869805bf79adbc73 +msgid "" +"In the first case, Nose will recognize the doctests as long as it is " +"called with the ``--with-doctest`` flag. But the second case will likely " +"require modifications or the writing of a new doctest plugin for Nose " +"that is IPython-aware." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:459 +#: 7d0ddb3b75fa4a03815f31b0c8132544 +msgid "" +"ReStructuredText files that contain code blocks. For this type of file, " +"we have three distinct possibilities for the code blocks:" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:462 +#: 3c573d911fa44322bac5bee184ec61a1 +msgid "They use ``>>>`` prompts." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:463 +#: ee230c62a26f46448ea367060d8311af +msgid "They use ``In [1]:`` prompts." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:464 +#: f31124d785d445a8a5c7bb027ff158c7 +msgid "They are standalone blocks of pure Python code without any prompts." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:466 +#: 248618fa67eb48b7b015b78c6e85c065 +msgid "" +"The first two cases are similar to the situation #2 above, except that in" +" this case the doctests must be extracted from input code blocks using " +"docutils instead of from the Python docstrings." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:470 +#: 423f2a9009614549b3f4118beae60620 +msgid "" +"In the third case, we must have a convention for distinguishing code " +"blocks that are meant for execution from others that may be snippets of " +"shell code or other examples not meant to be run. One possibility is to " +"assume that all indented code blocks are meant for execution, but to have" +" a special docutils directive for input that should not be executed." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:476 +#: 39835abdb8614654988f46f2ff99a702 +msgid "" +"For those code blocks that we will execute, the convention used will " +"simply be that they get called and are considered successful if they run " +"to completion without raising errors. This is similar to what Nose does " +"for standalone test functions, and by putting asserts or other forms of " +"exception-raising statements it becomes possible to have literate " +"examples that double as lightweight tests." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:485 +#: cc2ee6fdeeab4b0ebab0927a6d1924a8 +msgid "" +"Extension modules with doctests in function and method docstrings. " +"Currently Nose simply can't find these docstrings correctly, because the " +"underlying doctest DocTestFinder object fails there. Similarly to #2 " +"above, the docstrings could have either pure python or IPython prompts." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing.rst:491 +#: 76f88b8defb940c096e03c81db1cc671 +msgid "" +"Of these, only 3-c (reST with standalone code blocks) is not implemented " +"at this point." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:4 +#: 7fd912559a234328a65fcce0722f7681 +msgid "Testing Kernels" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:9 +#: 8573e2494af643f8a8a39a0e9c50d97f +msgid "" +"IPython makes it very easy to create wrapper kernels using its kernel " +"framework. It requires extending the Kernel class and implementing a set " +"of methods for the core functions like execute, history etc. Its also " +"possible to write a full blown kernel in a language of your choice " +"implementing listeners for all the zmq ports." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:15 +#: fe501ffb02594686894a1d145aecc074 +msgid "" +"The key problem for any kernel implemented by these methods is to ensure " +"that it meets the message specification. The kerneltest command is a " +"means to test the installed kernel against the message spec and validate " +"the results." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:21 +#: 7b31dba09d5a47299f3ed4ef5a2b6e7e +msgid "The kerneltest tool" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:23 +#: 549dafb64003458d8f8b967f49c49983 +msgid "" +"The kerneltest tool is part of IPython.testing and is also included in " +"the scripts similar to iptest. This takes 2 parameters - the name of the " +"kernel to test and the test script file. The test script file should be " +"in json format as described in the next section." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:32 +#: 5fd9047027264db9bce3a4edf6876994 +msgid "" +"You can also pass in an optional message spec version to the command. At " +"the moment only the version 5 is supported, but as newer versions are " +"released this can be used to test the kernel against a specific version " +"of the kernel." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:41 +#: b3ddf7ce2d6e4fb1b24c8f77e38bf1d2 +msgid "" +"The kernel to be tested needs to be installed and the kernelspec " +"available in the user IPython directory. The tool will instantiate the " +"kernel and send the commands over ZMQ. For each command executed on the " +"kernel, the tool will validate the reply to ensure that it matches the " +"message specification. In some cases the output is also checked, but the " +"reply is always returned and printed out on the console. This can be used" +" to validate that apart from meeting the message spec the kernel also " +"produced the correct output." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:51 +#: 2019ae65f9724169bb1658e38b787083 +msgid "The test script file" +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:53 +#: cd42870bafca489b90edbae0c2f74d01 +msgid "" +"The test script file is a simple json file that specifies the command to " +"execute and the test code to execute for the command." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:64 +#: 4359262ede2c4aeb880dfc926878c83d +msgid "" +"For some commands in the message specification like kernel\\_info there " +"is no need to specify the test\\_code parameter. The tool validates if it" +" has all the inputs needed to execute the command and will print out an " +"error to the console if it finds a missing parameter. Since the " +"validation is built in, and only required parameters are passed, it is " +"possible to add additional fields in the json file for test " +"documentation." +msgstr "" + +#: ../../source/contributing/ipython-dev-guide/testing_kernels.rst:82 +#: 4fc5400f96844bbf9df84e6464afcedc +msgid "A sample test script for the redis kernel will look like this" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:3 +#: 7cdec6422c37416198c0d6dc7c9dc0d6 +msgid "Getting Started Contributing" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:8 +#: 5c584864213f427bb4cf53d9e5af40a7 +msgid "Welcome fellow contributor! We appreciate your help." +msgstr "" + +#: ../../source/contributing/start-contributing.rst:10 +#: 73a04db5c4e641d7ab7212e7d891bb59 +msgid "" +"We typically label issues appropriate for new contributors as ``good " +"first issue`` or ``help wanted``. To start an issue, you may comment to " +"let everyone know that you'll be working on it. Our repos typically " +"provide development installation instructions in each repo's " +"``CONTRIBUTING.md`` or ``README.md``. **Should you find an issue with our" +" development installation instructions please let us know in our " +"issues.** We want to ensure that our documentation for development " +"installation is accurate. Additionally, other contributors are often " +"available to answer questions about fixing the issue on the issue number " +"or on the repo's gitter channel." +msgstr "" + +#: ../../source/contributing/start-contributing.rst:20 +#: 1543e510452c4f60bfb74d1d3bcdeb08 +msgid "" +"We strive to have a inclusive, welcoming community. Please read our " +"`code of conduct " +"`__" +" to learn more." +msgstr "" + +#: ../../source/contributing/start-contributing.rst:25 +#: 27870a74105e4dc8b93348a653df54ab +msgid "Major Repos and Issue Types" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:28 +#: f8bc48b12f6247dfa01f9868b2956086 +msgid "Python" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:30 +#: 31cebf4c21fc491482b9848d0dc1495e +msgid "" +"IPython, nbgrader, JupyterHub, repo2docker, and Binder are major repos " +"written primarily in Python." +msgstr "" + +#: ../../source/contributing/start-contributing.rst:34 +#: 740e8218ce82493693ecf8e5642edad8 +msgid "`IPython `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:33 +#: 7c6bb14ef43f46e8b6dd4dc0fcaa1d9b +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:34 +#: c4ea2ef1c83849baa0d671b50310b284 +msgid "" +"`Development Installation `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:35 +#: 8980ce7c7f1d455dac53a0bb4823dfdf +msgid "`Gitter Channel `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:37 +#: 74094a649b3a4163a803c22e3c0f9fdf +msgid "`nbgrader `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:37 +#: 9f4f1e39da6a486f9a16e22d6d28afdb +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:38 +#: e3ef8d52742f476baa8a1d334a0e7ce6 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:41 +#: fb670cf1d3b846af9f3df903d311b31f +msgid "`JupyterHub `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:40 +#: 7fff2596d8184dd8bc697357305ae19c +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:41 +#: f29f2ab687864c29b5c1f65392054bbf +msgid "" +"`Development Installation " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:42 +#: ../../source/contributing/start-contributing.rst:46 +#: 3425a1f6d2bf4f48b84505a26ddf9236 9d80f75f7ca64e28b1843070c8807e70 +msgid "`Gitter Channel `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:45 +#: 2382a5f95ff6401daef54cb16b18a5a5 +msgid "`repo2docker `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:44 +#: b16aebc617a046ee98254a0d428b86fb +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:45 +#: 6ed74d76dd3d4d7e85dfd1018e9bf641 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:50 +#: 298a9b5577f146a5bd31d1619d11bd14 +msgid "`Binder `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:48 +#: 78a080d4025741bbb62d49eb898da41b +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:49 +#: e333ee2de4884e3a93e835ae20e80762 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:50 +#: 23739247c3384beabf064105a8fec977 +msgid "`Gitter Channel `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:53 +#: 9fbb8b6c338a486682d5037ea628b13e +msgid "Documentation" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:55 +#: 61a4f2aa39a84f879bc09523abedcdd6 +msgid "" +"All our repos have documentation issues that are relevant for new " +"contributors. For example, the source for the documentation you are " +"reading right now can be found in the `jupyter/jupyter repository on " +"GitHub `__." +msgstr "" + +#: ../../source/contributing/start-contributing.rst:59 +#: ff1386ab435f4f12be129f4043800633 +msgid "JavaScript/TypeScript" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:61 +#: 5f2309aabf2041c59de962a203d20e6b +msgid "" +"Jupyter Notebook, JupyterLab, and IPyWidgets use JavaScript and " +"TypeScript." +msgstr "" + +#: ../../source/contributing/start-contributing.rst:65 +#: fceae4deb69f4bfb9395879db8a518da +msgid "`Jupyter Notebook `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:64 +#: 03a96ddd9cc5469699325673c2147c9a +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:65 +#: ed5087ab6a7c48e2821ce7343cb17b27 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:66 +#: d3e44c8c676e44a4b99deceff65e026d +msgid "`Gitter Channel `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:69 +#: dfe0a041c2654823b5090b494ed4b3aa +msgid "`JupyterLab `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:68 +#: f8a3d06a85694172b541230ac3e76774 +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:69 +#: c20fe39707704351911891655257caa5 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:70 +#: 11e79fafd4284fb9b17301509c70eef0 +msgid "`Gitter Channel `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:74 +#: 0308013e872b4d569576e99af378aac4 +msgid "`IPyWidgets `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:72 +#: 6b0b1dfb23ee4d2ab2ac87120314bbf9 +#, python-format +msgid "" +"`Notable Issues `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:73 +#: 09ab7f21b5844cda8764fd2be5a15953 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:74 +#: fef1d450f24f4efd9cbf571835c7c68a +msgid "`Gitter Channel `__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:77 +#: 811352620e214545a280174aad4b9478 +msgid "DevOps" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:79 +#: e9743098f874459cb2015a25c4e1711a +msgid "" +"JupyterHub, repo2docker, and Binder have many issues related to devops. " +"See the links above." +msgstr "" + +#: ../../source/contributing/start-contributing.rst:82 +#: 22921dcdacfa44078567fa32e0f9cdd6 +msgid "Web Development" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:84 +#: 629d27217ec34d9c8c40c9090f612f2f +msgid "We have issues related to the website." +msgstr "" + +#: ../../source/contributing/start-contributing.rst:87 +#: 18d8b32f1ef04413afa388e1bb4fdfe7 +msgid "" +"`Project Jupyter's Website " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:87 +#: 89af804165234421974541c9598bb1a7 +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +#: ../../source/contributing/start-contributing.rst:88 +#: 8920a227f92e411b8454379f5facc22e +msgid "" +"`Developer Installation `__" +msgstr "" + +#~ msgid "# Building automatically on ReadTheDocs" +#~ msgstr "" + +#~ msgid "## Using the ReadTheDocs service" +#~ msgstr "" + +#~ msgid "### Navigate to Settings" +#~ msgstr "" + +#~ msgid "" +#~ "Each GitHub repo has a Settings " +#~ "tab at the far right of the " +#~ "repo menubar. Navigate to Settings and" +#~ " then the **Webhooks & services** " +#~ "submenu tab." +#~ msgstr "" + +#~ msgid "" +#~ "![Settings and Webhooks & services " +#~ "submenu](static/gh-webhooks-services.png " +#~ "\"Screenshot of GitHub repo settings\")" +#~ msgstr "" + +#~ msgid "### Add the ReadTheDocs service" +#~ msgstr "" + +#~ msgid "" +#~ "Select **Add service** and enter " +#~ "*ReadTheDocs* in the **Available Services**" +#~ " input box." +#~ msgstr "" + +#~ msgid "" +#~ "The Services/Add ReadTheDocs window will " +#~ "open. Press the green **Add service**" +#~ " button to activate the ReadTheDocs " +#~ "service." +#~ msgstr "" + +#~ msgid "" +#~ "![Add ReadTheDocs service](static/gh-add-" +#~ "rtd.png \"Screenshot of adding ReadTheDocs " +#~ "service\")" +#~ msgstr "" + +#~ msgid "### Success" +#~ msgstr "" + +#~ msgid "" +#~ "![Service successfully added](static/gh-rtd-" +#~ "hook-success.png \"Screenshot of service " +#~ "successfully added\")" +#~ msgstr "" + +#~ msgid "*Created: 01-07-2016*" +#~ msgstr "" + +#~ msgid "# Setting up a README" +#~ msgstr "" + +#~ msgid "" +#~ "On a larger scope, having the " +#~ "Jupyter name appear prominently in a " +#~ "repo's `README.md` file improves the " +#~ "project's name awareness." +#~ msgstr "" + +#~ msgid "## Recommended elements in Jupyter project repos" +#~ msgstr "" + +#~ msgid "" +#~ "### Link in repo description Please " +#~ "include a link to the documentation " +#~ "in the repo's description." +#~ msgstr "" + +#~ msgid "" +#~ "![Repo description and documentation " +#~ "link](static/repo-description.png \"Screenshot of" +#~ " documentation link in GitHub repo " +#~ "description\")" +#~ msgstr "" + +#~ msgid "" +#~ "### Badges in README One common " +#~ "way that individuals find documentation " +#~ "is to look for and click on " +#~ "the doc badge that commonly is " +#~ "found right after the title. Another " +#~ "benefit is an easy visual indication " +#~ "if the docs are not rendering " +#~ "properly." +#~ msgstr "" + +#~ msgid "" +#~ "![Badges in README.md](static/repo-badges.png " +#~ "\"Screenshot of badges displayed under " +#~ "the repo title in the README " +#~ "file\")" +#~ msgstr "" + +#~ msgid "### Resources section in README" +#~ msgstr "" + +#~ msgid "" +#~ "A *Resources* section at the end " +#~ "of the `README.md` gives useful links" +#~ " and information to users about the" +#~ " individual project and the larger " +#~ "Project Jupyter organization. Make sure " +#~ "to include any links to the " +#~ "individual project's demo notebooks, if " +#~ "available." +#~ msgstr "" + +#~ msgid "The *Resources* section includes:" +#~ msgstr "" + +#~ msgid "" +#~ "![Resources section in `README.md`](static/repo-" +#~ "resources.png \"Screenshot of resource list" +#~ " at end of README file\")" +#~ msgstr "" + +#~ msgid "## Checklist adding docs to a new or existing GitHub Repo" +#~ msgstr "" + +#~ msgid "[ ] Add badges to README (Edit `README.md` and submit pull request)" +#~ msgstr "" + +#~ msgid "" +#~ "[ ] Add resources section to " +#~ "README (Edit `README.md` and submit pull" +#~ " request)" +#~ msgstr "" + +#~ msgid "*Dated: 1-4-2016* *Revised: 1-7-2016*" +#~ msgstr "" + +#~ msgid "Our documentation uses reStructured Text as well as Jupyter notebooks." +#~ msgstr "" + +#~ msgid "# Structuring a repo for docs" +#~ msgstr "" + +#~ msgid "## Root level of the repo" +#~ msgstr "" + +#~ msgid "``docs`` directory : All source files for documentation go here." +#~ msgstr "" + +#~ msgid "" +#~ "``readthedocs.yml`` : configuration file for" +#~ " readthedocs to build using conda" +#~ msgstr "" + +#~ msgid "" +#~ "![Repo root directory](static/repo-root.png " +#~ "\"Screenshot of GitHub repo root\")" +#~ msgstr "" + +#~ msgid "## Inside the docs directory" +#~ msgstr "" + +#~ msgid "" +#~ "``source`` directory : contains all " +#~ "content source files in ``.rst``, " +#~ "``.md``, or ``.ipynb``" +#~ msgstr "" + +#~ msgid "``makefile`` : used by Sphinx to build the docs" +#~ msgstr "" + +#~ msgid "``environment.yml`` : conda build instructions" +#~ msgstr "" + +#~ msgid "" +#~ "![``docs`` directory](static/docs-directory.png " +#~ "\"Screenshot of docs directory\")" +#~ msgstr "" + +#~ msgid "## Sphinx" +#~ msgstr "" + +#~ msgid "``conf.py`` : Sphinx configuration file" +#~ msgstr "" + +#~ msgid "" +#~ "``index.rst`` of ``contents.rst`` : Sphinx " +#~ "master table of contents file" +#~ msgstr "" + +#~ msgid "``_static`` directory : contains images, drawings, icons" +#~ msgstr "" + +#~ msgid "``_templates`` directory: overrides theme templates and layouts" +#~ msgstr "" + +#~ msgid "" +#~ "``build`` directory : html files " +#~ "generated by Sphinx (do not check " +#~ "this directory into GitHub)" +#~ msgstr "" + +#~ msgid "Resources section in README.md" +#~ msgstr "" + +#~ msgid "docs directory" +#~ msgstr "" + +#~ msgid "" +#~ "Each GitHub repo has a Settings " +#~ "tab at the far right of the " +#~ "repo menubar. Navigate to Settings and" +#~ " then the Webhooks & services submenu" +#~ " tab." +#~ msgstr "" + +#~ msgid "Settings and Webhooks & services submenu" +#~ msgstr "" + +#~ msgid "" +#~ "Select Add service and enter ReadTheDocs" +#~ " in the Available Services input box." +#~ msgstr "" + +#~ msgid "" +#~ "The Services/Add ReadTheDocs window will " +#~ "open. Press the green Add service " +#~ "button to activate the ReadTheDocs " +#~ "service." +#~ msgstr "" + +#~ msgid "Add ReadTheDocs service" +#~ msgstr "" + +#~ msgid "Service successfully added" +#~ msgstr "" + +#~ msgid "Created: 01-07-2016" +#~ msgstr "" + +#~ msgid "" +#~ "On a larger scope, having the " +#~ "Jupyter name appear prominently in a " +#~ "repo's README.md file improves the " +#~ "project's name awareness." +#~ msgstr "" + +#~ msgid "Repo description and documentation link" +#~ msgstr "" + +#~ msgid "Badges in README.md" +#~ msgstr "" + +#~ msgid "" +#~ "A Resources section at the end of" +#~ " the README.md gives useful links and" +#~ " information to users about the " +#~ "individual project and the larger " +#~ "Project Jupyter organization. Make sure " +#~ "to include any links to the " +#~ "individual project's demo notebooks, if " +#~ "available." +#~ msgstr "" + +#~ msgid "The Resources section includes:" +#~ msgstr "" + +#~ msgid "Resources section in" +#~ msgstr "" + +#~ msgid "[ ] Add badges to README (Edit README.md and submit pull request)" +#~ msgstr "" + +#~ msgid "" +#~ "[ ] Add resources section to " +#~ "README (Edit README.md and submit pull" +#~ " request)" +#~ msgstr "" + +#~ msgid "Dated: 1-4-2016 Revised: 1-7-2016" +#~ msgstr "" + +#~ msgid "" +#~ "We support and encourage the translation" +#~ " of Jupyter documentation to other " +#~ "languages as one way of making our" +#~ " community more inclusive and diverse. " +#~ "We are working toward having a " +#~ "consistent model for translation of " +#~ "Sphinx documentation across Jupyter projects" +#~ " based on prior work in the " +#~ "Python and Django communities. This " +#~ "project (https://jupyter.readthedocs.io) and the " +#~ "Jupyter Docker Stacks project are early" +#~ " adopters, meant to prove out the " +#~ "workflows described on this page." +#~ msgstr "" + +#~ msgid "" +#~ "Portable object files (.po) for the " +#~ "source documentation language (e.g., U.S. " +#~ "English, en-US) and for other " +#~ "locales (e.g., Brazilian Portuguese, pt-" +#~ "BR; Moroccan Arabic, ar-MA)" +#~ msgstr "" + +#~ msgid "" +#~ "ReadTheDocs, our preferred service for " +#~ "building and hosting documentation" +#~ msgstr "" + +#~ msgid "" +#~ "Transifex, a localization platform with " +#~ "free plans for open source projects, " +#~ "a friendly web interface, and support" +#~ " for .po files" +#~ msgstr "" + +#~ msgid "Translation CI/CD" +#~ msgstr "" + +#~ msgid "" +#~ "A user creates or edits reStructuredText" +#~ " (.rst) or Markdown (.md) documents " +#~ "written in U.S. English." +#~ msgstr "" + +#~ msgid "" +#~ "Meanwhile, the CI service runs Sphinx" +#~ " commands to extract translatable messages" +#~ " from U.S. English documents into " +#~ "en-US portable object (.po) files. " +#~ "For example:" +#~ msgstr "" + +#~ msgid "" +#~ "The CI service commits the English " +#~ ".po files to the project on " +#~ "GitHub. (e.g., " +#~ "https://github.com/jupyter/jupyter/commit/1330bc409842d8b8a7bbb3a1c63259c34a543be0)" +#~ msgstr "" + +#~ msgid "" +#~ "Transifex makes the messages in the " +#~ "English .po files available for " +#~ "translation in all configured languages." +#~ msgstr "" + +#~ msgid "" +#~ "Transifex submits a pull request to " +#~ "the GitHub project containing a " +#~ "localized .po file when all of the" +#~ " English messages have been translated, " +#~ "and optionally reviewed, for a given " +#~ "language (e.g., " +#~ "https://github.com/jupyter/jupyter/pull/485). For example:" +#~ msgstr "" + +#~ msgid "" +#~ "ReadTheDocs also runs Sphinx to load " +#~ "localized .po files, substitute translations" +#~ " into the original English text, and" +#~ " convert those translated documents into" +#~ " HTML (e.g., " +#~ "https://jupyter.readthedocs.io/pt_BR/latest/architecture/how_jupyter_ipython_work.html)" +#~ msgstr "" + +#~ msgid "" +#~ "We are delighted when members of " +#~ "the Jupyter community want to help " +#~ "translate documentation. We use Transifex " +#~ "to on-board translators in a " +#~ "friendly web interface without requiring " +#~ "knowledge of git, GitHub, Sphinx, or " +#~ "other software developer tools." +#~ msgstr "" + +#~ msgid "" +#~ "Getting Started as a Translator is " +#~ "an excellent on-boarding guide for " +#~ "new Transifex users. Follow the " +#~ "instructions to create an account. When" +#~ " prompted to join a team, look " +#~ "for jupyter-meta-documentation to start" +#~ " contributing translations to this " +#~ "documentation site. Alternatively, visit " +#~ "https://www.transifex.com/project-jupyter/jupyter-meta-" +#~ "documentation/ after creating your account " +#~ "and request to join the project. A" +#~ " project maintainer or language team " +#~ "coordinator will review and approve your" +#~ " request." +#~ msgstr "" + +#~ msgid "" +#~ "Transifex supports Reviewing Translations, " +#~ "peer review by members of a " +#~ "language team, to ensure translation " +#~ "quality. Project maintainers can choose " +#~ "whether Transifex should immediately send " +#~ "a pull request when translations of " +#~ "all text in a document are " +#~ "available or delay submitting a pull " +#~ "request until after all of those " +#~ "translations are also reviewed (the " +#~ "current setting for this project)." +#~ msgstr "" + +#~ msgid "" +#~ "Project maintainers can also grant " +#~ "Transfex team members the role of " +#~ "language coordinator. Language coordinators " +#~ "have permission to invite users to " +#~ "language teams, approve or deny join " +#~ "requests, assign language team roles, " +#~ "and perform other administrative actions " +#~ "for a particular project language. " +#~ "Empowering trusted members of the " +#~ "community as coordinators can help grow" +#~ " translation teams without software " +#~ "developer involvement." +#~ msgstr "" + +#~ msgid "" +#~ "Transifex organizes translation projects under" +#~ " organizations that mirror organizations " +#~ "and repositories on GitHub. At present," +#~ " only the https://github.com/jupyter organization" +#~ " has a corresponding org on Transifex" +#~ " (https://www.transifex.com/project-jupyter/public/) " +#~ "with the following organization " +#~ "administrators:" +#~ msgstr "" + +#~ msgid "" +#~ "Click the organization drop down in " +#~ "the top right of the Transifex " +#~ "dashboard page and select Organization " +#~ "Settings." +#~ msgstr "" + +#~ msgid "Click Details in the left sidebar." +#~ msgstr "" + +#~ msgid "" +#~ "Click inviting administrators in the " +#~ "Management section to add additional " +#~ "admins to the Transifex org." +#~ msgstr "" + +#~ msgid "Click Manage integrations in the left sidebar." +#~ msgstr "" + +#~ msgid "Click Install the Transifex app in the GitHub section." +#~ msgstr "" + +#~ msgid "" +#~ "Return to the tab where you " +#~ "clicked Install the Transifex app and" +#~ " click authorize Transifex in the " +#~ "GitHub section." +#~ msgstr "" + +#~ msgid "" +#~ "Transifex organization administrators can " +#~ "follow the instructions below to " +#~ "configure new translation projects for " +#~ "GitHub projects in the GitHub org " +#~ "corresponding to the one on Transifex." +#~ msgstr "" + +#~ msgid "Click Create new project in the lower left sidebar." +#~ msgstr "" + +#~ msgid "" +#~ "Select Public as the privacy type, " +#~ "indicate that the project is open " +#~ "source, and provide the GitHub URL " +#~ "for the repository." +#~ msgstr "" + +#~ msgid "Select English (en) as the source language." +#~ msgstr "" + +#~ msgid "Click Create project." +#~ msgstr "" + +#~ msgid "Click Settings under the project name in the left sidebar." +#~ msgstr "" + +#~ msgid "Click the Maintainers tab." +#~ msgstr "" + +#~ msgid "" +#~ "Invite additional project maintainers, " +#~ "typically software developers who will " +#~ "be responsible for maintaining the " +#~ "continuous integration and bootstrapping " +#~ "language teams." +#~ msgstr "" + +#~ msgid "Click Languages under the project name in the left sidebar." +#~ msgstr "" + +#~ msgid "Click Edit languages." +#~ msgstr "" + +#~ msgid "Click Apply." +#~ msgstr "" + +#~ msgid "" +#~ "Organization admins, project maintainers, and" +#~ " team managers can add users to " +#~ "translation teams with the roles of " +#~ "language coordinator, reviewer, or translator." +#~ msgstr "" + +#~ msgid "Click Teams in the top nav bar." +#~ msgstr "" + +#~ msgid "Click the Invite Collaborators button in the top right." +#~ msgstr "" + +#~ msgid "Select the role to assign to the user." +#~ msgstr "" + +#~ msgid "Click Invite more to enter additional users or Send invitation." +#~ msgstr "" + +#~ msgid "" +#~ "configure Sphinx to produce .po files" +#~ " for the source language and read " +#~ ".po files containing translations" +#~ msgstr "" + +#~ msgid "configure Transifex to watch for source language .po file changes" +#~ msgstr "" + +#~ msgid "" +#~ "configure the project CI service to " +#~ "update source language .po files when" +#~ " contributors make changes to the " +#~ "source documentation" +#~ msgstr "" + +#~ msgid "" +#~ "Project developers can do the following" +#~ " to configure Sphinx to seed source" +#~ " .po files and recognization translation" +#~ " .po files." +#~ msgstr "" + +#~ msgid "" +#~ "Add sphinx-intl to your Sphinx " +#~ "project requirements.txt or environment.yaml " +#~ "if it does not already exist." +#~ msgstr "" + +#~ msgid "Run sphinx-intl create-txconfig in the docs/ directory." +#~ msgstr "" + +#~ msgid "Add the following to the Sphinx source/conf.py file." +#~ msgstr "" + +#~ msgid "" +#~ "Run make gettext to extract all " +#~ "strings from the English source " +#~ "documentation." +#~ msgstr "" + +#~ msgid "Run sphinx-intl update -l en to generate the English source .po files." +#~ msgstr "" + +#~ msgid "" +#~ "Submit, review, and merge a pull " +#~ "request with the changes and generated" +#~ " .po files." +#~ msgstr "" + +#~ msgid "Click the Integrations tab." +#~ msgstr "" + +#~ msgid "Click Link Repository in the GitHub section." +#~ msgstr "" + +#~ msgid "" +#~ "Select the appropriate GitHub repository " +#~ "and integration branch. Then click Next." +#~ msgstr "" + +#~ msgid "" +#~ "Copy and paste the following " +#~ "configuration into the dialog, adjusting " +#~ "the commented values as appropriate, and" +#~ " then click Next." +#~ msgstr "" + +#~ msgid "" +#~ "Select when Transifex will submit " +#~ "translations a back to the repository." +#~ " Then click Save & Sync." +#~ msgstr "" + +#~ msgid "Click Close." +#~ msgstr "" + +#~ msgid "Click Resources in the left sidebar." +#~ msgstr "" + +#~ msgid "Click one of the .po files to see translation progress by language." +#~ msgstr "" + +#~ msgid "" +#~ "Click one of the languages to see" +#~ " details about translation progress, " +#~ "translate text, and review translations. " +#~ "See the Translator workflows section " +#~ "above for details." +#~ msgstr "" + +#~ msgid "" +#~ "After confirming the initial English .po" +#~ " files have reached Transifex, set up" +#~ " continuous integration to ensure source" +#~ " strings are kept up-to-date in" +#~ " Transifex whenever the English " +#~ "documentation changes. The steps to " +#~ "accomplish this end vary depending on" +#~ " the CI provider. The following " +#~ "describes how what to do when " +#~ "using GitHub Actions." +#~ msgstr "" + +#~ msgid "" +#~ "Create a new GitHub actions workflow " +#~ "file .github/workflows/gettext.yml in the " +#~ "project." +#~ msgstr "" + +#~ msgid "" +#~ "Add the following content to the " +#~ "file. Note that secrets.GITHUB_TOKEN is " +#~ "a built-in secret, not something " +#~ "you need to configure ahead of " +#~ "time." +#~ msgstr "" + +#~ msgid "" +#~ "Note the name of existing ReadTheDocs" +#~ " project containing your source language" +#~ " (e.g., jupyter)." +#~ msgstr "" + +#~ msgid "Click Import a Project." +#~ msgstr "" + +#~ msgid "Click Import Manually." +#~ msgstr "" + +#~ msgid "" +#~ "Enter the project name you noted " +#~ "above suffixed with a target language" +#~ " locale (e.g., jupyter-es, jupyter-" +#~ "pt-br)." +#~ msgstr "" + +#~ msgid "Check Edit advanced project options." +#~ msgstr "" + +#~ msgid "Click Next." +#~ msgstr "" + +#~ msgid "" +#~ "Select the name of the target " +#~ "language from the Language drop down " +#~ "(e.g. es -> Spanish, es-mx -> " +#~ "Mexican Spanish, pt-br -> Brazilian " +#~ "Portuguese)." +#~ msgstr "" + +#~ msgid "Click Finish." +#~ msgstr "" + +#~ msgid "Click Admin." +#~ msgstr "" + +#~ msgid "Click Translations." +#~ msgstr "" + +#~ msgid "" +#~ "Choose the name of the translation " +#~ "project created in step 5 from the" +#~ " Project drop down." +#~ msgstr "" + +#~ msgid "Click Add." +#~ msgstr "" + +#~ msgid "" +#~ "Now, any time you merge a pull " +#~ "request from Transifex containing .po " +#~ "translation file updates, ReadTheDocs will " +#~ "build both the source documentation site" +#~ " as well as sites for all " +#~ "supported languages. ReadTheDocs will " +#~ "associate the sites with one another " +#~ "and make them accessible via language" +#~ " links in a popup." +#~ msgstr "" + +#~ msgid "ReadTheDocs popup" +#~ msgstr "" + +#~ msgid "docs directory : All source files for documentation go here." +#~ msgstr "" + +#~ msgid "" +#~ "readthedocs.yml : configuration file for " +#~ "readthedocs to build using conda" +#~ msgstr "" + +#~ msgid "Repo root directory" +#~ msgstr "" + +#~ msgid "" +#~ "source directory : contains all content" +#~ " source files in .rst, .md, or " +#~ ".ipynb" +#~ msgstr "" + +#~ msgid "makefile : used by Sphinx to build the docs" +#~ msgstr "" + +#~ msgid "environment.yml : conda build instructions" +#~ msgstr "" + +#~ msgid "directory" +#~ msgstr "" + +#~ msgid "conf.py : Sphinx configuration file" +#~ msgstr "" + +#~ msgid "index.rst of contents.rst : Sphinx master table of contents file" +#~ msgstr "" + +#~ msgid "_static directory : contains images, drawings, icons" +#~ msgstr "" + +#~ msgid "_templates directory: overrides theme templates and layouts" +#~ msgstr "" + +#~ msgid "" +#~ "build directory : html files generated" +#~ " by Sphinx (do not check this " +#~ "directory into GitHub)" +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/contributor.po b/docs/source/locale/en/LC_MESSAGES/contributor.po new file mode 100644 index 000000000..08047c435 --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/contributor.po @@ -0,0 +1,466 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-05-09 11:43+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.8.0\n" + +#: ../../source/contributor/content-contributor.rst:2 +#: 03859b1b5045413e91671951d71e0b8f +msgid "Contributors" +msgstr "" + +# 1171d51e6719464b968b01a30c2df1d4 +#: ../../source/contributor/content-contributor.rst:13 +#: d6c85cbfbabb456882d48bfb369c5f2b +msgid "" +"Whether you are a new, returning, or current contributor to Project " +"Jupyter's subprojects or IPython, **we welcome you**." +msgstr "" + +# 300e2003927049dab5e95afdb87961d3 +#: ../../source/contributor/content-contributor.rst:16 +#: 0f5824fe01e84f1e997d8ef85cd9fe97 +msgid "" +"Project Jupyter has seen steady growth over the past several years, and " +"it is wonderful to see the many ways people are using these projects. As " +"a result of this rapid expansion, our project maintainers are balancing " +"many requirements, needs, and resources. We ask contributors to take some" +" time to become familiar with our contribution guides and spend some time" +" learning about our project communication and workflow." +msgstr "" + +# b8bdcf9762b9420b982a51c87522bb59 +#: ../../source/contributor/content-contributor.rst:23 +#: 7d9558a57558495e89fbd211a5d56d6b +msgid "" +"The Contributor Guides and individual project documentation offer " +"guidance. If you have a question, please ask us. `Community Resources " +"`_ provides information on our " +"commonly used communication methods." +msgstr "" + +# a6410f8dcf2a40f4bb0ac93598cba376 +#: ../../source/contributor/content-contributor.rst:28 +#: c35196bdf6184975bd0e8786bb7491dc +msgid "" +"We are very pleased to have you as a contributor, and we hope you will " +"find valuable your impact on the projects. **Thank you** for sharing your" +" interests, ideas, and skills with us." +msgstr "" + +# 135f6b0b508342ce97970e34fc45d3e7 +#: ../../source/contributor/content-contributor.rst:33 +#: 8f2a212b40fc453bb27160ca35e45985 +msgid "Do I really have something to contribute to Jupyter?" +msgstr "" + +# c019e9e3e874449c97154d6e7a727e78 +#: ../../source/contributor/content-contributor.rst:35 +#: b9dd11ab6dea4d428fbea31feee96aa6 +msgid "" +"Absolutely ✅. There are always ways to contribute to this community! " +"Whether it is is contributing code, improving documentation and " +"communications, teaching others, or participating in conversations in the" +" community, we welcome and value your contribution!" +msgstr "" + +# 98869a235e8a4a889da32cec31b99573 +#: ../../source/contributor/content-contributor.rst:41 +#: a5fb80cddcca426ca527cec6764ab7d8 +msgid "What kinds of contributions can I make?" +msgstr "" + +# 8f10671ad67d4eea908dd64ffee52b4c +#: ../../source/contributor/content-contributor.rst:43 +#: e922d3aba5c6476ca67843158158bc3b +msgid "" +"The following sections try to provide inspirations for different ways " +"that you can contribute to the Jupyter ecosystem. They're non-complete - " +"if you can think up any way to make an improvement, we appreciate it!" +msgstr "" + +# f409e68056af43bd9e38d096103a3883 +#: ../../source/contributor/content-contributor.rst:48 +#: e10bea632a754c95866c6bafcf534ef5 +msgid "Improving documentation" +msgstr "" + +# 34eefffe7e794af4a56bd5ea20b11a78 +#: ../../source/contributor/content-contributor.rst:50 +#: 1a2de715719949d1b8bd8544a4273969 +msgid "" +"One of the most important parts of the Jupyter ecosystem is its " +"documentation. Good documentation makes it easier for users to learn how " +"to use the tools. It also makes it easier to teach others, and to " +"maintain and improve the code itself. There are many ways to improve " +"documentation, such as **reading tutorials and reporting confusing " +"parts**, **finding type-os and minor errors in docs**, **writing your own" +" guides and tutorials**, **improving docstrings within the code**, and " +"**improving documentation style and design**." +msgstr "" + +# 9e1b5f837c5544e0b1b10324e31869ae +#: ../../source/contributor/content-contributor.rst:57 +#: 82d07b7da37f4fac95d9291ebb49293b +msgid "" +"If you'd like to improve documentation in the Jupyter community, check " +"out the :ref:`documentation-guide`." +msgstr "" + +# 560230393e4349dd825bc8cb04bd85e8 +#: ../../source/contributor/content-contributor.rst:60 +#: af2fd69723b84962a3f6e31ac6a21b79 +msgid "Improving code" +msgstr "" + +# d630c52da53f4130862db11c2c4d45e6 +#: ../../source/contributor/content-contributor.rst:62 +#: a938252d3dda4c9f86baeb6b943ca272 +msgid "" +"There are many different codebases that make up the tools in the Jupyter " +"ecosystem. These are split across many repositories in several GitHub " +"organizations. They cover many different parts of interactive computing, " +"such as **user interfaces**, **kernels**, **shared infrastructure**, " +"**interactive widgets**, or **structured documents**." +msgstr "" + +# 904018e4262349c680f3e06291ab5284 +#: ../../source/contributor/content-contributor.rst:67 +#: b35bc9db2d424ca8b84f430cbe6ddd3d +msgid "" +"We recommend checking out the :ref:`developer-guide` for more information" +" about how you can find the right project to contribute to, and where to " +"go next." +msgstr "" + +# 25a6e078d67442a2ba84ead181c460b3 +#: ../../source/contributor/content-contributor.rst:71 +#: 9623c68739844896abeae2f25e841685 +msgid "Participating in the community" +msgstr "" + +# a87966fbbbd14c878db02da9489bce82 +#: ../../source/contributor/content-contributor.rst:73 +#: a65ea6a28a1647ceac35c3fae4af439d +msgid "" +"The most important part of Jupyter is its community - this is a large and" +" diverse group of people spread across the globe. One of the best ways to" +" contribute to Jupyter is to simply be a positive and helpful member of " +"this community. Whether it **participating in online conversations**, " +"**offering to help others**, **coming to community meetings**, or " +"**teaching others about Jupyter**, there are many ways to improve the " +"Jupyter community. For more information about this, we recommend starting" +" with the :ref:`community-guide`." +msgstr "" + +# 593c43f0e5764d01a171016560a00f00 +#: ../../source/contributor/contrib_guide_blog.rst:3 +#: 14568408f7a24fbb97b9613b10785e7f +msgid "Communications Guide" +msgstr "" + +# 1b294ad959f94bd3b8dba73f56642cb2 +#: ../../source/contributor/contrib_guide_blog.rst:6 +#: b07f24f4a0e74848bb59eb4516098595 +msgid "Contents" +msgstr "" + +# c6416f19a43d4ae1a19bb1f7b9888966 +#: ../../source/contributor/contrib_guide_blog.rst:9 +#: fbd42b2b5a6b4450bd4b1042260e544d +msgid "Blog" +msgstr "" + +# a9b5e28dfd994ef29cdf392ff8a36fba +#: ../../source/contributor/contrib_guide_blog.rst:11 +#: 75b5ccb9a4b74e2a9e0b95a42de154a3 +msgid "" +"We publish our blog at ``_. We welcome ideas " +"for posts or guest posts to the Jupyter blog. If you have a suggestion " +"for a future post, please feel free to share your idea with us. We would " +"like to discuss the idea with you." +msgstr "" + +# 12ff4c6ea66d445991bcadec7ba0b31f +#: ../../source/contributor/contrib_guide_blog.rst:16 +#: 4d580892bafa4a4c9aa66e34978c1875 +msgid "" +"Do you enjoy writing? Please contact us about becoming a guest blogger. " +"We can help guide you through the process of creating a post." +msgstr "" + +# b3be44427ae8472a8a215b6e33127cca +#: ../../source/contributor/contrib_guide_blog.rst:20 +#: 87284b5ccc2d4865886dcdc3272528fb +msgid "Technical overview" +msgstr "" + +# f09b1742f1744a83893baf77b9ff4ffc +#: ../../source/contributor/contrib_guide_blog.rst:22 +#: dcc4775e4c8d4f19b02b42b866b9ab50 +msgid "" +"Jupyter's blog uses the Ghost blog platform for its contributor " +"flexibility and ease of use. Jupyter's blog is deployed at " +"``_." +msgstr "" + +# 43151242cf8847c792841f97ae59e095 +#: ../../source/contributor/contrib_guide_blog.rst:26 +#: d15ca28ddb584863aa3de9c10d2c5581 +msgid "Basic workflow from blog idea to published post" +msgstr "" + +# 1be90c5561f143808cb47de0c8c8022a +#: ../../source/contributor/contrib_guide_blog.rst:28 +#: b884df34d75a4c3894fb69ce8443e1c0 +msgid "" +"There are several major steps in the workflow from blog idea to a " +"published post including:" +msgstr "" + +# 3c5ad2bb281a4aa6ac16b54a10dbdd1e +#: ../../source/contributor/contrib_guide_blog.rst:31 +#: d72ece46cb8c4cea9478a9270ffe9225 +msgid "Be inspired to write a post" +msgstr "" + +# 92a83a1a36a144c9ba2bcf30cc4da74b +#: ../../source/contributor/contrib_guide_blog.rst:32 +#: 25dd5e828bc14f3db74099f7c0da8dfb +msgid "" +"Send us a message on the Jupyter mailing list and ask us for an author " +"account on our blog" +msgstr "" + +# 1cd0cdf496bf4a71b38d89513c9351f6 +# c454ba131c7947f3b756d636a19e3d39 +#: ../../source/contributor/contrib_guide_blog.rst:33 +#: ../../source/contributor/contrib_guide_blog.rst:42 +#: 63a9a5a395f04b27bfe46a73e17c04ce d2deb25fe3634c24880489a7a57aa0f4 +msgid "Creating a draft" +msgstr "" + +# d60237d5d70c48e289be8db755f5488a +#: ../../source/contributor/contrib_guide_blog.rst:34 +#: 2cd9fda1c89a4076b409eb3a5dca3499 +msgid "Draft Review" +msgstr "" + +# 8e5bbd0595ae4f22abc31856f1b54c0d +# 7a67f5bd5e864a89bdde0121c28c83cb +#: ../../source/contributor/contrib_guide_blog.rst:35 +#: ../../source/contributor/contrib_guide_blog.rst:99 +#: 12d9c5bdfc8c472e9933d6688530de3a 84b34c348f49425abce902c6b0e8c8d1 +msgid "Editorial acceptance" +msgstr "" + +# 2a828f70ea3a42ebb52ab8fe17c58d83 +# 8ca1d1189f084c22a6513a9f7f370c3a +#: ../../source/contributor/contrib_guide_blog.rst:36 +#: ../../source/contributor/contrib_guide_blog.rst:102 +#: f27f7312245343dcb62381bfe940f4f1 fa85d075d9ce44a59436098a27de6c4c +msgid "Publishing the post" +msgstr "" + +# 205eccbcaafc4d1c87184fdfa20ea1e0 +#: ../../source/contributor/contrib_guide_blog.rst:38 +#: 2272d889e67e4a53b17b72a47356aa19 +msgid "" +"We'll cover each of these as well as how to update a post once it has " +"been published." +msgstr "" + +# bbeb420a823542ee9f81fb9a9d9e9a4b +#: ../../source/contributor/contrib_guide_blog.rst:45 +#: 62ddc6c7e083402dbee8631492dd3325 +msgid "Title and metadata" +msgstr "" + +# cb2170d8f32f40ab8ddb9dfe33eb88ec +#: ../../source/contributor/contrib_guide_blog.rst:47 +#: 427ff4b043874fa690c2859c8a9da814 +msgid "" +"Always check in the metadata fields that a blog post has a title and a " +"canonical URL. It is possible to put the date in the canonical URL, in " +"particular for events like jupyter-day, that can occur several times. The" +" date of the event can differ from the date of the blog post." +msgstr "" + +# 275b539c7a0b4de092e7cbf9b0d07286 +#: ../../source/contributor/contrib_guide_blog.rst:52 +#: b60d6964db594eb5be65f4fc84c4bcb4 +msgid "" +"Once a post is published, **never** change the post's title or the url. " +"These changes will break links of tweets and RSS feeds that have already " +"referenced the existing, published URL. Keep in mind that when publishing" +" some platforms cache the url immediately; as a result changing the title" +" will direct people to a 404 page." +msgstr "" + +# 7c80a8faf2824bd4a6a0a8848026e336 +#: ../../source/contributor/contrib_guide_blog.rst:58 +#: b31570201201470789f7ccadada8c108 +msgid "" +"Title and metadata can always be refined after the actual content of the " +"blog is written, but should not be changed after publication. As a guest " +"you do not have to worry about metadata, the editor or admins will take " +"care of that." +msgstr "" + +# af2b4dd47be8465d9f86f09e8f35a907 +#: ../../source/contributor/contrib_guide_blog.rst:63 +#: c4a0b56a1bcf42bc994cd6fbb07898d1 +msgid "Working with images" +msgstr "" + +# 1dd8d06687a24b8294060cc78eb07ad9 +#: ../../source/contributor/contrib_guide_blog.rst:65 +#: c13c39a39c2d48d385a9db51b3d56805 +msgid "" +"Try not to link to external images. If you want to put an image in the " +"post, insert ``![]()`` in the editor view and drag and drop an image from" +" your desktop into the newly created field in the preview. External " +"images can change, and can break the blog post if they are taken down. " +"This cannot append if you drag and drop images. Moreover, these images " +"will be served from the same CDN (Content Delivery Network) as the blog, " +"which will insure the best overall experience for our readers." +msgstr "" + +# ae794323faec447a81ebde34bfcd39a1 +#: ../../source/contributor/contrib_guide_blog.rst:73 +#: a388284d0b954d56a9c017ea43d2bf0d +msgid "" +"The featured image you see at the top of a blog posts is set from within " +"the metadata field, not using the `![]()`. The featured image is treated " +"differently than inlined images by many feedreaders (especially on " +"mobile) and allows a user on a slow connection to read the content of the" +" blog earlier, which is a much better experience for the user than " +"waiting for the featured image to render." +msgstr "" + +# f8a4d5c3b90a4f598984c027f2b56f71 +#: ../../source/contributor/contrib_guide_blog.rst:80 +#: a111096b25c94235970048bc28268e99 +msgid "Links" +msgstr "" + +# 5a9171fe32504c848544ef93477c13e0 +#: ../../source/contributor/contrib_guide_blog.rst:82 +#: 9efb938b708b4405a94c56e67422b94a +msgid "" +"Do not use minified links when possible. The multiple redirects of " +"minified links degrades the mobile browsing experience. If you need " +"analytics of the number of page views, this information is tracked by " +"Google Analytics." +msgstr "" + +# 36175d5a99a4463b9397b07b190925e3 +#: ../../source/contributor/contrib_guide_blog.rst:87 +#: c8d346a10df04658bec2a1b02d6db472 +msgid "Draft review" +msgstr "" + +# 0b8e6790a0ea441c828238f2a79a627c +#: ../../source/contributor/contrib_guide_blog.rst:90 +#: dda1a3dfc8754017af23000ab7eef0af +msgid "Ask for a review" +msgstr "" + +# 3db41a20769540a18283ea37c44900b2 +#: ../../source/contributor/contrib_guide_blog.rst:92 +#: 984e3f9533704b0eaa6a1a85b58114bc +msgid "" +"Once you think you are done, ask someone else to reread your post, and " +"check the various parameters that you might have forgotten before " +"publishing. You are not on your own, this is teamwork, we are here to " +"help you. If we do things in a hurry you will probably spend more time " +"fixing mistakes that actually doing things right in a first place." +msgstr "" + +# 95365105a2e44a7d818b9f47b05853dc +#: ../../source/contributor/contrib_guide_blog.rst:104 +#: 0dda5f5f2f1b48c79ca21cc6cee6e2ee +msgid "" +"Usually an editor or admin will take care of publishing the post. The " +"task of the Editor/Admin is to check all metadata are correctly set, that" +" no external images are used, as well as all other quality check describe" +" before." +msgstr "" + +# 809dc486262e437ebb95ce53542c0b79 +#: ../../source/contributor/contrib_guide_blog.rst:108 +#: 8e357ec4ca414eb8ae3688435132db51 +msgid "It is then just a matter of making th post visible to everyone." +msgstr "" + +# 0b9fd999238245dca7a574888ca974b5 +#: ../../source/contributor/contrib_guide_blog.rst:111 +#: 0291e2d7a89f4cdea2be7b0837c9a949 +msgid "Changing an existing post" +msgstr "" + +# f7eb7e6e67924638b9fd1079ca1fd4be +#: ../../source/contributor/contrib_guide_blog.rst:114 +#: 0984200e22494815b10a26b1ffa7a6fe +msgid "Posts Updates" +msgstr "" + +# eee44374b12542d9b54cb3618fd3e868 +#: ../../source/contributor/contrib_guide_blog.rst:116 +#: 31bf62378ed24aaa8590a974fcaf095b +msgid "" +"Blog subscribers may receive notification at every update. So use updates" +" and fixes parsimoniously. It is OK to wait a few hours to fix a typo." +msgstr "" + +# ab638c99ec3c460abfaad8d60a1e8800 +#: ../../source/contributor/contrib_guide_blog.rst:119 +#: d0552763a6c041b69a3ce6d37f92ef8e +msgid "" +"If some substantial updates have to be made, like change of location, " +"time etc, please insert an `[Update]` section at top (or bottom of the " +"blog post depending on importance) with the Date/Time of the update. If " +"the information in the body of the blog is wrong, try not to replace it, " +"and just use strike-through to mark it as obsolete. This would help " +"reader determine which information is correct when dealing with multiple " +"source giving different information." +msgstr "" + +# 5fa61a2b985e43aa94c3cc695b08eed1 +#: ../../source/contributor/contrib_guide_blog.rst:128 +#: d06f0076e60e4d1b88c1750c6066ff3f +msgid "Newsletter" +msgstr "" + +# 5122c3d734f24dbdb2f00e9731a31a27 +# 424ebb5fc17844658e7b83d9209374ce +#: ../../source/contributor/contrib_guide_blog.rst:130 +#: ../../source/contributor/contrib_guide_blog.rst:136 +#: 589199db34b04f4c9f624d8d8ea5cbf3 e3c4f8c2796c4d05b01b8ef3c6856b37 +msgid "Documentation in progress." +msgstr "" + +# 174fa91d9686461fa8f40c348d73dda3 +#: ../../source/contributor/contrib_guide_blog.rst:134 +#: f3c2a87a3408474e874df7d84853eaad +msgid "Website" +msgstr "" + +# 621a2e3dd84a4243839c3502e29814d9 +#~ msgid "Contributor Guides" +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/developer-docs.po b/docs/source/locale/en/LC_MESSAGES/developer-docs.po new file mode 100644 index 000000000..83bf27958 --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/developer-docs.po @@ -0,0 +1,1163 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-06-11 23:18+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.8.0\n" + +# 4af9f71750c8467e8467b4e5c923c079 +#: ../../source/developer-docs/contrib_first_time.rst:3 +#: 2f873cf70b6b4a2380ab3823ac9987a7 +msgid "Contributing for the First Time" +msgstr "" + +# 856e1ce30fea448ebafd494bce7435e0 +# a1a8768c3922479fa3bb8f7c8ec19d78 +#: ../../source/developer-docs/contrib_first_time.rst:6 +#: ../../source/developer-docs/contrib_guide_code.rst:6 +#: 456761904f9c45bbac461af20321d672 e25761d52bc84616abe71be4fa242c95 +msgid "Contents" +msgstr "" + +# b75b7e5e93d443999da00800903a098c +#: ../../source/developer-docs/contrib_first_time.rst:8 +#: 2aecaab7a74a4a1aa2dc9c6518cddbfe +msgid "Welcome fellow contributor! We appreciate your help." +msgstr "" + +# feac7eb012a841038cfec4c31f26db07 +#: ../../source/developer-docs/contrib_first_time.rst:10 +#: 4dc6f0e8ef894b06a6498851c10110b4 +msgid "" +"We typically label issues appropriate for new contributors as ``good " +"first issue`` or ``help wanted``. To start an issue, you may comment to " +"let everyone know that you'll be working on it. Our repos typically " +"provide development installation instructions in each repo's " +"``CONTRIBUTING.md`` or ``README.md``. **Should you find an issue with our" +" development installation instructions please let us know in our " +"issues.** We want to ensure that our documentation for development " +"installation is accurate. Additionally, other contributors are often " +"available to answer questions about fixing the issue on the issue number " +"or on the repo's gitter channel." +msgstr "" + +# ee56c9c218734eb89634ced64adc7089 +#: ../../source/developer-docs/contrib_first_time.rst:20 +#: 49860a1c417f4f1fb27545280c2b00aa +msgid "" +"We strive to have a inclusive, welcoming community. Please read our " +"`code of conduct " +"`__" +" to learn more." +msgstr "" + +# fd7a319af3e449b6861b2d74e4e1c8cb +#: ../../source/developer-docs/contrib_first_time.rst:25 +#: 9125466d766241c899429977af3411f4 +msgid "Major Repos and Issue Types" +msgstr "" + +# fa17d1bbc25c469c8aa8e05eeeef1cca +#: ../../source/developer-docs/contrib_first_time.rst:28 +#: 7ac785c3639547a2a769370e806c0935 +msgid "Python" +msgstr "" + +# cd8ab1883a03446b91db2f5d1f7c13db +#: ../../source/developer-docs/contrib_first_time.rst:30 +#: e3fac126ad064c0c9ebd2063195c8713 +msgid "" +"IPython, nbgrader, JupyterHub, repo2docker, and Binder are major repos " +"written primarily in Python." +msgstr "" + +# 13e25fb7dc4c4715abc0394881b6e0f7 +#: ../../source/developer-docs/contrib_first_time.rst:34 +#: 6fec8efb7cd248c18fb10217e4824d37 +msgid "`IPython `__" +msgstr "" + +# c2da4aae25e4412a911d495ddecf8495 +#: ../../source/developer-docs/contrib_first_time.rst:33 +#: 298828bf9c0c4010a87be1bfac7cf290 +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +# c5ee2f00454c418ab40ddb37f145b04f +#: ../../source/developer-docs/contrib_first_time.rst:34 +#: d501dc6c9a9741099392014043766230 +msgid "" +"`Development Installation `__" +msgstr "" + +# d4df3d9d6a3a4a69b57ea417354f7e43 +#: ../../source/developer-docs/contrib_first_time.rst:35 +#: c62eed373b994b09bda430f6a73c9525 +msgid "`Gitter Channel `__" +msgstr "" + +# eb0579bf78894f9dbf75c8786657adb2 +#: ../../source/developer-docs/contrib_first_time.rst:37 +#: a8e7a94ec1e44677a5714b2f828190ac +msgid "`nbgrader `__" +msgstr "" + +# 4dbe9d98a5b04f3c97d6e3fcb5ac9c95 +#: ../../source/developer-docs/contrib_first_time.rst:37 +#: e218a41342f94fd7bfb8e6346e663d6a +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +# 831273b724474075be7ed229e8f7f7e0 +#: ../../source/developer-docs/contrib_first_time.rst:38 +#: f54c52e3594f4ed482c554801ca274e8 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +# d97b92c244d243088ab12928e87d6df7 +#: ../../source/developer-docs/contrib_first_time.rst:41 +#: 2722e998a3d3434fa9beb998a903a418 +msgid "`JupyterHub `__" +msgstr "" + +# 387d54bdacca494fbb48fe045047ad3b +#: ../../source/developer-docs/contrib_first_time.rst:40 +#: 5200d347a6aa4e98b9c85fe752c87a64 +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +# 103323470924458c96863a2956b18934 +#: ../../source/developer-docs/contrib_first_time.rst:41 +#: 5c8f83bfcf2c4fd19930e2cdaa029e21 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +# b060a9da9d1341a4b1bb023eb4a2a514 +# 971d63207aa04f5a8f60aefcf4af75fa +#: ../../source/developer-docs/contrib_first_time.rst:42 +#: ../../source/developer-docs/contrib_first_time.rst:46 +#: 06d2f499f6bb4d38bba36651f9b285b5 0e441c87aece432a8640b6a3c9ad3f13 +msgid "`Gitter Channel `__" +msgstr "" + +# c587dbe34ebf447e8ff83ec285a05cc4 +#: ../../source/developer-docs/contrib_first_time.rst:45 +#: bcec31523d7d481492f4934d115d613c +msgid "`repo2docker `__" +msgstr "" + +# 52bedabdb3b040e895cb1ca8f80d6041 +#: ../../source/developer-docs/contrib_first_time.rst:44 +#: 191f7a40297149b1a9a7c7630d62d098 +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +# 2f57686e120c44d695178d92b790da17 +#: ../../source/developer-docs/contrib_first_time.rst:45 +#: 442c2b61fb534bf69e012383cc6926a5 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +# 8d289dfea18048199cea959342abb58c +#: ../../source/developer-docs/contrib_first_time.rst:50 +#: 0ffa46d176f04b8f912f4d10138e383d +msgid "`Binder `__" +msgstr "" + +# 5857637ca0fd49e9808958dd94156769 +#: ../../source/developer-docs/contrib_first_time.rst:48 +#: 00e36141da8f4a89a2ee479346f6956a +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +# 782632da47684ce8a213946114dc86ed +#: ../../source/developer-docs/contrib_first_time.rst:49 +#: 755bdbd5dd244ddfa8e6ac4e2f3bed71 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +# 92bddf6026f94077b2f368e02315c5f9 +#: ../../source/developer-docs/contrib_first_time.rst:50 +#: 672509213bbe48258811dc5dfda26f59 +msgid "`Gitter Channel `__" +msgstr "" + +# 9b380cabc14b47179027d99a76fb7b8b +#: ../../source/developer-docs/contrib_first_time.rst:53 +#: b1e54f0ff6b74f75b9dbff9c4179b52b +msgid "Documentation" +msgstr "" + +# ad4855a98345426b8ff5b1012d31ccfe +#: ../../source/developer-docs/contrib_first_time.rst:55 +#: 42e92d67323848ffa0d20bcd12d7e730 +msgid "" +"All our repos have documentation issues that are relevant for new " +"contributors. For example, the source for the documentation you are " +"reading right now can be found in the `jupyter/jupyter repository on " +"GitHub `__." +msgstr "" + +# fb1acce4f0464fb583a61010ade7e13f +#: ../../source/developer-docs/contrib_first_time.rst:59 +#: 4ac8dad137d24ac39b8e580b64ada9c3 +msgid "JavaScript/TypeScript" +msgstr "" + +# d17b947479924673b44d5e34dba895af +#: ../../source/developer-docs/contrib_first_time.rst:61 +#: c0e6cb8913a342c2afe5f16950b5410e +msgid "" +"Jupyter Notebook, JupyterLab, and IPyWidgets use JavaScript and " +"TypeScript." +msgstr "" + +# e73febabcbe341d4ab5cd9062fe95128 +#: ../../source/developer-docs/contrib_first_time.rst:65 +#: f1a0a3d20bcc4a1ca42757d540e81482 +msgid "`Jupyter Notebook `__" +msgstr "" + +# 4fe96e2afbc140c8852dac6daa01b3fa +#: ../../source/developer-docs/contrib_first_time.rst:64 +#: 290b57d4f3a44d138b4a3b8460efed59 +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +# 67ec729c38dd4eb4afc774c99aad3512 +#: ../../source/developer-docs/contrib_first_time.rst:65 +#: 84351102512c436cae5c173424805630 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +# eacc49d0d4e046309c208bceab13b8cc +#: ../../source/developer-docs/contrib_first_time.rst:66 +#: 92779fa439c041c2b4ed5ce989842aaa +msgid "`Gitter Channel `__" +msgstr "" + +# 15087cd5dd224b8a882fad3d6db3085b +#: ../../source/developer-docs/contrib_first_time.rst:69 +#: 35b69425b9434f11b3b4c5cb2fe51402 +msgid "`JupyterLab `__" +msgstr "" + +# 87259f462bfe4ba692e18e59633251a5 +#: ../../source/developer-docs/contrib_first_time.rst:68 +#: 8b68caf2b9ca4e998fc1a4bbaefc4b4e +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +# 60727430accc47a59bdb9fd7c0dc9d10 +#: ../../source/developer-docs/contrib_first_time.rst:69 +#: 2f71734a4b594ecda46992a62d28ad23 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +# 889f6bb437974cbf98d5bc40c912e0b4 +#: ../../source/developer-docs/contrib_first_time.rst:70 +#: f9744aa169a24b9aaec0efc451cc3d8b +msgid "`Gitter Channel `__" +msgstr "" + +# e810bd44e3374585a51bf791e155e821 +#: ../../source/developer-docs/contrib_first_time.rst:74 +#: 700c7bde67ae46b4b2a69a7ffdd39e5c +msgid "`IPyWidgets `__" +msgstr "" + +# 27cd0846c54e44769e1ca07e09612753 +#: ../../source/developer-docs/contrib_first_time.rst:72 +#: 9006dba8667e47e4b10d36e2987f412e +#, python-format +msgid "" +"`Notable Issues `__" +msgstr "" + +# b2ed815f0f484e68a121c164065199df +#: ../../source/developer-docs/contrib_first_time.rst:73 +#: 335df1b56add43bc87dc22523aa11774 +msgid "" +"`Development Installation " +"`__" +msgstr "" + +# 72cbadaa4c3941bdb2196021192afe8c +#: ../../source/developer-docs/contrib_first_time.rst:74 +#: 5cc9e0dcff44403586113bb20689e87b +msgid "`Gitter Channel `__" +msgstr "" + +# 540681780cc14e65925a8c0e9aad0405 +#: ../../source/developer-docs/contrib_first_time.rst:77 +#: 6e5eddd4c28048e882c1e5ba54cc4b9b +msgid "DevOps" +msgstr "" + +# 4b08f960f4e941e2b3aa717d7edca63b +#: ../../source/developer-docs/contrib_first_time.rst:79 +#: 96832e6572134c7f8f874a4223b40706 +msgid "" +"JupyterHub, repo2docker, and Binder have many issues related to devops. " +"See the links above." +msgstr "" + +# c0634775654042c2ad49c3d398f14230 +#: ../../source/developer-docs/contrib_first_time.rst:82 +#: 4cb1e4b89f044090a04ac56fc4b3977c +msgid "Web Development" +msgstr "" + +# 2920f2549f3c4ca5a27867664fd04def +#: ../../source/developer-docs/contrib_first_time.rst:84 +#: 2bbb6cb2d9aa42018a0537aacf6136b7 +msgid "We have issues related to the website." +msgstr "" + +# 34830e753b7042d59da52a4bb2415161 +#: ../../source/developer-docs/contrib_first_time.rst:87 +#: c628e331836b4d3395a5ac9655071063 +msgid "" +"`Project Jupyter's Website " +"`__" +msgstr "" + +# d7b47f8c88964db889f77041e5e579ec +#: ../../source/developer-docs/contrib_first_time.rst:87 +#: b0610a0b8f2241be92e62b4f120dce42 +#, python-format +msgid "" +"`Notable Issues " +"`__" +msgstr "" + +# 2192a69a3d2f42008d5632996da49b7f +#: ../../source/developer-docs/contrib_first_time.rst:88 +#: 3871dad784c74f3d9ee756283757a990 +msgid "" +"`Developer Installation `__" +msgstr "" + +# 0485183fb72344cf959bce1ba5420bd6 +#: ../../source/developer-docs/contrib_guide_bugs_enh.rst:3 +#: d3b50a33f52247b9bedc4303a4f2fa5b +msgid "Submitting a Bug" +msgstr "" + +# af25f25c2cec41d8831b2e67c2a3e69c +#: ../../source/developer-docs/contrib_guide_bugs_enh.rst:4 +#: bc6648be670d4ca789e78902a4b1ec7f +msgid "" +"While using the Notebook, you might experience a bug that manifests " +"itself in unexpected behavior. If so, we encourage you to open issues " +"on GitHub. To make the navigating issues easier for both developers and " +"users, we ask that you take the following steps before submitting an " +"issue." +msgstr "" + +# 139a72d8dfdb45cf90edf3e35aec0059 +#: ../../source/developer-docs/contrib_guide_bugs_enh.rst:9 +#: 8d818111f5d04eb9846729a579ac2548 +msgid "" +"Search through StackOverflow and existing GitHub issues to ensure that " +"the issue has not already been reported by another user. If so, provide " +"your input on the existing issue if you think it would be valuable." +msgstr "" + +# cccad08769f44e52a04a90cbe76e2223 +#: ../../source/developer-docs/contrib_guide_bugs_enh.rst:13 +#: 44be980978ad4aca8e086dfe9e858b7b +msgid "" +"Prepare a small, self-contained snippet of code that will allow others to" +" reproduce the issue that you are experiencing." +msgstr "" + +# c3a86b1233534248bb19fa1c1b09bd9d +#: ../../source/developer-docs/contrib_guide_bugs_enh.rst:16 +#: d11b508764f94597a4a513924109efe9 +msgid "" +"Prepare information about the environment that you are executing the code" +" in, in order to aid in the debugging of the issue. You will need to " +"provide information about the Python version, Jupyter version, operating " +"system, and browser that you are using when submitting bugs. You can also" +" use ``pip list`` or ``conda list`` and ``grep`` in order to identify " +"the versions of the libraries that are relevant to the issue that you are" +" submitting." +msgstr "" + +# b4302021c41448839eae6dca5b34a39e +#: ../../source/developer-docs/contrib_guide_bugs_enh.rst:24 +#: 8c6b7dcfcf334a09a85e2fffc14abb4d +msgid "" +"Prepare a simple test that outlines the expected behavior of the code or " +"a description of the what the expected behavior should be." +msgstr "" + +# 47c214b9890f43c599c9bf0b8c6e0582 +#: ../../source/developer-docs/contrib_guide_bugs_enh.rst:27 +#: 18556085df794d539866e5fe22789d4e +msgid "" +"Prepare an explanation of why the current behavior is not desired and " +"what it should be." +msgstr "" + +# 971e73dd85a54bf9b588dad72b000207 +# fcc463f334c9426abb8e84b007b2f6cd +#: ../../source/developer-docs/contrib_guide_code.rst:3 +#: ../../source/developer-docs/index.rst:5 2fac60e39330417996dd48f1648b496f +#: c5636822f5bc464b86467a4362716e55 +msgid "Developer Guide" +msgstr "" + +# 7c5e21c9bdad4985aeab19c9c6a7af56 +#: ../../source/developer-docs/contrib_guide_code.rst:9 +#: 0617023f333c4627b630a7111583cc66 +msgid "A Note on Contributing to Open Source" +msgstr "" + +# b4b9389d3154437ba7df6c08d95bffb4 +#: ../../source/developer-docs/contrib_guide_code.rst:11 +#: d0e94890148142e0b2347af1b14dd597 +msgid "" +"Contributing to open source can be a nerve-wrecking process, but don't " +"worry everyone on the Jupyter team is dedicated to making sure that your " +"open source experience is as fun as possible. At any time during the " +"process described below, you can reach out to the Jupyter team on Gitter " +"or the mailing list for assistance. If you are nervous about asking " +"questions in public, you can also reach out to one of the Jupyter " +"developers in private. You can use the public Gitter to find someone who " +"has the best knowledge about the code you are working with and interact " +"with the in a personal chat." +msgstr "" + +# cc89b39165a446e5b87c4f9266495c26 +#: ../../source/developer-docs/contrib_guide_code.rst:20 +#: 439012f53d9d474ebbb53f966d93fd76 +msgid "" +"As you begin your open source journey, remember that it's OK if you don't" +" understand something, it's OK to make mistakes, and it's OK to only " +"contribute a small amount of the code necessary to fix the issue you are " +"tackling. Any and all help is welcome and any and all people are " +"encouraged to contribute." +msgstr "" + +# 641608cfd0864941a223bf39b6a0b4ce +#: ../../source/developer-docs/contrib_guide_code.rst:26 +#: 5133a05720fe46aa84f8261fe19b4dfc +msgid "How can I help?" +msgstr "" + +# a37196b3fb6a4df1870786ea3235406a +#: ../../source/developer-docs/contrib_guide_code.rst:28 +#: 9ba58432d6eb4ddc983087fdc34e103a +msgid "" +"Individuals are welcome, and encouraged, to submit pull requests and " +"contribute to the Jupyter source. If you are a first-time contributor " +"looking to get involved with Jupyter, you can use the following query in " +"a GitHub search to find beginner-friendly issues to tackle across the " +"Jupyter codebase. This query is particularly useful because the Jupyter " +"codebase is scattered across several repositories within the jupyter " +"organization, as opposed to a single repository. You can click the link " +"below to find sprint-friendly issues." +msgstr "" + +# 1eee498a843146fab2ef3b1e9317a7b3 +#: ../../source/developer-docs/contrib_guide_code.rst:36 +#: 87e8c4192e714fe0836b40562e22bd01 +msgid "" +"`is:issue is:open is:sprint-friendly user:jupyter " +"`_" +msgstr "" + +# e2e8942ce25f4d44a4dc7cc2e67730b5 +#: ../../source/developer-docs/contrib_guide_code.rst:39 +#: 3915d1d46efc4af4936b09a2b8b0883f +msgid "" +"Once you've found an issue that you are eager to solve, you can use the " +"guide below to get started. If you experience any problems while working " +"on the issue, leave a comment on the issue page in GitHub and someone on " +"the core team will be able to lend you assistance." +msgstr "" + +# df6093a6a72247089f0024bcb798dcbc +#: ../../source/developer-docs/contrib_guide_code.rst:44 +#: f709c29305a64969a453adfcfc990f40 +msgid "" +"Please keep in mind that what follows are guidelines. If you work through" +" the steps and have questions or run into time constraints, please submit" +" what you already have worked on as a pull request and ask questions on " +"it. Your effort, including partial or in-progress work, is appreciated." +msgstr "" + +# b3e3eb75571744d1b15d0d7f1bec2c13 +#: ../../source/developer-docs/contrib_guide_code.rst:49 +#: a3c9bada68a84f11ab0c4bb1dc2614f5 +msgid "" +"Fork the repository associated with the issue you are addressing and " +"clone it to a local directory on your machine." +msgstr "" + +# d4a40f6de2d243dc8f4c188d4bccb987 +#: ../../source/developer-docs/contrib_guide_code.rst:52 +#: 823b9b5d1d694e808295a616d112e063 +msgid "" +"``cd`` into the directory and create a new branch using ``git checkout -b" +" insert-branch-name-here``. Pick a branch name that gives some insight " +"into what the issue you are fixing is. For example, if you are updating " +"the text that is logged out by the program when a certain error happens " +"you might name your branch `update-error-text`." +msgstr "" + +# 022300380d634dca91632205f9c0c3b8 +#: ../../source/developer-docs/contrib_guide_code.rst:58 +#: 5c82b62c93414bb695d810aea69de9d5 +msgid "" +"Refer to the repository's README and documentation for details on " +"configuring your system for development." +msgstr "" + +# b294af0b7be547ae948f435194728ad6 +#: ../../source/developer-docs/contrib_guide_code.rst:61 +#: d8c0073a6f5f410983fcc724b67561b0 +msgid "" +"Identify the module or class where the code change you will make will " +"reside and leave a comment in the file describing what issue you are " +"trying to address." +msgstr "" + +# 3da7f1d0ab7249f893554f57520c67e6 +#: ../../source/developer-docs/contrib_guide_code.rst:65 +#: 726eebb773e540e0ae5c1ad8d346ea29 +msgid "" +"Open a pull request to the repository with ``[WIP]`` appended to the " +"front so that the core team is aware that you are actively pursuing the " +"issue. When creating a pull request, make sure that the title clearly and" +" concisely described what your code does. For example, we might use the " +"title \"Updated error message on ExampleException\". In the body of the " +"pull request, make sure that you include the phrase \"Closes #issue-" +"number-here\", where the issue number is the issue number of the issue " +"that you are addressing in this PR." +msgstr "" + +# 8a1d4bda15d54f63b755268e0ee3f928 +#: ../../source/developer-docs/contrib_guide_code.rst:74 +#: e93c2b52aab14084b0bf7bd7b0f0c178 +msgid "" +"Feel free to open a PR as early as possible. Getting early feedback on " +"your approach will save you time and prevent the need for an extensive " +"refactor later." +msgstr "" + +# 933a91389b064d329ba443dc8b4aac48 +#: ../../source/developer-docs/contrib_guide_code.rst:78 +#: d60a3343b89d419c9b1321a72e04081a +msgid "" +"Run the test suite locally in order to ensure that everything is properly" +" configured on your system. Refer to the repository's README for " +"information on how to run the test suite. This will typically require " +"that you run the ``nosetests`` command on the commandline. Alternatively," +" you may submit a pull request. Our Continuous Integration system will " +"test your code and report test results." +msgstr "" + +# 4940b5b766d34b728500b8ee01b00a2e +#: ../../source/developer-docs/contrib_guide_code.rst:85 +#: 77db1fa78d7a4be29dbcd6b1942f8468 +msgid "" +"Find the test file associated with the module that you will be changing. " +"In the test file, add some tests that outline what you expect the " +"behavior of the change should be. If we continue with our example of " +"updating the text that is logged on error, we might write test cases that" +" check to see if the exception raised when you induce the error contains " +"the appropriate string. When writing test cases, make sure that you test " +"for the following things." +msgstr "" + +# 190f4f31714c4eebbb80f054ed3b9ede +#: ../../source/developer-docs/contrib_guide_code.rst:93 +#: cf02fd5882ca48a2b608aad4245c58f6 +msgid "What is the simplest test case I can write for this issue?" +msgstr "" + +# bf18ca96f21e40d0a07cfa24d3f83ebb +#: ../../source/developer-docs/contrib_guide_code.rst:94 +#: ee6f586f8778479e85d83168f6793d58 +msgid "What will happen if your code is given messy inputs?" +msgstr "" + +# 5e238f0155c44fc198bbe03b5eb52072 +#: ../../source/developer-docs/contrib_guide_code.rst:95 +#: 7578683b17e74f9981d4ae6b0cd52c6a +msgid "What will happen if your code is given no inputs?" +msgstr "" + +# f642285810ad4b74996365fabf4a36bc +#: ../../source/developer-docs/contrib_guide_code.rst:96 +#: 93eadc3bf10a413b93dbf328c84c3b4b +msgid "What will happen if your code is given too few inputs?" +msgstr "" + +# fc7c95470d5c47d1a1c642101f0f128a +#: ../../source/developer-docs/contrib_guide_code.rst:97 +#: 48b117a8780640f983cd4d9492d3d78c +msgid "What will happen if your code is given too many inputs?" +msgstr "" + +# 1512fa1ef2674eb7b4fd8e0cffb9ea34 +#: ../../source/developer-docs/contrib_guide_code.rst:99 +#: 11ff1be3adb8417aa55a2f510715a34b +msgid "" +"If you need assistance writing test cases, you can place a comment on the" +" pull request that was opened earlier and one of the core team members " +"will be able to help you." +msgstr "" + +# 8ef9e5734a364dc2988978fbf5c1f717 +#: ../../source/developer-docs/contrib_guide_code.rst:103 +#: 617702aed0da4e69a9f283f463689b9e +msgid "" +"Go back to the file that you are updating and begin adding the code for " +"your pull request." +msgstr "" + +# 10fd03dbbce04657995fe36c868333db +#: ../../source/developer-docs/contrib_guide_code.rst:106 +#: 3ce6de194ae64affb677e6cd0310647b +msgid "" +"Run the test suite again to see if your changes have caused any of the " +"test cases to pass. If any of the test cases have failed, go back to your" +" code and make the updates necessary to have them pass." +msgstr "" + +# c8d1e89343e246daa2cdc22cdeb2611d +#: ../../source/developer-docs/contrib_guide_code.rst:110 +#: 36e5c63fc97e4694b3cd44484de05de0 +msgid "" +"Once all of your test cases have passed, commit both the test cases and " +"the updated module and push the updates to the branch on your forked " +"repository." +msgstr "" + +# 87111861fffe4a49a87827323e112ce7 +#: ../../source/developer-docs/contrib_guide_code.rst:113 +#: 46a9b39b7de147bf82aeb1543348abbf +msgid "" +"Once you are ready for your pull request to be reviewed, remove the [WIP]" +" tag from the front of issue, a project reviewer will review your code " +"for quality. You can expect the reviewer to check for the documentation " +"provided in the changes you made, how thorough the test cases you " +"provided are, and how efficient your code is. Your reviewer will provide " +"feedback on your code and you will have the chance to edit your code and " +"apply fixes." +msgstr "" + +# 5f6e2c2d4cc74b1686fec2915006f366 +#: ../../source/developer-docs/contrib_guide_code.rst:120 +#: 9c118a683f334ce69efb69eb35eb1f3c +msgid "" +"Once your PR is ready to become a part of the code base, it will be " +"merged by a member of the core team." +msgstr "" + +# 0b6fc432cbc7440aa4365d35fe0e7533 +#: ../../source/developer-docs/contrib_guide_code.rst:124 +#: 3f00a4a7c5ae4949b7220ee330865f81 +msgid "Contribution Workflow" +msgstr "" + +# 9869fb16c17e4a2dbe7e220f2099e7a4 +#: ../../source/developer-docs/contrib_guide_code.rst:130 +#: 2905f6990a2348e7b8bd876318de197a +msgid "Core Developer Workflow" +msgstr "" + +# d88b2538fa7c4b65a87600628a3190fa +#: ../../source/developer-docs/contrib_guide_code.rst:132 +#: 3693de73634f4d0b8441112dad9f6ef1 +msgid "" +"To help you understand our review process by core developers after you " +"submit a pull request, here's a guide that outlines the general process " +"(specifics may vary a bit across our repositories). Here is an example " +"for Jupyter notebook 4.x:" +msgstr "" + +# 6afb4060cab3492f8185187faada55b2 +#: ../../source/developer-docs/contrib_guide_code.rst:139 +#: c5c5430701664e119af80c17054f2bd5 +msgid "" +"In general, Pull Requests are against ``master`` unless they only affect " +"a backport branch. If a PR affects master and should be backported, the " +"general flow is:" +msgstr "" + +# 3b5bfc37063a4062a301ee23411528c0 +#: ../../source/developer-docs/contrib_guide_code.rst:143 +#: a6fc986c63834e33b39b45afa1da3b97 +msgid "mark the PR with milestone for the next backport release (4.3)" +msgstr "" + +# c42e3f791f6d4cc38b4fb9ac0eec129a +#: ../../source/developer-docs/contrib_guide_code.rst:144 +#: 0b31bb92d27a4c6f905c21a00134e2fa +msgid "merge into master" +msgstr "" + +# 018cd8318aef471484dc9184b43973c3 +#: ../../source/developer-docs/contrib_guide_code.rst:145 +#: 79374d9a40e2449c81d0f326a1b0148c +msgid "backport to 4.x" +msgstr "" + +# 7b28314df8154e5b8606b722f4d73856 +#: ../../source/developer-docs/contrib_guide_code.rst:146 +#: a7efc6c8aaec4ee4ad765bdb5658a738 +msgid "push updated 4.x branch" +msgstr "" + +# 10d9ca0afcf8439aac13eba4c1f428db +#: ../../source/developer-docs/contrib_guide_code.rst:148 +#: 912c7d44298346a9808eec5a502aa03f +msgid "" +"Backports can be done in a variety of ways, but we have `a script " +"`_ " +"for automating the common process to:" +msgstr "" + +# 370a6eafee694f6ca5d7753ca3ef1962 +#: ../../source/developer-docs/contrib_guide_code.rst:152 +#: ae5ef3a2f82443cc9e11afb8100e3039 +msgid "" +"download the patch ` e.g. `" +msgstr "" + +# 1964c880516c43f99cbf34dadca2bdf1 +#: ../../source/developer-docs/contrib_guide_code.rst:153 +#: 83520f0c79f64723b357ec8c3fc18d4a +msgid "checkout the 4.x branch" +msgstr "" + +# 70cb7a619981417393a3e1be5e661492 +#: ../../source/developer-docs/contrib_guide_code.rst:154 +#: e6431b1a514b49f69db983a321e1cf04 +msgid "apply the patch" +msgstr "" + +# 1d6c472ef4e34a87ba54dd61299b1607 +#: ../../source/developer-docs/contrib_guide_code.rst:155 +#: 6bc69122db5d455690120b460697dde4 +msgid "make a commit" +msgstr "" + +# bcc8acbb2663447fb1abece94d18a145 +#: ../../source/developer-docs/contrib_guide_code.rst:157 +#: 0825e762e24d46c19562d1a185a62e74 +msgid "which works for simple cases, at least." +msgstr "" + +# 481646fca06049c39c7ccc2c7dfb000d +#: ../../source/developer-docs/contrib_guide_code.rst:159 +#: 4bf69891969840fb8009c505c7df0d6c +msgid "In this case, it would be:" +msgstr "" + +# 871218e69ea840f6a710fffda0f59255 +#: ../../source/developer-docs/contrib_guide_code.rst:161 +#: 4d41410cba874761bf51b3c6e75d89fa +msgid "" +"python /path/to/ipython-repo/tools/backport_pr.py jupyter/notebook 4.x " +"1645" +msgstr "" + +# 59008b88919d4084b6e7278a762249be +#: ../../source/developer-docs/contrib_guide_vuln.rst:3 +#: c389466a7a0745108a19e8eb613ce0e6 +msgid "Reporting a Vulnerability" +msgstr "" + +#: ../../source/developer-docs/contrib_guide_vuln.rst:5 +#: e63ad362513746f8adff9fc9105812e3 +msgid "" +"If you believe you've found a security vulnerability in a Jupyter " +"project, please report it to `security@ipython.org " +"`_. If you prefer to encrypt your security " +"reports, you can use `this PGP public key `_." +msgstr "" + +# c52d228e243243108261b278ecd95e9b +#: ../../source/developer-docs/index.rst:7 e7d1c075e7834fbd9b84c0db863a518a +msgid "**Contents**" +msgstr "" + +# 1dc0b8ea396a43d29a89a7917b0c918c +#: ../../source/developer-docs/index.rst:20 f63a3db6014448259d94a08766d2d022 +msgid "" +"Whether you are a new contributor or a seasoned developer, we're pleased " +"that you are working on Jupyter. We hope you find the Developer Guide is " +"useful. Please suggest changes or ask questions about the contents. " +"Thanks!" +msgstr "" + +# ab19140a7ecf4481a9c8de4115df0760 +#: ../../source/developer-docs/index.rst:24 bfd8b848f03840178f48ee4e3a4a5222 +msgid "" +"If you are interested in installing a specific project from source, each " +"project has documentation on ReadTheDocs. For example, IPython " +"documentation can be found on `ReadTheDocs " +"`_. Most of our packages can be installed from " +"the source directory like any other Python package, by running:" +msgstr "" + +#: ../../source/developer-docs/index.rst:34 227b80e053904f2da5ec97ae99cfb6ca +msgid "" +"The Jupyter notebook needs some extra pieces to build Javascript " +"components; the information about that is in the `notebook contributor " +"documentation `_." +msgstr "" + +# ba9cdf4e3c534e8aaf851f3dda9197fa +#: ../../source/developer-docs/jupyter_enhancement_proposals.rst:2 +#: cffeb44a9ca44856bd674a3815d72a29 +msgid "Jupyter Enhancement Proposals" +msgstr "" + +# ca6fb9c7ab5a4fa886eeafec23b5e9d7 +#: ../../source/developer-docs/jupyter_enhancement_proposals.rst:5 +#: ed67871ee8f04184894ff38881e56cba +msgid "Submitting an Enhancement Proposal" +msgstr "" + +# 7b963188c0664d0eb0db00c494527254 +#: ../../source/developer-docs/jupyter_enhancement_proposals.rst:6 +#: 7b81ad59270a4ea8944c80dbf8c997b6 +msgid "" +"While using the Notebook, you might discover opportunities for growth and" +" ideas for useful new features. If so, feel free to submit an enhancement" +" proposal. The process for submitting enhancements is as follows:" +msgstr "" + +# 00dbb9daf8e847ae9582179a7c574667 +#: ../../source/developer-docs/jupyter_enhancement_proposals.rst:10 +#: 161a3138388243b1a6b02bd72927566c +msgid "" +"Identify the scope of the enhancement. Is it a change that affects only " +"on part of the codebase? Is the enhancement, to the best of your " +"knowledge, fairly trivial to implement? If the scope of the enhancement " +"is small, it should be be submitted as an issue in the project's " +"repository. If the scope of your enhancement is large, it should be " +"submitted to the official `Jupyter Enhancement Proposals repository " +"`_." +msgstr "" + +# ce6afac33e824a67b47c41ac989e42fe +#: ../../source/developer-docs/jupyter_enhancement_proposals.rst:17 +#: cbf0609158a34d15b02f993464904b23 +msgid "" +"Prepare a brief write-up of the problem that your enhancement will " +"address." +msgstr "" + +# b3c8157c7deb456cbfc628b50b9cb3e5 +#: ../../source/developer-docs/jupyter_enhancement_proposals.rst:19 +#: fda81fc4b94d41baa2c8bc01aaff243d +msgid "Prepare a brief write-up of the proposed enhancement itself." +msgstr "" + +# a3742f392e7d48269a6eb5ad6b3b29db +#: ../../source/developer-docs/jupyter_enhancement_proposals.rst:21 +#: e6a5cdb22ad64d07bd63f36d3bedc318 +msgid "" +"If the scope of your enhancement (as defined in step 1) is large, then " +"prepare a detailed write-up of how your enhancement can be potentially " +"implemented." +msgstr "" + +# 8b68a4fe91c741fa8ca70adea65993b3 +#: ../../source/developer-docs/jupyter_enhancement_proposals.rst:24 +#: eb0edfeacd5446dab2944c8634333b96 +msgid "" +"Identify a brief list of the pros and cons associated with implementing " +"the enhancement that you propose." +msgstr "" + +# 05d6c080c5694b76b055702502bba802 +#: ../../source/developer-docs/jupyter_enhancement_proposals.rst:27 +#: fc63f72ae8b443e1a630547a980c1a3d +msgid "" +"Identify the individuals who might be interested in implementing the " +"enhancement." +msgstr "" + +# c2300fb3ceac4a66a45558b7967a8b69 +#: ../../source/developer-docs/jupyter_enhancement_proposals.rst:29 +#: 59f29106521041bd85a47575e8ab3ba2 +msgid "" +"Depending on the scope of your enhancement, submit it either as an issue " +"to the appropriate repository or as a Jupyter Enhancement Proposal." +msgstr "" + +# 5229bf41eae2469e935b184e97efb92f +#: ../../source/developer-docs/releasing.rst:5 137805f1c2c64bc986e42e48e03765e8 +msgid "Basic template for releasing a Jupyter project" +msgstr "" + +# cd861154d1f84d8ea5d16b605e863348 +#: ../../source/developer-docs/releasing.rst:7 c626c59229ff46bba1984eab5ac58ff6 +msgid "" +"Jupyter consists of a bunch of small projects, and a few larger ones. " +"This lays out the basic process of releasing a smaller project, which " +"should also apply to larger projects, though they may have some added " +"steps." +msgstr "" + +# ee207b96ee4e491eb606356ff7070dfa +#: ../../source/developer-docs/releasing.rst:14 +#: 2c0d579208784f2bb68b340b6b4cc9ce +msgid "Milestones" +msgstr "" + +# 2a00176ea8fb4fe794664c05e57dd8b5 +#: ../../source/developer-docs/releasing.rst:16 +#: 35ebbd31eaa34c3f976fc70fc5cff5d1 +msgid "" +"Most Jupyter projects use a GitHub milestone system for marking issues " +"and pull requests in releases. Each release should have a milestone " +"associated with it. The first step in preparing for a release is to make " +"sure that every issue and pull request has the right milestone." +msgstr "" + +# 0c7eec680ceb4af9a72f8dab62c26656 +#: ../../source/developer-docs/releasing.rst:20 +#: 5d536f21ec644749b823d5a656d0a1cb +msgid "" +"Go through any **open** Issues and Pull Requests marked with the current " +"milestone. If there are any, they need to be resolved or bumped to the " +"next milestone. It's fine to bump issues - they are typically marked with" +" the earliest feasible milestone, but many such optimistically marked " +"tasks aren't complete when it's time to release. There's always next " +"time!" +msgstr "" + +# bb130aa7931f4847b76a34059a9c9d35 +#: ../../source/developer-docs/releasing.rst:25 +#: 1345696fd39849c8b4243edccefb43f4 +msgid "" +"Check **closed** Issues and Pull Requests, using the milestone filter " +"\"Issues with no milestone\". There should never be any closed issues or " +"pull requests without a milestone. If you find any, go through and mark " +"them with the current milestone or \"no action\" as appropriate." +msgstr "" + +# 405918c188824db7a4ae6128c0016fb5 +#: ../../source/developer-docs/releasing.rst:31 +#: 528e74ddba8c4ffaad4bbda91ab9ba15 +msgid "" +"A release may be ready to go when it has zero open issues or pull " +"requests." +msgstr "" + +# 1e581bc70c1245fa87d458bb6cf9da6f +#: ../../source/developer-docs/releasing.rst:35 +#: d1162958b14d4836aa2d6cc8037f5ac2 +msgid "Release notes" +msgstr "" + +# cee9ab2013764c5384b4744a1b53fc93 +#: ../../source/developer-docs/releasing.rst:37 +#: db07278d7b7245f0aaa8930b56fc13c9 +msgid "" +"Once all of the issues and pull requests are dealt with, it's time to " +"make release notes. The smaller projects generally have a " +":file:`changelog.rst` in the docs directory, where you can add a section " +"for the new release. Look through the pull requests merged for the " +"current milestone (this is why we use milestones), and write a short " +"summary of the highlights of the changes in this release. There should " +"generally be a link to the milestone itself for more details." +msgstr "" + +# 089a6812113341949f101391390ff914 +#: ../../source/developer-docs/releasing.rst:45 +#: 855d81ada8a04dd1895b94a871238bf2 +msgid "" +"Make a pull requests with these notes. It's a good idea to cc @willingc " +"for review of this PR. Make sure to mark this PR with your release's " +"milestone!" +msgstr "" + +# cc10475d5ef64e6ba38860fd5de6746d +#: ../../source/developer-docs/releasing.rst:51 +#: bbcf729cfe71486c951f0797536e7401 +msgid "Making the release" +msgstr "" + +# df383c7a5c5945838338679952e39cb2 +#: ../../source/developer-docs/releasing.rst:53 +#: 30a0f44742764515ae527c1efc592bc4 +msgid "" +"Now that your changelog is merged, we can actually build and publish the " +"release. We'll assume that ``V`` has been declared as a shell variable " +"containing the release version::" +msgstr "" + +# c3f810a58bec4ab593bd3cb5780a7800 +#: ../../source/developer-docs/releasing.rst:58 +#: 02808c45190346a5a236ef1ccbbc7208 +msgid "" +"Start by making sure you have a clean checkout of master, with no extra " +"files::" +msgstr "" + +# dfa0fb808869495cb344491a84a9bb95 +#: ../../source/developer-docs/releasing.rst:63 +#: cfe2d988cc5a451ea3318a07bad0569f +msgid "" +"First, update the version of the package, often in the file " +":file:`/_version.py` or similar." +msgstr "" + +# 4bcd13891eac4bb0ba91bbebcf098767 +#: ../../source/developer-docs/releasing.rst:65 +#: bbdee634ca8444a5839e2305f1da7a3a +msgid "Commit that change::" +msgstr "" + +# 34263cae40c2473d9fba3a813758b95f +#: ../../source/developer-docs/releasing.rst:71 +#: d814b47bd9f548abbe356a5dc59ebaf5 +msgid "" +"At this point, I like to run the tests just to be sure that setting the " +"version didn't confuse anything." +msgstr "" + +# 5a5e318fddd94e67a6ff324546cf6ea8 +#: ../../source/developer-docs/releasing.rst:74 +#: 4cd3f8d47c7c4e72a8ab08710054a655 +msgid "Build the distributions::" +msgstr "" + +# f6f03aad7bdd4be79c7cb7d1d4fd0898 +#: ../../source/developer-docs/releasing.rst:79 +#: 8b6962365f9f4d98b4dcef6523f1ddd5 +msgid "Tag the commit::" +msgstr "" + +# 83952c3b04f449d8a88e05fdb304dd29 +#: ../../source/developer-docs/releasing.rst:83 +#: b773e4f8d29a4eeeaf4a5b26f6caf6b4 +msgid "" +"And finally, publish everything, to github and PyPI using `twine " +"`_::" +msgstr "" + +# 6aae441e50b747efa6796a94f1d11211 +#: ../../source/developer-docs/releasing.rst:89 +#: 3d9041c26fe146bb814630f625bf24a7 +msgid "" +"We have a release! You can now bump the version to the next '.dev' " +"version, by editing :file:`/_version.py` (or similar) again, and " +"commit::" +msgstr "" + +# c3cde896bc9041b49e4f3305ec5d2128 +#: ../../source/developer-docs/releasing.rst:97 +#: 7447614b539c42d1bc59064bf7c23aea +msgid "" +"The pushes assume that `origin` points to the main jupyter/ipython repo. " +"Depending how you use git, this could be `upstream` or something else." +msgstr "" + +# f1a0b2f2975f459e8c85be7dfe502070 +#~ msgid "" +#~ "`Notable Issues " +#~ "`__" +#~ msgstr "" + +# f7a939c12a42438796221b1b3216b85c +#~ msgid "" +#~ "`Notable Issues " +#~ "`__" +#~ msgstr "" + +# 2d035ecd6e9e40dfa1aa14533fd7e41c +#~ msgid "" +#~ "`Notable Issues " +#~ "`__" +#~ msgstr "" + +# a848ceabd5bb48f9ba9cd7741ffe2733 +#~ msgid "" +#~ "If you believe you've found a " +#~ "security vulnerability in a Jupyter " +#~ "project, please report it to " +#~ "[security@ipython.org](mailto:security@ipython.org). If " +#~ "you prefer to encrypt your security " +#~ "reports, you can use [this PGP " +#~ "public key](https://jupyter-" +#~ "notebook.readthedocs.io/en/stable/_downloads/ipython_security.asc)." +#~ msgstr "" + +# 9219dc1779c14cdc86b8897e89749812 +#~ msgid "" +#~ "The Jupyter notebook needs some extra" +#~ " pieces to build Javascript components; " +#~ "the information about that is in " +#~ "the `notebook contributor documentation `_." +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/development_guide.po b/docs/source/locale/en/LC_MESSAGES/development_guide.po new file mode 100644 index 000000000..c5c536aad --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/development_guide.po @@ -0,0 +1,3953 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2019-10-04 14:36+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.7.0\n" + +# 68594f7b5d5243178cc934fef0ff52ac +#: ../../source/development_guide/boot2docker.rst:4 +msgid "Setup IPython development environment using boot2docker" +msgstr "" + +# c58a4d9ce362416aa2daee3df0414ffb +# e672e2de6d6449a29cc141b4ade2eeda +# da64540a97524eae993335e681c87efe +# df673bb406394df09796f62b181bc76c +# c6ccec59d6b24b65b672d2b16e0cfbf3 +# a3791289050546b592649661277f5df9 +# c7c0ad0e79bb413b8d7956188294533b +# 98a81ea5075b4ea7b5565d6bc0b86a03 +# 8443422c6ee045edbcd483ce2c654348 +# 0a17cb2a8248427c9980b12767b26bf5 +# 53507b55bf0d4779879707534702049f +# e7da595236724a8c9c3f228d663e0a98 +# fcc87c9518d44372986a025fb70993b6 +# 914169504e1f479db9966697a9c327b4 +# abe35ed53e9544aaba2a10892e50c995 +# 75aa173cd6e349c38f5c305f6c1e8cf6 +#: ../../source/development_guide/boot2docker.rst:7 +#: ../../source/development_guide/closing_prs.rst:7 +#: ../../source/development_guide/coding_style.rst:7 +#: ../../source/development_guide/documenting_ipython.rst:7 +#: ../../source/development_guide/github_workflow.rst:7 +#: ../../source/development_guide/index.rst:7 +#: ../../source/development_guide/js_events.rst:7 +#: ../../source/development_guide/lab_meetings.rst:7 +#: ../../source/development_guide/less.rst:7 +#: ../../source/development_guide/pull_request.rst:7 +#: ../../source/development_guide/py3compat.rst:7 +#: ../../source/development_guide/releasing.rst:7 +#: ../../source/development_guide/rest_api.rst:7 +#: ../../source/development_guide/sphinx_directive.rst:7 +#: ../../source/development_guide/testing.rst:7 +#: ../../source/development_guide/testing_kernels.rst:7 +msgid "" +"This is copied verbatim from the old IPython wiki and is currently under " +"development. Much of the information in this part of the development " +"guide is out of date." +msgstr "" + +# 838ebaf9ef564b538433da5fc636f7f1 +#: ../../source/development_guide/boot2docker.rst:9 +msgid "" +"The following are instructions on how to get an IPython development " +"environment up and running without having to install anything on your " +"host machine, other than ```boot2docker`` " +"`__ and ```docker`` " +"`__." +msgstr "" + +# b68287e01b4e44feaa6874beb4f48e33 +#: ../../source/development_guide/boot2docker.rst:16 +msgid "Install ``boot2docker``" +msgstr "" + +# 87465fdbf40840caa1d714143f237347 +#: ../../source/development_guide/boot2docker.rst:18 +msgid "" +"Install `boot2docker `__. " +"There are multiple ways to install, depending on your environment. See " +"the `boot2docker docs `__." +msgstr "" + +# 4b5576467cd04ab4addfaf7f2dbc9c8c +#: ../../source/development_guide/boot2docker.rst:24 +msgid "Mac OS X" +msgstr "" + +# c22634b884c6483ebe67c40611bc9805 +#: ../../source/development_guide/boot2docker.rst:26 +msgid "On a Mac OS X host with `Homebrew `__ installed:" +msgstr "" + +# db5a7fb63dbe455083f8e8e2caed7435 +#: ../../source/development_guide/boot2docker.rst:33 +msgid "Initialize ``boot2docker`` VM" +msgstr "" + +# 54c6a6b598ac43b6aee4cd42e11a47b6 +#: ../../source/development_guide/boot2docker.rst:40 +msgid "Start VM" +msgstr "" + +# 0f0d8f53a4ef40b590afdf1f1dcd8902 +#: ../../source/development_guide/boot2docker.rst:46 +msgid "" +"The ``boot2docker`` CLI communicates with the docker daemon on the " +"``boot2docker`` VM. To do this, we must set some environment variables, " +"e.g. ``DOCKER_HOST``," +msgstr "" + +# cc1d31d1c4a247378bfcaaad4453050f +#: ../../source/development_guide/boot2docker.rst:54 +msgid "To view the IP address of the VM:" +msgstr "" + +# 3644c712c8d042deb536906e299d7302 +#: ../../source/development_guide/boot2docker.rst:62 +msgid "Install ``ipython`` from Development Branch" +msgstr "" + +# fb26c1a1c9e64219a9569a2f09491a7c +#: ../../source/development_guide/boot2docker.rst:69 +msgid "Build Docker Image" +msgstr "" + +# 3186d34726d84139b077dd88cfcfb94a +#: ../../source/development_guide/boot2docker.rst:71 +msgid "" +"Use the Dockerfile in the cloned ``ipython`` directory to build a Docker " +"image." +msgstr "" + +# 07c715242d6d4a7fbf8b07eb27d00c5d +#: ../../source/development_guide/boot2docker.rst:80 +msgid "Run Docker Container" +msgstr "" + +# 1e5ff76a0da84a9d94587ef29a5ff8d4 +#: ../../source/development_guide/boot2docker.rst:82 +msgid "" +"Run a container using the new image. We mount the entire ``ipython`` " +"source tree on the host into the container at ``/srv/ipython`` to enable " +"changes we make to the source on the host immediately reflected in the " +"container." +msgstr "" + +# 7169e25c6baf40b8889c6a22f710203e +#: ../../source/development_guide/boot2docker.rst:93 +msgid "To list the running container from another shell on the host:" +msgstr "" + +# 03945f9ceca44f629ddca27e5a97b97e +#: ../../source/development_guide/boot2docker.rst:103 +msgid "Install IPython in Editable Mode" +msgstr "" + +# 5a1104a612284812a3ae1bbe1c90fea6 +#: ../../source/development_guide/boot2docker.rst:105 +msgid "" +"Once in the container, you'll need to uninstall the ``ipython`` package " +"and re-install in editable mode to enable your dev changes to be " +"reflected in your environment." +msgstr "" + +# 5ff35ef88252440b9f9b3eb342580672 +#: ../../source/development_guide/boot2docker.rst:120 +msgid "Run Notebook Server" +msgstr "" + +# 4e74c9cf2d184935a6c3a2b096d959b5 +#: ../../source/development_guide/boot2docker.rst:127 +msgid "Visit Notebook Server" +msgstr "" + +# 1c7053580c414a5288a396b9ed7805f8 +#: ../../source/development_guide/boot2docker.rst:129 +msgid "" +"On your host, run the following command to get the IP of the boot2docker " +"VM if you forgot:" +msgstr "" + +# 23da7928850040239ef807b7959c0cd9 +#: ../../source/development_guide/boot2docker.rst:138 +msgid "Then visit it in your browser:" +msgstr "" + +# cef8292d861940009dfe37218ea8e00b +#: ../../source/development_guide/boot2docker.rst:145 +msgid "" +"As a shortcut on a Mac, you can run the following in a terminal window " +"(or make it a bash alias):" +msgstr "" + +# dbb1b7b037264b6aa1392abd9a3cc4e8 +#: ../../source/development_guide/closing_prs.rst:4 +msgid "Policy on Closing Pull Requests" +msgstr "" + +# 4457e1e8c0744af2998ef6c8fda5393a +#: ../../source/development_guide/closing_prs.rst:9 +msgid "" +"IPython has the following policy on closing pull requests. The goal of " +"this policy is to keep our pull request queue small and allow us to focus" +" on code that is being actively developed and has a strong chance of " +"being merged in master soon." +msgstr "" + +# 6d8ef2f40c884f8485f2555032c90e65 +#: ../../source/development_guide/closing_prs.rst:14 +msgid "A pull request will be closed when:" +msgstr "" + +# 5296d8b1e26d4920b014f007532f13c1 +#: ../../source/development_guide/closing_prs.rst:16 +msgid "" +"It has been reviewed, but has sat for a month or more waiting for the " +"submitter to commit more code to address the comments." +msgstr "" + +# 1b189f41fadd4727b9518d4a36cea12e +#: ../../source/development_guide/closing_prs.rst:18 +msgid "" +"The review process has uncovered larger design or technical issues that " +"extend beyond the details of the specific pull request." +msgstr "" + +# 33f62e8f6d374379becff41a3411cfc3 +#: ../../source/development_guide/closing_prs.rst:21 +msgid "" +"In particular, we do not accept whole large \"cleanup\" changes which do " +"not address any specific bug. This includes trailing whitespace, PEP8, " +"etc. One of the reasons is that such massive cleanup provide plenty of " +"opportunities to introduce new and subtle bugs." +msgstr "" + +# ff27543439ef4ff797a196a8a4e5aed6 +#: ../../source/development_guide/closing_prs.rst:27 +msgid "" +"In general we will not close pull requests because of a lack of review. " +"If a pull request has sat for a month or more without review, we need to " +"kick ourselves and get to reviewing it." +msgstr "" + +# 836a8c8dc6d44c04a337d673fb6fbff0 +#: ../../source/development_guide/closing_prs.rst:31 +msgid "When a pull request is closed we will do the following:" +msgstr "" + +# 266b795ae71e43cc87cddb8286e40a03 +#: ../../source/development_guide/closing_prs.rst:33 +msgid "" +"Post a github message to the pull request to confirm that everyone is " +"fine with closing the pull request. This message should cite this policy." +msgstr "" + +# 16ba3fb52f27430f90d7f61930398bb1 +#: ../../source/development_guide/closing_prs.rst:36 +msgid "" +"Open an issue to track the pull request. This issue should describe what " +"would be needed in order to reopen the pull request." +msgstr "" + +# 0f58a1256caa4b7192796a5736a382fa +#: ../../source/development_guide/closing_prs.rst:38 +msgid "" +"Post a github message to the pull request encouraging the submitter to " +"continue with the work and detail what issues need to be addressed in " +"order for the pull request to be reopened." +msgstr "" + +# e69ccb3b0acf4fd084506753d3c24d19 +#: ../../source/development_guide/closing_prs.rst:42 +msgid "This policy was discussed in the following thread:" +msgstr "" + +# 1f3432526f934316b5cc8c24c79373d0 +#: ../../source/development_guide/closing_prs.rst:44 +msgid "https://mail.scipy.org/pipermail/ipython-dev/2012-August/010025.html" +msgstr "" + +# ed7cad128706471b952c27bef1853163 +#: ../../source/development_guide/closing_prs.rst:47 +msgid "Example Message:" +msgstr "" + +# 2ed6aa93ae254842abf6ac9840dcad6b +#: ../../source/development_guide/coding_style.rst:4 +msgid "Coding Style" +msgstr "" + +# 9dc8aa2c74864d179a5660cf9b835565 +#: ../../source/development_guide/coding_style.rst:9 +msgid "" +"This document describes our coding style. Coding style refers to the " +"following:" +msgstr "" + +# 3b823c54355c4add8d1a262896faff88 +#: ../../source/development_guide/coding_style.rst:12 +msgid "How source code is formatted (indentation, spacing, etc.)" +msgstr "" + +# 57c4f53e269a4abc99fb2f32b3c45fbe +#: ../../source/development_guide/coding_style.rst:13 +msgid "How things are named (variables, functions, classes, modules, etc.)" +msgstr "" + +# c110cd13183f48c3ba04055dc0fe3cd1 +#: ../../source/development_guide/coding_style.rst:16 +msgid "General coding conventions" +msgstr "" + +# 919ed475296f42af850c26db1f5cf22d +#: ../../source/development_guide/coding_style.rst:18 +msgid "" +"In general, we follow the standard Python style conventions as described " +"in Python's `PEP 8 `__, the " +"official Python Style Guide." +msgstr "" + +# af906044ad2e45d59473fa93957caf11 +#: ../../source/development_guide/coding_style.rst:22 +msgid "Other general comments:" +msgstr "" + +# a67babfcd44d4b78b92ae38338f1ae72 +#: ../../source/development_guide/coding_style.rst:24 +msgid "" +"In a large file, top level classes and functions should be separated by 2" +" lines to make it easier to separate them visually." +msgstr "" + +# 93eb729f53834df789c27c571a413cf3 +#: ../../source/development_guide/coding_style.rst:27 +msgid "Use 4 spaces for indentation, **never** use hard tabs." +msgstr "" + +# 7f266e5248eb4e03b2e6172a78a8192f +#: ../../source/development_guide/coding_style.rst:29 +msgid "" +"Keep the ordering of methods the same in classes that have the same " +"methods. This is particularly true for classes that implement similar " +"interfaces and for interfaces that are similar." +msgstr "" + +# f0f19b61545e4b3494e24b82a6428eb8 +#: ../../source/development_guide/coding_style.rst:34 +msgid "Naming conventions" +msgstr "" + +# 627a72694cf142f29149585571fe0f00 +#: ../../source/development_guide/coding_style.rst:36 +msgid "" +"For naming conventions, we also follow the guidelines of `PEP 8 " +"`__. Some of the existing code" +" doesn't honor this perfectly, but for all new and refactored IPython " +"code, we'll use:" +msgstr "" + +# 01c1d05be01b4ebaa2925993cda05b5e +#: ../../source/development_guide/coding_style.rst:41 +msgid "" +"All ``lowercase`` module names. Long module names can have words " +"separated by underscores (``really_long_module_name.py``), but this is " +"not required. Try to use the convention of nearby files." +msgstr "" + +# 735af590e2894b84a25c4e014f5668ac +#: ../../source/development_guide/coding_style.rst:45 +msgid "``CamelCase`` for class names." +msgstr "" + +# 79ba0d92752b4a81a3edd927e5bb04bb +#: ../../source/development_guide/coding_style.rst:47 +msgid "" +"``lowercase_with_underscores`` for methods, functions, variables and " +"attributes." +msgstr "" + +# 8bef511e37924748b1d2e276dbe87e14 +#: ../../source/development_guide/coding_style.rst:50 +msgid "" +"Implementation-specific *private* methods will use " +"``_single_underscore_prefix``. Names with a leading double underscore " +"will *only* be used in special cases, as they makes subclassing difficult" +" (such names are not easily seen by child classes)." +msgstr "" + +# 91bbe7cbf0a94cfbbbd298eaa6a826eb +#: ../../source/development_guide/coding_style.rst:55 +msgid "" +"Occasionally some run-in lowercase names are used, but mostly for very " +"short names or where we are implementing methods very similar to existing" +" ones in a base class (like ``runlines()`` where ``runsource()`` and " +"``runcode()`` had established precedent)." +msgstr "" + +# 7c362e1e2fa444b49046b01386e4deb0 +#: ../../source/development_guide/coding_style.rst:60 +msgid "" +"The old IPython codebase has a big mix of classes and modules prefixed " +"with an explicit ``IP`` of ``ip``. This is not necessary and all new code" +" should not use this prefix. The only case where this approach is " +"justified is for classes or functions which are expected to be imported " +"into external namespaces and a very generic name (like Shell) that is " +"likely to clash with something else. However, if a prefix seems " +"absolutely necessary the more specific ``IPY`` or ``ipy`` are preferred." +msgstr "" + +# 726f417c6f4f4bd7848b5a4fb6335b48 +#: ../../source/development_guide/coding_style.rst:69 +msgid "All JavaScript code should follow these naming conventions as well." +msgstr "" + +# 45e0d17e22f64edf9c68181820b2598c +#: ../../source/development_guide/coding_style.rst:72 +msgid "Attribute declarations for objects" +msgstr "" + +# 90a2d8345a8d431d9e85b972149d0aa2 +#: ../../source/development_guide/coding_style.rst:74 +msgid "" +"In general, objects should declare, in their *class*, all attributes the " +"object is meant to hold throughout its life. While Python allows you to " +"add an attribute to an instance at any point in time, this makes the code" +" harder to read and requires methods to constantly use checks with " +"hasattr() or try/except calls. By declaring all attributes of the object " +"in the class header, there is a single place one can refer to for " +"understanding the object's data interface, where comments can explain the" +" role of each variable and when possible, sensible defaults can be " +"assigned." +msgstr "" + +# 37f87ca28453415582149435e73f1912 +#: ../../source/development_guide/coding_style.rst:84 +msgid "" +"If an attribute is meant to contain a mutable object, it should be set to" +" ``None`` in the class and its mutable value should be set in the " +"object's constructor. Since class attributes are shared by all instances," +" failure to do this can lead to difficult to track bugs. But you should " +"still set it in the class declaration so the interface specification is " +"complete and documented in one place." +msgstr "" + +# 608ec84f1ee642bb993c493b2b6c2e9e +#: ../../source/development_guide/coding_style.rst:91 +msgid "A simple example:" +msgstr "" + +# 5c20ddda84a14bce9bf606623cc93d5c +#: ../../source/development_guide/coding_style.rst:108 +msgid "New files" +msgstr "" + +# 1cb302a31307483e8d7cbbf0b518efef +#: ../../source/development_guide/coding_style.rst:110 +msgid "" +"When starting a new Python file for IPython, you can use the `following " +"template <./template.py>`__ as a starting point that has a few common " +"things pre-written for you." +msgstr "" + +# 8dca628763ce406499eb008ec3428735 +#: ../../source/development_guide/documenting_ipython.rst:4 +msgid "Documenting IPython" +msgstr "" + +# 84d33dde8447417eb9e358383a11690f +#: ../../source/development_guide/documenting_ipython.rst:9 +msgid "" +"When contributing code to IPython, you should strive for clarity and " +"consistency, without falling prey to a style straitjacket. Basically, " +"'document everything, try to be consistent, do what makes sense.'" +msgstr "" + +# 7196603c3de542cea955a86758144197 +#: ../../source/development_guide/documenting_ipython.rst:13 +msgid "" +"By and large we follow existing Python practices in major projects like " +"Python itself or NumPy, this document provides some additional detail for" +" IPython." +msgstr "" + +# 219d53313b744213b12d81b83e8df5e1 +#: ../../source/development_guide/documenting_ipython.rst:18 +msgid "Standalone documentation" +msgstr "" + +# 18573d3352f3414eac2f83f8e1e871b7 +#: ../../source/development_guide/documenting_ipython.rst:20 +msgid "" +"All standalone documentation should be written in plain text (``.txt``) " +"files using reStructuredText [reStructuredText]\\_ for markup and " +"formatting. All such documentation should be placed in the directory " +"docs/source of the IPython source tree. Or, when appropriate, a suitably " +"named subdirectory should be used. The documentation in this location " +"will serve as the main source for IPython documentation." +msgstr "" + +# 5cd39db2efda4df4b349d060d6aa6fed +#: ../../source/development_guide/documenting_ipython.rst:27 +msgid "" +"The actual HTML and PDF docs are built using the Sphinx [Sphinx]\\_ " +"documentation generation tool. Once you have Sphinx installed, you can " +"build the html docs yourself by doing:" +msgstr "" + +# e998f0d0a6c04b7b8c56c83b9a9f331d +#: ../../source/development_guide/documenting_ipython.rst:36 +msgid "" +"Our usage of Sphinx follows that of matplotlib [Matplotlib]\\_ closely. " +"We are using a number of Sphinx tools and extensions written by the " +"matplotlib team and will mostly follow their conventions, which are " +"nicely spelled out in their documentation guide [MatplotlibDocGuide]\\_. " +"What follows is thus a abridged version of the matplotlib documentation " +"guide, taken with permission from the matplotlib team." +msgstr "" + +# 8e666fd21967441ea266b6c67f7d3525 +#: ../../source/development_guide/documenting_ipython.rst:43 +msgid "" +"If you are reading this in a web browser, you can click on the \"Show " +"Source\" link to see the original reStricturedText for the following " +"examples." +msgstr "" + +# cc20bf2f388f4367b6ba15ad83d829a0 +#: ../../source/development_guide/documenting_ipython.rst:47 +msgid "A bit of Python code:" +msgstr "" + +# 264cf7c13ba249b89ef7c49f385d7e84 +#: ../../source/development_guide/documenting_ipython.rst:55 +msgid "An interactive Python session:" +msgstr "" + +# 786a003a590a47deb799b41de76c206d +#: ../../source/development_guide/documenting_ipython.rst:63 +msgid "An IPython session:" +msgstr "" + +# 6b24f490d8474cb2b37153c2af7ce628 +#: ../../source/development_guide/documenting_ipython.rst:75 +msgid "A bit of shell code:" +msgstr "" + +# db00e5ea736140fb9f337702c96a4a8b +#: ../../source/development_guide/documenting_ipython.rst:84 +msgid "Docstring format" +msgstr "" + +# 4c0a416dddfd49c3a4dd057290418e1a +#: ../../source/development_guide/documenting_ipython.rst:86 +msgid "" +"Good docstrings are very important. Unfortunately, Python itself only " +"provides a rather loose standard for docstrings [PEP257]\\_, and there is" +" no universally accepted convention for all the different parts of a " +"complete docstring. However, the NumPy project has established a very " +"reasonable standard, and has developed some tools to support the smooth " +"inclusion of such docstrings in Sphinx-generated manuals. Rather than " +"inventing yet another pseudo-standard, IPython will be henceforth " +"documented using the NumPy conventions; we carry copies of some of the " +"NumPy support tools to remain self-contained, but share back upstream " +"with NumPy any improvements or fixes we may make to the tools." +msgstr "" + +# 55afdecbcdcf4655a4a1524d6a7dd4e8 +#: ../../source/development_guide/documenting_ipython.rst:97 +msgid "" +"The NumPy documentation guidelines [NumPyDocGuide]\\_ contain detailed " +"information on this standard, and for a quick overview, the NumPy example" +" docstring [NumPyExampleDocstring]\\_ is a useful read." +msgstr "" + +# 8b42aebb3a444d4d9b728e9ad4ddd161 +#: ../../source/development_guide/documenting_ipython.rst:101 +msgid "" +"For user-facing APIs, we try to be fairly strict about following the " +"above standards (even though they mean more verbose and detailed " +"docstrings). Wherever you can reasonably expect people to do " +"introspection with:" +msgstr "" + +# eeec98ec0a6b460f840a0694f95d90ab +#: ../../source/development_guide/documenting_ipython.rst:110 +msgid "the docstring should follow the NumPy style and be fairly detailed." +msgstr "" + +# ff6b3e20f5bf45a791cbe212c899964c +#: ../../source/development_guide/documenting_ipython.rst:112 +msgid "" +"For purely internal methods that are only likely to be read by others " +"extending IPython itself we are a bit more relaxed, especially for " +"small/short methods and functions whose intent is reasonably obvious. We " +"still expect docstrings to be written, but they can be simpler. For very " +"short functions with a single-line docstring you can use something like:" +msgstr "" + +# 356a512b00f64482a03af0ccb7086cf0 +#: ../../source/development_guide/documenting_ipython.rst:125 +msgid "and for longer multiline strings:" +msgstr "" + +# 317dcb97e87a48df8a65ea5a29ce8171 +#: ../../source/development_guide/documenting_ipython.rst:136 +msgid "" +"Here are two additional PEPs of interest regarding documentation of code." +" While both of these were rejected, the ideas therein form much of the " +"basis of docutils (the machinery to process reStructuredText):" +msgstr "" + +# 3c9e0437ad854754bfefb01141704884 +#: ../../source/development_guide/documenting_ipython.rst:140 +msgid "" +"`Docstring Processing System Framework " +"`__" +msgstr "" + +# 5693f929f2b34d5a8f7e870041bd26e3 +#: ../../source/development_guide/documenting_ipython.rst:142 +msgid "" +"`Docutils Design Specification " +"`__" +msgstr "" + +# a429c37f728d49268eb32174328bbecc +#: ../../source/development_guide/documenting_ipython.rst:145 +msgid "**note**" +msgstr "" + +# 0115bc4e0feb41acb766d6359b30a749 +#: ../../source/development_guide/documenting_ipython.rst:147 +msgid "" +"In the past IPython used epydoc so currently many docstrings still use " +"epydoc conventions. We will update them as we go, but all new code should" +" be documented using the NumPy standard." +msgstr "" + +# 0a62190ea5ec408199bc8c8de14bb3d5 +#: ../../source/development_guide/documenting_ipython.rst:152 +msgid "Building and uploading" +msgstr "" + +# e6d62b507602420ba1108675bd354123 +#: ../../source/development_guide/documenting_ipython.rst:154 +msgid "" +"The built docs are stored in a separate repository. Through some github " +"magic, they're automatically exposed as a website. It works like this:" +msgstr "" + +# 033f18c19fd14b2d850eebfe9c5bff9c +#: ../../source/development_guide/documenting_ipython.rst:157 +msgid "" +"You will need to have sphinx and latex installed. In Ubuntu, install " +"``texlive-latex-recommended texlive-latex-extra texlive-fonts-" +"recommended``. Install the latest version of sphinx from PyPI (``pip " +"install sphinx``)." +msgstr "" + +# 76ad90067595421eb7515641ec908c1e +#: ../../source/development_guide/documenting_ipython.rst:161 +msgid "" +"Ensure that the development version of IPython is the first in your " +"system path. You can either use a virtualenv, or modify your PYTHONPATH." +msgstr "" + +# 9a38ef6f51434d2a89b0910cf9abab96 +#: ../../source/development_guide/documenting_ipython.rst:164 +msgid "" +"Switch into the docs directory, and run ``make gh-pages``. This will " +"build your updated docs as html and pdf, then automatically check out the" +" latest version of the docs repository, copy the built docs into it, and " +"commit your changes." +msgstr "" + +# df5ab19592a5476285b9e7d8eb2afd48 +#: ../../source/development_guide/documenting_ipython.rst:168 +msgid "Open the built docs in a web browser, and check that they're as expected." +msgstr "" + +# 18be1af497b341e2a51dc82023fc53be +#: ../../source/development_guide/documenting_ipython.rst:170 +msgid "" +"(When building the docs for a new tagged release, you will have to add " +"its link to index.rst, then run ``python build_index.py`` to update " +"index.html. Commit the change.)" +msgstr "" + +# 8e1611ea31854e92a53e904775463bee +#: ../../source/development_guide/documenting_ipython.rst:173 +msgid "" +"Upload the docs with ``git push``. This only works if you have write " +"access to the docs repository." +msgstr "" + +# ec61477d7da4430a9b32d253523f183f +#: ../../source/development_guide/documenting_ipython.rst:175 +msgid "" +"If you are building a version that is not the current dev branch, nor a " +"tagged release, then you must run gh-pages.py directly with ``python gh-" +"pages.py ``, and *not* with ``make gh-pages``." +msgstr "" + +# 1649b48861b04f75bf0ebb94efa60170 +#: ../../source/development_guide/github_workflow.rst:4 +msgid "IPython on GitHub" +msgstr "" + +# 3585ed0c8e314d96a6bb14e72277340e +#: ../../source/development_guide/github_workflow.rst:9 +msgid "Notes on working with GitHub" +msgstr "" + +# 25cdba5ee7d847f0ac00fc8b042838d5 +#: ../../source/development_guide/github_workflow.rst:14 +msgid "Milestones" +msgstr "" + +# 0f8c5c03390e4297aa264a525fa88975 +#: ../../source/development_guide/github_workflow.rst:16 +#, python-format +msgid "100% of confirmed issues should have a milestone." +msgstr "" + +# 962e8c858379422dbd3521984486885f +#: ../../source/development_guide/github_workflow.rst:17 +msgid "An issue should never be closed without a milestone." +msgstr "" + +# 083f524c4a424ba0872df779d2fdd5ac +#: ../../source/development_guide/github_workflow.rst:18 +msgid "All pull requests should have a milestone." +msgstr "" + +# bbfa916999bf40bf86ac1e57bf98442d +#: ../../source/development_guide/github_workflow.rst:19 +msgid "" +"All issues closed should be marked with the next release milestone, next " +"backport milestone, or **no action**." +msgstr "" + +# a47267eb8fa34a3c95b8d48c20f67475 +#: ../../source/development_guide/github_workflow.rst:21 +msgid "Open issues should only lack a milestone if:" +msgstr "" + +# 2ade481e7b04485bbb5fa1e2edbcff5d +#: ../../source/development_guide/github_workflow.rst:23 +msgid "more clarification is required (label: ``needs-info``)" +msgstr "" + +# 25a12565438b42c4ade49360ba8d7f5c +#: ../../source/development_guide/github_workflow.rst:25 +msgid "In general, there will be four milestones with open issues:" +msgstr "" + +# 16bfe5662f274d3580492d27cc15f88c +#: ../../source/development_guide/github_workflow.rst:27 +msgid "" +"**next minor release**. This milestone contains issues that should be " +"backported for the next minor release. See `below <#backporting>`__ for " +"information on backporting." +msgstr "" + +# 75539ed429124cefbb1a4ca005b58e98 +#: ../../source/development_guide/github_workflow.rst:30 +msgid "" +"**next major release**. This should be the default milestone of all " +"issues. As the release approaches, issues can be explicitly bumped to " +"next release + 1." +msgstr "" + +# e0269932529847bf80bbfb32ef1eb875 +#: ../../source/development_guide/github_workflow.rst:33 +msgid "" +"**next major release + 1**. Only issues that we are confident will *not* " +"be included in the next release go here. This milestone should be mostly " +"empty until relatively close to release." +msgstr "" + +# 03b9b3e660694f1c975ef87b6237cb54 +#: ../../source/development_guide/github_workflow.rst:36 +msgid "" +"**wishlist**. This is the milestone for issues that we have no immediate " +"plans to address." +msgstr "" + +# 2d20a33c88384cbd9ac6d2b2853778fb +#: ../../source/development_guide/github_workflow.rst:39 +msgid "" +"The remaining milestone is **no action** for open or closed issues that " +"require no action:" +msgstr "" + +# ac39ba3996a54cdb84c3aabf70f2f42b +#: ../../source/development_guide/github_workflow.rst:42 +msgid "Not actually an issue (e.g. questions, discussion, etc.)" +msgstr "" + +# 4eb11b0ab81c4186af066494cbf6f880 +#: ../../source/development_guide/github_workflow.rst:43 +msgid "Duplicate of an existing Issue" +msgstr "" + +# e910e40d62ae40ba92ebf2aad4f571f7 +#: ../../source/development_guide/github_workflow.rst:44 +msgid "Closed because we won't fix it" +msgstr "" + +# f7fd1309dbb94e44816ac5f6d3412aae +#: ../../source/development_guide/github_workflow.rst:45 +msgid "" +"When an issue is closed with **no action**, it means that the issue will " +"not be fixed, or it was not an issue at all." +msgstr "" + +# 226b21806c0340128426c701cad68736 +#: ../../source/development_guide/github_workflow.rst:48 +msgid "When closing an issue, it should always have one of these milestones:" +msgstr "" + +# 0b2befff4807419fbd6f84974b7f8c46 +#: ../../source/development_guide/github_workflow.rst:50 +msgid "**next minor release** because the issue has been addressed" +msgstr "" + +# 146a5f43c2c440328ef41b0494c607b1 +#: ../../source/development_guide/github_workflow.rst:51 +msgid "**next major release** because the issue has been addressed" +msgstr "" + +# 8043711c7ac7473390f1aef4d28b1d95 +#: ../../source/development_guide/github_workflow.rst:52 +msgid "" +"**no action** because the issue *will not* be addressed, or it is a " +"duplicate/non-issue." +msgstr "" + +# 048050b4c6254852adc7aa6ba6bb05f6 +#: ../../source/development_guide/github_workflow.rst:55 +msgid "" +"In general: When in doubt, mark with **next release**. We can always push" +" back when we get closer to a given release." +msgstr "" + +# fd9848b03ee84d5a9624e3483c251a69 +#: ../../source/development_guide/github_workflow.rst:59 +msgid "Labels and issues" +msgstr "" + +# 9b8cd118660a40218ef73c550077249a +#: ../../source/development_guide/github_workflow.rst:61 +msgid "" +"Issues should always be labeled once they are confirmed (not necessary " +"for issues that are still being clarified, or may be duplicates or not " +"issues at all)." +msgstr "" + +# dcacfa148b804c6db2f154268d88c844 +#: ../../source/development_guide/github_workflow.rst:65 +msgid "Some significant labels:" +msgstr "" + +# 26d8c609c57b43c39115722f0ab20355 +#: ../../source/development_guide/github_workflow.rst:67 +msgid "" +"``needs-info``: issue needs more information from submitter before " +"progress can be made" +msgstr "" + +# 6b80d1ff88f84142a5403d8b16fa0239 +#: ../../source/development_guide/github_workflow.rst:69 +msgid "``bug``: errors are raised, or unintended behavior occurs" +msgstr "" + +# fb4b2da07e144e4e9a2a89ed6e2a8309 +#: ../../source/development_guide/github_workflow.rst:70 +msgid "``enhancement``: improvements that are not bugs" +msgstr "" + +# 89c22fbe066c4b50bc24db7569adf9ad +#: ../../source/development_guide/github_workflow.rst:77 +msgid "" +"backport-X.Y.Z: Any fix for this issue should be backported to the " +"maintenance branch. backports are expressed with milestones, starting " +"with 2.1." +msgstr "" + +# bea030babcf847d59f598000b057b061 +#: ../../source/development_guide/github_workflow.rst:80 +msgid "" +"``prio-foo``: a priority level for ranking issues - nonessential, but " +"prio-high/low are useful for explicitly promoting/demoting issues, " +"particularly when nearing release." +msgstr "" + +# 79d34ec383e549e9ad82a26201e9a3fe +#: ../../source/development_guide/github_workflow.rst:83 +msgid "" +"``ClosedPR``: This issue is a reminder for a PR that was closed for going" +" stale." +msgstr "" + +# ded670b7781b4ff38727ca5925f8fb91 +#: ../../source/development_guide/github_workflow.rst:85 +msgid "``sprint-friendly``: Obvious or easy fixes, where" +msgstr "" + +# f44525ee35164c348398f65d3d5fef6e +#: ../../source/development_guide/github_workflow.rst:87 +msgid "" +"All confirmed issues should at least have a ``bug`` or ``enhancement`` " +"label, and be marked with any affected components (e.g ``parallel``, " +"``qtconsole``, ``htmlnotebook``), or particular sources of error (e.g. " +"``py3k`` or ``unicode``) if we have appropriate labels." +msgstr "" + +# 2ecbbea9359e4cffa85607c65b703502 +#: ../../source/development_guide/github_workflow.rst:92 +msgid "" +"The ``sprint-friendly`` label is probably the best place for new " +"contributors to start." +msgstr "" + +# f3c4914e879d4e238f14c29a45205179 +#: ../../source/development_guide/github_workflow.rst:96 +msgid "Pull Requests" +msgstr "" + +# 22e663debf3c4bfeacb413987ead6d04 +#: ../../source/development_guide/github_workflow.rst:98 +msgid "All work is submitted via Pull Requests." +msgstr "" + +# 491be18ba00546098911880801ade3fa +#: ../../source/development_guide/github_workflow.rst:99 +msgid "" +"Pull Requests can be submitted as soon as there is code worth discussing." +" Pull Requests track the branch, so you can continue to work after the PR" +" is submitted. Review and discussion can begin well before the work is " +"complete, and the more discussion the better. The worst case is that the " +"PR is closed." +msgstr "" + +# c83bf74d841c41ba803f8f931d0be52d +#: ../../source/development_guide/github_workflow.rst:104 +msgid "" +"Pull Requests that have stalled should be closed (see [[our policy on " +"closing PRs\\|Dev: Closing Pull Requests]])" +msgstr "" + +# 8c5762198389470d8bf22c565df0f764 +#: ../../source/development_guide/github_workflow.rst:106 +msgid "" +"Pull Requests should always be made against master (backporting PRs is " +"described below)." +msgstr "" + +# 8ed220b836404a5ba572cd7705267e19 +#: ../../source/development_guide/github_workflow.rst:108 +msgid "Pull Requests should be tested, if feasible:" +msgstr "" + +# c5c2a705421a41f1886242b0d6eefa96 +#: ../../source/development_guide/github_workflow.rst:110 +msgid "bugfixes should include regression tests" +msgstr "" + +# 6cf267c40a434aafb57b42b651fafca1 +#: ../../source/development_guide/github_workflow.rst:111 +msgid "new behavior should at least get minimal exercise" +msgstr "" + +# aefe7e6aeddf40a8a222bde3337d4026 +#: ../../source/development_guide/github_workflow.rst:113 +msgid "" +"`Travis `__ does a pretty good job" +" testing IPython and Pull Requests, but it may make sense to manually " +"perform tests (possibly with our ``test_pr`` script), particularly for " +"PRs that affect ``IPython.parallel`` or Windows." +msgstr "" + +# d75b67a07bec499e8881441fa03ce53e +#: ../../source/development_guide/github_workflow.rst:119 +msgid "Opening an Issue" +msgstr "" + +# 44bde95ec4a44a86a2238a3e3f7c8c2d +#: ../../source/development_guide/github_workflow.rst:121 +msgid "When opening a new issue, please take the following steps:" +msgstr "" + +# eadd0bf02cea48c49c11fdb30a92cc85 +#: ../../source/development_guide/github_workflow.rst:123 +msgid "" +"Search GitHub and/or Google for your issue to avoid duplicate reports. " +"Keyword searches for your error messages are most helpful." +msgstr "" + +# 752323e4c9604015aaff8b37063830c2 +#: ../../source/development_guide/github_workflow.rst:125 +msgid "" +"If possible, try updating to master and reproducing your issue, because " +"we may have already fixed it." +msgstr "" + +# b570bdae9b6b4579ac1941165f1f801a +#: ../../source/development_guide/github_workflow.rst:127 +msgid "Try to include a minimal reproducible test case" +msgstr "" + +# ed1554fe87da45d2a5c64dc0579d52b0 +#: ../../source/development_guide/github_workflow.rst:128 +msgid "Include relevant system information. Start with the output of:" +msgstr "" + +# de41727a9280424c9fcd2c77ca6d7d3c +#: ../../source/development_guide/github_workflow.rst:134 +msgid "" +"And include any relevant package versions, depending on the issue, such " +"as matplotlib, numpy, Qt, Qt bindings (PyQt/PySide), tornado, web " +"browser, etc." +msgstr "" + +# b69dac6d20d84f4da9aa176b1dca247d +#: ../../source/development_guide/github_workflow.rst:139 +msgid "Backporting" +msgstr "" + +# 6201a6ddc0724acc9f0aa6e2395950b0 +#: ../../source/development_guide/github_workflow.rst:141 +msgid "" +"We should keep an ``A.x`` maintenance branch for backporting fixes from " +"master." +msgstr "" + +# bad96dd4bf104af59b483097f351f7cd +#: ../../source/development_guide/github_workflow.rst:143 +msgid "" +"That branch shall be called ``A.x``, e.g. ``2.x``, not ``2.1``. This way," +" there is only one maintenance branch per release series." +msgstr "" + +# c8f4a678969e4923818596582284101b +#: ../../source/development_guide/github_workflow.rst:145 +msgid "" +"When an Issue is determined to be appropriate for backporting, it should " +"be marked with the ``A.B`` milestone." +msgstr "" + +# 7b66404e9301456dba12b13f438d61a3 +#: ../../source/development_guide/github_workflow.rst:147 +msgid "" +"Any Pull Request which addresses a backport issue should also receive the" +" same milestone." +msgstr "" + +# 9c79bfa009914fafa0019f6e67f48dbf +#: ../../source/development_guide/github_workflow.rst:149 +msgid "" +"Patches are backported to the maintenance branch by applying the pull " +"request patch to the maintenance branch (currently with the " +"`backport\\_pr " +"`__ " +"script)." +msgstr "" + +# 2a7eba1900684fab9689312035a9dbdc +#: ../../source/development_guide/index.rst:14 +msgid "Core Documents" +msgstr "" + +# e80a134fe74c41b79acb0093738690ee +#: ../../source/development_guide/index.rst:23 +msgid "Lab Meetings" +msgstr "" + +# 5d68328888874591905ffd0a0dc08e60 +#: ../../source/development_guide/index.rst:29 +msgid "Development Policies" +msgstr "" + +# 4b19b84c247c45fca67f4925c727048b +#: ../../source/development_guide/index.rst:35 +msgid "Other Information" +msgstr "" + +# 591c48743b9042228f7607d064abfbb1 +#: ../../source/development_guide/index.rst:4 +msgid "IPython Development Guide (source: old IPython wiki)" +msgstr "" + +# 6289363304d44f5496a77e25f2bf8c1d +#: ../../source/development_guide/index.rst:9 +msgid "" +"IPython does all of its development using GitHub. All of our development " +"information is hosted on this GitHub wiki. This page indexes all of that " +"information. Developers interested in getting involved with IPython " +"development should start here." +msgstr "" + +# 12e4517c27a449f48e194515bcda319e +#: ../../source/development_guide/index.rst:49 +msgid "" +"A template for new Python files in IPython: `template.py " +"<./template.py>`__" +msgstr "" + +# 4081c049edfb42229114ea36feec288e +#: ../../source/development_guide/js_events.rst:4 +msgid "JavaScript Events" +msgstr "" + +# c61b275655c7434c93b6bb942d2ed50e +#: ../../source/development_guide/js_events.rst:9 +msgid "(Note: this page is not currently consistent with IPython/Jupyter master)" +msgstr "" + +# 47edbb5e6fb747099a83a04e95f7f67e +#: ../../source/development_guide/js_events.rst:11 +msgid "" +"Javascript events are used to notify unrelated parts of the notebook " +"interface when something happens. For example, if the kernel is busy " +"executing code, it may send an event announcing as such, which can then " +"be picked up by other services, like the notification area. For details " +"on how the events themselves work, see the `JQuery documentation " +"`__." +msgstr "" + +# 98fae31d7b944a1da58cc96e0d1a220b +#: ../../source/development_guide/js_events.rst:18 +msgid "" +"This page documents the core set of events, and explains when and why " +"they are triggered." +msgstr "" + +# e86a5f198ce441e9937343199282991b +#: ../../source/development_guide/js_events.rst:22 +msgid "Cell-related events" +msgstr "" + +# def2f5fa02a743ff9d48c421f82994b3 +#: ../../source/development_guide/js_events.rst:24 +msgid "`command\\_mode.Cell <#command_modecell>`__" +msgstr "" + +# 3a4fd40f4b784920befbe4e8934de8b6 +#: ../../source/development_guide/js_events.rst:25 +msgid "`create.Cell <#createcell>`__" +msgstr "" + +# a53e4f646d3a4c559b61693d04bdddb1 +#: ../../source/development_guide/js_events.rst:26 +msgid "`delete.Cell <#deletecell>`__" +msgstr "" + +# 3d75746bb0c04b4e955c7e1d4dbbcf20 +#: ../../source/development_guide/js_events.rst:27 +msgid "`edit\\_mode.Cell <#edit_modecell>`__" +msgstr "" + +# 0145fa086f07433695ab1dfece970b60 +#: ../../source/development_guide/js_events.rst:28 +msgid "`select.Cell <#selectcell>`__" +msgstr "" + +# 24648c742e394165a105e4acba22fea8 +#: ../../source/development_guide/js_events.rst:29 +msgid "`output\\_appended.OutputArea <#output_appendedoutputarea>`__" +msgstr "" + +# 40072d87d4004a328417903975367ee6 +#: ../../source/development_guide/js_events.rst:32 +msgid "CellToolbar-related events" +msgstr "" + +# 366a5bb76dfb438db5d7533545658e2a +#: ../../source/development_guide/js_events.rst:34 +msgid "`preset\\_activated.CellToolbar <#preset_activatedcelltoolbar>`__" +msgstr "" + +# 0ad06e30020348f8a58b2db214d1f8b0 +#: ../../source/development_guide/js_events.rst:35 +msgid "`preset\\_added.CellToolbar <#preset_addedcelltoolbar>`__" +msgstr "" + +# baf353e6b30e48d3bc81d5d881a9324a +#: ../../source/development_guide/js_events.rst:38 +msgid "Dashboard-related events" +msgstr "" + +# a436b7cbd47040b0bc344ad7412951bd +#: ../../source/development_guide/js_events.rst:40 +msgid "`app\\_initialized.DashboardApp <#app_initializeddashboardapp>`__" +msgstr "" + +# 94c8cba81b564a65b7050479ce437c58 +#: ../../source/development_guide/js_events.rst:41 +msgid "`sessions\\_loaded.Dashboard <#sessions_loadeddashboard>`__" +msgstr "" + +# 7181c050bc5a411a92fb218852db8fe7 +#: ../../source/development_guide/js_events.rst:44 +msgid "app\\_initialized.DashboardApp" +msgstr "" + +# 68fe58e26be54560a352829efd8b9dc8 +#: ../../source/development_guide/js_events.rst:46 +msgid "" +"When the Jupyter Notebook browser window opens for the first time and " +"initializes the Dashboard App. The Dashboard App lists the files and " +"notebooks in the current directory. Additionally, it lets you create and " +"open new Jupyter Notebooks." +msgstr "" + +# b81706f287f048049876387fb9273ce3 +#: ../../source/development_guide/js_events.rst:52 +msgid "Kernel-related events" +msgstr "" + +# b4874043cb84481095a16e4ccb23b3ed +#: ../../source/development_guide/js_events.rst:54 +msgid "`execution\\_request.Kernel <#execution_requestkernel>`__" +msgstr "" + +# 3ac81f6c2d4b40aabda9ee264ca363e2 +#: ../../source/development_guide/js_events.rst:55 +msgid "`input\\_reply.Kernel <#input_replykernel>`__" +msgstr "" + +# 6f8eced167314851835ce91f934c2d11 +#: ../../source/development_guide/js_events.rst:56 +msgid "`kernel\\_autorestarting.Kernel <#kernel_autorestartingkernel>`__" +msgstr "" + +# 47a691a1f6bd4f3baa34f121bec16585 +#: ../../source/development_guide/js_events.rst:57 +msgid "`kernel\\_busy.Kernel <#kernel_busykernel>`__" +msgstr "" + +# 80c97c23fa2c40f09bfddee1110217b7 +#: ../../source/development_guide/js_events.rst:58 +msgid "`kernel\\_connected.Kernel <#kernel_connectedkernel>`__" +msgstr "" + +# 70785bb0e881407e9b26806267abb5ee +#: ../../source/development_guide/js_events.rst:59 +msgid "`kernel\\_connection\\_failed.Kernel <#kernel_connection_failedkernel>`__" +msgstr "" + +# dae8b17088d34805ae776a6c9bc17640 +#: ../../source/development_guide/js_events.rst:60 +msgid "`kernel\\_created.Kernel <#kernel_createdkernel>`__" +msgstr "" + +# 95e5ad5a50454661ac3c028a5896c504 +#: ../../source/development_guide/js_events.rst:61 +msgid "`kernel\\_created.Session <#kernel_createdsession>`__" +msgstr "" + +# 321a1e2d289644f59c756f5095dc7e86 +#: ../../source/development_guide/js_events.rst:62 +msgid "`kernel\\_dead.Kernel <#kernel_deadkernel>`__" +msgstr "" + +# 48e693465ecf4609b40ff7ec7b4c421b +#: ../../source/development_guide/js_events.rst:63 +msgid "`kernel\\_dead.Session <#kernel_deadsession>`__" +msgstr "" + +# e24e76bda50c4198a90a6b4cc9c7f41c +#: ../../source/development_guide/js_events.rst:64 +msgid "`kernel\\_disconnected.Kernel <#kernel_disconnectedkernel>`__" +msgstr "" + +# 791e73bc75a14f1d8efeb196576bdcca +#: ../../source/development_guide/js_events.rst:65 +msgid "`kernel\\_idle.Kernel <#kernel_idlekernel>`__" +msgstr "" + +# 870b93e3cf294b75b3788188a886f91b +#: ../../source/development_guide/js_events.rst:66 +msgid "`kernel\\_interrupting.Kernel <#kernel_interruptingkernel>`__" +msgstr "" + +# f026b24ce61844a0998a46cc46f712dd +#: ../../source/development_guide/js_events.rst:67 +msgid "`kernel\\_killed.Kernel <#kernel_killedkernel>`__" +msgstr "" + +# 8c243948993b422e9ce7979e67bf8806 +#: ../../source/development_guide/js_events.rst:68 +msgid "`kernel\\_killed.Session <#kernel_killedsession>`__" +msgstr "" + +# 50229b3359a24ecdaca9c2121b0f7e8e +#: ../../source/development_guide/js_events.rst:69 +msgid "`kernel\\_ready.Kernel <#kernel_readykernel>`__" +msgstr "" + +# ab8223c68bbe48ee8271e0d69fe60c56 +#: ../../source/development_guide/js_events.rst:70 +msgid "`kernel\\_reconnecting.Kernel <#kernel_reconnectingkernel>`__" +msgstr "" + +# fac3dd7af8514c258e0bf48ff3fea8c3 +#: ../../source/development_guide/js_events.rst:71 +msgid "`kernel\\_restarting.Kernel <#kernel_restartingkernel>`__" +msgstr "" + +# 2a0189d15f2f4cb587ce28f32c98e471 +#: ../../source/development_guide/js_events.rst:72 +msgid "`kernel\\_starting.Kernel <#kernel_startingkernel>`__" +msgstr "" + +# 790b63aed1b04fb0b44083b1531a8a10 +#: ../../source/development_guide/js_events.rst:73 +msgid "`send\\_input\\_reply.Kernel <#send_input_replykernel>`__" +msgstr "" + +# bf0734bc1ee045d7beac313b9b15b5b7 +#: ../../source/development_guide/js_events.rst:74 +msgid "`shell\\_reply.Kernel <#shell_replykernel>`__" +msgstr "" + +# 54b1c3618ccb47aa8e5439b65a594ffe +#: ../../source/development_guide/js_events.rst:75 +msgid "`spec\\_changed.Kernel <#spec_changedkernel>`__" +msgstr "" + +# a2877fd8d7ad42b28685938bc5f7c1be +#: ../../source/development_guide/js_events.rst:78 +msgid "kernel\\_created.Kernel" +msgstr "" + +# 3040632873c245529628ae604083e2e8 +#: ../../source/development_guide/js_events.rst:80 +msgid "" +"The kernel has been successfully created or re-created through " +"``/api/kernels``, but a connection to it has not necessarily been " +"established yet." +msgstr "" + +# 7816516d914c4c1eb141b2becc6478b5 +#: ../../source/development_guide/js_events.rst:85 +msgid "kernel\\_created.Session" +msgstr "" + +# 0367845004434dbab781a2552639d4f4 +#: ../../source/development_guide/js_events.rst:87 +msgid "" +"The kernel has been successfully created or re-created through " +"``/api/sessions``, but a connection to it has not necessarily been " +"established yet." +msgstr "" + +# 72a7c504f85e448ca8fe72c0a32b2c4a +#: ../../source/development_guide/js_events.rst:92 +msgid "kernel\\_reconnecting.Kernel" +msgstr "" + +# 87126ef97bd34214865023e905e33d95 +#: ../../source/development_guide/js_events.rst:94 +msgid "" +"An attempt is being made to reconnect (via websockets) to the kernel " +"after having been disconnected." +msgstr "" + +# 1ec32fcfb4ed408bac1e566e8b97aec0 +#: ../../source/development_guide/js_events.rst:98 +msgid "kernel\\_connected.Kernel" +msgstr "" + +# 5acfc372f6f64cdc87c084c55679f892 +#: ../../source/development_guide/js_events.rst:100 +msgid "" +"A connection has been established to the kernel. This is triggered as " +"soon as all websockets (e.g. to the shell, iopub, and stdin channels) " +"have been opened. This does not necessarily mean that the kernel is ready" +" to do anything yet, though." +msgstr "" + +# 29b6688f9bce412ebbb884ff886068f6 +#: ../../source/development_guide/js_events.rst:106 +msgid "kernel\\_starting.Kernel" +msgstr "" + +# b70c01a2eefc4af2a57708d038debff0 +#: ../../source/development_guide/js_events.rst:108 +msgid "" +"The kernel is starting. This is triggered once when the kernel process is" +" starting up, and can be sent as a message by the kernel, or may be " +"triggered by the frontend if it knows the kernel is starting (e.g., it " +"created the kernel and is connected to it, but hasn't been able to " +"communicate with it yet)." +msgstr "" + +# ec64854942e54e16a0fc04bda832f976 +#: ../../source/development_guide/js_events.rst:115 +msgid "kernel\\_ready.Kernel" +msgstr "" + +# b138893ce9964ff6b4347388855c5ade +#: ../../source/development_guide/js_events.rst:117 +msgid "" +"Like kernel\\_idle.Kernel, but triggered after the kernel has fully " +"started up." +msgstr "" + +# 3ad6f65bcbbb4e1ebd1bbd29c253aa85 +#: ../../source/development_guide/js_events.rst:121 +msgid "kernel\\_restarting.Kernel" +msgstr "" + +# 5b6939501d04409d8860c0faf100b222 +#: ../../source/development_guide/js_events.rst:123 +msgid "" +"The kernel is restarting. This is triggered at the beginning of an " +"restart call to ``/api/kernels``." +msgstr "" + +# 3bdabb293a8a4cdcb236b8349e518532 +#: ../../source/development_guide/js_events.rst:127 +msgid "kernel\\_autorestarting.Kernel" +msgstr "" + +# a41bf1e6a4284693ba02b1d148163713 +#: ../../source/development_guide/js_events.rst:129 +msgid "" +"The kernel is restarting on its own, which probably also means that " +"something happened to cause the kernel to die. For example, running the " +"following code in the notebook would cause the kernel to autorestart:" +msgstr "" + +# fc34e9d75f1941b3ad2ed2530d2a04e7 +#: ../../source/development_guide/js_events.rst:139 +msgid "kernel\\_interrupting.Kernel" +msgstr "" + +# ffc813b955594063b70bb592d70b548f +#: ../../source/development_guide/js_events.rst:141 +msgid "" +"The kernel is being interrupted. This is triggered at the beginning of a " +"interrupt call to ``/api/kernels``." +msgstr "" + +# ccf8af5eed16478796b627d55f104864 +#: ../../source/development_guide/js_events.rst:145 +msgid "kernel\\_disconnected.Kernel" +msgstr "" + +# 3ab698370f4b46968370a25c425567e8 +#: ../../source/development_guide/js_events.rst:147 +msgid "The connection to the kernel has been lost." +msgstr "" + +# 2802009fc67b490584fbd85d24b2882a +#: ../../source/development_guide/js_events.rst:150 +msgid "kernel\\_connection\\_failed.Kernel" +msgstr "" + +# 13c1dbef4b9349b0b838a4256d07143b +#: ../../source/development_guide/js_events.rst:152 +msgid "" +"Not only was the connection lost, but it was lost due to an error (i.e., " +"we did not tell the websockets to close)." +msgstr "" + +# ba8926d5bf55416e8aa6ab5ee053e637 +#: ../../source/development_guide/js_events.rst:156 +msgid "kernel\\_idle.Kernel" +msgstr "" + +# d1f3c042055548dab598e2a4b494c115 +#: ../../source/development_guide/js_events.rst:158 +msgid "The kernel's execution state is 'idle'." +msgstr "" + +# 12539ba4f1724ab5bef3dc6922eba206 +#: ../../source/development_guide/js_events.rst:161 +msgid "kernel\\_busy.Kernel" +msgstr "" + +# 88b1443b9d7d4d9a9102d7014d36313a +#: ../../source/development_guide/js_events.rst:163 +msgid "The kernel's execution state is 'busy'." +msgstr "" + +# 9136374f3b774c08a9acfc0c33fd311a +#: ../../source/development_guide/js_events.rst:166 +msgid "kernel\\_killed.Kernel" +msgstr "" + +# 67232b97369b4224baec2481ad5f4dd0 +#: ../../source/development_guide/js_events.rst:168 +msgid "The kernel has been manually killed through ``/api/kernels``." +msgstr "" + +# f79f7754a4a94c9ca64eaa9152f7b873 +#: ../../source/development_guide/js_events.rst:171 +msgid "kernel\\_killed.Session" +msgstr "" + +# 2da99d85b9ad4167af4cbf22803c0d84 +#: ../../source/development_guide/js_events.rst:173 +msgid "The kernel has been manually killed through ``/api/sessions``." +msgstr "" + +# b011fd6bcdef4824ac275758512959d7 +#: ../../source/development_guide/js_events.rst:176 +msgid "kernel\\_dead.Kernel" +msgstr "" + +# 58190fd19f3843e7b01f0adedbc72a49 +#: ../../source/development_guide/js_events.rst:178 +msgid "" +"This is triggered if the kernel dies, and the kernel manager attempts to " +"restart it, but is unable to. For example, the following code run in the " +"notebook will cause the kernel to die and for the kernel manager to be " +"unable to restart it:" +msgstr "" + +# a07a9dcaa9fa414a87e8bb387d584657 +#: ../../source/development_guide/js_events.rst:192 +msgid "kernel\\_dead.Session" +msgstr "" + +# e50094f75e0e4779bdd5bd9cc231672b +#: ../../source/development_guide/js_events.rst:194 +msgid "" +"The kernel could not be started through ``/api/sessions``. This might be " +"because the requested kernel type isn't installed. Another reason for " +"this message is that the kernel died or was killed, but the session " +"wasn't." +msgstr "" + +# cdb10a3240634a88bcb5ab603db13223 +#: ../../source/development_guide/js_events.rst:200 +msgid "Notebook-related events" +msgstr "" + +# ff5d6d331e274e01bf17ba723380972d +#: ../../source/development_guide/js_events.rst:202 +msgid "`app\\_initialized.NotebookApp <#app_initializednotebookapp>`__" +msgstr "" + +# c890a4f26e0743d28633290be51d4ccc +#: ../../source/development_guide/js_events.rst:203 +msgid "`autosave\\_disabled.Notebook <#autosave_disablednotebook>`__" +msgstr "" + +# 45c56970e40d4a27b4bd50085f013c61 +#: ../../source/development_guide/js_events.rst:204 +msgid "`autosave\\_enabled.Notebook <#autosave_enablednotebook>`__" +msgstr "" + +# 787d5edb4c4e4666b0c1d0b5f194e13a +#: ../../source/development_guide/js_events.rst:205 +msgid "`checkpoint\\_created.Notebook <#checkpoint_creatednotebook>`__" +msgstr "" + +# 0f4a0e636e6e4b5fb64dc4c2cb14a538 +#: ../../source/development_guide/js_events.rst:206 +msgid "" +"`checkpoint\\_delete\\_failed.Notebook " +"<#checkpoint_delete_failednotebook>`__" +msgstr "" + +# 15725ecac791496abcf4ac17f3d8a964 +#: ../../source/development_guide/js_events.rst:207 +msgid "`checkpoint\\_deleted.Notebook <#checkpoint_deletednotebook>`__" +msgstr "" + +# 89e00e136b2f43b6ba5d6ded5606b27b +#: ../../source/development_guide/js_events.rst:208 +msgid "`checkpoint\\_failed.Notebook <#checkpoint_failednotebook>`__" +msgstr "" + +# 458ba96596ea4f3c8e8760f3ff1bff75 +#: ../../source/development_guide/js_events.rst:209 +msgid "" +"`checkpoint\\_restore\\_failed.Notebook " +"<#checkpoint_restore_failednotebook>`__" +msgstr "" + +# 891d9244f3424af0bb816f2d35e8d3a3 +#: ../../source/development_guide/js_events.rst:210 +msgid "`checkpoint\\_restored.Notebook <#checkpoint_restorednotebook>`__" +msgstr "" + +# a087cd1aa32546cdab0c1832cbb53ac2 +#: ../../source/development_guide/js_events.rst:211 +msgid "`checkpoints\\_listed.Notebook <#checkpoints_listednotebook>`__" +msgstr "" + +# afc574cc44784feeba00a72f727b8cce +#: ../../source/development_guide/js_events.rst:212 +msgid "`command\\_mode.Notebook <#command_modenotebook>`__" +msgstr "" + +# 35231218e930429b84217ae364e1a881 +#: ../../source/development_guide/js_events.rst:213 +msgid "`edit\\_mode.Notebook <#edit_modenotebook>`__" +msgstr "" + +# a4e3da5247db4bd9ac0ff46302355b8e +#: ../../source/development_guide/js_events.rst:214 +msgid "" +"`list\\_checkpoints\\_failed.Notebook " +"<#list_checkpoints_failednotebook>`__" +msgstr "" + +# d54d2621b1d848448d7f51b2c0c4abf9 +#: ../../source/development_guide/js_events.rst:215 +msgid "`notebook\\_load\\_failed.Notebook <#notebook_load_failednotebook>`__" +msgstr "" + +# 297dd5a18c3e491abfbf2fc1d198a746 +#: ../../source/development_guide/js_events.rst:216 +msgid "`notebook\\_loaded.Notebook <#notebook_loadednotebook>`__" +msgstr "" + +# abc6ecf1fc8b499fb2b212b8ec45139a +#: ../../source/development_guide/js_events.rst:217 +msgid "`notebook\\_loading.Notebook <#notebook_loadingnotebook>`__" +msgstr "" + +# 1ab9c46f713b4011ae03db3d1565aa99 +#: ../../source/development_guide/js_events.rst:218 +msgid "`notebook\\_rename\\_failed.Notebook <#notebook_rename_failednotebook>`__" +msgstr "" + +# 705d0d6e532a47c8acf6a47bb07b3430 +#: ../../source/development_guide/js_events.rst:219 +msgid "`notebook\\_renamed.Notebook <#notebook_renamednotebook>`__" +msgstr "" + +# 9630174248894aa0bb6b67091c37352a +#: ../../source/development_guide/js_events.rst:220 +msgid "`notebook\\_restoring.Notebook <#notebook_restoringnotebook>`__" +msgstr "" + +# 19d828a32334434482f103cea343d015 +#: ../../source/development_guide/js_events.rst:221 +msgid "`notebook\\_save\\_failed.Notebook <#notebook_save_failednotebook>`__" +msgstr "" + +# d3fcdab1a0ae4813a968084486583389 +#: ../../source/development_guide/js_events.rst:222 +msgid "`notebook\\_saved.Notebook <#notebook_savednotebook>`__" +msgstr "" + +# 1826b5fd328441cd9b281e97e21b8bfc +#: ../../source/development_guide/js_events.rst:223 +msgid "`notebook\\_saving.Notebook <#notebook_savingnotebook>`__" +msgstr "" + +# 14dc21e830634ecbb3120013d479d6a1 +#: ../../source/development_guide/js_events.rst:224 +msgid "`rename\\_notebook.Notebook <#rename_notebooknotebook>`__" +msgstr "" + +# 545d212ebca44e1898c3d4906ae53fb9 +#: ../../source/development_guide/js_events.rst:225 +msgid "" +"`selected\\_cell\\_type\\_changed.Notebook " +"<#selected_cell_type_changednotebook>`__" +msgstr "" + +# bd96bdc9213240ca9c347317afc1bb83 +#: ../../source/development_guide/js_events.rst:226 +msgid "`set\\_dirty.Notebook <#set_dirtynotebook>`__" +msgstr "" + +# 8c289d8ea7d74ff5bd87d081e3c143b3 +#: ../../source/development_guide/js_events.rst:227 +msgid "`set\\_next\\_input.Notebook <#set_next_inputnotebook>`__" +msgstr "" + +# d7f8269d162c425dbce0001d2a0bdffe +#: ../../source/development_guide/js_events.rst:228 +msgid "`trust\\_changed.Notebook <#trust_changednotebook>`__" +msgstr "" + +# 3be14fb7ddaa44f9898f33c9984781a6 +#: ../../source/development_guide/js_events.rst:231 +msgid "Other" +msgstr "" + +# 28cfc866239f4bb0be2907f27c335b2c +#: ../../source/development_guide/js_events.rst:233 +msgid "`open\\_with\\_text.Pager <#open_with_textpager>`__" +msgstr "" + +# 9d0f63ac175a4e06b6060c1b5c0589b9 +#: ../../source/development_guide/js_events.rst:234 +msgid "`rebuild.QuickHelp <#rebuildquickhelp>`__" +msgstr "" + +# 052142391c524dbd9cd3b11b73fbdcf4 +#: ../../source/development_guide/lab_meetings.rst:4 +msgid "Lab Meetings on Air" +msgstr "" + +# 655db7d08bf94cb7b434583f46de9302 +#: ../../source/development_guide/lab_meetings.rst:9 +msgid "" +"Academic labs have long had the tradition of the weekly lab meeting, " +"where all topics of interest to the lab are discussed. IPython has strong" +" roots in academia, but it is also an open source project that needs to " +"engage an active international community. So while our goal with IPython " +"is not to publish the next paper, we've been thinking about the value " +"these regular discussions bring to how teams work on sustained efforts " +"involving difficult problems, and wanted to bring that bit of academic " +"practice into the open source workflow. So we have decided to conduct " +"weekly \"lab meetings\" for IPython, that will be held publicly using a " +"Google Hangout on Air." +msgstr "" + +# b7e924ebaa1442abb4ce8579e7dfb513 +#: ../../source/development_guide/lab_meetings.rst:21 +msgid "Logistics" +msgstr "" + +# 07e6cc2da96b4754b66212a9314e3eb2 +#: ../../source/development_guide/lab_meetings.rst:23 +msgid "" +"We are trying to keep things simple and with a minimum of new moving " +"parts:" +msgstr "" + +# a6bfaf8f74724ff792320a67ceb36788 +#: ../../source/development_guide/lab_meetings.rst:26 +msgid "" +"Meetings happen on Tuesdays at 10am California time (i.e. UTC-8 or -7 " +"depending on the time of year)." +msgstr "" + +# 2872a2e95c9c4eca8e795423ba1dbc40 +#: ../../source/development_guide/lab_meetings.rst:28 +msgid "" +"We broadcast the meeting as it happens via G+ and leave the public " +"YouTube link afterwards." +msgstr "" + +# cb7960e779de46a393549f9b14437b25 +#: ../../source/development_guide/lab_meetings.rst:30 +msgid "" +"During the meeting, all chat that needs to happen by typing can be done " +"on our `Gitter chat room `__." +msgstr "" + +# 75e889a166a94bb3a0358a1465121a4b +#: ../../source/development_guide/lab_meetings.rst:33 +msgid "" +"We keep a running document with `minutes of the meeting on HackPad " +"`__ where we summarize main points. (`2015 " +"part 1 `__)" +msgstr "" + +# 7ee9bd48be064c18b6f1c952e070a66d +#: ../../source/development_guide/lab_meetings.rst:37 +msgid "" +"We welcome and encourage help from others in updating these minutes " +"during the meeting, but we'll make no major effort in ensuring that they " +"are a detailed and accurate record of the whole discussion. We simply " +"don't have the time for that." +msgstr "" + +# 425913e731c54469be844019d93a0581 +#: ../../source/development_guide/lab_meetings.rst:43 +msgid "Prior meetings" +msgstr "" + +# 05fd7d7f121346c290fd8ce8550118bf +#: ../../source/development_guide/lab_meetings.rst:45 +msgid "" +"You can find a list of the videos on the `ipythondev YouTube user page " +"`__." +msgstr "" + +# d512e27aff344444aae5dfaf62a1a9c2 +#: ../../source/development_guide/less.rst:4 +msgid "How to Compile .less Files" +msgstr "" + +# ad2b306908b048c6bdec64929c3d6c15 +#: ../../source/development_guide/less.rst:9 +msgid "" +"For testing your development work in CSS, you'll need to compile the " +".less files to CSS. Make sure you have dependencies that LESS requires, " +"including fabric, node, and lessc. Follow the below steps to compile the " +".less files:" +msgstr "" + +# 515ed293377b44b88d86fd11e6cb76f8 +#: ../../source/development_guide/less.rst:18 +msgid "Alternatively, you can:" +msgstr "" + +# f66d911ce52644939f54e1c4cfa7cdd0 +#: ../../source/development_guide/pull_request.rst:4 +msgid "The Perfect Pull Request" +msgstr "" + +# 89a81be294c9411c8f07631085687f58 +#: ../../source/development_guide/pull_request.rst:9 +msgid "A brief guide to making and reviewing pull requests." +msgstr "" + +# 223a61361a9d42d19e8f544bbed9ede8 +#: ../../source/development_guide/pull_request.rst:12 +msgid "1. It works" +msgstr "" + +# ee97d94a227d426a91e8cf8eb7fac5fd +#: ../../source/development_guide/pull_request.rst:14 +msgid "The code does what it's supposed to!" +msgstr "" + +# 7191fb41b3f446c2b047ca063a5e4356 +#: ../../source/development_guide/pull_request.rst:17 +msgid "2. It works on all of the platforms that IPython officially supports" +msgstr "" + +# 88d94c97480c46a98e8ee9c20f7d521c +#: ../../source/development_guide/pull_request.rst:19 +msgid "IPython has to work on:" +msgstr "" + +# a330b995df754c6db1c6d675a7f71ec2 +#: ../../source/development_guide/pull_request.rst:21 +msgid "Linux of various kinds, Windows & Mac" +msgstr "" + +# 0982b10a11ac4969ad699d4c552c26a2 +#: ../../source/development_guide/pull_request.rst:22 +msgid "Python 2 & 3" +msgstr "" + +# dae2ad7446ea4d9daade79e4c60bc60a +#: ../../source/development_guide/pull_request.rst:25 +msgid "3. Handles unicode issues properly" +msgstr "" + +# fd066b3664f148a6b16e1cec798ad3ca +#: ../../source/development_guide/pull_request.rst:27 +msgid "" +"Much of our code base deals with strings and unicode. This needs to be " +"done in a manner that is unicode aware and works on Python 2 and 3. [This" +" article] (http://www.joelonsoftware.com/articles/Unicode.html) is a good" +" intro to unicode." +msgstr "" + +# 2e6a238797d34b35a2e3ccd7363775d8 +#: ../../source/development_guide/pull_request.rst:33 +msgid "4. Adheres to our coding style" +msgstr "" + +# 6cf5f6068ddc420d91eef5c6aac49a51 +#: ../../source/development_guide/pull_request.rst:35 +msgid "" +"Coding style refers to how source code is formatted and how variables, " +"functions, methods and classes are named. Your code should follow our " +"coding style, which is described [[here\\|Dev: Coding style]]." +msgstr "" + +# 414e07fca966418d833f8e539fa75dd5 +#: ../../source/development_guide/pull_request.rst:40 +msgid "5. Clean & commented" +msgstr "" + +# 3fd8703e90d14aff80b997e371af9e5b +#: ../../source/development_guide/pull_request.rst:42 +msgid "" +"The code should be well organized, and have inline comments where " +"appropriate. When we look at the code, it should be clear what it's doing" +" and why. It should not break abstractions that we have established in " +"the project." +msgstr "" + +# 755c8ba81fe34db1a85d015bb87412f2 +#: ../../source/development_guide/pull_request.rst:48 +msgid "6. Tested" +msgstr "" + +# b74b1c16fc754989b663b171b313d43d +#: ../../source/development_guide/pull_request.rst:50 +msgid "" +"If it fixes a bug, the pull request should ideally add an automated test " +"that fails without the fix, and passes with it. Normally it should be " +"sufficient to copy an existing test and tweak it. New functionality " +"should come with its own tests as well. Details about testing IPython can" +" be found [[here\\|Dev: Testing]]." +msgstr "" + +# 16f7363d77e5489f9ce488ca4a26f71d +#: ../../source/development_guide/pull_request.rst:57 +msgid "7. Well documented" +msgstr "" + +# ba75b92346094faa90b2e78c95c69a98 +#: ../../source/development_guide/pull_request.rst:59 +msgid "" +"Don't forget to update docstrings, and any relevant parts of `the " +"official documentation `__. " +"New features or significant changes warrant an entry in the *What's New* " +"section too. Details about documenting IPython can be found [[here\\|Dev:" +" Documenting IPython]]." +msgstr "" + +# d854f6fc89a64ddcb42f0a9a55973b77 +#: ../../source/development_guide/py3compat.rst:4 +msgid "Python 3 Compatibility Module" +msgstr "" + +# c004d43c8f534c84a82ec4fef2b5b1df +#: ../../source/development_guide/py3compat.rst:9 +msgid "" +"The ``IPython.utils.py3compat`` module provides a number of functions to " +"make it easier to write code for Python 2 and 3. We also use 2to3 in the " +"setup process to change syntax, and the ``io.open()`` function, which is " +"essentially the built in open function from Python 3." +msgstr "" + +# b192dadb5475442db1b2a0490e225483 +#: ../../source/development_guide/py3compat.rst:11 +msgid "The names provided are:" +msgstr "" + +# 30de9621716043538db5664d131cb897 +#: ../../source/development_guide/py3compat.rst:13 +msgid "**PY3**: True in Python 3, False in Python 2." +msgstr "" + +# 8f5c3e60ac0747f2b79902da7a2bdae3 +#: ../../source/development_guide/py3compat.rst:16 +msgid "Unicode related" +msgstr "" + +# b6a2d35346a64709aa527b4abda7d7ee +#: ../../source/development_guide/py3compat.rst:17 +msgid "" +"**decode**, **encode**: Shortcuts to decode or encode strings, using " +"``sys.stdin.encoding`` by default, and using replacement characters on " +"errors." +msgstr "" + +# 73ee89f9102a4788baa41e5b229a9562 +#: ../../source/development_guide/py3compat.rst:18 +msgid "" +"**str_to_unicode**, **unicode_to_str**, **str_to_bytes**, " +"**bytes_to_str**: Convert to/from the platform's standard ``str`` type " +"(bytes in Python 2, unicode in Python 3). Each function is a no-op on one" +" of the two platforms." +msgstr "" + +# a1dee6dc1a2c46c8a5ec2956070e3a10 +#: ../../source/development_guide/py3compat.rst:19 +msgid "" +"**cast_unicode**, **cast_bytes**: Accept unknown unicode or byte strings," +" and convert them accordingly." +msgstr "" + +# 47bc77989e70427ba4a7cc1cafd7915b +#: ../../source/development_guide/py3compat.rst:20 +msgid "" +"**cast_bytes_py2**: Casts unicode to byte strings on Python 2, but " +"doesn't do anything on Python 3." +msgstr "" + +# 4e8dd403d59b46b9bdb3d5a502311b1b +# 80822ca0571045df983fab67282f3c6d +#: ../../source/development_guide/py3compat.rst:23 +#: ../../source/development_guide/rest_api.rst:20 +msgid "Miscellaneous" +msgstr "" + +# cb19d92f73c243b89006254015d4035b +#: ../../source/development_guide/py3compat.rst:24 +msgid "" +"**input**: Refers to ``raw_input`` on Python 2, ``input`` on Python 3 " +"(needed because 2to3 only converts calls to raw_input, not assignments to" +" other names)." +msgstr "" + +# f998ff129b49488897a174f56cf0a528 +#: ../../source/development_guide/py3compat.rst:25 +msgid "" +"**builtin_mod_name**: The string name you import to get the builtins " +"(``__builtin__`` --> ``builtins``)." +msgstr "" + +# 59da6755c02d48118c18d89fce1aa672 +#: ../../source/development_guide/py3compat.rst:26 +msgid "**isidentifier**: Checks if a string is a valid Python identifier." +msgstr "" + +# 871668c2bc504ea298b8e5b945f27fad +#: ../../source/development_guide/py3compat.rst:27 +msgid "" +"**open**: Simple wrapper for Python 3 unicode-enabled open. Similar to " +"``codecs.open``, but allows universal newlines. The current " +"implementation only supports the very simplest use." +msgstr "" + +# 43c6fddb42a946f0b38d44892e529478 +#: ../../source/development_guide/py3compat.rst:28 +msgid "" +"**MethodType**: ``types.MethodType`` from Python 3. Takes only two " +"arguments: function, instance. The class argument for Python 2 is filled " +"automatically." +msgstr "" + +# d94ea732977d42438b860b989f2a313c +#: ../../source/development_guide/py3compat.rst:29 +msgid "" +"**doctest_refactor_print**: Can be called on a string or a function (or " +"used as a decorator). In Python 3, it converts print statements in " +"doctests to print() calls. 2to3 does this for real doctests, but we need " +"it in several other places. It simply uses a regex, which is good enough " +"for the current cases." +msgstr "" + +# e25ce2b110e44536a7af4a448c4eaa6f +#: ../../source/development_guide/py3compat.rst:30 +msgid "" +"**u_format**: Where tests use the repr() of a unicode string, it should " +"be written ``'{u}\"thestring\"'``, and fed to this function, which will " +"produce ``'u\"thestring\"'`` for Python 2, and ``'\"thestring\"'`` for " +"Python 3. Can also be used as a decorator, to work on a docstring." +msgstr "" + +# 679faf609998417083db36b8e8a04382 +#: ../../source/development_guide/py3compat.rst:31 +msgid "" +"**execfile**: Makes a return on Python 3 (where it's no longer a " +"builtin), and upgraded to handle Unicode filenames on Python 2." +msgstr "" + +# 6070e9e6628b4aa09ed6655604054931 +#: ../../source/development_guide/releasing.rst:4 +msgid "Steps for Releasing IPython" +msgstr "" + +# 474fc1460c5b4777abee30aa86907ed6 +#: ../../source/development_guide/releasing.rst:9 +msgid "" +"This document contains notes about the process that is used to release " +"IPython. Our release process is currently not very formal and could be " +"improved." +msgstr "" + +# c1f41e0fa6da4994b9b19379eb2bc23f +#: ../../source/development_guide/releasing.rst:13 +msgid "" +"Most of the release process is automated by the ``release`` script in the" +" ``tools`` directory of our main repository. This document is just a " +"handy reminder for the release manager." +msgstr "" + +# a9b95a6e657e46b28c6e52dbcc201a18 +#: ../../source/development_guide/releasing.rst:18 +msgid "0. Environment variables" +msgstr "" + +# 8d5be193613e4256b862d9f8e07041fa +#: ../../source/development_guide/releasing.rst:20 +msgid "" +"You can set some env variables to note previous release tag and current " +"release milestone, version, and git tag:" +msgstr "" + +# de9c9247cc124e2893d9ec0f227a643d +#: ../../source/development_guide/releasing.rst:31 +msgid "" +"These will be used later if you want to copy/paste, or you can just type " +"the appropriate command when the time comes. These variables are not used" +" by scripts (hence no ``export``)." +msgstr "" + +# 6c0a769309184688b2fb014ff2f8c796 +#: ../../source/development_guide/releasing.rst:36 +msgid "1. Finish release notes" +msgstr "" + +# e869e1ec6f9742c8bf23bacb602a60b9 +#: ../../source/development_guide/releasing.rst:38 +msgid "If a major release:" +msgstr "" + +# 666b2be953434d93bb878827050ab63d +#: ../../source/development_guide/releasing.rst:40 +msgid "merge any pull request notes into what's new:" +msgstr "" + +# 3724968cf84e4e99b20121379514a4e0 +#: ../../source/development_guide/releasing.rst:46 +msgid "" +"update ``docs/source/whatsnew/development.rst``, to ensure it covers the " +"major points." +msgstr "" + +# 75183279a5dc4eba93af2a9c26039722 +#: ../../source/development_guide/releasing.rst:48 +msgid "move the contents of ``development.rst`` to ``versionX.rst``" +msgstr "" + +# c24f0f091e7949f3bf48de122e6334af +#: ../../source/development_guide/releasing.rst:49 +msgid "generate summary of GitHub contributions, which can be done with:" +msgstr "" + +# 4b8b45a7487a4bd4b31ae0b9d16bd8d0 +#: ../../source/development_guide/releasing.rst:55 +msgid "" +"which may need some manual cleanup. Add the cleaned up result and add it " +"to ``docs/source/whatsnew/github-stats-X.rst`` (make a new file, or add " +"it to the top, depending on whether it is a major release). You can use:" +msgstr "" + +# 843c53e7f17142a09ae961e46c0cfa4d +#: ../../source/development_guide/releasing.rst:63 +msgid "" +"to find duplicates and update ``.mailmap``. Before generating the GitHub " +"stats, verify that all closed issues and pull requests :ref:`have " +"appropriate milestones `. `This search " +"`__" +" should return no results." +msgstr "" + +# 73753e8a58e34787817ed3238ed82716 +#: ../../source/development_guide/releasing.rst:71 +msgid "2. Run the ``tools/build_release`` script" +msgstr "" + +# 16ac313a93e049638a7f863d317ce63f +#: ../../source/development_guide/releasing.rst:73 +msgid "" +"This does all the file checking and building that the real release script" +" will do. This will let you do test installations, check that the build " +"procedure runs OK, etc. You may want to also do a test build of the docs." +msgstr "" + +# e7ffacc8c81a4834a14d0b314e17690b +#: ../../source/development_guide/releasing.rst:79 +msgid "3. Create and push the new tag" +msgstr "" + +# b8b0871867cd4fcc80b3e368e4d95844 +#: ../../source/development_guide/releasing.rst:81 +msgid "Edit ``IPython/core/release.py`` to have the current version." +msgstr "" + +# 3c370bad39e746c39111430ccc936310 +#: ../../source/development_guide/releasing.rst:83 +msgid "Commit the changes to release.py and jsversion:" +msgstr "" + +# 76be04383e184e9da329e3aa0d098a3c +#: ../../source/development_guide/releasing.rst:90 +msgid "Create and push the tag:" +msgstr "" + +# 507ccfbc828145e9b0d1d4dfee83d563 +#: ../../source/development_guide/releasing.rst:97 +msgid "Update release.py back to ``x.y-dev`` or ``x.y-maint``, and push:" +msgstr "" + +# 4877cb8b2c564ce5bd36962492de8d10 +#: ../../source/development_guide/releasing.rst:105 +msgid "4. Get a fresh clone of the tag for building the release:" +msgstr "" + +# f52cc49dec9346f1b0c98b00a01785d9 +#: ../../source/development_guide/releasing.rst:113 +msgid "5. Run the ``release`` script" +msgstr "" + +# cec8d17770c84efca03630775ab98d9d +#: ../../source/development_guide/releasing.rst:119 +msgid "" +"This makes the tarballs, zipfiles, and wheels. It posts them to " +"archive.ipython.org and registers the release with PyPI." +msgstr "" + +# f1685ede7c474aac941535883e418b17 +#: ../../source/development_guide/releasing.rst:122 +msgid "This will require that you have current wheel, Python 3.4 and Python 2.7." +msgstr "" + +# 9a7908665a6b48459d926aaf5bde37ef +#: ../../source/development_guide/releasing.rst:126 +msgid "7. Update the IPython website" +msgstr "" + +# 84184061981f4f93a42f63d827dc1374 +#: ../../source/development_guide/releasing.rst:128 +msgid "release announcement (news, announcements)" +msgstr "" + +# 107c03099a624fa686299b8bd37f9f80 +#: ../../source/development_guide/releasing.rst:129 +msgid "update current version and download links" +msgstr "" + +# ee281737c90c44458452d4dceae0f9ad +#: ../../source/development_guide/releasing.rst:130 +msgid "(If major release) update links on the documentation page" +msgstr "" + +# 7e0ab94df3f949269ccc4e70aa69f593 +#: ../../source/development_guide/releasing.rst:133 +msgid "8. Drafting a short release announcement" +msgstr "" + +# 36d7bb70789c43c8b561212dfb878412 +#: ../../source/development_guide/releasing.rst:135 +msgid "" +"This should include i) highlights and ii) a link to the html version of " +"the *What's new* section of the documentation." +msgstr "" + +# 8182a6c415a44cedb150dcf452395ea9 +#: ../../source/development_guide/releasing.rst:138 +msgid "Post to mailing list, and link from Twitter." +msgstr "" + +# 5b55b0e918cc4d15a5f839aea3cb8a98 +#: ../../source/development_guide/releasing.rst:141 +msgid "9. Update milestones on GitHub" +msgstr "" + +# 816cc83ee1b345a78effb459097dc99e +#: ../../source/development_guide/releasing.rst:143 +msgid "close the milestone you just released" +msgstr "" + +# 5f3da01008e84e7aaf469cda8e6b8899 +#: ../../source/development_guide/releasing.rst:144 +msgid "open new milestone for (x, y+1), if it doesn't exist already" +msgstr "" + +# 00455207637744b5a45442f59ea981a9 +#: ../../source/development_guide/releasing.rst:147 +msgid "10. Celebrate!" +msgstr "" + +# 8cfab3dcdbf94612acc47b332d1b3feb +#: ../../source/development_guide/rest_api.rst:4 +msgid "Architecture of IPython notebook's Dashboard" +msgstr "" + +# e1e8a4f3cb2e41ac8593e4fc18d62d01 +#: ../../source/development_guide/rest_api.rst:9 +msgid "" +"The tables below show the current RESTful web service architecture " +"implemented in IPython notebook. The listed URL's use the HTTP verbs to " +"return representations of the desired resource." +msgstr "" + +# 2bc47a02cbd945568fb33dc9224b0f07 +#: ../../source/development_guide/rest_api.rst:13 +msgid "" +"We are in the process of creating a new dashboard architecture for the " +"IPython notebook, which will allow the user to navigate through multiple " +"directory files to find desired notebooks." +msgstr "" + +# 4fdebc16479d422b8922fb8f9fce7cc5 +#: ../../source/development_guide/rest_api.rst:18 +msgid "Current Architecture" +msgstr "" + +# fe498a404e0a4c30ae3e620b1d10cc34 +# 9ec2dc9f4138483bb35b689d665d6639 +# b3c5e3a8af40456783a930038b3c4809 +# 98e0a158be994fd88c0bedf17a6b36ae +# 6e16b609a4ed40f7a2290b0eb520d729 +# fb83ef26d0b44c429af002716f4abdc7 +# 9b2ccd8da72441869fea8111af33760c +# 96da17585dfd4826bffb704c0793263d +#: ../../source/development_guide/rest_api.rst:23 +#: ../../source/development_guide/rest_api.rst:38 +#: ../../source/development_guide/rest_api.rst:112 +#: ../../source/development_guide/rest_api.rst:145 +#: ../../source/development_guide/rest_api.rst:169 +#: ../../source/development_guide/rest_api.rst:189 +#: ../../source/development_guide/rest_api.rst:212 +#: ../../source/development_guide/rest_api.rst:242 +msgid "HTTP verb" +msgstr "" + +# e82c6c0b009d44669ddc88b336f64581 +# 7bd84f2c31bb407293fcfa5046887b9d +# 96d32c89f5ca4ab8a563425ba6b8065e +# 1fbabf44108c41ddb9ed1872f64855c7 +# 229067f6b1ff4d939c63260bd2e3fe20 +# 7ddac55fc7ea4abda4866b2bf48d8019 +# 74921be61dbf48f8a7c10d2ea8bfcdea +#: ../../source/development_guide/rest_api.rst:23 +#: ../../source/development_guide/rest_api.rst:38 +#: ../../source/development_guide/rest_api.rst:145 +#: ../../source/development_guide/rest_api.rst:169 +#: ../../source/development_guide/rest_api.rst:189 +#: ../../source/development_guide/rest_api.rst:212 +#: ../../source/development_guide/rest_api.rst:242 +msgid "URL" +msgstr "" + +# de2ab75d45694fb984403d78fddeaca2 +# deb3e95c78574322a84329ee678366dd +# 9361819f0837429babf92f04c4595287 +# 7a06c5af6c6f4f8cb20893c23c5936f3 +# 32c8b21b1d474f68acf0742198d18634 +# f0d3556b5b834db28df348b1f153db64 +# b9924939f4d34b9eab2effd17d29121b +# 2eb6a4f4943d48fea7dab628f14d222e +#: ../../source/development_guide/rest_api.rst:23 +#: ../../source/development_guide/rest_api.rst:38 +#: ../../source/development_guide/rest_api.rst:112 +#: ../../source/development_guide/rest_api.rst:145 +#: ../../source/development_guide/rest_api.rst:169 +#: ../../source/development_guide/rest_api.rst:189 +#: ../../source/development_guide/rest_api.rst:212 +#: ../../source/development_guide/rest_api.rst:242 +msgid "Action" +msgstr "" + +# 763401d3039247d79e58ce1ec12fd518 +# 5afcd411ddb747738c3352f5189e036e +# 78df1bb43b284a90a495991bf9d3e890 +# ab0547f84b784914bedd133e870b0057 +# 6cecf55719c145c9ae0796cbb378ac92 +# 4c4b2d742a8e4ea19985b66a37bb67a7 +# d27bb38bd52b4a6593a520840121b7ac +# 5d1afd0c0a934b6bbd21eb57e7e7cbc7 +# fe6be4c15d914e3bbbf61432eee841ad +# c487a63b691042b59b1f83490001ce47 +# 14c8617aa9b3490ab38b80f37f3fcf4c +# 08f7c8eb565445b180c2fd363fa0f054 +# 50663441342e4b959bceae65ee26c8f6 +# 741a15dfa12a4f38b3f93bfb536647fb +# f1181df2b3154c76bc292c53aa05391e +# 91931ae80d9f490c850685d2db412081 +# 6037f22576504cb3a6fc7c3010dc2192 +# bd10507b0d50427782417823e54cd3be +# cb2f272b24ce45bc894c2946f1267dcc +# 480cf3b73cc148d7ad7bf74c6c263c55 +# 23b5ee04c60745ddbdcdf2cfd2219e93 +# 73c5e9f321b34b6abd5421f2b40285a1 +# 51cbcb5b73ea4c19ab76aef565c16595 +# b488e84daab844beb51647a2057fc030 +# bf3bc78ec5ab439d9c8d693b0f0491f5 +# de5dc5031a1e4aa4be45a7414af059b0 +# be05eeb20901486d80386c7ee69aa827 +# 5e2686db0ed743cdba7ef66620ee9939 +# 657ece27d618456b8c1d6c33ddf1f800 +# 3428328645e242ea89296246917f99f4 +# b72e3436c8de4d38ae7000fabba5d221 +# 33784dfc6de24eea92bd419c1a486195 +# 5386f0dbdf2c4ec99c19ff3369bd4a78 +#: ../../source/development_guide/rest_api.rst:26 +#: ../../source/development_guide/rest_api.rst:28 +#: ../../source/development_guide/rest_api.rst:32 +#: ../../source/development_guide/rest_api.rst:41 +#: ../../source/development_guide/rest_api.rst:44 +#: ../../source/development_guide/rest_api.rst:48 +#: ../../source/development_guide/rest_api.rst:88 +#: ../../source/development_guide/rest_api.rst:115 +#: ../../source/development_guide/rest_api.rst:117 +#: ../../source/development_guide/rest_api.rst:134 +#: ../../source/development_guide/rest_api.rst:137 +#: ../../source/development_guide/rest_api.rst:148 +#: ../../source/development_guide/rest_api.rst:155 +#: ../../source/development_guide/rest_api.rst:172 +#: ../../source/development_guide/rest_api.rst:174 +#: ../../source/development_guide/rest_api.rst:192 +#: ../../source/development_guide/rest_api.rst:199 +#: ../../source/development_guide/rest_api.rst:215 +#: ../../source/development_guide/rest_api.rst:218 +#: ../../source/development_guide/rest_api.rst:220 +#: ../../source/development_guide/rest_api.rst:224 +#: ../../source/development_guide/rest_api.rst:227 +#: ../../source/development_guide/rest_api.rst:231 +#: ../../source/development_guide/rest_api.rst:235 +#: ../../source/development_guide/rest_api.rst:245 +#: ../../source/development_guide/rest_api.rst:248 +#: ../../source/development_guide/rest_api.rst:251 +#: ../../source/development_guide/rest_api.rst:255 +#: ../../source/development_guide/rest_api.rst:259 +#: ../../source/development_guide/rest_api.rst:263 +#: ../../source/development_guide/rest_api.rst:266 +#: ../../source/development_guide/rest_api.rst:268 +#: ../../source/development_guide/rest_api.rst:276 +msgid "``GET``" +msgstr "" + +# dffd12ae712b43ce8d6cf80d826c8017 +#: ../../source/development_guide/rest_api.rst:26 +msgid "/.\\*/\\" +msgstr "" + +# 5ce071fb24d14854b986d15e69e2114e +#: ../../source/development_guide/rest_api.rst:26 +msgid "Strips trailing slashes." +msgstr "" + +# 1a776f1e82e44612aa2fdec9644afe9e +#: ../../source/development_guide/rest_api.rst:28 +msgid "\\/api\\" +msgstr "" + +# cbed5e8bbde04a74aa860b0dbf7e4880 +#: ../../source/development_guide/rest_api.rst:28 +msgid "Returns api version information." +msgstr "" + +# 486f00bc379041ddb7f6fcdbd9e95e7d +#: ../../source/development_guide/rest_api.rst:30 +msgid "``*``" +msgstr "" + +# feff0224746046688e5c25ff5c3c6171 +#: ../../source/development_guide/rest_api.rst:30 +msgid "\\/api/notebooks" +msgstr "" + +# 01a8e34b3a694b098bb91525785b7e36 +#: ../../source/development_guide/rest_api.rst:30 +msgid "Deprecated: redirect to /api/contents" +msgstr "" + +# d8dabd59231844c6ad324fc4d271e6af +#: ../../source/development_guide/rest_api.rst:32 +msgid "\\/api/nbconvert" +msgstr "" + +# dacbd2c6987f42409c2feb109d0dde44 +#: ../../source/development_guide/rest_api.rst:35 +msgid "Notebook contents API." +msgstr "" + +# aef631b0aed447688207bd806340cd63 +#: ../../source/development_guide/rest_api.rst:41 +msgid "/api/contents" +msgstr "" + +# f5cde97e47e548379614ab3affbdddf0 +#: ../../source/development_guide/rest_api.rst:41 +msgid "Return a model for the base directory. See /api/contents//." +msgstr "" + +# 1448b28828454b7d9d1ed2853bcaf819 +#: ../../source/development_guide/rest_api.rst:44 +msgid "/api/contents/ " +msgstr "" + +# 3c765646a94f4d75a4d7c5ad89e8fe42 +#: ../../source/development_guide/rest_api.rst:44 +msgid "" +"Return a model for the given file in the base directory. See " +"/api/contents//." +msgstr "" + +# a4605641dd4f4cfebfe87b0155e422b2 +# 1e7d59f407dd49099f7351c0553beac9 +# 712b8ef05e294ee0b1b61e14ac733a19 +# 13225189dbd94717a156bab23927b5a1 +# 1d9baa4d593b4548af6606a84a2d2731 +#: ../../source/development_guide/rest_api.rst:48 +#: ../../source/development_guide/rest_api.rst:53 +#: ../../source/development_guide/rest_api.rst:70 +#: ../../source/development_guide/rest_api.rst:73 +#: ../../source/development_guide/rest_api.rst:85 +msgid "/api/contents/ /" +msgstr "" + +# ed7bc4dabc754ad697cb7d97b98947f9 +#: ../../source/development_guide/rest_api.rst:48 +msgid "" +"Return a model for a file or directory. A directory model contains a list" +" of models (without content) of the files and directories it contains." +msgstr "" + +# dfd73d904a7d4864aacd914ec6e2d4a3 +# 6eed25236c154ee7af6ba6c83fb8edaf +#: ../../source/development_guide/rest_api.rst:53 +#: ../../source/development_guide/rest_api.rst:202 +msgid "``PUT``" +msgstr "" + +# eb1c17f460184abe9577e7513ecd048e +#: ../../source/development_guide/rest_api.rst:53 +msgid "" +"Saves the file in the location specified by name and path. PUT is very " +"similar to POST, but the requester specifies the name, where as with " +"POST, the server picks the name. PUT /api/contents/path/Name.ipynb Save " +"notebook at ``path/Name.ipynb``. Notebook structure is specified in " +"``content`` key of JSON request body. If content is not specified, create" +" a new empty notebook. PUT /api/contents/path/Name.ipynb with JSON body " +"{\"copy\\_from\" : \"[path/to/] OtherNotebook.ipynb\"} Copy OtherNotebook" +" to Name" +msgstr "" + +# ceb6808281824129852733d7c9e4eeb5 +# 5625ae0380c34bc090c776621551f97e +#: ../../source/development_guide/rest_api.rst:70 +#: ../../source/development_guide/rest_api.rst:158 +msgid "``PATCH``" +msgstr "" + +# 75933adea4084527b478230d805980a3 +#: ../../source/development_guide/rest_api.rst:70 +msgid "Renames a notebook without re-uploading content." +msgstr "" + +# 17c634548eb74c01a0dc92e4f58f49b4 +# caf03f3932b148388a33c42c74810505 +# fa50085f68ac4687be99cc75d2422897 +# 9d82e240de48406fa0d56bf23cc5c36c +# d10b01d8ba9242d28457c629dba7ab6a +# aaced630d1a043d7aed4dcba55b355e1 +# db725a152cba4888803919aec39c9ec6 +# 1fae8fe1e28345118a5d9c21b4b17854 +# 9961f9c83d9d4eceb9c2d7c49f3dfe62 +#: ../../source/development_guide/rest_api.rst:73 +#: ../../source/development_guide/rest_api.rst:92 +#: ../../source/development_guide/rest_api.rst:96 +#: ../../source/development_guide/rest_api.rst:120 +#: ../../source/development_guide/rest_api.rst:126 +#: ../../source/development_guide/rest_api.rst:150 +#: ../../source/development_guide/rest_api.rst:177 +#: ../../source/development_guide/rest_api.rst:195 +#: ../../source/development_guide/rest_api.rst:271 +msgid "``POST``" +msgstr "" + +# 0536f641b6934319af698bda9cedf4e7 +#: ../../source/development_guide/rest_api.rst:73 +msgid "" +"Creates a new file or directory in the specified path. POST creates new " +"files or directories. The server always decides on the name. POST " +"/api/contents/path New untitled notebook in path. If content specified, " +"upload a notebook, otherwise start empty. POST /api/contents/path with " +"body {\"copy\\_from\":\"OtherNotebook.ipynb\"} New copy of OtherNotebook " +"in path" +msgstr "" + +# d44cc798e58e4cad9b54269ba21156ad +# ef7cfa1704f143d092483ccd5da72212 +# 30b3b06e66a24d61a5b24a611ccc0230 +# 9e98d4862452477c8ce4249aac75162e +# 6c47ab0a66b644d28ac57748a4937e45 +#: ../../source/development_guide/rest_api.rst:85 +#: ../../source/development_guide/rest_api.rst:102 +#: ../../source/development_guide/rest_api.rst:123 +#: ../../source/development_guide/rest_api.rst:162 +#: ../../source/development_guide/rest_api.rst:205 +msgid "``DELETE``" +msgstr "" + +# 9ceef3bacd5340ad8d5aeec1466a076b +#: ../../source/development_guide/rest_api.rst:85 +msgid "delete a file in the given path." +msgstr "" + +# 202361a1c09e47c2ad83579b433f5f4f +# 15dde1b4832b42e7ad20afa5bee4e930 +#: ../../source/development_guide/rest_api.rst:88 +#: ../../source/development_guide/rest_api.rst:92 +msgid "/api/contents/ / /checkpoints" +msgstr "" + +# 05ec1d01737d4688a6567dbaa710c7c3 +#: ../../source/development_guide/rest_api.rst:88 +msgid "get lists checkpoint for a file." +msgstr "" + +# ca6e8400ef244624b6839870077fd6e3 +#: ../../source/development_guide/rest_api.rst:92 +msgid "post creates a new checkpoint." +msgstr "" + +# 992ccde95573448aa6f41302d413bb40 +# a8be10f1246244ed965f085222bf11ff +#: ../../source/development_guide/rest_api.rst:96 +#: ../../source/development_guide/rest_api.rst:102 +msgid "/api/contents/ / /checkpoints/ " +msgstr "" + +# 2cd3d316ad3441c7b0d552eb718b6d28 +#: ../../source/development_guide/rest_api.rst:96 +msgid "post restores a file from a checkpoint." +msgstr "" + +# 5bfe5a66d89d446fb55eb87325c487f3 +#: ../../source/development_guide/rest_api.rst:102 +msgid "delete clears a checkpoint for a given file." +msgstr "" + +# a15416a2e61a4aaab583905d4af0963f +#: ../../source/development_guide/rest_api.rst:109 +msgid "Kernel API" +msgstr "" + +# c83393dead364609ba046887ad58eda4 +#: ../../source/development_guide/rest_api.rst:112 +msgid "URI" +msgstr "" + +# a22a8dde569a49fdaabee69c4c8a4922 +# 9ce37afd4749427b86a9bdb405154753 +#: ../../source/development_guide/rest_api.rst:115 +#: ../../source/development_guide/rest_api.rst:120 +msgid "/api/kernels" +msgstr "" + +# 61ec1cbf32c64bbfb1ea3eaa0d19192c +#: ../../source/development_guide/rest_api.rst:115 +msgid "Return a model of all kernels." +msgstr "" + +# ef7ea762242943969ec5c1e7cea1eada +# 31cfc33080984d38b979a875687f4a62 +#: ../../source/development_guide/rest_api.rst:117 +#: ../../source/development_guide/rest_api.rst:123 +msgid "/api/kernels /" +msgstr "" + +# 3547722485614d43b0f8342ef19860bd +#: ../../source/development_guide/rest_api.rst:117 +msgid "Return a model of kernel with given kernel id." +msgstr "" + +# 50a8cf2db9a44b2d8bd1229939621a61 +#: ../../source/development_guide/rest_api.rst:120 +msgid "Start a new kernel with default or given name." +msgstr "" + +# 5e1f9fc90a784841ac614c10dc3516db +#: ../../source/development_guide/rest_api.rst:123 +msgid "Shutdown the given kernel." +msgstr "" + +# aba500823d0a4193996e93e699a48012 +#: ../../source/development_guide/rest_api.rst:126 +msgid "/api/kernels / /" +msgstr "" + +# f15d513346c34e96b482db11c73ebe2f +#: ../../source/development_guide/rest_api.rst:126 +msgid "" +"Perform action on kernel with given kernel id. Actions can be " +"\"interrupt\" or \"restart\"." +msgstr "" + +# 60b68955ab9746548149c88070e09d1b +#: ../../source/development_guide/rest_api.rst:130 +msgid "``WS``" +msgstr "" + +# e8e11e0467134d0c9c7792aa498d65dd +#: ../../source/development_guide/rest_api.rst:130 +msgid "/api/kernels / /channels" +msgstr "" + +# de4521b7a70a4a78987145e026a49607 +#: ../../source/development_guide/rest_api.rst:130 +msgid "Websocket stream" +msgstr "" + +# 70afdc93b80448788de5ee906115a591 +#: ../../source/development_guide/rest_api.rst:134 +msgid "/api/kernel specs" +msgstr "" + +# e18bed8d78d245a4a5c2973178a7528e +#: ../../source/development_guide/rest_api.rst:134 +msgid "Return a spec model of all available kernels." +msgstr "" + +# a611384ba3e146aab1d36ad045577752 +#: ../../source/development_guide/rest_api.rst:137 +msgid "/api/kernel specs/ " +msgstr "" + +# 7505bc902e344212856aab8a1be8f17a +#: ../../source/development_guide/rest_api.rst:137 +msgid "Return a spec model of all available kernels with a given kernel name." +msgstr "" + +# 81461b43739140fc8fc0ad640eb498d5 +#: ../../source/development_guide/rest_api.rst:142 +msgid "Sessions API" +msgstr "" + +# 08e4e18abc2244ceb8abf296ca974619 +#: ../../source/development_guide/rest_api.rst:148 +msgid "/api/sessions" +msgstr "" + +# 6a2b019dacde41fba26edae7451aa2e5 +#: ../../source/development_guide/rest_api.rst:148 +msgid "Return model of active sessions." +msgstr "" + +# e56fef54527d48dc8ba3b121cd264e40 +#: ../../source/development_guide/rest_api.rst:150 +msgid "/api/sessions" +msgstr "" + +# f76c7178430e4df4884d2e39182e9c8b +#: ../../source/development_guide/rest_api.rst:150 +msgid "" +"If session does not already exist, create a new session with given " +"notebook name and path and given kernel name. Return active session." +msgstr "" + +# 5a4883c124374c5badd2612c1995b17e +# 62a139f0726b4521b1217f734f0a7a3c +# 58e922b4809b4ef6a9c622a81b6e8037 +#: ../../source/development_guide/rest_api.rst:155 +#: ../../source/development_guide/rest_api.rst:158 +#: ../../source/development_guide/rest_api.rst:162 +msgid "/api/sessions /" +msgstr "" + +# 1a7b5abb09a84f49a0fe343a7f667a61 +#: ../../source/development_guide/rest_api.rst:155 +msgid "Return model of active session with given session id." +msgstr "" + +# b5c11a8bffec49dca8bfc9c581d9bf4f +#: ../../source/development_guide/rest_api.rst:158 +msgid "" +"Return model of active session with notebook name or path of session with" +" given session id." +msgstr "" + +# 83e67dff5c6c4c4282abc35a809886d6 +#: ../../source/development_guide/rest_api.rst:162 +msgid "Delete model of active session with given session id." +msgstr "" + +# ce880e4d63aa4f60b1cde75c9f07ec78 +#: ../../source/development_guide/rest_api.rst:166 +msgid "Clusters API" +msgstr "" + +# 57b49bd43c8946b885d05a550d10998b +#: ../../source/development_guide/rest_api.rst:172 +msgid "/api/clusters" +msgstr "" + +# d597dde5def54af390dfb8c068248ad8 +#: ../../source/development_guide/rest_api.rst:172 +msgid "Return model of clusters." +msgstr "" + +# 8dcc8aa616184ff39f7509a2821ba18c +#: ../../source/development_guide/rest_api.rst:174 +msgid "/api/clusters " +msgstr "" + +# b7c8e1591a6d4ffe8c6fccfd070ec56f +#: ../../source/development_guide/rest_api.rst:174 +msgid "Return model of given cluster." +msgstr "" + +# 67a870b779114a1e8b55bc3682417ea9 +#: ../../source/development_guide/rest_api.rst:177 +msgid "/api/clusters " +msgstr "" + +# 985c28ae15c543afb7ad154db3b46f50 +#: ../../source/development_guide/rest_api.rst:177 +msgid "" +"Perform action with given clusters. Valid actions are \"start\" and " +"\"stop\"" +msgstr "" + +# 819cb4187e2d4cc6a0e7107dc259977b +#: ../../source/development_guide/rest_api.rst:183 +msgid "Old Architecture" +msgstr "" + +# b0cef61ad6954909ac7f0e849285224f +#: ../../source/development_guide/rest_api.rst:185 +msgid "" +"This chart shows the web-services in the single directory IPython " +"notebook." +msgstr "" + +# fdeb7827a6d343a9a6066a8165be18d4 +# c2ec6a32978841179b74bed14bbd3ea1 +#: ../../source/development_guide/rest_api.rst:192 +#: ../../source/development_guide/rest_api.rst:195 +msgid "/notebooks" +msgstr "" + +# af756cf6dda9437e9945475459ef4e5f +#: ../../source/development_guide/rest_api.rst:192 +msgid "return list of dicts with each notebook's info" +msgstr "" + +# 944132b8c9934cab857e811235689f40 +#: ../../source/development_guide/rest_api.rst:195 +msgid "" +"if sending a body, saving that body as a new notebook; if no body, create" +" a a new notebook." +msgstr "" + +# 903e8f3495274ef5bd24dafa8c5004dd +# c6e1a714498f409eabce7a39a40568aa +# e4621bb9f8c34d9ab8d60469bac19bd2 +#: ../../source/development_guide/rest_api.rst:199 +#: ../../source/development_guide/rest_api.rst:202 +#: ../../source/development_guide/rest_api.rst:205 +msgid "/notebooks /" +msgstr "" + +# fa3253b06f424c3fa9827596beeb038e +#: ../../source/development_guide/rest_api.rst:199 +msgid "get JSON data for notebook" +msgstr "" + +# 3ac66b01afa544639b6e56e520fcf336 +#: ../../source/development_guide/rest_api.rst:202 +msgid "saves an existing notebook with body data" +msgstr "" + +# f2d62f8edd154a1694c266cb01d161da +#: ../../source/development_guide/rest_api.rst:205 +msgid "deletes the notebook with the given ID" +msgstr "" + +# 76792199079742d7ba728bfd36c6e12b +#: ../../source/development_guide/rest_api.rst:209 +msgid "This chart shows the architecture for the IPython notebook website." +msgstr "" + +# 4b327f0782284c11bffe95726ba3d093 +#: ../../source/development_guide/rest_api.rst:215 +msgid "/" +msgstr "" + +# 8f2f602d40da4dc693e34cfbfdf8f3b7 +#: ../../source/development_guide/rest_api.rst:215 +msgid "navigates user to dashboard of notebooks and clusters." +msgstr "" + +# 29f4821c5000491d8ff30a06d4a649b5 +#: ../../source/development_guide/rest_api.rst:218 +msgid "/" +msgstr "" + +# 6d09e8fe05b141529561184b06fe4678 +#: ../../source/development_guide/rest_api.rst:218 +msgid "go to wepage for that notebook" +msgstr "" + +# 24836333d48d47d3986688ce667283a7 +#: ../../source/development_guide/rest_api.rst:220 +msgid "/new" +msgstr "" + +# 4a85061aeca048fd9010b52afc06f83b +#: ../../source/development_guide/rest_api.rst:220 +msgid "" +"creates a new notebook with profile (or default, if no profile exists) " +"settings" +msgstr "" + +# ff97d5e191354ac49a2e70163427c4c2 +#: ../../source/development_guide/rest_api.rst:224 +msgid "/ /copy" +msgstr "" + +# 0589cdc545964cf0926fa8eb459123b5 +#: ../../source/development_guide/rest_api.rst:224 +msgid "opens a duplicate copy or the notebook with the given ID in a new tab" +msgstr "" + +# ff517ea185b049dfa1f37f0135487226 +#: ../../source/development_guide/rest_api.rst:227 +msgid "/ /print" +msgstr "" + +# 70ade4f0505d436c949d0a14cea03ce6 +#: ../../source/development_guide/rest_api.rst:227 +msgid "" +"prints the notebook with the given ID; if notebook doesn't exist, " +"displays error message" +msgstr "" + +# ef1e03a67e434bcebb694721b956c0a4 +#: ../../source/development_guide/rest_api.rst:231 +msgid "/login" +msgstr "" + +# 54945e6f06af47a3948156bb62efe0f2 +#: ../../source/development_guide/rest_api.rst:231 +msgid "" +"navigates to login page; if no user profile is defined, it navigates user" +" to dashboard" +msgstr "" + +# 7b8ee796640a4c1a86cd204b274f42d6 +#: ../../source/development_guide/rest_api.rst:235 +msgid "/logout" +msgstr "" + +# 2f224f13e6a5446bb8683b23cf41436a +#: ../../source/development_guide/rest_api.rst:235 +msgid "logs out of current profile, and navigates user to login page" +msgstr "" + +# 461cac9f248140918942166ba0e0b01d +#: ../../source/development_guide/rest_api.rst:239 +msgid "This chart shows the Web services that act on the kernels and clusters." +msgstr "" + +# de02268e21c94de3a4759a55773c3ea2 +#: ../../source/development_guide/rest_api.rst:245 +msgid "/kernels" +msgstr "" + +# d5845cac753b4c1abdc62104632c17c5 +#: ../../source/development_guide/rest_api.rst:245 +msgid "return the list of kernel IDs currently running" +msgstr "" + +# 2bb5311d7d954a3f9c8f4ca85472bf76 +#: ../../source/development_guide/rest_api.rst:248 +msgid "/kernels /" +msgstr "" + +# 77fd3900942741b09303446a7004120a +# c7c4420e0aa341a2af83c24a2d1767fe +# 13d18f18fab7449d9f5a9ebbb3bd0724 +# f9521b40d2cc4a8caf50dc7788d4d135 +# 2a226c3f624349ae9a76a4adef40b2a8 +#: ../../source/development_guide/rest_api.rst:248 +#: ../../source/development_guide/rest_api.rst:255 +#: ../../source/development_guide/rest_api.rst:259 +#: ../../source/development_guide/rest_api.rst:263 +#: ../../source/development_guide/rest_api.rst:266 +msgid "---" +msgstr "" + +# e136d989d52e439e8e6d924f02a1268b +#: ../../source/development_guide/rest_api.rst:251 +msgid "/kernels / " +msgstr "" + +# 59d771a7602d4cf0aba2314257cb6ac8 +#: ../../source/development_guide/rest_api.rst:251 +msgid "performs action (restart/kill) kernel with given ID" +msgstr "" + +# e70044bc6b954eb5982a61f2d9f35fc4 +#: ../../source/development_guide/rest_api.rst:255 +msgid "/kernels / /iopub" +msgstr "" + +# 368154e364f94b5b9f449a21c01529e5 +#: ../../source/development_guide/rest_api.rst:259 +msgid "/kernels / /shell" +msgstr "" + +# 562e776b3fbb4f7e91b6208e783b6a15 +#: ../../source/development_guide/rest_api.rst:263 +msgid "/rstservice/ render" +msgstr "" + +# 05a3c48c4b62422eb4d4079b522f3f99 +#: ../../source/development_guide/rest_api.rst:266 +msgid "/files/(.\\*)" +msgstr "" + +# 569ac69c0a2c4b75b0e0de52468cbc7e +#: ../../source/development_guide/rest_api.rst:268 +msgid "/clusters" +msgstr "" + +# 84144edf06b64ad8bd71aa7cf35943f3 +#: ../../source/development_guide/rest_api.rst:268 +msgid "returns a list of dicts with each cluster's information" +msgstr "" + +# 081da73e88514f32b9fbd6e610569422 +#: ../../source/development_guide/rest_api.rst:271 +msgid "/clusters / /" +msgstr "" + +# ed0932c1d56548e598921efeeb5cc74b +#: ../../source/development_guide/rest_api.rst:271 +msgid "performs action (start/stop) on cluster with given profile ID" +msgstr "" + +# 4499cb69e075466ca0738fe9600eac8f +#: ../../source/development_guide/rest_api.rst:276 +msgid "/clusters /" +msgstr "" + +# 5144fcfdab6143b1975f8e8837e184db +#: ../../source/development_guide/rest_api.rst:276 +msgid "returns the JSON data for cluster with given profile ID" +msgstr "" + +# ecaf0b8eb09146c1990b346ac4c12ea8 +#: ../../source/development_guide/sphinx_directive.rst:4 +msgid "IPython Sphinx Directive" +msgstr "" + +# 1a6af3d02129462689efcf761c98db39 +#: ../../source/development_guide/sphinx_directive.rst:9 +msgid "" +"The ipython directive is a stateful ipython shell for embedding in sphinx" +" documents. It knows about standard ipython prompts, and extracts the " +"input and output lines. These prompts will be renumbered starting at " +"``1``. The inputs will be fed to an embedded ipython interpreter and the" +" outputs from that interpreter will be inserted as well. For example, " +"code blocks like the following::" +msgstr "" + +# be1f1c5ba2854ae9abcec8403c98b857 +#: ../../source/development_guide/sphinx_directive.rst:23 +msgid "will be rendered as" +msgstr "" + +# 95d3f01bb5da46e7b1fc259b1f68fd9b +#: ../../source/development_guide/sphinx_directive.rst:34 +msgid "" +"This tutorial should be read side-by-side with the Sphinx source for this" +" document because otherwise you will see only the rendered output and not" +" the code that generated it. Excepting the example above, we will not in" +" general be showing the literal ReST in this document that generates the " +"rendered output." +msgstr "" + +# 7a9bcf56e253423cbc1c6256b5c4501e +#: ../../source/development_guide/sphinx_directive.rst:41 +msgid "" +"The state from previous sessions is stored, and standard error is " +"trapped. At doc build time, ipython's output and std err will be " +"inserted, and prompts will be renumbered. So the prompt below should be " +"renumbered in the rendered docs, and pick up where the block above left " +"off." +msgstr "" + +# 8661fbdc92ab401b81044a193e9cdead +#: ../../source/development_guide/sphinx_directive.rst:66 +msgid "" +"The embedded interpreter supports some limited markup. For example, you " +"can put comments in your ipython sessions, which are reported verbatim. " +"There are some handy \"pseudo-decorators\" that let you doctest the " +"output. The inputs are fed to an embedded ipython session and the " +"outputs from the ipython session are inserted into your doc. If the " +"output in your doc and in the ipython session don't match on a doctest " +"assertion, an error will be" +msgstr "" + +# 3f187933d2ca4ee8a3754fca19ba9c27 +#: ../../source/development_guide/sphinx_directive.rst:92 +msgid "Multi-line input is supported." +msgstr "" + +# 2f404b366a7c4e33a08ad3536a33b782 +#: ../../source/development_guide/sphinx_directive.rst:103 +msgid "" +"You can do doctesting on multi-line output as well. Just be careful when" +" using non-deterministic inputs like random numbers in the ipython " +"directive, because your inputs are ruin through a live interpreter, so if" +" you are doctesting random output you will get an error. Here we " +"\"seed\" the random number generator for deterministic output, and we " +"suppress the seed line so it doesn't show up in the rendered output" +msgstr "" + +# cd769347eca441e6ae41012cbd6c3368 +#: ../../source/development_guide/sphinx_directive.rst:132 +msgid "Another demonstration of multi-line input and output" +msgstr "" + +# e25d68950302401aab1b4a8efbca2b28 +#: ../../source/development_guide/sphinx_directive.rst:156 +msgid "" +"Most of the \"pseudo-decorators\" can be used an options to ipython mode." +" For example, to setup matplotlib pylab but suppress the output, you can" +" do. When using the matplotlib ``use`` directive, it should occur before" +" any import of pylab. This will not show up in the rendered docs, but " +"the commands will be executed in the embedded interpreter and subsequent " +"line numbers will be incremented to reflect the inputs::" +msgstr "" + +# d512e1317bf34899ba98769e96504ffc +#: ../../source/development_guide/sphinx_directive.rst:177 +msgid "" +"Likewise, you can set ``:doctest:`` or ``:verbatim:`` to apply these " +"settings to the entire block. For example," +msgstr "" + +# 750e9c6085cb47f494525d6d700016eb +#: ../../source/development_guide/sphinx_directive.rst:211 +msgid "" +"You can create one or more pyplot plots and insert them with the " +"``@savefig`` decorator." +msgstr "" + +# 7e0cba55af2c4726b80908fc11bd87d4 +#: ../../source/development_guide/sphinx_directive.rst:223 +msgid "" +"In a subsequent session, we can update the current figure with some text," +" and then resave" +msgstr "" + +# 26224a89dd6b4104993adddc105e30d2 +#: ../../source/development_guide/sphinx_directive.rst:236 +msgid "You can also have function definitions included in the source." +msgstr "" + +# 4fee5a90c5924503a796fe31c61836cd +#: ../../source/development_guide/sphinx_directive.rst:250 +msgid "Then call it from a subsequent section." +msgstr "" + +# 40f4c170c68d465ebd0facc61091d74c +#: ../../source/development_guide/sphinx_directive.rst:262 +msgid "Writing Pure Python Code" +msgstr "" + +# 27b06e32117148dd9ac27196ea17cff7 +#: ../../source/development_guide/sphinx_directive.rst:264 +msgid "" +"Pure python code is supported by the optional argument `python`. In this " +"pure python syntax you do not include the output from the python " +"interpreter. The following markup::" +msgstr "" + +# 9bfc9399e7344f47aeee6b108d4c80c8 +#: ../../source/development_guide/sphinx_directive.rst:275 +msgid "Renders as" +msgstr "" + +# 143dfd8c90d640d1ae379cff861c53fc +#: ../../source/development_guide/sphinx_directive.rst:284 +msgid "" +"We can even plot from python, using the savefig decorator, as well as, " +"suppress output with a semicolon" +msgstr "" + +# 4e5f8f65f700433da3aa7c77aff0b8e8 +#: ../../source/development_guide/sphinx_directive.rst:292 +msgid "Similarly, std err is inserted" +msgstr "" + +# be359198a34747a2a02d4ec1202f60f7 +#: ../../source/development_guide/sphinx_directive.rst:299 +msgid "Comments are handled and state is preserved" +msgstr "" + +# 26da84518202409ebcf6b00f0d273bb8 +#: ../../source/development_guide/sphinx_directive.rst:306 +msgid "If you don't see the next code block then the options work." +msgstr "" + +# 9e1cb6242761493abd5e4b9f305f73c6 +#: ../../source/development_guide/sphinx_directive.rst:313 +msgid "Multi-line input is handled." +msgstr "" + +# 91f37105015c41d79b3605f85c3c69f5 +#: ../../source/development_guide/sphinx_directive.rst:323 +msgid "Functions definitions are correctly parsed" +msgstr "" + +# 09192d72a72842c1af4869ff794d0c94 +#: ../../source/development_guide/sphinx_directive.rst:336 +msgid "And persist across sessions" +msgstr "" + +# 8df88447cc244a0e98ada814e7bb2c75 +#: ../../source/development_guide/sphinx_directive.rst:343 +msgid "" +"Pretty much anything you can do with the ipython code, you can do with a " +"simple python script. Obviously, though it doesn't make sense to use the " +"doctest option." +msgstr "" + +# 078e5ad91f7e496e8f8551f9d8447521 +#: ../../source/development_guide/sphinx_directive.rst:348 +msgid "Pseudo-Decorators" +msgstr "" + +# 8496e2e10f8249f8a0889c63bc0bdc01 +#: ../../source/development_guide/sphinx_directive.rst:350 +msgid "" +"Here are the supported decorators, and any optional arguments they take." +" Some of the decorators can be used as options to the entire block (eg " +"``verbatim`` and ``suppress``), and some only apply to the line just " +"below them (eg ``savefig``)." +msgstr "" + +# 46581c1b4489455a9401ef030eb19f7e +#: ../../source/development_guide/sphinx_directive.rst:355 +msgid "@suppress" +msgstr "" + +# 78c15d5d9d2148f1b24d668c8bbf3a12 +#: ../../source/development_guide/sphinx_directive.rst:357 +msgid "" +"execute the ipython input block, but suppress the input and output block " +"from the rendered output. Also, can be applied to the entire " +"``..ipython`` block as a directive option with ``:suppress:``." +msgstr "" + +# f80914b7f9d84a0cb2269c32131f57c5 +#: ../../source/development_guide/sphinx_directive.rst:361 +msgid "@verbatim" +msgstr "" + +# 7581a6ec4f3340009ea650860d1a4e87 +#: ../../source/development_guide/sphinx_directive.rst:363 +msgid "" +"insert the input and output block in verbatim, but auto-increment the " +"line numbers. Internally, the interpreter will be fed an empty string, so" +" it is a no-op that keeps line numbering consistent. Also, can be applied" +" to the entire ``..ipython`` block as a directive option with " +"``:verbatim:``." +msgstr "" + +# 5c4589b166cc4f8bbfc0ac493852cbba +#: ../../source/development_guide/sphinx_directive.rst:369 +msgid "@savefig OUTFILE [IMAGE_OPTIONS]" +msgstr "" + +# 3527e86c071e4a66b28c3634d27c12f7 +#: ../../source/development_guide/sphinx_directive.rst:371 +msgid "" +"save the figure to the static directory and insert it into the document, " +"possibly binding it into a minipage and/or putting code/figure " +"label/references to associate the code and the figure. Takes args to pass" +" to the image directive (*scale*, *width*, etc can be kwargs); see `image" +" options " +"`_ " +"for details." +msgstr "" + +# 9bb837c64a9f47b09c9e6cdd748149cc +#: ../../source/development_guide/sphinx_directive.rst:379 +msgid "@doctest" +msgstr "" + +# a7c37652b27f49259655b5e77a94f2f1 +#: ../../source/development_guide/sphinx_directive.rst:381 +msgid "" +"Compare the pasted in output in the ipython block with the output " +"generated at doc build time, and raise errors if they don’t match. " +"Also, can be applied to the entire ``..ipython`` block as a directive " +"option with ``:doctest:``." +msgstr "" + +# 981a1d3bd1774d75893718ec6fc08f09 +#: ../../source/development_guide/sphinx_directive.rst:387 +msgid "Configuration Options" +msgstr "" + +# 3df1f28cd6bf45acade20f5d1517e6f6 +#: ../../source/development_guide/sphinx_directive.rst:389 +msgid "ipython_savefig_dir" +msgstr "" + +# 792602678601404a8d3ac21aa40be6b1 +#: ../../source/development_guide/sphinx_directive.rst:391 +msgid "" +"The directory in which to save the figures. This is relative to the " +"Sphinx source directory. The default is `html_static_path`." +msgstr "" + +# 140a2c7a2b9d402cad12d5a024cb3e60 +#: ../../source/development_guide/sphinx_directive.rst:394 +msgid "ipython_rgxin" +msgstr "" + +# bd034db7665a47e8b4d9368ff619aafa +#: ../../source/development_guide/sphinx_directive.rst:396 +msgid "" +"The compiled regular expression to denote the start of IPython input " +"lines. The default is re.compile('In \\[(\\d+)\\]:\\s?(.*)\\s*'). You " +"shouldn't need to change this." +msgstr "" + +# f7c5465041ba48c2850106f6e9e94697 +#: ../../source/development_guide/sphinx_directive.rst:400 +msgid "ipython_rgxout" +msgstr "" + +# 77908add9c29480690fd25915d879634 +#: ../../source/development_guide/sphinx_directive.rst:402 +msgid "" +"The compiled regular expression to denote the start of IPython output " +"lines. The default is re.compile('Out\\[(\\d+)\\]:\\s?(.*)\\s*'). You " +"shouldn't need to change this." +msgstr "" + +# 3201a8e59323478684c80a3454c2f8df +#: ../../source/development_guide/sphinx_directive.rst:407 +msgid "ipython_promptin" +msgstr "" + +# d057091b1f274838b754082ae5624619 +#: ../../source/development_guide/sphinx_directive.rst:409 +#, python-format +msgid "" +"The string to represent the IPython input prompt in the generated ReST. " +"The default is 'In [%d]:'. This expects that the line numbers are used in" +" the prompt." +msgstr "" + +# 7b8b46b701f441eabf3e9e4bd61d6ff1 +#: ../../source/development_guide/sphinx_directive.rst:413 +msgid "ipython_promptout" +msgstr "" + +# 890612f5be0b41c4aa95fbf2df2106b7 +#: ../../source/development_guide/sphinx_directive.rst:415 +#, python-format +msgid "" +"The string to represent the IPython prompt in the generated ReST. The " +"default is 'Out [%d]:'. This expects that the line numbers are used in " +"the prompt." +msgstr "" + +# 27a6f000767e4d5ca50192bbba9a45cb +#: ../../source/development_guide/testing.rst:4 +msgid "Testing IPython for users and developers" +msgstr "" + +# e1c007bdd68b49d897c585eb20430783 +#: ../../source/development_guide/testing.rst:10 +msgid "Overview" +msgstr "" + +# 844d10e3be9a4277aa773c204884291a +#: ../../source/development_guide/testing.rst:12 +msgid "" +"It is extremely important that all code contributed to IPython has tests." +" Tests should be written as unittests, doctests or other entities that " +"the IPython test system can detect. See below for more details on this." +msgstr "" + +# 821bcb831c114683b15276dc6ec5899f +#: ../../source/development_guide/testing.rst:17 +msgid "" +"Each subpackage in IPython should have its own ``tests`` directory that " +"contains all of the tests for that subpackage. All of the files in the " +"``tests`` directory should have the word \"tests\" in them to enable the " +"testing framework to find them." +msgstr "" + +# 570ccbdb6bbf4d93bca65ee6004cbf20 +#: ../../source/development_guide/testing.rst:22 +msgid "" +"In docstrings, examples (either using IPython prompts like ``In [1]:`` or" +" 'classic' python ``>>>`` ones) can and should be included. The testing " +"system will detect them as doctests and will run them; it offers control " +"to skip parts or all of a specific doctest if the example is meant to be " +"informative but shows non-reproducible information (like filesystem " +"data)." +msgstr "" + +# eb5ea7f7c4bd4149b910b6e7fdc90548 +#: ../../source/development_guide/testing.rst:29 +msgid "" +"If a subpackage has any dependencies beyond the Python standard library, " +"the tests for that subpackage should be skipped if the dependencies are " +"not found. This is very important so users don't get tests failing simply" +" because they don't have dependencies." +msgstr "" + +# 1bae5608051d4014aaf1bdd3fea06df1 +#: ../../source/development_guide/testing.rst:34 +msgid "" +"The testing system we use is an extension of the `nose " +"`__ test runner. In " +"particular we've developed a nose plugin that allows us to paste verbatim" +" IPython sessions and test them as doctests, which is extremely important" +" for us." +msgstr "" + +# f197bc1384eb4e908a7315e7a18894cd +#: ../../source/development_guide/testing.rst:41 +msgid "Running the test suite" +msgstr "" + +# d4eb05e8dab545a8bc155c101920e037 +#: ../../source/development_guide/testing.rst:43 +msgid "" +"You can run IPython from the source download directory without even " +"installing it system-wide or having configure anything, by typing at the " +"terminal:" +msgstr "" + +# 8aff3ac30add49aa91a752e8b3ae02b8 +#: ../../source/development_guide/testing.rst:51 +msgid "To start the web-based notebook you can use:" +msgstr "" + +# 5786563b0bdd48439fa3dc0295306ac5 +#: ../../source/development_guide/testing.rst:57 +msgid "" +"In order to run the test suite, you must at least be able to import " +"IPython, even if you haven't fully installed the user-facing scripts yet " +"(common in a development environment). You can then run the tests with:" +msgstr "" + +# 14fb987065c2432dba155af720fe2bb1 +#: ../../source/development_guide/testing.rst:65 +msgid "Once you have installed IPython either via a full install or using:" +msgstr "" + +# 71ac67c588434e1590c51a6eb7173c8a +#: ../../source/development_guide/testing.rst:71 +msgid "" +"you will have available a system-wide script called ``iptest`` that runs " +"the full test suite. You can then run the suite with:" +msgstr "" + +# 4f379e62ed0a48ebb0b34290233f8743 +#: ../../source/development_guide/testing.rst:78 +msgid "" +"By default, this excludes the relatively slow tests for " +"``IPython.parallel``. To run these, use ``iptest --all``." +msgstr "" + +# b953130e61dd46fea865b2f3db368b9e +#: ../../source/development_guide/testing.rst:81 +msgid "" +"Please note that the iptest tool will run tests against the code imported" +" by the Python interpreter. If the command ``python setup.py symlink`` " +"has been previously run then this will always be the test code in the " +"local directory via a symlink. However, if this command has not been run " +"for the version of Python being tested, there is the possibility that " +"iptest will run the tests against an installed version of IPython." +msgstr "" + +# 9710816ba7b2484ea640d3a6b1b99c31 +#: ../../source/development_guide/testing.rst:89 +msgid "" +"Regardless of how you run things, you should eventually see something " +"like:" +msgstr "" + +# 614b34f2ec5b4490a5e840f9d501ba70 +#: ../../source/development_guide/testing.rst:114 +msgid "" +"If not, there will be a message indicating which test group failed and " +"how to rerun that group individually. For example, this tests the " +"``IPython.utils`` subpackage, the ``-v`` option shows progress " +"indicators:" +msgstr "" + +# 472241ea528a4474bf852a4a2b3192bf +#: ../../source/development_guide/testing.rst:129 +msgid "" +"Because the IPython test machinery is based on nose, you can use all nose" +" syntax. Options after ``--`` are passed to nose. For example, this lets " +"you run the specific test ``test_rehashx`` inside the ``test_magic`` " +"module:" +msgstr "" + +# a8b75c70816c4171995e1b3d69bc62af +#: ../../source/development_guide/testing.rst:145 +msgid "" +"When developing, the ``--pdb`` and ``--pdb-failures`` of nose are " +"particularly useful, these drop you into an interactive pdb session at " +"the point of the error or failure respectively: ``iptest mymodule -- " +"--pdb``." +msgstr "" + +# cc865cad5eff4c63bde73d0e5ed83c27 +#: ../../source/development_guide/testing.rst:150 +msgid "" +"The system information summary printed above is accessible from the top " +"level package. If you encounter a problem with IPython, it's useful to " +"include this information when reporting on the mailing list; use::" +msgstr "" + +# 89f6b6f7135644de883cfe881958da37 +#: ../../source/development_guide/testing.rst:156 +msgid "from IPython import sys_info print sys_info()" +msgstr "" + +# 1ad64a55fae24664865a1daa9546bc92 +#: ../../source/development_guide/testing.rst:159 +msgid "and include the resulting information in your query." +msgstr "" + +# 5c0493f32ba34c32a7f7a26b75a45b3c +#: ../../source/development_guide/testing.rst:162 +msgid "Testing pull requests" +msgstr "" + +# 56dccf1edc7d42ba97235fc0909a286b +#: ../../source/development_guide/testing.rst:164 +msgid "" +"We have a script that fetches a pull request from Github, merges it with " +"master, and runs the test suite on different versions of Python. This " +"uses a separate copy of the repository, so you can keep working on the " +"code while it runs. To run it:" +msgstr "" + +# 5f6f81a06a5548aa92e363c518a23423 +#: ../../source/development_guide/testing.rst:173 +msgid "" +"The number is the pull request number from Github; the ``-p`` flag makes " +"it post the results to a comment on the pull request. Any further " +"arguments are passed to ``iptest``." +msgstr "" + +# e9bf9d2d0d9e464d8c84e83b6ecea186 +#: ../../source/development_guide/testing.rst:177 +msgid "" +"This requires the `requests `__ " +"and `keyring `__ packages." +msgstr "" + +# cb70af2a41f444c19d09ba4052f15034 +#: ../../source/development_guide/testing.rst:181 +msgid "For developers: writing tests" +msgstr "" + +# 94aeb6cea2674d37b05d9ec68916a4c7 +#: ../../source/development_guide/testing.rst:183 +msgid "" +"By now IPython has a reasonable test suite, so the best way to see what's" +" available is to look at the ``tests`` directory in most subpackages. But" +" here are a few pointers to make the process easier." +msgstr "" + +# d5cf58b941044fde967b425c2e2952a2 +#: ../../source/development_guide/testing.rst:188 +msgid "Main tools: ``IPython.testing``" +msgstr "" + +# 473653eaf4104a50a6472b679f60cc7a +#: ../../source/development_guide/testing.rst:190 +msgid "" +"The ``IPython.testing`` package is where all of the machinery to test " +"IPython (rather than the tests for its various parts) lives. In " +"particular, the ``iptest`` module in there has all the smarts to control " +"the test process. In there, the ``make_exclude`` function is used to " +"build a blacklist of exclusions, these are modules that do not get even " +"imported for tests. This is important so that things that would fail to " +"even import because of missing dependencies don't give errors to end " +"users, as we stated above." +msgstr "" + +# 40dbcdef36d64128ad582781f05c660b +#: ../../source/development_guide/testing.rst:199 +msgid "" +"The ``decorators`` module contains a lot of useful decorators, especially" +" useful to mark individual tests that should be skipped under certain " +"conditions (rather than blacklisting the package altogether because of a " +"missing major dependency)." +msgstr "" + +# 8c1c005edf93476a8ae62b269d4404a6 +#: ../../source/development_guide/testing.rst:205 +msgid "Our nose plugin for doctests" +msgstr "" + +# bfb15655ad094c51b4473555ba6ceb28 +#: ../../source/development_guide/testing.rst:207 +msgid "" +"The ``plugin`` subpackage in testing contains a nose plugin called " +"``ipdoctest`` that teaches nose about IPython syntax, so you can write " +"doctests with IPython prompts. You can also mark doctest output with ``# " +"random`` for the output corresponding to a single input to be ignored " +"(stronger than using ellipsis and useful to keep it as an example). If " +"you want the entire docstring to be executed but none of the output from " +"any input to be checked, you can use the ``# all-random`` marker. The " +"``IPython.testing.plugin.dtexample`` module contains examples of how to " +"use these; for reference here is how to use ``# random``:" +msgstr "" + +# 1292a78c838b4a9caeca2665510d1b04 +#: ../../source/development_guide/testing.rst:249 +msgid "and an example of ``# all-random``:" +msgstr "" + +# 2d557c51b55e49a693c25acd171eb9bc +#: ../../source/development_guide/testing.rst:279 +msgid "" +"When writing docstrings, you can use the ``@skip_doctest`` decorator to " +"indicate that a docstring should *not* be treated as a doctest at all. " +"The difference between ``# all-random`` and ``@skip_doctest`` is that the" +" former executes the example but ignores output, while the latter doesn't" +" execute any code. ``@skip_doctest`` should be used for docstrings whose " +"examples are purely informational." +msgstr "" + +# 70efd2988ecf430f99d724409ed8cec0 +#: ../../source/development_guide/testing.rst:286 +msgid "" +"If a given docstring fails under certain conditions but otherwise is a " +"good doctest, you can use code like the following, that relies on the " +"'null' decorator to leave the docstring intact where it works as a test:" +msgstr "" + +# 3878be7f250c4ca5ba17f9028f5309a5 +#: ../../source/development_guide/testing.rst:304 +msgid "" +"With our nose plugin that understands IPython syntax, an extremely " +"effective way to write tests is to simply copy and paste an interactive " +"session into a docstring. You can writing this type of test, where your " +"docstring is meant *only* as a test, by prefixing the function name with " +"``doctest_`` and leaving its body *absolutely empty* other than the " +"docstring. In ``IPython.core.tests.test_magic`` you can find several " +"examples of this, but for completeness sake, your code should look like " +"this (a simple case):" +msgstr "" + +# f2323f599c37435999518cd691eb254f +#: ../../source/development_guide/testing.rst:322 +msgid "" +"This function is only analyzed for its docstring but it is not considered" +" a separate test, which is why its body should be empty." +msgstr "" + +# a1a31cd900144f6498b312df387bf326 +#: ../../source/development_guide/testing.rst:326 +msgid "JavaScript Tests" +msgstr "" + +# 55e925644bbf42f18fea76e793e5f7ea +#: ../../source/development_guide/testing.rst:328 +msgid "" +"We currently use `casperjs `__ for testing the " +"notebook javascript user interface." +msgstr "" + +# 86ed51fe4d284284812995f9c2aa800d +#: ../../source/development_guide/testing.rst:331 +msgid "" +"To run the JS test suite by itself, you can either use ``iptest js``, " +"which will start up a new notebook server and test against it, or you can" +" open up a notebook server yourself, and then:" +msgstr "" + +# 10ef19ece8954410aa7023ae524cfe0e +#: ../../source/development_guide/testing.rst:340 +msgid "" +"If your testing notebook server uses something other than the default " +"port (8888), you will have to pass that as a parameter to the test suite " +"as well." +msgstr "" + +# d4dd9155cfc741168d07245a00e7449e +#: ../../source/development_guide/testing.rst:349 +msgid "Running individual tests" +msgstr "" + +# 27e768bba3f64ba7b12e8e7225779467 +#: ../../source/development_guide/testing.rst:351 +msgid "" +"To speed up development, you usually are working on getting one test " +"passing at a time. To do this, just pass the filename directly to the " +"``casperjs test`` command like so:" +msgstr "" + +# 11f7653601b84925a2ec145e210d7da0 +#: ../../source/development_guide/testing.rst:360 +msgid "Wrapping your head around the javascript within javascript:" +msgstr "" + +# ed4f3f26b8dc4b3eaba4975661c195c3 +#: ../../source/development_guide/testing.rst:362 +msgid "" +"CasperJS is a browser that's written in javascript, so we write " +"javascript code to drive it. The Casper browser itself also has a " +"javascript implementation (like the ones that come with Firefox and " +"Chrome), and in the test suite we get access to those using " +"``this.evaluate``, and it's cousins (``this.theEvaluate``, etc). " +"Additionally, because of the asynchronous / callback nature of " +"everything, there are plenty of ``this.then`` calls which define steps in" +" test suite. Part of the reason for this is that each step has a timeout " +"(default of 5 or 10 seconds). Additionally, there are already convenience" +" functions in ``util.js`` to help you wait for output in a given cell, " +"etc. In our javascript tests, if you see functions which " +"``look_like_pep8_naming_convention``, those are probably coming from " +"``util.js``, whereas functions that come with casper " +"``haveCamelCaseNamingConvention``" +msgstr "" + +# b834615955564a74a7c34b4071190cdc +#: ../../source/development_guide/testing.rst:377 +msgid "" +"Each file in ``test_cases`` looks something like this (this is " +"``test_cases/check_interrupt.js``):" +msgstr "" + +# 52615ee776ef4a71bf05c26f46670d28 +#: ../../source/development_guide/testing.rst:419 +msgid "" +"For an example of how to pass parameters to the client-side javascript " +"from casper test suite, see the ``casper.wait_for_output`` implementation" +" in ``IPython/html/tests/casperjs/util.js``" +msgstr "" + +# fae96465d4094630ac562426a0003dbc +#: ../../source/development_guide/testing.rst:424 +msgid "Testing system design notes" +msgstr "" + +# 58335def9eaa4f669f9521490ecbaa26 +#: ../../source/development_guide/testing.rst:426 +msgid "" +"This section is a set of notes on the key points of the IPython testing " +"needs, that were used when writing the system and should be kept for " +"reference as it evolves." +msgstr "" + +# 4b0a9eccc5924a96aae6703bb568a450 +#: ../../source/development_guide/testing.rst:430 +msgid "" +"Testing IPython in full requires modifications to the default behavior of" +" nose and doctest, because the IPython prompt is not recognized to " +"determine Python input, and because IPython admits user input that is not" +" valid Python (things like ``%magics`` and ``!system commands``." +msgstr "" + +# 800dc52e25ed4b7c91a299d5226f21ef +#: ../../source/development_guide/testing.rst:435 +msgid "We basically need to be able to test the following types of code:" +msgstr "" + +# b91ada24535c4452b163e02c66844461 +#: ../../source/development_guide/testing.rst:439 +msgid "" +"Pure Python files containing normal tests. These are not a problem, since" +" Nose will pick them up as long as they conform to the (flexible) " +"conventions used by nose to recognize tests." +msgstr "" + +# 62b8a60a8b14443ebfc3ca1dba0de170 +#: ../../source/development_guide/testing.rst:445 +msgid "Python files containing doctests. Here, we have two possibilities:" +msgstr "" + +# 6324a400853c4860abf99f4cbd08a59c +#: ../../source/development_guide/testing.rst:448 +msgid "The prompts are the usual ``>>>`` and the input is pure Python." +msgstr "" + +# 65fa6dd816c24f4e9b84f6d0920c5756 +#: ../../source/development_guide/testing.rst:449 +msgid "" +"The prompts are of the form ``In [1]:`` and the input can contain " +"extended IPython expressions." +msgstr "" + +# 9ad1cecfc10347bfac60314688c8dba6 +#: ../../source/development_guide/testing.rst:452 +msgid "" +"In the first case, Nose will recognize the doctests as long as it is " +"called with the ``--with-doctest`` flag. But the second case will likely " +"require modifications or the writing of a new doctest plugin for Nose " +"that is IPython-aware." +msgstr "" + +# 200c3b0361b1483fabdf8735413bdd04 +#: ../../source/development_guide/testing.rst:459 +msgid "" +"ReStructuredText files that contain code blocks. For this type of file, " +"we have three distinct possibilities for the code blocks:" +msgstr "" + +# 1886e7b95147471b9c70104d4bb51db6 +#: ../../source/development_guide/testing.rst:462 +msgid "They use ``>>>`` prompts." +msgstr "" + +# 09bac740954c4fdca7173fafa7ff0716 +#: ../../source/development_guide/testing.rst:463 +msgid "They use ``In [1]:`` prompts." +msgstr "" + +# 4b346c61197a47b2b1be0d95b8afa113 +#: ../../source/development_guide/testing.rst:464 +msgid "They are standalone blocks of pure Python code without any prompts." +msgstr "" + +# 15b043cc6fa14b5687221a1c8176794e +#: ../../source/development_guide/testing.rst:466 +msgid "" +"The first two cases are similar to the situation #2 above, except that in" +" this case the doctests must be extracted from input code blocks using " +"docutils instead of from the Python docstrings." +msgstr "" + +# 66f66893cec8416fbf35c58a4d7a6a28 +#: ../../source/development_guide/testing.rst:470 +msgid "" +"In the third case, we must have a convention for distinguishing code " +"blocks that are meant for execution from others that may be snippets of " +"shell code or other examples not meant to be run. One possibility is to " +"assume that all indented code blocks are meant for execution, but to have" +" a special docutils directive for input that should not be executed." +msgstr "" + +# 31b72bf0802e45aabd969ed1ee4de26f +#: ../../source/development_guide/testing.rst:476 +msgid "" +"For those code blocks that we will execute, the convention used will " +"simply be that they get called and are considered successful if they run " +"to completion without raising errors. This is similar to what Nose does " +"for standalone test functions, and by putting asserts or other forms of " +"exception-raising statements it becomes possible to have literate " +"examples that double as lightweight tests." +msgstr "" + +# 4656af2388f0464ba9945c046148ce4c +#: ../../source/development_guide/testing.rst:485 +msgid "" +"Extension modules with doctests in function and method docstrings. " +"Currently Nose simply can't find these docstrings correctly, because the " +"underlying doctest DocTestFinder object fails there. Similarly to #2 " +"above, the docstrings could have either pure python or IPython prompts." +msgstr "" + +# b81efc4dc4b94b3bbb7f5d2ec96ce033 +#: ../../source/development_guide/testing.rst:491 +msgid "" +"Of these, only 3-c (reST with standalone code blocks) is not implemented " +"at this point." +msgstr "" + +# f838da91fa8045d89293ced7d8692fc2 +#: ../../source/development_guide/testing_kernels.rst:4 +msgid "Testing Kernels" +msgstr "" + +# ac92e155007c43bc80418b77b9a0cf88 +#: ../../source/development_guide/testing_kernels.rst:9 +msgid "" +"IPython makes it very easy to create wrapper kernels using its kernel " +"framework. It requires extending the Kernel class and implementing a set " +"of methods for the core functions like execute, history etc. Its also " +"possible to write a full blown kernel in a language of your choice " +"implementing listeners for all the zmq ports." +msgstr "" + +# f736b303e5ac4f49bbc8a3f25e509692 +#: ../../source/development_guide/testing_kernels.rst:15 +msgid "" +"The key problem for any kernel implemented by these methods is to ensure " +"that it meets the message specification. The kerneltest command is a " +"means to test the installed kernel against the message spec and validate " +"the results." +msgstr "" + +# 91370782e52f4012abf6b8acf0a5bc16 +#: ../../source/development_guide/testing_kernels.rst:21 +msgid "The kerneltest tool" +msgstr "" + +# 0e98a93a5d064fdabde647dc8406ff87 +#: ../../source/development_guide/testing_kernels.rst:23 +msgid "" +"The kerneltest tool is part of IPython.testing and is also included in " +"the scripts similar to iptest. This takes 2 parameters - the name of the " +"kernel to test and the test script file. The test script file should be " +"in json format as described in the next section." +msgstr "" + +# 3ce7cd1696494c4eae12a69ea3b741ee +#: ../../source/development_guide/testing_kernels.rst:32 +msgid "" +"You can also pass in an optional message spec version to the command. At " +"the moment only the version 5 is supported, but as newer versions are " +"released this can be used to test the kernel against a specific version " +"of the kernel." +msgstr "" + +# d2b4dcfce0e84905b4c9bfc15f589e93 +#: ../../source/development_guide/testing_kernels.rst:41 +msgid "" +"The kernel to be tested needs to be installed and the kernelspec " +"available in the user IPython directory. The tool will instantiate the " +"kernel and send the commands over ZMQ. For each command executed on the " +"kernel, the tool will validate the reply to ensure that it matches the " +"message specification. In some cases the output is also checked, but the " +"reply is always returned and printed out on the console. This can be used" +" to validate that apart from meeting the message spec the kernel also " +"produced the correct output." +msgstr "" + +# 810f483237f74986bf01858b41067f9a +#: ../../source/development_guide/testing_kernels.rst:51 +msgid "The test script file" +msgstr "" + +# a645935aa17a44a3924eac56c4b49160 +#: ../../source/development_guide/testing_kernels.rst:53 +msgid "" +"The test script file is a simple json file that specifies the command to " +"execute and the test code to execute for the command." +msgstr "" + +# 1d1a27261190419b852cc9ddc37c4615 +#: ../../source/development_guide/testing_kernels.rst:64 +msgid "" +"For some commands in the message specification like kernel\\_info there " +"is no need to specify the test\\_code parameter. The tool validates if it" +" has all the inputs needed to execute the command and will print out an " +"error to the console if it finds a missing parameter. Since the " +"validation is built in, and only required parameters are passed, it is " +"possible to add additional fields in the json file for test " +"documentation." +msgstr "" + +# ecab2837ce3b434db96892386181204c +#: ../../source/development_guide/testing_kernels.rst:82 +msgid "A sample test script for the redis kernel will look like this" +msgstr "" + +# beddc03b335a4e8fb4cd44d441db527b +#~ msgid "" +#~ "In general, objects should declare, in" +#~ " their *class*, all attributes the " +#~ "object is meant to hold throughout " +#~ "its life. While Python allows you " +#~ "to add an attribute to an instance" +#~ " at any point in time, this " +#~ "makes the code harder to read and" +#~ " requires methods to constantly use " +#~ "checks with hasattr() or try/except " +#~ "calls. By declaring all attributes of" +#~ " the object in the class header, " +#~ "there is a single place one can" +#~ " refer to for understanding the " +#~ "object's data interface, where comments " +#~ "can explain the role of each " +#~ "variable and when possible, sensible " +#~ "deafaults can be assigned." +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/glossary.po b/docs/source/locale/en/LC_MESSAGES/glossary.po new file mode 100644 index 000000000..2c2bc1ac3 --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/glossary.po @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2019-07-04 19:51-0400\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.6.0\n" + +# 938cb2236c5e4a24a0d1cd9f80149b27 +#: ../../source/glossary.rst:5 +msgid "Glossary" +msgstr "" + +# 9d41e58ffa16468b8e023a9712b29b3b +#: ../../source/glossary.rst:8 +msgid "command line" +msgstr "" + +# 5f6a8ec0ea1d4dad93821e3a29a9e5a5 +#: ../../source/glossary.rst:10 +msgid "The terminal or console window where you type commands." +msgstr "" + +# a9505efde187467c88289d5b5c57bc92 +#: ../../source/glossary.rst:11 +msgid "Command Prompt" +msgstr "" + +# fb1bf6539f8d4152a96bbfff01ede6bb +#: ../../source/glossary.rst:13 +msgid "" +"On Windows, this is the application where commands are typed into a " +"window for execution." +msgstr "" + +# a53402578c0c4ec4aef323352f576b9c +#: ../../source/glossary.rst:15 +msgid "conda" +msgstr "" + +# 48aea7fb60ea46b48b9d5cecc6b7c9f6 +#: ../../source/glossary.rst:17 +msgid "The package manager for Anaconda." +msgstr "" + +# 9144299b6c03438697d2df100f252f0c +#: ../../source/glossary.rst:18 +msgid "config" +msgstr "" + +# af39f4ba81f8473f919ef55fefc8023c +#: ../../source/glossary.rst:20 +msgid "Refers to the configuration files and process." +msgstr "" + +# 7621f3badf974780adee77534f946e48 +#: ../../source/glossary.rst:21 +msgid "kernel" +msgstr "" + +# ac15ce043620490d8fc7a9d46fc5d4ae +#: ../../source/glossary.rst:23 +msgid "" +"A kernel provides programming language support in Jupyter. IPython is the" +" default kernel. Additional kernels include R, Julia, and many more." +msgstr "" + +# 6c87a739094e41f5b1ab517a786e0376 +#: ../../source/glossary.rst:25 +msgid "Notebook Dashboard" +msgstr "" + +# f5dc136dc22c4ea5bf8f382048d69acd +#: ../../source/glossary.rst:27 +msgid "" +"The notebook user interface which shows a list of the notebooks, files, " +"and subdirectories in the directory where the notebook server is started." +msgstr "" + +# 9d4b3fafd38844b3913fef20c976aea2 +#: ../../source/glossary.rst:30 +msgid "pip" +msgstr "" + +# dde7ae79c1cd4295989a3d816c0d9106 +#: ../../source/glossary.rst:32 +msgid "Python package manager." +msgstr "" + +# 025167dfb0b849158f1433aafcc4b7c3 +#: ../../source/glossary.rst:33 +msgid "profiles" +msgstr "" + +# 4f1bce8c1652475c9e8c7313bdcc0155 +#: ../../source/glossary.rst:35 +msgid "" +"Not available in Jupyter. In IPython 3, profiles are collections of " +"configuration and runtime files." +msgstr "" + +# 98ba4c37a4704f0a84921a8a7f14b8cb +#: ../../source/glossary.rst:37 +msgid "REPL" +msgstr "" + +# 1127a9c1dee04fc18f0af7e6d4087e5b +#: ../../source/glossary.rst:39 +msgid "read-eval-print-loop." +msgstr "" + +# dbf08896a556455faf46a74c9049cdc4 +#: ../../source/glossary.rst:40 +msgid "terminal" +msgstr "" + +# fb3383cb17244feba592bcdc60f6bdeb +#: ../../source/glossary.rst:42 +msgid "A window used to type in commands to be executed (Linux and OS X)." +msgstr "" + +# ec11c3cf781043bcb094685869a6fd12 +#: ../../source/glossary.rst:43 +msgid "widget" +msgstr "" + +# 204b394a671c4318ad854b78304049d8 +#: ../../source/glossary.rst:45 +msgid "" +"A user interface component, similar to a plugin, that allows customized " +"input, such as a slider." +msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/index.po b/docs/source/locale/en/LC_MESSAGES/index.po new file mode 100644 index 000000000..6517a73b2 --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/index.po @@ -0,0 +1,739 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2020. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2021-02-28 00:41+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.9.0\n" + +#: ../../source/index.md:1 bf89968877074d9ea8649a7c4069377c +msgid "Jupyter Project Documentation" +msgstr "" + +#: ../../source/index.md:3 0f701e86dd9248a7aea38f3d737119f2 +msgid "" +"**Welcome to the Jupyter Project documentation**. This website acts as " +"\"meta\" documentation for the Jupyter ecosystem. It has a collection of " +"resources to navigate the tools and communities in this ecosystem, and to" +" help you get started." +msgstr "" + +#: ../../source/index.md:8 232876daa16742e79c34e15e876b8ac6 +msgid "Start Here" +msgstr "" + +#: ../../source/index.md:10 e6cc1c89962748718d1fc190a36407d7 +msgid "{doc}`Get started with Jupyter Notebook `" +msgstr "" + +#: ../../source/index.md:12 04b32bbbf52a48019e8f7136f7fb4461 +msgid "Try the notebook" +msgstr "" + +#: ../../source/index.md:14 24a26cf98dcb45be8a28e2cd4525d9a3 +msgid "{doc}`Community `" +msgstr "" + +#: ../../source/index.md:16 e929e4ec79084efeac081d2339eefcd2 +msgid "Sustainability and growth" +msgstr "" + +#: ../../source/index.md:18 662cad3aba72405092586e58e9834870 +msgid "{doc}`Architecture `" +msgstr "" + +#: ../../source/index.md:20 cf7243768ae246aebeb49f07ee12ae09 +msgid "What is Jupyter?" +msgstr "" + +#: ../../source/index.md:22 2932369a57ba42358fb8ad035068ae80 +msgid "{doc}`Contributor Guides `" +msgstr "" + +#: ../../source/index.md:24 f73e4092f72b4076b82dc1f6f01d0e8b +msgid "How to contribute to the projects" +msgstr "" + +#: ../../source/index.md:26 f66c633359f749b1aaa2ad948527da8c +msgid "{doc}`Narratives and Use Cases `" +msgstr "" + +#: ../../source/index.md:28 7328928961e74f1faf2043cbce9181ab +msgid "Narratives of common deployment scenarios" +msgstr "" + +#: ../../source/index.md:30 efc6b085e7284b7abad39c0c48f7d5a3 +msgid "{doc}`Release Notes `" +msgstr "" + +#: ../../source/index.md:32 e66735bdbbe143d484cb12c0f6aacdfb +msgid "New features, upgrades, deprecation notes, and bug fixes" +msgstr "" + +#: ../../source/index.md:34 55318c5d57d84102a0806f1c7c8d2bc7 +msgid "{doc}`IPython `" +msgstr "" + +#: ../../source/index.md:36 e95d1d58ef41492c809d4b77a5d9868d +msgid "An interactive Python kernel and REPL" +msgstr "" + +#: ../../source/index.md:38 e3e9d1f0a67c493a8116f9181b6b262e +msgid "{doc}`Reference `" +msgstr "" + +#: ../../source/index.md:40 cb18ae3862a44ff68f3c055fd70693dc +msgid "APIs" +msgstr "" + +#: ../../source/index.md:42 41fbb5ab8e8747c8b9b7dcc1c8a0f744 +msgid "{doc}`Installation, Configuration, and Usage `" +msgstr "" + +#: ../../source/index.md:44 98618984bfba456b8be01b6ea29b7794 +msgid "Documentation for users" +msgstr "" + +#: ../../source/index.md:46 dd01bd73ed4049d18aa7bec77ab12801 +msgid "{doc}`Advanced `" +msgstr "" + +#: ../../source/index.md:48 4de856ec5f0a4f9d88d1f31a08edae99 +msgid "Documentation for advanced use-cases" +msgstr "" + +#: ../../source/index.md:54 ea769180309d4ae5a6fce73d6a49b8b8 +msgid "Sub-project documentation" +msgstr "" + +#: ../../source/index.md:56 4021cfd31f3a404ab87bc1beaa7ec1b7 +msgid "Jupyter User Interfaces" +msgstr "" + +#: ../../source/index.md:58 12e5b46f950e45f58a6b661852e9bc72 +msgid "[Jupyter Notebook](http://jupyter-notebook.readthedocs.io/en/latest/)" +msgstr "" + +#: ../../source/index.md:59 263de66420914f768021130a155e9bb1 +msgid "[Jupyter console](http://jupyter_console.readthedocs.io/en/latest)" +msgstr "" + +#: ../../source/index.md:60 db5aaacf5d9148dbbb0692139260e880 +msgid "[Qt console](https://qtconsole.readthedocs.io/en/stable)" +msgstr "" + +#: ../../source/index.md:63 162f21b9370144a383e6cdce730caa70 +msgid "JupyterHub" +msgstr "" + +#: ../../source/index.md:65 b47fb4496906459a920e50793d334139 +msgid "[JupyterHub](http://jupyterhub.readthedocs.io/en/latest)" +msgstr "" + +#: ../../source/index.md:66 1fa8fc5a2aa14fd09fd5421323bbeb69 +msgid "" +"[configurable HTTP proxy](https://github.com/jupyter/configurable-http-" +"proxy)" +msgstr "" + +#: ../../source/index.md:67 183a2789abe3475cbefb81adde60c3a2 +msgid "[dockerspawner](https://github.com/jupyter/dockerspawner)" +msgstr "" + +#: ../../source/index.md:68 c7f59a7c173744d4ae54fa3d5156a2f3 +msgid "[ldapauthenticator](https://github.com/jupyter/ldapauthenticator)" +msgstr "" + +#: ../../source/index.md:69 d240eb0f4f024121afbce4230d52688f +msgid "[oauthenticator](https://github.com/jupyter/oauthenticator)" +msgstr "" + +#: ../../source/index.md:70 3f3d4cc58fec4d2d8add2077d885dba1 +msgid "[sudospawner](https://github.com/jupyter/sudospawner)" +msgstr "" + +#: ../../source/index.md:73 65cf13ce937f41d7a7dbbdbaf607b5ce +msgid "Education" +msgstr "" + +#: ../../source/index.md:75 a507d6c820194b5d83629f0da035a1b4 +msgid "[nbgrader](http://nbgrader.readthedocs.io/en/latest)" +msgstr "" + +#: ../../source/index.md:78 7ccc3de999934d16913f2e32cbe23869 +msgid "Conversion and Formatting" +msgstr "" + +#: ../../source/index.md:80 4362e8c8723d47c98a5204a6af23922e +msgid "[nbconvert](http://nbconvert.readthedocs.io/en/latest)" +msgstr "" + +#: ../../source/index.md:81 83e3a6d58f0244829699f4871fce839d +msgid "[nbformat](http://nbformat.readthedocs.io/en/latest)" +msgstr "" + +#: ../../source/index.md:84 264cf34a76e44443ae217793493a46cf +msgid "Kernels" +msgstr "" + +#: ../../source/index.md:86 766a8c7a60a84f94a78ac9085741fe42 +msgid "[IPython](https://ipython.readthedocs.io/en/stable>)" +msgstr "" + +#: ../../source/index.md:87 65e933664ad04dd282a4c6a9d188db84 +msgid "[IRkernel](https://irkernel.github.io)" +msgstr "" + +#: ../../source/index.md:88 e0b532ff74894460bc3a9ce0fd55882b +msgid "[IJulia](https://github.com/JuliaLang/IJulia.jl)" +msgstr "" + +#: ../../source/index.md:89 83199c73baf04ef3822c263259125424 +msgid "" +"[Community maintained kernels](https://github.com/ipython/ipython/wiki" +"/IPython-kernels-for-other-languages)" +msgstr "" + +#: ../../source/index.md:92 af325a8c703c490687e65ade0757f2cd +msgid "IPython" +msgstr "" + +#: ../../source/index.md:94 e701c24c0fc742348ce24d71e3596876 +msgid "[IPython](http://ipython.readthedocs.io/en/stable>)" +msgstr "" + +#: ../../source/index.md:95 a9fbe3e72f064417ba2a06943b910b3f +msgid "[ipykernel](https://ipython.readthedocs.io/en/stable)" +msgstr "" + +#: ../../source/index.md:96 fd43898a63b0420f87bd6ec8fa1a3c9c +msgid "[ipyparallel](https://ipyparallel.readthedocs.io/en/latest)" +msgstr "" + +#: ../../source/index.md:99 7307576f339e4d5fb18488e73778e426 +msgid "Architecture" +msgstr "" + +#: ../../source/index.md:101 52ea2472623f44508e35aaa5bc27554a +msgid "[jupyter_client](http://jupyter-client.readthedocs.io/en/latest)" +msgstr "" + +#: ../../source/index.md:102 c49ed39d8c79432cbe9c5f82bf61c422 +msgid "[jupyter_core](http://jupyter-core.readthedocs.io/en/latest)" +msgstr "" + +#: ../../source/index.md:105 b3a6d72ac13d4676b8ced725aa807958 +msgid "Deployment" +msgstr "" + +#: ../../source/index.md:107 aa0e9af6e38845ce83d1a23dcc969d17 +msgid "[docker-stacks](https://github.com/jupyter/docker-stacks)" +msgstr "" + +#: ../../source/index.md:108 55999d66cbcb4d38b044f4b5d393f6f3 +msgid "[jupyter-sphinx-theme](https://github.com/jupyter/jupyter-sphinx-theme)" +msgstr "" + +#: ../../source/index.md:109 b874407c1f9843dca9bb62d5fe439d20 +msgid "[kernel_gateway](http://jupyter-kernel-gateway.readthedocs.io/en/latest)" +msgstr "" + +#: ../../source/index.md:110 59606480542643ac88b1b629feb77305 +msgid "[nbviewer](https://github.com/jupyter/nbviewer)" +msgstr "" + +#: ../../source/index.md:111 8904def09c00448bb6c952a2dcbfd98d +msgid "[tmpnb](https://github.com/jupyter/tmpnb)" +msgstr "" + +#: ../../source/index.md:112 aa34402194304014b32dc53f6fe59cd9 +msgid "[traitlets](http://traitlets.readthedocs.io/en/stable)" +msgstr "" + +#: ../../source/index.md:115 97f4bae9a9714008827dd3d8d6e31e7c +msgid "JupyterLab" +msgstr "" + +#: ../../source/index.md:117 c0f99f466e054787b36c4a9033a8f654 +msgid "[JupyterLab](https://github.com/jupyterlab/jupyterlab)" +msgstr "" + +#: ../../source/index.md:118 2be53fec0747421091f57c873bb9b207 +msgid "[ipywidgets](https://ipywidgets.readthedocs.io/en/latest)" +msgstr "" + +#: ../../source/index.md:123 0c64c07a0d7d4e0ea867b8f5a9db9729 +msgid "Table of Contents" +msgstr "" + +#: ../../source/index.md:170 b37fe368edec4888be565664fb19bf7d +msgid "Resources" +msgstr "" + +#: ../../source/index.md:172 cbba8ed45a174b79be74d0c58f7cfee3 +msgid "Site" +msgstr "" + +#: ../../source/index.md:172 eba5c392904340c691693984aae3db6e +msgid "Description" +msgstr "" + +#: ../../source/index.md:172 288cc957c9204cd398b197e3f81573b6 +msgid "[Jupyter website](https://jupyter.org)" +msgstr "" + +#: ../../source/index.md:172 75e2d24a68714c19a3e86f5843a9b65b +msgid "Keep up to date on Jupyter" +msgstr "" + +#: ../../source/index.md:172 77182499e0274662860f9a1000a92584 +msgid "[IPython website](https://ipython.org)" +msgstr "" + +#: ../../source/index.md:172 250f519ecf4f449d97bdd32834ae6e34 +msgid "Learn more about IPython" +msgstr "" + +#: ../../source/index.md:172 ddcebdcd3277416f92f571a6710ac53f +msgid "[jupyter/help repo](https://github.com/jupyter/help)" +msgstr "" + +#: ../../source/index.md:172 a4ad3bc7a9d84f51b392f1e51cf2f51f +msgid "Start here for help and support questions" +msgstr "" + +#: ../../source/index.md:172 c707d5d70941499583578bcab5e12cf1 +msgid "[Jupyter mailing list](https://groups.google.com/forum/#!forum/jupyter)" +msgstr "" + +#: ../../source/index.md:172 c81544c67bb14440b3130c93d09395fd +msgid "General discussion of Jupyter's use" +msgstr "" + +#: ../../source/index.md:172 868e5189ffae4cc4bc8d1c50fb80d623 +msgid "" +"[Jupyter in Education group](https://groups.google.com/forum/#!forum" +"/jupyter-education)" +msgstr "" + +#: ../../source/index.md:172 5f6a91f31f7449149287b061002667bc +msgid "Discussion of Jupyter's use in education" +msgstr "" + +#: ../../source/index.md:172 84a3311a9fcb4e83857872d231c00e55 +msgid "[NumFocus](http://www.numfocus.org)" +msgstr "" + +#: ../../source/index.md:172 26b6d75f1b0d4bcfbbeee2f859d51238 +msgid "Promotes world-class, innovative, open source scientific software" +msgstr "" + +#: ../../source/index.md:172 370fbbe1fcaa4a62b2e12149d3185662 +msgid "" +"[Donate to Project Jupyter](https://numfocus.salsalabs.org/donate-to-" +"jupyter/index.html)" +msgstr "" + +#: ../../source/index.md:172 6e077789dcf04f05a72d427f12590258 +msgid "Please contribute to open science collaboration and sustainability" +msgstr "" + +#: ../../source/index.md:186 1218f525bd5a4132b35d31957eb39c1c +msgid "Indices and tables" +msgstr "" + +#: ../../source/index.md:188 ffefc4fd63db4f64bd054bd7797eddfb +msgid "{ref}`genindex`" +msgstr "" + +#: ../../source/index.md:189 cfa5fc4402974e2dbd00aa9fdd5775af +msgid "{ref}`glossary`" +msgstr "" + +#: ../../source/index.md:190 f6b7d680a1f240528a3e59328a900c1b +msgid "{ref}`search`" +msgstr "" + +#~ msgid "`Jupyter Notebook Quickstart `_" +#~ msgstr "" + +#~ msgid "`Community `_" +#~ msgstr "" + +#~ msgid "`Architecture `_" +#~ msgstr "" + +#~ msgid "`Contributor Guides `_" +#~ msgstr "" + +#~ msgid "`Narratives and Use Cases `_" +#~ msgstr "" + +#~ msgid "`Release Notes `_" +#~ msgstr "" + +#~ msgid "`IPython `_" +#~ msgstr "" + +#~ msgid "`Reference `_" +#~ msgstr "" + +#~ msgid "`Installation, Configuration, and Usage `_" +#~ msgstr "" + +#~ msgid ":doc:`Jupyter Notebook Quickstart `" +#~ msgstr "" + +#~ msgid ":doc:`Narratives and Use Cases `" +#~ msgstr "" + +#~ msgid ":doc:`IPython `" +#~ msgstr "" + +#~ msgid ":doc:`Advanced `" +#~ msgstr "" + +#~ msgid ":doc:`Architecture `" +#~ msgstr "" + +#~ msgid ":doc:`Contributor Guides `" +#~ msgstr "" + +#~ msgid ":doc:`Narratives and Use Cases `" +#~ msgstr "" + +#~ msgid ":doc:`Advanced `" +#~ msgstr "" + +#~ msgid "`IPython `_" +#~ msgstr "" + +#~ msgid "`IPython `_" +#~ msgstr "" + +#~ msgid "" +#~ "**Welcome to the Jupyter Project " +#~ "documentation**. This website acts as " +#~ "\"meta\" documentation for the Jupyter " +#~ "ecosystem. It has a collection of " +#~ "resources to navigate the tools and " +#~ "communities in this ecosystem, and to" +#~ " help you get started." +#~ msgstr "" + +#~ msgid ":doc:`Get started with Jupyter Notebook `" +#~ msgstr "" + +#~ msgid ":doc:`Community `" +#~ msgstr "" + +#~ msgid ":doc:`Architecture `" +#~ msgstr "" + +#~ msgid ":doc:`Contributor Guides `" +#~ msgstr "" + +#~ msgid ":doc:`Narratives and Use Cases `" +#~ msgstr "" + +#~ msgid ":doc:`Release Notes `" +#~ msgstr "" + +#~ msgid ":doc:`IPython `" +#~ msgstr "" + +#~ msgid ":doc:`Reference `" +#~ msgstr "" + +#~ msgid "" +#~ ":doc:`Installation, Configuration, and Usage " +#~ "`" +#~ msgstr "" + +#~ msgid ":doc:`Advanced `" +#~ msgstr "" + +#~ msgid "`Jupyter Notebook `_" +#~ msgstr "" + +#~ msgid "`Jupyter console `_" +#~ msgstr "" + +#~ msgid "`Qt console `_" +#~ msgstr "" + +#~ msgid "`JupyterHub `_" +#~ msgstr "" + +#~ msgid "" +#~ "`configurable HTTP proxy `_" +#~ msgstr "" + +#~ msgid "`dockerspawner `_" +#~ msgstr "" + +#~ msgid "`ldapauthenticator `_" +#~ msgstr "" + +#~ msgid "`oauthenticator `_" +#~ msgstr "" + +#~ msgid "`sudospawner `_" +#~ msgstr "" + +#~ msgid "`nbgrader `_" +#~ msgstr "" + +#~ msgid "`nbconvert `_" +#~ msgstr "" + +#~ msgid "`nbformat `_" +#~ msgstr "" + +#~ msgid "`IPython `__" +#~ msgstr "" + +#~ msgid "`IRkernel `_" +#~ msgstr "" + +#~ msgid "`IJulia `_" +#~ msgstr "" + +#~ msgid "" +#~ "`Community maintained kernels " +#~ "`_" +#~ msgstr "" + +#~ msgid "`IPython `__" +#~ msgstr "" + +#~ msgid "`ipykernel `_" +#~ msgstr "" + +#~ msgid "`ipyparallel `_" +#~ msgstr "" + +#~ msgid "`jupyter_client `_" +#~ msgstr "" + +#~ msgid "`jupyter_core `_" +#~ msgstr "" + +#~ msgid "`docker-stacks `_" +#~ msgstr "" + +#~ msgid "" +#~ "`jupyter-sphinx-theme `_" +#~ msgstr "" + +#~ msgid "" +#~ "`kernel_gateway `_" +#~ msgstr "" + +#~ msgid "`nbviewer `_" +#~ msgstr "" + +#~ msgid "`tmpnb `_" +#~ msgstr "" + +#~ msgid "`traitlets `_" +#~ msgstr "" + +#~ msgid "`JupyterLab `_" +#~ msgstr "" + +#~ msgid "`ipywidgets `_" +#~ msgstr "" + +#~ msgid "`Jupyter website `_" +#~ msgstr "" + +#~ msgid "`IPython website `_" +#~ msgstr "" + +#~ msgid "`jupyter/help repo `_" +#~ msgstr "" + +#~ msgid "" +#~ "`Jupyter mailing list " +#~ "`_" +#~ msgstr "" + +#~ msgid "" +#~ "`Jupyter in Education group " +#~ "`_" +#~ msgstr "" + +#~ msgid "`NumFocus `_" +#~ msgstr "" + +#~ msgid "" +#~ "`Donate to Project Jupyter " +#~ "`_" +#~ msgstr "" + +#~ msgid ":ref:`genindex`" +#~ msgstr "" + +#~ msgid ":ref:`glossary`" +#~ msgstr "" + +#~ msgid ":ref:`search`" +#~ msgstr "" + +#~ msgid "" +#~ "Welcome to the Jupyter Project " +#~ "documentation. This website acts as " +#~ "\"meta\" documentation for the Jupyter " +#~ "ecosystem. It has a collection of " +#~ "resources to navigate the tools and " +#~ "communities in this ecosystem, and to" +#~ " help you get started." +#~ msgstr "" + +#~ msgid "Get started with Jupyter Notebook" +#~ msgstr "" + +#~ msgid "Community" +#~ msgstr "" + +#~ msgid "Contributor Guides" +#~ msgstr "" + +#~ msgid "Narratives and Use Cases" +#~ msgstr "" + +#~ msgid "Release Notes" +#~ msgstr "" + +#~ msgid "Reference" +#~ msgstr "" + +#~ msgid "Installation, Configuration, and Usage" +#~ msgstr "" + +#~ msgid "Advanced" +#~ msgstr "" + +#~ msgid "Jupyter Notebook" +#~ msgstr "" + +#~ msgid "Jupyter console" +#~ msgstr "" + +#~ msgid "Qt console" +#~ msgstr "" + +#~ msgid "configurable HTTP proxy" +#~ msgstr "" + +#~ msgid "dockerspawner" +#~ msgstr "" + +#~ msgid "ldapauthenticator" +#~ msgstr "" + +#~ msgid "oauthenticator" +#~ msgstr "" + +#~ msgid "sudospawner" +#~ msgstr "" + +#~ msgid "nbgrader" +#~ msgstr "" + +#~ msgid "nbconvert" +#~ msgstr "" + +#~ msgid "nbformat" +#~ msgstr "" + +#~ msgid "IRkernel" +#~ msgstr "" + +#~ msgid "IJulia" +#~ msgstr "" + +#~ msgid "Community maintained kernels" +#~ msgstr "" + +#~ msgid "ipykernel" +#~ msgstr "" + +#~ msgid "ipyparallel" +#~ msgstr "" + +#~ msgid "jupyter_client" +#~ msgstr "" + +#~ msgid "jupyter_core" +#~ msgstr "" + +#~ msgid "docker-stacks" +#~ msgstr "" + +#~ msgid "jupyter-sphinx-theme" +#~ msgstr "" + +#~ msgid "kernel_gateway" +#~ msgstr "" + +#~ msgid "nbviewer" +#~ msgstr "" + +#~ msgid "tmpnb" +#~ msgstr "" + +#~ msgid "traitlets" +#~ msgstr "" + +#~ msgid "ipywidgets" +#~ msgstr "" + +#~ msgid "Jupyter website" +#~ msgstr "" + +#~ msgid "IPython website" +#~ msgstr "" + +#~ msgid "jupyter/help repo" +#~ msgstr "" + +#~ msgid "Jupyter mailing list" +#~ msgstr "" + +#~ msgid "Jupyter in Education group" +#~ msgstr "" + +#~ msgid "NumFocus" +#~ msgstr "" + +#~ msgid "Donate to Project Jupyter" +#~ msgstr "" + +#~ msgid "genindex" +#~ msgstr "" + +#~ msgid "glossary" +#~ msgstr "" + +#~ msgid "search" +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/install-kernel.po b/docs/source/locale/en/LC_MESSAGES/install-kernel.po new file mode 100644 index 000000000..68c88dcc7 --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/install-kernel.po @@ -0,0 +1,108 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2019-07-04 19:51-0400\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.6.0\n" + +# efdc3f834e74419fa6a4b57c74ee4fcd +#: ../../source/install-kernel.rst:3 +msgid "*Optional:* Installing Kernels" +msgstr "" + +# a8453d1a49ac44b1a666c35084a9ae4d +#: ../../source/install-kernel.rst:7 +msgid "Contents" +msgstr "" + +# da930aecf67d4103b678a613f2b8f9ae +#: ../../source/install-kernel.rst:9 +msgid "" +"This information gives a high-level view of using Jupyter Notebook with " +"different programming languages (kernels)." +msgstr "" + +# 0b4e24aa51dd400782dfff162b605bb3 +#: ../../source/install-kernel.rst:13 +msgid "Are any languages pre-installed?" +msgstr "" + +# ea86f10aa988483fbc44ed6fc2ed5c1c +#: ../../source/install-kernel.rst:15 +msgid "" +"Yes, installing the Jupyter Notebook will also install the `IPython " +"`_ :term:`kernel`. This allows" +" working on notebooks using the Python programming language." +msgstr "" + +# 94ea0ff4960049e8bffc34755b0c57d0 +#: ../../source/install-kernel.rst:20 +msgid "How do I install Python 2 and Python 3?" +msgstr "" + +# 9e28ab95796d4facb934d8a06dbaf56c +#: ../../source/install-kernel.rst:22 +msgid "" +"To install an additional version of Python, i.e. to have both Python 2 " +"and 3 available, see the IPython docs on `installing kernels " +"`_." +msgstr "" + +# fc0d1726d8ff4504922a6164a4841b27 +#: ../../source/install-kernel.rst:27 +msgid "How do I install other languages like R or Julia?" +msgstr "" + +# 3eff7ec0dacb45dc9198c7dc21af8e4e +#: ../../source/install-kernel.rst:29 +msgid "" +"To run notebooks in languages other than Python, such as R or Julia, you " +"will need to install additional kernels. For more information, see the " +"full `list of available kernels`_." +msgstr "" + +# a15c5c1d7def408f8bf85bb8b39608f6 +#: ../../source/install-kernel.rst:37 +msgid ":ref:`Jupyter Projects `" +msgstr "" + +# 8a2af66f6aa14ac2ae3d77f3214ed281 +#: ../../source/install-kernel.rst:36 +msgid "" +"Detailed installation instructions for individual Jupyter or IPython " +"projects." +msgstr "" + +# ea589c0dbe5d4f7a8f61edf4c78fa86b +#: ../../source/install-kernel.rst:40 +msgid ":ref:`Kernels `" +msgstr "" + +# 0bd2cf28af6e4107a801fb8e3d0e0ac3 +#: ../../source/install-kernel.rst:40 +msgid "Information about additional programming language kernels." +msgstr "" + +# 8ce58b34c6cb4505ae83e5359e506a04 +#: ../../source/install-kernel.rst:42 +msgid ":ref:`Kernels documentation for Jupyter client `" +msgstr "" + +# 9d06f59e323b40d497adf08f5a3c677f +#: ../../source/install-kernel.rst:43 +msgid "Technical information about kernels." +msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/install.po b/docs/source/locale/en/LC_MESSAGES/install.po new file mode 100644 index 000000000..896065c15 --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/install.po @@ -0,0 +1,456 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2021-01-21 18:52+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.9.0\n" + +#: ../../source/install.rst:5 86def18d699c44928ad1a3d265bf2009 +msgid "Install and Use" +msgstr "" + +#: ../../source/install.rst:9 2ef6fb3da2ed41e7a8b8f0c34d923474 +msgid "" +"This page contains information and links about installing and using tools" +" across the Jupyter ecosystem. Generally speaking, the documentation of " +"each tool is the place to learn about the best-practices for how to " +"install and use the tool." +msgstr "" + +#: ../../source/install.rst:14 b5dde42612e24774b2dc222ae405a48e +msgid "Jupyter Notebook Interface" +msgstr "" + +#: ../../source/install.rst:16 6868c4df01c2430d98b9c483a8ecab9b +msgid "" +"The **Jupyter Notebook interface** is a Web-based application for " +"authoring documents that combine live-code with narrative text, equations" +" and visualizations." +msgstr "" + +#: ../../source/install.rst:20 b01e6bcf87c94d6b8546904f4a9ab6e6 +msgid "`GitHub Repo `__" +msgstr "" + +#: ../../source/install.rst:21 1a669f892df14aedaf7c00fe603fb65f +msgid "`Docs `_" +msgstr "" + +#: ../../source/install.rst:31 bf93bb08cb6a4eca94f03e3c1d115061 +msgid "Jupyter Lab" +msgstr "" + +#: ../../source/install.rst:33 a00fa41954554f33910cc957c0dc3aca +msgid "" +"**JupyterLab** is a next-generation web-based user interface for Project " +"Jupyter." +msgstr "" + +#: ../../source/install.rst:35 9e643b1850ca4a37968d43e0830be5b5 +msgid "`GitHub Repo `__" +msgstr "" + +#: ../../source/install.rst:36 8f172578852945a6901ffd3453761037 +msgid "`Docs `__" +msgstr "" + +#: ../../source/install.rst:37 3c0cbddd30ff44b7a3e1de56b8144adc +msgid "" +"`Install instructions " +"`__" +msgstr "" + +#: ../../source/install.rst:41 94a75624534b452c93d7f2fe9087b867 +msgid "Jupyter Hub" +msgstr "" + +#: ../../source/install.rst:43 0d6cc8ca69374a4b8e5223b1693c3d06 +msgid "" +"**JupyterHub** is a multi-user hub for interactive computing sessions, " +"made for teams and organizations, and with pluggable authentication and " +"scalability." +msgstr "" + +#: ../../source/install.rst:46 e1f74c7780d143b6bd95487d3c90a4cd +msgid "`GitHub Repo `__" +msgstr "" + +#: ../../source/install.rst:47 0254214bd75941cd9a97535bcc4e4b27 +msgid "`Docs `__" +msgstr "" + +#: ../../source/install.rst:48 196c6b33791c48f1b29f4534d8abc681 +msgid "" +"`Install instructions `__" +msgstr "" + +#: ../../source/install.rst:52 500b36b6166e45d0bba11685da745377 +msgid "Jupyter Console" +msgstr "" + +#: ../../source/install.rst:54 bf09350864b844188f37d9f33db9364f +msgid "" +"The **Jupyter Console** is a terminal-based console for interactive " +"computing." +msgstr "" + +#: ../../source/install.rst:56 d994f2afe3744186bc741cf1b707258d +msgid "`GitHub Repo `__" +msgstr "" + +#: ../../source/install.rst:57 75c6b8340ed14d0392016a8a48044881 +msgid "" +"`Docs and Install instructions `_" +msgstr "" + +#: ../../source/install.rst:61 8ad1c4a8ed964c4aa0683bf2d6eb74c3 +msgid "Jupyter QtConsole" +msgstr "" + +#: ../../source/install.rst:63 965c2e24969c4f0d80a05202b9c30a56 +msgid "" +"The **Jupyter QtConsole** is a Qt application for interactive computing " +"with rich output." +msgstr "" + +#: ../../source/install.rst:65 bfa094ae4ea644d88358d89254d0fb22 +msgid "`GitHub Repo `__" +msgstr "" + +#: ../../source/install.rst:66 abe30f2c89404121ba50ba5f190b21a2 +msgid "`Docs `__" +msgstr "" + +#: ../../source/install.rst:67 66f81b523add4766894b8dd99360ffea +msgid "" +"`Install instructions " +"`__" +msgstr "" + +#: ../../source/install.rst:71 8a2d2b0cb4bd444680077acb571fd8f1 +msgid "Jupyter Kernels" +msgstr "" + +#: ../../source/install.rst:73 bc3191575e3f4fae819f4aa74a132465 +msgid "" +"You can install **Jupyter Kernels** to add support for new languages and " +"code behavior." +msgstr "" + +#: ../../source/install/kernels.rst:3 980dd79a12694e41ad267a597c7f5f0f +msgid "Installing Kernels" +msgstr "" + +#: ../../source/install/kernels.rst:5 d3e5b594ed494563b9d9de73de607478 +msgid "" +"This information gives a high-level view of using Jupyter Notebook with " +"different programming languages (kernels)." +msgstr "" + +#: ../../source/install/kernels.rst:9 1eeff811bae247458b0de2129a0c9700 +msgid "Are any languages pre-installed?" +msgstr "" + +#: ../../source/install/kernels.rst:11 7e9707b6a3ed4c07bd46a3f27f84a313 +msgid "" +"Yes, installing the Jupyter Notebook will also install the `IPython " +"`_ :term:`kernel`. This allows" +" working on notebooks using the Python programming language." +msgstr "" + +#: ../../source/install/kernels.rst:17 ed0a26bc7db54339b9881ad418fe5522 +msgid "How do I install Python 2 and Python 3?" +msgstr "" + +#: ../../source/install/kernels.rst:19 250fe8203640489b94db512bd790d1a7 +msgid "" +"To install an additional version of Python, i.e. to have both Python 2 " +"and 3 available, see the IPython docs on `installing kernels " +"`_." +msgstr "" + +#: ../../source/install/kernels.rst:25 f633e76349674f5eb0d7741886726933 +msgid "How do I install other languages like R or Julia?" +msgstr "" + +#: ../../source/install/kernels.rst:27 28ec4d06193748eca8e61f881f5974f8 +msgid "" +"To run notebooks in languages other than Python, such as R or Julia, you " +"will need to install additional kernels. For more information, see the " +"full `list of available kernels`_." +msgstr "" + +#: ../../source/install/kernels.rst:35 06d61e342ac64aa9991618f5427db583 +msgid ":doc:`Jupyter Projects `" +msgstr "" + +#: ../../source/install/kernels.rst:34 195087c7f3f8464ca92e4a91583ac8f1 +msgid "" +"Detailed installation instructions for individual Jupyter or IPython " +"projects." +msgstr "" + +#: ../../source/install/kernels.rst:38 96397b352756447185315226c183219d +msgid ":ref:`Kernels `" +msgstr "" + +#: ../../source/install/kernels.rst:38 5b685f8fb6ce4982ab5ed6893b775618 +msgid "Information about additional programming language kernels." +msgstr "" + +#: ../../source/install/kernels.rst:40 39c7b4e0fd8e4bdfae05117b3c215c1f +msgid ":ref:`Kernels documentation for Jupyter client `" +msgstr "" + +#: ../../source/install/kernels.rst:41 a8c1c57ef67844d1b61f435135256e18 +msgid "Technical information about kernels." +msgstr "" + +#: ../../source/install/notebook-classic.rst:3 7e099c0e0c9d455bae117453f51a6c7c +msgid "Installing the classic Jupyter Notebook interface" +msgstr "" + +#: ../../source/install/notebook-classic.rst:5 78c8c2e36b3645b080f136eb0b4aeb42 +msgid "" +"This section includes instructions on how to get started with **Jupyter " +"Notebook**. But there are multiple Jupyter user interfaces one can use, " +"based on their needs. Please checkout the list and links below for " +"additional information and instructions about how to get started with " +"each of them." +msgstr "" + +# 24944b561f924ddd911096f48f136f64 +#: ../../source/install/notebook-classic.rst:10 +#: 2cb333a9b1574fd194211686e1b199ff +msgid "" +"This information explains how to install the Jupyter Notebook and the " +"IPython kernel." +msgstr "" + +# 9adca524080f4c91b4eb73369181cac7 +#: ../../source/install/notebook-classic.rst:14 +#: 0d92271609f740f58d6a3081ddd78f68 +msgid "Prerequisite: Python" +msgstr "" + +# d169910c38f948b7ac2952e799e585d5 +#: ../../source/install/notebook-classic.rst:16 +#: 17a8ebf32f784f5596ded486f748823c +msgid "" +"While Jupyter runs code in many programming languages, **Python** is a " +"requirement (Python 3.3 or greater, or Python 2.7) for installing the " +"Jupyter Notebook." +msgstr "" + +# 085979bf68e84b0e9b15d137d1234a8b +#: ../../source/install/notebook-classic.rst:20 +#: 2140a0128e2642c8970f09ab623b044a +msgid "" +"We recommend using the `Anaconda `_ " +"distribution to install Python and Jupyter. We'll go through its " +"installation in the next section." +msgstr "" + +# 16c5366b626b4d39b19b501cccb27142 +#: ../../source/install/notebook-classic.rst:27 +#: 70eb7bb312c646f59148a8934166ee8c +msgid "Installing Jupyter using Anaconda and conda" +msgstr "" + +# 767eb05028794e92bc704d599083862d +#: ../../source/install/notebook-classic.rst:29 +#: 848b8c4193de4213a939bd11cf10375d +msgid "" +"For new users, we **highly recommend** `installing Anaconda " +"`_. Anaconda conveniently installs " +"Python, the Jupyter Notebook, and other commonly used packages for " +"scientific computing and data science." +msgstr "" + +# 05c5808a5e0148158765958378b90b6f +#: ../../source/install/notebook-classic.rst:34 +#: 4e1ab1e1742541bb96291775a6316267 +msgid "Use the following installation steps:" +msgstr "" + +# a27f5cc69d014699b0df24449e9429fd +#: ../../source/install/notebook-classic.rst:36 +#: efd067709e4942699f4020d4a7564c65 +msgid "" +"Download `Anaconda `_. We recommend " +"downloading Anaconda's latest Python 3 version (currently Python 3.7)." +msgstr "" + +# 4a21fbaf720541fda995cb60551befb4 +#: ../../source/install/notebook-classic.rst:39 +#: ee55f790dd7e4740abebd865bfb410b2 +msgid "" +"Install the version of Anaconda which you downloaded, following the " +"instructions on the download page." +msgstr "" + +# d5a47880420642eaba90590b54097b26 +#: ../../source/install/notebook-classic.rst:42 +#: 0271e223938948b5acb69219190ae385 +msgid "Congratulations, you have installed Jupyter Notebook. To run the notebook:" +msgstr "" + +# 6227c09c5e6b4a59be669bfb1c4c2fdc +#: ../../source/install/notebook-classic.rst:48 +#: 7626ec79cca549b78794b539f848b864 +msgid "See :ref:`Running the Notebook ` for more details." +msgstr "" + +# a57622d290e3435084627a34b100ce79 +#: ../../source/install/notebook-classic.rst:53 +#: 8c0a81fe848341a8beb887654d7e1190 +msgid "*Alternative for experienced Python users:* Installing Jupyter with pip" +msgstr "" + +# 4ff159ed555344a5b35b67086a401fda +#: ../../source/install/notebook-classic.rst:57 +#: da9ea4426ef0450cb29e69dbf21b79a0 +msgid "" +"Jupyter installation requires Python 3.3 or greater, or Python 2.7. " +"IPython 1.x, which included the parts that later became Jupyter, was the " +"last version to support Python 3.2 and 2.6." +msgstr "" + +# dbff8577777040db8c06790617420c29 +#: ../../source/install/notebook-classic.rst:61 +#: 6f516f3ec6114f819f4b09a5a2565151 +msgid "" +"As an existing Python user, you may wish to install Jupyter using " +"Python's package manager, :term:`pip`, instead of Anaconda." +msgstr "" + +# ef9257faebfd4ba4bbf41fda5f195413 +#: ../../source/install/notebook-classic.rst:66 +#: 861ef194c3e24b639384169adf33ce4f +msgid "" +"First, ensure that you have the latest pip; older versions may have " +"trouble with some dependencies:" +msgstr "" + +# bc2ec7faaa854a36bd339cbebc78741c +#: ../../source/install/notebook-classic.rst:73 +#: 7d44e9b6f30f4cedade698b228affc8b +msgid "Then install the Jupyter Notebook using:" +msgstr "" + +# cc79a3bf6e1a46b4bb1ab37da05e643d +#: ../../source/install/notebook-classic.rst:79 +#: b879fdea0b474998b4964e7d7770189f +msgid "(Use ``pip`` if using legacy Python 2.)" +msgstr "" + +# bedb9ecab9554259ae2a7d28ea48e972 +#: ../../source/install/notebook-classic.rst:81 +#: 50b26e79644942e7ba85d2baf3c6e373 +msgid "" +"Congratulations. You have installed Jupyter Notebook. See :ref:`Running " +"the Notebook ` for more details." +msgstr "" + +# 54686805017a467b9a216e0a7704ce74 +#~ msgid "" +#~ "Download `Anaconda `_." +#~ " We recommend downloading Anaconda's latest" +#~ " Python 3 version (currently Python " +#~ "3.5)." +#~ msgstr "" + +#~ msgid "Install Instructions" +#~ msgstr "" + +# 7ab1cb39403041899fd89e70ec072c36 +#~ msgid "Contents" +#~ msgstr "" + +#~ msgid "" +#~ "**Jupyter Notebook** - *Web-based " +#~ "application for authoring documents that " +#~ "combine live-code with narrative text," +#~ " equations and visualizations.*" +#~ msgstr "" + +#~ msgid "`GitHub Repo `_" +#~ msgstr "" + +#~ msgid "" +#~ "**JupyterLab** - *A next-generation " +#~ "web-based user interface for Project " +#~ "Jupyter.*" +#~ msgstr "" + +#~ msgid "`GitHub Repo `_" +#~ msgstr "" + +#~ msgid "`Docs `_" +#~ msgstr "" + +#~ msgid "" +#~ "`Install instructions " +#~ "`_" +#~ msgstr "" + +#~ msgid "**Jupyter Console** - Terminal based console for interactive computing." +#~ msgstr "" + +#~ msgid "`GitHub Repo `_" +#~ msgstr "" + +#~ msgid "" +#~ "**Jupyter QtConsole** - Qt application " +#~ "for interactive computing with rich " +#~ "output." +#~ msgstr "" + +#~ msgid "`GitHub Repo `_" +#~ msgstr "" + +#~ msgid "`Docs `_" +#~ msgstr "" + +#~ msgid "" +#~ "`Install instructions " +#~ "`_" +#~ msgstr "" + +# ffbb37b4a6064c4293bd70b5fddb96e4 +#~ msgid "Installing Jupyter Notebook" +#~ msgstr "" + +#~ msgid "*Optional:* Installing Kernels" +#~ msgstr "" + +#~ msgid ":ref:`Jupyter Projects `" +#~ msgstr "" + +#~ msgid "" +#~ "**JupyterLab** is A next-generation " +#~ "web-based user interface for Project " +#~ "Jupyter." +#~ msgstr "" + +#~ msgid "" +#~ "You can install **Jupyer Kernels** to" +#~ " add support for new languages and" +#~ " code behavior." +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/ipython.po b/docs/source/locale/en/LC_MESSAGES/ipython.po new file mode 100644 index 000000000..49d05a46c --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/ipython.po @@ -0,0 +1,99 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-05-09 11:43+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.8.0\n" + +#: ../../source/ipython/content-ipython.rst:37 +msgid "IPython website" +msgstr "" + +#: ../../source/ipython/content-ipython.rst:37 +msgid "Gallery of interesting notebooks" +msgstr "" + +#: ../../source/ipython/content-ipython.rst:37 +msgid "IPython documentation" +msgstr "" + +# e06aa197a71b41eeaf94dfe9f0caaca2 +#: ../../source/ipython/content-ipython.rst:2 1ac84e9d4c454baf88efce4f414f7e96 +msgid "IPython" +msgstr "" + +# 93415afba3654a1c904000d9a30c7b04 +#: ../../source/ipython/content-ipython.rst:5 2041c667be5e4894935642cc1f6b81fe +msgid "Contents" +msgstr "" + +# 0fb8abaae6d6439eb2d541d1cc83182b +#: ../../source/ipython/content-ipython.rst:13 94a4e85e5c6d4f6f8bb62d8a676100ac +msgid "Description" +msgstr "" + +# 0ffa752b43e04a8f84cf0772fdeeda3b +#: ../../source/ipython/content-ipython.rst:15 be02e0142e8246a0a96f406772a2fa2a +msgid "IPython provides a rich architecture for interactive computing with:" +msgstr "" + +# c81ecc03613b4623a05ae0b069bfc6a8 +#: ../../source/ipython/content-ipython.rst:17 3be2435c5ba14af0b7b0162e1e48d6d2 +msgid "A powerful interactive shell." +msgstr "" + +# cfe69331de214e0f9492f7cdde2deeff +#: ../../source/ipython/content-ipython.rst:18 b01d35444c45459297ddc3984863c103 +msgid "A kernel for Jupyter." +msgstr "" + +# 405d110fdb06459f97fd470b08f9b45a +#: ../../source/ipython/content-ipython.rst:19 7c02acfdf9fe4cac8935e7d5688bde7e +msgid "Support for interactive data visualization and use of GUI toolkits." +msgstr "" + +# 198111746308470bb460f4eff0187c9c +#: ../../source/ipython/content-ipython.rst:20 5798cfd5681e468088ff5dd5437a9f02 +msgid "Flexible, embeddable interpreters to load into your own projects." +msgstr "" + +# cc784dedd7924d66b116dc0cee97b0ca +#: ../../source/ipython/content-ipython.rst:21 15bc23286e874bacb57ac82553d8cd69 +msgid "Easy to use, high performance tools for parallel computing." +msgstr "" + +# 2807f7be8ea5430caabaadf467ac3d28 +#: ../../source/ipython/content-ipython.rst:24 decb7d66ae4840299e866264b835b96d +msgid "Background" +msgstr "" + +# 3735a8ce15d6486f90b2e6150041cf39 +#: ../../source/ipython/content-ipython.rst:26 e7df2ca9c7c146209554cd594629c336 +msgid "" +"IPython is a growing project, with increasingly language-agnostic " +"components. IPython 3.x was the last monolithic release of IPython, " +"containing the notebook server, qtconsole, etc. As of IPython 4.0, the " +"language-agnostic parts of the project: the notebook format, message " +"protocol, qtconsole, notebook web application, etc. have moved to new " +"projects under the name Jupyter. IPython itself is focused on interactive" +" Python, part of which is providing a Python kernel for Jupyter." +msgstr "" + +# a902c3e9aab34a9bb26248bf4ebffc1b +#: ../../source/ipython/content-ipython.rst:35 2d33e690bbef42bb8b33ef00551546a4 +msgid "Resources" +msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/migrating.po b/docs/source/locale/en/LC_MESSAGES/migrating.po new file mode 100644 index 000000000..37eba3496 --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/migrating.po @@ -0,0 +1,562 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2019-07-04 19:51-0400\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.6.0\n" + +# 8f5cd3c486474d4b8a13ff41c24e3e75 +#: ../../source/migrating.rst:5 +msgid "Migrating from IPython Notebook" +msgstr "" + +# a0bf9b469b3d41b486c705edbe1a32d3 +#: ../../source/migrating.rst:8 +msgid "Contents" +msgstr "" + +# 661d74638f8e402c8844e1dae8178361 +#: ../../source/migrating.rst:11 +msgid "Abstract" +msgstr "" + +# 7b16ca89f25647868cf204d88a1e4d29 +#: ../../source/migrating.rst:13 +msgid "" +"`The Big Split `__ " +"moved IPython's various language-agnostic components under the Jupyter " +"umbrella. Going forward, Jupyter will contain the language-agnostic " +"projects that serve many languages. IPython will continue to focus on " +"Python and its use with Jupyter." +msgstr "" + +# 06bf34e702fa456e9ce4f7b616eb546e +#: ../../source/migrating.rst:19 +msgid "" +"This document describes what has changed, and how you may need to modify " +"your code or configuration when migrating from IPython version 3 to " +"Jupyter." +msgstr "" + +# 3b23232adf694c6cb4998078211d9109 +#: ../../source/migrating.rst:24 +msgid "Understanding the Migration Process" +msgstr "" + +# aa9fcadf57d549aa8a6d3f4126d60ca4 +#: ../../source/migrating.rst:27 +msgid "Automatic migration of files" +msgstr "" + +# f5ec35e6c2494acbac3e543734ba12f2 +#: ../../source/migrating.rst:29 +msgid "" +"The first time you run any ``jupyter`` command, it will perform an " +"automatic migration of files. The automatic migration process **copies** " +"files, instead of moving files, leaving the originals in place and the " +"copies in the Jupyter file locations. You can re-run the migration, if " +"needed, by calling ``jupyter migrate``. Your custom configuration will be" +" migrated automatically and should work with Jupyter without further " +"editing. When you update or modify your configuration in the future, " +"please keep in mind that the file locations may have changed." +msgstr "" + +# 2284d903d20c49b7acf289fede63d7e7 +#: ../../source/migrating.rst:39 +msgid "Where have my configuration files gone?" +msgstr "" + +# 14350789ee634cb3a07a1f7564d87294 +#: ../../source/migrating.rst:41 +msgid "Also known as: \"Why isn't my configuration having any effect anymore?\"" +msgstr "" + +# 07d5f3408f704edfb54df3fd57924e6e +#: ../../source/migrating.rst:43 +msgid "" +"Jupyter splitting out from IPython means that the locations of some files" +" have moved, and Jupyter projects have not inherited everything from how " +"IPython did it." +msgstr "" + +# cec706b3328f4024bf9b8cac2bd78686 +#: ../../source/migrating.rst:47 +msgid "" +"When you start your first Jupyter application, the relevant configuration" +" files are automatically copied to their new Jupyter locations. The " +"original configuration files in the IPython locations have no effect on " +"Jupyter's execution. If you accidentally edit your original IPython " +"config file, you may not see the desired effect with Jupyter now. You " +"should check that you are editing Jupyter's configuration file, and you " +"should see the expected effect after restarting the Jupyter server." +msgstr "" + +# 35761bdec57845c5956afcbd2518fcb2 +#: ../../source/migrating.rst:56 +msgid "Finding the Location of Important Files" +msgstr "" + +# 0e91703834714ff8a450c3e1f4e19183 +#: ../../source/migrating.rst:58 +msgid "" +"This section provides quick reference for common locations of IPython 3 " +"files and the migrated Jupyter files." +msgstr "" + +# b3066e3c9a824483918e9feabfddd439 +#: ../../source/migrating.rst:62 +msgid "Configuration files" +msgstr "" + +# d1be8dd7d028443bab89581071668b40 +#: ../../source/migrating.rst:64 +msgid "" +"Configuration files customize Jupyter to the user's preferences. The " +"migrated files should all be **automatically copied** to their new " +"Jupyter locations. Here are the location changes:" +msgstr "" + +# e5dc4b2fb1b2448a9fa739dddd5fdfdc +#: ../../source/migrating.rst:69 +msgid "IPython location" +msgstr "" + +# 716d92fb1fa94db28397bdfddd9c29f0 +#: ../../source/migrating.rst:69 +msgid "Jupyter location" +msgstr "" + +# 9678737a7e6342c7bb833a2c8242b625 +#: ../../source/migrating.rst:71 +msgid ":file:`~/.ipython/profile_default/static/custom`" +msgstr "" + +# 1008e78186164ff2adcc4c0a92dae223 +# 72fe30c2d0404ee59bde125a2de1e38f +# d91efb208eae4ad7b4965599aa9fb65e +# a7a49c506f0e42f19e6f5d03cdbc5096 +# af9332d2f5a34982a36a9bb2cdcd0473 +# e8415a6ea7a14ab9bdc8dd7fbab6d67d +# 9e046db52de3436fa30a19e5d1d9b045 +# e853fee326ff469da5a56f61d7a961a8 +# 56b6aa8cb49b41c19612910e3afb2563 +# c1d9598dce504f2380373045dfdc7625 +# 128040d623434edb9bbeda55c9507f00 +# 1fe82a47a7eb4b06a73d941d6d5ee283 +#: ../../source/migrating.rst:71 ../../source/migrating.rst:72 +#: ../../source/migrating.rst:73 ../../source/migrating.rst:74 +#: ../../source/migrating.rst:75 ../../source/migrating.rst:241 +#: ../../source/migrating.rst:242 ../../source/migrating.rst:243 +#: ../../source/migrating.rst:244 ../../source/migrating.rst:245 +#: ../../source/migrating.rst:246 ../../source/migrating.rst:247 +msgid "→" +msgstr "" + +# 3305847c2b3c4dd597ec3b649ca0feb4 +#: ../../source/migrating.rst:71 +msgid ":file:`~/.jupyter/custom`" +msgstr "" + +# 8a5dbaf9bbb24302b7f8c44d5c70d748 +#: ../../source/migrating.rst:72 +msgid ":file:`~/.ipython/profile_default/ipython_notebook_config.py`" +msgstr "" + +# 44d5bf8302184c91ab5ea2642ff4b0af +#: ../../source/migrating.rst:72 +msgid ":file:`~/.jupyter/jupyter_notebook_config.py`" +msgstr "" + +# f17f8f9f52884c2bbc2fce452120161a +#: ../../source/migrating.rst:73 +msgid ":file:`~/.ipython/profile_default/ipython_nbconvert_config.py`" +msgstr "" + +# 6e8948fba80a4d329cf88b88e14f34a3 +#: ../../source/migrating.rst:73 +msgid ":file:`~/.jupyter/jupyter_nbconvert_config.py`" +msgstr "" + +# 3e89a17fc5b24bdb8db5e054e654b496 +#: ../../source/migrating.rst:74 +msgid ":file:`~/.ipython/profile_default/ipython_qtconsole_config.py`" +msgstr "" + +# 272ac1f228084a03ac2d2114a6412072 +#: ../../source/migrating.rst:74 +msgid ":file:`~/.jupyter/jupyter_qtconsole_config.py`" +msgstr "" + +# 2e3a6302c7924ba29ba73e7c4a68be2f +#: ../../source/migrating.rst:75 +msgid ":file:`~/.ipython/profile_default/ipython_console_config.py`" +msgstr "" + +# 2ecee964e7b24a10bef99b7524da7344 +#: ../../source/migrating.rst:75 +msgid ":file:`~/.jupyter/jupyter_console_config.py`" +msgstr "" + +# 4d628b8f2fd64ed883e979d8ba54112c +#: ../../source/migrating.rst:78 +msgid "" +"To choose a directory location other than the default :file:`~/.jupyter`," +" set the ``JUPYTER_CONFIG_DIR`` environment variable. You may need to run" +" ``jupyter migrate`` after setting the environment variable for files to " +"be copied to the desired directory." +msgstr "" + +# 6441364aeb0d4174b78105a74f688c16 +#: ../../source/migrating.rst:84 +msgid "Data files: kernelspecs and notebook extensions" +msgstr "" + +# e2924a8235fd431b9f9fd56ae0f39d23 +#: ../../source/migrating.rst:86 +msgid "" +"Data files include files, other than configuration files, which are user " +"installed. Examples include kernelspecs and notebook extensions. Like the" +" configuration files, data files are also **automatically migrated** to " +"their new Jupyter locations." +msgstr "" + +# ec6e2b0e388b4bafbefdc42d92b69ab1 +#: ../../source/migrating.rst:91 +msgid "In **IPython 3**, data files lived in ``~/.ipython``." +msgstr "" + +# db9667c61df04f03b389007dde80592b +#: ../../source/migrating.rst:93 +msgid "In **Jupyter**, data files use platform-appropriate locations:" +msgstr "" + +# 6ec16f9359924bcaad831b990915ac81 +#: ../../source/migrating.rst:95 +msgid "OS X: ``~/Library/Jupyter``" +msgstr "" + +# 06b69be6aab34415a18b114a688ef046 +#: ../../source/migrating.rst:96 +msgid "Windows: the location specified in ``%APPDATA%`` environment variable" +msgstr "" + +# b8aa64d12c084a09a9caf7f0997b9694 +#: ../../source/migrating.rst:97 +msgid "" +"Elsewhere, ``$XDG_DATA_HOME`` is respected, with the default of " +"``~/.local/share/jupyter``" +msgstr "" + +# bcf6cf06fa7849d5adb27a36bb68475a +#: ../../source/migrating.rst:100 +msgid "" +"In all cases, the ``JUPYTER_DATA_DIR`` environment variable can be used " +"to set a location explicitly." +msgstr "" + +# 5ff8200b58f0422aab90ae5013d1bc60 +#: ../../source/migrating.rst:103 +msgid "" +"Data files installed system-wide (e.g. in ``/usr/local/share/jupyter``) " +"have not changed. Per-user installation of data files has changed " +"location from ``.ipython`` to the platform-appropriate Jupyter location." +msgstr "" + +# 8fc50bfd17e74c08aaee715d4df0aa28 +#: ../../source/migrating.rst:108 +msgid "Since Jupyter does not have profiles, how do I customize it?" +msgstr "" + +# f21e1f21ab634dfeae67d57a810af7e8 +#: ../../source/migrating.rst:110 +msgid "" +"While IPython has the concept of :term:`profiles`, **Jupyter does not " +"have profiles**." +msgstr "" + +# fbab5d83e70641b58ba8d8c25a1b5505 +#: ../../source/migrating.rst:113 +msgid "" +"In IPython, profiles are collections of configuration and runtime files. " +"Inside the IPython directory (``~/.ipython``), there are directories with" +" names like ``profile_default`` or ``profile_demo``. In each of these are" +" configuration files (``ipython_config.py``, " +"``ipython_notebook_config.py``) and runtime files (``history.sqlite``, " +"``security/kernel-*.json``). Profiles could be used to switch between " +"configurations of IPython." +msgstr "" + +# df3baa2e23de4665a1ba0a95d9bd1d53 +#: ../../source/migrating.rst:120 +msgid "" +"Previously, people could use commands like ``ipython notebook --profile " +"demo`` to set the profile for *both* the notebook server and the IPython " +"kernel. This is no longer possible in one go with Jupyter, just like it " +"wasn't possible in IPython 3 for any other kernels." +msgstr "" + +# 900e8e17d08548eabeaa79549d4aa98b +#: ../../source/migrating.rst:126 +msgid "Changing the Jupyter notebook configuration directory" +msgstr "" + +# 6e7aba03567842fdb5bcd279d8cf35dd +#: ../../source/migrating.rst:128 +msgid "" +"If you want to change the notebook configuration, you can set the " +"``JUPYTER_CONFIG_DIR``:" +msgstr "" + +# b29b24c9af764ad4a280ddc011a49965 +#: ../../source/migrating.rst:137 +msgid "Changing the Jupyter notebook configuration file" +msgstr "" + +# a7614ee085ba47d488cafe7699656792 +#: ../../source/migrating.rst:139 +msgid "If you just want to change the config file, you can do:" +msgstr "" + +# a6aac6dd2d4943659e18520f5d392cf9 +#: ../../source/migrating.rst:146 +msgid "Changing IPython's profile using custom kernelspecs" +msgstr "" + +# 9563bde765c14e3690a51f73d7c92cf7 +#: ../../source/migrating.rst:148 +msgid "" +"If you do want to change the IPython kernel's profile, you can't do this " +"at the server command-line anymore. Kernel arguments must be changed by " +"modifying the kernelspec. You can do this without relaunching the server." +" Kernelspec changes take effect every time you start a new kernel. " +"However, there isn't a great way to modify the kernelspecs. One approach " +"uses ``jupyter kernelspec list`` to find the ``kernel.json`` file and " +"then modifies it, e.g. ``kernels/python3/kernel.json``, by hand. " +"Alternatively, `a2km `__ is an " +"experimental project that tries to make these things easier." +msgstr "" + +# 45d3b19664bd49fea20a62ec0e77c3ad +#: ../../source/migrating.rst:158 +msgid "" +"For example, add the ``--profile`` option to a custom kernelspec under " +"``kernels/mycustom/kernel.json`` (see the Jupyter kernelspec directions " +"`here `__):" +msgstr "" + +# 2a98d819b7e04e5bbfc60ef439b635e2 +#: ../../source/migrating.rst:172 +msgid "" +"You can then run Jupyter with the ``--kernel=mycustom`` command-line " +"option and IPython will find the appropriate profile." +msgstr "" + +# df14211cf90e4c57a5fa18626c872c72 +#: ../../source/migrating.rst:176 +msgid "Understanding Installation Changes" +msgstr "" + +# b8d826a3ba3345abbedf16171c095d5c +#: ../../source/migrating.rst:178 +msgid "" +"See the :ref:`install` page for more information about installing " +"Jupyter. Jupyter automatically migrates some things, like Notebook " +"extensions and kernels." +msgstr "" + +# fa33a2f4f8f94829a7c473d7071b0f43 +#: ../../source/migrating.rst:183 +msgid "Notebook extensions" +msgstr "" + +# 51d5f0d804f442a9a97c7655e580e79b +#: ../../source/migrating.rst:185 +msgid "" +"Any IPython notebook extensions should be **automatically migrated** as " +"part of the data files migration." +msgstr "" + +# 5fd92d1027fb4b85ae426a42c82fe947 +#: ../../source/migrating.rst:188 +msgid "Notebook extensions were installed with:" +msgstr "" + +# 91ab0eeefe084c70a44650fbd51644b7 +#: ../../source/migrating.rst:194 +msgid "Now, extensions are installed with:" +msgstr "" + +# 5b197ef97efc43b5bbd741f814a6ee64 +#: ../../source/migrating.rst:200 +msgid "" +"The notebook extensions will be installed in a system-wide location (e.g." +" ``/usr/local/share/jupyter/nbextensions``). If doing a ``--user`` " +"install, the notebook extensions will go in the ``JUPYTER_DATA_DIR`` " +"location. Installation **SHOULD NOT** be done manually by guessing where " +"the files should go." +msgstr "" + +# 8f205aaaf5ee46de8e9d0522c240dc83 +#: ../../source/migrating.rst:207 +msgid "Kernels" +msgstr "" + +# 6835584aca814c54909e4f5519afbf77 +#: ../../source/migrating.rst:209 +msgid "" +"Kernels are installed in much the same way as notebook extensions. They " +"will also be **automatically migrated**." +msgstr "" + +# 221543b8255b44c6a970364430b396b9 +#: ../../source/migrating.rst:212 +msgid "Kernel specs used to be installed with:" +msgstr "" + +# 7c691c23e0594313a3eade3815aa8c3f +#: ../../source/migrating.rst:218 +msgid "They are now installed with:" +msgstr "" + +# 7300ff40baec4daa85964d98a508f28c +#: ../../source/migrating.rst:224 +msgid "" +"By default, kernel specs will go in a system-wide location (e.g. " +"``/usr/local/share/jupyter/kernels``). If doing a ``--user`` install, the" +" kernel specs will go in the ``JUPYTER_DATA_DIR`` location. Installation " +"**SHOULD NOT** be done manually by guessing where the files should go." +msgstr "" + +# 7347a7230ab645599d5be543b3b019d0 +#: ../../source/migrating.rst:230 +msgid "Understanding Changes in imports" +msgstr "" + +# e84b04296df74f698d561ee40d3355cc +#: ../../source/migrating.rst:232 +msgid "" +"IPython 4.0 includes shims to manage dependencies; so, all imports that " +"work on IPython 3 should continue to work on IPython 4. If you find any " +"differences, please `let us know " +"`__." +msgstr "" + +# 56813b80163249d3b2a3e603b904015d +#: ../../source/migrating.rst:236 +msgid "Some changes include:" +msgstr "" + +# 4f027d18d7bd44c7a354068d322e7b32 +#: ../../source/migrating.rst:239 +msgid "IPython 3" +msgstr "" + +# 126977d37c5a49c09790822aabadb9fe +#: ../../source/migrating.rst:239 +msgid "Jupyter and IPython 4.0" +msgstr "" + +# 4243295b32bd48229e2f24ac3feb22c2 +#: ../../source/migrating.rst:241 +msgid "``IPython.html``" +msgstr "" + +# 07dcd5f404274ab0b1593a89a10eda12 +#: ../../source/migrating.rst:241 +msgid "``notebook``" +msgstr "" + +# eb1f964c367445f19d1aebc8b52fa46a +#: ../../source/migrating.rst:242 +msgid "``IPython.html.widgets``" +msgstr "" + +# 75653597f60c4e2facecc6342d4ee141 +#: ../../source/migrating.rst:242 +msgid "``ipywidgets``" +msgstr "" + +# 2e80aada7b9b4fbfbd8bc21f683b5a33 +#: ../../source/migrating.rst:243 +msgid "``IPython.kernel``" +msgstr "" + +# ee6c0d3100a0430887bc2ec59c836066 +#: ../../source/migrating.rst:243 +msgid "``jupyter_client``, ``ipykernel``" +msgstr "" + +# 6ef0dd165dd9439b869e08965c69222a +#: ../../source/migrating.rst:244 +msgid "``IPython.parallel``" +msgstr "" + +# 282f79d57dc84378a575ad9037ceda9f +#: ../../source/migrating.rst:244 +msgid "``ipyparallel``" +msgstr "" + +# 0d2d805e0ebc4d1ca6e714416e5ba544 +#: ../../source/migrating.rst:245 +msgid "``IPython.qt.console``" +msgstr "" + +# 3d9ae3c27ca949228f137c7099ff4dac +#: ../../source/migrating.rst:245 +msgid "``qtconsole``" +msgstr "" + +# d7fbddb811bc4e4ba54deb111b3f0a87 +#: ../../source/migrating.rst:246 +msgid "``IPython.utils.traitlets``" +msgstr "" + +# e051da2ba487485eb14be36b1cbc0c02 +#: ../../source/migrating.rst:246 +msgid "``traitlets``" +msgstr "" + +# 417499484a6241a5ba01fa609cf782f2 +#: ../../source/migrating.rst:247 +msgid "``IPython.config``" +msgstr "" + +# 5686f8ec952f403bb20dad55c84bd2e7 +#: ../../source/migrating.rst:247 +msgid "``traitlets.config``" +msgstr "" + +# 1069489e11e54f5683906ef69dd939f4 +#: ../../source/migrating.rst:252 +msgid "The ``IPython.kernel`` Split" +msgstr "" + +# b3e32d27b5ec43d8b46b37ab774c3713 +#: ../../source/migrating.rst:254 +msgid "``IPython.kernel`` became two packages:" +msgstr "" + +# 37e65f7a48a049849c032d103355c88c +#: ../../source/migrating.rst:256 +msgid "``jupyter_client`` for the Jupyter client-side APIs." +msgstr "" + +# daef865437274272bfbf0f835bab4a68 +#: ../../source/migrating.rst:257 +msgid "``ipykernel`` for Jupyter's IPython kernel" +msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/projects.po b/docs/source/locale/en/LC_MESSAGES/projects.po new file mode 100644 index 000000000..2f6dadc59 --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/projects.po @@ -0,0 +1,2393 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2020-07-22 22:44+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.8.0\n" + +# edd42737bc98463498d711d9d916c157 +# 73d33f0f3c864e74b012a215450194c5 +#: ../../source/projects/architecture/content-architecture.rst:3 +#: ../../source/projects/doc-proj-categories.rst:69 +#: 9a7d845fc8e647a691d9bb30923056b6 c667f538637149b490b7f1d123719c92 +msgid "Architecture" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:5 +#: 1c9055831b344bc8a2f15d0e695a1e17 +msgid "" +"This page has information about the different architectural designs of " +"core pieces in the Jupyter ecosystem. Some of these are individual " +"projects, and others show the relationships between projects." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:11 +#: f089dc2d645946b98925cd05e0b12595 +msgid "IPython Kernel" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:13 +#: c5e1fc0126044786a6283e7498516741 +msgid "" +"This section focuses on IPython and kernels. When we discuss ``IPython``," +" we talk about two fundamental roles:" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:16 +#: 4fac3561603a44d790a6bf332ad55466 +msgid "Terminal IPython as the familiar REPL" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:17 +#: 6dc58fbf45eb4e6b950c29a9059d92d2 +msgid "" +"The IPython kernel that provides computation and communication with the " +"frontend interfaces, like the notebook" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:22 +#: bee0628ce519418abcb251949e2631ff +msgid "Terminal IPython" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:24 +#: 96822faa01e8430dbf46db798441406c +msgid "" +"When you type ``ipython``, you get the original IPython interface, " +"running in the terminal. It does something like this::" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:31 +#: a05407bbf0a74ca2a6521dbe00a9a2f2 +msgid "" +"Of course, it's much more complex, because it has to deal with multi-line" +" code, tab completion using :mod:`readline`, magic commands, and so on. " +"But the model is like code example: prompt the user for some code, and " +"when they've entered it, execute it in the same process. This model is " +"often called a :term:`REPL`, or Read-Eval-Print-Loop." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:38 +#: 878a0a66448b491c8d3995c81d2d3b42 +msgid "The IPython Kernel" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:40 +#: e40b04637c0946eba6435af5bdcb243e +msgid "" +"All the other interfaces —- the Notebook, the Qt console, ``ipython " +"console`` in the terminal, and third party interfaces —- use the IPython " +"Kernel. The IPython Kernel is a separate process which is responsible for" +" running user code, and things like computing possible completions. " +"Frontends, like the notebook or the Qt console, communicate with the " +"IPython Kernel using JSON messages sent over `ZeroMQ " +"`_ sockets; the protocol used between the frontends " +"and the IPython Kernel is described in :ref:`jupyterclient:messaging`." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:49 +#: 8518a5a5099a48d6896f9cf56232d205 +msgid "" +"The core execution machinery for the kernel is shared with terminal " +"IPython:" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:53 +#: d5c05eada42c44b19b2503ab071ba400 +msgid "" +"A kernel process can be connected to more than one frontend " +"simultaneously. In this case, the different frontends will have access to" +" the same variables." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:58 +#: 5b75a6a4635d4ae189f12391d654d381 +msgid "" +"This design was intended to allow easy development of different frontends" +" based on the same kernel, but it also made it possible to support new " +"languages in the same frontends, by developing kernels in those " +"languages, and we are refining IPython to make that more practical." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:63 +#: 3ba5f2a951db43509a64ab255cb02a75 +msgid "" +"Today, there are two ways to develop a kernel for another language. " +"Wrapper kernels reuse the communications machinery from IPython, and " +"implement only the core execution part. Native kernels implement " +"execution and communications in the target language:" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:70 +#: 89db678016424d37994ec140a2f12869 +msgid "" +"Wrapper kernels are easier to write quickly for languages that have good " +"Python wrappers, like `octave_kernel " +"`_, or languages where it's " +"impractical to implement the communications machinery, like `bash_kernel " +"`_. Native kernels are likely " +"to be better maintained by the community using them, like `IJulia " +"`_ or `IHaskell " +"`_." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:80 +#: 1381c01e18224b6aa0cf6ab68877bfb7 +msgid ":ref:`jupyterclient:kernels`" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:82 +#: 5db64fe481ca49518621864e432018de +msgid ":ref:`Kernels `" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:86 +#: cdc72bbeed194fbb9e64963b54062c35 +msgid "The Jupyter Notebook format" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:88 +#: 365e952640e9413d9e0806c2d68f5fdd +msgid "" +"Jupyter Notebooks are structured data that represent your code, metadata," +" content, and outputs. When saved to disk, the notebook uses the " +"extension ``.ipynb``, and uses a JSON structure. For more information " +"about the notebook format structure and specification, see `the nbformat " +"documentation " +"`_." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:95 +#: 8e8b50a9e8944799a3073bbefb86935e +msgid "The Jupyter Notebook Interface" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:97 +#: 8a892e4821814c33b03b53878a377e44 +msgid "" +"Jupyter Notebook and its flexible interface extends the notebook beyond " +"code to visualization, multimedia, collaboration, and more. In addition " +"to running your code, it stores code and output, together with markdown " +"notes, in an editable document called a notebook. When you save it, this " +"is sent from your browser to the notebook server, which saves it on disk " +"as a JSON file with a ``.ipynb`` extension." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:106 +#: e6e19c8605a64bd48dde9b8841e5a75d +msgid "" +"The notebook server, not the kernel, is responsible for saving and " +"loading notebooks, so you can edit notebooks even if you don't have the " +"kernel for that language—you just won't be able to run code. The kernel " +"doesn't know anything about the notebook document: it just gets sent " +"cells of code to execute when the user runs them." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:114 +#: c77552c0869a4f058759130528aa1c6a +msgid "Exporting Jupyter Notebooks to other formats" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:116 +#: 1ca0a78d7fab4c6fa3668480ad316ffa +msgid "" +"The :doc:`Nbconvert tool ` in Jupyter converts notebook " +"files to other formats, such as HTML, LaTeX, or reStructuredText. This " +"conversion goes through a series of steps:" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:122 +#: e2d632f021584a9a84e98d495a85e747 +msgid "" +"Preprocessors modify the notebook in memory. E.g. ExecutePreprocessor " +"runs the code in the notebook and updates the output." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:124 +#: 8a277e4a45b540be805a1b6721a4fd01 +msgid "" +"An exporter converts the notebook to another file format. Most of the " +"exporters use templates for this." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:126 +#: f2abfa2cd5b94d1a8a128745ed6b2195 +msgid "Postprocessors work on the file produced by exporting." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:128 +#: 2bd5b9dfd824468cb60d28c9415b5323 +msgid "" +"The `nbviewer `_ website uses nbconvert " +"with the HTML exporter. When you give it a URL, it fetches the notebook " +"from that URL, converts it to HTML, and serves that HTML to you." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:133 +#: f3b75185f48f4f02bc0a72c2a122e831 +msgid "IPython.parallel" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:135 +#: 9a61d9ad75e64950bbcec6d8bbeab376 +msgid "" +"IPython also includes a parallel computing framework, `IPython.parallel " +"`_. This allows you to " +"control many individual engines, which are an extended version of the " +"IPython kernel described above." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:142 +#: 358338d6ae4e429a8b3f360308c0a112 +msgid "JupyterHub and Binder" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:144 +#: bec370c9293f4e2ebf3cd5aaac086c48 +msgid "" +"JupyterHub is a multi-user Hub that spawns, manages, and proxies multiple" +" instances of the single-user Jupyter notebook server. This can be used " +"to serve a variety of interfaces and environments, and can be run on many" +" kinds of infrastructure. JupyterHub on Kubernetes is a Helm Chart for " +"running JupyterHub on kubernetes infrastructure, and BinderHub is a " +"customized JupyterHub deployment for sharable, reproducible interactive " +"computing environments." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:150 +#: 559c7c6486474c8ea8b4a1e1f9d031fc +msgid "" +"The links below describe the architecture of JupyterHub and several " +"distributions of JupyterHub." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:153 +#: e786cbd884944f5d82c0221b407655d0 +msgid ":doc:`JupyterHub core architecture `" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:154 +#: 1130fb65aa6e4952934ec9ae3377b73b +msgid "" +":doc:`JupyterHub for Kubernetes architecture " +"`" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:155 +#: 0f87c4a7bf214b38a90ec195c53d5d9c +msgid ":ref:`BinderHub architecture `" +msgstr "" + +# 469c33adacf44e77be8479c50a3afde7 +#: ../../source/projects/architecture/content-architecture.rst:159 +#: ../../source/projects/doc-proj-categories.rst:60 +#: 2e8ee7d4b754445185232fe6a4acd8f3 761669761e554140ba95f10b72d1bd8f +msgid "JupyterLab" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:161 +#: d7f2c681b9ee41ab957f8ea3e87d5967 +msgid "" +"JupyterLab is a flexible, extensible interface for interactive computing." +" Below are a few links that are useful for understanding the JupyterLab " +"architecture." +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:164 +#: a9daccc7d434404a9449a178fffca62b +msgid ":doc:`JupyterLab document model `" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:165 +#: 461e26a2e6c6413b98803cde2276255b +msgid ":doc:`JupyterLab notebook model `" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:166 +#: 19f49dc1aefa4fa8a90c1a04d9524cda +msgid ":doc:`Design patterns in JupyterLab `" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:169 +#: 6f66a0c7246a44828465f8308b6cbfae +msgid "Projects overview" +msgstr "" + +#: ../../source/projects/architecture/content-architecture.rst:171 +#: 41d0ba6af5ce4aa7a75e82168d534d44 +msgid "" +"Below is a high level visual overview of project relationships. It is " +"current as of 2017." +msgstr "" + +# 9910335ae4fe47adbef725bbdb9f7faa +#: ../../source/projects/content-projects.rst:5 +#: befdb7bf5b8744a39201b0db4f168b69 +msgid "Jupyter Projects" +msgstr "" + +#: ../../source/projects/content-projects.rst:7 +#: 806055b788244b9f8950de14d3f9bfbd +msgid "" +"The Jupyter community is composed of several sub-communities and " +"projects. These are organized around particular use-cases, users, or " +"other aspects of the Jupyter community. This section contains information" +" to help navigate these projects both from the perspective of a user and " +"a community member." +msgstr "" + +#: ../../source/projects/content-projects.rst:32 +#: eeac2644a1224fb8b8840a3422ff95ce +msgid "Jupyter Projects and Communities" +msgstr "" + +#: ../../source/projects/content-projects.rst:34 +#: 7fbc8e3bb6df47ff87d949da04f63095 +msgid "" +"Information relevant to understanding the many projects in the Jupyter " +"ecosystem, including their technical components and how they work and " +"relate to one another." +msgstr "" + +#: ../../source/projects/content-projects.rst:52 +#: 2a713028dbff456ea04f79d3bbff9e1d +msgid "More information" +msgstr "" + +# bada42846faa4c76bcb0870aa7b4ff67 +#: ../../source/projects/conversion.rst:3 8b43b1f295dc4adca721e108f4f2a9c3 +msgid "Formatting and Conversion" +msgstr "" + +# 8a0210fab25448ce9a8ce955a5e98b81 +#: ../../source/projects/conversion.rst:5 349558b9556e4272b5eabfcf50dfacdd +msgid "" +"Notebooks are rich interactive documents that combine live code, " +"narrative text (using markdown), visualizations, and other rich media. " +"The following utility subprojects allow programmatic format conversion " +"and manipulation of notebook documents." +msgstr "" + +# 63aa809df72b43d187a73bb2e4e6a583 +#: ../../source/projects/conversion.rst:11 0cc8d2a732574112b6fb788bfc3d4e86 +msgid "`nbconvert `__" +msgstr "" + +# 4c57295fbf23443daf9fdd2905ef7fcf +#: ../../source/projects/conversion.rst:13 bdd01a4c18324b379141311f83bfb022 +msgid "" +"Convert dynamic notebooks to static formats such as HTML, Markdown, " +"LaTeX/PDF, and reStrucuredText. `Documentation " +"`__ | `Repo " +"`__" +msgstr "" + +# ce77e006f955438aa5a921968dc8b922 +#: ../../source/projects/conversion.rst:17 89afea93f0e84450a07166b6f13de100 +msgid "`nbformat `__" +msgstr "" + +# 6dff295e412a47da84bb23b4786708b9 +#: ../../source/projects/conversion.rst:19 1b9dad5e227f4847901841de14d87465 +msgid "" +"Work with notebook documents programmatically. `Documentation " +"`__ | `Repo " +"`__" +msgstr "" + +#: ../../source/projects/core.rst:3 69fc5b769a5a484aa2fbc969bdf22f0e +msgid "Core Building Blocks" +msgstr "" + +# 2c6f57f2e66247acbba9d318b5c2ce75 +#: ../../source/projects/core.rst:5 f6b3f55fd0c4427f8116c24f53e21f9e +msgid "" +"The Jupyter architecture relies on these projects' specifications and " +"implementation." +msgstr "" + +# 682935d71e0f4ab7be95b5b3aea567d5 +#: ../../source/projects/core.rst:9 af0107911fcf4b8f9bf1dc762e883a0f +msgid "`jupyter_client `__" +msgstr "" + +# 0e90e5cc30614edab2b9cb1f02d94a33 +#: ../../source/projects/core.rst:11 9c88835f2bdd41278c2b992ad7b1fb4a +msgid "" +"The specification of the Jupyter message protocol and a client library in" +" Python. `Documentation `__ | `Repo " +"`__" +msgstr "" + +# ed800037c68c47df8948d52e1b135a2b +#: ../../source/projects/core.rst:15 babf5756e36a45f593f6751a1b6a55fa +msgid "`jupyter_core `__" +msgstr "" + +# d925cc4bc47747ea85133aad35a742dc +#: ../../source/projects/core.rst:17 c890c6805a7642f5ba8dee48cd2bc90a +msgid "" +"Core functionality and miscellaneous utilities. `Documentation `__ | `Repo " +"`__" +msgstr "" + +#: ../../source/projects/deployment.rst:3 82f33c69c1c14ef98ff8a1fe8ad0d475 +msgid "Deployment and infrastructure" +msgstr "" + +# 9bddab1e2cba4c829b435171cbe67474 +#: ../../source/projects/deployment.rst:5 719f0e331e044993b79a9a0e5aa0367a +msgid "" +"To serve a variety of users and use cases, these subprojects are being " +"developed to support notebook deployment in various contexts, including " +"multiuser capabilities and secure, scalable cloud deployments." +msgstr "" + +# eefb0ea614334021a3d54a1978ace7c4 +#: ../../source/projects/deployment.rst:10 17d2d5c2ea7548eead2ccb674aec9935 +msgid "`jupyterhub `__" +msgstr "" + +# 17d831ed81344a498d1e6449876780e6 +#: ../../source/projects/deployment.rst:12 c83159651d1646b1b72bdfa2f9adca35 +msgid "" +"Multi-user notebook for organizations with pluggable authentication and " +"scalability. `Documentation " +"`__ | `Repo " +"`__" +msgstr "" + +# bf80256b0a2d49beb74926620c0e63d0 +#: ../../source/projects/deployment.rst:16 56668c98661d49db936e384cd2da8439 +msgid "`jupyter-drive `__" +msgstr "" + +# d6e3c6aaebe44f4cb095e4097d8ffbfe +#: ../../source/projects/deployment.rst:18 b0d2bb768df74b24abf5e88b11c54261 +msgid "" +"Store notebooks on Google Drive. `Documentation " +"`__ | `Repo " +"`__" +msgstr "" + +# 7abe71ed8d0c4b78abda9410c630fce5 +#: ../../source/projects/deployment.rst:21 e675ad3d3f574e3dab7fbc7179cfb250 +msgid "`nbviewer `__" +msgstr "" + +# 9f9dbdacd8284a36a9e4fabb09e6f75b +#: ../../source/projects/deployment.rst:23 f6263531f7924181b17438e94dc2cd2f +msgid "" +"Share notebooks as static HTML on the web. `Documentation " +"`__ | `Repo " +"`__" +msgstr "" + +# 21c5717ce0bb494abeb4f7efe21689cf +#: ../../source/projects/deployment.rst:26 41465dbe5cfa4e1c8f7c5458f0a1d902 +msgid "`tmpnb `__" +msgstr "" + +# b33b868fce914e299fd08a5835536be1 +#: ../../source/projects/deployment.rst:28 0f94f460ba54441a8307b518c9f686f5 +msgid "" +"Create temporary, transient notebooks in the cloud. `Documentation " +"`__ | `Repo " +"`__" +msgstr "" + +# 21a190811e944b0da16ade016dc3b614 +#: ../../source/projects/deployment.rst:31 a25224774319437e830bfa8dd70a6edf +msgid "`tmpnb-deploy `__" +msgstr "" + +# 5daf6e80c11b44c595c655040dc09d64 +#: ../../source/projects/deployment.rst:33 9449846be8f34d5aa11f52c7b170f33a +msgid "" +"Deployment tools for tmpnb. `Documentation `__ | `Repo `__" +msgstr "" + +# 1f8ac9a7b4db4bb3b330567ac288e212 +#: ../../source/projects/deployment.rst:36 ea526fc3363e4edaaebac34b0f3f057b +msgid "`dockerspawner `__" +msgstr "" + +# 2b17819baf714cbea333e87b1007f41a +#: ../../source/projects/deployment.rst:38 377612fee20a4067973b9870049fc7fc +msgid "" +"Deploy notebooks for 'jupyterhub' inside Docker containers. " +"`Documentation `__ | `Repo " +"`__" +msgstr "" + +# 8ef739ace1cf4cc8bad61fb84a2d4c6d +#: ../../source/projects/deployment.rst:41 8153b8bbc5dc45898ee8ba5ba75f9b17 +msgid "`docker-stacks `__" +msgstr "" + +# d77ec1880fb64bef854fafe43b182310 +#: ../../source/projects/deployment.rst:43 3c0270377af54a54a081eb11a8a569b6 +msgid "" +"Stacks of Jupyter applications and kernels as Docker containers. " +"`Documentation `__ | `Repo " +"`__" +msgstr "" + +# 878b87f3b5334557964db57fe6ecfc00 +#: ../../source/projects/doc-proj-categories.rst:3 +#: e60946e5acad40eb9064fa3c5a49189d +msgid "Project Documentation" +msgstr "" + +# 90da53f4dfa74557a08b864016016453 +# e79e0aed79164105ba0c59db1e7cc25f +# f3a563b080c148449967e4dfb0c0c397 +# 4670de024ca342e0ae42d85db75b0b47 +# d8a293acd5814a1d8797cdf904961a54 +# bb604039b6df48aeb10f4bfd47611399 +# 79fb4da0ecf7403f8bdf26c7e5200dea +#: ../../source/projects/doc-proj-categories.rst:6 +#: ../../source/projects/incubator.rst:6 +#: ../../source/projects/ipython_projects.rst:6 +#: 1f89e69dbf8e43519b04b28eac508e44 442dcf1da78a4b6ea6927a4f612e5800 +#: 886a6055d5bc4db792fba77aa3913a44 +msgid "Contents" +msgstr "" + +# da1412ca76794532b4409e1da1d6a9c6 +#: ../../source/projects/doc-proj-categories.rst:8 +#: 290254598505444b913c81d405313bef +msgid "" +"Links to **information on usage, configuration and development** hosted " +"on Read The Docs or in the GitHub project repo." +msgstr "" + +# 05e0c934a6004550a2bbc836a9f8241e +# fc0cfc8377c448dd87f57ad3d7faf590 +#: ../../source/projects/doc-proj-categories.rst:12 +#: ../../source/projects/user-interfaces.rst:3 1903deb1bc1d4df5aef9be72060f6b40 +#: 3fac30be374f45c99d58c432c202c916 +msgid "Jupyter User Interfaces" +msgstr "" + +# 67a117c7d3874a8b9183c9c321d6a4a0 +#: ../../source/projects/doc-proj-categories.rst:13 +#: b2e24b8be3254a899c7383210f5fb31b +msgid "`Jupyter Notebook `_" +msgstr "" + +# f0f7ba9f5be24319a67f3822fdca4e63 +#: ../../source/projects/doc-proj-categories.rst:14 +#: 364acaca748f4f78a2ea8a62583eb2cc +msgid "`jupyter_console `_" +msgstr "" + +# d11bac142e77476e8ed00dbc47d8cca4 +#: ../../source/projects/doc-proj-categories.rst:15 +#: da1472b49aa54783863e0fc25dc79c3b +msgid "`qtconsole `_" +msgstr "" + +# 2c1b9d78c1164045b7e3ee67011405cb +#: ../../source/projects/doc-proj-categories.rst:18 +#: f8383b068b6149c99eab558e12e2d27b +msgid "JupyterHub" +msgstr "" + +# fed298a75504421993d6e9e5bc630551 +#: ../../source/projects/doc-proj-categories.rst:19 +#: 21878b518bed4f94b9131ba59df137b2 +msgid "`JupyterHub `_" +msgstr "" + +# 7572a9cc7da44692b9f3bc4386564364 +#: ../../source/projects/doc-proj-categories.rst:20 +#: de0a20eed2ac4ca79370896a2d777702 +msgid "" +"`configurable-http-proxy `_" +msgstr "" + +# 5c5566158224426295e9e97bb73ecc46 +#: ../../source/projects/doc-proj-categories.rst:21 +#: 2160ae2e4a3e4bbbb15bbb4f5e3b5e32 +msgid "`dockerspawner `_" +msgstr "" + +# bb55cce340ef4ea4892839cbd8337e8f +#: ../../source/projects/doc-proj-categories.rst:22 +#: d7a4dd901ec94a93aa3a04f8ea8a81cb +msgid "`ldapauthenticator `_" +msgstr "" + +# f7d54f483595450fa4b37781fd887452 +#: ../../source/projects/doc-proj-categories.rst:23 +#: 521854a746064b3dbc4a0247388b41df +msgid "`oauthenticator `_" +msgstr "" + +# dc23452377da44edbe127d34cd305a19 +#: ../../source/projects/doc-proj-categories.rst:24 +#: cb7875f485a745ee8157335b5a6e9dee +msgid "`sudospawner `_" +msgstr "" + +# fec520fc2c8a4b7aa8f54bda8447e976 +# e31418dae87748369b4fa4826b428dfc +#: ../../source/projects/doc-proj-categories.rst:27 +#: ../../source/projects/education.rst:3 a004e1ba2dd744819e3c0d94178ebe7b +#: e0865f3896de414183dfd2b5e9df7a58 +msgid "Education" +msgstr "" + +# e8ecf2b2e0e240438b897616cb0d1cec +#: ../../source/projects/doc-proj-categories.rst:28 +#: 70b9ac0a798c43f7a43f47e744a385b3 +msgid "`nbgrader `_" +msgstr "" + +# bcf3e08d367944c39c38201049663273 +#: ../../source/projects/doc-proj-categories.rst:31 +#: 5f6627db04654e44b1b1271617b92467 +msgid "Notebook Conversion and Formatting" +msgstr "" + +# 6f5a84f0d0b64958a31aeb68b9bd9d43 +#: ../../source/projects/doc-proj-categories.rst:32 +#: d3feaa1c5a4d420fa300afdaed4d075c +msgid "`nbconvert `_" +msgstr "" + +# 87e7cf3391ae49e2b5719e4f2843a9bc +#: ../../source/projects/doc-proj-categories.rst:33 +#: b9e67e5e50324643a72536def8319824 +msgid "`nbformat `_" +msgstr "" + +# 1642454b670a4f23b884da1cf8b42095 +# 838d9a305b6d4cf29191f3b95bd29e52 +#: ../../source/projects/doc-proj-categories.rst:36 +#: ../../source/projects/kernels.rst:18 9276fd73c2194a21811ec3f92ae10129 +#: 940a939777a04049857f919aae906367 +msgid "Kernels" +msgstr "" + +# 12d4b4b3066048b68cc4ff247e2beb3c +#: ../../source/projects/doc-proj-categories.rst:37 +#: fecb31fd44cd490d842cdb9f3b66d445 +msgid "`IPython `_" +msgstr "" + +# 0939ba530c894801ae11b4e65e2530f2 +#: ../../source/projects/doc-proj-categories.rst:38 +#: 792d04a2124f4656bddb5fd58a29b6e0 +msgid "`IRkernel `_" +msgstr "" + +# 10e09d0397ef4458890c8ed800194814 +#: ../../source/projects/doc-proj-categories.rst:39 +#: db01d925170c4d69bf3aa0ea69e55521 +msgid "`IJulia `_" +msgstr "" + +# e7d05d24d92f4db3a46dd43f6b247ad6 +#: ../../source/projects/doc-proj-categories.rst:40 +#: 47ee4d30281f4f91bfc28c99756b9ec9 +msgid "" +"`List of community maintained language kernels " +"`_" +msgstr "" + +# 831ada76059b4ebea4e80a139b91ef06 +#: ../../source/projects/doc-proj-categories.rst:43 +#: ../../source/projects/ipython_projects.rst:3 +#: 7988712ac6304fe1b9c589b549cfc102 cc298e1dac824a4a82accfb54c0e1e9c +msgid "IPython" +msgstr "" + +# 38ae294a26394b5d97233f08b0fe9b0d +#: ../../source/projects/doc-proj-categories.rst:44 +#: 13b220c1820c43b787b1363b2bf9f183 +msgid "`IPython`_" +msgstr "" + +# 8c06cd6a311e440a8b4b90313e599a5d +#: ../../source/projects/doc-proj-categories.rst:45 +#: a3371af724514f9fab23ca507c98d747 +msgid "`ipykernel `_" +msgstr "" + +# b890abfa9d4c4040a128bf67fdaa6139 +#: ../../source/projects/doc-proj-categories.rst:46 +#: a6c8d631e859471583bc758a69c34914 +msgid "`ipyparallel `_" +msgstr "" + +# 1f0fbbbf059d4c7182c15c9c48dd5450 +# aafbcd62f5d4479f9501ef2df6a138f0 +#: ../../source/projects/doc-proj-categories.rst:49 +#: 091c288836124588985a2941b587e208 +msgid "Deployment" +msgstr "" + +# 3e5210e31d784c19acf03439c303ab54 +#: ../../source/projects/doc-proj-categories.rst:50 +#: b907caf70eb5462b86b5210d652fe5aa +msgid "`docker-stacks `_" +msgstr "" + +# 4ee088e2656c4478ae6af2f710282744 +#: ../../source/projects/doc-proj-categories.rst:51 +#: 9479c83bc1814b44ba6442983d3b8429 +msgid "`ipywidgets `_" +msgstr "" + +# 6ce5c42884a14600bb1271b40d06d02b +#: ../../source/projects/doc-proj-categories.rst:52 +#: c2f23cbc829d4037823521d67db6c859 +msgid "`jupyter-drive `_" +msgstr "" + +# 97e013d4dc7e44dc88d18c6151f7f7e7 +#: ../../source/projects/doc-proj-categories.rst:53 +#: b31a5018e0e24e8f8b6b7f2fb6c9bbbf +msgid "`jupyter-sphinx-theme `_" +msgstr "" + +#: ../../source/projects/doc-proj-categories.rst:54 +#: 398c715f09f44ec4ac1c3d52fa8ff410 +msgid "" +"`kernel_gateway `_" +msgstr "" + +# 6b76351692c6479493985193869e2a03 +#: ../../source/projects/doc-proj-categories.rst:55 +#: 8a6996a5db054c5cbdc50e79c31ecb2f +msgid "`nbviewer `_" +msgstr "" + +# 66405b5e2ad54aa39e2dd7f77874a08c +#: ../../source/projects/doc-proj-categories.rst:56 +#: ddbd672dcd394159ab6d215030d133de +msgid "`tmpnb `_" +msgstr "" + +# 0a3317a3f98a4a428c7af8adb2d282be +#: ../../source/projects/doc-proj-categories.rst:57 +#: 016c5379e3d441939fa6c3b330fb9755 +msgid "`traitlets `_" +msgstr "" + +# e73d09d0ce1245c88186f99fb6d07143 +#: ../../source/projects/doc-proj-categories.rst:61 +#: 4148dcc99afd49a8a7701502d24563f8 +msgid "`jupyter-js-notebook `_" +msgstr "" + +# 312f96ae98194c598857978bec70d4e1 +#: ../../source/projects/doc-proj-categories.rst:62 +#: eeabdb4a2eeb42109a293441cadb6130 +msgid "`jupyter-js-phosphide `_" +msgstr "" + +# 3f8abf0c8fa54d01ba938fe0cfa6ae3f +#: ../../source/projects/doc-proj-categories.rst:63 +#: 9d587445281c4d64b7315080fc0a8729 +msgid "`jupyter-js-plugins `_" +msgstr "" + +# f563f0f8921b40c9a56aa72a62a7ae08 +#: ../../source/projects/doc-proj-categories.rst:64 +#: de89a9f4f32c4408b5cde69bdfea30b1 +msgid "`jupyter-js-services `_" +msgstr "" + +# 932e4e56da8149dc9b19c939d0ce6291 +#: ../../source/projects/doc-proj-categories.rst:65 +#: 2a28d7a966684f10a9c4c23ea3d0090c +msgid "`jupyter-js-ui `_" +msgstr "" + +# 5d5e4940d3624873a4b2c39ce7d4ea00 +#: ../../source/projects/doc-proj-categories.rst:66 +#: 921ca309a8a647d9805960b7b8401af2 +msgid "`jupyter-js-utils `_" +msgstr "" + +# 94f4104fc2a346e9b752026e94ccb9b8 +#: ../../source/projects/doc-proj-categories.rst:70 +#: 854e4f5b4c52490a8509d94d5869b383 +msgid "`jupyter_client `_" +msgstr "" + +# a7c0c77907204a10aa56b382435e60e7 +#: ../../source/projects/doc-proj-categories.rst:71 +#: 80b26ee700c441998a5ae7c231368cd1 +msgid "`jupyter_core `_" +msgstr "" + +# de4778c3365b43a3b2f0eaf1202f009e +#: ../../source/projects/education.rst:5 1d843ef77bf347e48eab2dd59287d054 +msgid "" +"Jupyter Notebooks offer exciting and creative possibilities in education." +" The following subprojects are focused on supporting the use of Jupyter " +"Notebook in a variety of educational settings." +msgstr "" + +# 7c1bb06e24c34d31a3e5d647eb968ef4 +#: ../../source/projects/education.rst:10 b00836087c964143b56f75362d0c50c0 +msgid "`nbgrader `__" +msgstr "" + +# e871a361fed74d7984ccf6be1d16ae4f +#: ../../source/projects/education.rst:12 2e8cc58e20b348a287c6cc22f64e30f2 +msgid "" +"tools for managing, grading, and reporting of notebook based assignments." +" `Documentation `__ | `Repo " +"`__" +msgstr "" + +# cba6565dfef44292847ee4619fb67cdd +#: ../../source/projects/incubator.rst:3 1f1778081df946a49ad98f6c97f90f42 +msgid "Incubator Projects" +msgstr "" + +# 28287c3575fc4697829583939cfd9ef0 +#: ../../source/projects/incubator.rst:8 bc7f7bbf9813435da9bf31f01b85d5a4 +msgid "" +"The `Jupyter incubator `_ gives " +"emerging projects a place to evolve." +msgstr "" + +# b6fadf1a90d64f40bc531afda9e7f181 +#: ../../source/projects/incubator.rst:12 1085147744204109890f96f19754c487 +msgid "Descriptions" +msgstr "" + +# 75694883742b41c7b1dbf76b66fab082 +#: ../../source/projects/incubator.rst:14 d7b89ca766624a528e6b86d75e67b0cc +msgid "Interesting projects include:" +msgstr "" + +# edf5c1a57381452f81241ced74bfd684 +#: ../../source/projects/incubator.rst:16 2d4835fdae924e9f9684986ccfc50b6f +msgid "" +"`content management extensions `_ - Jupyter Content Management Extensions" +msgstr "" + +# 60cda82020be42c08afd057695bea4a4 +#: ../../source/projects/incubator.rst:17 ccf861baed1e49219f1b377ce8b7d4c3 +msgid "" +"`dashboards `_ - Jupyter" +" Dynamic Dashboards from Notebooks" +msgstr "" + +# 254de647304647ab8073b020d1cc3b01 +#: ../../source/projects/incubator.rst:18 77444fc2164b462f895b3125dd603823 +msgid "" +"`declarative widgets `_ - Jupyter Declarative Widgets Extension" +msgstr "" + +# 43b5a7a788f74c0fa8d7532dcec2a001 +#: ../../source/projects/incubator.rst:19 3b1da08b7351473693d9dc648f513a5e +msgid "" +"`kernel gateway bundlers `_ - Converts a notebook to a kernel " +"gateway microservice bundle for download" +msgstr "" + +# a70e8c643c034c8f95ecc7d52c3b76eb +#: ../../source/projects/incubator.rst:20 320a91d998f14acd9e619e9da28110c6 +msgid "" +"`showcase`_ - A spot to try demos of one or more incubating Jupyter " +"projects in `Binder `_" +msgstr "" + +# d70eebc552ab4bd197ee7bbd9def1a9b +#: ../../source/projects/incubator.rst:21 8448666d869a4e7b8346cd096abf4f39 +msgid "" +"`sparkmagic `_ - Jupyter" +" magics and kernels for working with remote Spark clusters" +msgstr "" + +# 99fd5864d2694a498188465e90d5e366 +#: ../../source/projects/incubator.rst:22 fd9a1f7360834c2b931c30829bf70efe +msgid "" +"`traittypes `_ - " +"Traitlets types for NumPy, SciPy and friends" +msgstr "" + +# 39368898693b438885f9f91f59f62a9f +#: ../../source/projects/incubator.rst:24 e1de8a25045d40da986adc57fb4749b3 +msgid "" +"There's also a `repository with proposals `_ of projects wishing to enter the incubator." +msgstr "" + +# 71076519b1d94f87afd451f597df50a4 +#: ../../source/projects/incubator.rst:28 d33051989e064da0b0e1bd546fbe0215 +msgid "Try the Incubator Projects" +msgstr "" + +# a90ed853561445ad937d3baab7ed807a +#: ../../source/projects/incubator.rst:30 cec5f4848fd04164839ac8e4d1d7a8ce +msgid "" +"The `showcase`_ application allows you to try demos of one or more " +"incubating Jupyter projects in `Binder `_. Just " +"head over to the `showcase`_ repo and press the :guilabel:`Launch Binder`" +" button badge to launch the online trial. You should see an interactive " +"notebook similar to this one:" +msgstr "" + +# 7f631307348a402f9ab66eba132737cb +# 40bf2641321f415f931e61d4e62e90cb +#: ../../source/projects/ipython_projects.rst:9 +#: c75f37b86eb54f13b3aa976ec8ed2a65 +msgid "Description" +msgstr "" + +# 543da61e80f44ef1b1e3d57d909161c4 +#: ../../source/projects/ipython_projects.rst:11 +#: 2df04b81508e4ccd9609169f43000780 +msgid "" +"`IPython `_ provides a rich architecture for " +"interactive computing with:" +msgstr "" + +# 8e4ff36b60e9432594471c8fee1d7163 +#: ../../source/projects/ipython_projects.rst:14 +#: c380133161014b66a64b203652f89ed7 +msgid "A powerful interactive shell." +msgstr "" + +# d432b9c2e4c64adfb2f6100665eb0f9c +#: ../../source/projects/ipython_projects.rst:15 +#: 57720b8e59f543aaa27dbbdbadde8f91 +msgid "A kernel for Jupyter." +msgstr "" + +# b0e52b8513b0457eb61bda3e14f785ec +#: ../../source/projects/ipython_projects.rst:16 +#: 1f8bdfc3e93a4975bc13842e3eaf1ad9 +msgid "Support for interactive data visualization and use of GUI toolkits." +msgstr "" + +# aaaead17f2ca44c896c99ed5e1192dee +#: ../../source/projects/ipython_projects.rst:17 +#: 73dcc8d0eba941c598ac56e780a855f5 +msgid "Flexible, embeddable interpreters to load into your own projects." +msgstr "" + +# ea29a6d9e0734512a00cfa5ad436bec1 +#: ../../source/projects/ipython_projects.rst:18 +#: 7960eeb1a5c24e40b07a4089208faf21 +msgid "Easy to use, high performance tools for parallel computing." +msgstr "" + +# 2cc5f1f88b0c4d8cb1a1613e4282356c +#: ../../source/projects/ipython_projects.rst:21 +#: 628853f85bd44347b2967b5d03bbdcee +msgid "Background" +msgstr "" + +# 3fe872113f4c4e15b82282d04efface1 +#: ../../source/projects/ipython_projects.rst:23 +#: f4305070f24f4930990523cb1e2aec08 +msgid "" +"IPython is a growing project, with increasingly language-agnostic " +"components. IPython 3.x was the last monolithic release of IPython, " +"containing the notebook server, qtconsole, etc. As of IPython 4.0, the " +"language-agnostic parts of the project: the notebook format, message " +"protocol, qtconsole, notebook web application, etc. have moved to new " +"projects under the name Jupyter. IPython itself is focused on interactive" +" Python, part of which is providing a Python kernel for Jupyter." +msgstr "" + +# b42a67733d444e32973954185f0f70cb +#: ../../source/projects/ipython_projects.rst:32 +#: fc6e953c8e64431480e126adbec60208 +msgid "Resources" +msgstr "" + +# 3e453e9551974bec9e26dd108e807789 +#: ../../source/projects/ipython_projects.rst:34 +#: 9ff9e28edf2e4ed6af09d6c968a48dc4 +msgid "The projects with repos in the IPython organization on GitHub include:" +msgstr "" + +# 5031645557cd44ecb80e167383ac147f +#: ../../source/projects/ipython_projects.rst:36 +#: e705dbd896b748ba92cd876ea35c529c +msgid "" +"IPython `ipykernel `_ " +"interactive computing in Python." +msgstr "" + +# fcd79ae7b74b40ccbf3aaf50a7ace569 +#: ../../source/projects/ipython_projects.rst:38 +#: 91e01e0d910b488e8e5e5ddc73a934be +msgid "" +"`ipyparallel `_ " +"lightweight parallel computing in Python offering seamless notebook " +"integration" +msgstr "" + +# 69568ee92daf451489775caebb747947 +#: ../../source/projects/ipython_projects.rst:40 +#: fd2e1e2726e6455389b7a0a34d607a35 +msgid "" +"`ipywidgets `_ interactive " +"widgets for Python in the Jupyter Notebook" +msgstr "" + +# 8ccbc30eb55f436d8af25b13a9cd5ef7 +#: ../../source/projects/kernels.rst:5 93480518f1ac406a95251925bc4eaea3 +msgid "Kernels (Programming Languages)" +msgstr "" + +# badc42c2b34c4d11ae7aa2b2767f3728 +#: ../../source/projects/kernels.rst:7 85a6186c908847eeaeeb6f9eba983d5a +msgid "" +"The Jupyter team maintains the `IPython kernel " +"`_ since the Jupyter notebook server " +"depends on the IPython :term:`kernel` functionality. Many other " +"languages, in addition to Python, may be used in the notebook." +msgstr "" + +# 028a578af22144598ff940f737764962 +#: ../../source/projects/kernels.rst:12 e899fbd1ce764c61a9fbaaf13317be3b +msgid "" +"The community maintains many other language kernels, and new kernels " +"become available often. Please see the `list of available kernels`_ for " +"additional languages and `kernel installation instructions`_ to begin " +"using these language kernels." +msgstr "" + +# c4527340da8c4cb89829a1a1b39ed1a5 +#: ../../source/projects/kernels.rst:20 19d23bf23e114f51a67387ab6ea3b4a4 +msgid "" +"Kernels are `programming language specific` processes that run " +"independently and interact with the Jupyter Applications and their user " +"interfaces. `IPython `__ is the reference Jupyter " +"kernel, providing a powerful environment for interactive computing in " +"Python." +msgstr "" + +# 6dd6dcd0bc1840da8916fc03f01788ef +#: ../../source/projects/kernels.rst:26 b113a09ef00f418d927e4f693a92e2ce +msgid "`IPython `__" +msgstr "" + +# f2c9f65822ee444fbaa722750c715cce +#: ../../source/projects/kernels.rst:28 99e1ae2bf1c14322b4ebc9a30c3f99fe +msgid "" +"interactive computing in Python. `Documentation " +"`__ | `Repo " +"`__" +msgstr "" + +# bb0dcd6ea74f438e8a548661894d6f19 +#: ../../source/projects/kernels.rst:31 e4947295a5224f00a88936ab0dcafc03 +msgid "`ipywidgets `__" +msgstr "" + +# ca8e8d5e5b844a9ca0d94fbd32717a7a +#: ../../source/projects/kernels.rst:33 3c0d379247034afb850c7e89fed9e72a +msgid "" +"interactive widgets for Python in the Jupyter Notebook. `Documentation " +"`__ | `Repo " +"`__" +msgstr "" + +# c377fd53c79042d6b56baae717d8c2a0 +#: ../../source/projects/kernels.rst:36 e5456858f1f745e9bab609f3251f9b82 +msgid "`ipyparallel `__" +msgstr "" + +# 6d54f08db9124d3ab5eb18ab39c88c6e +#: ../../source/projects/kernels.rst:38 baf3ea6a78144e52a1ce563a0b439c00 +msgid "" +"lightweight parallel computing in Python offering seamless notebook " +"integration. `Documentation " +"`__ | `Repo " +"`__" +msgstr "" + +# 5d320a536a8b490fa66f06971b80fcbf +#: ../../source/projects/kernels.rst:44 68dc9c86edd94006bbc887dd914e012e +msgid "" +"`Jupyter kernels `_" +msgstr "" + +# 9474725a4e414c47a8a2c081deb7d361 +#: ../../source/projects/kernels.rst:46 4626b1f1b59a4e1f85435cb28a75d3dc +msgid "" +"A full list of kernels available for other languages. Many of these " +"kernels are developed by third parties and may or may not be stable." +msgstr "" + +# c84899e578ac4b95b3ddcb1e19ae40e4 +#: ../../source/projects/user-interfaces.rst:5 684a8d961659447f8c6746d8c1b05b99 +msgid "" +"The Jupyter user interfaces offer a foundation of interactive computing " +"environments where scientific computing, data science, and analytics can " +"be performed using a wide range of programming languages." +msgstr "" + +# 3c3427b170f3480eacb5a12321c2763f +#: ../../source/projects/user-interfaces.rst:10 +#: 51afe2efface46cfb9c48687d8971e9e +msgid "`Jupyter Notebook `__" +msgstr "" + +# 83a65fc880d64bcd9cbdc020b85c0c6c +#: ../../source/projects/user-interfaces.rst:12 +#: 4c5422b57aaa41bc84517ccff5b49f27 +msgid "" +"Web-based application for authoring documents that combine live-code with" +" narrative text, equations and visualizations. `Documentation `__ | `Repo " +"`__" +msgstr "" + +# aec9f2d0779b4c4c92d8cf427f0d8716 +#: ../../source/projects/user-interfaces.rst:16 +#: a2c99cc942ba45f6b6ae4672a3efc0c2 +msgid "`Jupyter Console `__" +msgstr "" + +# 1849d5bef10540caba484b7e713d550c +#: ../../source/projects/user-interfaces.rst:18 +#: 11b81832772f41019a1070ddfb7b91b2 +msgid "" +"Terminal based console for interactive computing. `Documentation `__ | `Repo " +"`__" +msgstr "" + +# 6d562e69261247958e947bf1f99a1578 +#: ../../source/projects/user-interfaces.rst:21 +#: 7a313db19dc84e3db53f051dc66589b1 +msgid "`Jupyter QtConsole `__" +msgstr "" + +# d11809f22b934f51994dbdd75402efe0 +#: ../../source/projects/user-interfaces.rst:23 +#: 76da2fd888d44447a2b0617eeeb8448e +msgid "" +"Qt application for interactive computing with rich output. `Documentation" +" `__ | `Repo " +"`__" +msgstr "" + +# ba1504c274984be89d08649e83e6a9a4 +#~ msgid "" +#~ "Set this environment variable to provide" +#~ " extra directories for the data " +#~ "search path. :envvar:`JUPYTER_PATH` should " +#~ "contain a series of directories, " +#~ "separated by ``os.pathsep`` (``;`` on " +#~ "Windows, ``:`` on Unix). Directories " +#~ "given in :envvar:`JUPYTER_PATH` are searched" +#~ " before other locations." +#~ msgstr "" + +# 97d7c73abdeb4f0389a7e650d037fc10 +#~ msgid "Installation, Configuration, and Usage" +#~ msgstr "" + +# 2844f35d88594b1cbcdd4fabba433e14 +#~ msgid "" +#~ "`kernel_gateway `_" +#~ msgstr "" + +#~ msgid "Advanced Use Cases" +#~ msgstr "" + +#~ msgid "Migrating from IPython Notebook" +#~ msgstr "" + +#~ msgid "Abstract" +#~ msgstr "" + +#~ msgid "" +#~ "`The Big Split `__ moved IPython's " +#~ "various language-agnostic components under " +#~ "the Jupyter umbrella. Going forward, " +#~ "Jupyter will contain the language-" +#~ "agnostic projects that serve many " +#~ "languages. IPython will continue to " +#~ "focus on Python and its use with" +#~ " Jupyter." +#~ msgstr "" + +#~ msgid "" +#~ "This document describes what has " +#~ "changed, and how you may need to" +#~ " modify your code or configuration " +#~ "when migrating from IPython version 3" +#~ " to Jupyter." +#~ msgstr "" + +#~ msgid "Understanding the Migration Process" +#~ msgstr "" + +#~ msgid "Automatic migration of files" +#~ msgstr "" + +#~ msgid "" +#~ "The first time you run any " +#~ "``jupyter`` command, it will perform an" +#~ " automatic migration of files. The " +#~ "automatic migration process **copies** files," +#~ " instead of moving files, leaving the" +#~ " originals in place and the copies" +#~ " in the Jupyter file locations. You" +#~ " can re-run the migration, if " +#~ "needed, by calling ``jupyter migrate``. " +#~ "Your custom configuration will be " +#~ "migrated automatically and should work " +#~ "with Jupyter without further editing. " +#~ "When you update or modify your " +#~ "configuration in the future, please keep" +#~ " in mind that the file locations " +#~ "may have changed." +#~ msgstr "" + +#~ msgid "Where have my configuration files gone?" +#~ msgstr "" + +#~ msgid "" +#~ "Also known as: \"Why isn't my " +#~ "configuration having any effect anymore?\"" +#~ msgstr "" + +#~ msgid "" +#~ "Jupyter splitting out from IPython means" +#~ " that the locations of some files " +#~ "have moved, and Jupyter projects have" +#~ " not inherited everything from how " +#~ "IPython did it." +#~ msgstr "" + +#~ msgid "" +#~ "When you start your first Jupyter " +#~ "application, the relevant configuration files" +#~ " are automatically copied to their " +#~ "new Jupyter locations. The original " +#~ "configuration files in the IPython " +#~ "locations have no effect on Jupyter's" +#~ " execution. If you accidentally edit " +#~ "your original IPython config file, you" +#~ " may not see the desired effect " +#~ "with Jupyter now. You should check " +#~ "that you are editing Jupyter's " +#~ "configuration file, and you should see" +#~ " the expected effect after restarting " +#~ "the Jupyter server." +#~ msgstr "" + +#~ msgid "Finding the Location of Important Files" +#~ msgstr "" + +#~ msgid "" +#~ "This section provides quick reference " +#~ "for common locations of IPython 3 " +#~ "files and the migrated Jupyter files." +#~ msgstr "" + +# bee4d55638044b5ca68875379f764a1c +#~ msgid "Configuration files" +#~ msgstr "" + +#~ msgid "" +#~ "Configuration files customize Jupyter to " +#~ "the user's preferences. The migrated " +#~ "files should all be **automatically " +#~ "copied** to their new Jupyter locations." +#~ " Here are the location changes:" +#~ msgstr "" + +#~ msgid "IPython location" +#~ msgstr "" + +#~ msgid "Jupyter location" +#~ msgstr "" + +#~ msgid ":file:`~/.ipython/profile_default/static/custom`" +#~ msgstr "" + +#~ msgid "→" +#~ msgstr "" + +#~ msgid ":file:`~/.jupyter/custom`" +#~ msgstr "" + +#~ msgid ":file:`~/.ipython/profile_default/ipython_notebook_config.py`" +#~ msgstr "" + +#~ msgid ":file:`~/.jupyter/jupyter_notebook_config.py`" +#~ msgstr "" + +#~ msgid ":file:`~/.ipython/profile_default/ipython_nbconvert_config.py`" +#~ msgstr "" + +#~ msgid ":file:`~/.jupyter/jupyter_nbconvert_config.py`" +#~ msgstr "" + +#~ msgid ":file:`~/.ipython/profile_default/ipython_qtconsole_config.py`" +#~ msgstr "" + +#~ msgid ":file:`~/.jupyter/jupyter_qtconsole_config.py`" +#~ msgstr "" + +#~ msgid ":file:`~/.ipython/profile_default/ipython_console_config.py`" +#~ msgstr "" + +#~ msgid ":file:`~/.jupyter/jupyter_console_config.py`" +#~ msgstr "" + +#~ msgid "" +#~ "To choose a directory location other " +#~ "than the default :file:`~/.jupyter`, set " +#~ "the ``JUPYTER_CONFIG_DIR`` environment variable. " +#~ "You may need to run ``jupyter " +#~ "migrate`` after setting the environment " +#~ "variable for files to be copied to" +#~ " the desired directory." +#~ msgstr "" + +#~ msgid "Data files: kernelspecs and notebook extensions" +#~ msgstr "" + +#~ msgid "" +#~ "Data files include files, other than " +#~ "configuration files, which are user " +#~ "installed. Examples include kernelspecs and" +#~ " notebook extensions. Like the " +#~ "configuration files, data files are also" +#~ " **automatically migrated** to their new" +#~ " Jupyter locations." +#~ msgstr "" + +#~ msgid "In **IPython 3**, data files lived in ``~/.ipython``." +#~ msgstr "" + +#~ msgid "In **Jupyter**, data files use platform-appropriate locations:" +#~ msgstr "" + +#~ msgid "OS X: ``~/Library/Jupyter``" +#~ msgstr "" + +#~ msgid "Windows: the location specified in ``%APPDATA%`` environment variable" +#~ msgstr "" + +#~ msgid "" +#~ "Elsewhere, ``$XDG_DATA_HOME`` is respected, " +#~ "with the default of ``~/.local/share/jupyter``" +#~ msgstr "" + +#~ msgid "" +#~ "In all cases, the ``JUPYTER_DATA_DIR`` " +#~ "environment variable can be used to " +#~ "set a location explicitly." +#~ msgstr "" + +#~ msgid "" +#~ "Data files installed system-wide (e.g." +#~ " in ``/usr/local/share/jupyter``) have not " +#~ "changed. Per-user installation of data" +#~ " files has changed location from " +#~ "``.ipython`` to the platform-appropriate " +#~ "Jupyter location." +#~ msgstr "" + +#~ msgid "Since Jupyter does not have profiles, how do I customize it?" +#~ msgstr "" + +#~ msgid "" +#~ "While IPython has the concept of " +#~ ":term:`profiles`, **Jupyter does not have " +#~ "profiles**." +#~ msgstr "" + +#~ msgid "" +#~ "In IPython, profiles are collections of" +#~ " configuration and runtime files. Inside" +#~ " the IPython directory (``~/.ipython``), " +#~ "there are directories with names like" +#~ " ``profile_default`` or ``profile_demo``. In " +#~ "each of these are configuration files" +#~ " (``ipython_config.py``, ``ipython_notebook_config.py``) " +#~ "and runtime files (``history.sqlite``, " +#~ "``security/kernel-*.json``). Profiles could be " +#~ "used to switch between configurations of" +#~ " IPython." +#~ msgstr "" + +#~ msgid "" +#~ "Previously, people could use commands " +#~ "like ``ipython notebook --profile demo`` " +#~ "to set the profile for *both* the" +#~ " notebook server and the IPython " +#~ "kernel. This is no longer possible " +#~ "in one go with Jupyter, just like" +#~ " it wasn't possible in IPython 3 " +#~ "for any other kernels." +#~ msgstr "" + +#~ msgid "Changing the Jupyter notebook configuration directory" +#~ msgstr "" + +#~ msgid "" +#~ "If you want to change the notebook" +#~ " configuration, you can set the " +#~ "``JUPYTER_CONFIG_DIR``:" +#~ msgstr "" + +#~ msgid "Changing the Jupyter notebook configuration file" +#~ msgstr "" + +#~ msgid "If you just want to change the config file, you can do:" +#~ msgstr "" + +#~ msgid "Changing IPython's profile using custom kernelspecs" +#~ msgstr "" + +#~ msgid "" +#~ "If you do want to change the " +#~ "IPython kernel's profile, you can't do" +#~ " this at the server command-line " +#~ "anymore. Kernel arguments must be " +#~ "changed by modifying the kernelspec. You" +#~ " can do this without relaunching the" +#~ " server. Kernelspec changes take effect " +#~ "every time you start a new kernel." +#~ " However, there isn't a great way " +#~ "to modify the kernelspecs. One approach" +#~ " uses ``jupyter kernelspec list`` to " +#~ "find the ``kernel.json`` file and then" +#~ " modifies it, e.g. " +#~ "``kernels/python3/kernel.json``, by hand. " +#~ "Alternatively, `a2km `__" +#~ " is an experimental project that " +#~ "tries to make these things easier." +#~ msgstr "" + +#~ msgid "" +#~ "For example, add the ``--profile`` " +#~ "option to a custom kernelspec under " +#~ "``kernels/mycustom/kernel.json`` (see the Jupyter" +#~ " kernelspec directions `here `__):" +#~ msgstr "" + +#~ msgid "" +#~ "You can then run Jupyter with the" +#~ " ``--kernel=mycustom`` command-line option " +#~ "and IPython will find the appropriate" +#~ " profile." +#~ msgstr "" + +#~ msgid "Understanding Installation Changes" +#~ msgstr "" + +#~ msgid "" +#~ "See the :ref:`install` page for more " +#~ "information about installing Jupyter. Jupyter" +#~ " automatically migrates some things, like" +#~ " Notebook extensions and kernels." +#~ msgstr "" + +#~ msgid "Notebook extensions" +#~ msgstr "" + +#~ msgid "" +#~ "Any IPython notebook extensions should " +#~ "be **automatically migrated** as part of" +#~ " the data files migration." +#~ msgstr "" + +#~ msgid "Notebook extensions were installed with:" +#~ msgstr "" + +#~ msgid "Now, extensions are installed with:" +#~ msgstr "" + +#~ msgid "" +#~ "The notebook extensions will be " +#~ "installed in a system-wide location " +#~ "(e.g. ``/usr/local/share/jupyter/nbextensions``). If " +#~ "doing a ``--user`` install, the notebook" +#~ " extensions will go in the " +#~ "``JUPYTER_DATA_DIR`` location. Installation **SHOULD" +#~ " NOT** be done manually by guessing" +#~ " where the files should go." +#~ msgstr "" + +#~ msgid "" +#~ "Kernels are installed in much the " +#~ "same way as notebook extensions. They" +#~ " will also be **automatically migrated**." +#~ msgstr "" + +#~ msgid "Kernel specs used to be installed with:" +#~ msgstr "" + +#~ msgid "They are now installed with:" +#~ msgstr "" + +#~ msgid "" +#~ "By default, kernel specs will go " +#~ "in a system-wide location (e.g. " +#~ "``/usr/local/share/jupyter/kernels``). If doing a" +#~ " ``--user`` install, the kernel specs " +#~ "will go in the ``JUPYTER_DATA_DIR`` " +#~ "location. Installation **SHOULD NOT** be " +#~ "done manually by guessing where the " +#~ "files should go." +#~ msgstr "" + +#~ msgid "Understanding Changes in imports" +#~ msgstr "" + +#~ msgid "" +#~ "IPython 4.0 includes shims to manage " +#~ "dependencies; so, all imports that work" +#~ " on IPython 3 should continue to " +#~ "work on IPython 4. If you find " +#~ "any differences, please `let us know " +#~ "`__." +#~ msgstr "" + +#~ msgid "Some changes include:" +#~ msgstr "" + +#~ msgid "IPython 3" +#~ msgstr "" + +#~ msgid "Jupyter and IPython 4.0" +#~ msgstr "" + +#~ msgid "``IPython.html``" +#~ msgstr "" + +#~ msgid "``notebook``" +#~ msgstr "" + +#~ msgid "``IPython.html.widgets``" +#~ msgstr "" + +#~ msgid "``ipywidgets``" +#~ msgstr "" + +#~ msgid "``IPython.kernel``" +#~ msgstr "" + +#~ msgid "``jupyter_client``, ``ipykernel``" +#~ msgstr "" + +#~ msgid "``IPython.parallel``" +#~ msgstr "" + +#~ msgid "``ipyparallel``" +#~ msgstr "" + +#~ msgid "``IPython.qt.console``" +#~ msgstr "" + +#~ msgid "``qtconsole``" +#~ msgstr "" + +#~ msgid "``IPython.utils.traitlets``" +#~ msgstr "" + +#~ msgid "``traitlets``" +#~ msgstr "" + +#~ msgid "``IPython.config``" +#~ msgstr "" + +#~ msgid "``traitlets.config``" +#~ msgstr "" + +#~ msgid "The ``IPython.kernel`` Split" +#~ msgstr "" + +#~ msgid "``IPython.kernel`` became two packages:" +#~ msgstr "" + +#~ msgid "``jupyter_client`` for the Jupyter client-side APIs." +#~ msgstr "" + +#~ msgid "``ipykernel`` for Jupyter's IPython kernel" +#~ msgstr "" + +# 92339a9a41b542e298b60cdb6f6cbf61 +#~ msgid "Jupyter's Common Configuration Approach" +#~ msgstr "" + +# 50ef143cd1864073a32ebb2bebdb1498 +# 4e98dda3ce1c4ddb8e35780e8e7651a6 +#~ msgid "Summary" +#~ msgstr "" + +# 67c9b078874340d2a7434509d80b1dcb +#~ msgid "" +#~ "**Common Jupyter configuration system** The" +#~ " Jupyter applications have a common " +#~ "config system, and a common :ref:`config" +#~ " directory `. By default, this" +#~ " directory is :file:`~/.jupyter`." +#~ msgstr "" + +# 631c35d8d9ea49129b1a252a853e4683 +#~ msgid "" +#~ "**Kernel configuration directories** If " +#~ "kernels use config files, these will " +#~ "normally be organised in separate " +#~ "directories for each kernel. For " +#~ "instance, the IPython kernel looks for" +#~ " files in the :ref:`IPython directory " +#~ "` instead of the default " +#~ "Jupyter directory :file:`~/.jupyter`." +#~ msgstr "" + +# c275e83d19c14b30a5fed2db4d317a77 +#~ msgid "The Python config file" +#~ msgstr "" + +# 883c3694cddb4a79b753d056967b392f +#~ msgid "To create a default config file, run:" +#~ msgstr "" + +# 249e9606296f42fd9d3d746ce2e2e818 +#~ msgid "" +#~ "The generated file will be named " +#~ ":file:`jupyter_{application}_config.py`." +#~ msgstr "" + +# 5885d077ef0c4a399da2fd455a465fca +#~ msgid "" +#~ "By editing the " +#~ ":file:`jupyter_{application}_config.py` file, you " +#~ "can configure class attributes like " +#~ "this::" +#~ msgstr "" + +# 5b49864fb34346d38f53ab5c5cc396dc +#~ msgid "" +#~ "Be careful with spelling. Incorrect " +#~ "names will simply be ignored, with " +#~ "no error message." +#~ msgstr "" + +# ab038bbb09b648e59a1f74f6d2a58d7a +#~ msgid "" +#~ "To add to a collection which may" +#~ " have already been defined elsewhere, " +#~ "you can use methods like those " +#~ "found on lists, dicts and sets: " +#~ "``append``, ``extend``, " +#~ ":meth:`~traitlets.config.LazyConfigValue.prepend` (like " +#~ "extend, but at the front), ``add``, " +#~ "and ``update`` (which works both for " +#~ "dicts and sets)::" +#~ msgstr "" + +# ee2b6c90ccd04fe4b948fcc54a29816f +#~ msgid "Command line options for configuration" +#~ msgstr "" + +# e9fa04aaf42e49cbb4d8262ce23da43d +#~ msgid "" +#~ "Every configurable value can also be " +#~ "set from the command line and " +#~ "passed as an argument, using this " +#~ "syntax:" +#~ msgstr "" + +# 4ab9825a5d064abb8181c8eecc58c8aa +#~ msgid "" +#~ "Frequently used options will also have" +#~ " short aliases and flags, such as " +#~ "``--port 8754`` or ``--no-browser``." +#~ msgstr "" + +# b4439d388ac44302a41c3f75677822ef +#~ msgid "" +#~ "To see the abbreviated options, pass " +#~ "``--help`` or ``--help-all`` as follows:" +#~ msgstr "" + +# 2029a2c8cf304fc1a83b1903b362fe7e +#~ msgid "" +#~ "Command line options **will override** " +#~ "options set within a configuration file." +#~ msgstr "" + +# 36415b5e588946969565a4a22179fb99 +#~ msgid ":mod:`traitlets:traitlets.config`" +#~ msgstr "" + +# ae0cd4a04e9e4835a145e80ea304ec17 +#~ msgid "The low-level architecture of this config system." +#~ msgstr "" + +#~ msgid "Using Jupyter" +#~ msgstr "" + +# b3daae6ac8b8407d9311cebd6b0cd982 +#~ msgid "Installation" +#~ msgstr "" + +# 25e5f9f40ad84a3183e46a0701c5d083 +#~ msgid "How do I decide which packages I need?" +#~ msgstr "" + +# c96ce8e348c543bfbb7beb3622bd7d3b +#~ msgid "Configuration" +#~ msgstr "" + +# 54d90121c5e24975be1c0cb3350e3a0b +#~ msgid "Usage and Projects" +#~ msgstr "" + +# d70338c3f7bf458daf73b7925ba29e35 +#~ msgid "IPython Projects" +#~ msgstr "" + +# 5873cdc3af584936a50d5b8af40991b8 +#~ msgid "The :command:`jupyter` Command" +#~ msgstr "" + +# dc3c602ec8854657a96f6c09c3dd9f45 +#~ msgid "Synopsis" +#~ msgstr "" + +# 5d111077ba074d05aa380c53ba1077ea +#~ msgid "" +#~ "Commands like ``jupyter notebook`` start " +#~ "Jupyter applications. The ``jupyter`` command" +#~ " is primarily a namespace for " +#~ "subcommands. A command like ``jupyter-" +#~ "foo`` found on your :envvar:`PATH` will" +#~ " be available as a subcommand " +#~ "``jupyter foo``." +#~ msgstr "" + +# 0e8211d5b2854743b58424aefd143a97 +#~ msgid "" +#~ "The :command:`jupyter` command can also " +#~ "be used to do actions other than" +#~ " starting a Jupyter application." +#~ msgstr "" + +# a546e6c4a3b24260a822ed09c7693c0b +#~ msgid "Command options" +#~ msgstr "" + +# d3d42ef830c540d385919f7ed738f6a4 +#~ msgid "Show help information, including available subcommands." +#~ msgstr "" + +# 2ee91915ba0a4908852438e641def692 +#~ msgid "Show the location of the config directory." +#~ msgstr "" + +# 997e64311bf24e22a8e4e0a0a9b89dbd +# 22ee798fcab64510b6f0c41b0df73590 +#~ msgid "Show the location of the data directory." +#~ msgstr "" + +# e5e91677a331416b8f2a98f8aa6fd883 +#~ msgid "Show the location of the runtime directory." +#~ msgstr "" + +# e5c4ae5c93e746cda9ba4d8983622523 +#~ msgid "Show all Jupyter directories and search paths." +#~ msgstr "" + +# 4d02755d025148c1a043839fec6f39ac +#~ msgid "Print directories and search paths in machine-readable JSON format." +#~ msgstr "" + +# ccb6b7bfee9d4fad9e1e4da9ab283003 +#~ msgid "Common Directories and File Locations" +#~ msgstr "" + +# 0b4e49809d05429a85146eae83d1b3a5 +#~ msgid "" +#~ "Jupyter stores different files (i.e. " +#~ "configuration, data, runtime) in a " +#~ "number of different locations. Environment " +#~ "variables may be set to customize " +#~ "for the location of each file " +#~ "type." +#~ msgstr "" + +# 5ee6c30612914af782ef9436a418d1ea +#~ msgid "" +#~ "Jupyter separates **data files** " +#~ "(nbextensions, kernelspecs) from **runtime " +#~ "files** (logs, pid files, connection " +#~ "files) from **configuration** (config files," +#~ " custom.js)." +#~ msgstr "" + +# a2bb292bb5b44bc6ac0a00926eb1a21c +#~ msgid "Config files are stored by default in the :file:`~/.jupyter` directory." +#~ msgstr "" + +# e41adbe74f6d474e9cc3eb26c516ce89 +#~ msgid "" +#~ "Set this environment variable to use " +#~ "a particular directory, other than the" +#~ " default, for Jupyter config files." +#~ msgstr "" + +# e12398b48b1340d6bbaf749a104ae9e7 +#~ msgid "" +#~ "Besides the user config directory " +#~ "mentioned above, Jupyter has a search" +#~ " path of additional locations from " +#~ "which a config file will be " +#~ "loaded. Here's a table of the " +#~ "locations to be searched, in order " +#~ "of preference:" +#~ msgstr "" + +# 279e6f91f5d44886a35a4c1357897789 +#~ msgid "Unix" +#~ msgstr "" + +# 6fd5c493414044c59661c483a397b901 +# 7ac748a5da594a0e8795dc4d126d5ff6 +#~ msgid "Windows" +#~ msgstr "" + +# 7d93e5f1b6964a0a8749d3f4589b2c66 +#~ msgid ":envvar:`JUPYTER_CONFIG_DIR`" +#~ msgstr "" + +# 76ba7f9b667d4164a38b80798883a1b7 +#~ msgid "``{sys.prefix}/etc/jupyter/``" +#~ msgstr "" + +# 91813f6c49834cf3af9f4a75bdd82a3f +#~ msgid "``/usr/local/etc/jupyter/`` ``/etc/jupyter/``" +#~ msgstr "" + +# e74637fd387f47ccb068dbc01bded802 +#~ msgid "``%PROGRAMDATA%\\jupyter\\``" +#~ msgstr "" + +# 712a90ba320f4bda9acb4e6df9b85bc2 +#~ msgid "" +#~ "To list the config directories " +#~ "currently being used you can run " +#~ "the below command from the " +#~ ":term:`command line`::" +#~ msgstr "" + +# 3d7cf86772e94325921cf76bee6e2870 +#~ msgid "The following command shows the config directory specifically:::" +#~ msgstr "" + +# 64964fbe2be242c8bac8ee7af6ec573a +#~ msgid "Data files" +#~ msgstr "" + +# 11ceec0e782b4fc29d0268325a9e2a2c +#~ msgid "" +#~ "Jupyter uses a search path to find" +#~ " installable data files, such as " +#~ ":ref:`kernelspecs ` and notebook " +#~ "extensions. When searching for a " +#~ "resource, the code will search the " +#~ "search path starting at the first " +#~ "directory until it finds where the " +#~ "resource is contained." +#~ msgstr "" + +# c90c9a0db78f48a2a2d9c62ec1d46ab6 +#~ msgid "" +#~ "Each category of file is in a " +#~ "subdirectory of each directory of the" +#~ " search path. For example, kernel " +#~ "specs are in ``kernels`` subdirectories." +#~ msgstr "" + +# 647d5ad697844066856582f9798bac8c +#~ msgid "" +#~ "Set this environment variable to provide" +#~ " extra directories for the data " +#~ "search path. :envvar:`JUPYTER_PATH` should " +#~ "contain a series of directories, " +#~ "separated by ``os.pathsep`` (``;`` on " +#~ "Windows, ``:`` on Unix). Directories " +#~ "given in :envvar:`JUPYTER_PATH` are searched" +#~ " before other locations. This is used" +#~ " in addition to other entries, rather" +#~ " than replacing any." +#~ msgstr "" + +# f8a146011f294865a766b75fa7e17ca7 +#~ msgid "Linux (& other free desktops)" +#~ msgstr "" + +# b050321d85634c2b8e2b2a6dcd904919 +#~ msgid "Mac" +#~ msgstr "" + +# cd9e53136025484cacee2884c4b0d516 +#~ msgid ":envvar:`JUPYTER_PATH`" +#~ msgstr "" + +# 391fe50861314e57a7daa84d3e5e2bab +#~ msgid "``~/.local/share/jupyter/`` (respects ``$XDG_DATA_HOME``)" +#~ msgstr "" + +# 06e83363053c4fbba0effd942e901744 +#~ msgid "``~/Library/Jupyter``" +#~ msgstr "" + +# 6d67a10caff64039a15564a99c3006f9 +#~ msgid "``%APPDATA%\\jupyter``" +#~ msgstr "" + +# deb75cfd63164420803927a5649e969a +#~ msgid "``{sys.prefix}/share/jupyter/``" +#~ msgstr "" + +# f0d3dcdaccca4791b9a44deae35c97e4 +#~ msgid "``/usr/local/share/jupyter`` ``/usr/share/jupyter``" +#~ msgstr "" + +# b7b523630e9242a4a12dbf7542ad65dc +#~ msgid "``%PROGRAMDATA\\jupyter``" +#~ msgstr "" + +# c016305bf516483f8048f46243bedb89 +#~ msgid "" +#~ "The config directory for Jupyter data" +#~ " files, which contain non-transient, " +#~ "non-configuration files. Examples include " +#~ "kernelspecs, nbextensions, or voila templates." +#~ msgstr "" + +# 93f141ed01a04032ba00104d9008f0ce +#~ msgid "" +#~ "Set this environment variable to use " +#~ "a particular directory, other than the" +#~ " default, as the user data directory." +#~ msgstr "" + +# be2f6aa85e8348f0b48fe81a9e7c7e51 +# 17b2259855234b139898fe8b707f7f99 +#~ msgid "" +#~ "As mentioned above, to list the " +#~ "config directories currently being used " +#~ "you can run the below command from" +#~ " the :term:`command line`::" +#~ msgstr "" + +# e1f07d1d80ef45ab86cfab2a02a686e2 +#~ msgid "The following command shows the data directory specifically:::" +#~ msgstr "" + +# b93aebf5941e4312998c3a4c9f1e295e +#~ msgid "Runtime files" +#~ msgstr "" + +# 9e1d0a2fed714ebdad259185c2c0ebbc +#~ msgid "" +#~ "Things like connection files, which are" +#~ " only useful for the lifetime of " +#~ "a particular process, have a runtime " +#~ "directory." +#~ msgstr "" + +# 6863708a008443d2b5c64ccc5536c1e0 +#~ msgid "" +#~ "On Linux and other free desktop " +#~ "platforms, these runtime files are " +#~ "stored in ``$XDG_RUNTIME_DIR/jupyter`` by " +#~ "default. On other platforms, it's a " +#~ "``runtime/`` subdirectory of the user's " +#~ "data directory (second row of the " +#~ "table above)." +#~ msgstr "" + +# bd275402d825484bb6293ac54280c325 +#~ msgid "An environment variable may also be used to set the runtime directory." +#~ msgstr "" + +# dffbcd47c8624f2b9add3a0577b40ea2 +#~ msgid "Set this to override where Jupyter stores runtime files." +#~ msgstr "" + +# ff2734f738bc4684a4f5005e16bf7a29 +#~ msgid "The following command shows the runtime directory specifically:::" +#~ msgstr "" + +# f79b9f3ae9f64f58abb71234571306d4 +#~ msgid ":envvar:`JUPYTER_CONFIG_DIR` for config file location" +#~ msgstr "" + +# 337b31b2027e41ee99263264a0e43464 +#~ msgid ":envvar:`JUPYTER_PATH` for datafile directory locations" +#~ msgstr "" + +# 68aa88fd12b5481391003547261aa646 +#~ msgid ":envvar:`JUPYTER_DATA_DIR` for data file location" +#~ msgstr "" + +# 5d107ae276ea4dc8bf1d85dbb80bc83d +#~ msgid ":envvar:`JUPYTER_RUNTIME_DIR` for runtime file location" +#~ msgstr "" + +# e23bc6d9b72d47548301020f53a1ed24 +#~ msgid ":mod:`jupyter_core.paths`" +#~ msgstr "" + +# ca3b8f756259407baf25bf422b315237 +#~ msgid "The Python API to locate these directories." +#~ msgstr "" + +# 5ce8e7c0d39740a1bfcbf01c68fd1eaf +#~ msgid ":ref:`jupyter_command`" +#~ msgstr "" + +# 77254e7e6f644d49a9475e8bd2e47d8a +#~ msgid "Locate these directories from the command line." +#~ msgstr "" + +# b8c9bc5ad06b47d1bf4eb72a5bb7778a +#~ msgid "" +#~ "Project Jupyter is developed as a " +#~ "set of subprojects. This section " +#~ "describes the subprojects with links to" +#~ " their documentation or GitHub " +#~ "repositories." +#~ msgstr "" + +# 42f7355e70a2465091323cab4580f41c +#~ msgid "Upgrading Jupyter Notebook" +#~ msgstr "" + +# 440ad06fd1184be59ef54118786fb0e4 +#~ msgid "Upgrading Jupyter Notebook using Anaconda" +#~ msgstr "" + +# 18dbe73b2ce04c938891ba31dea7fe2c +# dd8463cadc3a4083a009cd56974e52d5 +#~ msgid "If using **Anaconda**, update Jupyter using ``conda``:" +#~ msgstr "" + +# a9da6695326c43b2a352e704d29b2dca +# 6fab146490114576a0eb827544c97bda +#~ msgid "See :ref:`Run the Notebook ` for running the Jupyter Notebook." +#~ msgstr "" + +# f8b0d1051b0744969dc1f9f522461d3e +#~ msgid "Upgrading IPython Notebook to Jupyter Notebook" +#~ msgstr "" + +# 1a22753f51114de08d7186b0712d06b8 +#~ msgid "" +#~ "The Jupyter Notebook used to be " +#~ "called the IPython Notebook. If you " +#~ "are running an older version of " +#~ "the IPython Notebook (version 3 or " +#~ "earlier) you can use the following " +#~ "to upgrade to the latest version " +#~ "of the Jupyter Notebook." +#~ msgstr "" + +# d88146b35caa48739050570489690ea2 +#~ msgid "*or*" +#~ msgstr "" + +# e5a0f0b2480d4d288496520262d1b1f5 +#~ msgid "If using :term:`pip`:" +#~ msgstr "" + +# f3af7fac60674d649aee3681c819a3f8 +#~ msgid "" +#~ "The :ref:`migrating ` document has" +#~ " additional information about migrating " +#~ "from IPython 3 to Jupyter." +#~ msgstr "" + +#~ msgid "Narratives and Use Cases" +#~ msgstr "" + +#~ msgid "What are Narratives?" +#~ msgstr "" + +#~ msgid "" +#~ "Narratives are *collaborative*, *shareable*, " +#~ "*publishable*, and *reproducible*. We believe" +#~ " that Narratives help both yourself " +#~ "and other researchers by sharing your" +#~ " use of Jupyter projects, technical " +#~ "specifics of your deployment, and " +#~ "installation and configuration tips so " +#~ "that others can learn from your " +#~ "experiences." +#~ msgstr "" + +#~ msgid "Jupyter for Data Science" +#~ msgstr "" + +#~ msgid "" +#~ "The purpose of this page is to " +#~ "highlight kernels and other projects " +#~ "that are central to the usage of" +#~ " Jupyter in data science. This page" +#~ " is not meant to be comprehensive " +#~ "or unbiased, but rather to provide " +#~ "an opinionated view of the usage " +#~ "of Jupyter in data science based " +#~ "on our interactions with users." +#~ msgstr "" + +#~ msgid "The following Jupyter kernels are widely used in data science:" +#~ msgstr "" + +#~ msgid "python" +#~ msgstr "" + +#~ msgid "IPython (`GitHub Repo `__)" +#~ msgstr "" + +#~ msgid "R" +#~ msgstr "" + +#~ msgid "" +#~ "IRkernel (`Documentation `__," +#~ " `GitHub Repo " +#~ "`__)" +#~ msgstr "" + +#~ msgid "IRdisplay (`GitHub Repo `__)" +#~ msgstr "" + +#~ msgid "repr (`GitHub Repo `__)" +#~ msgstr "" + +#~ msgid "Julia" +#~ msgstr "" + +#~ msgid "" +#~ "IJulia Kernel (`GitHub Repo " +#~ "`__)" +#~ msgstr "" + +#~ msgid "" +#~ "Interactive Widgets (`GitHub Repo " +#~ "`__)" +#~ msgstr "" + +#~ msgid "Bash (`GitHub Repo `__)" +#~ msgstr "" + +#~ msgid "Jupyter in Education" +#~ msgstr "" + +#~ msgid "" +#~ "We're actively working on this section" +#~ " of the documentation to improve it" +#~ " for you. Thanks for your patience." +#~ msgstr "" + +#~ msgid "Jupyter in the Enterprise" +#~ msgstr "" + +#~ msgid "" +#~ "Businesses, especially those that started " +#~ "their ‘digital transformation’ journey, are" +#~ " producing ever-increasing volumes of " +#~ "data. Enterprise data science aims to" +#~ " unearth the hidden value of those" +#~ " digital assets, which are typically " +#~ "siloed, uncategorized, and inaccessible to " +#~ "humans." +#~ msgstr "" + +#~ msgid "" +#~ "Jupyter and JupyterHub can play a " +#~ "major role in related initiatives, " +#~ "especially in companies with an " +#~ "established open-source culture. The " +#~ "intent of this page is to provide" +#~ " you with ideas how Jupyter " +#~ "technology can fit into *your* " +#~ "organization's processes and system " +#~ "landscapes, by providing real-world " +#~ "examples and showcases." +#~ msgstr "" + +#~ msgid "Example Use-Cases" +#~ msgstr "" + +#~ msgid "" +#~ "`Beyond Interactive: Notebook Innovation at" +#~ " Netflix `_" +#~ msgstr "" + +#~ msgid "" +#~ "`Part 2: Scheduling Notebooks at Netflix" +#~ " `_" +#~ msgstr "" + +#~ msgid "" +#~ "`PayPal Notebooks: Data science and " +#~ "machine learning at scale, powered by" +#~ " Jupyter `_ (JupyterCon 2018 " +#~ "· `video `_)" +#~ msgstr "" + +#~ msgid "" +#~ "`Bloomberg BQuant platform `_" +#~ msgstr "" + +#~ msgid "" +#~ "`Jupyter & Python in the corporate " +#~ "LAN `_" +#~ msgstr "" + +#~ msgid "" +#~ "`DevOps Intelligence with JupyterHub " +#~ "`_" +#~ msgstr "" + +#~ msgid "" +#~ "We're actively working on this section" +#~ " of the documentation to improve it" +#~ " for you. If you've got a " +#~ "suggestion for a resource that would " +#~ "be helpful, please create an issue " +#~ "or a pull request!" +#~ msgstr "" + +#~ msgid "JupyterHub Narratives" +#~ msgstr "" + +#~ msgid "" +#~ "JupyterHub Narratives explore deployment and" +#~ " scaling of the Jupyter Notebook for" +#~ " a group of users. JupyterHub allows" +#~ " flexibility in configuration and " +#~ "deployment which makes JupyterHub valuable " +#~ "to education, industry research teams, " +#~ "and service providers. In these " +#~ "Narratives, we will look at differences" +#~ " in deployment, deployment advantages, and" +#~ " best practices." +#~ msgstr "" + +#~ msgid "Narrative examples" +#~ msgstr "" + +#~ msgid "A basic JupyterHub deployment" +#~ msgstr "" + +#~ msgid "" +#~ "A `reference deployment of JupyterHub " +#~ "using Docker `_" +#~ msgstr "" + +#~ msgid "" +#~ "Teaching a Course with JupyterHub and" +#~ " nbgrader using a `reference deployment " +#~ "on a single server and Ansible " +#~ "scripts `_ to automate set up" +#~ msgstr "" + +#~ msgid "Teaching a Course with JupyterHub, nbgrader, and containers" +#~ msgstr "" + +#~ msgid "JupyterHub deployments using Containers including Docker" +#~ msgstr "" + +#~ msgid "Notebook Narratives" +#~ msgstr "" + +#~ msgid "" +#~ "The Notebook Narratives explore uses of" +#~ " the Jupyter Notebook in a variety" +#~ " of applications." +#~ msgstr "" + +#~ msgid "Using the Notebook for data exploration" +#~ msgstr "" + +#~ msgid "Using extensions and widgets" +#~ msgstr "" + +#~ msgid "Using nbconvert for code execution and workflow simplification" +#~ msgstr "" + +#~ msgid "Using nbconvert for publishing" +#~ msgstr "" + +#~ msgid "Using multiple language kernels" +#~ msgstr "" + +#~ msgid "Narratives - Building blocks" +#~ msgstr "" + +#~ msgid "" +#~ "This section presents some examples of" +#~ " integrating different projects together. " +#~ "These projects form the foundation of" +#~ " innovative services and provide building" +#~ " blocks for future applications." +#~ msgstr "" + +#~ msgid "A Narrative about Creating Dashboards" +#~ msgstr "" + +#~ msgid "A Narrative about Thebe" +#~ msgstr "" + +#~ msgid "A Narrative about Hydrogen" +#~ msgstr "" + +#~ msgid "Jupyter and Scientific Computing" +#~ msgstr "" + diff --git a/docs/source/locale/en/LC_MESSAGES/reference.po b/docs/source/locale/en/LC_MESSAGES/reference.po new file mode 100644 index 000000000..437580851 --- /dev/null +++ b/docs/source/locale/en/LC_MESSAGES/reference.po @@ -0,0 +1,343 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Jupyter Team, https://jupyter.org +# This file is distributed under the same license as the Jupyter +# Documentation package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Jupyter Documentation 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2021-02-28 00:41+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.9.0\n" + +# 4186a713d84a4c2b806a912fb2becfc9 +#: ../../source/reference/content-reference.rst:2 +#: 5b3aa66e0dbb4098b5d423b65d25ca23 +msgid "Reference" +msgstr "" + +# 47d932f599ef4dc1a3fce9d83d3e7bc4 +#: ../../source/reference/content-reference.rst:13 +#: ../../source/reference/ipython.rst:32 6270e27b56f241899308f40f598f37ec +#: 6a008a8ffd0f480790897011b0c4bd46 +msgid "Resources" +msgstr "" + +# 23b33a4ebf624f9f8ac3989d8fb30bd8 +#: ../../source/reference/content-reference.rst:15 +#: 3ad995d71bbd42bf9e0aaba2367864b7 +msgid ":ref:`genindex`" +msgstr "" + +# fdf2e34429ec43cfa4182e18d95e3546 +#: ../../source/reference/content-reference.rst:16 +#: 4892856e92cc40bda19e0596eaa83521 +msgid ":ref:`search`" +msgstr "" + +#: ../../source/reference/ipython.rst:34 +msgid "IPython website" +msgstr "" + +#: ../../source/reference/ipython.rst:34 +msgid "Gallery of interesting notebooks" +msgstr "" + +#: ../../source/reference/ipython.rst:34 +msgid "IPython documentation" +msgstr "" + +#: ../../source/reference/ipython.rst:2 fe496bef64d8497abae901aa6c4595c1 +msgid "IPython" +msgstr "" + +#: ../../source/reference/ipython.rst:10 9b6ab0cee7eb4ca6bb841dede6dd0ac2 +msgid "Description" +msgstr "" + +#: ../../source/reference/ipython.rst:12 fca9f79c7d02439297ece7c3b643c7de +msgid "IPython provides a rich architecture for interactive computing with:" +msgstr "" + +#: ../../source/reference/ipython.rst:14 65bac16bda6f4c269d28d6e306c65653 +msgid "A powerful interactive shell." +msgstr "" + +#: ../../source/reference/ipython.rst:15 c6d5c759659f4f3980188df11ae9035a +msgid "A kernel for Jupyter." +msgstr "" + +#: ../../source/reference/ipython.rst:16 335453586708437293ca29a2b84e2f45 +msgid "Support for interactive data visualization and use of GUI toolkits." +msgstr "" + +#: ../../source/reference/ipython.rst:17 c882aa225bcc4af18bc64ec39969d538 +msgid "Flexible, embeddable interpreters to load into your own projects." +msgstr "" + +#: ../../source/reference/ipython.rst:18 56f7c7db74304d929737e0deb4d756ae +msgid "Easy to use, high performance tools for parallel computing." +msgstr "" + +#: ../../source/reference/ipython.rst:21 a64db25217fa41e3b84e9c13082b0e6b +msgid "Background" +msgstr "" + +#: ../../source/reference/ipython.rst:23 39f5bc53c29b4ab6bec99434d5470413 +msgid "" +"IPython is a growing project, with increasingly language-agnostic " +"components. IPython 3.x was the last monolithic release of IPython, " +"containing the notebook server, qtconsole, etc. As of IPython 4.0, the " +"language-agnostic parts of the project: the notebook format, message " +"protocol, qtconsole, notebook web application, etc. have moved to new " +"projects under the name Jupyter. IPython itself is focused on interactive" +" Python, part of which is providing a Python kernel for Jupyter." +msgstr "" + +#: ../../source/reference/mimetype.md:1 f93abd175bb942a9b316f67c2c98fa83 +msgid "Custom mimetypes (MIME types)" +msgstr "" + +#: ../../source/reference/mimetype.md:4 ccff8f238ddc425786b9f935ab09d3e8 +msgid "What's a mimetype?" +msgstr "" + +#: ../../source/reference/mimetype.md:6 eb744a32b5a14e07bbd1144c758a27de +msgid "" +"When an internet request and response occurs, a `Content-Type` header is " +"passed. A mimetype, also referred to as MIME type, identifies how the " +"content that is being returned should be handled or used, based on type, " +"by the application and browser. A MIME type is made up of a MIME *group* " +"(i.e. application, image, audio, etc.) and a MIME *subtype*. For example," +" a MIME type is `image/png` where MIME *group* is `image` and *subtype* " +"is `png`." +msgstr "" + +#: ../../source/reference/mimetype.md:13 fd99233bf49f43fe86253a44fd672798 +msgid "" +"As types may contain vendor specific items, a [custom vendor specific " +"MIME type](https://en.wikipedia.org/wiki/Media_type#Vendor_tree), `vnd`, " +"can be used. A vendor specific MIME type will contain `vnd` such as " +"`application/vnd.jupyter.cells`." +msgstr "" + +#: ../../source/reference/mimetype.md:19 f01067e47f8b48c295b8165548254e23 +msgid "Custom mimetypes used in Jupyter and IPython projects" +msgstr "" + +#: ../../source/reference/mimetype.md:21 f89c8ac678e141cfb6d644332b701d27 +msgid "`application/vnd.jupyter`" +msgstr "" + +#: ../../source/reference/mimetype.md:22 6bfb6c494a4d4e48bf45932c9da9b46d +msgid "`application/vnd.jupyter.cells`" +msgstr "" + +#: ../../source/reference/mimetype.md:23 28aba84d21d644e087c16ec1e2b3f930 +msgid "`application/vnd.jupyter.dragindex` used by nbdime" +msgstr "" + +#: ../../source/reference/mimetype.md:24 bcf782a14bfe4badbcc3d9d8575f8238 +msgid "`application/x-ipynb+json` for notebooks" +msgstr "" + +#: ../../source/reference/mimetype.md:25 f0f5b954da644789bfdb381233cfbf87 +msgid "`text/html`" +msgstr "" + +# a04e3276582c4710b3b13a854e8aaa65 +#: ../../source/reference/mimetype.md:26 1538705c7ce147b789289593c776cea1 +msgid "metadata:" +msgstr "" + +#: ../../source/reference/mimetype.md:27 033a51c4ff1247e99214400073471282 +msgid "`isolated: boolean` -- HTML should be rendered inside an `