- Issue created by @marcus_johansson
- 🇦🇺Australia kim.pepper 🏄♂️🇦🇺Sydney, Australia
marcus_johansson → credited kim.pepper → .
- 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
Switching to the correct tag
This is still currently at the planning stage, but the research of the AI Platform component of Symfony is a no-brainer when its stable - and the AI Store is also a likely possible candidate that we want to move to.
We should do everything possible to make this move prepared in 2.0.0, so that we make sure that any normalization and abstraction layer of input and output, will be at a first stage interoperable with the AI Platform and AI Store and a later stage maybe exchanged.
The most likely timeline of this is the we introduce breaking changes in 2.0.0 (autumn release) that make interoperability possible with the Symfony AI at its then current featureset, with added Drupal featureset just added for what is not covered in Symfony AI. That means that we might for instance have to use the Symfony Client for certain OpenAI calls, and the openai-php client for others - but this is a design pattern we already know from some providers like Ollama where we have one client to do calls, and another client to control Ollama.
For 3.0.0 (late winter, early spring) we might then do a full switch, where input and output classes are either directly from Symfony AI or most likely decorated versions of them.
We are having discussion with people from the Symfony team, and we want to help contribute there with learning and in general with manpower. As we have seen in the Drupal AI community, with a decoupled architecture you can have a lot of people working on many fronts at the same time, so it should be possible to help out a lot in the Symfony AI issue queue.
Active
2.0
AI Core module
marcus_johansson → credited kim.pepper → .
Switching to the correct tag