Show some love ❤️ to the Spring AI project

[piotrooo]

General

@markpollack and @tzolov, a few words for you first. It's fantastic that this project has come to life! A great deal of the credit goes to both of you. There's no doubt about that. Everything we do can now be fully based on Spring, from simple HTTP requests to handling data returned from AI. It's truly great that we have another gem in the Spring ecosystem!

I know that every major project raises from chaos. And this time, it's no coincidence that such a good project has come about in this way, and in the future, I think it will be even better! However, all Spring projects, such as Spring Framework, Spring Boot, or Spring Security, are characterized by being really well-organized and managed. I'm mainly referring to the management of issues and pull requests at the labels level.

In the spring-ai project, this is somewhat lacking. Soon, we'll probably be celebrating version 1.0.0 GA. Therefore, maybe now is a good time to think about what we could do to improve the management of this project.

Ideas

I have gathered some facts and information, and I also have a few ideas. Allow me to share them with you.

Currently, the following labels are in use:

Labels

• agents
• AOT/Native
• azure
• Bedrock
• bug
• chat client
• Chat Memory
• CI/CD
• client timeouts
• cross platform
• design
• docker-compose
• documentation
• duplicate
• embedding
• enhancement
• ETL
• Evaluation
• function calling
• Getting Started Experience
• good first issue
• help wanted
• huggingface
• image models
• invalid
• Malicious/Attack
• messages
• metadata filters
• milvus
• model client
• modularity
• Observability
• ollama
• onxx
• openai
• pgvector
• qdrant
• question
• RAG
• redis
• testcontainers
• testing
• to discuss
• vector store
• vertex
• wontfix

As you can see, there are many inconsistencies in the naming. What is my proposal?

Labels status:

In-use

• status: declined replaces wontfix
• status: duplicate replaces duplicate
• status: first-timers-only replaces good first issue
• status: ideal-for-contribution replaces help wanted
• status: invalid replaces invalid
• status: pending-design-work replaces design

New

• status: feedback-provided
• status: waiting-for-feedback

Labels type:

In-use

• type: bug replaces bug
• type: documentation replaces documentation
• type: enhancement replaces enhancement
• type: question replaces question

Labels for:

• for: team-attention replaces to discuss

Labels theme:

In-use

• theme: agents replaces agents
• theme: aot replaces AOT/Native
• theme: chat-client replaces chat client
• theme: cross-platform replaces cross platform
• theme: embedding replaces embedding
• theme: etl replaces ETL
• theme: evaluation replaces Evaluation
• theme: function-calling replaces function calling
• theme: image-models replaces image models
• theme: model replaces model client zawsze w połączeniu z label model:
• theme: multimodality replaces multimodality
• theme: observability replaces Observability
• theme: rag replaces RAG
• theme: vector-store replaces vector store

Labels model:

These labels indicate that a given issue or pull request is related to a specific model.

In-use

• model: azure replaces azure
• model: bedrock replaces Bedrock
• model: huggingface replaces huggingface
• model: ollama replaces ollama
• model: onxx replaces onxx
• model: openai replaces openai
• model: vertex replaces vertex

Of course, any new issue or pull request related to models not listed here should result in adding a new label.

Labels vector-store:

These labels indicate that a given issue or pull request is related to a specific model.

In-use

• vector-store: milvus replaces milvus
• vector-store: pgvector replaces pgvector
• vector-store: qdrant replaces qdrant
• vector-store: redis replaces redis

Of course, any new issue or pull request related to vector stores not listed here should result in adding a new label.

To discuss/remove

• Chat Memory do we really need this, if yes, how it should be named
• CI/CD do we really need this, if yes, how it should be named
• client timeouts to delete
• docker-compose to delete
• Getting Started Experience to delete
• Malicious/Attack to delete
• messages to delete, but I'm not sure what does exactly mean
• metadata filters to delete, but I'm not sure what does exactly mean
• testcontainers to delete
• testing do we really need this, if yes, how it should be named

---

I believe these changes will make this project even better!

I invite everyone to join the discussion.