On 9/14/06, SmileyChris <[EMAIL PROTECTED]> wrote: > > Michael Radziej wrote: > > I'd appreciate if we could find a > > way to state what kind of patches are interesting for the > > committers and what not *before* the patch is created fully. This > > is of course more important for large patches. > > I think this is the core of my underlying concerns of how the tickets > are handled currently. To use GTD terminology, there does not seem to > be distinct lines between what is in the Inbox, Someday/Maybe, Waiting > and Next Actions containers.
I agree with this. The general workflow and responsibility for tickets in the system is a little vague. This situation isn't helped by the fact that anyone (even anonymous users) can modify the state of patches. I think Malcolms idea of a triage team has a lot of merit, and this is exactly the kind of task that I think the triage team should be handling. Most of all, I think we need someone to explicity take ownership of the ticket system; at the moment, issue tracking is being treated very much as a community activity (since anyone can modify any ticket). While ticket reporting should be open to everyone, I don't believe that effective ticket management can be acheived in a free-for-all framework. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
