Page MenuHomePhabricator
Create Task
Maniphest T196390

Decide guidelines for creation and how to distribute phabricator badges
Closed, DeclinedPublic
Actions

Description

There's been no discussion of this to my knowledge, so I'm opening a ticket for it.

Currently "futile" badges (especially the "volunteer") are distributed on demand/without any particular scheme (is there any documentation on this subject?).
Couldn't we imagine that they would be distributed automatically, like StackOverflow? What would be the criteria then?
Or do we keep the idea of distributing them on an ad hoc basis, but we still need to have a minimum number of criteria explained somewhere.

Related Objects
Search...

Event Timeline

Framawiki created this task.Jun 4 2018, 4:52 PM
Framawiki triaged this task as Low priority.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 4 2018, 4:52 PM
zeljkofilipin awarded a token.Jun 4 2018, 4:53 PM

The first step could be a draft of the proposed rules in task description. So far, I have awarded a few badges without any process to a few people, including to myself. 😅

Aklapper added a comment.Jun 4 2018, 5:58 PM

Couldn't we imagine that they would be distributed automatically, like StackOverflow?

Is there an upstream feature request about this? Either https://secure.phabricator.com/maniphest/query/advanced/ or https://discourse.phabricator-community.org

Ebe123 subscribed.EditedJun 4 2018, 6:06 PM

There does not seem to be, however automatic badges were in the task for creating the Badges application: https://secure.phabricator.com/T6526, but were not added it seems (and the task is closed)

• Vvjjkkii renamed this task from Decide how to distribute phabricator badges to 1nbaaaaaaa.Jul 1 2018, 1:06 AM
• Vvjjkkii raised the priority of this task from Low to High.
• Vvjjkkii added projects: CheckUser, Connected-Open-Heritage-Batch-uploads (RAÄ-KMB_1_2017-02), Tamil-Sites, Gamepress, Hashtags, Jade, KartoEditor, Language-2018-Apr-June, New-Editor-Experiences, Mail, TCB-Team (now WMDE-TechWish).
• Vvjjkkii updated the task description. (Show Details)
• Vvjjkkii removed a subscriber: Aklapper.
CommunityTechBot renamed this task from 1nbaaaaaaa to Decide how to distribute phabricator badges.Jul 2 2018, 7:59 AM
CommunityTechBot lowered the priority of this task from High to Low.
CommunityTechBot updated the task description. (Show Details)
CommunityTechBot removed projects: TCB-Team (now WMDE-TechWish), Mail, New-Editor-Experiences, Language-2018-Apr-June, KartoEditor, Jade, Hashtags, Gamepress, Tamil-Sites, Connected-Open-Heritage-Batch-uploads (RAÄ-KMB_1_2017-02), CheckUser.
CommunityTechBot added a subscriber: Aklapper.
Aklapper lowered the priority of this task from Low to Lowest.Jul 27 2018, 6:43 PM
Aklapper moved this task from To Triage to Policies on the Phabricator board.Aug 29 2018, 6:36 PM
DannyS712 subscribed.Dec 22 2020, 10:57 AM

