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

[Chris Withers]

Ken Manheimer wrote:
> I think what your saying amounts to "stuff in deferred languishes because
> there's so much of it and nobody looks there, so we should move it to
> pending".

It's not really volume. It's more "stuff in deferred languishes because 
people put it there, then forget about it / move on, and no-one thinks 
to look there, even when they resolve the thing being discussed in the 
issue"

> What i think this will accomplish is make it harder to tell the 
> difference between stuff that's assessed as being deferrable and stuff 
> that's not.  Why would you want to do that?

I want to see more issues resolved in a more satisfactory way. Having 
stuff dumped into a Deferred state doesn't seem to aid this :-S

>>pending with a comment is how this works in practice...
> 
> Evidently not everyone's practice.  

No, evidently not everyone's THEORY ;-)

> I think if deferred were understood 
> and used the way it should be there would be a gain.

Yeah, maybe, for a while, as long as people have a point to prove and 
time to spare. Then it drops back to being an oubliet :-S

> Making things get hidden in Pending, which is worse.

I don't think so, people browse pending, usually from the end backwards. 
They may glace at something there which if in Deferred they would never 
have done. I know if most of the issues I hauled out of Deferred had 
been in Pending, I would have gotten to them months sooner...

> I think if people understood the difference better (thank you for this 
> effort to make that happen!) it would work better.

I think that's a nice theory scuppered by the reality of people's 
limited time and memory...

Chris - me, cynical? naaah ;-)

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