Q1 2021 Mautic Community Roadmap

Community
1

The goal of this quarterly roadmap is to provide clarity for the Mautic Community Teams and our wider community about our priorities for the next 3 months. This will also be shared on Github (as a pinned issue) to ensure that we reach the widest possible audience.

Over time we expect to be planning further ahead, but for now we will start with one quarter at a time. While these are the projects and tasks we’ll be focusing on, life happens and iterations might take place.

We have included, where appropriate, information about how you can contribute to these projects and tasks. Many are very significantly under-resourced at present and would very much value your involvement.

NOTE: All meetings are featured on the Mautic Community Calendar in addition to release dates, contribution weekends, office hours and meetups.

Q1 2021 - January-March

Community Team

Team Lead: Ekke Guembel
Assistant Team Lead: Nico Grienauer
Slack: #t-community
Meetings: Async on Slack, every other Thursday at 1600hrs UTC

Education Team

Team Lead: Leon-Elias Oltmanns
Assistant Team Lead: Favour Kelvin
Slack: #t-education
Meetings: Async on Slack, every other Friday at 1200hrs UTC

Legal & Finance Team

Team Lead - Vacant (Contact: Ruth Cheesley)
Assistant Team Lead - Vacant
Slack: #t-legal-finance

Marketing Team

Team Lead: Radu Zlatianu
Assistant Team Lead: Oluwatobi Owolabi
Slack: #t-marketing
Meetings: Async on Slack, every other Monday at 1800hrs UTC

  • Finish the setup and deploy the Mautic instance for Mautic.org.

  • Related issue/s: [TMAR-40] Get the Mautic Cloud instance up and running - Jira

  • Task owner: Laurine Augiron

    • GDPR re-consent process
    • List import and cleaning
    • Setup and configuration of the instance
    • Start sending newsletters and announcements 1st of March

  • Recruit into the team to have 6 actively contributing members (currently 4 - Radu, Oluwatobi, David & Laurine)

  • Task owner: Radu Zlatianu

  • Content Marketing to start 1st of March with a clear plan and deliverables

Product Team

Team Lead: Norman Pracht
Assistant Team Lead (Development): Mohit Aghera
Assistant Team Lead (Product): Joey Keller
Slack: #t-product
Meetings: Async on Slack, every other Tuesday at 1300hrs UTC

  • Reduce pending PRs from 200 to less than 100 by testing ready to test PRs and adding tests to ready to test but missing tests.

    • Hold a contribution event in advance of each release and work with the Marketing Team to increase the number of contributors attending
    • Review and update the onboarding resources for new contributors

  • Synchronise and align release process with the Docker image to ensure that it remains up to date

  • Become a CNA so that we manage all security issues and assign CVE’s ourselves

  • Task owner: Ruth Cheesley

  • Status: In progress - Ruth Cheesley and Alan Hartless have undertaken the mandatory training and will shortly be moving to the next step in the process

Releases

  • Develop themes for each minor release going forward and structure pending PR’s accordingly

  • Ensure that all releases are made according to the release schedule

  • Ensure that all merged PR’s meet the required quality standards (maintains or improves code coverage, has documentation where required)

Builders Initiative

:warning: Contributors are needed to support this initiative! :warning:

Slack: #i-builders
Meetings: Every Thursday at 1500hrs on Zoom

  • Finalise the GrapeJS builder (email and landing page) for inclusion as an optional plugin in the 3.3 release

  • Work with the Education and Marketing teams to prepare documentation and tutorials for the 3.3 release

  • Iterate on the initial release with the aim to have it ready for testing in the Mautic 4 pre-release packages (Mar-Apr) as the default browser

  • Form a builders tiger team for ongoing management

Composer Initiative

:warning: Contributors are needed to support this initiative! :warning:

Slack: #i-builders
Meetings: Every Wednesday at 0900hrs on Zoom

Related Confluence page: https://mautic.atlassian.net/wiki/spaces/MI/pages/324337710/Composer+Support

  • Decide on folder structure that will be required for Composer Support

  • Prepare a first draft of the proposed implementation for review by the Core Team

  • Prepare PR for consideration in Mautic 4.0 release

Install/upgrade initiative

:warning: Contributors are needed to support this initiative! :warning:

Slack: #i-install-upgrade

Marketplace initiative

:warning: Contributors are needed to support this initiative! :warning:

Slack: #i-mautic-marketplace

Next Generation initiative

:warning: Contributors are needed to support this initiative! In particular, developers with experience in Symfony, API Platform and Angular :warning:

#i-mautic-next-generation

  • Decouple two plugins from core and document the process for others to follow

  • Proof of Concept for front-end (Angular)

  • Proof of Concept for API Platform / Symfony 5 / Assets bundle

Resource management initiative

:warning: Contributors are needed to support this initiative! :warning:

Slack: #i-resource-management

  • Build a team to work on the issues in the project scope

  • Prepare a PR to implement the exporting of campaigns and associated resources

  • Prepare a PR to implement the state of ‘archived’ for resources in Mautic and the associated views that will be required

Project-wide

  • Develop a partners programme to showcase organisations who contribute to the community and offer Mautic services

    • Task owner: Ruth Cheesley

  • Status: In progress

  • Publish a blog post highlighting the future roadmap, Strategic Initiatives and the ‘future of Mautic’

  • Task owner: Ruth Cheesley

  • Status: Not started

3 Likes
3

Composer Initiative

:warning: Contributors are needed to support this initiative! :warning:

Decide on folder structure that will be required for Composer Support
Status: We’re working this. It’s actually a bit broader than a folder structure, but more a packagist / git repository structure issue. We’re foreseeing repositories similar to the Drupal project. The team is working on a good local setup so we can reproduce the complexitites of packagist.org locally and test some structures out.

  • Prepare a first draft of the proposed implementation for review by the Core Team
    In progress

  • Prepare PR for consideration in Mautic 4.0 release
    To be started

1 Like
4

Community Team

Mautic Conference

  • Visual Design overhauled
  • Announcement published
  • Sponsorship open
  • Call for Papers published

Local Communities

  • testing name / URLs
  • Draft document in progress
1 Like
5

Product Team

Successfully achieved

  • Become a CNA so that we manage all security issues and assign CVE’s ourselves. Thanks Ruth and Alan for your amazing work.
  • We have drafted a release community focus for each release. We believe it’s easier to fix issues about email (for example) when you are already working around emails. Also it would help the marketing team to call for contributions by giving a theme.

Still in progress

  • Reduce pending PRs is still an issue, we’re stucked to 200 also thanks to the fact that we have more and more contributions. Nevertheless, we’ve been thinking about giving a focus for each minor release, then we can easier communicate about a community focus (any other topic is also welcomed and included in the version) and probably easier to engage more contributions. See topic here above.
  • Synchronise and align release process with the Docker image to ensure that it remains up to date.
1 Like
6

Marketing Team

Mautic instance in tests
currently testing

Recruit into the team
Joey Keller to join the team
5 members active (Radu, Oluwatobi, Laurine, David, Joey)

2 Likes