PEAR user 'clay' request & New PEPr Proposal

Hello, I'd like to request that the PEAR account 'clay' be activated with this md5() encrypted password: c4f13f4c3d126ebf332e0d50818b9c28 ... So that I may submit a PEPr Proposal for my SCM_SVN package. I originally requested a PEAR account when I was just getting my feet wet with PEAR -- before I fully realized that I didn't need one at that time. Now that I'm ready to submit a package proposal, I find that I get a "username unavailable"-type error when trying to request a PEAR account with the login of 'clay'. SCM_SVN is a complete OO interface to the Subversion 'svn' command-line client. A draft of the package description from package.xml is below. I feel that the SVN class belongs in its own category, since it's feasible that other SCM (Software Configuration Management/Source Control Management, take your pick) packages may go well with PEAR, such as a SCM_CVS package, etc. Without a SCM category, I'm not sure where the package would be best situated ... I'm open to suggestion on that! : ) More about the package itself: Since SCM_SVN is a complete interface to the svn command-line client, it includes subclasses for both reading from and writing to a Subversion repository, making all kinds of fun stuff possible with version controlled Wikis, PHP-powered Subversion GUIs (either web-based or GTK based), etc. The package is 90% complete, and includes a few examples and tutorials. I plan to create an example for each subclass command, as well as a tutorial for the PEAR online manual that covers several different uses. Package Description from package.xml: What is SCM_SVN? SCM_SVN is a simple OO-style interface for Subversion, the free/open-source version control system. SCM_SVN can be used to manage trees of source code, text files, image files -- just about any collection of files. Some of SCM_SVN's features: * Full support of svn command-line client's subcommands. * Use of flexible error reporting provided by PEAR_ErrorStack. * Multi-object factory. * Source fully documented with PHPDoc. * Stable, extensible interface. * Collection of helpful quickstart examples and tutorials. What can be done with SCM_SVN? * Mix together with the Auth class, Text::Wiki or I18N::Translation2 for a robust, version-controlled website. * Make your source code available to your remote dev team or project manager. * Build your own WYSIWYG web interface to a Subversion repository! Note: Requires a Subversion installation. Subverison is available from http://subversion.tigris.org/ SCM_SVN is tested against Subversion 1.0.1 Please let me know if you need any additional information -- I apologize for the non-standard account situation! Hope it doesn't create too many headaches. Many thanks, -Clay Loveless -- Killersoft.com -- Killersoft.com