Welcome to cq Discussions!

[peteski22]

Welcome to cq discussions

This space is for the conversations that don't fit cleanly into a GitHub Issue or a pull request.

What goes here

• Design proposals / RFCs. Larger features and architectural changes get a discussion thread: problem statement, options, tradeoffs, so people can react before any code is written. Only open one when a mozilla.ai maintainer has asked for it (usually off the back of an Issue or an Idea); unsolicited RFCs will be redirected. Once a direction is agreed, a short ADR captures the decision and lives in the repo; the thread stays as the record of why.
• Ideas. Half-formed thoughts, "would it make sense if cq...", explorations that aren't ready to be a concrete request.
• Q&A. Usage questions, integration questions, "is this the right way to..." prompts.
• Show and tell. Cool things you've built on top of cq, integrations, war stories.

What still goes in Issues

• Concrete bug reports with reproduction steps.
• Scoped feature requests where the what is already clear and only the how needs implementation.
• Anything you can imagine landing in a milestone or a release note.

Rule of thumb: if the next sensible step is write code, it's an Issue. If the next sensible step is talk it through, it's a Discussion.

RFC workflow

1. A maintainer asks for an RFC on the back of an Issue or Idea.
2. Open a thread in the RFCs category with a problem statement, options, and tradeoffs.
3. Iterate in the thread; reactions and comments are first-class.
4. Once a direction is agreed, open an Issue to track the implementation and (if useful) commit a short ADR summarising the decision.
5. Close the discussion with a link to the Issue or ADR.

Looking forward to seeing what people start.