public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Pereira <danielmaraboo@gmail.com>, linux-doc@vger.kernel.org
Subject: Re: [QUERY] Guidelines for starting pt_BR documentation translations
Date: Mon, 02 Feb 2026 08:51:35 -0700	[thread overview]
Message-ID: <87a4xrta7s.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAMAsx6dzNMHYA630UWtD5EJX5QqyT9BqJX03c5QzHN9EizjQtQ@mail.gmail.com>

Daniel Pereira <danielmaraboo@gmail.com> writes:

[Responding to the public post rather than the private email]

> My name is Daniel and I am a Linux instructor and systems engineer
> from Brazil. I've noticed that the Linux Kernel documentation
> currently lacks a pt_BR (Brazilian Portuguese) translation directory.

That is true; nobody has shown interest (until now) in creating or
maintaining such a thing.

I have become a little leery of translation efforts; they tend to be
started with a lot of enthusiasm.  But keeping documentation up to date
is a real treadmill of a job, and that enthusiasm tends to fade over
time, especially if it's a single-person effort.

Nonetheless, if you want to make a try at it, we can certainly accept
it.

> I have started translating the 'howto.rst' file and I intend to
> maintain the pt_BR translation tree. However, before submitting any
> patches, I would like to ask for guidance on the proper procedure:
>
> 1. Should I first submit a patch creating the
> Documentation/translations/pt_BR directory along with the first
> translated file?

It seems you have already done that :)  That is a good first step.  Your
timing is not ideal, though, in that the merge window starts in a week.
I'll not be able to accept a new translation until the merge window
ends.

> 2. Is there a specific coordinator for Portuguese translations I
> should reach out to, or should I send patches directly to the
> documentation maintainers?

The coordinator for Portuguese translations, I think, will be you...
yes, send patches to me, please.

> 3. Regarding the MAINTAINERS file, should I include myself as the
> maintainer for this new section in the same patch as the translation?

Yes, or as a separate patch in the series.

Thanks,

jon

  reply	other threads:[~2026-02-02 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-01  0:23 [QUERY] Guidelines for starting pt_BR documentation translations Daniel Pereira
2026-02-02 15:51 ` Jonathan Corbet [this message]
2026-02-02 17:08   ` Daniel Pereira
2026-02-02 17:27     ` 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=87a4xrta7s.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --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