All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: sumitraartsy@gmail.com, outreachy@lists.linux.dev,
	Sumitra Sharma <sumitraartsy@gmail.com>
Cc: julia.lawall@inria.fr
Subject: Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma
Date: Fri, 17 Mar 2023 16:15:37 +0100	[thread overview]
Message-ID: <3190629.0WQXIW03uk@suse> (raw)
In-Reply-To: <10119311.0AQdONaE2F@suse>

On venerdì 17 marzo 2023 12:05:09 CET Fabio M. De Francesco wrote:
> On giovedì 16 marzo 2023 09:31:16 CET Sumitra Sharma wrote:
> > On Sun, Mar 12, 2023 at 10:07:57AM -0700, Sumitra Sharma wrote:
> > > 2. The outreachy document directly links the ".rst" file
> > > https://elixir.bootlin.com/linux/latest/source/Documentation/process/
> 
> coding-
> 
> > > style.rst at many places under different sections. And as noted by fabio
> > > there is a difference between the .rst source files content and its
> > > corresponding .html file which can lead to confusions and missing
> 
> important
> 
> > > information. I would like to suggest to change the links to the 
.html/.pdf
> > > files rather than the > .rst source files.
> > 
> > Hi mentors
> > 
> > I would like to have some update on this.
> > 
> > Regards,
> > 
> > Sumitra
> 
> Hi Sumitra,
> 
> As you know I'm for this change.
> AFAIK, only Alison can grant you the permission to access that document in
> write mode.
> If she hasn't granted that access to you yet, please ask her directly with 
an
> email to her address.
> 
> Thanks for working on this (important, from my POV) change.
> 
> Fabio

Sumitra,

When doing this change, please skim the whole document and replace _all_ the 
links to the .rst files (regardless they point to elixir.bootlin.com or not) 
with the corresponding generated .html in kernel.org.

The document about the Highmem subsystem which I showed you is useless in .rst 
format from the point of view of people who needs to learn its content. I'm 
not sure whether or not we have the same problem with the Linux kernel 
development guidelines, however it does not matter how much it differs from 
the human readable counterpart.

We should make it clear that the source .rst is never the right document to 
consult, unless one want to make changes. The generated documentation from 
.rst with "make htmldocs" (or with other similar commands for .pdf and .epub) 
should be the only to consult for purposes of study (it does not matter if one 
generates them locally or find them in the "documentation" section of the 
kernel.org website).

Thanks,

Fabio

P.S.: I just saw the last message from Julia (in this same thread) regarding 
Mutt configuration. I want to echo her and ask you or other Applicants for 
making also those changes. Don't forget that Alison said that they count as 
contributions that you can add in your records.        



  parent reply	other threads:[~2023-03-17 15:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 17:07 [KERNEL NEWBIES ACCESS] Sumitra Sharma Sumitra Sharma
2023-03-13  9:09 ` Bagas Sanjaya
     [not found]   ` <20230314081646.GA37415@sumitra.com>
2023-03-14  9:27     ` Bagas Sanjaya
     [not found]       ` <20230314123317.GB38692@sumitra.com>
2023-03-15  8:41         ` Bagas Sanjaya
2023-03-17  8:59   ` Bagas Sanjaya
2023-03-16  8:31 ` Sumitra Sharma
2023-03-17  8:51   ` Bagas Sanjaya
2023-03-17 16:15     ` Sumitra Sharma
2023-03-17 11:05   ` Fabio M. De Francesco
2023-03-17 11:12     ` Julia Lawall
2023-03-17 15:15     ` Fabio M. De Francesco [this message]
2023-03-17 18:00       ` Sumitra Sharma
2023-03-17 19:24         ` Fabio M. De Francesco
2023-03-18  6:54           ` Sumitra Sharma

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=3190629.0WQXIW03uk@suse \
    --to=fmdefrancesco@gmail.com \
    --cc=julia.lawall@inria.fr \
    --cc=outreachy@lists.linux.dev \
    --cc=sumitraartsy@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.