Skip to content

Update Lifecycle: extension types, workflow, review criteria

bgm requested to merge bgm/dev:lifecycleCriteria into master

I got a bit sidetracked here. I wanted to propose changes to the Review Criteria, but ended up also changing a lot of references to "Official" vs "Contributed" extensions, because there is no such thing (there are Core Extensions and Contributed, and they are not particularly linear).

I think most of the changes are pretty straight forward, but I am proposing to change 4 review criteria:

  • Reviewed Extensions must be CiviCRM extensions (and not a CMS plugin/module). We do not control the distribution of CMS plugins, so it does not feel relevant.
  • Must support translation (wrap strings in ts, but also in a way that it actually works).
  • Must adhere to CiviCRM coding standards
  • Issues are tracked in an open, public issue management system

Merge request reports