Description: ------------ It might that I don't have the permissions to see this on a user page, but it would be good if there was a button to mark a complete user inactive instead of needing to go through all of his packages and mark him inactive in there separately.

My own user profile page should also have a checkbox/button "Mark me as inactive"

The main problem with this (tho I'm not against this being added just to have that clear) is that when a new release is done the user goes active again if he hasn't been put inactive in the xml file but well I suppose we can't change that :)

I'm wondering if we should make this a one go process or persistent option. i.e. I mark me as inactive on my info page, all packages get marked as inactive, Greg releases pearweb and forgets to put me as inactive in the package.xml file 1) pearweb marks me as active again and thus I'd have to mark my self as inactive again 2) because I marked my self inactive globally then pearweb will ignore the value from package.xml and just keep me inactive Wonder which way we should take this feature ?

Really cool would be an automated process: - Dev marks himself inactive on the user page - Someone uploads a package with inactive dev marked as active - PEAR tells him that the user is inactive and the package.xml should be fixed BUT lets him release the package anyway - User gets a mail that he should mark himself active because package had been released with him being active

The "Mark me as inactive" button should lead to a windows-like "do you really really really make yourself inactive?". If the user does this, a mail should go to pear-dev.

I would prefer that if a user is marked as globally inactive, and a package release is uploaded where the user is marked active, that the release be refused. Updating package.xml to set a user inactive is trivial, and the REST files would be inaccurate if we simply ignore it. In terms of how to mark this, we will need to add an "active" field to the users database, and to programmatically cascade if a user marks themself as inactive. If the user then re-awakens and marks themself as active, they would have to manually re-activate each package they intend to re-support.

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.