It seems like everything but the trust and safety badge (https://phabricator.wikimedia.org/badges/view/13/) is restricted - can I suggest restricting that one too?

Peachey88 subscribed.EditedDec 30 2020, 1:44 AM
In T196390#6707927, @DannyS712 wrote:

It seems like everything but the trust and safety badge (https://phabricator.wikimedia.org/badges/view/13/) is restricted - can I suggest restricting that one too?

It's restricted to acl*sre and acl*security, the latter which you are a member of (via subproject).

DannyS712 added a comment.Dec 30 2020, 1:54 AM
In T196390#6714250, @Peachey88 wrote:
In T196390#6707927, @DannyS712 wrote:

It seems like everything but the trust and safety badge (https://phabricator.wikimedia.org/badges/view/13/) is restricted - can I suggest restricting that one too?

It's restricted to acl*sre and acl*security, the latter which you are a member of (via subproject).

Oh, nevermind then (though perhaps acl*security_team might be better since)

Aklapper added a comment.Jul 11 2021, 6:01 PM

I'd propose to disable badges instead. Less work for everyone.

Peachey88 added a comment.EditedJul 11 2021, 9:04 PM

For the record, This is a list of all our current active and disabled badges (as the other weekend).

I think if badges were to remain, I think we need to develop guidelines around creation going forward (and i've slightly rescoped the task title to match this as I believe it can be completed in the same task), and maybe have the requirements for gaining the badge clearly documented on the badge page.

Badge IDNameDescriptionUsersActive
1Phabricator AdminA Phabricator admin is someone with the ability to edit phabricator settings and generally make sure that everything is running as it should. They also have limited ability to maintain user access, disable troublesome bots and other limited administrative tasks. Phabricator admin abilities are not far-reaching superpowers but the special powers granted, must be applied with care and restraint. A list of current admins is available with this custom search query.8N
2BugwranglerThe bugwrangler, bugmaster or bugmeister is a Wikimedia Foundation employee who coordinates bug management. See Bugwrangler (mediawiki.org) for further details about what this means.1Y
3VolunteerPeople who are proud to call themselves just volunteers for the Wikimedia movement. Well, we are awesome!22Y
4Tea LoverThis user loves tea!2N
5Backport DeployerBackport windows are set times for Wikimedia production deployments, are done by a member(s) of the backport deploy team. All the gory details are on wikitech: Backport windows.16Y
6Chaos MonkeyThe recipients of this badge must earn the distinguished honor by inadvertently breaking a Wikimedia production service using nothing more than the power of Scap.4Y
7JanitorialAwarded to recognize people who help out with keeping our projects and repositories orderly.1N
8Continuous IntegratorThis badge is awarded to show our appreciation to those who make significant contributions of time and expertise to help maintain and improve our continuous integration infrastructure. Thank you, from the Release-Engineering-Team. Your generous and helpful contributions are truly appreciated! Creation context T16120815Y
9Repository AdminDiffusion-Repository-Administrators are people who have volunteered to help maintain the very large number of git repositories for all of Wikimedia's projects. It's a mostly thankless job. It comes with no glory nor groupies. Nonetheless we salute you, Diffusion-Repository-Administrators!1N
10Bug UnravelerThis badge is awarded to those who dedicate themselves to discovering bugs, and have gone through the process of unearthing, studying, and documenting bugs – 1,000 times! This badge is typically held by those that form their livelihood on the collecting of these pesky creatures.3Y
11Train ConductorAwarded to people doing MediaWiki train deploys.7Y
12ResourceLoader module terminatorThis badge will be given to users who do a majestic job on improving performance of Wikipedia by tidying up ResourceLoader modules.4Y
13Trust & SafetyUsers with this badge are members of the Wikimedia Trust and Safety team.13Y
14Nerd SniperThe wily nerd sniper lurks in IRC and shows bug report links to the unwary. If you fail a wisdom check you will end up in their rabbit hole of interesting, but time consuming, misbehaving code. see also: https://xkcd.com/356/, rat catcher6Y
15Rat CatcherA rat catcher risks their personal safety to go down into the dark places where things that go bump in the night live. When this works out well they come back with a story of an epic fight with a hidden foe. When it fails, they just don't come back. Often targeted by a nerd sniper.2Y
16InternOutreachy or Google Summer of Code intern. Present or past.37Y
17Web Perf HeroThis special badge is given by the Wikimedia Performance Team to contributors who have demonstrated initiative in improving the web performance of Wikimedia projects. You care about performance and that's awesome. Thank you, on behalf of the Performance Team! https://www.mediawiki.org/wiki/Wikimedia_Performance_Team/Web_Perf_Hero_award4Y
18MentorOutreachy or Google Summer of Code mentor. Present or past.54Y
19QTEQuality and Test Engineering Team: MediaWiki: QTE Phabricator: Quality-and-Test-Engineering-Team (QTE) Blog: https://phabricator.wikimedia.org/phame/blog/view/21/11Y
20Outreach Program OrganizersWork tirelessly to ensure a successful operation of Wikimedia outreach programs.4Y
21W3C AC repThis is a badge to mark whoever is the Wikimedia Foundation's W3C Advisory Committee representative. This single person represents the Foundation at W3C and casts the Foundation's votes on working group charters, W3C elections, etc. If you would like to be involved in W3C working groups and community groups under the Foundation's membership, please ask that person.1Y
22Deployment Training Graduate✨For successful completion of backport deployment training!✨ …snip… To learn more see: Release-Engineering-Team (Deployment Training Requests)11Y
23Chief Mailmaner1Y
Peachey88 renamed this task from Decide how to distribute phabricator badges to Decide guidelines for creation and how to distribute phabricator badges.Jul 11 2021, 9:05 PM
Peachey88 added a parent task: T106924: Consider using the Badges application for a few special roles to highlight those users' comments.
zeljkofilipin added a project: User-zeljkofilipin.Jul 12 2021, 4:44 PM
zeljkofilipin moved this task from Backlog 🪒 to Watching 📺 on the User-zeljkofilipin board.
zeljkofilipin removed a project: User-zeljkofilipin.Oct 7 2021, 11:05 AM
valerio.bozzolan subscribed.May 1 2023, 11:13 AM
Aklapper closed this task as Declined.Nov 29 2023, 8:42 PM

Or do we keep the idea of distributing them on an ad hoc basis,

That seems to reflect the reality.

but we still need to have a minimum number of criteria explained somewhere.

I don't think so as I don't see a problem so far (apart from meta discussions in T106924 whether badges in general make sense). Established community members (see T106924#9368650 for details) who like to use badges and see some sense in badges can use badges (or userboxes on the wiki). Thus resolving this task.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits