Re: Auth_Enterprise

On May 20, 2004, at 10:53 AM, Lukas Smith wrote:

Paul M Jones wrote:

On May 20, 2004, at 10:28 AM, Lukas Smith wrote:

I think we should remove this package. It hasnt seens any public development, or a release to date and its beeing registered since 2003-01-14 22:43:00. http://pear.php.net/package/Auth_Enterprise It just confuses potential new PEAR users.

If, after contacting the developer, he cannot be bothered to make a release, then I think that's a fair course.

As you may have noticed I CC'ed the author.

I failed to notice; well done. So how long does he get to respond?

Someone (hi PEAR Group! :-) should write something down as to how kind

Err, didnt we just move to the RFC system for this kind of stuff?

Is this an RFC issue for the developers, or an opportunity for PEAR Group to state its expectations? You are initiating this as a PEAR Group man, I assume, and not one of the unwashed. Perhaps I am mistaken. If as one of the unwashed, may any developer ask that a package be removed "because it is potentially confusing"? (Yes, this is a devil's advocate position.)

of thing will be handled in future; if not a rule per se, then a statement of expectation and consequences. Having a written statement can only be helpful, in that it means nobody can say they didn't know.

We dont need hard rules, as every package is different .. in size, scope, authors time etc.

Understood, but a list of general expectations can only be helpful, otherwise it looks like (could be perceived as) arbitrary action.

Among the things PEAR needs to remember again, aside from trust, is common sense. I just asked a common sense question to pear dev (and to the author directly in case he doesnt read pear dev.

Common sense is good, but your sense of what is common and mine may disagree (they do not in this case). Your common sense question, to me, reveals that PEAR Group expectations, indeed the community standards, are not spelled out sufficiently in this case. Also, this is not an issue of "trust" to me so much as it is a matter of continuity. If for whatever reason you are unable to perform your PEAR Group duties, a written set of guidelines and expectations (not necessarily rules) will help to ensure that things continue in a similar manner. Persons new to the community will be able to "read in" and refer to the guidelines so they may appropriately construct their behavior. I think this can only be good, but maybe that's just me. -- Paul M. Jones Savant: the simple alternative to Smarty for PHP. http://phpsavant.com/ DB_Table: build RDBMS tables and XHTML forms in one PHP class. http://wiki.ciaweb.net/yawiki/index.php?area=DB_Table Yawiki: your collaborative online documentation system. http://wiki.ciaweb.net/yawiki/index.php?area=Yawiki Yawp: a single-file foundation for PHP applications. http://phpyawp.com/