Package maintainers

[sirkitree]

Currently, we're consolidating everything into Eliza, which works well for now. The independent nature of each package is beneficial, and while centralizing everything within core Eliza is manageable and even preferable at this stage, it could become challenging to maintain as the project grows.

Should we start considering a separation of concerns—transitioning these packages into their own repositories with dedicated maintainers, independent development, and release cycles—while keeping Eliza as the central integrator?

I'd love to hear your thoughts on whether this approach could enhance scalability and sustainability.

[sirkitree]

Barring this approach - we could keep things in core and designate maintainers of particular packages/sections of core. I believe I saw this mentioned in Discord recently as well https://discord.com/channels/1253563208833433701/1298900529178742796/1312215678815567964

[sirkitree]

One logical separation I can think of would be

• Clients: have some responsible for Twitter, another for Discord, yet another for Telegram, etc.
• Actions: buttplug (seriously why is this core?), tee, video-generation, etc.
• DB Adapters: Supabase, pgsql, sqlite, etc.
• LLM integrations: OpenAI, Local, Anthropic, etc.
• Chain integrations: Solana, EVM, etc.
• Docs