Yes, I tried to provide some front matter rationale and discretize the policy items so it was more clear. I will say I'm a bit skeptical on the specifics because LLM code contribution seems likely to become less and less obvious as time goes on. We clearly don't want to be answering agents or unsupervised LLM contribution however, as it isn't the maintainers' job to train the LLMs.
Let's go with this for now and revisit as needed. https://gdal--14500.org.readthedocs.build/en/14500/community/ai_tool_policy.html > On May 13, 2026, at 5:19 AM, Even Rouault via gdal-dev > <[email protected]> wrote: > > Howard submitted a substantial update / counter-proposal to my initial one. > I've taking it, but with amendments re-introducing points of my initial > version. Please check > > Le 12/05/2026 à 13:34, Even Rouault via gdal-dev a écrit : >> Any further comments before submitting to vote? >> >> Le 06/05/2026 à 18:29, Even Rouault via gdal-dev a écrit : >>> Hi, >>> >>> based on the experience gained from the initial policy, I propose to >>> significantly revise it to drastically limit their use. See >>> https://github.com/OSGeo/gdal/pull/14500 >>> >>> Even >>> > -- > http://www.spatialys.com > My software is free, but my time generally not. > > _______________________________________________ > gdal-dev mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/gdal-dev _______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
