From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Pereira <danielmaraboo@gmail.com>,
Daniel Castro <arantescastro@gmail.com>
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: pt_BR: translate process/1.Intro.rst
Date: Mon, 16 Mar 2026 17:55:16 -0600 [thread overview]
Message-ID: <87cy13fhy3.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAMAsx6e9qqdw+aBGkkU3tDONdAmF=ATiCOn50FMfmd1Mzsfuxw@mail.gmail.com>
Daniel C.: please CC the documentation maintainer on docs patches.
Daniel P.: thanks for reviewing! I do have some comments below...
Daniel Pereira <danielmaraboo@gmail.com> writes:
> On Mon, Mar 16, 2026 at 6:25 PM Daniel Castro <arantescastro@gmail.com> wrote:
>>
>> Add Brazilian Portuguese translation of the development process
>> introduction (Documentation/process/1.Intro.rst), covering the
>> executive summary, importance of mainline code, and licensing.
>>
>> Assisted-by: Claude:claude-opus-4-6
>> Signed-off-by: Daniel Castro <arantescastro@gmail.com>
>> ---
>> Documentation/translations/pt_BR/index.rst | 1 +
>> .../translations/pt_BR/process/1.Intro.rst | 300 ++++++++++++++++++
>> 2 files changed, 301 insertions(+)
>> create mode 100644 Documentation/translations/pt_BR/process/1.Intro.rst
> Removal of AI credits: Remove the Assisted-by: Claude tag. Kernel
> documentation requires full human review to ensure no conceptual or
> literal translation errors. As the author, you are legally responsible
> for the integrity of the text under the DCO.
I have to disagree with this; the Assisted-by tag is part of our
emerging consensus on work resulting from these tools. See
Documentation/process/coding-assistants.rst.
I will confess to having mixed feelings, at best, about the use of such
tools. But I do not feel it's right to ban such output just based on
its origin. Documentation patches, like all others, need to be
carefully reviewed and are, in the end, the responsibility of the person
submitting them.
> There are lines with residual white spaces (visible as isolated +
> symbols in the diff). Remove these to prevent rendering warnings in
> Sphinx.
Comments like this are best made inline so that the submitter can see
exactly where the problem is.
> Legal Terminology: In the licensing section, change "propriedade
> original" to "titularidade original". This is the technically correct
> term for copyright in Portuguese.
> Remove the reference label at the top of the file (..
> _development_process_intro:), as it is unnecessary for this stage of
> the translation.
These too - please use our normal style for review comments.
Glad to see you calling out the top label! :)
Daniel C.: the presence of that label suggests that you did not actually
build your changes with sphinx, since it should have resulted in a
"duplicate label" warning.
Thanks,
jon
next prev parent reply other threads:[~2026-03-16 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 21:24 [PATCH] docs: pt_BR: translate process/1.Intro.rst Daniel Castro
2026-03-16 22:59 ` Daniel Pereira
2026-03-16 23:55 ` Jonathan Corbet [this message]
2026-03-17 14:01 ` [PATCH v2] " Daniel Castro
2026-03-17 16:43 ` Daniel Pereira
2026-03-17 17:00 ` Jonathan Corbet
2026-03-17 17:16 ` Daniel Pereira
2026-03-22 20:47 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cy13fhy3.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=arantescastro@gmail.com \
--cc=danielmaraboo@gmail.com \
--cc=linux-doc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox