Jetpack/Contribution

Overview

• Changes should follow the design guidelines for Jetpack
• Changes must follow the code style guide for Jetpack
• All changes must be accompanied by tests
• In order to land, patches must have review from a core Jetpack developer
• Patches should have additional API review when needed
• Patches should have additional review from a Mozilla platform domain-expert when needed

If you have questions, ask in #jetpack on IRC or on the Jetpack mailing list.

How to Make Code Contributions

If you have code that you'd like to contribute the Jetpack project, follow these steps:

1. Look for your issue in the bugs already filed
2. If no bug exists, file one here
3. Make your changes, per the Overview
4. Write a test (intro, API)
5. Attach your code changes and tests in a combined patch to the bug
6. Ask for code review by setting the "review" flag on your attachment to "?" and entering the email of the appropriate developer

Reviewers

• All changes must be reviewed by Atul, until the platform settles
• On top of Atul's review:
  • For review of Mozilla platform usage and best practices, ask review from Drew, Myk or Dietrich (and they can find the domain expert)
  • For API and developer ergonomics review, ask Myk