-
Notifications
You must be signed in to change notification settings - Fork 383
Contributing
We'd love to accept your patches and contributions to this project and hope you'll become an ongoing participant in our open source community but we also welcome one-off contributions for the issues you're particularly passionate about.
How would you like to help?
File an issue if you find a bug in the AMP Plugin. Providing details for each section predefined in the issue template is much appreciated!
Project maintainers are regularly monitoring issues and aim to fix open bugs quickly.
File a "feature request" issue if you have a suggestion for a way to improve the AMP Plugin, or a request for a new feature.
We'd love to have your help contributing code and features to the AMP Plugin! Head over to the Engineering guidelines for details on the process you can use to contribute.
Contributions to this project must be accompanied by a Contributor License Agreement. You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of the project. For more information, see the OpenJSF Contributor License Agreement (CLA).
You generally only need to submit a CLA once, so if you've already submitted one (even if it was for a different project), you probably don't need to do it again.
The list of contributors who are featured on the WordPress.org plugin directory are subject to change over time. The organizations and individuals who contribute significantly and consistently (e.g. 3-month period) to the project are eligible to be listed. Those listed should generally be considered as those who take responsibility for the project (i.e. owners). Note that contributions include more than just code, though contributors who commit are most visible. The sort order of the contributors list should generally follow the sort order of the GitHub contributors page, though again, this order does not consider work in issues and the support forum, so it cannot be relied on solely.
The AMP Project accepts responsible security disclosures through the Google Application Security program.
In addition to the Community Guidelines, this project follows an explicit Code of Conduct.
Notice: Please also see the plugin documentation on amp-wp.org