Jakarta EE Town Hall Part 2 - Community Q&A
summary
Community updates state Jakarta EE now focuses on open specs, a faster release cadence with multiple releases a year, and a marketing plan that is increasing blog and webinar output; the spec process favors tracked text (recommendation: asciidoc in a git repo rather than Google Docs) and preserving TCK-based portability; MicroProfile features (config, metrics, tracing, rest client) are already appearing in runtimes like Open Liberty, WildFly and Payara and a developer onboarding tool (StartMicroProfile.io wizard) and consolidated samples are being built.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:28Marketing strategies
- 6:10Community initiatives
- 8:17Specification process
- 10:33JakartaOne insights
- 13:55Jakarta EE vs MicroProfile
- 20:22Technical vision
- 23:43Roles of PMC, committers, and working groups
- 28:24Marketing resources
- 30:09MicroProfile integration
- 36:51Portability concerns
- 41:41Developer mindshare
- 46:26Developer experience
- 51:50Closing remarks
related talks
15mJakarta EE: Why and how to get involved in Open Source Software?
42mWhat's Going on With Jakarta EE
36mMicroProfile and Jakarta EE Panel
43mJakarta EE 9 and Beyond
51mJakarta EE 10 and Beyond
02h 38mJakarta in 2023, What Is the Situation?
48mA Developer's Guide to #JakartaEE 11
40mJakarta EE and Cloud Native Projects at Eclipse Foundation