Contributing a SonexLabs TTS plugin — existing PyPI package name conflict

[ayushi-agarwall]

Hi team,

I maintain SonexLabs's TTS API and would like to contribute a livekit-plugins-sonex plugin to this monorepo so it can be listed on the TTS plugins page.

Before submitting a PR, I wanted to flag one thing: I already publish a standalone package named livekit-plugins-sonex on PyPI under my own account (source: https://github.com/sonexlabs/livekit-plugins-sonex), following the pattern I used before learning about the monorepo contribution process.

Since plugins merged into this repo are published to PyPI by LiveKit's own release automation under the same livekit-plugins-<name> naming convention, I want to check the right path forward before opening a PR:

1. Should I transfer/yield the existing livekit-plugins-sonex PyPI name to LiveKit's publishing account, or
2. Would you prefer a different package name for the monorepo version, or
3. Is there a preferred process for this situation?

Happy to follow whatever convention works best. Thanks!

[tinalenguyen]

hi @ayushi-agarwall, thanks for reaching out! we'd prefer if you open a PR with the implementation first, and once that's merged in you can transfer ownership to LiveKit

[ayushi-agarwall]

Opened #6777 with the plugin implementation, per your suggestion above. CLA is signed. Also just pushed a follow-up commit addressing the automated review feedback (sample-rate reporting, Python 3.10 timeout handling, ruff format/lint). Happy to make any further changes needed — and can transfer the livekit-plugins-sonex PyPI package name to LiveKit once this is merged.