From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Sumitra Sharma <sumitraartsy@gmail.com>
Cc: outreachy@lists.linux.dev, julia.lawall@inria.fr,
alison.schofield@intel.com
Subject: Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma
Date: Fri, 17 Mar 2023 20:24:59 +0100 [thread overview]
Message-ID: <4774662.F8r316W7xa@suse> (raw)
In-Reply-To: <20230317180055.GA3391@sumitra.com>
On venerdì 17 marzo 2023 19:00:55 CET Sumitra Sharma wrote:
> On Fri, Mar 17, 2023 at 04:15:37PM +0100, Fabio M. De Francesco wrote:
> > On venerdì 17 marzo 2023 12:05:09 CET Fabio M. De Francesco wrote:
[snip]
> >
> > 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).
>
> Hi Fabio
>
> Here it is
> https://lore.kernel.org/outreachy/20230317175007.GA3275@sumitra.com/T/#u
I just read the list of the links. You showed pairs of links: the first is the
current one pointing to .rst files, the second points to the output .html
file.
If I'm reading correctly, and you took special care to check that the web
pages you are linking are at the right URL, I'm OK with your list of changes
(I cannot check them one by one).
> > 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.
(Here it looks like you merged your message with mine. OK, don't worry about
it now but be careful next time).
> > Don't forget that Alison said that they count as
> > contributions that you can add in your records.
>
> I am also working on the Mutt configuration. Can you tell me how we are
> going to mention these kind of contributions when recording the
> contribution?
Alison will help you as soon as she can. I don't know how the contributions to
the kernelnewbies website should be recorded, I think that they go to into the
same form you should use for the patches.
Please wait for her answers about this subject.
> Also, are we suppose to record the contribution for each
> and every patch separately or we have to compile them together in one go
> during the last days of contribution period?
Contributions can only be registered one at a time using the appropriate form
accessible from the project(s) you wish to work on. I suggest choosing one or
two projects, no more than two. If you prefer to apply for your first choice
and a fallback project you should record each contribution twice.
The sooner candidates start recording the contributions, the easier our job
will be.
Thanks,
Fabio
> Regards,
>
> Sumitra
next prev parent reply other threads:[~2023-03-17 19:25 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
2023-03-17 18:00 ` Sumitra Sharma
2023-03-17 19:24 ` Fabio M. De Francesco [this message]
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=4774662.F8r316W7xa@suse \
--to=fmdefrancesco@gmail.com \
--cc=alison.schofield@intel.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.