Merge pull request #12 from jupyterlab/saulshanabrook-patch-1

Document process for adding new jupyterlab repos

Author: saulshanabrook

README.md

@@ -1,8 +1,35 @@
 # team-compass
+
 A repository for team interaction, syncing, and handling meeting notes across the JupyterLab ecosystem.
 
 ## Weekly Developer Meeting
 Weekly Developer Meetings take place on [zoom](https://zoom.us/my/jovyan). Minutes will be taken at [Hackmd.io](https://hackmd.io/Uscrk0N1RhCtX-p6ZHUuWQ). Each week an issue will be opened with that week's meeting minutes and the issue from the previous week will be closed. 
 
 ## 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.](https://github.com/jupyter/governance/blob/master/conduct/code_of_conduct.md)
+
+## 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](https://github.com/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](https://github.com/jupyter/governance/blob/master/newsubprojects.md) for adopting new subprojects. More specifically for contributing extension codebases to the JupyterLab GitHub organization, the process for contributing is:
+
+1. 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](https://github.com/jupyter/governance/blob/master/newsubprojects.md#criteria-for-official-subprojects).
+2. 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. If the JupyterLab maintainers decide to accept the extension into the JupyterLab GitHub organization, the process in the Project Jupyter [incorporation guidelines](https://github.com/jupyter/governance/blob/master/newsubprojects.md#incorporation) 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"