Re: Refinition of proposal orphan process

> Hi guys! > > Since the current process of removing orphan PEPr proposals is much to > hard to maintain, I'd like to propose a redifinition. So, what do you think: > > -- > Proposals in draft and proposl state will no more be warned but > immediatelly deleted after the current time-spans: > - Draft: 10 days > - Proposal: 30 days I would keep the warning, pearweb should make it easy for the qa team to select the state of the proposal and take the necessary actions. 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. > For proposals in finished state which can not be found as registered > packages automatic reminder emails will be send out to the proposer and > pear-qa@ every 10 days after 30 days, as long as a QA-Core member marks > the proposal officially as orphan by the subject tag "[QA-orphan]". I'm not sure I get this one. Arnaud. > -- > > That'll make things much more easy and I will be up with a patch within > some minutes when these changes are accepted publically. > > Regards, > Toby