From: "Máté Eckl" <ecklm94@gmail.com>
To: hacker kernel <thekernelhacker007@gmail.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Fwd: Interested to join in any sub-system as a newbie
Date: Wed, 5 Feb 2020 12:34:46 +0100 [thread overview]
Message-ID: <20200205113446.xu2wkmsplgfhaxkc@sch.bme.hu> (raw)
In-Reply-To: <CA+Jm+AHUQBsn+MXwaDc-ZZ3CMJ9gbyH6uzgTJNCdZuht8mDxKQ@mail.gmail.com>
Hi,
I'm not a maintainer or anything, indeed the only subsystem I consider myself
part of (quite passively, though) is Netfilter. But my suggestion is to specify
a bit more what you are interested in. Looking for just _any_ subsystem won't
serve you for long, I can say from personal experience. Try to find out what you
are most interested in (it was networks for me), and look for a subsystem that
is related to that field. You _will_ need personal motivation when you encounter
errors, Kernel world is tough.
Once you sorted this out, look for the mailing list of the specific subsystem,
this is a good navigation point: http://vger.kernel.org/vger-lists.html although
it might not host _all_ the lists, I'm not the expert on this part of the
community. Subscribe to that list and start following the threads, you can ask
more specific questions there.
If you are really in the discovering phase, you might want to have a look at
Google Summer of Code. Even if you are not a student, you might find interesting
project ideas and have an impression what projects are out there, what the
subsystems need. Although, it's not Linux kernel specific, so you will need time
to filter the possibilities.
Hope this helped.
Bests,
Máté
On Thu, Jan 30, 2020 at 10:59:49AM +0530, hacker kernel wrote:
> ---------- Forwarded message ---------
> From: hacker kernel <thekernelhacker007@gmail.com>
> Date: Thu, Jan 30, 2020 at 10:41 AM
> Subject: Interested to join in any sub-system as a newbie
> To: <linux-kernel@vger.kernel.org>, <newbies@vger.kernel.org>
>
>
> Hi all,
>
> This is Dileep, im a newbie, i would like to contribute in any
> sub-system so that it would help me in learning. please help me in
> taking into your project.
>
> Thanks in advance.
prev parent reply other threads:[~2020-02-05 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+Jm+AGWbHG4U7T7R=6JhzXJywRD4tinDecEKEdfvfzyOkm0dg@mail.gmail.com>
2020-01-30 5:29 ` Fwd: Interested to join in any sub-system as a newbie hacker kernel
2020-02-05 11:34 ` Máté Eckl [this message]
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=20200205113446.xu2wkmsplgfhaxkc@sch.bme.hu \
--to=ecklm94@gmail.com \
--cc=linux-newbie@vger.kernel.org \
--cc=thekernelhacker007@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 read-only IMAP folder(s) and NNTP newsgroup(s).