WebExtensions/FAQ: Difference between revisions

WebExtensions/FAQ (view source)

Revision as of 23:02, 21 October 2016

229 bytes added , 21 October 2016

m

community question

AmyT

Confirmed users

1,605

edits

@@ Line 5: / Line 5: @@
 These FAQs are in '''draft''' status.
-=== Is it multi-process Firefox compatible? ===
+=== Is it multiprocess Firefox compatible? ===
 Yes, all APIs work with multi process Firefox and are marked as compatible by default.
@@ Line 48: / Line 48: @@
 Some of these are relevant, but come from an FAQ around the decision to implement WebExtensions in August of 2015. They may not still be relevant.
-=== It sounds like you've made decisions without community input, why? ===
+=== How are you involving the community in the development of WebExtensions? ===
-We're just getting started with WebExtensions, and have begun with a set of APIs that are commonly used with Chrome so people can kick the tires. We don't want to be a Chrome copy, and we want to ensure we differentiate while integrating Electrolysis and other initatives into Firefox. To innovate will require input and assistance from the community, which we are actively seeking. The path for WebExtensions will evolve in the coming weeks, months, and years, and we want the developer community to be a big part of that evolution.
+We are actively reaching out to developers to find out what APIs they need to migrate to WebExtensions. This helps us figure out which ones will help the greatest number of developers, and prioritize them accordingly. The goal is to first reach Chrome parity, then go beyond. Anyone can request a new API by [https://wiki.mozilla.org/WebExtensions/NewAPIs filing a bug].
+To make the decision process as transparent as possible, we hold a [https://wiki.mozilla.org/Add-ons/Contribute/Triage public triage] of these bugs every other week. Each one is labeled "design needed", "approved", or "rejected". If approved, additional information on how to write the API is included, and an advisor is assigned. Anyone who is interested in working on it can take it.
 === Why are these big changes needed? ===