Add-ons/SDK: Difference between revisions

Add-ons/SDK (view source)

Revision as of 21:31, 5 February 2016

275 bytes removed , 5 February 2016

m

update

AmyT

Confirmed users

1,605

edits

@@ Line 1: / Line 1: @@
-= Status =
+= Current Status =
+*We will continue to support the SDK
-'''This is a draft proposal for the Add-on SDK''', of thoughts by andym. It is nothing more than that.
+*We are not adding new features
+*Staff will continue to fix security and other high-priority bugs such as:
-It’s hoped that with community input and collaboration we can clearly communicate to our developers and users where things are in with the Add-on SDK.
-== Current status ==
-The Add-on SDK is in maintenance mode which means the following:
-* security fixes will be applied
-* high priority fixes will be applied such as
 ** e10s fixes
 ** serious stability problems that affect the browser
-* all other fixes
+*The project will remain open to volunteers and we will hold a regular meeting and triage to keep it open
-** should be evaluated or ignored? (understanding that even evaluating those and applying criteria takes time)
-** new features will not be accepted
+= Tasks =
-== Tasks ==
+==Set up monthly community meeting==
+* Second Tuesday of every month at 10am Pacific
+* Status review
+* Bug triage
+* Migration
+* Any other community concerns
-=== Bug triage ===
+== 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?
+* 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. Should we do anything more to clarify this?
+* Currently the SDK is on github but patches need to land in mozilla-central. Clarify this somewhere and link it in the bugs.
-=== Stabilize ===
+== Stabilize ==
 * Get jpm tests passing
 * Get SDK tests passing with e10s
@@ Line 35: / Line 33: @@
 * Clean up documentation to reflect this eg: [Jetpack|Jetpack]
-== Maintenance ==
+= Future =
-There are features in the SDK that will need to start to be deprecated as we move towards e10s, the removal of XUL and so on. We will need to build a suitable deprecation plan.
-=== Tasks ===
-* Monthly public meeting or email to review status
-* Bug triage of any new SDK bugs
-== Migration ==
+==Migration==
-How can we help move people towards WebExtensions?
+*There are features in the SDK that will need to start to be deprecated as we move towards e10s, the removal of XUL and so on. We will need to build a suitable deprecation plan.
-* Have WebExtensions be callable from the SDK?
+*How can we help move people towards WebExtensions?
-* Have the SDK be callable from WebExtensions?
+** Have WebExtensions be callable from the SDK?
-** Make a wrapper for WebExtensions in the SDK and then throw a deprecation warning each time its called.
+** Have the SDK be callable from WebExtensions?
-* Specific documentation on how we’d do that.
+*** 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.