With a package like Math_Polynomial its a bit harder to get attention since many of use won't be using it, and so don't care all that much about it.
There is that.
A couple weeks seems like a long enough wait for me, but it might have been good to send out a couple emails askings for feedback before moving to voting.
That is a good thing to do when there are no comments.
Yes thins are burearucratic, some people who are involved in PEAR like to be pendantic, thats part of OSS too I guess.
They have to be to some extent. Bureaucracy should be as light as possible though.
I would agree with you, except we've got burned in the paste with people starting a project never getting it to usable point, and then being a pain when someone else tried to get a similar PEAR package in place. So most proposals are at least ready for an alpha release at the proposal time. That being said you code looks far enough along to get accepted, Its not a requirement that every feature is in before exceptance, just that you show you're willing to listen to feature requests.
Indeed.
As such, it seems strange to me that I'd get voted with 0s because of coding style issues ( which are trivial to fix, and could be fixed before a release if they really need to be ).
But hey, whatever, vote for/against the package and whatever happens happens.
Some people are a pain about coding style issues, they review that instead of design or code. Not much anyone can do about that except live with it.
To keep in mind, CS help a lot when you have to read the code of the package and can just do that instead of trying to figure out how it is written :)
Arnaud.