RE: [PEAR-DEV] Wanted: permanent maintainer for HTTP_Request

> Well, as you probably noticed, a new release of HTTP_Request is out > after a long period of inactivity. > > I stepped out to apply pending patches and fix the bugs present in the > package and was granted lead developer rights by Richard Heyes to be > able to make a release and to make further bugfixing releases. > > The problem is, I have enough packages to maintain already and will not > have enough time to dedicate to HTTP_Request development (except for bug > fixes) in the near future. Richard Heyes doesn't have time either and > Christian Stocker already announced that he can't maintain the package. > > Thus a new maintainer who is able to dedicate enough time to the package > is needed. To prevent the situation when a person is assigned as a > maintainer first and then it comes out that he is unable to really do > anything (be it due to lack of time or skill), the potential maintainer > will have to prove himself. There are at least two areas that need a lot > of work and good knowledge of HTTP_Request: First of all, i don't want to be a lead maintainer of HTTP_Request, because i already have already three packages and i even now don't have time to update Payment_Clieop. > 1) Documentation (none currently) Well, somehow i don't get peardoc to work ;-( Whenever i issue the command 'make test', it always (on my system) returns an error in a NNTP package. So, when i have peardoc to work, i can start write documentation for this package (and my own packages). > 2) Unit tests Currently i'm exploring how to use the phpUnit package for these unit tests. But the unit tests for HTTP_Request aren't that easy. Take for an example uploads. Which site allow free uploading of images or other files? Testing the download is easy. Downloading a pear logo from the site will be suffiant. There were also some bugfixes which need to be tested, for example the HTTP 100 continue status. Personaly i never saw this status (excluding RFC2616 ;-) > Whoever does one of these or comes up with another *significant* > contribution to the package will be made a permanent maintainer. I'm using the package to index my own website. This because i have (static) content on disk aswell dynamic content in my database. Again, i'm not willing to take the lead development, so i will help when possible. Regards, Dave