Allow grouping by contributor
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-sponsoring |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
The sponsoring request come from a great variety of people, and the best approaches to interacting with them can also be different.
It would be (for me at least) helpful to easily infer from the main table what type of contributor we are dealing with and allowing to group the results by their identity and other contributor characteristics.
This would have a few advantages I can think of:
1) One could easily start sponsoring a certain person's contributions and have a two-way communication that may turn into a longer lasting sponsoring/
2) It would allow quickly differentiating between experienced developers who do not have upload rights to specific areas or need an extra check from someone, and for these contributors the sponsor can forgo all the welcoming and handholding that a new contributor would appreciate. Also it would show roughly how many people with experience could use an upgrade in their uploading permissions. This differentiation may be inferred from karma but maybe LP does not have enough info to tell number of existing uploads or something more representative of packaging/patching experience.
3) Showing who is a Canonical employee (or regular contributor a public team) would allow most of the time skipping a certain sponsoring entry as those are usually best done by teammates - ex Ubuntu One uploads or Foundation work.
This seems to be a fairly vague proposal.
1. Seems like it could be solved by adding a column that names the uploader of the last patch on the bug, or merge proposer.
2. We don't have a very big developer community. If you sponsor fairly regularly you should know most people in the queue aside from the newcomers / drive-by- contributors. Of course that doesn't scale...
Karma may be useful metric. Highlighting proposals from someone with no ubuntu uploads may also be useful, but I don't know how useful. Personally, I just review everything in the queue, from top to bottom, when I feel like sponsoring.
3. The canonical group isn't visible to non-employees, so this can't be easily determined.