[KERNEL NEWBIES ACCESS] Sumitra Sharma

[KERNEL NEWBIES ACCESS] Sumitra Sharma

[Sumitra Sharma]

Dear Outreachy Team,

I am Sumitra Sharma an outreachy applicant. Since being an applicant I was
following the outreachy first-patch document https://kernelnewbies.org/Outreachyfirstpatch
I encountered some issues for which I would like to suggest some updates in the document. 

1. The outreachy document does not include the steps to make the inbox with mutt. The steps below can be added to configure mutt with gmail.

	- Open the ~/.muttrc
	- Add the information 
		
		set sendmail="/usr/bin/esmtp"
		set envelope_from=yes
		set from="Your Name <my.email@gmail.com>"
		set use_from=yes
		set edit_headers=yes
		
		# IMAP settings
		set imap_user = "username@gmail.com"
		set imap_pass = "<mailbox password>"

		# SMTP settings
		set smtp_url = "smtps://username@smtp.gmail.com"
		set smtp_pass = "<mailbox password>"

		# Remote Gmail folders
		set folder = "imaps://imap.gmail.com/"
		set spoolfile = "+INBOX"
		set postponed = "+[Gmail]/Drafts"
		set record = "+[Gmail]/Sent Mail"
		set trash = "+[Gmail]/Trash"
	
	- Where the imap_pass, smtp_pass would be the App password or
	  the mailbox password.

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.


Regards 

Sumitra

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Bagas Sanjaya]

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

On Sun, Mar 12, 2023 at 10:07:57AM -0700, Sumitra Sharma wrote:
> 1. The outreachy document does not include the steps to make the inbox with mutt. The steps below can be added to configure mutt with gmail.
> 
> 	- Open the ~/.muttrc
> 	- Add the information 
> 		
> 		set sendmail="/usr/bin/esmtp"
> 		set envelope_from=yes
> 		set from="Your Name <my.email@gmail.com>"
> 		set use_from=yes
> 		set edit_headers=yes
> 		
> 		# IMAP settings
> 		set imap_user = "username@gmail.com"
> 		set imap_pass = "<mailbox password>"
> 
> 		# SMTP settings
> 		set smtp_url = "smtps://username@smtp.gmail.com"
> 		set smtp_pass = "<mailbox password>"
> 
> 		# Remote Gmail folders
> 		set folder = "imaps://imap.gmail.com/"
> 		set spoolfile = "+INBOX"
> 		set postponed = "+[Gmail]/Drafts"
> 		set record = "+[Gmail]/Sent Mail"
> 		set trash = "+[Gmail]/Trash"
> 	
> 	- Where the imap_pass, smtp_pass would be the App password or
> 	  the mailbox password.

Hi,

You may also consider updating OutreachyfirstpatchAlt.

For MTA, replace the now abandoned esmtp with Postfix. Configure the MTA as
null client (see [1]). For system-generated emails sent to root and postmaster,
you will also need to canonicalize these recipient addresses to your email
address (see [2]).

For mutt config, set sendmail to "/usr/sbin/sendmail"/

Thanks.

[1]: https://www.thegeeksearch.com/how-to-configure-postfix-null-client/
[2]: https://askubuntu.com/a/599513

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Bagas Sanjaya]

