Current method for determing team membership is flawed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro patch metrics |
Fix Released
|
Medium
|
Milo Casagrande |
Bug Description
The documentation for the script that is responsible for figuring out LP team membership and updating the patches database says:
In order to generate metrics on patches submitted by team, we pull the
membership data of the Linaro team in Launchpad and store it locally. This is
done by a script which runs a few times a day and uses Launchpad's RESTful API.
This script had to be changed recently due to a permissions change to the
Launchpad user which the script was running as. Now we will only pick up new
users if they submit a patch rather than picking up new users as soon as they
register for a Linaro project on Launchpad.
Given that we aren't using private teams now, it isn't clear why we have a permissions issue or, if we do, we should be able to overcome it by using an account that is made a member of the sysadmins team.
The current mechanism is flawed because until someone in a given team submits a bug, that team appears to be empty, e.g.:
http://
Although there would seem to still be a problem associated with the fact that not everyone publishes their email address on Launchpad, so that would seem to prevent us from associating submitted patches with that particular person as well.
Changed in linaro-patchmetrics: | |
assignee: | nobody → Milo Casagrande (milo) |
Changed in linaro-patchmetrics: | |
milestone: | none → 2013.09 |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in linaro-patchmetrics: | |
milestone: | 2013.09 → 2013.10 |
This was already fixed and deployed in production as well.