Proposed changes to workflow bug management

[Reinhard Tartler]

"Emmet Hikory" <emmet.hikory at gmail.com> writes:

>> What does people (specially those in affected teams like ubuntu-archive) think
>> about this [assigning workflow bugs to teams] approach?
>
>     I have three objections to this approach, as follows:
>
> 1)  It is not always the related team that is responsible for the next
> action for these bugs, and in cases where more information is
> requested, not always the last person to work on the bug who ought
> respond.
>
> 2)  As assignment is typically used to indicate "I'm working on this",
> this use of assignment may create the false impression that things are
> in progress which nobody is tracking closely, or for which nobody
> feels specific responsibility, and so are available as general work
> items.
>
> 3)  Due to the way in which launchpad works, notification for
> assignees is very different than notification for subscribers.  As a
> result, such a change further impacts the workflows and teams, and may
> require the creation of supporting mailing lists, etc. in order to
> ensure that team members are receiving mail appropriately.

I fully agree to the arguments given here. TBH, I think we should ask
the launchpad guys to prevent bugs to be assigned to a team. I know the
kernel team is doing this, but I still haven't found out why. Could some
member of the kernel team give a rationale for this please?

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4