Intellectual property#

This page describes our approach to intellectual property with any assets we interact with regarding open source code, text, images, and upstream communities.1

Software licenses#

In 2i2c repositories#

Our fiscal sponsor holds the rights to any code that is generated in the 2i2c repository (@2i2c-org).

Any code that we control should be released under an OSI approved license with permissive restrictions. For example, the Apache License 2.0 or the BSD-3 Clause “New” or “Revised” license. By default, we use whatever license is most prevalent in the community where we operate. For example, in the scientific python community, that is the BSD 3-Clause license.

In upstream repositories#

Upstream communities own the right to any code or text that is contributed to a repository in an upstream organization (e.g., @jupyterhub). 2i2c gives up its right to this code - it is stewarded by the legal entity that owns the upstream repository.2 These communities dictate the license that these contributions are released under (generally speaking, it is a permissive license like the BSD 3-Clause license)

Text and non-trademark design assets#

Our fiscal sponsor holds the rights to any written assets and non-trademark design assets (e.g. diagrams made for blog posts).

We release them under the Creative Commons BY 4.0 (CC-BY 4.0) license. In some cases we may share material with a Share Alike clause (CC-BY SA) but generally do not release material with an Non-commercial (NC) or No Derivatives (ND) license.

Trademarks and logos#

Our fiscal sponsor holds the rights to any trademarks or logos that are created as part of a 2i2c effort. We do not license these for re-use.


1

See the CS&S briefing on Intellectual Property for an overview of some considerations here.

2

In Jupyter’s case, this is the fiscal sponsor NumFocus.