1074350 - "new to bugzilla" indicator should be removed when a user is added to 'editbugs', not 'canconfirm'

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Extensions, defect)

Description

[Lukas Blakk [:lsblakk] use ?needinfo]

I'm not certain what the current criteria is for disabling the "new to bugzilla" signifier but in my blog post (http://lukasblakk.com/new-to-bugzilla/) on recent observations with new contributors I've come up with some criteria as I believe the “New to Bugzilla” flag does not stay up long enough. 

Here's what I recommend, that we should have it stay up until the following criteria are met:
* The person has made at least 10 comments
* The person has put up at least one attachment
* The person has either reported, resolved, been assigned to, or verified at least one bug

Comment 1

[Lukas Blakk [:lsblakk] use ?needinfo]

I also wonder if implementing something like this would be a potential 'good first bug'?

Comment 2

[Mike Hoye [:mhoye]]

Hmmm, could be! DKL, what do you think?

Comment 3

[David Lawrence [:dkl]]

The current criteria for being tagged as NEW is:

1. user is not in 'canconfirm' group
2. profile is less than 60 days old
3. and they have made less than 25 comments

Creating a new bug and adding a new attachment normally also adds a comment so that makes a difference. Other changes, the user may not make a comment. But typically the user loses the tag after 60 days anyway.

So from comment 0, it looks like we would shorten the time rather than lengthen it or do I misread?

dkl

Comment 4

[Justin Dolske [:Dolske]]

All of those criteria are needed for a user to be marked as "new"? I'd guess that canconfirm is what's tripping things up here, if new users were granted this privilege early. Maybe just remove that criteria?

Seems like the way people effectively stop being "new" is more a result of time and activity. So from that perspective, canconfirm is orthogonal. It would make more sense with editbugs (since people should be somewhat experienced before needing that), but I think part of the point of http://lukasblakk.com/new-to-bugzilla/ is that there's still value in erring on the side of tagging people as new. It's a cue that they might need a little more help/patience and people should make an extra effort to be welcoming to a new contributor.

Comment 5

[Liz Henry (:lizzard) (relman/hg->git project)]

It could be my fairly liberal granting of canconfirm you're running into Lukas. I don't hand it out that often but I do grant it to new bug triagers who show they understand the basics and aren't going to be too reckless with it.  You can always have a look at their user profile (click on their name in comments) to see recent and total activity. 

I agree with Justin that having canconfirm shouldn't remove the "New to Bugzilla" flag.

Comment 6

[Lukas Blakk [:lsblakk] use ?needinfo]

Thanks all - definitely don't want to shorten the time so it must be the canconfirm.  Liz, is that always manually set on people?  Any way to automate instead (or get you reports of potential no-longer-new so perhaps viable canconfirmers)?

Comment 7

[David Lawrence [:dkl]]

(In reply to Lukas Blakk [:lsblakk] use ?needinfo from comment #6)
> Thanks all - definitely don't want to shorten the time so it must be the
> canconfirm.  Liz, is that always manually set on people?  Any way to
> automate instead (or get you reports of potential no-longer-new so perhaps
> viable canconfirmers)?

In addition to those like Liz who have admin rights to the 'canconfirm' group, we also have the [e-mail] address that people email asking us for extra perms such as 'canconfirm' and 'editbugs'.

https://bugzilla.mozilla.org/page.cgi?id=get_permissions.html

dkl

Comment 8

[Liz Henry (:lizzard) (relman/hg->git project)]

People generally ask me for canconfirm or editbugs. Not very often; maybe once or twice a month. I also offer it when I follow up with someone who came to a test day or training.

I would love a report that shows me new Bugzilla accounts that have taken more than a few actions within a particular time span but that is something for another request, I think.   Automatically granting canconfirm doesn't seem like a great idea. But we could automatically let people know how to ask for it.

Comment 9

[Justin Dolske [:Dolske]]

(In reply to Liz Henry :lizzard from comment #8)

> I would love a report that shows me new Bugzilla accounts that have taken
> more than a few actions within a particular time span but that is something
> for another request, I think.   Automatically granting canconfirm doesn't
> seem like a great idea. But we could automatically let people know how to
> ask for it.

A mechanism to find active non-canconfirm accounts sounds like a good idea -- new bug? ;-) I suspect there's a big social aspect to a contributor being told "hey, good job, here's an extra capability/recognition" (ideally in more words than that). +1 to getting better at finding those users.

Comment 10

[Liz Henry (:lizzard) (relman/hg->git project)]

Right on. I filed bug 1075798 for a (new) user activity report.

Comment 11

[:glob ✱]

To ssh://[e-mail]/webtools/bmo/bugzilla.git
   1030251..e8a33a1  master -> master