Microsoft votes 0 (abstains).
We believe either option is fine as long as both the terms Jakarta EE and MicroProfile are in the repository name. This reflects our customer centric design objective that this CDI extension should work in any environment where either Jakarta EE, MicroProfile, or both technology sets are present. Indeed we will strive to make this extension work in a Java SE environment using just CDI as well.
We highly appreciate the effort with regards to properly following process.
From: microprofile-wg <microprofile-wg-bounces@xxxxxxxxxxx> on behalf of Jan Westerkamp via microprofile-wg <microprofile-wg@xxxxxxxxxxx>
Sent: Wednesday, February 26, 2025 8:08 AM
To: microprofile-wg@xxxxxxxxxxx <microprofile-wg@xxxxxxxxxxx>
Cc: Jan Westerkamp <jan.westerkamp@xxxxxxx>
Subject: Re: [microprofile-wg] Fwd: Vote on the repo name created under langchin4j
Option 2 (iJUG)
Why:
The order reflects the technical dependency between Jakarta EE
(Core Profile) and MicroProfile in that order.
Best,
Jan
PS: When doing official communication like voting, the use of an
official EF WG communication channel must be used, as documented
in the EF WG Operations Guide - so this should have been done on
this mailing list instead of a Google Group (where we also lost
some thread history recently).
Am 25.02.25 um 20:22 schrieb Emily
Jiang via microprofile-wg:
Please vote asap.
Further to the conversation regarding where the repo
smallrye-lm
should be landed, based on
this
thread, the consensus was to contribute this repo to
langchain4j. The
current prototype of smallrye-llm has the integration of
MicroProfile Config, Fault Tolerance, Telemetry and Jakarta
CDI.
As for the new repo name, even though the smallrye-llm was
started from MP AI discussions as a prototype, it is important
to have Jakarta on the repo name to indicate MicroProfile and
Jakarta together work nicely with the langchain4j framework. I
checked with Eclipse Foundation EMO regarding the usage of
MicroProifle and Jakarta in other github org. Eclipse
Foundation permits us to use MicroProfile and Jakarta part of
the repo name with the requirement of putting an R-in-a-circle
on the first use of Jakarta or MicroProfile in text, along
with a trademark attribution.
Currently there are 2 options on the table for the repo
names:
- Option 1: langchain4j-microprofile-jakarta (a
recognition of the original work from MicroProfile and
most integrations are for MP specs)
- Option 2: langcahin4j-jakarta-microprofile
(demonstrating jakarta CDI is heavily used)
Both options have some merits. In order to settle on one,
we need MP committers to decide with your votes.
Voting runs from 18th Feb and ends on 25th Feb 2025. Only
MicroProfile committers have binding votes. The non
MicroProfile committers are welcome to vote but will counted
as non-binding votes.
Thanks
Emily