Simon Tournier <[email protected]> writes:

> ** Pledge
>
> We propose the following project commitments:
>
> 1. The project (defined as maintainers, team members, and anyone with write
>    access to a Guix repository, including Weblate, or to Guix resources such
>    as the build farm) *will not use or encourage use of genAI*.  Namely, the
>    use of genAI means *not simply pasting* answers, code or packages, code
>    reviews, artwork, translations or comments generated by genAI *without
>    proper review using human own input*.

IMHO zimoun’s last sentence is clearer, explicit, less strict wording
than Ludo’s “*use* genAI to author/produce”.  Either way, whatever
strictness can pass consensus, translations are another real problem.

Apparently, “AI” is part of the workflow of some human translators.  In
translating, it is not the real problem.  The real problem is as zimoun
writes, when LLM output is simply pasted without qualified review.
Review is hard when translators don’t really know Guix.  It is worse
when not knowing grammar.

To me, there’s only one realistic way not to make a false promise with
this pledge: Stick with taking translations from the Codeberg Weblate,
but don’t mention translations nor Weblate in the pledge.  Generative
LLM AI are not really the problem in translations, though we can
discourage its use in a possibly ignored Weblate message.

Or less realism: Set up our own Weblate for Guix, with few translators
who maybe better know Guix (which I will not set up; this likely is not
a real option in the near future).


Ludovic Courtès <[email protected]> writes:

> Hi Florian,
>
> "pelzflorian (Florian Pelz)" <[email protected]> skribis:
>
>>>    - by improving tools for mechanical translation, refactoring, and
>>>      updates such as =guix import=, =guix style=, and =guix refresh=,
>>>      so that tedious packaging tasks can be automated in a way that is
>>>      transparent, deterministic, and maintains the project’s
>>>      sovereignty.
>>
>> Do not mention mechanical translation
>
> In this context “mechanical translation” refers to what ‘guix import’
> does: translating repository metadata (PyPI, CRAN, etc.) to Guix package
> definitions (hence “such as”, but let me know if you still find it
> ambiguous).
>

Oops!  All fine here.

Regards,
Florian

Reply via email to