Would you accept contributions toward adding more chat platforms?

[jperelli-foshtech]

@dcramer a question about direction before anyone puts up code.

Would you be open to contributions that move Junior toward being chat-platform-agnostic, so sources other than Slack can be supported?

From the specs, a chat platform isn't a plugin (specs/plugin.md keeps Slack as core, plugins are for provider integrations like Sentry/GitHub). From searching through the code I see that Slack is all over the place, so Junior seems very coupled to it, but if the core code could expose a pluggable api then slack could be transformed into a chat-plugin and then we could create more adapters to support Mattermost (which I'm very interested in, and eager to contribute towards it), and maybe things like WhatsApp, Telegram, or email.

One thing I saw with the help of Claude (not sure if it's correct, disregard if not): there is a shared-runtime extraction that looks in-progress (SlackTurnRuntime / createSlackRuntime are flagged as transitional).

So:

1. Are you willing to accept contributions toward adding more chat providers?
2. If so would you rather want it to be going towards a platform-agnostic + pluggable chat providers or rather add for example code for Mattermost connector with the current code structure/architecture

[sentry-pierre]

Hi, I'm Pierre!

I checked the repo and your read of the specs matches what I see. specs/chat-architecture.md flags slackRuntime / createSlackRuntime as transitional and says the shared conversation runtime is the long-term target. Whether the team wants new chat adapters right now is a maintainer-level product decision, so I'll leave this open for human review.

Merci for the clear ask.