[wp-meta] [Making WordPress.org] #3521: Unify profile badges for all teams

[Making WordPress.org]

#3521: Unify profile badges for all teams
----------------------+----------------------
 Reporter:  danieltj  |       Owner:
     Type:  task      |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  Profiles  |  Resolution:  invalid
 Keywords:            |
----------------------+----------------------
Changes (by coffee2code):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 There is already the convention for each team to have two badges: a "team"
 badge for being on the team itself (by whatever measure the team decides)
 and a "contributor" badge for contributing to the given team (again, by
 whatever measure decided upon by that team). The team badge is assigned so
 long as the person is an active contributor to the team, and removed once
 that is no longer the case. The contributor badge is permanent once
 assigned.

 The key sentiment from the above is that badges are a recognition on a
 per-team basis. What each team deems as the criteria for their team and
 contributor badges is up to their own team's consensus.

 As to the specific requests raised by this ticket:

 > Create two badges for each team.

 This is largely already the case. There are 15 teams with paired badges
 created. That includes badges for WP-CLI and Hosting (both for each) and
 Training (contributor badge) that aren't meaningfully assigned yet. Only 2
 teams lack only a contributor badge: Accessibility (as you noted) and
 Mobile. And only two teams lack any sort of badge: Testing and Tide.

 Any team wanting either or both of their badges implemented need to have
 one of their team members make a meta.trac request to do so. The following
 information is required:

 * Dashicon for the team
 * Primary color for the badge (the darker color used for the dashicon and
 ring around it)
 * List of users to be initially assigned the given badge(s) (or the means
 by which those users could be obtained)
 * Optional: Programmatically determinable method to assign/remove badge
 going forward, if known and/or possible (basically so a script or plugin
 could be written)

 > Define a clear list of how you earn each badge.

 See #527 (particularly starting at
 [https://meta.trac.wordpress.org/ticket/527#comment:8 comment:8]) for
 discussion on also having each team host a handbook page dedicated to
 their badges.

 I'm in favor of having each team document their own badges in their own
 handbooks because (1) handbooks are documentation for their contributors
 and badges are their team's recognition for contributors and (2) the docs
 for the badges would live where it matters most and with those who would
 need to edit it. Having the badge info somewhere central (e.g. the meta
 team handbook) puts it out of sight and mind of the teams in charge of the
 badges and adds overhead to them being able to get the entries edited.

 The drawback of this approach is getting all 16+ teams to create the badge
 page in their respective handbooks. Having a dedicated ticket for this
 effort would be good, so that any recommendations can be conveyed (for
 instance, suggesting the page be titled "Contributor Badges" or maybe
 "Profile Badges") and perhaps a suggested page layout/template. Then team
 leads could be pinged and progress tracked.

 > Update the meta handbook with a new guide on how to earn every single
 badge currently available.

 For the reasons I cited in response to the previous item, the meta
 handbook shouldn't act as the central hub for badge requirements. The
 [https://make.wordpress.org/meta/handbook/documentation/profile-badges/
 list that currently exists] is sufficient, except we would eventually
 replace the contents of the "Criteria" column with a link to each team's
 handbook page for their badges. From a meta team perspective, we just want
 to list the badges, their icons, their colors, and point users to team-
 specific documentation on how they handle their badges.

 Closing this ticket since only 1 of the 3 suggestions is something we'll
 act on, and that one warrants its own ticket since it would mostly be for
 managing and tracking the efforts of 16+ different teams (and thus should
 be a focused ticket).

 Cheers!

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3521#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org