Page MenuHomePhabricator

Visually indicate when a Phabricator user is new (Welcome culture)
Open, LowPublicFeature

Description

(Discussed the welcoming culture in Phabricator at Lyon Hackathon 2015 where this was a topic again.)

bugzilla.mozilla.org displays "(New to Bugzilla") in the Comments section next to the names of recently registered Bugzilla accounts, shown to people who are in editbugs. (Downstream Mozilla Bugzilla code ; background discussions)

This could be a helpful reminder to be patient and friendly to our new community members and contributors. But it could also be branding users as "newbies" who might not like that tag.

Implementation could be similar to the "Disabled users" circle shown in front of a user name, and checking via the dateCreated value (currently not exposed) of that account in phabricator_user.
Files that potentially need code changes (or not) are:

  • ./src/applications/maniphest/controller/ManiphestReportController.php
  • ./src/applications/people/storage/PhabricatorUser.php
  • ./src/applications/people/customfield/PhabricatorUserSinceField.php
  • ./src/applications/phid/PhabricatorObjectHandle.php

Old upstream comment about using badges for this (=not applicable): https://secure.phabricator.com/T6526#116150

Upstreamed as https://we.phorge.it/T15675

Details

Reference
bz62324

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 3:05 AM
bzimport set Reference to bz62324.
bzimport added a subscriber: Unknown Object (MLST).

Wikimedia has migrated from Bugzilla to Phabricator. Learn more about it here: https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla - This task does not make sense anymore in the concept of Phabricator, hence closing as declined.

Aklapper renamed this task from Visual indication of newly registered Bugzilla users to Visually indicate when a Phabricator user is new (Welcome culture).May 23 2015, 5:14 PM
Aklapper reopened this task as Open.
Aklapper updated the task description. (Show Details)
Aklapper edited projects, added Phabricator; removed Wikimedia-Bugzilla.
Aklapper set Security to None.
Aklapper edited subscribers, added: Qgil; removed: Unknown Object (MLST).
Aklapper added a subscriber: Bmueller.

Maybe related: Implement "Badges" or "Medals", for annotating special users https://secure.phabricator.com/T6526

Phabricator (Upstream)?

Have we considered this might have the opposite effect: e.g. a giant "user is newb" sign might make the user self conscious

Have we considered this might have the opposite effect

See my sentence above: "But it could also be branding users as "newbies" who might not like that tag."

Upstream comment regarding using the implementation of badges for this: https://secure.phabricator.com/T6526#116150

But it could also be branding users as "newbies" who might not like that tag.

I still think the advantage would be bigger. I find myself clicking task reporter names to check whether it might be the first time they use Phabricator in order to add a "Thanks for taking the time to report this" first sentence to my reply.
If their name had a small star next to their name (or something like that, though that would interfere with the use of stars for Watchlist stuff in MediaWiki) for, say, their first five activities in Phabricator and then the star would get removed, all established users could at least get to know that their actions on the task should even more have an explanation.
Hearing concerns that Phabricator is not welcoming (not only for social but also for technical reasons though as it's a different interface than a wiki), many established users don't have the time to always explain their actions (e.g. just marking a task as duplicate without any further explanation) and such an indicator could at least help creating awareness: "be more patient and consider elaborating".

Why don't we ask the participants of the last GSoC and 2xOutreachy rounds? They have a fresh memory of their first days in Phabricator as a newcomer.

We could also ask to a semi-random sample of actual Phabricator newcomers, say one every five new users in the past 30 or 60 days.

With Conpherence, doing this is quite trivial.

At least we would have other opinions.

Aklapper lowered the priority of this task from Low to Lowest.Feb 9 2016, 9:54 PM

But it could also be branding users as "newbies" who might not like that tag.

I still think the advantage would be bigger.

Good!

If their name had a small star next to their name (or something like that, though that would interfere with the use of stars for Watchlist stuff in MediaWiki) for, say, their first five activities in Phabricator and then the star would get removed

Is there a feature for assigning/removing badges automatically in Phabricator?

Is there a feature for assigning/removing badges automatically in Phabricator?

No.

Then I would decline for now and reopen if/when Phabricator has this feature. Manually maintenance is quite of a blocker here, regardless of the usefulness of the idea.

Moving to the upstream project; task is already lowest priority. (It's still something I'd like to see and we keep tasks open in downstream.)
If this is about reducing the Developer-Advocacy backlog, feel free to remove the project tag.

(This ticket came back to my mind when reading WMF's internal conversations on communication ("ERC").)

IIUC, GitLab only uses a 1 indicator in some circle/star next to the username for someone's first patchset (and not for tasks/issues/tickets etc):

Screenshot from 2021-10-05 11-20-29.png (202×1 px, 27 KB)

For the records, OR criteria in Mozilla Bugzilla (Perl code now at https://github.com/mozilla-bteam/bmo/commits/master/extensions/TagNewUsers ) are:

# users younger than PROFILE_AGE days will be tagged as new
use constant PROFILE_AGE => 60;

# users with fewer comments than COMMENT_COUNT will be tagged as new
use constant COMMENT_COUNT => 25;

If implemented, this visual indicator should also be applied to non-comment actions (e.g. status/assignee changes etc).

Aklapper raised the priority of this task from Lowest to Low.
Aklapper changed the subtype of this task from "Task" to "Feature Request".

I wrote a quick Proof of Concept patch in P52415 which needs further clean up but is probably the most minimal possible?
It adds a star in front of a username link when there's no other decoration ("Availability" or "Unverified" circles still take priority and get displayed instead).

Aklapper moved this task from Backlog to Upstreamed on the Phabricator (Upstream) board.
Aklapper removed a subscriber: Prtksxna.

Not a convincing usecase for upstream.