I strongly agree — this discussion has opened up an excellent topic. In addition, I believe that for FLUSS to embrace the AI ecosystem could be a highly systematic effort. I’ve initiated an FIP proposal: https://cwiki.apache.org/confluence/display/FLUSS/FIP-34%3A+Making+Fluss+an+AI-Native+Project, which explores various aspects of making Fluss AI-Native. Everyone is also very welcome to join the discussion and share feedback in this discussion thread: https://lists.apache.org/thread/xm35s36fsqt8dyhbkkvq05nwm7l48rp2.
Junbo Wang <[email protected]> 于2026年3月19日周四 11:33写道： > +1 for this. > > Beyond AGENT.md, I believe we could prioritize making Fluss natively > AI-agent-ready. Investing in CLI and Skills designed for AI agents > will be increasingly important — it enables Fluss to be operated and > consumed programmatically by agents, not just humans. A well-prepared > CLI for agents will likely gain more traction in the coming year. > > > Best regards， > Junbo Wang > > > Jark Wu <[email protected]> 于2026年3月19日周四 11:17写道： > > > +1 for this. > > > > I believe we must proactively embrace AI agents. Beyond simply adding > > AGENT.md and similar tools to support AI development, we should also > > support Fluss CLIs and Skills to ensure our ecosystem is fully > > optimized for AI agent interaction. > > > > > > Best, > > Jark > > > > On Thu, 19 Mar 2026 at 02:32, Giannis Polyzos <[email protected]> > > wrote: > > > > > > Hi Vaibhav, > > > Thank you for initiating this discussion. > > > > > > +1 for this, we already had similar discussions on this topic offline. > > > > > > So it will be great to introduce something similar and some guidelines. > > > > > > Let’s see what we can do here. > > > > > > Best, > > > Giannis > > > > > > On Wed, 18 Mar 2026 at 6:29 PM, Vaibhav Kumar <[email protected]> > > > wrote: > > > > > > > Hi everyone, > > > > > > > > I wanted to start a discussion on a growing challenge across Apache > > > > projects: AI-generated contributions. > > > > > > > > Other communities are already seeing increased maintainer burden from > > PRs > > > > that require significant effort but add limited value. Some projects > > (e.g., > > > > Iceberg, Flink) have started addressing this with files like AGENT.md > > to > > > > better guide contributors and AI tools. > > > > > > > > Since Fluss is still in incubation, this could be a good opportunity > > to be > > > > proactive and put some lightweight guardrails in place early. > > > > > > > > Some initial ideas: > > > > > > > > - Introducing an AGENT.md (similar to Iceberg/Flink) to guide > > > > AI-assisted contributions > > > > > > > > This isn’t about discouraging AI usage, but about maintaining quality > > as > > > > the project grows. > > > > > > > > What do others think? > > > > > > > > Worth addressing now during incubation? > > > > > > > > Regards, > > > > Vaibhav > > > > > > >
