Re: Right ways to get things done: improving Linux::LVM

If I were you, I'd implement one of the changes (and the corresponding tests), and then send a patch to the module author.

If he incorporates it, go on with the next feature.

If he rejects, discuss the matter, and maybe improve your patch.

If he doesn't response at all, you can still think about taking over or forking the module.

Comment on Re: Right ways to get things done: improving Linux::LVM

Replies are listed 'Best First'.
Re^2: Right ways to get things done: improving Linux::LVM by sandboxed (Sexton) on Apr 15, 2008 at 11:59 UTC
Thank you, moritz! I will follow this way, starting with the easier changes. New questions about testing popped up now, so I will try to clear them through the appropiate Tutorials.	[reply]
Re^3: Right ways to get things done: improving Linux::LVM by moritz (Cardinal) on Apr 15, 2008 at 12:24 UTC
Another good source for testing information is extreme perl. It covers far more than that (it's an entire development model and philosophy), but the sections test driven design and unit testing might be interesting for you (and others).	[reply]
Re^4: Right ways to get things done: improving Linux::LVM by sandboxed (Sexton) on Apr 15, 2008 at 17:41 UTC
Thank you again! After reading a little at Extreme Perl about testing, I think I'll begin with Test::Tutorial, Test::Simple and finally Test::More. The perl debugger will be waiting for me too! UPDATE: The owner of the module didn't reply to my request, so probably it'll be a fork. This will multiply the job to do at least by 20. In a few weeks I'll tell him that I will be obliged to fork the module.	[reply]