You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disclosure: I use Claude Code all the time while I'm maintaining cpal, co-maintaining Rodio, and looking into dasp. Sometimes I do keep generated function blocks entirely, and often it does assist me to create PR descriptions.
So what I do violates the published AI policy. If that's a problem then you'll need to show me the door. If not a problem, I want to be clear about that too. Following the discussions on Discord, I have a growing discomfort to be part of a community that forbids and shuns my way of working.
I am not looking to sway anyone on their AI stance. I am asking for clarity whether RustAudio and I are good like this or whether we need to part ways. And if we're good, then let's work on a more inclusive and output-focused AI policy.
Added some comments in Discord and summarizing here.
Rules will be updated to note that maintainers may have different AI policies. I still want to avoid low-quality vibe-coded projects in Discord, and protect against PR spam from repositories that don't have active maintainers. However, you are in full control of this project's management, and (IMO) you are trusted in the community to make decisions that will benefit this project. If you'd like to use and permit AI beyond what is described, that is totally up to you.
The policy's language is strict, as its intended audience is general chat members. Before making our rules clearly visible on Discord, we had multiple slop projects posted per week (outnumbering posts of projects created by real people).
The policy's language is strict, as its intended audience is general chat members. Before making our rules clearly visible on Discord, we had multiple slop projects posted per week (outnumbering posts of projects created by real people).
I understand we want to keep this out, and that it's hard to find the right language for a policy that targets what we want to exclude without catching legitimate use cases. I appreciate it.
I've updated this slightly to address some feedback & to clarify language after sitting on this for a few days. Instead of being wishy-washy on what is and isn't allowed (which will definitely lead to confusion), I've listed cpal directly as an exception to the AI policy. I think having this opt-in with crates under the org will better help establish those guidelines than just "check with the maintainer, we dunno"
Going to merge this in in a day or so, please get any comments in.
Activity
roderickvd commentedon Jan 18, 2026
This has been added in #16 and published here: https://rust.audio/community/ai/
Disclosure: I use Claude Code all the time while I'm maintaining cpal, co-maintaining Rodio, and looking into dasp. Sometimes I do keep generated function blocks entirely, and often it does assist me to create PR descriptions.
So what I do violates the published AI policy. If that's a problem then you'll need to show me the door. If not a problem, I want to be clear about that too. Following the discussions on Discord, I have a growing discomfort to be part of a community that forbids and shuns my way of working.
I am not looking to sway anyone on their AI stance. I am asking for clarity whether RustAudio and I are good like this or whether we need to part ways. And if we're good, then let's work on a more inclusive and output-focused AI policy.
piedoom commentedon Jan 18, 2026
Added some comments in Discord and summarizing here.
Rules will be updated to note that maintainers may have different AI policies. I still want to avoid low-quality vibe-coded projects in Discord, and protect against PR spam from repositories that don't have active maintainers. However, you are in full control of this project's management, and (IMO) you are trusted in the community to make decisions that will benefit this project. If you'd like to use and permit AI beyond what is described, that is totally up to you.
The policy's language is strict, as its intended audience is general chat members. Before making our rules clearly visible on Discord, we had multiple slop projects posted per week (outnumbering posts of projects created by real people).
Is that a reasonable compromise?
roderickvd commentedon Jan 20, 2026
Yes, thank you.
I understand we want to keep this out, and that it's hard to find the right language for a policy that targets what we want to exclude without catching legitimate use cases. I appreciate it.
piedoom commentedon Jan 22, 2026
@roderickvd I've created a PR, please let me know your thoughts.
#19
piedoom commentedon Jan 25, 2026
I've updated this slightly to address some feedback & to clarify language after sitting on this for a few days. Instead of being wishy-washy on what is and isn't allowed (which will definitely lead to confusion), I've listed cpal directly as an exception to the AI policy. I think having this opt-in with crates under the org will better help establish those guidelines than just "check with the maintainer, we dunno"
Going to merge this in in a day or so, please get any comments in.