curriculum for integrator certification - #16
Conversation
jiteshkhatwani
changed the title
| - LTS designation within a series, and active versus security support windows | ||
| - Extended Long Term Support as a paid, per-instance programme | ||
| - Reading the releases table to select a version for an engagement | ||
| - Mautic's role as a CVE Numbering Authority |
There was a problem hiding this comment.
it's "CVE Naming Authority" https://mautic.org/security/
| - Mautic's role as a CVE Numbering Authority | |
| - Mautic's role as a CVE Naming Authority |
| - [mautic/mautic](https://github.com/mautic/mautic) | ||
| - [The Open Source Definition](https://opensource.org/osd) | ||
|
|
||
| ## Module 2: Git, GitHub, Contribution and Translation |
There was a problem hiding this comment.
The Prerequisites describe "Basic PHP literacy (reading configuration arrays, awareness of Symfony as a framework)", but this section contains a bunch of point that I feel are more geared towards developers (which is why they are described in https://contribute.mautic.org/en/latest/contributing/developer.html, after all...)
| ### Learning Objectives | ||
| - Navigate the Mautic GitHub organisation and identify the repository for a given purpose | ||
| - Fork, clone and branch correctly against Mautic's branching strategy | ||
| - Prepare a pull request that meets Mautic's coding standard, test and documentation requirements |
There was a problem hiding this comment.
Integrators do not need to know how to make actual code changes IMO
| - Coding standards enforced by a pre-commit php-cs-fixer hook installed by Composer | ||
| - Mandatory unit tests, and the PHPUnit, Codeception and PHPStan tooling |
There was a problem hiding this comment.
This is knowledge for Devs, not Integrators
| - System default language, per-user language, and string override files | ||
|
|
||
| ### Official Reference Links | ||
| - [Contributing as a Developer](https://contribute.mautic.org/en/latest/contributing/developer.html) |
There was a problem hiding this comment.
I feel like this should not be "required reading" for Integrators, by definition
| - Doctrine ORM as the schema definition layer and where entities live | ||
| - The metadata builder, its common helpers, and the character cap on string and indexed fields |
There was a problem hiding this comment.
I don't think actual knowledge of ORM should be required for integrators, that is more of a developer thing
|
|
||
| ### Official Reference Links | ||
| - [Mautic Requirements](https://mautic.org/mautic-requirements/) | ||
| - [Entities and Schema](https://devdocs.mautic.org/en/6.0/plugins/database.html) |
There was a problem hiding this comment.
Knowing the schema should be expected for integrators, but this page is clearly geared towards developers
| - [Troubleshooting](https://docs.mautic.org/en/6.0/troubleshooting/troubleshooting.html) | ||
| - [Installing Mautic](https://docs.mautic.org/en/6.0/getting_started/how_to_install_mautic.html) | ||
| - [Command Line Interface](https://docs.mautic.org/en/6.0/configuration/command_line_interface.html) | ||
| - [Doctrine ORM](https://www.doctrine-project.org/projects/orm.html) |
There was a problem hiding this comment.
I don't think actual knowledge of ORM should be required for integrators, that is more of a developer thing
| ### Key Topics | ||
| - DDEV and Docker or Colima prerequisites | ||
| - Starting Mautic with a clone and a single start command | ||
| - Services provisioned: mail catcher, database administration and cache inspection tools |
| - API settings and the default token lifetimes | ||
| - Asset directory placement outside the public web root | ||
| - IP lookup service configuration and the licence key format | ||
| - The tokens reference and why it is not a configuration parameter reference |
There was a problem hiding this comment.
What is meant by "why it is not a configuration parameter reference"?
2 participants
No description provided.