|[ee4j-community] On Complexity and Good Intentions|
Jesse McConnell wisely suggested that I start cross-posting my blog posts here. So here it is.I would also like to apologize for my spotty participation on this list over the past few days. I've actually been traveling on vacation.
We are now about six months into the process of migrating Java EE to the Eclipse Foundation, and I think weâre all learning a lot as we go. I wanted to take a moment and take stock of the scale of this project, its complexity, and where we are.
Java EE is a (roughly) twenty year old technology that is one of the worldâs most successful software platforms. It powers the business critical applications that run our modern world. Millions of developers work with Java EE technologies every day. Billions of users use these systems every day. Throughout Java EEâs twenty year history it has been developed and marketed in a pretty particular way.
At the core of Java EEâs success has been an approach that enabled a multi-vendor ecosystem where enterprises had a choice of compatible implementations from a number of companies.
Together we are changing every single one of those items above. All at once. While retaining the core value of enabling compatible independent implementations in a multi-vendor ecosystem.
This is big and it is complicated.
I honestly believe that no institution other than the Eclipse Foundation could handle this task. We have the people, the skills, the history, and the knowledge of how the Java ecosystem works. The staff at the Eclipse Foundation are highly skilled and community minded professionals. Similarly, the team at Oracle, along with the folks from IBM, Payara, Red Hat, Tomitribe and the EE4J PMC are working hard to move this along. Collectively they are working their butts off to support this transition and to make Jakarta EE the platform and community of choice for the next twenty years.
Overall, I believe weâve been pretty successful at managing the complexity, and working hard to communicate our progress and plans. We havenât always been perfect, as case in point this past week where we had a bit of a kerfuffle on our Jakarta community mailing list. Without going into the details, I would say that the root cause of that was poor communication on my part. I didnât do a good enough job in communicating the plans and dates for selecting the new logo. My bad.
Chris Anisczcyk, a good friend and open source community colleague of mine tweeted some months back that âOpen source would be a lot more fun if everyone assumed good intentions.â With his wise words in mind, I want to say is this: what we are collectively undertaking here is a massive and complex task. Mistakes and miscommunications are going to happen. But letâs all assume good intentions, and build a community based on trust, honesty, and respect.