Present: deb, justdavefrank hecker, chris blizzard, chase, josh, ben,
mscott, asa, dbaron, chofmann, myk, jay, chase, dveditz, brendan,
- Developer Preview - Push off the things on our list that can go into a
- cbeard heading things up from a product side
- asa and chofmann from engineering side
- Most of this work for alpha is done work - where will draw the line?
- Shooting to have all Deer park 1.1 work wrapped up for the end of this
- Coordinate what will need to happen for beta
- Alpha - things that matter to developers
- Trunk has seen substantial changes
- Finalise security tasks to get alpha out this week
- mconnor is working on it
- One public regression with a workaround; needs to be fixed in next
- chofmann need to make progress against the list.
- need 2-3 weeks before we do another release
- need that time to do a better job of testing, making the right
changes; review testing process and make changes accordingly
- Asa to work with cbeard and our PR folks to get the community awards
- Asa to write up the proposal and try to get it to MozillaZine this
- Pretty positive board meeting
- Talked about engineering resourcing and scheduling more project
- Is our current interface ultimately the right user interface?
- Not sure what is best for the user
- brendan - amazon search plug in makes a good amount of money, some
kind of non-intrustive highlighting - linked type in effect
- End-user focus
- 1.1 and 1.5
- Talked about DevMo
- What 1.1 might be about
- Structure and governance
- Search relationships
- Consolidation of gains - (infrastructure, localization, and new hires)
- Firefox progress
- Management (product and engineering)
- DevMo (asa would add this as well)
I hate to ask this, but do we happen to know what that might be? Enlightening
the rest of us as to the great and lofty plans would be very much appreciated.
Nothing wrong with asking - but I don't know. The premier reason is that
I wasn't at that meeting, and the secondary one is that it's more a
drivers rather than a staff thing, isn't it?
Fair enough, but is the fact that getting this information out of drivers is
nigh-impossible a staff thing?
Perhaps it would help if drivers@ had a publicly-archived list like
aviary@? Almost all the planning emails sent to aviary-private@ are those
that are also CCed to drivers@ -- this is to keep them both under the same
policy. If there were a drivers-public@, perhaps more of the discussion
would take place on a combination of aviary@ and drivers-public@, where
other people could read the archives, rather than on drivers@ and
aviary-private@, where they can't.
I get the feeling that it may just create another dead list (the public
aviary list has received about 10 messages over a period of 6 months, a
combination of announcements which were also posted elsewhere and a couple
of questions which didn't get answered), with the discussion happening on
the closed lists.
Rather than trying to persuade drivers to have all their discussions in
public (and some of the "public" will inevitably read too much into some
of the things said and get upset...), it would be better for drivers to
reach decisions and then publish them. Of course, if the plans never
reach a "final" state until the events have overtaken them, that's not