Apply comments

content/blog/2025/binder-singlenode/index.md

@@ -0,0 +1 @@
+

content/blog/2025/community-ownership/index.md

@@ -12,7 +12,7 @@ draft: false
 
 In this post, we're sharing our [Commitment to Open Technology](../../../open-technology/index.md). It is focused on _software licenses_ for reasons we'll describe below. We hope that it clarifies what kind of licenses we'll use, and assures our communities that we will not change our stance towards open source technology in the future. This ensures 2i2c's long-term commitment to community-owned and open infrastructure.
 
-Being a platform and service provider gives us a lot of power, and also introduces a potential source of _lock-in_ for our member communities. While 2i2c's organizational mission and culture is strongly aligned with open infrastructure, we believe it's important to encode commitments like these in a formal way to provide both transparency and accountability to our member communities.
+Being a platform and service provider gives us a lot of power, and also introduces a potential source of _lock-in_ for our member communities. While 2i2c's organizational mission and culture are strongly aligned with open infrastructure, we believe it's important to encode commitments like these in a formal way to provide both transparency and accountability to our member communities.
 
 ## Our commitment to open technology
 
@@ -42,7 +42,7 @@ In plain language, here's what this commitment means:
 Many organizations claim to be committed to open infrastructure, while retaining the ability to _change this commitment in the future when it is in their interests_. A classic example of this is a "bait and switch" that looks something like this:
 
 1. A company releases software under an open source license and professes to build an open source community around it.
-2. However, they retain the rights to all of the code in their projects through a [Contributor License Agreement](https://en.wikipedia.org/wiki/Contributor_License_Agreement) (CLA). This generally means that contributors must _give up the rights to their contribution_ in order to make that contribution.
+2. However, they retain the rights to all of the code in their projects through a [Contributor License Agreement](https://en.wikipedia.org/wiki/Contributor_License_Agreement) (CLA) with copyright assignment. This generally means that contributors must _give up the rights to their contribution_ in order to make that contribution.
 3. Once their product has gained traction and it is in their interests, the company can _change the license_ to whatever they wish (even one that is not open source) because they retain the rights to all contributions in the codebase.
 4. They then leverage this new position as owners of a proprietary project to extract business value or grow their position in a market.
 
@@ -52,22 +52,23 @@ Think this sounds unlikely? Here are just a few recent examples of companies tha
 - [Hashicorp / Terraform](https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license)
 - [Elastic Search](https://en.wikipedia.org/wiki/Elasticsearch#Licensing_changes)
 
-We want to ensure our commities that 2i2c is not headed down this path, in order to give them confidence in treating us as a long-term service partner.
+We want to ensure our communities that 2i2c is not headed down this path, in order to give them confidence in treating us as a long-term service partner.
 
 ## What does this change about 2i2c's open source commitment?
 
-In short: nothing. These are already the principles that 2i2c was committed to from its inception. However, we wanted to make these commitments more formally in order to give ourselves more accountability to sticking with them, and to provide more transparency for our community members and stakeholders.
+In short: nothing. These are already the principles that 2i2c was committed to from its inception, and already implied via our [Right to Replicate](../../../right-to-replicate/). However, we wanted to make these commitments more formally in order to give ourselves more accountability to sticking with them, and to provide more transparency for our community members and stakeholders.
 
 ## Who is this for?
 
 We imagine three audiences for this policy:
 
 1. **2i2c present and future staff** who want to ensure that their organization remains committed to our open principles. This document provides a sense of psychological safety to have bold discussions about structuring our approach to open source.
-2. **Member communities and 2i2c stakeholders** who _need_ to have a better understanding of the guarantees that we provide in order to trust 2i2c as a service developer and provider. This is similar to the effect our [Right to Replicate](/right-to-replicate) has.
+2. **Member communities and 2i2c stakeholders** who need to have an understanding of the guarantees that we provide in order to trust 2i2c as a service developer and provider. This is similar to the effect our [Right to Replicate](/right-to-replicate) has.
+3. **Open source communities** who need to understand our long-term commitment and goals around open technology in order to trust as a peer and collaborator within open source communities.
 
 ## We'd love feedback
 
-We hope that these ideas both clarify our intent and the reason that we think it's important. We'd love feedback about early refinements to these principles in order to make them more effective, as well as ways that we can provide more community oversight and participation in evolving these policies moving forward. If you have any thoughts to share, please send us feedback to `[hello@2i2c.org](mailto:hello@2i2c.org)`.
+We hope that these ideas both clarify our intent and the reason that we think it's important. We'd love feedback about early refinements to these principles in order to make them more effective, as well as ways that we can provide more community oversight and participation in evolving these policies moving forward. If you have any thoughts to share, please open an issue at [2i2c-org/compass](https://github.com/2i2c-org/team-compass/issues/new).
 
 ---