Confirm
324
edits
Changes
m
- * Utilize common web developer tools when building extensions - ** Craft examples that show how to use ES6 imports and other features that typically require code transpilation with babel or rollup- * Automatically keep the web-ext tool up to date to avoid bugs - ** Alert the developer if their version of web-ext is out of date- * Offer extension “linting” in code editors - ** Integrate web-ext's existing lint checking feature into popular editors such as Atom, Vim, and Emacs- * Add a new web-ext command that lays out a directory structure for an extension - ** This command would automatically generate a manifest.json file and other common files to help the developer get started on a new extension- * Build a mock WebExtension API for use in automated tests- * Invent a JavaScript library that developers can use to execute tests for their extension without having to launch a web browser
- * Intermediate experience with JavaScript, preferably with some ES6 experience- * Familiarity with the command line environment for NodeJS development- * Ability to communicate in English, primarily in written form
- * Try out the web-ext tool and file a bug if you find one- * Look through WebExtension examples and try them out with web-ext run- * Search for good first bugs in the web-ext repository and submit a patch
→Make WebExtension Development More Awesome: add mentor link, fix bullets
====Make WebExtension Development More Awesome====
* Mentor: [https://mozillians.org/en-US/u/kumar/ Kumar McMillan] (kumar on IRC)
The WebExtension API lets anyone extend and customize their web browser, such as blocking ads on every website they visit. This is an exciting time for the API because it’s now possible to write a single extension that works in both Firefox, Chrome, Opera, and soon IE. At Mozilla we provide several tools and resources to make developing extensions fun and easy but we’d like to make this development experience even better.
The participant would improve the productivity of WebExtension developers in the following ways. Most of these tasks involve changing the web-ext command line tool but others may involve writing documentation or example code.
Contributing to WebExtensions is a great opportunity to empower those who are extending the web!
Desired technical skills:
How to familiarize yourself with the project:
====Build a Library of Inclusion Best Practices and Case Studies====
