560329 - Review reminders

Status: RESOLVED DUPLICATE of bug 682847

(bugzilla.mozilla.org :: General, enhancement)

Description

[Mike Kristoffersen (:MikeK)]

This is a follow up bug to a discussion in mozilla.dev.planning "Speeding up reviews" where one of the conclusions made is that we would like to have a system of automatic mailing of reminders if users have pending review requests that they don't follow up on.

It's currently possible to setup whines to do the searches and generate reports, but we would like a more automated system (should still be possible to subscribe/unsubscribe to it).

I suggested extending this system to not only handle review requests, but instead create a regular status mail, something like:

************************************************************

Hi,

this is Bugzilla with your weekly status report:

You have 2 greens, 1 yellow and 1 red this week.

---------
(GREEN)
You are active on 5 bugs, and are doing a great job!

bug1111: Bug descrpition 1
bug2222: Bug description 2
bug3333: Bug description 3
bug4444: Bug description 4
bug5555: Bug description 5

---------
(YELLOW)
Could you have a look at the following 2 bugs that you are assigned to, but haven't touched in more than a month.  Please verify that you still should be assigned to these and that they have enough information in them.  If you are not going to work on them in the near future, please move them back into the pool of unassigned bugs, or pass them on to someone else.

bug6666: Bug description 6
bug7777: Bug description 7

---------
(GREEN)
You have been asked to review the following bug since last time - please review it or estimate when you have time to review it (for the benefit of the project and the poor soul who worked hard on creating a patch).

bug8888: Bug description 8

---------
(RED)
You have one review request that is more than a month old, please don't forget about it.

bug9999: Bug description 9

---------

Statistics:

You closed 3 bugs this week (total 103)
You opened 1 bug this week (total 57)
You are assigned to 5 bugs
Your average time for processing a bug is 20 days 

************************************************************

Comment 1

[Max Kanat-Alexander]

Okay. Well, the "review" flag is specific to bmo. So are you asking for a generic Flag-request reminder system in Bugzilla?

Comment 2

[Mike Kristoffersen (:MikeK)]

Could be, or maybe the bug is in the wrong category?  

I think the consensus is that a feature as described would be beneficial for the Mozilla project, how its implemented is secondary.  Do you have a suggestion for a better category?

Comment 3

[Max Kanat-Alexander]

Oh, well, if it's going to be Mozilla-specific, then it should go into the bmo component, here. If the bmo admins would rather see a generic Bugzilla feature for this, they can bounce it back to us.

Comment 4

[Max Kanat-Alexander]

By the way, my experience with reminder emails like this is that if you send one big email every day to people, they will just ignore it.

A better solution is to send an individual email to people every X days for each flag they haven't handled in Y days.

Comment 5

[Frédéric Buclin]

/me remains out of the noise generated by bmo-specific only requests.

Comment 6

[Mike Kristoffersen (:MikeK)]

Maybe that discussion is better to have in the newsgroup?

Comment 7

[Dan Mosedale (:dmosedale, :dmose)]

DavidA wrote up a tool that extracts data from bmo using an earlier version of Gerv's REST API <https://wiki.mozilla.org/Bugzilla:REST_API> for Bugzilla, and slaps it into a CouchDB instance for further handling.  My understanding is that he no longer has the bandwidth to maintain it, but I suspect he could be convinced to offer up the source code for further development.  Adding him to the CC for his thoughts...

Comment 8

[David Ascher (:davida)]

(maybe off topic, but hey):

The source to my code isn't that useful, but it's available at http://hg.mozilla.org/users/dascher_mozilla.com/bedbug/ to anyone who'se curious.  The lessons learned are maybe more interesting:

1) REST+JSON makes it trivial to export data from bugzilla into couchdb.  Thanks to Gerv for putting together that proxy!

2) bmo export performance on that proxy at least was problematic if one were to consider a semi-realtime feed.  I don't know if that's been fixed.

3) Having a read-only couchdb "mirror" of bugzilla makes decentralized experimentation really easy for webdevs.  Individual devs can maintain clones of parts of the database and do local dev, without having to learn anything more than JS, JSON and REST.  It obviously doesn't make anything easier to someone familiar with bugzilla internals and SQL =).

4) for me at least, having a local JSON store is a lot easier to work with than the bugzilla APIs.  The dev cycle is just much faster if a) I can look at the json data in situ, b) i'm developing against a localhost server, c) all of the oddities of the bugzilla data model are dealt with ahead of time by the couchdb importer.

If I were to move ahead with what I did, I'd "productize" the update.py script which does the cloning, and then explain how to do clones & build sample couch apps.

I would also:

a) not discuss what the review reminders should be and why, I'd just write my own and ask for feedback based on working code =)

b) encourage others to fork my code and implement better versions.

;-)

Comment 9

[Gervase Markham [:gerv]]

See also bug 441775. And https://wiki.mozilla.org/Bugzilla:REST_API:HowTo for comments on how to get details of requests from the BzAPI.

I'm pretty certain you wouldn't need to do a complete export of Bugzilla into CouchDB for this. And you are right, it would be inefficient and laggy.

Gerv