We are excited to announce that the Mautic 7 Columba edition beta version is now available for public testing!

With Mautic 7, we are focused on removing outdated code and functionality to ensure Mautic remains secure and performant aligned with modern coding standards, while also delivering more improvements and features to Mautic.

We’ve worked really hard to get to this point – a huge thanks to all the community members who have contributed to the release!

IMPORTANT NOTE:

This is a pre-release, which means it should never be used in a production environment. At this stage we do not test the upgrade path nor do we guarantee upgrading from Beta to later versions. 

Please only use it in testing environments, and report back your findings.

The major release focuses on a major update to Symfony 7, but it also brings several user-facing changes and some changes that are relevant for developers. Read on for more information.

What’s new in Mautic 7 Beta Columba Edition?

User-facing changes

• Improvements to user experience for scheduled sending of emails (#14254)
• Improvements in bounce recognition for Outlook and Exchange (#15371)
• New slider form field type (#15332)
• Improvements in user experience for text message and web notification previews (#15410 and #15247)
• Add Projects support for stages, dynamic web content and points (#15409)

Developer-facing changes

• API Platform implemented (see /api/v2) (#14812)
• Ability to define multiple mailer DSNs (#14254)
• Ability to replace DB cache with Redis or similar service (#15554)
• Add events in the Projects bundle to allow bundles/plugins to extend entity type to model key mappings (#15485)
• Projects unified in API endpoints (#15507)

Download Mautic 7 Beta and help speed up the releases

All these exciting new features and code improvements now need to be extensively tested so they can get into the hands of our users as soon as possible.

As an open source project, the Mautic Community is the foundation of our progress, so join us today and help speed up the release of Mautic 7 into the General Availability version.

The General Availability release of Mautic 7.0 is scheduled to be released in Q4 2025, and with your help we’ll make that deadline.

Here is what you can do to help:

Each Friday we will be having our usual Open Source Friday community sprints, a great way to have mentored onboarding to get started with contributing to Mautic. Join us on Slack and head over to #new-contributors if you’d like to get started, or jump right into any of the teams, whose channels start with #t-<team name>.

Right now we have Hacktoberfest running, which means there’s even more onboarding support from our awesome team leads!

Check the features, enhancements, refactoring and bug fixes which are slated for release in the Release Candidate, and help us by testing them. Check our docs on testing – which can almost always be done locally or using a GitHub Codespace in the browser by any user of Mautic. Don’t forget to leave a formal review, that counts as a contribution to Mautic!

Help us with completing the updates needed for the end-user and developer documentation by joining #t-education on Slack. We have regular onboarding calls to help you get started.  There’s everything from updating screenshots to reviewing our code examples, something for everyone!

Useful resources

https://github.com/mautic/mautic/blob/7.x/UPGRADE-7.0.md – developer-facing changes

7.0.0-alpha release – https://github.com/mautic/mautic/releases/tag/7.0.0-alpha

7.0.0-beta release – https://github.com/mautic/mautic/releases/tag/7.0.0-beta

7.0.0-Release Candidate milestone: https://github.com/mautic/mautic/milestone/127 

7.0.0-General Availability milestone: https://github.com/mautic/mautic/milestone/128 

But I’m here to tell you something that should shift your perspective: Open source is more than just code. It’s a vast, vibrant ecosystem built on collaboration, where every skill set has a vital role to play. We need to stop correlating contributions solely with writing programming code.

I’m Ayu, and I currently serve as the Assistant Team Lead for the Education Team at Mautic. I can speak to this from experience: my first contribution to Mautic was a no-code submission in 2024. It’s precisely this kind of contribution that drives Mautic’s core belief: bridging the gap for low- and no-code contributors. We want to actively support and encourage all types of contributions that help our projects and our entire community to thrive.

The scope of contribution

When we look at the different ways people can contribute to a project, we can organize them into a comprehensive scope.

At one end is traditional programming, which involves writing complex application logic, fixing bugs, or developing new features. This is the conventional open source contribution most people think of.

The low-code contributions

Documentation may look like a simple task, but it’s one of the most critical parts of any project. Good documentation is what makes a project usable, welcoming, and successful.

Fact is, even writing documentation often requires a bit of code. Whether you’re writing in Markdown, ReStructured Text, or another markup language, you’re using structured syntax. You typically use a code editor to write and format it, and you engage with the project’s codebase to submit your changes, usually through a Pull Request (PR). Because of this, we can safely categorize documentation as a low-code contribution. It still utilizes technical tools and syntax, but the focus isn’t on application logic.

The crucial no-code contributions

Now let’s move to the other end of the scope—the pure no-code contributions. These efforts are crucial for a project’s survival and growth, yet they often involve zero lines of programming code.

Contributors can add massive value to our projects in areas like:

• Testing & feedback (PR reviews): Checking for clarity and grammar in documentation, or testing bug fixes and new features, confirming the logic, and providing detailed feedback.
  
• Design & user experience (UX): Creating mockups, designing social media flyers, or crafting a new website layout in tools like Figma or Canva.
  
• Education & training materials: Writing blog posts, tutorials, and success stories on our blog and knowledgebase, or making tutorial videos, streaming demos, or recording project updates on a platform like YouTube.
  
• Community engagement, marketing & translations: Running social media campaigns, managing the project’s presence, translating project materials, helping with logistics for community events, or triaging issues.

These are massive, valuable contributions. They keep the project healthy, make it more accessible, grow the user base, and ultimately allow developers to focus on writing code. The open source community, at its best, sees all of these as valid and important contributions to their project or organization.

The challenge of recognition: counting no-code in Hacktoberfest

The challenge arises when organizations, especially during events like Hacktoberfest, try to recognize and quantify these diverse contributions.

Hacktoberfest requires a set number of merged PRs to count toward challenge completion, which works perfectly for traditional programming and low-code contributions. But how do we count those invaluable, vital no-code contributions? How can we ensure that these contributors are recognized and celebrated alongside the coders?

It’s a problem we, like many others, set out to solve in Mautic. We wanted a clear, fair, and open way to count contributions that don’t result in a traditional code PR.

Mautic’s approach to no-code recognition

We established a system using a dedicated low-no-code repository. It’s a simple yet effective mechanism for tracking non-code work.

Here’s how it works:

1. Work on a deliverable: The contributor does their work using their preferred public tools. It might be a Google Doc for an article, a YouTube channel for a tutorial video, a Figma or Canva link for a design, or a link to the specific feature PR they reviewed or tested. The key is that they must have a publicly accessible “media” of their work that they can link to and share.
   
   
2. Document and submit: They create a new entry in a dedicated Markdown file within our special repository. In this entry, they must list:
   • Their name and GitHub handle
   • Links to their specific contribution (the Google Doc, the YouTube video, the Figma or Canva board, etc.)
   • A brief description of the contribution
3. The PR is the count: They then create a PR to be merged. This PR counts towards their Hacktoberfest contribution. It serves as a verifiable acknowledgment of the valuable work completed outside the codebase.

A call for greater appreciation

More open source projects need to find ways to appreciate and formally recognize their no-code contributors. They are the unrecognized champions of the community. Without the writers, designers, testers, marketers, and community organizers, our projects would stagnate, become unusable, or be forgotten.

This system is just one way to do it—and it works for us. It establishes a clear record, gives contributors a measurable result for their efforts, and fits perfectly with the PR-based structure of events like Hacktoberfest.

If you’ve been hesitant to contribute to open source because you don’t feel like a “coder,” please let go of that idea. Your skills are not only needed but also valuable, and they deserve recognition.

Look for projects that actively welcome contributions across the entire scope. Ask how you can help test, write, or design. You might find that your biggest contribution doesn’t involve a single line of application code.

The future of open source is inclusive. Let’s build it together, with every skill and every contribution appreciated and counted.

It’s in this spirit of collaboration that we make this exciting announcement: Nominations are now open for the Mautic Council, and we’re looking for two driven and community-focused individuals like YOU to step up.

The Mautic Council is a critical component in shaping our future and amplifying the voice of our community in decision making. Serving on the Council offers a unique opportunity for you, as an individual, to influence Mautic’s trajectory, lending your unique perspectives and experiences to its development and governance. There are seven seats in total on the Council, and the term of appointment is three years – read more in the Governance Model and meet the current Council here.

This year, we’re saying a big thank you and goodbye to Ekkehard Gümbel and Prateek Jain, who are coming to the end of their initial two-year term on the Council (initial terms were three, two and one year to ensure members didn’t all leave in the same year, incoming members will serve for three years).

So why should you nominate someone (or yourself) for the Mautic Council?  

1. Steering Mautic’s future course: Council membership allows you to play a direct role in critical decisions affecting Mautic’s future as a product and the wider community.  
2. Voice of the community: As a Council member, you’re in a position to represent the needs, ideas, and suggestions of the Mautic community.  
3. Leadership development: Being a member of the Mautic Council aids your professional development, sharpening your leadership and governance skills in a real-world, dynamic context.  

To nominate someone (or yourself), the proposed candidate will have to be an individual member of Mautic.

Diversity is a cornerstone of our community, so we warmly encourage nominations for individuals from different backgrounds, affiliations, and areas of expertise. 

Nominees should have a strong commitment towards open source principles, possess an in-depth understanding of Mautic, and be willing to proactively work with other council members and the broader community. We particularly welcome those who have experience in business development, leadership and scaling organizations as this will also be a big focus for Mautic in the coming years.

To be successful as a Council member, you are expected to attend two 2-hour meetings each quarter (one at the middle, and one at the end) and have 5-10 hours per week on average to dedicate towards preparing for the meetings, working on any tasks assigned to you through our executive committees, and generally keeping in touch with both the Council and the wider community. We’re not a Council that sits back and reads reports (although we do that too!), we’re actively involved in shaping the future of Mautic, and we can’t wait for you to join us.

Interested? Then take that next step and put forward your nomination here. 

Nominations will close on 10th November 2025, so make sure you don’t miss this exciting opportunity.

Fill the council seats with the power of the community, let your voice be heard, and help Mautic reach new heights. Happy nominating!

Have questions? Please drop into #wg-governance on Slack, or drop me an email at ruth.cheesley@mautic.org.

This November, the global Mautic community is discussing these topics. In person in London and online all over the world. 

The experience awaits

Monday, 3rd November – The main event kicks off at Sea Containers London, where the Thames meets innovation. This isn’t your typical conference talking shop – up to 150 of marketing automation’s brightest minds are gathering to chart the course ahead. 

Tuesday, 4th November – Community Day. Roll up your sleeves and contribute directly to the platform that’s changing the face of marketing automation. Code, documentation, strategy, copy – whatever your skill, there’s a place for you in building Mautic’s future.

Thursday-Friday, 6-7th November – The conversation goes global with our online conference days. Can’t make it to London? Join Mauticians worldwide as we extend the community dialogue across time zones, languages and continents.

Why London, why now?

London has always been where innovation meets opportunity. From the Thames to the tech corridors, this city understands reinvention. And right now, marketing needs reinventing.

AI is rewriting the rules of customer discovery. Traditional touchpoints are shifting. Brand relationships that took decades to build can vanish with an algorithm update. But here’s what the smartest marketers already know: the companies that will thrive are those that control their own customer conversations.

Marketers and decision makers need to be empowered to make savvy decisions when choosing their technology stack. Technology that serves your brand, not the other way around. Technology that keeps your customer relationships in your hands, not scattered across platforms you don’t control.

Answer the call – speakers wanted

We’re building a speaker lineup that reflects our community’s diversity and expertise. Whether you’re a Mautic veteran sharing hard-won insights, an expert in email or SMS deliverability, a newcomer bringing fresh perspectives, or someone bridging marketing automation with emerging technologies – we want to hear from you.

The Call for Speakers is open now. Share your story on London’s stage (or on the virtual stage, if you can’t make it in-person) and help shape the conversation that will define marketing automation’s next chapter.

Back the movement – sponsors welcome

This conference runs on community spirit, but it needs practical support. Our sponsors get great brand visibility and become part of a movement reshaping how marketing works. From privacy-first automation to platform independence, your support directly advances the future we’re building together.

Current sponsors include KumoMTA, Sales Snap, Dropsolid, EmailExpert, enable.services and VML, but there’s room for many more organisations ready to back real change in marketing technology. Sign up today!

The numbers that matter

• Early Bird tickets: £129 (until 31st August 2025)
• General admission: £149
• Online only: £29
• Maximum physical capacity: 200 attendees
• Expected online attendance: 300 attendees
• Location: Sea Containers London, 20 Upper Ground, London SE1 9PD

This is your call

The marketing world is changing whether we’re ready or not. Platform algorithms shift overnight. Privacy regulations tighten. Customer expectations evolve. But communities like ours don’t just adapt to change – we drive it.

London calling to developers building the next generation of marketing tools. London calling to marketers breaking free from platform dependence. London calling to organisations choosing data sovereignty over convenient captivity.

The question isn’t whether marketing automation will evolve.

The question is whether you’ll be part of shaping that evolution.

Register now. Submit your speaker proposal. Join the movement.

London is calling. Will you answer?

Mautic World Conference 2025 takes place 3-7 November. Physical events Monday-Tuesday in London and streamed online, online-only components Thursday-Friday globally. Register at 2025.mauticon.org

The magic of community coming together

There’s something truly remarkable about watching the Mautic community unite around a shared purpose. In Prague, we witnessed the beautiful convergence of passionate individuals working side by side, whilst simultaneously welcoming remote contributors who joined our mission from around the globe. The energy was palpable – both in the room and across our digital channels.

The on-site team in Prague brought lovely enthusiasm to each and every task, diving deep into code reviews, tackling complex bugs, and engaging in the kind of spontaneous collaboration that only happens when minds share the same physical space. Meanwhile, our remote contributors proved that distance is no barrier to meaningful participation, contributing valuable insights, code reviews, and solutions that kept the momentum flowing throughout both days. But it was much more than just about the development side of things. 

It was a community effort to make the end user experience so much better. 

What we accomplished together

The results speak for themselves: Over those two intensive days, our community delivered significant improvements that will benefit every Mautic user:

Major platform upgrades

Our team successfully upgraded Mautic to Symfony 7, a substantial undertaking that strengthens the foundation of our platform and ensures we’re building on the most current, secure framework available.

User experience enhancements

We tackled numerous UI/UX improvements that users will notice immediately:

• Fixed segment filter display issues that were causing confusion
• Resolved email builder problems that were hampering campaign creation
• Improved dynamic content functionality for more sophisticated marketing automation
• Enhanced form and campaign management interfaces

Quality and performance improvements

Beyond the visible changes, we focused extensively on code quality, addressing bugs that improve platform stability and performance. Every fix, no matter how small, contributes to a more reliable Mautic experience.

Developer experience upgrades

We invested significant effort in code refactoring that will make future development smoother and more efficient, benefiting not just our core team but every developer who contributes to Mautic.

Combining the power of working side by side with remote supporters

What to me made this sprint truly special was how seamlessly we blended in-person collaboration with remote participation. Being remote, it was great to see how the Prague team could tackle complex problems through immediate discussion and pair solutioning, whilst we remote contributors provided fresh perspectives, thorough reviews, and additional expertise across different time zones.And also tackled our own tasks, issues and improvements. 

The collaboration extended beyond just code. Our marketing efforts saw immediate coordination between content creation, social media strategy, and technical documentation – all happening simultaneously across multiple locations. This distributed yet coordinated approach showcased the true strength of our global community.

The spirit that drives us forward

What struck me most during those two days wasn’t just what we accomplished, but how we accomplished it. Every participant, whether physically present in Prague or contributing remotely, brought genuine enthusiasm for making Mautic better. There were moments of frustration when tackling particularly stubborn bugs, celebrations when breakthrough solutions emerged, and constant encouragement as team members supported each other through challenges.

This spirit of collaboration and mutual support is what makes Mautic more than just a marketing automation platform – it’s a community united by shared values and common goals.

London calling – join us in London at the Mautic World Conference 2025

The Prague sprint was just the beginning. We’re already looking ahead to our next major community gathering: the Community Sprint at Mautic World Conference 2025 in London during the week of the 3rd of November (with the in person conference on the 3rd, the Community Sprint on the 4th and the remote conference on the 6th & 7th). . 

This will be our opportunity to bring together an even larger group of contributors, users, and advocates. Whether you’re a seasoned developer, a marketing professional who uses Mautic daily, or someone who’s simply passionate about open source marketing automation, we want you there.

The combination of the main conference sessions and the community sprint creates the perfect environment for learning, networking, and contributing. You’ll have the chance to work alongside the core team, tackle real challenges, and help shape the future of Mautic.

Ready to join us in London?

Learn more and secure your place at 2025.mauticon.org. Whether you’re planning to contribute code, documentation, testing, or simply want to be part of our incredible community, MautiCon 2025 is where you belong.

The Prague sprint showed us what’s possible when our community comes together. London will be our chance to go even further. We can’t wait to see what we’ll accomplish together.

• Finances: Significant boost from the GitHub Secure Open Source Fund, steady GitHub Sponsors and memberships; our expenditures are higher due to delayed employment invoices and costs associated with the Mautic World Conference event. A strong focus is needed on H2 income to stabilise cash flow.
  
• Contributions: We continue to see strong organisational activity (Acquia, Dropsolid, Leuchtfeuer, Webmecanik and more) and many awesome individual efforts (Renato, John Linhart, Ayu Adiati, and many more), with new contributors joining to contribute across many areas.
  
• Product and usage: We continue to see around 600 monthly trial signups and we’ve open sourced the Product Tour plugin for wider use. We’re going to be changing the pricing tiers next month for the Managed Mautic service as approved by the Council. We estimate around 25,000 active sites with Mautic tracking enabled and we’re continuing to see growing adoption of Mautic 5 and 6.
  
• Community sprint outcomes: The Prague sprint advanced Mautic 7.0 alpha toward release and enabled a quality-first review of the application which resulted in several bug fixes and some key decisions to simplify email/form creation and rename campaigns to workflows which will be coming in future releases.

Finances

Income

This month we’ve had a large injection of funds thanks to the GitHub Secure Open Source Fund which two of our team participated in last month (read more in the blog post here) – we will receive $6,000 initially and then two more batches of $2,000 at 6 and 12 months respectively after the program.

We’ve seen a fairly steady income on our monthly sponsors and a small contribution from folks attending the community sprint in Prague.

This month we had quite a few renewals of individual memberships which was great to see!

Expenditure

This month there were two invoices for employment due to delayed approval resulting from queries on some changes in amounts due to tax changes.

We’ve incurred some expenses on behalf of the MautiCon event this month which will be recouped from the sponsorship when it starts to come in over the coming months. Our contractors, admin support and infrastructure expenditure remains steady, and there were planned travel expenses for the Community Sprint.

Overall, we do need to focus more strongly on achieving our goals in the second half of the year when it comes to income, to ensure that our cash flow remains stable. More focus is coming on this in the coming months.

Contributions

These organisations are making Mautic and helping to grow our awesome community!

You can always take a look at the data for the last 90 days via this link: Mautic | Last 90 Days Report and you can now view this month’s report here: Mautic | Monthly Report for July 2025!

 = Increase from last month
 = Decrease from last month

Organizations

Most active companies

Acquia 137 ( 132.20%)
Leuchtfeuer Digital Marketing 93 ( 43.08%)
Dropsolid 91 ( 56.90%)
Webmecanik 69 (  34.91%)
Aivie 62 ( 31.91%)
Friendly 45 ( 9.76%)
Moorwald | Sven Döring 45 ( 66.67%)
UpScale 22
Comarch 21
Twentyzen 13

Top contributing companies

Dropsolid 47 ( 38.24%)
Acquia 41 ( 20.59%)
Aivie 38 ( 26.67%)
Webmecanik 24
Leuchtfeuer Digital Marketing 21 ( 31.25%)
UpScale 15 ( 650%)
Comarch 12 ( 71.43%)
Moorwald | Sven Döring 7 ( 600%)
ut11 2
Amrita School of computing 1

Contributions are as defined here with the addition of Jira issues being closed as completed, GitHub Pull Request reviews and Knowledgebase articles being written or translated, which we track through Savannah’s API.

Want to appear on this list? Get contributing, and drop me a line with your company name, domain and the folk who work for you and we’ll make sure that you are attributed correctly! 

Individuals

A big thank you also to all the individuals who are helping us build this awesome community :mautibot: :hands-raised:

Most active contributors

Renato 210
John Linhart 126
Ayu Adiati 117
Anderson José Eccel 85
Zdeno Kuzmany 64
Rahul Shinde 59
Ekke Guembel 45
Sven Döring 45
Joey Keller 43
Ima-Abasi Effiong 24

Top contributors

Anderson José Eccel 44
Rahul Shinde 38
A.Sagitov 33
John Linhart 29
Ayu Adiati 27
Zdeno Kuzmany 23
Martin Vooremäe 15
Patryk Gruszka 12
Patrick Jenkner 10
Renato 7

Welcome to our new contributors this month 

OlgaMarchuk
tishaa17
Pep
martin-korf
Niels Aers
Zeroday BYTE
Greg Harvey
Lukas Scharnhorst
Isreal Hogan
jamesl
Marcos ‘Marcão’ Aurelio
InboxSOS
mcgumbel
Prajwal Prasad
Allan

Top supporters

Rahul Shinde 3
Achilles Poloynis 2
Carlo 1
Sascha Foerster 1
Tom Friedhof 1
Jasmine-Gift Kelvin 1
jamesl 1
Pep 1
mcgumbel 1
Favour Chibueze 1

Usage of Mautic

We’re continuing to see a steady rate of signups for the Mautic trials, with around 600 a month initiating a trial.

This month the team at Dropsolid has open sourced the Product Tour plugin which we’re using in the trials with a view to us developing it further and enabling more Mautic users to take advantage of it.

We also passed some changes to the pricing tiers in the Mautic Council which will be applied in August.

We’re continuing to see growth in sites that use Mautic tracking, with approaching 25,000 sites currently active and detected by BuiltWith.

We are starting to see a strong uptake of Mautic 6, with around 75% of Mautic instances that are updating and sending data back to Mautic running version 5 or 6.

This isn’t surprising because we only support updates to Mautic 4 under the Extended Long Term Support program now. As we’ve seen in previous years, we expect the gradual reduction of Mautic 4 and 3 instances as businesses update to more recent versions.

We know that many larger organisations will wait for Mautic 7.3 LTS to be released before updating from Mautic 5.2 LTS, given the shortened bridging release of Mautic 6, so it’s likely that we’ll see a slower uptake as a result.

Community Health

July saw Mautic’s annual Community Sprint happening in Prague – an opportunity for our community to come together for a couple of days and work on specific tasks together while physically co-located.

We know that these sprints are a precious opportunity to make progress on initiatives and this year was no different.

One team were tasked with finalising the work to release Mautic 7.0 alpha, and the other team were focusing on improving product quality. They broke out into pairs and worked through a list of every action that a user might take in Mautic, logging any bugs that they encountered, areas for improvement, and things that were confusing as a user. Quite a few were fixed and merged during the sprint but we have a full backlog on our GitHub Project Board.

Some critical decisions were made during the sprint as a result of this close review, including:

• Removing the two types of email selection when creating an email
• Removing the two types of form selection when creating a form

You’ll see some of these changes coming over the next months – please consider helping us with reviewing and testing new features, bug fixes and enhancements: https://mau.tc/tester.

Conclusion

In my experience, months like July show how our community’s energy, transparent finances, and thoughtful product choices move us toward true digital independence. We shipped meaningful improvements through the Prague sprint, and saw steady growth in adoption and contributions. Where can you lend your strengths this month – reviewing, testing, mentoring, or sponsoring – to help us keep up this momentum? Take a look at https://mau.tc/contribute and help us move Mautic forward faster.

For three weeks the participants learned about everything from securing automated workflows and the tools that can be used to detect vulnerabilities through to planning for dealing with incidents and learning about the latest developments in security regarding AI/ML and MCP servers.

Attended by Project Lead Ruth Cheesley and Docker Working Group Lead Renato Castro, the training has been instrumental in helping Mautic to develop its security posture and ensure that we are operating in a way which ensures the safety and security of our ecosystem.

We’re delighted to share that we graduated from the program, which you can read about on the GitHub blog announcing the first 71 projects they worked with.

The work doesn’t stop with the end of the program, though, and that’s the beauty of this opportunity – the entire cohort of 40 open source projects and their maintainers will stay together in a private community as we all work to secure open source.

Together we will all be working through our backlog and focusing on keeping our open source projects secure.

What’s more, GitHub is also financially supporting the projects who complete the program by providing a $10,000 contribution and we’ve also been offered a substantial amount of Azure credits to support Mautic’s continued growth.

Both Renato and Ruth found the training extremely insightful:

Project Lead Ruth Cheesley said:

It was such a great opportunity to learn from the experts across GitHub and the wider technology community – not to mention from our fellow maintainers – over the course of the three weeks. We’ve already implemented many of the learnings and I’m sure it’s going to have a big impact going forward.

Renato Castro, Docker Working Group Lead said:

During the training I had the opportunity to learn more about multiple cybersecurity topics which I wasn’t completely aware of. It was awesome to discover Github’s security-driven features, and share insights with not only other open source maintainers, but also with Github experts who are very passionate about their products. The program has definitely helped us to improve Mautic’s security, making us align even more with our vision of being the most privacy (and security) focused marketing automation product on the market.