Skip to content

Latest commit

 

History

History
42 lines (32 loc) · 4.01 KB

README.md

File metadata and controls

42 lines (32 loc) · 4.01 KB
Raw

Jupyter Frontends team-compass

A repository for team interaction, syncing, and handling meeting notes across the JupyterLab ecosystem.

Weekly Jupyter Frontends team meeting

Weekly team meetings take place on the Jupyter Zoom room on Wednesdays at 9:00 AM Pacific Time (your time). Minutes will be taken at Hackmd.io. Each meeting's minutes will be added as a comment to an issue in this project.

Weekly Jupyter triage meeting

Weekly triage meetings take place on the Jupyter Zoom room on Tuesdays at 9:00 AM Pacific Time (your time). We look at JupyterLab issues that need triage and Jupyter Notebook issues. Minutes will be taken at Hackmd.io. Each meeting's minutes will be added as a comment to an issue in this project.

Each meeting's minutes will be added as a comment to an issue in this project.

Code of Conduct

As an official Jupyter Project, all communication across all repositories in this organization should adhere to the Project Jupyter Code of Conduct.

Contributing extensions to the JupyterLab GitHub organization

JupyterLab is built to foster a rich ecosystem of plugins. Occasionally developers of an existing JupyterLab extension will want to contribute the extension to Project Jupyter and maintain the extension in the JupyterLab GitHub organization under Project Jupyter governance, which includes:

  • adopting the standard Jupyter license and copyright
  • adhering to Project Jupyter community guidelines
  • being subject to the Project Jupyter BDFL, Steering Council, and governance.

Project Jupyter has official guidelines for adopting new subprojects. More specifically for contributing extension codebases to the JupyterLab GitHub organization, the process for contributing is:

  1. First consider contributing the extension to jupyterlab-contrib
  2. If you think the extension should be considered as a core extension, post an issue on this repo describing your extension and linking to the existing code. The issue should address each point of the criteria for subprojects.
  3. The community reviews the proposal over at least a week. In addition to the criteria listed in the Project Jupyter governance:
    1. a core maintainer will review the existing code
    2. we will also take into account how involved the extension maintainers are in the JupyterLab community
    3. we may recommend that the extension belongs in jupyterlab-contrib
  4. If the JupyterLab maintainers decide to accept the extension into the JupyterLab GitHub organization, the process in the Project Jupyter incorporation guidelines is followed. Additionally:
    1. JupyterLab maintainers and other relevant Jupyter leadership (such as BDFL) are given permission to publish the package.
    2. Extension maintainers are given admin permission on the relevant @jupyterlab/extension npm package. To do this, a user must be added to a team, which then has access to packages (under "Teams"):
      1. Admin logs in to https://www.npmjs.com
      2. Select avatar dropdown and go to "Profile Settings"
      3. Select the jupyterlab org
      4. Go to Members
      5. Click "Invite Members..."
      6. Add the username or email
      7. Click "Invite"
      8. Click "Continue"