On Wed, Jul 20, 2011 at 12:09 PM, Chad <innocentkiller(a)gmail.com> wrote:
Right. Most people who are on CC lists are there
because they asked to
be added. Same thing with being the default assignee. I'm not too thrilled
that this is happening en masse without having the discussion first...
Fair point. I'm less concerned about cc lists than default assignees.
In fact, I think that if someone has been taken off the default
assignee, they should (by default) be put on the cc line if they
haven't already.
As for extensions: they absolutely should always have
a default assignee,
and as a matter of policy I refuse to ever add new extensions to BZ unless
someone is willing to take the assignee role.
I'm not so sure this is the right position. For WMF-maintained
extensions, we may have multiple people who would be logical choices.
For other extensions, we're not going to be able to stop people from
filing bugs once it's in the repository. If we're going to have a
gatekeeper function, I'd prefer that we gate things from getting into
the repository if there's no one to fix bugs. Once the extension is
in our repository, the bugs will get filed, and the result will be
we'll just lose metadata by not letting people enter it.
As Mark and Sumana have both expressed, the assignee should mean something.
Rob