From: Anuz Pratap Singh Tomar <chambilkethakur@gmail.com>
To: Jack Winch <sunt.un.morcov@gmail.com>, Rik van Riel <riel@surriel.com>
Cc: kernelnewbies <Kernelnewbies@kernelnewbies.org>
Subject: Re: Introduction & Query on Newbie Website Status
Date: Sun, 2 Feb 2020 23:26:24 +0000 [thread overview]
Message-ID: <CAJnfX5tWqdboxvMJFdJErxeMVzgn652Y6tDoTJFL3W2vaad6zg@mail.gmail.com> (raw)
In-Reply-To: <CAFhCfDaVa2DaDkz44Fvxgh4D2wCanG=J6iEnLzjLOMSpptBW8g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1810 bytes --]
On Fri, Jan 31, 2020 at 11:14 PM Jack Winch <sunt.un.morcov@gmail.com>
wrote:
> Hi All,
>
> Just joined the mailing list (as I will no doubt be calling on the
> community's expertise in the near future). I am looking to get my
> hands dirty with some kernel development - mainly because I want to
> improve my understanding of the kernel and I honestly believe that
> getting involved will be a worthwhile investment of my time and will
> also be highly educational.
>
> Over the next coming months, I shall be undertaking a more structured
> approach to studying and gaining familiarity with the kernel source.
> I will also be looking to get involved in some simple patch
> development (e.g., simple janitorial type jobs), such that I can gain
> some experience of the patch development and submission process. I am
> aware that kernelnewbies.org typically lists some of these types of
> job and that the kernel project has plenty of documentation and tips
> from veteran contributors concerning these topics.
>
> Areas of particular interest to me include:
> - Industrial I/O
> - Device Driver Development
> - 'Real-Time' Systems
> - Time Synchronisation
> - Networking & Communication Protocols
>
> If anyone knows of any newbie projects in these specific areas, then
> it would be great to hear from you.
>
> Lastly, the Kernel Newbies website seems to be unavailable at the
> moment (Google last cached the site on 31 Jan 2020 01:49:1 UTC). Any
> idea when it will be available again?
>
> Rik maintains the website, I think.
ccing him for an answer.
Many Thanks,
> Jack W.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
Thank you
Warm Regards
Anuz
[-- Attachment #1.2: Type: text/html, Size: 2772 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-02-02 23:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 23:12 Introduction & Query on Newbie Website Status Jack Winch
2020-02-01 12:20 ` Cindy Sue Causey
2020-02-02 23:26 ` Anuz Pratap Singh Tomar [this message]
2020-02-03 0:36 ` Rik van Riel
2020-02-03 16:32 ` USB Hid driver Help Lucas Tanure
2020-02-03 20:11 ` Greg KH
2020-02-03 22:00 ` Lucas Tanure
2020-02-04 13:27 ` Lucas Tanure
2020-02-04 18:15 ` Lucas Tanure
2020-02-03 19:49 ` Introduction & Query on Newbie Website Status Jack Winch
2020-02-03 20:10 ` Rik van Riel
2020-02-05 15:46 ` Jack Winch
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=CAJnfX5tWqdboxvMJFdJErxeMVzgn652Y6tDoTJFL3W2vaad6zg@mail.gmail.com \
--to=chambilkethakur@gmail.com \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=riel@surriel.com \
--cc=sunt.un.morcov@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).