-
Notifications
You must be signed in to change notification settings - Fork 187
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Debezium moving to Commonhaus Announcement
- Loading branch information
Showing
2 changed files
with
104 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
--- | ||
layout: post | ||
title: Moving Debezium to a Foundation | ||
date: 2024-11-04 00:00:00 | ||
tags: [ announcement ] | ||
author: ccranfor | ||
--- | ||
|
||
After consulting with the community both inside and outside of Red Hat, we have made the decision to submit a request for the https://github.com/debezium[Debezium project] to join the https://www.commonhaus.org[Commonhaus Foundation]. | ||
|
||
+++<!-- more -->+++ | ||
|
||
Today, we are thrilled to announce that the Debezium project is starting the transition to the Commonhaus Foundation. | ||
Debezium is the leading open-source distributed platform for Change Data Capture (CDC), and has been sponsored exclusively by Red Hat since its inception back in 2015. | ||
The move to CommonHaus aligns with our link:2024-10-03-plan-to-move-debezium-to-foundation[goal to foster a more inclusive, collaborative environment]. | ||
|
||
== Why Move to a Foundation? | ||
|
||
Debezium has seen exceptional growth and adoption since 2015. | ||
Many data streaming providers rely on a variety of foundational components, and for CDC, that most often means Debezium. | ||
We want to continue this momentum, and we believe moving to a foundation helps to facilitate that goal. | ||
|
||
For more details, see our link:2024-10-03-plan-to-move-debezium-to-foundation[goals and reasons] for moving to a foundation. | ||
|
||
== Why Commonhaus? | ||
|
||
Commonhaus stands out because of its innovative governance framework and commitment to project independence. | ||
This benefits the Debezium community and its collaborators by allowing us to continue to provide the same release cadence and commitment to excellence that we have today. | ||
We are thrilled to join other prominent projects at Commonhaus, which includes Hibernate, Jackson, and Quarkus. | ||
|
||
== What's Next? | ||
|
||
We are committed to keeping Debezium the open-source leader in the Change Data Capture (CDC) space. | ||
We remain ever vigilant in our pursuit to innovate, evolve, and deliver the best experience for our vibrant user community. | ||
This transition will enable us to welcome a wider array of contributions from a more diverse cross-section of developers and organizations. | ||
|
||
The move to foundation isn't just about Debezium, it's equally about the community. | ||
If you're organization wishes to ensure that Debezium evolves and grows in a direction that benefits your organization, get involved. | ||
Join us in helping Debezium transition to the Commonhaus Foundation. | ||
|
||
The Commonhaus Foundation is currently bootstrapping, enabling it to be shaped to help you and open-source projects like Debezium have a place to call home. | ||
For questions about this move, please refer to our link:/foundation/faq[dedicated FAQ] or reach out through our usual channels. | ||
|
||
On behalf of the Debezium team. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
--- | ||
layout: page-menu | ||
title: Debezium at Commonhaus FAQ | ||
permalink: /foundation/faq/ | ||
--- | ||
:linkattrs: | ||
:icons: font | ||
:source-highlighter: highlight.js | ||
|
||
=== Why move to a foundation? | ||
|
||
Enable us to welcome more contributions from a diverse range of developers and organisations. | ||
|
||
=== Which Debezium projects as moving to a foundation? | ||
|
||
All projects under the https://github.com/debezium[Debezium GitHub] organization. | ||
|
||
=== What is Commonhaus? | ||
|
||
See https://www.commonhaus.org[https://www.commonhaus.org]. | ||
|
||
=== Why Commonhaus? | ||
|
||
The main reason for choosing Commonhaus over another foundation was its governance framework, which emphasises project self-governance. | ||
See, in particular, its guiding principles. | ||
|
||
=== Why not move to any other foundation? | ||
|
||
See Commonhaus’ own https://www.commonhaus.org/about/faq.html[FAQ]. | ||
|
||
=== What does the move consist of exactly? | ||
|
||
The move consists of donating the Debezium-related intellectual property owned by Red Hat. | ||
The donated intellectual property includes in particular: | ||
|
||
* Debezium trademark | ||
* All related domain names | ||
|
||
This does not include copyright, since Red Hat does not have exclusive claims to copyright on the Debezium code. | ||
|
||
=== Is Red Hat reducing the funding for Debezium development? | ||
|
||
No, not all. | ||
|
||
=== How is Red Hat's involvement in Debezium changing? | ||
|
||
Red Hat's involvement in Debezium remains unchanged and as committed as ever. | ||
|
||
The Debezium team is expecting increased collaboration between Red Hat and other organizations, which may require setting time aside to onboard new contributors and collaborators. | ||
|
||
=== What is changing in practice for contributors to the Debezium project? | ||
|
||
Commonhaus requires Debezium to adhere to its https://www.commonhaus.org/policies/[policies], including in particular its https://www.commonhaus.org/policies/ip-policy/[intellectual property policy], and https://www.commonhaus.org/policies/trademark-policy/[trademark policy]. | ||
|
||
This is great news for you all, as it legally binds the project to remain open-source forever. | ||
Commonhaus also requires having a code of conduct, and provides a recommended one, but each project can freely customize the details as needed. | ||
|
||
Debezium contributors can opt to become Commonhaus Members; this is not a requirement to participate in the Debezium project, but is a requirement to help define Commonhaus. | ||
|
||
The Debezium project's core contributors, internal governance and processes remain the same. |