DevTools/2011-04-14

From MozillaWiki
Jump to: navigation, search

Meeting Details

  • Thursday Apr. 14, 2010 - 8:00am Pacific, 11:00am Eastern, 15:00 UTC
  • 650-903-0800 or 650-215-1282 x92 Conf# 9364
  • 1-800-707-2533 (pin 369) Conf# 9364 (US)
  • #devtools on irc.mozilla.org for backchannel

Notices

  • Welcome to new folks
    • Cedric, Kyle and Mike
  • Firebug update
    • 1.7.1 coming soon
    • wants to deal with the memory problem
    • Dojo script debugging isn't working because 2 wrappers are not equal
    • in 1.8, they want to get rid of with(FBL) (Firebug Library) and prefix the calls with "FBL."
    • can then clean up the 8000 line FBL file
  • Web Console update
    • Enhancements in Firefox 5
      • console.debug
      • a couple of fixes
    • Planning for 6
      • want to land a bunch of our outstanding patches
      • things we wanted in 5
      • console service, new autocompletion, repositioning, more console object additions
  • Workspaces update
    • Not in 5, should be in 6
    • security review today
    • a few more unit tests needed per review request
    • l10n review needed
  • Highlighter/Inspector update
    • patch in progress
    • e10s part of that in a followup - will try to minimize contact points with content
  • GCLI update
    • nearly working in Firefox, a bit more CSS required
    • expect to have it working in Fx tomorrow
  • New projects kicking off
    • CSS Inspector
    • View source
    • Ace code folding
    • Debugger
    • CSS Doctor soon
  • Landing Ace in
    • Workspaces seems like the first touchpoint for Ace

Roundtable

  • Does rapid release change how features land? (smaller patches = quicker reviews)
    • small bits with tests could always land
    • small patches are good, but landing dead code is not always so good
  • testday for Workspaces
    • might be a little funny since the tool is only useful for people writing code
  • Honza would like to do some e10s experiments
  • dcamp: do we want the devtools repo (http://hg.mozilla.org/projects/devtools) to be a landing queue for our patches?
    • seems like it's cedar just for us
    • can we get more value from the repo?
    • what if we land stuff that's had internal review but is not reviewed for landing in central?
    • which is more valuable: a landing queue or a playground?
    • perhaps we land stuff on devtools so that people can play with features that are almost ready and then do a timed merge to central
  • Google Summer of Code starting
    • Mentoring starts next week