[-- Attachment #1: Type: text/plain, Size: 4989 bytes --]

On Tue, Mar 14, 2023 at 01:16:46AM -0700, Sumitra Sharma wrote:
> > Hi,
> > 
> > You may also consider updating OutreachyfirstpatchAlt.
> >
> 
> Hi,
> 
> I am sorry but I am unable to understand this line. Are you referring here to the changes you are mentioning? or to some other document called "outreachyfirstpatchAlt?

On Outreachyfirstpatch, there is a pointer to Outreachyfirstpatchalt
(which contains instructions on spinning up Ubuntu VM), so you need to
install your tools (including postfix and mutt) there if you want to
contribute through there. So I think the latter doc should be kept as
is.

> 
> > For MTA, replace the now abandoned esmtp with Postfix. Configure the MTA as
> > null client (see [1]). For system-generated emails sent to root and postmaster,
> > you will also need to canonicalize these recipient addresses to your email
> > address (see [2]).
> > 
> 
> Okay, So then these will be the following new updates I will propose in
> the Outreachy firstpatch document.
> 
> Configure Postfix Null Client
> 
> 1. Install postfix using below commands. The installation process will open some interactive prompts where you set "General type of mail configuration -> Insternet Site" and "System mail name -> example.com".
> Note: The postfix will then use the address <username@example.com> to send and recieve emails.
> 
> 	> sudo apt update
> 	> sudo apt install postfix
> 
> 2. Edit and set /etc.postfix/main.cf for gmail as:
> 
> 	relayhost = [smtp.gmail.com]:587
> 	inet_interfaces=loopback-only
> 	mynetworks=127.0.0.0/8 [::1]/128
> 	myorigin=example1.example.com
> 	local_transport=error: local delivery disabled
> 
> And add this in main.cf:
> 
> 	recipient_canonical_maps = hash:/etc/postfix/recipient_canonical
> 
> 3. Create file named /etc/postfix/recipient_canonical and add the
> following:
> 	
> 	root@example.com postmaster@example.com
> 
> This will enable the forwarded mail addressed to root@ and postmaster@ to be received in your primary account.
> 
> Finally hash it.
> 	> postmap /etc/postfix/recipient_canonical
> 
> 4. Add Gmail Username and App password to postfix configuration by creating a sasl_passwd file in /etc/postfix/sasl_passwd and add the gmail id and App password:
> 
> 	[smtp.gmail.com]:587 <username>@gmail.com:<App Password>
> 
> Finally hash it.
> 	> postmap /etc/postfix/sasl/sasl_passwd
> 
> 5. Restart your postfix using
> 
> 	> systemctl restart postfix
> 

You miss some important SASL authentication configs, since in this case Postfix
acts as email client. The SASL recipe is (ignore markdown except bullet
lists):

1. Adjust TLS level for Postfix SMTP client in `/etc/postfix/main.cf` so that Postfix can
   relay emails:

   ```
   smtp_tls_security_level = may
   ```

2. Add SASL settings to `/etc/postfix/main.cf`:

   ```
   smtp_sasl_auth_enable = yes
   smtp_sasl_security_options = noanonymous
   smtp_sasl_password_maps = hash:/etc/postfix/sasl/passwd
   ```

3. Enter SMTP credentials in `/etc/postfix/sasl/passwd`:

   ```
   [smtp.gmail.com]:587		my.email@gmail.com:<app password>
   my.email@gmail.com		my.email@gmail.com:<app password>
   ```

4. Build the password database:

   ```
   # postmap /etc/postfix/sasl/passwd
   ```

5. In case you have multiple email accounts, you can activate sender-dependent
   relay. To do so, append to `/etc/postfix/main.cf`:

   ```
   smtp_sender_dependent_authentication = yes
   sender_dependent_relayhost_maps = hash:/etc/postfix/relayers
   ```

   Add relay servers associated with your email addresses to
   `/etc/postfix/relayers`:

   ```
   my.email@gmail.com		[smtp.gmail.com]:587
   my.email@provider.net	[provider.net]:587
   ```

   Add credentials for your other addresses to `/etc/postfix/sasl/passwd`:

   ```
   my.email@provider.net	my.email@provider.net:<email password>
   ```

   Rebuild the databases:

   ```
   $ postmap /etc/postfix/relayers /etc/postfix/sasl/passwd
   ```

6. Restart Postfix.

Note that if you use SMTPS port (465), you will also need to append
`smtp_tls_wrappermode=yes` to `/etc/postfix/main.cf`.

> - Open the ~/.muttrc
>         - Add the information
> 
>                 set sendmail="/usr/sbin/sendmail"
>                 set envelope_from=yes
>                 set from="Your Name <my.email@gmail.com>"
>                 set use_from=yes
>                 set edit_headers=yes
> 
>                 # IMAP settings
>                 set imap_user = "username@gmail.com"
>                 set imap_pass = "<mailbox password>"
> 
>                 # SMTP settings
>                 set smtp_url = "smtps://username@smtp.gmail.com"
>                 set smtp_pass = "<mailbox password>"
> 

If you have set sendmail, you don't need to set SMTP credentials above,
as Postfix will do the job.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Bagas Sanjaya]

