zbendhiba commented on PR #27265: URL: https://github.com/apache/camel/pull/27265#issuecomment-6167710332
Thanks for writing this up. I'm okay with making this easy. No objection on the mechanism itself. My concern is the door it opens. Adding a mini DSL is hard today, and that difficulty is our governance. This design makes it cheap. So one ask. Add this rule to the doc: ▎ A new DSL extension needs a design doc and dev-list agreement. Project decision, not component decision. And our AI review guidelines should flag any PR that adds a new DSL extension. Easy to detect. It catches the agent-written PRs where everything goes green and nobody asked "should this exist?". On the AI use cases specifically. I've hit this limitation in the past, so I get the motivation. But today I'd rather keep AI complexity in external frameworks and have Camel integrate better with them, like we started doing with LangChain4j, AI tools... Not grow AI-specific DSLs inside Camel. That's exactly the kind of case where I'd want the dev-list discussion to happen first. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
