Key open source communities are those that align with 2i2c’s values and that are central to 2i2c’s mission. They build technology that is essential for the infrastructure that 2i2c offers.
Ways to support key communities¶
While we try to make upstream contributions wherever we can, we make extra effort to support key communities. Here are a few examples of this:
Seek leadership positions within key communities and help guide their strategy and policy.
Perform ongoing maintenance as part of our 2i2c time (not nights and weekends).
Put extra time into doing community work and support, not just code.
Put extra time into reviewing pull requests from others, not just our own.
Seek funding that we can use to make improvements and give support (see Funding for open source)
Track our efforts in these communities and include them in our self-assessments about impact.
List of key communities¶
Currently, the following communities are considered “key communities” for 2i2c.[1]
| Title |
|---|
| @binder-examples |
| @cryptnono |
| @dask |
| @executablebooks |
| @jupyter |
| @jupyter-server |
| @jupyterhub |
| @jupyterlab |
| @pangeo-data |
| @pydata |
| @rocker-org |
This is pulled directly from the source of truth TOML file. Edit that file to update the list.