New maintainer for PEAR::Auth

Hi, I'm planing to give up the maintenance of PEAR::Auth soon, so I can better concentrate on other PEAR issues. Thus I'm looking for someone to take over the job. This will not only give me more free time, but it will also be vital for Auth, as there will hopefully be some new features implemented, for which I have no time. To become the new lead maintainer, you should at least meet the following requirements: * You have strong experience in PHP and general object oriented software development. * You are willing to actively maintain PEAR::Auth for a long period of time. This includes fixing bugs, maintaining the documentation, responding on user questions and developing a new major version with groundbreaking features. * You are willing to communicate with the developers of the storage containers which in most cases have no CVS access on cvs.php.net and thus will send updates for their container to you. * Ideally you know the source code of PEAR::Auth and the concept behind it. You will get full control over the source code and over the release process and you will be the official lead developer of the package. At the same time, the original authors (me and James Flemer) remain (lead) developers and our credits inside the source code will remain. We are willing to assist you if you have any questions and we will perhaps implement new features or fix bugs from time to time. If you want to take over the job, either reply to the mailing list or even better privately to me. Thanks, -- - Martin Martin Jansen http://martinjansen.com/