Bug 200435 - Auto-Assigner: Assign to Reporter if reporter=committer and maintainer(s) != committer(s)
Summary: Auto-Assigner: Assign to Reporter if reporter=committer and maintainer(s) != ...
Status: Open
Alias: None
Product: Services
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Some People
Assignee: Bugmeister
Keywords: dogfood, easy, feature, needs-qa
Depends on:
Reported: 2015-05-25 04:12 UTC by Kubilay Kocak
Modified: 2018-02-17 02:34 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Kubilay Kocak freebsd_committer freebsd_triage 2015-05-25 04:12:03 UTC
There is an opportunity to reduce the number of issues added to the "unassigned pool" requiring triage.

Currently if a port is maintained by a committer, it is assigned to that committer. If not, the maintainer is cc'd, leaving the port assigned to freebsd-ports-bugs, ready to be assigned

There is a case where the reporter is also a committer but the maintainer is *not*, these issue should be assigned to the reporter (who can commit and resolve the issue)

In the cases where committer is not a *specific* committer (read: base, ports, docs), this is an incentive to use the reviews system, collaborate outside a specific repository (cross-fertilization), and obtain the requisite approval to commit the change.

For an example, see

* Bug 200145
* https://reviews.freebsd.org/D2600

The auto-assigner could/should also add a comment similar to the following to make it clear what the intent is:

"Assign to reporter, reporter is committer"
Comment 1 Marcus von Appen freebsd_committer freebsd_triage 2015-11-03 07:25:02 UTC
We have committers, who are no legit to commit things to base, doc or ports. If those are now assignees of the bug, they'd have to reassign the bug manually.

Committers with the appropriate rights should be encouraged to grab their own bug reqort instead.
Comment 2 Oleksandr Tymoshenko freebsd_committer freebsd_triage 2018-02-17 02:34:42 UTC
Kubilay is this issue still relevant or current logic is acceptable?