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

Making WordPress.org noreply at wordpress.org
Mon Mar 19 08:07:41 UTC 2018


#3521: Unify profile badges for all teams
----------------------+-----------------
 Reporter:  danieltj  |      Owner:
     Type:  task      |     Status:  new
 Priority:  normal    |  Milestone:
Component:  Profiles  |   Keywords:
----------------------+-----------------
 Profile badges are a popular thing on the WordPress.org network, every
 team has at least one corresponding profile badge and the requirements to
 earn them vary drastically across all of the teams. I'd like to unify the
 profile badge experience and strictly define how you earn each badge to
 make it clearer and easier for people to earn the badges they deserve.

 The [https://make.wordpress.org/meta/handbook/documentation/profile-
 badges/ meta handbook] explains how you can earn most of them but it
 doesn't go into detail for each one.

 So there are two parts to this ticket:

 1. Improve the explanations of each badge in the table
 2. Create two badges for each team that can be earned (

 Profile badges have become what seems like a sensitive topic, something
 you shouldn't ask about and something that shouldn't bother you if you get
 one. Profile badges show contribution and a dedication to the community.
 '''''It's important to show that contributing for the sole purpose of a
 badge is okay because it's still a contribution, irrespective of the
 original intent.'''''

 So, what can / should we do?

 - Create two badges for each team. For example, accessibility only has a
 team badge (badge with a fill background), so does the training team (what
 what I can see). Test (formerly Flow) doesn't have a badge at all and some
 teams have their team badge as an additional contributor badge such as
 Theme Reviewers or Polyglot Editors so there is quite a lot of
 inconsistency here.

 - Define a clear list of how you earn each badge. An example of this is
 the Core contributor badge is earned automatically by receiving props, but
 the documentation badge is manually assigned based on what seems is an
 unknown, or lesser known set of requirements. Some badges are much easier
 to get than others, which is okay, but the harder to get badges stem from
 what seems is unknown prerequisites.

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

 ''Not directly related to this ticket but share some relevance:''

 - [https://meta.trac.wordpress.org/ticket/1152 Open source profiles theme]
 - [https://meta.trac.wordpress.org/ticket/527 Link badges through to
 teams]
 - [https://meta.trac.wordpress.org/ticket/1312 bbPress contributor badges]
 - [https://meta.trac.wordpress.org/ticket/1313 BuddyPress contributor
 badges]
 - [https://meta.trac.wordpress.org/ticket/1424 Automate meta badge]
 - [https://meta.trac.wordpress.org/ticket/929 Automate training badge]
 - [https://meta.trac.wordpress.org/ticket/2683 Add Marketing badge]
 - [https://meta.trac.wordpress.org/ticket/2312 Automate theme badge]

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


More information about the wp-meta mailing list