Re: Refinition of proposal orphan process
| From: | Tobias Schlitt | Date: | Tue, 21 Jun 2005 17:07:38 +0000 |
| Subject: | Re: Refinition of proposal orphan process | ||
| References: | 1 2 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-2769@lists.php.net to get a copy of this message | ||
Hi Arnaud Limbourg!
On 06/21/05 18:57 you wrote:
> My idea is
> Proposal we page: QA group can see a little set of radio buttons "warn"
> and "suspend".
> Warn will send a mail to the owner.
> Suspend will mark the proposal inactive and record the date.
> A cron job will delete a suspended proposal that has not been
> reactivated after 15 days.
> The "warn" state could also be reached when a proposal has not seen any
> activity in 30 days, no matter what the state.
Sounds comfortable, but means change of the database structure and more
work because of this... Of course this will last much longer.
I can't see the sense in warning people in draft and proposal stage
anymore, since those proposals can be re-created very easy, if deleted
accedentally.
And of course the warning for finished proposals should be manageable by
hand (and should be much more convenient by hand).
Regards,
Toby
--
Tobias Schlitt - Zend Certified Engineer GPG Key: 0xA6529579
a passion for php http://www.schlitt.info
Like to say "thank you"? - http://pear.php.net/wishlist.php/toby