--- canonical: https://chaoss.community/what-happens-to-relicensed-open-source-projects-and-their-forks/ meta-article:modified_time: 2025-01-16T15:56:18+00:00 meta-article:published_time: 2025-01-16T15:56:15+00:00 meta-author: Dawn Foster meta-generator: Powered by WPBakery Page Builder - drag and drop page builder for WordPress. meta-msapplication-TileImage: https://chaoss.community/wp-content/uploads/2019/06/60138530-917bae80-975f-11e9-8cd6-7d48ca5a0ed3.png meta-og:description: Featured image by Ursula Gamez on Unsplash. This post has been republished with permission from the original article on The New Stack: What Happens to Relicensed Open Source Projects and Their... meta-og:image: https://chaoss.community/wp-content/uploads/2025/01/62f2b75e-open-source-forks-1024x576-1.jpg meta-og:image:height: 576 meta-og:image:type: image/jpeg meta-og:image:width: 1024 meta-og:locale: en_US meta-og:site_name: CHAOSS meta-og:title: What Happens to Relicensed Open Source Projects and Their Forks? - CHAOSS meta-og:type: article meta-og:url: https://chaoss.community/what-happens-to-relicensed-open-source-projects-and-their-forks/ meta-robots: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1 meta-twitter:card: summary_large_image meta-twitter:data1: Dawn Foster meta-twitter:data2: 7 minutes meta-twitter:label1: Written by meta-twitter:label2: Est. reading time meta-viewport: width=device-width, initial-scale=1, maximum-scale=1, user-scalable=0 title: What Happens to Relicensed Open Source Projects and Their Forks? - CHAOSS --- [#](#) [](https://chaoss.community) [#searchbox](#searchbox) [#sidewidgetarea](#sidewidgetarea) - [About](https://chaoss.community/about-chaoss/) - [About](https://chaoss.community/about-chaoss/) - [Charter](https://chaoss.community/charter/) - [Code of Conduct](https://chaoss.community/code-of-conduct/) - [Code of Conduct](https://chaoss.community/code-of-conduct/) - [Procedure for Making a Code of Conduct Report](https://chaoss.community/procedure-for-making-a-code-of-conduct-report/) - [Code of Conduct Incident Response Plan](https://chaoss.community/code-of-conduct-incident-response-plan/) - [Data Policies](https://chaoss.community/data-policies/) - [Governance](https://chaoss.community/governance/) - [Governing Board](https://chaoss.community/governing-board/) - [Calendar](https://chaoss.community/chaoss-calendar/) - [Community](https://chaoss.community/kb-chaoss-community/) - [Documentation](https://chaoss.community/kb-chaoss-community/) - [Quick Start for New Contributors](https://chaoss.community/kb-getting-started/) - [CHAOSS Educational Videos](https://chaoss.community/chaoss-education/) - [Working Groups](https://chaoss.community/kb/working-groups/) - [Newsletter](https://github.com/chaoss/community/discussions) - Events - [CHAOSScon-2026-EU](https://chaoss.community/chaosscon-2026-eu/) - Previous CHAOSScons - [CHAOSScon-2025-Africa](https://chaoss.community/chaosscon-africa-2025/) - [CHAOSScon-2025-EU](https://chaoss.community/chaosscon-2025-eu/) - [CHAOSScon Hackathon 2025](https://chaoss.community/chaoss-data-science-hackathon-2025/) - [CHAOSScon-2025-NA](https://chaoss.community/chaosscon-2025-na/) - [CHAOSScon-2024-NA](https://chaoss.community/chaosscon-2024-na/) - [CHAOSScon-2024-EU](https://chaoss.community/chaosscon-2024-eu/) - [CHAOSScon-2023-Africa](https://chaoss.community/chaosscon-2023-africa/) - [CHAOSScon-2023-NA](https://chaoss.community/chaosscon-2023-na/) - [CHAOSScon-2023-EU](https://chaoss.community/chaosscon-2023-eu/) - [CHAOSScon-2022-EU](https://chaoss.community/chaosscon-2022-eu/) - [CHAOSScon-2021-NA](https://chaoss.community/chaosscon-2021-na/) - [CHAOSScon-2020-NA](https://chaoss.community/chaosscon-2020-na/) - [CHAOSScon-2020-EU](https://chaoss.community/chaosscon-2020-eu/) - [CHAOSScon-2019-NA](https://chaoss.community/chaosscon-2019-na/) - [CHAOSScon-2019-EU](https://chaoss.community/chaosscon-2019-eu/) - [CHAOSScon-2018-NA](https://chaoss.community/chaosscon-2018-na/) - [CHAOSScon-2018-EU](https://chaoss.community/chaosscon-2018-eu/) - [Travel Support – ON HOLD](https://chaoss.community/?page_id=3929) - [CHAOSS Blog](https://chaoss.community/blog/) - [CHAOSScast](https://podcast.chaoss.community) - [Upcoming Talks](https://chaoss.community/chaoss-calendar-talks/) - [Metrics](https://chaoss.community/kb-metrics-and-metrics-models/) - [Software](https://chaoss.community/software/) - [Badging](https://badging.chaoss.community/) - [Guides](https://chaoss.community/about-chaoss-practitioner-guides/) - [Practitioner Guide Introduction – Start Here](https://chaoss.community/practitioner-guide-introduction/) - [Assessing Viability](https://chaoss.community/practitioner-guide-viability/) - [Contributor Sustainability](https://chaoss.community/practitioner-guide-contributor-sustainability/) - [Demonstrating Organizational Value](https://chaoss.community/practitioner-guide-demonstrating-org-value/) - [Diverse Leadership](https://chaoss.community/practitioner-guide-diverse-leadership/) - [Organizational Participation](https://chaoss.community/practitioner-guide-organizational-participation/) - [Responsiveness](https://chaoss.community/practitioner-guide-responsiveness/) - [Security](https://chaoss.community/practitioner-guide-security/) - [Sunsetting an Open Source Project](https://chaoss.community/practitioner-guide-sunset/) - - [#searchbox](#searchbox) [Blog Post](https://chaoss.community/category/blog-post/) # What Happens to Relicensed Open Source Projects and Their Forks? By [Dawn Foster](https://chaoss.community/author/dawn-foster/ "Posts by Dawn Foster")January 16, 2025[No Comments](https://chaoss.community/what-happens-to-relicensed-open-source-projects-and-their-forks/#respond) Featured image by Ursula Gamez on Unsplash. This post has been republished with permission from the original article on [The New Stack: What Happens to Relicensed Open Source Projects and Their Forks?](https://thenewstack.io/what-happens-to-relicensed-open-source-projects-and-their-forks/) Many popular [open source projects](https://thenewstack.io/open-source/) are owned and driven by a single company, and in today’s difficult economic climate, those companies are under [increasing pressure](https://redmonk.com/rstephens/2024/08/26/software-licensing-changes-and-their-impact-on-financial-outcomes/) to deliver a strong return on their investments. One response to this pressure has been relicensing popular open source projects to more restrictive licenses in the hopes of generating more revenue. In some cases, relicensing has [resulted in a hard fork](https://thenewstack.io/why-open-source-forking-is-a-hot-button-issue/) of the original project. These relicensing events and their forks can be disruptive to the organizations and individuals using and contributing to affected open source projects. Several companies have relicensed their open source projects in the past few years, so the [CHAOSS project](https://chaoss.community/) decided to look at how an open source project’s [organizational dynamics](https://chaoss.community/practitioner-guide-organizational-participation/) evolve after relicensing, both within the original project and its fork. Our research compares and contrasts data from three case studies of projects that were forked after relicensing: Elasticsearch with fork [OpenSearch](https://thenewstack.io/opensearch-how-the-project-went-from-fork-to-foundation), Redis with fork [Valkey](https://thenewstack.io/navigating-the-path-from-redis-to-valkey), and Terraform with fork [OpenTofu](https://thenewstack.io/how-opentofu-happened-and-whats-next). These relicensed projects and their forks represent three scenarios that shed light on this topic in slightly different ways. The following summarizes what we found when we looked at the data, and you can dive into the details about these six projects in the [paper, presentation and data](https://github.com/chaoss/wg-data-science/tree/main/publications) we shared at the recent [OpenForum Academy Symposium](https://symposium.openforumeurope.org/). ## Elasticsearch and OpenSearch Almost all contributions to the original Elasticsearch project came from employees of the relicensing company (Elastic), and the fork was created by new contributors and owned by a single company ([Amazon](https://aws.amazon.com/?utm_content=inline+mention)). ### Elasticsearch Elasticsearch was an open source project under the Apache 2.0 license until Feb. 3, 2021, when the [project was relicensed](https://www.elastic.co/blog/licensing-change) under the Server Side Public License (SSPL) and the Elastic License. On Aug. 29, 2024, it again became an open source project when Elastic announced it was adding the GNU Affero General Public License (AGPLv3) as an additional licensing option, but there isn’t yet enough data to include this in the analysis. Both before and after the relicense, contributors to the [Elasticsearch repository](https://github.com/elastic/elasticsearch) were mostly Elastic employees; they consistently made over 95% of the lines added to and deleted from Elasticsearch, with almost no participation from contributors outside of Elastic. As a result, the 2021 relicense had little to no impact on contributors, but there was a bigger impact on the users or consumers of Elasticsearch who were forced to decide whether to continue using it, and if so, under which of the two available licenses. ### OpenSearch OpenSearch was forked from Elasticsearch on April 12, 2021, under the Apache 2.0 license, by the Amazon Web Services (AWS) team so that it could continue to offer this service to its customers. OpenSearch was owned by Amazon until September 16, 2024, when it [transferred the project](https://thenewstack.io/aws-transfers-opensearch-to-the-linux-foundation/) to the Linux Foundation. As with Elasticsearch, most contributions to the [OpenSearch repository](https://github.com/opensearch-project/OpenSearch) came from Amazon employees, however, to a lesser extent and with increases in organizational diversity over time. In the first year of the fork, a small number of Amazon employees made 80% of total additions and 91% of total deletions to the code. Only two people who didn’t work for Amazon made 10 or more commits, making up 7% of additions and 4% of deletions. In the final year of the fork under Amazon’s ownership (before the project was moved under the Linux Foundation), its organizational diversity improved, with 63% of additions and 64% of deletions coming from Amazon employees who made 10 or more commits. Six people who didn’t work for Amazon made 10 or more commits, making up 11% of additions and 13% of deletions. In summary, the contributors are mostly from Amazon, but organizational diversity is gradually improving. ## Terraform and OpenTofu Almost all contributions to the relicensed Terraform project came from employees of the company (HashiCorp), and the fork (OpenTofu) was created by new contributors as a foundation project. ### Terraform Terraform was under the open source Mozilla Public License v2.0 (MPL 2.0) until Aug. 10, 2023, when it was relicensed along with HashiCorp’s other open source projects (e.g., Vagrant, Vault) to the Business Source License (BSL). Similar to Elasticsearch, the [Terraform repository](https://github.com/hashicorp/terraform) had very few contributors who weren’t HashiCorp employees. In the year before and the year after relicensing, there were only two contributors to Terraform who were not affiliated with HashiCorp, and they both made a very small number of contributions. Since there were so few contributions from outside of the company, there was no substantial impact on the contributor community from the relicensing event, so the only people affected would likely have been Terraform users. ### OpenTofu OpenTofu was forked from Terraform on Aug. 25, 2023, by a group of users as a Linux Foundation project under the MPL 2.0. These users were starting from scratch with the codebase since no contributors to the [OpenTofu repository](https://github.com/opentofu/opentofu) had previously contributed to Terraform. Contributions came from 31 people at 11 organizations who made five or more contributions to the OpenTofu repository in the first year. The most substantial contributions came from Spacelift, whose employees made over half of the additions and deletions. Employees from Env0 and Scalr have also made a few contributions, so there is some organizational diversity across the project. ## Redis and Valkey The relicensed project (Redis) had significant numbers of contributors who were not employed by the company, and the fork (Valkey) was created by those existing contributors as a foundation project. ### Redis The Redis project was an open source project under the Berkeley Software Distribution 3-clause (BSD-3) until March 20, 2024, when the project was relicensed under the Redis Source Available License (RSALv2) and the SSPLv1. This was contrary to the [2018 Redis blog post](https://redis.io/blog/redis-license-bsd-will-remain-bsd/) stating that the Redis open source project would always remain under the BSD license. The Redis project differs from Elasticsearch and Terraform in the number of contributions to the [Redis repository](https://github.com/redis/redis) from people who were not employees of Redis. In the year leading up to the relicense, when Redis was still open source, there were substantial contributions from employees of other companies: Twice as many non-Redis employees made five or more commits, and about a dozen employees of other companies made almost twice as many commits as Redis employees made. In the six months after the relicense, all of the external contributors from companies (including Amazon, Alibaba, Tencent, Huawei and Ericsson) who contributed over five commits to the Redis project in the year prior to the relicense stopped contributing. In sum, Redis had strong organizational diversity before the relicense, but only Redis employees made significant contributions afterward. ### Valkey [Valkey](https://thenewstack.io/valkey-a-redis-fork-with-a-future/) was forked from Redis 7.2.4 on March 28, 2024, as a Linux Foundation project under the BSD-3 license. The fork was driven by a group of people who previously contributed to Redis with public support from their employers. Within its first six months, the [Valkey repository](https://github.com/valkey-io/valkey) had 29 contributors employed at 10 companies, and 18 of those people previously contributed to Redis. Valkey has a diverse set of contributors from various companies, with Amazon having the most contributors. ## Next Steps This is the first step in a much larger research project underway within the [CHAOSS Data Science Working Group](https://github.com/chaoss/wg-data-science/tree/main/dataset/license-changes/fork-case-study). To date, we’ve only looked at the primary repository and organizational affiliation data for each project, so we’re working toward including more repositories and additional metrics to better understand the project health dynamics within these projects. We also might expand to look at other projects that were forked after being relicensed. Looking at all of these projects together, we see that the forks from relicensed projects tend to have more organizational diversity than the original projects. This is especially true when the forks are created under a neutral foundation, like the Linux Foundation, rather than forked by a single company. It is still too early to understand the ultimate success or failure of these projects — both the original and the fork. The new forks have more organizational diversity, and projects with greater organizational diversity tend to be more sustainable. However, we don’t yet know if this will be true for these projects, especially for companies that continue struggling to meet their investors’ expectations. *CHAOSS will take part in [State of Open Con](https://stateofopencon.com/), a conference covering open source software, open hardware, open data, open standards and AI openness on Feb. 4 and 5 in London. [Alex Williams](https://thenewstack.io/author/alex/), founder and publisher of The New Stack, will moderate a track on the future of open source.* ## Author - [Dawn Foster](https://chaoss.community/author/dawn-foster/ "Dawn Foster") [View all posts](https://chaoss.community/author/dawn-foster/ "View all posts")[mailto:geekygirldawn@gmail.com](mailto:geekygirldawn@gmail.com) Archives Select Month February 2026 December 2025 November 2025 October 2025 September 2025 July 2025 June 2025 February 2025 January 2025 December 2024 November 2024 October 2024 September 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 October 2023 September 2023 August 2023 July 2023 June 2023 May 2023 April 2023 March 2023 February 2023 January 2023 December 2022 November 2022 October 2022 September 2022 August 2022 July 2022 June 2022 May 2022 April 2022 March 2022 February 2022 January 2022 December 2021 November 2021 October 2021 September 2021 August 2021 July 2021 June 2021 May 2021 April 2021 March 2021 February 2021 January 2021 December 2020 November 2020 October 2020 September 2020 August 2020 July 2020 June 2020 May 2020 October 2019 August 2019 July 2019 June 2019 May 2019 March 2019 February 2019 January 2019 November 2018 October 2018 September 2018 July 2018 June 2018 January 2018 August 2017 [#](#) [Share](# "Share this")[Tweet](# "Tweet this")[Share](# "Share this")[Pin](# "Pin this") - [https://twitter.com/chaossproj](https://twitter.com/chaossproj) - [https://www.linkedin.com/company/chaoss?original_referer=](https://www.linkedin.com/company/chaoss?original_referer=) - [https://www.youtube.com/c/CHAOSStube](https://www.youtube.com/c/CHAOSStube) - [https://github.com/chaoss](https://github.com/chaoss) - [https://join.slack.com/t/chaoss-workspace/shared_invite/zt-r65szij9-QajX59hkZUct82b0uACA6g](https://join.slack.com/t/chaoss-workspace/shared_invite/zt-r65szij9-QajX59hkZUct82b0uACA6g) - [https://chaoss.discourse.group/categories](https://chaoss.discourse.group/categories) Copyright ©CHAOSS a Linux Foundation® project. All rights reserved. Linux is a registered trademark of Linus Torvalds. [#](#) - [About](https://chaoss.community/about-chaoss/) - [About](https://chaoss.community/about-chaoss/) - [Charter](https://chaoss.community/charter/) - [Code of Conduct](https://chaoss.community/code-of-conduct/) - [Code of Conduct](https://chaoss.community/code-of-conduct/) - [Procedure for Making a Code of Conduct Report](https://chaoss.community/procedure-for-making-a-code-of-conduct-report/) - [Code of Conduct Incident Response Plan](https://chaoss.community/code-of-conduct-incident-response-plan/) - [Data Policies](https://chaoss.community/data-policies/) - [Governance](https://chaoss.community/governance/) - [Governing Board](https://chaoss.community/governing-board/) - [Calendar](https://chaoss.community/chaoss-calendar/) - [Community](https://chaoss.community/kb-chaoss-community/) - [Documentation](https://chaoss.community/kb-chaoss-community/) - [Quick Start for New Contributors](https://chaoss.community/kb-getting-started/) - [CHAOSS Educational Videos](https://chaoss.community/chaoss-education/) - [Working Groups](https://chaoss.community/kb/working-groups/) - [Newsletter](https://github.com/chaoss/community/discussions) - Events - [CHAOSScon-2026-EU](https://chaoss.community/chaosscon-2026-eu/) - Previous CHAOSScons - [CHAOSScon-2025-Africa](https://chaoss.community/chaosscon-africa-2025/) - [CHAOSScon-2025-EU](https://chaoss.community/chaosscon-2025-eu/) - [CHAOSScon Hackathon 2025](https://chaoss.community/chaoss-data-science-hackathon-2025/) - [CHAOSScon-2025-NA](https://chaoss.community/chaosscon-2025-na/) - [CHAOSScon-2024-NA](https://chaoss.community/chaosscon-2024-na/) - [CHAOSScon-2024-EU](https://chaoss.community/chaosscon-2024-eu/) - [CHAOSScon-2023-Africa](https://chaoss.community/chaosscon-2023-africa/) - [CHAOSScon-2023-NA](https://chaoss.community/chaosscon-2023-na/) - [CHAOSScon-2023-EU](https://chaoss.community/chaosscon-2023-eu/) - [CHAOSScon-2022-EU](https://chaoss.community/chaosscon-2022-eu/) - [CHAOSScon-2021-NA](https://chaoss.community/chaosscon-2021-na/) - [CHAOSScon-2020-NA](https://chaoss.community/chaosscon-2020-na/) - [CHAOSScon-2020-EU](https://chaoss.community/chaosscon-2020-eu/) - [CHAOSScon-2019-NA](https://chaoss.community/chaosscon-2019-na/) - [CHAOSScon-2019-EU](https://chaoss.community/chaosscon-2019-eu/) - [CHAOSScon-2018-NA](https://chaoss.community/chaosscon-2018-na/) - [CHAOSScon-2018-EU](https://chaoss.community/chaosscon-2018-eu/) - [Travel Support – ON HOLD](https://chaoss.community/?page_id=3929) - [CHAOSS Blog](https://chaoss.community/blog/) - [CHAOSScast](https://podcast.chaoss.community) - [Upcoming Talks](https://chaoss.community/chaoss-calendar-talks/) - [Metrics](https://chaoss.community/kb-metrics-and-metrics-models/) - [Software](https://chaoss.community/software/) - [Badging](https://badging.chaoss.community/) - [Guides](https://chaoss.community/about-chaoss-practitioner-guides/) - [Practitioner Guide Introduction – Start Here](https://chaoss.community/practitioner-guide-introduction/) - [Assessing Viability](https://chaoss.community/practitioner-guide-viability/) - [Contributor Sustainability](https://chaoss.community/practitioner-guide-contributor-sustainability/) - [Demonstrating Organizational Value](https://chaoss.community/practitioner-guide-demonstrating-org-value/) - [Diverse Leadership](https://chaoss.community/practitioner-guide-diverse-leadership/) - [Organizational Participation](https://chaoss.community/practitioner-guide-organizational-participation/) - [Responsiveness](https://chaoss.community/practitioner-guide-responsiveness/) - [Security](https://chaoss.community/practitioner-guide-security/) - [Sunsetting an Open Source Project](https://chaoss.community/practitioner-guide-sunset/) - We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent. Cookie SettingsAccept All Manage consent Close #### Privacy Overview This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience. Necessary Necessary Always Enabled Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously. | Cookie | Duration | Description | | --- | --- | --- | | cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". | | cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". | | cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". | | cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. | | cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". | | viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. | Functional Functional Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features. Performance Performance Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors. Analytics Analytics Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc. Advertisement Advertisement Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads. Others Others Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet. SAVE & ACCEPT