Scott Mattocks [2005-01-07 14:53 UTC] I think it would be a good idea to clean out some of the proposals that are sitting in draft and proposed state also. After a few months without any activity it would be nice if PEAR QA encouraged the proposer to move things along or delete the proposal.
Examples:
http://pear.php.net/pepr/pepr-proposal-show.php?id=55
http://pear.php.net/pepr/pepr-proposal-show.php?id=57
http://pear.php.net/pepr/pepr-proposal-show.php?id=64
http://pear.php.net/pepr/pepr-proposal-show.php?id=79
http://pear.php.net/pepr/pepr-proposal-show.php?id=106
bertrand Gugger [2005-01-07 14:59 UTC] And each 100 days, maintainers get a "happy birthday, are you still there ?"
in case they are clever developers,
and they didn't need to answer or comment since 100 days...
Else, since they were responding,
wait 100 days more.
Firman Wandayandi [2005-01-08 11:00 UTC] I think not only proposal, this procedure should be apply on the package too. There are some registered packages has no release yet after few months when i looking for that. Do the action on this proposal and the last QA action is unregistered a package. So no more trash in PEAR.
Examples:
http://pear.php.net/package/Archive_Zip
http://pear.php.net/package/Auth_Enterprise
http://pear.php.net/package/Log_Parser
Alan Knowles [2005-01-11 03:01 UTC] The RFC, deals with issues relating to un-contactable maintainers, but doesnt really deal with the issue of redundant proposals, that should be voted on or deleted. (eg. I'm guessing 1 month without activity, and you get a QA note saying this must be deleted or proposed within 1 months)... or something..
The principle being, they could recreate the proposal later if they intend it to be considered..
|
