Commonhaus and Jakarta EE certification

[marko-bekhta]

Hey 🙂 👋🏻 ,

With some of the Jakarta EE specification implementations now moved to Commonhaus I'm trying to figure out how the certification process on the Jakarta EE side should look now:

• https://jakarta.ee/committees/specification/tckprocess/#_filing_a_certification_request

Here are a couple of examples from the previous requests:

• Compatibility certification request for Hibernate Validator for Validation 3.1.0 jakartaee/validation-spec#281
• Compatibility certification request for Hibernate 7.0.0.Alpha2 jakartaee/persistence#623

You can see that there's an organization mentioned in there and the acknowledgement of the EFTL terms by that organization. So with that in mind, on behalf of which org should I (or others) be filing the certification request now?

CC: @yrodiere, @bstansberry (assuming there would be a similar need for WildFly?)

[yrodiere]

cc @starksm64 , @tomjenkinson who might tell us more about Jakarta EE certifications :)

As far as I understand it, the organization's name on the certification request is just to ensure that people submitting requests use the TCK responsibly/legally. Which is a bit late if you ask me, but nevertheless: as the steward of our projects and IP owner is Commonhaus, and project leads are committing to only act in compliance with Commonhaus's rules, it stands to reason Commonhaus would be the organization that needs to agree with the EFTL.

So +1 to put Commonhaus in the certification request, and +1 to agree with the EFTL -- it's not like it's a new thing. I suspect we don't specifically need to ask permission: it's about agreeing with the license as a user, not as a contributor. But if others think it's necessary, we can always formalize the agreement with a vote.

[ebullient]

yes. Commonhaus would be the organization/legal entity.

[starksm64]

I believe it will need to be signed as either Red Hat or IBM as a requirement is that entity making the compatibility claim be a member of the Jakarta EE WG. This fragment from the [Jakarta EE Compatibility Trademark License Agreement] (https://app.hellosign.com/s/Aoi0Sx4E) speaks to that:

We will probably need a consult with the IBM/Red Hat legal to determine what is desired.

[starksm64]

The alternative is to get Commonhaus accepted as a guest member of the WG.

[yrodiere]

Would you knw what is the status of the Apache Foundation in this group? I know Apache BVal used to be a certified implementation of Bean Validation back in Java EE times... I don't know if they continued with Jakarta.

[starksm64]

Apache still is a guest member, along with a few JUGs:
https://jakarta.ee/membership/members