kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Pending work related to kernel for a newbie
Date: Wed, 20 Jul 2016 03:54:30 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1607200351380.30818@localhost.localdomain> (raw)
In-Reply-To: <20160720103729.4844518e@fujitsu>

On Wed, 20 Jul 2016, Aleksander Alekseev wrote:

> Hello, Ashijeet
>
> > I am kernel newbie and I was looking for something to work upon to
> > improve my skill-set. I have good knowledge of C and experience in
> > writing patches. Also please refer me if there is a to-do list for
> > newbies related to pending tasks for linux kernel.
>
> I'm newbie here as well. Still I have an experience of working on some
> other open source projects. I believe the idea is always the same.
>
> First, take a look on project's issue tracker:
>
> https://bugzilla.kernel.org/
>
> Also you could probably review an existing code and propose refactoring
> or optimization patches. Static code analyzers is always a good start
> point. Try looking for typos in comments - you will be surprised how
> many mistakes are there. Usually people like to write code but don't
> like to document and/or test it. Join testing and reviewing new
> patches, try to improve them.
>
> I hope this will help.

  i've mentioned this before ... if you want a safe project that will
still teach you a whole lot about the kernel, improve all the
documentation under the Documentation/ directory. there's a *ton* of
stuff there that is either in need of improving or, in some cases,
deletion because it's so old. or if you're feeling really ambitious,
write some *new* documentation for some subsystem for which there is
none.

  and, finally, you can't screw things up by changing the docs.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2016-07-20  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 16:24 Pending work related to kernel for a newbie Ashijeet Acharya
2016-07-20  7:37 ` Aleksander Alekseev
2016-07-20  7:54   ` Robert P. J. Day [this message]
2016-07-20  8:56     ` sham pavman

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.LFD.2.20.1607200351380.30818@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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).