Re: How long to wait for maintainers?

Erich Enke wrote:

Hello all, light of the past inactivity of the project, I wonder, "How long should I wait?" which in turn begs the question, "Until I do what?"

Wait no longer to maintain your own cvs checkout of SQL_Parser - this way you can easily merge in your changes with any cvs updates from existing maintainers. You can always release your own packages privately for work containing bugfixes.

If I were to be considered as maintainer for this project, I would be willing. Regarding my abilities, IMHO I am well qualified, being a professional programmer who has a heart for doing things the right way. I have read and reread GOF "Design Patterns" for instance. I program daily for work, being our company's coding best-practices guru. Unfortunately, I haven't yet had the opportunity to submit any other patches to PEAR than the two that I included in my bug responses. So, I'm asking the list: 1. How long should I wait until I see activity from the maintainer?

a week or two is reasonable.

2. If that time expires, what should I do to make sure that my patches can get reviewed?

PEAR has a QA group, PEAR-QA, with their own mailing list

3. What would it take to get the group here to trust me and my code? Should I just continue submitting my fixes and active development via enhancement requests on the SQL_Parser bug page? (But how would anyone know if the maintainer isn't monitoring the status of the project?)

Just keep doing stuff, and send messages to pear-qa@lists.php.net if it is ignored. PEAR tends to operate on a slower timescale until you get in the loop. We could use a few more devs on the core package too or on phpDocumentor, do you have a professional interest in either of these packages? ;) Greg