Thank you for casting your vote! Below is the summary of
          the votes:
        Option 1: 
        
        Binding votes: 6 (Emily, Ed Burns, John, Amelia, Ryan,
          Emerson)
        Non-binding votes: 3 (Mohamed, Micahel, Luis)
        
        
        Option 2:
        Binding votes:  2 (Kenji, Jan)
        Non-binding votes: 1 (Ed Bratt)
        
        
        Either:
        Non-binding votes: 1 (Reza)
        
        
        I declare the winning vote is Option 1
        The next step is to have the repo
          langchain4j-microprofile-jakarta created under the langchain4j
          org and then populate the repo in due course.
        
        
        Thanks
        Emily
       
      
        
        
          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
          
          
          
          
          
          
          -- 
          You received this message because you are subscribed to the
          Google Groups "MicroProfile" group.
          To unsubscribe from this group and stop receiving emails from
          it, send an email to microprofile+unsubscribe@xxxxxxxxxxxxxxxx.
          To view this discussion visit https://groups.google.com/d/msgid/microprofile/7ef454df-8a5c-42d1-a4ef-03d9eb5a9c02n%40googlegroups.com.