Taking over a module

Yes, I know, this is off-topic for this list, but my employer terminated
our newsfeed, and I don't like using DejaNews, and I knew that someone
here would have the answer.

I was wondering what the correct procedure is to take over a module
without the approval of the author. I need to make some improvements to
IniConf.pm, and have been unable to get hold of the author, Scott Hutton
([email protected]). I've been trying to contact him on and off for
about a year, so I'm reasonably confident that he's not at that address
any more. (If anyone knows how to get hold of him, please let me know.)
Anyways, failing that, do I just make my changes, and upload the module
to my directory, with appropriate notes that I've taken over maintenance
of it?

For some reason, you're not allowed to add new items to the config file,
which is very irritating. I'm sure that he had a reason for doing this,
since he's very intentionally forbidding it. But perhaps it would be
nice to include an additional method to permit it.

Rich
-- 
http://www.ApacheUnleashed.com/
Lexington Perl Mongers - http://lexington.pm.org/
PGP Key - http://www.rcbowen.com/pgp.txt