Giter Club home page Giter Club logo

foundations-and-standards-team-compass's Introduction

Jupyter

Read this in other languages: English, Español, Português, Français

Jupyter metapackage for installation and documents

Documentation structure

This documentation uses the Sphinx 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 and MyST Markdown.

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. 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.

    $ git clone https://github.com/jupyter/jupyter
    $ cd jupyter
  2. Install nox

    $ pip install nox
  3. Run the docs command

    $ 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:

$ 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.

Next, navigate to the /docs directory and create a conda environment:

conda env create -f environment.yml

Activate the environment:

source activate jupyter_docs

Build the docs using Sphinx with the following commands:

make clean
make html

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.

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 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!

foundations-and-standards-team-compass's People

Contributors

ivanov avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

foundations-and-standards-team-compass's Issues

Membership check for joint Foundations and Standards team council

Per jupyter/governance#196 - I've gone ahead and created a joint team compass for Foundations and Standards subproject.

I initially populated the membership from the union of the two previous groups, but wanted to trigger a membership maintenance check

Every six months, one currently active member should open an issue in the team-compass repo asking all currently active team members to reply if they still consider themselves active. If not (or no response is given by a team member), it will be assumed that they have gone inactive. This will help keep the active member list up-to-date.

Remember, an inactive member can return at any time by simply changing their status on the team-compass page.

Please indicate below one way or the other if you would like to remain as an active member of this council, or if you prefer to become inactive at this time.

This poll will remain open until the first week of January, 2024, at which point we will assume an inactive role for anyone not participating.

Also, you can leave a comment here if your affiliation is not correct, I did my best (which is never good enough) ;)

  • @damianavila wishes to …

    • remain active
    • become inactive
  • @kevin-bates wishes to …

    • remain active
    • become inactive
  • @Carreau wishes to …

    • remain active
    • become inactive
  • @SylvainCorlay wishes to …

    • remain active
    • become inactive
  • @jasongrout wishes to …

    • remain active
    • become inactive
  • @ivanov wishes to …

    • remain active
    • become inactive
  • @rgbkrk wishes to …

    • remain active
    • become inactive
  • @minrk wishes to …

    • remain active
    • become inactive
  • @JohanMabille wishes to …

    • remain active
    • become inactive
  • @MSeal wishes to …

    • remain active
    • become inactive
  • @blink1073 wishes to …

    • remain active
    • become inactive
  • @willingc wishes to …

    • remain active
    • become inactive

election of Software Steering Council representative

Dear @jupyter/foundations-and-standards-council ,

I've been serving as the Jupyter Subproject Steering Council (SSC) for this subproject, and I am happy to continue to do so. In the team compass documentation we have, which I adapted from this template , I included a section reflecting the current representative that I copied from the JupyterLab, which reads

Each official subproject in Jupyter gets a single Software Steering Council Representative. JupyterLab’s representative is elected by the members. This representative should be re-elected every year (i.e. in January).

I don't think we ever discussed as a subproject how frequently or when we should re-elect the SSC representative, but it seems like a reasonable course of action, and it also happens to be January.

Per Project Jupyter Software Steering Council section on term length, we are advised that

There is no term length for SSC membership, as each Jupyter Subproject is in charge of selecting its own representative. Projects are encouraged to define their own expectations around SSC membership tenure, to share SSC membership responsibilities among core team members, and to provide mechanisms for healthy rotation that avoid burnout.

Having said all that, I'd like to open up this thread for other nominations for SSC representative for this subproject (self nominations are acceptable, I just did it). I propose we hold the nomination period open for two weeks until January 22nd, and then use the two weeks following that (Jan 22-Feb 5) for the election.

Update: Jan 28th

We are a week behind on starting this election. No one else has stepped forward with a nomination so we are running the election with one candidate.

Please indicate your choice by February 12th.

  • @damianavila votes for…

    • Paul Ivanov
    • none of the above
  • @kevin-bates votes for…

    • Paul Ivanov
    • none of the above
  • @Carreau votes for…

    • Paul Ivanov
    • none of the above
  • @SylvainCorlay votes for…

    • Paul Ivanov
    • none of the above
  • @jasongrout votes for…

    • Paul Ivanov
    • none of the above
  • @ivanov votes for…

    • Paul Ivanov
    • none of the above
  • @rgbkrk votes for…

    • Paul Ivanov
    • none of the above
  • @minrk votes for…

    • Paul Ivanov
    • none of the above
  • @JohanMabille votes for…

    • Paul Ivanov
    • none of the above
  • @blink1073 votes for…

    • Paul Ivanov
    • none of the above
  • @willingc votes for…

    • Paul Ivanov
    • none of the above

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.