<div dir="ltr"><div>I also strongly suspect that "require an issue to describe the issue" would simply translate to "the LLM is asked to generate even more fluff than it usually puts in the PR description".</div><div><br></div><div>Also, would it mean that one-line docs typo PRs need an approved issue? If not, what would be the threshold for "this proposed change must be approved" and who would decide it?</div><div><br></div><div>Cheers,</div><div>Daniel</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, 13 May 2026 at 23:10, Even Rouault via gdal-dev <<a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<p>Andrew,</p>
<p>I doubt you can enforce that through github configuration, and
even if we could, that seems to me like adding overhead to all the
people acting reasonably (some "institutional" large projects may
have that kind of policy, but none of the projects I regularly or
occasionally contribute to require this). That said, opening an
issue to discuss a problem and expose some ideas can certainly be
done when needed (and going through a full RFC for substantial
changes), but someone contributing a typo fix shouldn't have to
open a ticket first.</p>
<p>Even</p>
<div>Le 13/05/2026 à 19:38, Andrew Bell a
écrit :<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>Would it be helpful to require an issue that describes
the change to be made and then some approval before
permitting an PR to be opened? (I have no idea if this is
technically feasible.)<br>
<br>
</div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, May 6, 2026 at
12:29 PM Even Rouault via gdal-dev <<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote">Hi,<br>
<br>
based on the experience gained from the initial policy, I
propose to <br>
significantly revise it to drastically limit their use.
See <br>
<a href="https://github.com/OSGeo/gdal/pull/14500" rel="noreferrer" target="_blank">https://github.com/OSGeo/gdal/pull/14500</a><br>
</blockquote>
</div>
<div><br>
</div>
<span class="gmail_signature_prefix">-- </span><br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>Andrew Bell</div>
<a href="mailto:andrew.bell.ia@gmail.com" target="_blank">andrew.bell.ia@gmail.com</a></div>
</div>
</div>
</div>
</blockquote>
<pre cols="72">--
<a href="http://www.spatialys.com" target="_blank">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</div>
_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
</blockquote></div>