firefox development process changes

Gregory Szorc gps at mozilla.com
Mon Aug 11 18:35:07 UTC 2014


Sure, Bugzilla, Mercurial, etc aren't the full picture. But looking at 
recent status reports, a large part of content (I estimate >70%) is 
"review bug X," "land bug Y," "code bug Z." This is territory for 
automation.

Large parts of my status reports are generated automatically by [1]. I'd 
much prefer if the status tool asked what I did that wasn't tracked by 
tools (meetings, Vidyo calls, etc). Even then, we could pull that data 
from calendar, Vidyo logs, etc. I just don't want to tell tools things 
they should already know.

[1] 
http://gregoryszorc.com/blog/2014/04/01/using-mercurial-for-status-reports/

On 8/11/14 11:25 AM, Gavin Sharp wrote:
> The short answer:
> - Bugzilla or Mercurial aren't the whole picture
> - even if they were, brief aggregated summaries are useful
>
> Some tooling investment can help with the second, but wouldn't help
> with the first.
>
> Gavin
>
> On Mon, Aug 11, 2014 at 10:52 AM, Chris Peterson <cpeterson at mozilla.com> wrote:
>> As gps asked in bug 1048558, why ask people what they've already done when
>> most of that work is documented in Bugzilla and Mercurial?
>>
>> Google has (had?) a similar system, called "Snippets", that is similar to
>> bsmedberg's Status tool. It has a minimally-distruptive email interface and
>> it is a standard through the whole company. More info:
>>
>> http://blog.idonethis.com/why-google-snippets/
>>
>> http://blog.idonethis.com/silicon-valleys-productivity-secret/
>>
>> chris
>>
>>
>>
>> On 8/11/14 8:20 AM, Gavin Sharp wrote:
>>>
>>> We have a bug on file to make some improvements to bsmedberg's tool
>>> (or a forked version of it) for our purposes:
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1048558
>>>
>>> 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 mozilla.com>
>>> 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 mozilla.org
>>>> https://mail.mozilla.org/listinfo/firefox-dev
>>>
>>> _______________________________________________
>>> firefox-dev mailing list
>>> firefox-dev at mozilla.org
>>> https://mail.mozilla.org/listinfo/firefox-dev
>>
>>
>> _______________________________________________
>> firefox-dev mailing list
>> firefox-dev at mozilla.org
>> https://mail.mozilla.org/listinfo/firefox-dev
> _______________________________________________
> firefox-dev mailing list
> firefox-dev at mozilla.org
> https://mail.mozilla.org/listinfo/firefox-dev
>




More information about the firefox-dev mailing list