Launchpad bug workflow change

[Scott Kitterman]

On Tuesday 19 June 2007 19:28, Henrik Nilsen Omma wrote:
> Scott Kitterman wrote:
> > OK.  I guess I missed the meeting.  Where is this change documented?  Was
> > there a spec?  Anything those of us who were unable to participate in UDS
> > could have seen this coming?
>
> The discussion was scheduled on a public webpage, but the Launchpad spec
> was not public (and thus I have opened a much larger discussion ...).
> I'm CCing the launchpad community contact who might want to comments on
> this.
>
> > Restrictions imposed by the technical change are defacto policy.  If you
> > change the system, you've changed policy.
>
> That is true, but I'd like you to recognise that the policy that you
> suggested above had been imposed (that bugs should not be assigned to
> triagers) is in no way related to this technical change. It is only my
> personal opinion and I've stated that twice.

I understand that now.  Thanks for the clarification.

> >>> I'm not sure how taking away triaging tools aligns with your stated
> >>> goal?
> >>
> >> I think I have helped create more triage tools than I have taken away ;)
> >
> > I have no idea.  I think here you are taking them away for no good reason
> > that I have seen.
>
> What has beene taken away? The ability for anyone with an email address
> to set bugs to In progress and similar. We have also added 3 new bug
> states which I think will be very useful.

Yes.  So now anyone who is not in -dev or -qa that wants to work on a bug will 
need to bother someone else to set the status or not set it and risk 
duplication of effort (or give up on the bureaucracy and go home).  Is there 
evidence that this solves an actual problem?

Sott K