On 3/14/23 19:33, Sumitra Sharma wrote:
>> On Outreachyfirstpatch, there is a pointer to Outreachyfirstpatchalt
>> (which contains instructions on spinning up Ubuntu VM), so you need to
>> install your tools (including postfix and mutt) there if you want to
>> contribute through there. So I think the latter doc should be kept as
>> is.
>>
> 
> Hi
> 
> Can you send me a link to Outreachyfirstpatchalt, I am unable to find
> it.
> 

For your completeness, see https://kernelnewbies.org/OutreachyfirstpatchAlt.

Again, what I mean that OutreachyfirstpatchAlt is about spinning up
Linux VM. If you need follow setting up tools in Outreachyfirstpatch,
you can do that in the VM. So I suggest not to modify OutreachyfirstpatchAlt
for now. (But I wish the slug could be better named as LinuxVMSetup).

When replying to public mailing list, like here and LKML, reply with
"Reply all" button or similar. Do not just hit "Reply", as it will
reply in private.

Sorry for confusion.

-- 
An old man doll... just what I always wanted! - Clara

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Bagas Sanjaya]

[-- Attachment #1: Type: text/plain, Size: 697 bytes --]

On Mon, Mar 13, 2023 at 04:09:34PM +0700, Bagas Sanjaya wrote:
> For MTA, replace the now abandoned esmtp with Postfix. Configure the MTA as
> null client (see [1]). For system-generated emails sent to root and postmaster,
> you will also need to canonicalize these recipient addresses to your email
> address (see [2]).
> 

Hi,

Another thing that I forget to mention is to also configure git to send
patches with Postfix. You need to set:

```
$ git config sendemail.sendmailcmd "/usr/sbin/sendmail"
$ git config sendemail.envelopeSender "auto"
```

See git-send-email(1) for explanation of these knobs.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Sumitra Sharma]

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

> Regards

> Sumitra

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Bagas Sanjaya]

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

On Thu, Mar 16, 2023 at 01:31:16AM -0700, 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. 
> 

OK, please go ahead. You need to link to
https://docs.kernel.org/process/coding-style.html.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Sumitra Sharma]

On Fri, Mar 17, 2023 at 03:51:14PM +0700, Bagas Sanjaya wrote:
> On Thu, Mar 16, 2023 at 01:31:16AM -0700, 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. 
> > 
> 
> OK, please go ahead. You need to link to
> https://docs.kernel.org/process/coding-style.html.
>

Okay! Thank you. But as Fabio wrote I need to get permission from
Alison to get access the outreachyfirstpatch document in write mode.

Regards,

SUmitra

> -- 
> An old man doll... just what I always wanted! - Clara

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Fabio M. De Francesco]

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 

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Julia Lawall]

[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]



On Fri, 17 Mar 2023, 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.

I have the impression that there hasn't been any update for the email
instructions, to show how to receive mail in mutt?  There has been a lot of
discussion in the mailing list, but in the next round the problem will
arise again.

thanks,
julia

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Fabio M. De Francesco]

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.        

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Sumitra Sharma]

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:
> > 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).
>

Hi Fabio

Here it is https://lore.kernel.org/outreachy/20230317175007.GA3275@sumitra.com/T/#u

> 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.        
>

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? 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?

Regards,

Sumitra

> 

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Fabio M. De Francesco]

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

Re: [KERNEL NEWBIES ACCESS] Sumitra Sharma

[Sumitra Sharma]

On Fri, Mar 17, 2023 at 08:24:59PM +0100, Fabio M. De Francesco wrote:
> 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). 
>

Yes, you understand it right. Thanks.


> > > 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).
> 


I did it by mistake. I will take care of it.


> > > 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.
>

If so then what links are we suppose to attach for these wiki updates
while recording the contribution?

> Please wait for her answers about this subject. 
> 

Sure.

> > 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.
> 

Okay! Thank you.

Regards,

Sumitra
> Thanks,
> 
> Fabio
>