Jetpack/Features/2012-03-23

From MozillaWiki
Jump to: navigation, search

Details

  • Time: Friday, 2012 March 23, 9:05 - 9:50am PT (16:05 - 16:50 UTC)
  • Location:
    • Audio/Video: Jetpack vroom
    • Audio Only:
      • US Only: +1-800-707-2533, password 369, conference number 99449
      • US/Intl: +1-650-903-0800, extension 92, conference number 99449
  • Notes: etherpad

Agenda

  • actions from previous meeting
    • gozala to create a branch containing only the loader in preparation for landing it in firefox
    • gozala to finalize proposal for a packageless sdk
    • myk & dietrich to draft mission statement/statement of principles for jetpack features
    • myk to look at packageless proposal and provide feedback once gozala updates it
  • whatever folks want to talk about

Attendees

  • gozala
  • mixedpuppy
  • myk

Minutes

actions from previous meeting

gozala to create a branch containing only the loader in preparation for landing it in firefox

  • didn't manage to get this done yet

gozala to finalize proposal for a packageless sdk

  • gozala updated the proposal
  • got some additional feedback and should still make some changes

myk & dietrich to draft mission statement/statement of principles for jetpack features

  • hasn't happened yet

myk to look at packageless proposal and provide feedback once gozala updates it

schedule for landing jetpack

  • mixedpuppy has been reworking code in share and amigo
  • both of those are without any jetpack in them at the moment
  • talk has been around landing those, unclear if jetpack stuff will beat the landings
  • working without it certainly shows how jetpack is useful to what we do
  • loader, page-mods, page-worker, not having to deal with restartlessness
  • those are the top four parts of jetpack that provide utility to those projects
  • landing the loader is the first step
  • next step is to land apis one by one (or two by two, but process will be iterative)

widgets UX mockups

making the SDK self-hosted

parallelizing api landings

  • can we parallelize api landings so mixedpuppy can land the ones he needs the most?
  • we're trying to avoid landing low-level stuff that we're going to change so people don't use them
  • but anyone who wants to use sdk modules as they are now can have their own namespace where they land them and use them from there
  • mixedpuppy can start using stuff as it lands; once loader lands
  • it would help labs projects quickly generate an addon
  • and maybe some way to identify stuff labs projects do a lot
  • which gozala could consider for landing in the sdk/firefox

extensibility

  • a few times we talked about base classes not being extensible
  • we explored ideas for allowing subclassing while keeping them secure
  • we have now landed a replacement for traits that allows us to do this
  • some modules already have it
  • uses namespaces <http://jeditoolkit.com/2012/03/15/namespaces.html#post>
  • uses Base, a base class that you can subclass
  • sugar to do prototypal inheritance

argentina mozcamp

  • unclear if anyone jetpacky is going
  • canuckistani not going
  • if no one from jetpack is going, maybe mixedpuppy should talk about jetpack
  • canuckistani is organizing road tour after mozcamp
  • possible road tourers: canuckistani, thunder, robert niemann, havi, shez

Actions

  • gozala to create a branch containing only the loader in preparation for landing it in firefox
  • gozala to finalize proposal for a packageless sdk
  • myk & dietrich to draft mission statement/statement of principles for jetpack features
  • mixedpuppy to point gozala at stuff labs projects do a lot with sdk
  • mixedpuppy to identify set of topics to speak about at mozcamp argentina