Propose new Mautic features

A working session to prepare the project plan for the Campaign Portability project.

Attendees

• Ruth Cheesley
• John Linhart
• Rahul Shinde

Notes from this meeting

• https://docs.google.com/document/d/15HwRLpwbguR0YeVtX9GuVerdIoj7CD6kZvWvzmfyGj0/edit?usp=sharing project plan outline draft from Ruth
• Discussion on whether we would need API endpoints?
• Yes, we do need to make sure that we can export and import campaigns at the API
• John suggested if we need to export all the other entities, so we could enable those entities to be exported and imported as well.
• How do we take into account things like pluigns which might be connected to a campaign?
• The architecture needs to be extensible so developers can plug into it
• We need to think about dependencies - how do we check if plugins are installed and turned on, how do we know what events are core, and what are from plugins
• Might need to facilitate this by marking campaign events as core or third-party
• Need to think about the version of Mautic as well, as there could be events in newer versions not compatible with older versions.
• Also need to think about themes
• How do we deal with Docker-based deployments where the plugin/theme/campaign is installing dependencies, but it would need to be then added to their docker-compose file - might need to detect and make it possible to copy/paste what needs to be changed (with a send to your server admin option)
• John suggested there should be a dry-run which shows you what is going to happen.
• Maybe we can create a category related to the import, then we could also have the option to undo an import.

Project plan finalised ready for discussing with NLNet.