Add-ons/SDK

Current Status

• We will continue to support the SDK
• We are not adding new features
• Staff will continue to fix security and other high-priority bugs such as:
  • e10s fixes
  • serious stability problems that affect the browser
• The project will remain open to volunteers and we will hold a regular meeting and triage to keep it open

Tasks

Set up monthly community meeting

• Second Tuesday of every month at 10am Pacific
• Status review
• Bug triage
• Migration
• Any other community concerns

Initial Bug triage

• Triage through all the existing bugs in bugzilla to apply the above criteria
• Bugs that don’t meet the above criteria get closed with a reference back to this doc
• Currently the SDK is on github but patches need to land in mozilla-central. Clarify this somewhere and link it in the bugs.

Stabilize

• Get jpm tests passing
• Get SDK tests passing with e10s
  • There is a tracking bug on this.
• Pull request triage through the pull requests on github to see what we
  • Can move to a bug in mozilla central.
  • Can close.
• See who is available to help
  • [Module ownership]
  • [Contribute docs]
• Clean up documentation to reflect this eg: [Jetpack|Jetpack]

Future

Your input is welcome and appreciated on how to move forward with the SDK.

• There are features in the SDK that will need to start to be deprecated as we move towards e10s, the deprecation of access to XPCOM and XUL, and so on. We will need to build a suitable deprecation plan.
• How can we help move people towards WebExtensions?
  • Have WebExtensions be callable from the SDK?
  • Have the SDK be callable from WebExtensions?
    • Make a wrapper for WebExtensions in the SDK and then throw a deprecation warning each time its called.
  • Specific documentation on how we’d do that.