Re: Thoughts on PEPr voting frequency

Greg Beaver wrote:

Is there any particular reason why most of you do not participate in the votings? Is it because of the interface? Are you simply not

Yes, it is because I don't even have enough time to maintain all of my packages. I only vote on packages that I feel I can have an opinion based on prior knowledge. I won't vote for or against a package that I don't know anything about and would have to research extensively just to understand what it does :). I can't speak for the others, but for me the rate of new packages is a bit too much to handle effectively, so I apologize if I seem reticent to vote, it's not an indictment of the coding quality.

Greg hits the nail on the head here. I don't want to vote merely for the sake of voting, I want to vote because (a) I understand the problem, (b) I understand the proposed solutions, and (c) I have analyzed the proposed solution, at least in a cursory manner, and feel I know enough to say with some authority that "yes, this is a good PEAR addition" or "no, this should not be in PEAR as it is". To vote without some reasonable knowledge and analysis is somewhat irresponsible, I think. Additionally, unless a particular package is of direct or near-term interest to me, it's not a priority to learn enough about it make an intelligent vote. Additionally, Martin says this:

hey, you all are part of PEAR and you should be aware of what is added to _your_ project.

I regard "my" part of the PEAR project primarily as the stewardship of my packages in PEAR according to the published standards, and indirectly their relationship to the other packages in PEAR (e.g. DB_Table, and then its relation to HTML_QuickForm). -- pmj