Benjamin Balder Bach @benjaoming@social.data.coop
Public

@pauloxPaolo Melchiorre Re:

> shared technical or governance approaches

We do need to start collecting these resources. Python.org has one:

devguide.python.org/getting-st

It's definitely a more cautious approach, because it doesn't clearly spell out that AI-generated code is not allowed. I would guess that people are scratching their heads on how that would even be enforced.

Python Developer's Guide

Generative AI

Generative AI tools have evolved rapidly, and their suggested results can be helpful. As with using any tool, the resulting contribution is the responsibility of the contributor. We value good code...

devguide.python.org · Python Developer's Guide

Paolo Melchiorre @paulox@fosstodon.org
Public

Thanks for the link @benjaomingBenjamin Balder Bach ,I didn’t know that Python.org page and it’s very useful. Django has a similar section for AI-assisted security reports:
docs.djangoproject.com/en/dev/

What I find interesting is how GNOME, Python, and Django converge on the same idea: AI can be a tool, but responsibility, disclosure, and reviewability stay with the contributor, otherwise the cost shifts to maintainers.

Maybe the next step is finding a shared place to collect and compare these approaches.

Django logo

Django’s security policies | Django documentation

The web framework for perfectionists with deadlines.

docs.djangoproject.com · Django Project

Link author: Django@django@fosstodon.org

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://fosstodon.org/users/paulox/statuses/115735253862599492 on your instance and quote it. (Note that quoting is not supported in Mastodon.)