Re: PEAR's mission statement - let the fun begin

Terra Frost wrote:

Daniel O'Connor wrote:

To clarify; that's what it felt like the first time I put up a package. It got nitpicked. I know the nitpicking is to maintain quality in pear, but as a newcomer it felt like a huge "go away; we don't care what you've made" I'd much prefer to go through a nitpicking / etc when i'm trying to pass something off as stable.

I think one of PEAR's bigger perks, for developers, is a *@php.net email address. And you don't get this email address when your package is released as stable - you get it when your package has been accepted. You get it when you get a CVS account (which acceptance lets you do). Per that, I don't have a problem at all with nitpicking prior to acceptance. If you want a *@php.net email address, why shouldn't you give PEAR something that it wants (eg. code that confirms to PEARs CS)? Lol and you sent your mail from GMail :)

I think there is a lot of validity in getting nitpicked by the developers and the users also, probably the user more than developers in all honesty! Most users I assume don't install packages that are not in the package list, if they could install ALPHA / BETA packages of all proposals then there is a wider community to give the feedback - this will make the packages better surely, and give some motivation to the developers and steer the package the right way. So I think that allowing all package proposals as long as they meet Alpha standards should be on the list for PEAR install - then to meet stable requirements takes a whole lot more.