From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: linux-kernel@vger.kernel.org, lwn@lwn.net
Cc: jgarzik@mandrakesoft.com,
Andrey Panin <pazke@orbita.don.sitek.net>,
Hans Grobler <grobh@sun.ac.za>,
Andrew Morton <andrewm@uow.edu.au>,
Rasmus Andersen <rasmus@jaquet.dk>
Subject: [ANNOUNCE] The Janitor Project
Date: Thu, 22 Mar 2001 21:52:15 -0300 [thread overview]
Message-ID: <20010322215215.A1052@conectiva.com.br> (raw)
Hi,
The Kernel Janitor's Project grew out of our search for things to help in
the development of the Linux kernel, and learning from other patches
submitted by more experienced people, we saw that some of these patches
indicated error patterns that could exist in other parts of the kernel, we
looked and... yes, we discovered that some parts of the kernel suffered
from the same problems and in the process we found code bitrotting...
I (acme) started maintaining a TODO list for things to fix or clean up and
people started submitting suggestions for things to fix that I collected at
http://bazar.conectiva.com.br/~acme/TODO, looking at the httpd logs I
discovered that _lots_ of people accessed it, so this indeed was something
useful as a starting point for people also wanting to help in cleaning
up/fixing parts of the kernel.
Now we're expanding this so that this continues to be useful, hosting it at
sourceforge to make possible for other people to include more things to
clean/fix.
So, get your broom and start cleaning! 8)
regards,
The kernel-Janitor team.
-------------------------------------------------------------------------
One anouncement is not enough, so here's another one 8)
-------------------------------------------------------------------------
The kernel janitor project has been created at
http://www.sourceforge.net/projects/kernel-janitor
Acme's TODO list is now held there in CVS, and there are also mailing lists
announcing new addtions, and another for discussion.
This project does not replace, but instead compliments the existing janitor
list maintained by Acme. By keeping this in CVS with multiple maintainers,
updates will happen more frequently.
The mailing list will contain many discussions of patches fixing problems
on the TODO, and also explanations of how these things can be fixed.
regards,
The kernel-Janitor team.
-------------------------------------------------------------------------
And yes, the Stanford team work is helping to make the TODO bigger 8)
next reply other threads:[~2001-03-24 0:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 0:52 Arnaldo Carvalho de Melo [this message]
2001-03-27 8:43 ` [ANNOUNCE] The Janitor Project Werner Almesberger
2001-03-26 17:34 ` Arnaldo Carvalho de Melo
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=20010322215215.A1052@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=andrewm@uow.edu.au \
--cc=grobh@sun.ac.za \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=pazke@orbita.don.sitek.net \
--cc=rasmus@jaquet.dk \
/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