sethfowler / bzbeaver Goto Github PK

Goal is to provide some interesting numbers and make it easy to answer questions like "what did I accomplish this week / month / quarter?"

Could also consider expanding the cards on mouseover.

Right now we keep the user's password in memory to reauthenticate with Bugzilla. This is unnecessary; we should eagerly retrieve their Bugzilla token, create a BugzillaSession, and then forget the password immediately.

Probably makes sense to put it on the right side of the dashboard. It should show changes since you last looked, like "New comments on bug XXX" or "XXX r+'d your patch on bug YYY".

Clicking the notification should clear it and take you to the bug in question. When it makes sense to do so, we should autoclear notifications - for example, once all new comments for a bug have been acknowledged, we should clear the notification.

There should be a "Clear all notifications" button.

It should be possible to conveniently use bzbeaver from a phone or tablet.

Could monitor for:

(1) Mentions of the user, and treat those as notifications. (Link to an online IRC log.)
(2) Mentions of a bug, and add those to the bug as a second type of comment.
(3) Maybe support other keywords too.

We need a category for bugs that we gave review or feedback for, but which have not been resolved.

Can store them both on specific bugs/requests, and overall on the dashboard.

We need the database for this because without caching this will hammer Bugzilla's servers, since we need to call getUser for every user and each call results in a separate request.

Ideally it would review an applied version of the patch to give full context, and support code navigation via something like DXR.

Could be very handy!

Texting could be supported with UI sugar over emailing, since all major cell providers I know of provide email-to-text gateways.

I think the simplest approach is to have the number of exclamation points equal the number of weeks overdue, with a max of 4.

When you click on a bug (maybe just its comments area?) you should get a full height comments panel in the center of the screen, probably with the rest of the page faded out behind it.

Comments should remain new until you mark them as read. There should be a "mark all as read" button for a bug. We should remember which comments are new in the DB layer.

Add the ability to mark a certain request as one that you're actively working on, and give a special category for these requests. Probably this could work like 'favoriting' a request.

For this project I think AcidState would work well.

See #21.

The current server-side templating is a slow hack. It needs to be replaced with something clean before we start building more complex features.

Zombie bugs are defined as bugs which have status RESOLVED, but either have resolution 'REOPENED' or have new comments.

We need several categories:

(1) Our bugs that are waiting for review or feedback
(2) Bugs that we got review or feedback for, but which have not been resolved

We want the ability to register interest in other users. If we're interested in a user, and they're CC'ed on a bug, we can indicate that by showing their gravatar somewhere on the bug's card.

(1) Let's make code vs quote detection more robust, and improve rendering of code. Can we get syntax highlighting?

(2) Nested quotes aren't handled well right now. Let's fix that.

Not sure at this point how this would work, but it'd be great to have the ability to do things like:

(1) Tell you if a patch needs rebasing automatically.
(2) Push a patch to 'try' from the dashboard.
(3) Push a patch to a repo from the dashboard.
(4) Backout a patch from the dashboard.

I'm thinking that as you scroll down the page, we should have different 'masonry' groups, one for each category. They should be listed vertically in an order that makes sense in terms of urgency (needinfo/feedback/review should be early) and likely size of the category (assigned should be last).

We can have controls (collapse/show for each category, etc.) placed next to the appropriate category.