[OSGeo-Discuss] [Board] Request for a moratorium on AI/LLM use within OSGeo
Laurențiu Nicola
lnicola at dend.ro
Tue Nov 3 22:59:03 PST 2026
1. On Wed, Nov 4, 2026, at 08:27, Antonovic P. Milan via Discuss wrote:
> Check the example of the Rust community: https://forge.rust-lang.org/policies/llm-usage
Hi,
I'm not sure Rust is the best example. It has a very strong political bias, and many contributors are very vocal against LLMs, large companies etc. The same bias also tends to cause some tension between independent contributors and corporate backers (who happen to provide considerable financial resources to the project).
Still, even Rust will generally accept LLMs for fuzzing, reviews etc. Second, the policy applies to the Rust toolchain itself. There are sub-projects (libraries, tooling etc.) and these are not forced to adopt the same policy. Many will, but a number of them already have different AI policies.
I propose the Linux kernel as an example. I already see people who threaten to switch to NetBSD because of it. The latest release of PostgreSQL was notably affected too, not because of LLM-written code (which it doesn't have), but because it has a huge number of fixes for bugs found by them.
While for OSGeo I suspect Even would very much prefer a general ban, despite the "each group could potentially reframe it" dispensation.
Personally I wouldn't be totally against a general "LLM usage is strongly discouraged for writing code and especially public communication, but each project is allowed to pick its own policy", but I don't really want OSGeo to become a vehicle for "we should guillotine some CEOs" (or even independent developers, it's happened before).
But of course, I have no decision power here. I just want open source projects to thrive and their developers to be happy.
Laurentiu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/discuss/attachments/20261104/0e3283cb/attachment.htm>
More information about the Discuss
mailing list