On 20 Sep 2026, at 22:13, Frédéric Desbiens via paho-dev <paho-dev@xxxxxxxxxxx> wrote:
Hi everyone. The Eclipse project handbook contains generative AI guidelines for committers. If AI contributions are accepted, then they should comply with the rules highlighted in the handbook. The short version is: any usage of AI should be properly disclosed, and the human contributor remains responsible.
That’s really interesting thanks - in 1-3 years we are all going to be using AI and those who aren’t will disappear (imvho)
The pain at the moment is mostly trying to find a completely new set of best practice in a tech. world that appears to be accelerating on an exponential curve.
The Singularity Approaches.
(I do appreciate the problem of maintaining Quality and the work to deal with AI slop. But I’m a year in now and I can do over a week’s work in a day. This stuff isn’t going away imho)
Cheers,
Alex
Naturally, a project could decide to exclude AI contributions. In that case, the project team should take a proper vote on this matter and make this policy known on the website, on GitHub, and through other channels as well.
Best Regards,
Frédéric DESBIENS Project Lead | Eclipse ThreadX Senior Manager —
Embedded Systems, IoT, and Open Hardware Programs | Eclipse Foundation Mastodon: @fdesbiens@xxxxxxxxxxxxxxxxxxxxx Eclipse Foundation: The Community for Open Innovation and Collaboration Greg Troxel via paho-dev <paho-dev@xxxxxxxxxxx> writes:
> can be left for future work. A ban now is now forever. Admitting LLM
Sorry, "not forever" and actual human word-o. My point is that while a
"just no" policy now seems drastic, it, like any policy is temporary.
What is not temporary is anything merged to the repo under a looser
policy, because unwinding things is both so controversial as to make it
unlikely to happen, and a lot of work.
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/paho-dev
|
