[Meego-qa] Default assignee "need-triage at meego.com"
shuang.wan at intel.com
Wed Jun 8 19:29:42 PDT 2011
> > Folks reassign tasks to this account with a comment in the spirit of "I
> > am not the right assignee and I don't care to find the right one" with
> > no follow-up process whatsoever that is known to me.
The bugs in some components are lack of follow up or lack of resources to fix is a critical indicator for project management.
And its nature for default assignee to say it's not his/her scope if it really does. Why we should lose this key input to project management?
And I think this should be fixed at project management level. Assignee has no power to fix resource gap issue.
> Do you agree that this is a problem?
> My proposal is to get rid of the account need-triage at meego.com
> completely. It creates more problems than benefit (actually I don't see
> any benefit at all currently - if you do, please describe).
> Plus to get back to Iekku's initial question: Wasn't a keyword
> "need-triage" the original plan, instead of this account?
No, I don't agree with your proposal to get rid of this fake account.
need-triage at meego.com serves for follow purposes:
1) If a new component is needed but no owner is identified yet, we need a fake account as default assignee temporarily. Bugzilla don't allow empty default assignee when create component.
2) If a bug need further triage or owner is not right then set default assignee to need-triage at meego.com. Keyword is also works for this purpose but not good enough. If the default assignee still keeps in assignee field, generally, others may still think he/she is the bug owner from bug query or bug report. You can't assume all users have the knowledge that she/he need to take a look keyword further. For lack of follow up issue, it's another story.
> Andre Klapper (maemo.org bugmaster)
More information about the MeeGo-qa