Decide how to allocate a badge to a particular team or contribution type for reporting purposes

[adamlofting]

For example in adhoctribution, each contributor action is logged:

• against a team: https://github.com/adamlofting/adhoctribution/blob/master/views/partials/logging/select-teams.handlebars
• As a type: https://github.com/adamlofting/adhoctribution/blob/master/views/partials/logging/select-type.handlebars

Any Mozilla member of staff can log contribution to any team and contribution type (the team is not linked to the logged in user).

But the benefit of this is we can show contribution graphs for individual teams, and provide some basic grouping about what types of contribution drives a teams number (ie is it code contribution, or volunteering at events). E.g. http://adamlofting.github.io/mofo-contributors-dashboard/?team=opennews

---

This grouping is for our reporting rather than relevant to the badge recipient, so I would suggest this is a mapping we maintain between a given badge type and our teams.

Could these be a additional fields you set in mozbadges when you create a badge?

[adamlofting]

Following chat with @davidascher , I will move the teams list from Adhoctribution into a separate location that can be used by both of these apps. That task is tracked in Bugzilla here: https://bugzilla.mozilla.org/show_bug.cgi?id=1017677

[adamlofting]

I've just setup a place to store this file, and some example data in case you want to start anything on this today: https://github.com/mozilla/team-list/

[adamlofting]

@christensenep I added a node module to this today that you can install via npm to consume the gh-pages maintained list within badge apps: https://github.com/mozilla/team-list/tree/gh-pages/node

[adamlofting]

This isn't going to ship today. This is dependent on the conversations about who can create and issue a contributor badge and what level of permissions the system needs vs what level of training explanation goes with the system.

[adamlofting]

I'm going to make a call on this and change the scope.

Contribution type isn't required for two reasons:

• Baloo database and reporting doesn't require this
• The badges are granular so queries can be built after the fact by selecting a group of badges

For teams, I suggest we do this.

• A badge can be associated with a team, if the badge author has permission to do this.
• This does not affect the badge itself, but is a relational mapping we can use to report on badge metrics by team.
• The list of teams should be pulled from and maintained here: https://github.com/mozilla/team-list/

I'll file this as a separate action for the build.