[tc][all][ptg] 2027.1 "Indri" OpenStack Agentic Workflows PTG Summary
Hello Stackers, Contributors to the TaCT SIG's ``agentic-workflows`` effort (the ``openstack/agentic-workflows`` repository) met during the Indri PTG. The session reviewed the OpenInfra Foundation AI policy. The TC has not adopted it for OpenStack. The likely next step is an OpenStack proposal, based on the OIF policy, for community debate and adoption. The TaCT SIG's ``agentic-workflows`` repository is the common home for shared workflow tooling, templates, and conventions. It needs maintainers and a defined process for reviewing and merging contributions. For project guidance, the recommendation is to use ``AGENTS.md`` as a routing file: point to existing RST/Sphinx documentation and project-specific skills instead of copying documentation into another large Markdown tree. Safe, reviewable agent workflows -------------------------------- When using agents for code review, the recommendation is to treat agents as untrusted actors: give them separate credentials, use authenticated service layers and narrow allowlists, and do not put human credentials in their context. Agents should work through ordinary Gerrit review and Zuul gating, not privileged side channels. The experiments from sean-k-mooney (teim-review) and mordred (OpenClaw for Zuul) run review agents as Zuul jobs. They use project skills and conventions, leave Gerrit comments and HTML reports. These tools are being tuned to avoid noisy or incorrect feedback. They do not change the merge bar: tests and human review still decide whether a change lands. Maintainers also need to remain able to understand and maintain AI-assisted code. Measurements and next steps --------------------------- A query of merged changes found 1,753 ``Assisted-By`` trailers in ``openstack/*`` between 12 March and 30 September 2026: ~12.0% of merged changes. This is trend data, not a scorecard. It may help us understand how contributor and maintainer work is changing. The OIF policy recommends ``Assisted-By`` going forward; ``Generated-By`` remains an approved label. An OpenStack policy will need to decide whether either label is required. The group did not propose a periodic IRC meeting for now. Those interested in the work should join the ``#openstack-agentic-workflows`` channel on OFTC and chat async. Action items ------------ - Existing ``agentic-workflows`` cores will define the review/merge process and revisit a periodic IRC meeting if needed. - Formulate, propose, debate, and adopt an OpenStack version of the OIF AI policy (TC, volunteers needed) Thank you for reading and participating in this discussion! Goutham Pacha Ravi (gouthamr) [1] https://openinfra.org/legal/ai-policy [2] https://etherpad.opendev.org/p/r.9ac2725fa952d297db46e59670606e48 [3] https://www.seanmooney.info/blog/agentic-ai-teim-review/ [4] https://www.youtube.com/watch?v=T5hj_VqFqw8
participants (1)
-
Goutham Pacha Ravi