All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Nelson <james4765@cwazy.co.uk>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Introduction...
Date: Mon, 07 Feb 2005 02:51:57 +0000	[thread overview]
Message-ID: <4206D7CD.8060003@cwazy.co.uk> (raw)
In-Reply-To: <4206AF91.9315.17FD337@localhost>

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

Stephen Biggs wrote:
> Greetings all,
> 
> Domen Puncer knows me as "GuestMe" on the IRC channel.
> 
> I would like to introduce myself as someone who wishes to join the 
> kernel-janitors team in order to help out. My hardware is pretty much 
> run-of-the-mill: P4P-800VM motherboard, Pentium IV 2.4GHz, dual-boot 
> with Windows, Fedora Core 3 fully updated as of yesterday, including 
> kernel, 2 IDE drives and one SATA drive, one of the IDE drives being my 
> Linux disk, two DVD drives, one of which writes single-layer DVD, 1394 
> video capture card and an Adaptec SCSI card for a negative scanner.
> 
> Domen has told me that there are only 5 of you?
> 

Dunno.  As regular contributors, maybe.  More people pop in every once in awhile 
(like myself).

> I understand that the TODO list on the website is out of date and needs 
> updating... What are some of the outstanding and high-priority tasks to 
> do that no one has started doing?
> 

Fixing compile warnings.  Especially on unmaintained drivers.  A `make 
allyesconfig && make bzImage 2>warnings.txt` is a great way to start.  There's 
running compiles with the gcc 4 beta, and fixing the new compile warnings that 
generates.  There's also learning how to use sparse, and tackling what it turns up 
(I'm not to that level, tho...).  People are working on them IIRC, but there's a 
lot of work to be done.

Work off of -mm, since most of the janitorial work will go through Andrew Morton's 
series for awhile before being pushed into mainline.  I've had a few times when 
I've duplicated work in the -mm tree, only finding out *after* I sent the patches...

There's always whitespace cleanup.  Unglamorous but helpful.  Not everyone doing 
cleanup works through this mailing list (Adrian Bunk is the most prolific on LKML) 
but it is a good place to start kernel work.

Welcome.

Jim



[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  reply	other threads:[~2005-02-07  2:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06 22:00 [KJ] Introduction Stephen Biggs
2005-02-07  2:51 ` Jim Nelson [this message]
2005-02-07  9:14 ` Stephen Biggs
2005-02-07 11:26 ` Jim Nelson
2005-02-07 13:14 ` Stephen Biggs
2005-02-07 15:35 ` Randy.Dunlap
2005-02-07 21:44 ` Jim Nelson
2005-02-12 22:05 ` Francois Romieu

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=4206D7CD.8060003@cwazy.co.uk \
    --to=james4765@cwazy.co.uk \
    --cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.