... | ... | @@ -3,17 +3,17 @@ |
|
|
### Administrative
|
|
|
|
|
|
* [ ] Required: Code is licensed under AGPLv3+, GPLv2+, LGPLv2+, MIT/X11, or BSD-2c
|
|
|
* [ ] Required: Code is published on github.com or lab.civicrm.org
|
|
|
* [ ] Required: Code is published on github.com or lab.civicrm.org
|
|
|
* [ ] Suggested: Extension uses a short namespace (not org.civicrm.example) ~~Extension name uses "org.civicrm.*" namespace~~
|
|
|
* [ ] Suggested: Bus factor >= 2 (n/a if hosted on lab.civicrm.org)
|
|
|
* [ ] Suggested: Access to project is granted to infra team (n/a if hosted on lab.civicrm.org)
|
|
|
* [ ] Suggested: Access to project is granted to infra team (n/a if hosted on lab.civicrm.org)
|
|
|
|
|
|
### Code
|
|
|
|
|
|
* [ ] Required: All code complies with civicrm-core style guidelines
|
|
|
* ̂[ ] Required: All dependencies are at similar stage (Ex: A stable project should not depend on an experimental project)
|
|
|
* [ ] Required: All dependencies are at similar stage (Ex: A stable project should not depend on an experimental project)
|
|
|
* [ ] Required: All user-visible strings are wrapped in `E::ts()`
|
|
|
* [ ] Suggested: Release schedule is aligned with core
|
|
|
* [ ] ~~Suggested: Release schedule is aligned with core~~ (redundant with "keeping up"?)
|
|
|
* [ ] Suggested: Automated tests execute within 3 minutes (or less)
|
|
|
* [ ] Required: The project does not override PHP or TPL files from civicrm-core
|
|
|
* [ ] Required: The project does not do dangerous modifications the SQL schema of a standard civicrm-core table
|
... | ... | @@ -22,7 +22,7 @@ |
|
|
### Distribution
|
|
|
|
|
|
* [ ] ~~Required: The project is packaged as a CiviCRM Extension, Drupal Module, Backdrop Module, Joomla Extension, or WordPress plugin~~ (don't we only support CiviCRM Extensions for automatic distribution?)
|
|
|
* [ ] Required: The project has a stable version (1.0+; not alpha or beta)
|
|
|
* [ ] Required: The project has a stable version (1.0+; not alpha or beta)
|
|
|
* [ ] ~~Suggested: A demo site is provided~~ (seems overkill?)
|
|
|
|
|
|
### QA
|
... | ... | @@ -30,12 +30,12 @@ |
|
|
* [ ] Required: The project declares, on the in-app extension management screen, the nature of any changes it makes to existing data or functionality.
|
|
|
* [ ] Required: The extension works in all CMS's
|
|
|
* [ ] Suggested: An automated test suite is included
|
|
|
* [ ] Required: Project is periodically re-validated with newer versions of CiviCRM and compatibility updates are published
|
|
|
* [ ] Required: Project is periodically re-validated with newer versions of CiviCRM and compatibility updates are published
|
|
|
* [ ] Suggested: All patches are subjected to peer review (merge/pull-requests validated by another developer)
|
|
|
* [ ] Suggested: All patches are subjected automated tests
|
|
|
|
|
|
### Support
|
|
|
|
|
|
* [ ] Required: The extension provides a clear README.md and info.xml description
|
|
|
* [ ] Suggested: Documentation is published
|
|
|
* [ ] Required: Issues are tracked in an open, public issue management system |
|
|
* [ ] Suggested: Documentation is published
|
|
|
* [ ] Required: Issues are tracked in an open, public issue management system |