No subject

[Regina Obe]

> That sounds like decision to embrace vibe coding, and to ignore the
license
> issues.  I'll see how you proceed, and may step away to just enough to
keep
> things working for my needs.  Maybe people will like that better ;)

Nah we'd be bored without you.  Strk was complaining the mailing list is too
quiet and he's all happy now.

Part of the exercise is to see what license issues could come up too.

Like the only thing I can think of is to claim -- well LLMs are all trained
on stolen data therefore their work is stolen.

But there is no proof to that and there is no way to assume the same about a
user doing the same thing.

Like for example look at this patch:

https://github.com/postgis/postgis/pull/945/changes

Can you say there is anything stolen looking about it, if a human gave you
this patch?
Clearly whoever wrote this looked at our code base, saw we use ST_Normalize
to solve many of our regression issues and did the same and of course it
didn't test it's work so it fails regression

https://github.com/postgis/postgis/actions/runs/27699559886/job/81931938915

So anyway a lot of these pull requests look like trying to solve problems
the way we've solved in the past. Can we provide guidance on what is good
code to follow and what is not?