Services_Ebay package - maintenance ... or more ?

Hello at all the PEAR community! I am new on this mailing-list, so please, let me introduce myself: My name is Edouard, a 21 years old guy living in France, keen on PHP and having proudly passed his ZCE certification 1 month ago. I am studying computer science while working in part-time for a small company that sells shoes on the Internet as a PHP developper. This company also sells its products on the ebay.com website (and others), and I am in charge of creating the listing, retrieving orders, integrating all the stuff in the information system in an automated way... thus I studied the eBay API from top to bottom. Unfortunatly, I didn't know much of the API when I began, so I preferred the "Do it Yourself" way and developed muy own PHP library around the API. Thus I did not use the Service_Ebay package. But now I see that it is unmaintained, waiting for someone, breaking my heart :'( Hereby I would like to propose my help to maintain the package again. But after peering at the source code, and experiencing the most common usages with the eBay API in my job (basic CRUD most of the time), I think that the actual package is a little bit complicated to use and maintain, not to say overwhelming. I say that because the package tried to implement every single call of the eBay Trading API when it's been created (take a look here http://developer.ebay.com/devzone/xml/docs/reference/ebay/index.html) . The problem resides in the fact that eBay works actively on its API, making it evolve constantly over the time, deprecating some calls / parameters, introducting new ones. Those constants changes make it hard to maintain such a big package. The more to maintain, the less to enjoy dive into the code ... Even TurboLister, official eBay software that wraps most of the API trading calls, does not use as many as in the current package! So I propose a new version of the package, a less overwhelming version. Something very simple that wraps the most used API calls in an efficient way (do CRUD with items and orders, following the bids ...). For the rest of the calls, an abstract call would be created, allowing the package's user to implements easily the calls he needs. Of course the whole package would be developped following PHP5 standards with E_STRICT enabled. I don't know if it's in the PEAR philosophy to rewrite a package instead of just update its code. Nonetheless, I hope the community shall consider my request as it is very serious, while being very important for me on a personnal level since it would be my first steps in an official PHP developpers' community. Sincerely yours, Edouard