I think this makes sense to do. However, we should probably formalize our AI policy before adding it. I think Iceberg and Arrow might be reasonable places to borrow ideas from here.
On Thursday, May 7, 2026, Aaron Niskode-Dossett via dev < [email protected]> wrote: > Yes, I've found in practice that this almost always happens. > > On Thu, May 7, 2026 at 9:42 AM Andrew Lamb <[email protected]> wrote: > > > I would personally request we update the human documentation as well with > > this information (and ideally point the AGENT file to it). There is no > > reason to hide such useful information only in an AGENTS file in my > opinion > > > > On Thu, May 7, 2026 at 10:16 AM Aaron Niskode-Dossett via dev < > > [email protected]> wrote: > > > >> Yes, +1! My recent PRs were written with codex and I'd be happy to > glean > >> insights (actually, instruct codex to glean the insights) from them and > >> contribute to an AGENTS file. > >> > >> On Thu, May 7, 2026 at 9:10 AM Arnav Balyan <[email protected]> > >> wrote: > >> > >> > Hi team, > >> > > >> > As more users adopt coding agents to navigate and debug Parquet, I > just > >> > wanted to check if it would be a good idea to introduce AGENTS.md to > the > >> > Parquet repo as a small top level file giving project context (on > module > >> > layout, build/test commands, generated code paths, conventions). > >> > > >> > It may make it easier for end users debugging parquet related > >> exceptions in > >> > their applications, and new users onboarding to Parquet codebase. > Would > >> > love to get your thoughts, Thanks! > >> > > >> > Warm Regards, > >> > Arnav > >> > > >> > >> > >> -- > >> Aaron Niskode-Dossett, Data Engineering -- Etsy > >> > > > > -- > Aaron Niskode-Dossett, Data Engineering -- Etsy >
