Labs/Jetpack/Weekly Meeting/2010-04-27

Agenda

• followups from last week
• 0.3 status
• FlightDeck status - (instructions for interacting with py docs parser)
• EM rewrite status
• significant bug fixes
• 0.4/0.5 planning
• roundtable

Minutes

• followups from last week
  • dtownsend: detecting python path (windows/batchfile): half works, will keep on it #558505
• 0.3 status
  • shipped rc2, no news is good news
  • will release as 0.3 tomorrow unless blocker is discovered
  • tree will thaw today
• flightdeck status
  • rearranging DB, preview is up, incorporates bespin support
  • piotr needs docs MD-to-JSON tool from warner
  • dbuc: writing doc comparing development on SDK vs on FlightDesk
• Extension Manager rewrite (dtownsend)
  • held up to avoid breaking mobile branch, hoping to land this week
  • haven't yet thought about backporting to 3.6
  • atul considering testing some actual addons before landing APIs
• bug fixes (dbuc)
  • what's worth going into release notes? nothing came to mind
• 0.4/0.5 planning
  • what do we think is important to get into this pair of releases?
  • Single UI Element (dbuc)
  • catalog API needs for current popular addons, find fine-grained APIs for future (warner)
  • Simple Storage
  • separate thread addons (running jetpack code in separate thread) (atul)
  • tabs API
  • Panels API
  • lifecycle API
  • restartless addons compatibility
  • how to mark firefox-specific packages, how to build cross-app packages
  • how to mark chrome-authority-needing packages (warner)
  • Page Worker API
  • directory of community-created packages (atul)
    • well-defined SDK search path for added packages (warner)
  • JS catch-alls or other tooling to enable security wrappers, maybe Simple Storage (atul)
  • unforgeable JID (warner)
  • SDK test harness HTTP server: allow package tests to use it to test XHR, etc
  • "the other APIs" (misses from 0.3)
  • content exposure module
  • factor out shared code between page mods, context menu, tabs. RE "the active tab"
  • post-release "find and merge similar code" party (atul)
  • code similarity analysis tools (in flighdeck?) (warner)
  • module usage static analysis for package size optimizations ('require' scanner / minimal linker / import-security-enforcement)
  • toolbar button API (phase one)
  • Twitter example third-party API (enable community to create non-chrome components)
  • docs restructuring: tutorial, philosophy, API reference
  • "cfx" tool reference: list of commands, options, on 'cfx docs' webpage
  • docs: change language: split philosophy ("it's not here yet, but here's where we want it to go") from actual-present parts ("this is how it works right now")
  • doc contribution process (from community)
  • logging to in-application console, object introspection in logs (ddahl's work)

Followups

• piotr needs docs MD-to-JSON tool from warner