[Zope-dev] Re: [Zope-Coders] Collector Status Meanings

[Chris Withers]

Lennart Regebro wrote:
> I made a quick workflow diagram, and quickly realized that "deferred" 
> actually ends up as a "need more information" state. It is not pending 
> rejection, but pending decision in that case. Of course, that is what 
> the pending state is for...

Yeah, but it's REALLY handy to have a state that indicates more 
information has been requested, and no further action need be taken 
until that information arrives. Furthermore, if that information doesn't 
arrive within a set period of time, the issue is rejected. "Pending 
Deletion" works for me, "Deferred" also works for me, was available and 
didn't seem to be helping in its current use...

> somebody has noticed. So I suggest a "submitted" state, as default state 
> for new issues, and that we change it to "pending" if we need more info, 

I agree with the reasons, btu see my KISS comment earlier w.r.t. number 
of states...

Chris

-- 
Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk