David, I had read your initial e-mail as let's start filing tracking bugs and fixing issues. I didn't get that there would first be measurement. Thank you for the clarification.
Lawrence ----- Original Message ----- > Lawrence, > Your first course of action, is an end result. In order to get > there we need an information gathering exercise as to what this > performance bar is going to be and what we want to begin > measuring. > > Part of that is the work to get bars of performance for the > system. From what I can tell this "bar" will require input from > many people. > What I imagine is that the "bar" is going to require measurements > from different groups, and then that work to define that bar is > going to be spread out > among different teams. When I mention that the work could be tracked > as part of other meetings, it is to make sure that we don't become > the bottlenecks to progress. > > Hope this makes things clearer. > > > > -David > > > ----- Original Message ----- > From: "Lawrence Mandel" <[email protected]> > To: "David Clarke" <[email protected]> > Cc: "Justin Lebar" <[email protected]>, "Benjamin Francis" > <[email protected]>, "Jonas Sicking" <[email protected]>, "Josh > Carpenter" <[email protected]>, "David Mandelin" > <[email protected]>, "Anthony Chung" <[email protected]>, > "Clint Talbert" <[email protected]>, "Dietrich Ayala" > <[email protected]>, [email protected] > Sent: Wednesday, October 17, 2012 8:02:54 AM > Subject: Re: [b2g] B2G Perf / Stability V1 > > > B2G Performance / Stability V1: > > > > We all know the date is getting near, I wanted to convene a group > > to > > tackle performance / stability issues. > > > > There has been a lot of interest in this topic, so hopefully we can > > make some progress in some of these areas. > > I started filling out an etherpad, generally would like to gather > > different thoughts and ways of approaching this problem. (hopefully > > using as much existing architecture as possible). > > My hope is that we can start the conversation about what needs to > > happen for V1 in the etherpad. > > (https://etherpad.mozilla.org/b2g-perf-v1) > > I am hoping that before end of the week we can have a kick off > > discussion about the items on the list, and begin to arrange some > > sort of priority order around what needs to happen. > > > > My thought is that we want to come out with a set of tracking bugs > > / > > implementation bugs that would be tracked through other processes / > > meetings ( > > Ex: memshrink, slimfast, triage.etc.etc). The idea is not to create > > another tracking meeting, but figure out for V1 what we want to do > > , > > and slot the work into existing processes. > > I think the first course of action is to set a clear bar for > performance of the system. To me this means establishing measurable > goals for the phone and its apps. Once we have the goals we can > measure the current state of the system, come up with strategies for > improving the performance of the system, and file the tracking bugs > that you talked about. > > Lawrence > > > > > > > Drop Thoughts about what needs to happen for V1: > > https://etherpad.mozilla.org/b2g-perf-v1 > > Put your name on the invitee list if you are interested in getting > > a > > direct invite to the meeting. > > > > Setting up a Time to Meet: (Get out to vo te) > > http://www.doodle.com/fgrg9rv43xywmrft > > > > > > > > -David > > _______________________________________________ > > dev-b2g mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-b2g > > > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
