-
Notifications
You must be signed in to change notification settings - Fork 27
Blog post about Red Hat Middleware move to IBM #211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,61 @@ | ||||||
= About Red Hat and IBM | ||||||
Yoann Rodière | ||||||
:awestruct-tags: ["Red Hat", "IBM", "Community", "Commonhaus"] | ||||||
:awestruct-layout: blog-post | ||||||
|
||||||
A few weeks ago, Red Hat announced its Middleware division would move to IBM. | ||||||
As a change of this nature is likely to raise a few questions, I felt it would be best to provide some information -- even though the team as a whole is not yet ready to provide an official statement. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
== What's happening? | ||||||
|
||||||
Red Hat employees from the Middleware division are being transferred to an equivalent division at IBM, | ||||||
with the initial target date set to May 2025. | ||||||
You can find more information in https://www.redhat.com/en/blog/evolving-our-middleware-strategy[the official announcement]. | ||||||
|
||||||
These employees work for the most part on open-source Java technologies, | ||||||
for example Quarkus, whose team https://quarkus.io/blog/quarkus-redhat-strategy/[also commented on the move]. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There seems to be other blogs out there already. Maybe I should link to WildFly's as well? https://www.wildfly.org/news/2025/03/05/WildFly_and_Red_Hat_strategy/ |
||||||
|
||||||
When it comes to Hibernate, this affects several of our most active contributors, | ||||||
and in particular all project leaders. | ||||||
|
||||||
== What's the impact on Hibernate users and contributors? | ||||||
|
||||||
The displayed intent of the move is to keep funding open-source development, | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
which implies no negative impact on the open-source software community. | ||||||
Early internal communication I received was consistent with this, | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
highlighting open-source development as a strategic investment. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
As a reminder, I (in part, but mostly the rest of the Hibernate team) have been working a lot on making our projects _more_ open in the past few months: | ||||||
the re-licensing of https://in.relation.to/2025/03/14/orm-asl/[Hibernate ORM] | ||||||
and https://in.relation.to/2024/06/10/hibernate-search-7-2-0-Alpha2/#switch-project-license-to-apache-license-2-0[Hibernate Search] | ||||||
from LGPL to ASL2 is now complete, | ||||||
and the https://in.relation.to/2024/04/09/hibernate-to-commonhaus/[move of Hibernate to the Commonhaus Foundation] is well under way, | ||||||
with the final steps being worked on as we speak. | ||||||
|
||||||
Also, yes, if you can believe it, these initiatives are a happy coincidence: | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
the Hibernate team started them more than a year ago, | ||||||
while we were made aware of the move to IBM almost at the same time as everybody else, a few weeks ago. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
== Some quotes from Hibernate team members | ||||||
|
||||||
I took the liberty to collect quotes from fellow Hibernate team members. | ||||||
Note this reflects each person's opinion, and is not meant as an official statement from the whole team. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
[quote,Steve Ebersole, Hibernate ORM project lead] | ||||||
____ | ||||||
As I see it, the move from Red Hat to IBM is a simple matter of employment. Nothing will change in my day-to-day. Consider too that IBM acquired Red Hat nearly 6 years ago and there was hand-wringing even at that time about the future of Hibernate projects from some in the community. Yet here we are and the sky has not fallen. | ||||||
|
||||||
The take away, for me at least, is that Red Hat and now IBM have been very good stewards of our projects. The upcoming https://in.relation.to/2024/04/09/hibernate-to-commonhaus/[move to Commonhaus], I think, mitigates these fears even more - ensuring that Hibernate remains free, open-source and actively developed as community projects. | ||||||
____ | ||||||
|
||||||
[quote,Marko Bekhta, Hibernate Validator and Hibernate Search project lead] | ||||||
____ | ||||||
I contributed to Hibernate projects long before joining Red Hat; I am contributing to and maintaining Hibernate projects while I am at Red Hat. I don't see a reason not to continue doing so in the foreseeable future: I'll continue contributing to the Hibernate family of projects. Particularly because the projects we work on provide meaningful and practical solutions for problems software engineers encounter in their day-to-day work. As long as there's data -- you need to validate it, persist it, and search it. | ||||||
|
||||||
We have a great community and a lot of contributors beyond the core team. The colour of the logo won't change any of that. | ||||||
____ | ||||||
|
||||||
== Comments? | ||||||
|
||||||
As usual, the https://hibernate.org/community/[Community page] provides all information necessary to reach out to the Hibernate team, | ||||||
be it to ask questions, report issues, or start contributing! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.