--- a/addon-sdk/source/CONTRIBUTING.md
+++ b/addon-sdk/source/CONTRIBUTING.md
@@ -5,39 +5,29 @@
 - In order to land, changes need a review by one of the Jetpack reviewers
 - Changes may need an API review
 - Changes may need a review from a Mozilla platform domain-expert
 
 If you have questions, ask in [#jetpack on IRC][jetpack irc channel] or on the [Jetpack mailing list].
 
 ## How to Make Code Contributions
 
-To write code for the Jetpack project, follow these steps:
+Follow the [standard mozilla contribution guidelines](https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction). All contributions and patches should be through Bugzilla.
 
-1. Look for your issue in the list of [bugs already filed][open bugs]. If you don't already know what you want to do, we keep a list of [good first bugs].
-2. If no bug exists, [make one][make bug].
-3. Get the code: get a [GitHub][GitHub] account, fork the [Add-on SDK repo][Add-on SDK repo], and clone it to your machine.
-4. Make your changes. Changes should follow the [design guidelines] as well as the [coding style guide].
-5. Write tests: [unit testing introduction][test intro], [unit testing API][test API].
-6. Submit a pull request with the changes and a title in the form of `Bug XXX - description`.
-7. Make sure that [Travis CI](https://travis-ci.org/mozilla/addon-sdk/branches) tests are passing for your branch.
-8. Copy the pull request link from GitHub and paste it in as an attachment to the bug.
-9. Each pull request should ideally contain only one commit, so squash the commits if necessary.
-10. Flag the attachment for code review from one of the Jetpack reviewers listed below. This step is optional, but could speed things up.
-11. Address any issues mentioned in the review.
-
-Finally, once the review is positive, a team member will do the merging
+Pull requests on github are not accepted and new pull requests on github will be rejected.
 
 ## Good First Bugs
 
 There is a list of [good first bugs here][good first bugs].
 
 ## Reviewers
 
-All changes need a review by someone on the Jetpack review crew:
+Changes should be reviewed by someone on the [add-on sdk review team](https://bugzilla.mozilla.org/page.cgi?id=review_suggestions.html#Add-on%20SDK) within Bugzilla.
+
+Others who might be able to help include:
 
 - [@mossop]
 - [@gozala]
 - [@ZER0]
 - [@jsantell]
 - [@zombie]
 
 For review of Mozilla platform usage and best practices, ask [@autonome],

--- a/addon-sdk/source/README.md
+++ b/addon-sdk/source/README.md
@@ -1,10 +1,12 @@
 # Mozilla Add-on SDK [![Build Status](https://travis-ci.org/mozilla/addon-sdk.png)](https://travis-ci.org/mozilla/addon-sdk)
 
+We suggest that developers of new add-ons [should look at using WebExtensions](https://developer.mozilla.org/en-US/Add-ons/WebExtensions).
+
 Using the Add-on SDK you can create Firefox add-ons using standard Web technologies: JavaScript, HTML, and CSS. The SDK includes JavaScript APIs which you can use to create add-ons, and tools for creating, running, testing, and packaging add-ons.
 
 If you find a problem, please [report the bug here](https://bugzilla.mozilla.org/enter_bug.cgi?product=Add-on%20SDK).
 
 ## Developing Add-ons
 
 These resources offer some help: