community-contributions.py script should use Launchpad to determine who is not a Canonical employee

Bug #513608 reported by Karl Fogel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

The utilities/community-contributions.py script, which updates https://dev.launchpad.net/Contributions automatically, currently contains a hardcoded list of Canonical employees known to hack on Launchpad, so they can be eliminated from the output (even when they commit from a non-Canonical email address, as often happens for historical reasons).

Instead, the script should use launchpadlib (https://help.launchpad.net/API/launchpadlib) to determine at run-time who is and isn't a Canonical employee. Ideally, it would even be able to figure out when that user joined the ~canonical team in Launchpad, so that contributions made before/after their employment would be counted as non-Canonical contributions.

This bug corresponds to the "XXX" comment above the 'known_canonical_devs' list in the code.

Setting Importance to "Low" because it's fairly easy to just update the script whenever we notice bogus inclusions on https://dev.launchpad.net/Contributions. It's just silly to keep doing that forever when there's a way to solve the problem permanently.

Karl Fogel (kfogel)
summary: - community contributions script should use Launchpad to determine who is
- not a Canonical employee
+ community-contributions.py script should use Launchpad to determine who
+ is not a Canonical employee
Karl Fogel (kfogel)
Changed in launchpad-foundations:
assignee: Karl Fogel (kfogel) → nobody
Curtis Hovey (sinzui)
Changed in launchpad-foundations:
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.