firefox development process changes

Blake Winton bwinton at
Mon Aug 11 15:25:22 UTC 2014

It’s in progress.  (I’ve got assigned bug data showing up, but haven’t worked on the styling yet.)

In the meantime, you can all use Darrin’s status viewer to get a nice looking view of the data (although it doesn’t support status entry yet).

The code is all in github, and I would happily accept style patches if anyone felt like they had some free time…  :)

Blake Winton   UX Engineer
bwinton at

On Aug 11, 2014, at 11:20, Gavin Sharp <gavin at> wrote:

> We have a bug on file to make some improvements to bsmedberg's tool
> (or a forked version of it) for our purposes:
> I'm not sure what the current plan is there - Blake, do you have an update?
> Gavin
> On Thu, Aug 7, 2014 at 5:40 PM, Blair McBride <bmcbride at> wrote:
>> On 30/07/2014 11:41 a.m., Gavin Sharp wrote:
>>> - We will eliminate the Tuesday status meetings entirely. In their
>>> place, we will ask all team members to provide daily updates via
>>> bsmedberg's status tool. Updates should be short and submitted at the
>>> beginning of your day, and mention what you accomplished yesterday, what
>>> you plan to do today, and anything you're blocked on. Your updates
>>> should include specific status updates for each of the bugs that you're
>>> committed to: "work in progress", "in review", or "landed".
>> Using this again was a bit of a shock, TBH. The visual design, or lack
>> thereof, feels dispiriting at the start of the day.
>> I don't mean that as a trivial thing - it's well established that visually
>> appealing tools result in a more positive and productive experience, and has
>> follow-on effects to other tasks.
>> - Blair
>> _______________________________________________
>> firefox-dev mailing list
>> firefox-dev at

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the firefox-dev mailing list