From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Ujjwal Kumar <ujjwalkumar0501@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] Evaluate and Improve checkpatch: general doubts about project
Date: Wed, 9 Sep 2020 08:45:46 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2009090839110.5622@felia> (raw)
In-Reply-To: <a5104e46-c652-ce52-3604-c33000234718@gmail.com>
On Wed, 9 Sep 2020, Ujjwal Kumar wrote:
> Hello Lukas,
>
> I'm Ujjwal Kumar, and this is my first mail to the community :).
>
> Recently I came across the following project on Community Bridge:
> "Linux Kernel: Evaluate and Improve checkpatch.pl"
>
> I'm interested in the project (as I think of it as a head-start for me with
> Linux kernel development).
>
> While I was going through prerequisites and mailing list archives, some doubts
> came to my mind. These are:
>
> 1. The prerequisite says: "Show that you are able to modify checkpatch.pl and
> get a change accepted in the community". Because I'm a bit late I am wondering
> if it is even possible to get a patch accepted and hence to complete the
> prerequisite. As you are not familiar with my abilities and knowledge, please
> consider answering this based on your experience.
>
You will need to be experienced with perl, basic English writing skills,
and need to show some basic scientific thinking, i.e., understand how to
evaluate a change on a larger dataset to estimate pros and cons.
> 2. I already see some people working around the project, so I have this
> specific doubt. Does the nature of this particular project allow selection and
> hence the contribution of more than one mentee?
>
The project provides different areas of focus and there is enough work and
investigation to look into. Multiple mentees can be mentored on this
project.
The selection is based on the most promising learning curve and the
mentee's ability to structure and show that they can identify an issue and
find reasonable solutions through the discussion with the mentor and the
community.
The first task is to set up a working environment that allows contribution
of changes to the kernel community and the follow-up discussion.
Lukas
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-09-09 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 3:46 [Linux-kernel-mentees] Evaluate and Improve checkpatch: general doubts about project Ujjwal Kumar
2020-09-09 6:45 ` Lukas Bulwahn [this message]
2020-09-09 9:17 ` Ujjwal Kumar
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=alpine.DEB.2.21.2009090839110.5622@felia \
--to=lukas.bulwahn@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=ujjwalkumar0501@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 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).