I of the opinion that we have a TODO page on the LTP website, this will
help potential contributers to LTP identifiy areas where they can focus
their development efforts. We can throw ideas on the mailing list and
then formalize this on the LTP web page later. Any thoughts?
Here is a start.
1. Split LTP as follows for easy download and use. Actually debian did
this already in their packaging of LTP, not quite the same as below but
this is my suggestion.
LTP-base (library, pan, tools)
LTP-kernelsyscalls (kernel system call module)
LTP-kernelsubsystem (IO, IPC, FS, ... etc tests module)
LTP-networking (networking related tests module)
LTP-commands (commands related tests module)
LTP-development (development file, include files module)
LTP-documentation (man pages, HTML pages module)
LTP-utils (already exists as a module, coverage tools etc ...)
LTP-misc (miscillaneous stuff module)
Monthly release of LTP may contain the complete LTP package and
will not be
split into individual modules.
2. Code clean up (actually porting). This topic has been discussed time
and time again, flames thrown and the horse beaten to death!. LTP has
code from SGI, IBM, WIPRO, and others. Tons of code! Code is mostly
tested on X86 and sometimes PPC hardware, community can help clean up
(port) for other archs.
3. Assign 3 - 4ppl with code review responsibility, I am sure this will
help Robbie a lot he is over whelmed with patches every hour. The
responsibility can be shared in a round robin fashion. Preferably each
reviewer can have access/expertise with different h.w arch.
4. New test cases for 2.5.x system calls / functionality, tests for
system services and RAS features.