From: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
To: Matthew Wilcox <willy@infradead.org>,
Matic Urbanija <maticurbanija@protonmail.com>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: Translation of kernel documentation
Date: Mon, 10 Jun 2024 13:49:53 -0500 [thread overview]
Message-ID: <12acfd83-96a3-4c2a-8aa4-e52709e0cf12@gmail.com> (raw)
In-Reply-To: <44ed000a-8dd4-4dde-853a-2b35fffc8c9d@gmail.com>
On 6/10/24 13:44, Carlos Bilbao wrote:
> Hello Matic,
>
> On 6/7/24 14:11, Matthew Wilcox wrote:
>> On Fri, Jun 07, 2024 at 05:45:10PM +0000, Matic Urbanija wrote:
>>> Hi,
>>>
>>> first of all, I'm terribly sorry if this isn't the right place to ask about translation. I sent an email to helpdesk but so far no answer from them.
>> This is the right place!
>>
>>> My name is Matic Urbanija, I am a teacher at Vegova - Upper Secondary School of Electrical and Computer Engineering and Technical Gymnasium Ljubljana, Slovenia (https://www.vegova.si/about-us-vegova/).
>>>
>>> I would like to translate kernel documentation into Slovenian language. Maybe some of my students would also like to participate.
>>>
>>> Are there some special requirements or procedures which have to be fulfilled before starting translation project? What is the proper or recommend way to start to translate the kernel documentation?
>> Start by creating Documentation/translations/sl/ (the iso639 code for Slovenian)
>> Add an entry to Documentation/translations/index.rst
>> Add Documentation/translations/sl/index.rst
>
> Your first commit will probably resemble this:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20240607&id=444064185df7c4b0f7bb41e25b1bb197a1e4a918
> but, please, don't add yourself to MAINTAINERS if you aren't willing to review
> future contributions (maintaining).
> This is a fantastic way to introduce your students to the kernel
> contribution process. Note they should at least have a basic understanding
> of operating systems and low-level languages (mostly C) to translate
> effectively.
> Feel free to add my email in CC in future communications so I can help.
>
By the way, next time you probably want to CC linux-kernel@vger.kernel.org
so we can easily search for this thread (e.g., in lkml.org).
>> Now start adding documents ;-)
>>
>> You can send patches to this mailing list for Jon to apply to the
>> documentation tree for merging.
>>
> Thanks,
> Carlos
Thanks,
Carlos
>
next prev parent reply other threads:[~2024-06-10 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 17:45 Translation of kernel documentation Matic Urbanija
2024-06-07 19:11 ` Matthew Wilcox
2024-06-10 18:44 ` Carlos Bilbao
2024-06-10 18:49 ` Carlos Bilbao [this message]
2024-06-10 20:11 ` Jonathan Corbet
2024-06-10 20:09 ` Jonathan Corbet
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 16:38 Matic Urbanija
2024-06-17 14:25 ` Jonathan Corbet
2024-06-17 15:30 ` Matic Urbanija
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=12acfd83-96a3-4c2a-8aa4-e52709e0cf12@gmail.com \
--to=carlos.bilbao.osdev@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=maticurbanija@protonmail.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).