The nomination period for the Jakarta EE Working group elections has closed. Now, it is up to the candidates to convince you why they should get YOUR vote. To help with this, I have offered each candidate a short Studio Jakarta EE interview.
Next week, I will be conducting interviews with more of the candidates. So, tune in to Studio Jakarta EE to learn more about the candidates before casting your vote!
I know, it’s Monday and I am one day late…I usually publish these Hashtags on Sundays. My excuse this time is that it was such beautiful weather and I was busy preparing my boat for the season. Totally slipped my mind, but here we go!
Have you nominated yourself to the Jakarta EE Elections yet? If you haven’t, there is still time. The nomination period ends on April 24, 2020.
Serving on one of the Jakarta EE committees is an excellent opportunity to increase your knowledge about governance in general and Jakarta EE specifically. It is the best way to influence the direction forward and be a part of shaping the future of Jakarta EE. Who knows, it may even boost your career!
This is the third Jakarta EE Developer Survey. The survey last year had more than 1,700 responses from individuals around the World. Let’s beat that number this year! It provides valuable insight into the state of the community to better understand the top priorities for future Jakarta EE releases.
It has been an interesting week in the Jakarta EE community. The work with Jakarta EE 9 makes progress, but we still need any help we can get from the community. Make sure you tune in to the Jakarta EE Update Call on Wednesday for more information about how you can help!
The ongoing thread on the Jakarta EE Community mailing list regarding creating a fork of MicroProfile Config as a basis for a Jakarta Config specification goes on. Please make sure to chime in with your opinion there.
I think this discussion shows that it is important that Jakarta EE states how the technical alignment with MicroProfile (as well as other potential candidates for standardization) should be from a Jakarta EE standpoint. The MicroProfile community selected a Pull approach, which in plain words means that they will not initiate any standardization efforts with Jakarta EE, or anywhere else. The Jakarta EE working group should come up with a similar strategy, or statement, for how the technical alignment should be from the Jakarta EE side in order to end this confusion.
There is a very interesting discussion ongoing on the Jakarta EE Community mailing list about forking Eclipse MicroProfile as Jakarta Configuration. While the discussion on the mailing list initially is about the MicroProfile Config specification specifically, it also raises the question of how the strategy of Jakarta EE should be for technical alignment with Eclipse MicroProfile.
A couple of weeks ago, there was a vote in the Eclipse MicroProfile community about how the technical alignment with downstream consumers. Two approaches, the Pull Model and the Push Model were voted on. The Pull Model got the most votes, and thus was selected as the strategy for technical alignment.
In parallel, the discussions regarding the creation of a MicroProfile working group have been going on since October last year. Several suggestions have been explored, including separate working groups, a combined working group with Jakarta EE, or a combination of the two with two working groups linked together with an umbrella working group.
Whether there is a single working group, a group of working groups under an umbrella working group, or just independent working groups is actually not relevant to this discussion. The technical alignment will still be the same. The MicroProfile community has chosen the Pull Model, and this is something Jakarta EE needs to figure out how to relate to.
In my mind, it is pretty simple. Jakarta EE should create a fork of the specifications that makes sense to make a part of the Jakarta EE Platform. There are several reasons for this. I have touched upon a couple of them here.
MicroProfile wants to move fast and break things, while Jakarta EE wants to maintain a certain level of backward compatibility. By creating a fork, Jakarta EE won’t have to address this concern since it will then control the life cycle of its specifications.
Java EE, and by succession Jakarta EE, has always been a very cohesive platform. A central piece like configuration will be used throughout the entire platform and it only makes sense that it is in the same namespace as the rest of the platform.
By maintaining a fork of the specification, Jakarta EE is free to make modifications that are relevant for Jakarta EE, but maybe wouldn’t be relevant for MicroProfile.
As I pointed out in Hashtag Jakarta EE #11, the headache of diverging tines of the fork lands on the vendors that support both Jakarta EE and MicroProfile in the same product. Therefore, it is kind of interesting to see that the vendors that were most in favor of the Pull approach that are all shipping products that are both Jakarta EE and MicroProfile compliant. So, clearly, they must have thought about this and have a solution in place.
EclipseCon 2020 is added to the long list of events that transforms into a virtual event this year. For those with an eye for detail will notice that the conference has changed the name from EclipseCon Europe to simply EclipseCon.
The name change has nothing to do with the decision to go virtual this year. EclipseCon is a global event and has been so for years, so removing the Europe part of the name just makes sense.
The seemingly never-ending story of creating a working group for Eclipse MicroProfile took an interesting turn at the end of this week. In an email to the Microprofile mailing list, Mike Milinkovich tasked the MicroProfile community to come up with a proposal for a MicroProfile Working Group Charter. This means that the efforts of creating a common working group or an Umbrella working group structure in relation to Jakarta EE have been put on hold.
I think it is a good thing that the discussions now can be around how to get the MicroProfile Working Group up and running so we can all focus our energy on technical challenges rather than governance.
In this snippet, I go through the new navigation elements added to the specifications part of the Jakarta EE website. Specifically, links to the Eclipse Project pages and an external webpage if that exists.
A trivia at the end. Which year did we get the shirt I am wearing in the video at JavaOne? Tweet me the reply if you remember it. A photo of yourself in the same shirt is a bonus! No prices other than fame and glory 🙂
As I wrote in my latest #Hashtag Jakarta EE. I just started a new YouTube channel called Studio Jakarta EE. Since I totally forgot to introduce myself in the first video, I uploaded a new one today to correct that. This short video also features Duke as my distinguished guest.
I hope you enjoy this effort as it is a completely new experience for me. These first recordings are probably not up for any Academy Awards yet…
But if you bear with me and my silly stuff now in the beginning as I walk my first steps as Youtuber, my promise to You is that the videos will be better and maybe even contain some relevant information in the near future. Stay tuned!