Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[microprofile-wg] [DISCUSSION] [Straw Poll] MicroProfile -> Jakarta EE - moving repos
On May 28, 2025, at 9:49 AM, Emily Jiang via microprofile-wg <microprofile-wg@xxxxxxxxxxx> wrote:

This is a non-binding straw poll vote-only thread, detailed below.  Anyone can vote. The working group member reps will be counted separately for the corresponding ballot projection. Please respond with +1 (positive), 0 (abstain), or -1 (reject).  Any feedback that you can provide to support your vote will be appreciated.  Please respond by June 4th, 2025.


  • All MicroProfile specification projects that have been released would be moved as they are to Jakarta EE under the pattern of github,com/jakartaee/microprofile-*. Changes could happen afterwards.

Similar feedback as before.  Github repos in Jakarta are required to use a fixed format.  A specification project is given a prefix and must use that in all its repo names.  That is github,com/jakartaee/<spec-project> or github,com/jakartaee/<spec-project>-*.  Some examples:

Messaging Project has:

 - github,com/jakartaee/messaging
 - github,com/jakartaee/messaging-proposals

Security Project has:

 - github,com/jakartaee/security
 - github,com/jakartaee/security-examples
 
Specification projects may have several specification documents and repositories.  For example:

 - github,com/jakartaee/microprofile
 - github,com/jakartaee/microprofile-jwt
 - github,com/jakartaee/microprofile-config
 - github,com/jakartaee/microprofile-opentelemetry

If we want all specifications to remain, at least initially, in a future MicroProfile specification project at Jakarta the repos would be required to be github,com/jakartaee/microprofile-* regardless of what is voted on here.

Given that, is this really a vote that we do keep the specifications, at least initially, in a future MicroProfile specification project vs moving them to other specification projects?


-David

Back to the top