We will need a lot of help on this front as well
o Jakarta EE specifications: specification documents and APIs
We have heard from members of the community some suggestions on what they need from the specification, but we can always use more. Get involved in the discussion on Github (https://github.com/eclipse-ee4j/jakartaee-platform/issues).
o Jakarta EE TCK
It’s a goliath, inconvenient, and we want to slowly begin to break it up into separate TCKs for each specification. Not for the very first release of Jakarta EE, but we need to start planning and discussing the approach.
o Compatible Implementations
To make a final version of a specification alive we need specification implementations. Whether the implementation is hosted in Eclipse Foundation or not is not the focus, we need you to implement the specification.
Collateral material related work
While we encourage everyone to participate in specification development, please keep in mind this isn’t limited to coding only. Of equal importance is the need for collateral material related to the specification(s). This includes documentation, presentations, videos, demos, examples, blogs, tech talks, etc. This is the type of content we can circulate through the community and use to educate and spread the news on the new specifications. Presenting the material on the conferences is yet another aspect where you can help out also!