Re: [LTP] Contribution to LTP

[Subrata Modak <subrata@linux.vnet.ibm.com>]

Hi Praveen,

On Tue, 2009-05-19 at 13:43 +0530, Praveen wrote: 
> Hi,
> 
>  
> 
> I am a C/Shell scripting Developer. I would like to
> contribute/participate in LTP.
> 
>  
> 
> Please let me know, if I have any opportunity to work with LTP.

You have all the opportunity at your disposal to contribute to LTP. In
fact, we need lots of volunteers to contribute to LTP. As, beginner, the
first thing to do is just watch over the mailing list to find out how
people work. And then there are lots of things in store for you:
(And, off course, first subscribe to this list and this is available on
subscription basis, which is free:
http://sourceforge.net/mail/?group_id=3382),

1) Pick up some area in kernel for which tests do not exist in LTP (Of
course this area should be of your interest). Try to write small tests
for them and submit to LTP. It would be better if you track
http://kernelnewbies.org/LinuxChanges for the changes and start with a
latest stable kernel release,

2) Execute the existing LTP tests on all the machines available to you,
and see if you can hit a LTP/Kernel bug. If it is an LTP issue(s), send
the corresponding patch to the mailing list for review,

3) Make the LTP provision system more better, so that we can be more
efficient/effective in running these tests. You can also work towards
making it more automated.

The present LTP provisioning engine PAN has lots of drawbacks and it is
old. This needs to be updated, or, replaced with something better.
Sometime back Nathan Straz posted some comments on it:

http://fedorahosted.org/collie/
http://marc.info/?t=122540445800003&r=1&w=2,

I need somebody, who can do a feasibility analysis of the advantages of
PAN over collie, and show the fruits of migration from PAN to COLLIE. A
workable version of the patch would also be welcome. The work would be
little tough as PAN has stabilized and we would be resisting any changes
which introduces bug(s) in our existing provisioning environment,

4) Another important aspect would be to improve documentation for LTP.
You can start with by reading individual test cases, understand the code
(you will be assisted with the minimal existent description, so, do not
worry), refer to man pages, google, and improve upon the test case(s)
description. You are free to start from where ever you like.

You are welcome to LTP and i would hope your enthusiasm does not die
down soon ;-)

Regards--
Subrata

> 
>  
> 
>  
> 
> Thanks,
> 
> Praveen Kumar k
> 
> PrimeSoft IP Solutions Inc 
> 
> Phone: 040-27762986/27762987 
> 
> Skype ID: kpraveen72
> 
> www.primesoftsolutionsinc.com 
> 
>  
> 
> 
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables 
> unlimited royalty-free distribution of the report engine 
> for externally facing server and web deployment. 
> http://p.sf.net/sfu/businessobjects
> _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list


------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list