2 July 2026 – by Jeroen Ticheler – President of OSGeo
Notes from the Timisoara BoF
Opinions in the room were strong and differed a lot, which was the point. We wanted to hear from people who use AI in their work and from people who have concerns or bad experiences, and would rather block AI contributions completely.
The problem is clear. Some projects now get many AI-generated pull requests that land on the desks of a few core reviewers. They cannot keep up. A lot of these PRs are long and give no useful reason for the change. The tone can be pushy and cold. On top of that, there is little human to human discussion behind these PRs, which makes the whole process feel inhuman from the start. When this keeps happening, trust drops, people feel worn down, and conflict becomes more likely, because they hold different technical and ethical standards.
People shared their own stories
We heard what it is like to get an anonymous PR with no real person behind it, where the sender seems to have done little more than press submit.
We also heard positive experiences, where developers have taught AI tools their own coding style and review habits, then used those tools in two ways. One is to write new code that is hard to tell apart from your own. The other is to fight fire with fire: let AI check incoming PR’s and reject the ones that ignore the project rules, so those never reach a human.
We also talked about newcomers. Many students and young developers learned to code with AI from the start. Do they know enough to contribute well, and how will they learn to write the kind of code an OSGeo project needs? The room saw a link with earlier changes, like the move to new programming languages. Each time the needed skills changed, and each time people adapted.
A call on tone and community
The first outcome was a call to be careful with the way we talk to each other. If we lose respect and stop being a welcoming community, the harm lasts longer than any single PR. *We are in this together.* AI-assisted coding is here to stay, and it also opens doors, for example for people who do not code but want to help once good guardrails exist. The room agreed on this and backed it.
A call to build shared AI practices
The second outcome was a call to start a new OSGeo effort where developers build shared skills, agents, and contribution practices that any project can use. This is not about copying one person’s style. We have not yet decided if this should sit at OSGeo level or inside each project.
If you code with AI or review PRs, we want you involved and I invite you to start the conversation on our discuss list or on our Discourse General channel.
Thanks for reading!
Jeroen Ticheler
President of the board of directors of OSGeo
