Our second year of running the event, we welcome everyone interested in deepening their knowledge of Mautic and joining our vibrant community. Whether you’re a developer, marketer, technical writer, or simply curious about Mautic, this is the perfect opportunity to dive into the world of this outstanding open source marketing automation platform.

What to Expect

The event kicks off on the first day with a comprehensive introduction to Mautic during a training session. This session is tailor-made to provide a solid foundation for individuals new to Mautic, ensure you’re up to speed, and ready to unlock its full potential. Don’t miss this chance to supercharge your Mautic skills!

For the subsequent two days, we have lined up an exciting schedule of community contribution sessions. These sessions offer firsthand experience in various aspects of the Mautic project, including development, testing, marketing, technical writing, community building, and event organizing. Regardless of your expertise, there will be ample opportunities for you to make a valuable impact and contribute to the growth of Mautic.

Embrace Flexibility

In recognition of the diverse Mautic community spread across the globe, we are pleased to offer a remote participation option. If you can’t make it to Vienna, you can still join us virtually from anywhere. We want to ensure that every member of the Mautic community has the chance to participate and contribute, no matter their location.

Several of our team members will be contributing remotely so we will have mentors available both in-person and online to get you started.

Mautic Sprint (21st-22nd) 

Kickoff: Friday 10:00 h
Please see Slack channel #community-sprint for hours and all coordination 
(Use https://mau.tc/slack-invite if you do not yet have an account for the Mautic Slack space)

Access for remote attendees: via Zoom
(Meeting ID: 875 0093 1130, Passcode: 330242)
 

What we’re going to be working on:

Community Team

• Strategy for growing local communities
• Preparations for the next in-person Mautic conference

Education Team

• Finalising work on the new developer docs (API documentation writers needed!) and end-user docs

Legal & Finance Team

• Workflows for CollectiveVoice integration for collaborative approving of expenses on Open Collective in Slack (doc & video, form to complete)
• Tooling for implementing the new governance model
• Preparing copy and workflows for the call for nominations for the Mautic Council

Marketing Team

• Preparatory work for the upcoming strategy workshop
• Content and visuals to support the Mautic 5.0 release

Product Team

• Testing the Mautic 5.0 alpha release
• Fixing bugs identified
• Writing Mautic-specific email transports for Symfony Mailer

Location

If you’re planning to join us in-person, here’s some information about the venue:

The event is happening at the University of Vienna (Oskar-Morgenstern-Platz 1, 1090 Vienna), located very centrally in the city of Vienna. The main contribution area will be in the Sky Lounge event room on the 12th floor, which includes a rooftop terrace with a panoramic view of the city!

The venue is certified for green meetings and surrounded by restaurants and well known points of interest like the Freud museum. The 1st district is just a 5 minute walk away.

Location, location, location:

• One tram station away or a 3-minute walk to the U2 & U4 Station Schottenring. Get the Wiener Linien APP on your phone or use a maps service for public transportation information.
• Important Update: As can be read here, the Vienna Public Transportation System will be doing construction on the U2 and U4 lines that will affect us during the event. 

You can read more about the venue on the DDD website.

How to Get Involved

To be a part of Mautic Developer Days and Community Sprint in Vienna, firstly make sure that you mark these dates in your calendar.

If you plan to attend in-person, please book your ticket here. (132 EUR including coffee, heathy snacks, drinks and evening entertainment)

If you plan to attend remotely, please book your ticket here. (free, but donations welcome)

We will be sharing updates on the event agenda, registration process, and logistics.

In the meantime, we encourage you to spread the word among your networks and colleagues who might share an interest in Mautic. The more diverse and engaged our community, the stronger we become.

Conclusion

The Mautic Developer Days and Community Sprint in Vienna is your gateway to immerse yourself in the world of Mautic, enhance your skills, and contribute directly to this awesome open-source project. Whether you attend in person or remotely, we look forward to your active participation and dedication.

Don’t miss this fantastic opportunity to connect with like-minded individuals, share insights, and help shape the future of Mautic. Together, we will build and improve a powerful marketing automation platform that empowers businesses around the world.

Stay tuned for further updates and get ready to join us in Vienna or remotely from July 19th to July 21st.

The aim of our event was to bring together in person Mautic developers to learn and share, but also to have the opportunity to work collaboratively on some major projects we have coming up.

These include:

• Updating Mautic to support Symfony 5 – a large project on the scale of the Mautic 3 upgrade
• Implementing PHP8 support which was blocked by several significant challenges
• Improving and fixing bugs with the Composer implementation
• Completing the migration of our developer documentation to Read the Docs
• Moving forward with the migration of our end-user documentation to Read the Docs

At the event in Ghent we had in total seven attendees supported to attend by Acquia, Webmecanik and Dropsolid with other contributors from Aivie and Steer Campaign supporting the event remotely.

Our progress in numbers:

• Over 50% of the work for Symfony 5 completed and a further 10% in progress.
• Implementation of Twig templates for developers to provide Symfony 5 compatibility alongside PHP templates until Mautic 5 is released
• Substantial progress in updating the Mautic Developer Documentation and the End-User documentation which we aim to launch with Mautic 4.3
• Fixing issues blocking PHP8
• Fixing issues with Composer-based installations due to an upstream change in Doctrine, and some problems with the autoloader.

Now the work starts with testing and reviewing all of these changes – if you can spare some time over the coming weeks please do let us know, we’re happy to help you get set up for testing (which can now all be done completely in the web browser with a pre-created Mautic instance).

We have also addressed some critical blockers which were preventing us from supporting PHP8, and tracked down an upstream change which was breaking our Composer based installations which will be fixed in the upcoming 4.2.2 release.

We will be continuing the work in our Open Source Friday community sprints every Friday, and also in our in-person sprint in Budapest in a few weeks’ time.

But before discussing how to contribute, let us briefly talk about Mauticians. You’ll often hear this term as you get involved in our community. Mauticians are the backbone of our community. They’re amazing volunteers who contribute their time and skills to improve Mautic. They come from diverse backgrounds and skill levels, united by a common goal: to improve Mautic.

However, this article will focus on how you, as a developer, can engage and contribute to Mautic through code contributions and pull request testers.

Whether you’re a seasoned developer or just starting out, we offer opportunities for everyone. By contributing to Mautic, you’ll help shape our platform’s future and connect with a global community of passionate individuals.

Now, how can you get started contributing to Mautic?

Familiarize Yourself with GitHub

Our project lives on GitHub, and we assume you already have an account there. If not, go to their official website and create one.

Then, try to understand the GitHub basics. Learn essential concepts like repositories, branches, commits, and pull requests. Afterward, explore advanced features such as forking, merging, and resolving merge conflicts. At this point, it’s also important to learn the basic Git command to help you later with code contribution.

We won’t discuss these concepts in this article. However, you can read the official GitHub documentation to familiarize yourself with GitHub and the Git Guide to learn about basic Git commands.

Explore Mautic Issues and Pull Requests

Once you understand the basics of Git and GitHub, the next step is to explore issues and pull requests in our repository.

If you’re familiar with the tech stack we use at Mautic and want to contribute right away, you can explore the open issues available in our repository. You must search for those that are not assigned to anyone. Look at the “Assignee” tab to see which are still available. When it’s still empty, it’s still available to work on.

Tip: Leave a comment to ask to be assigned to an issue. Only claim another issue after you finish the one assigned to you so you don’t get overwhelmed.

As we said, there’s always opportunity for everyone, regardless of skill level. So, if you’re unsure and want to learn Mautic’s codebase and how things work, one of the best ways is to help us review and test the open pull requests. Head to the “Pull requests” tab and look for a pull request you want to test.

Depending on your skill level and familiarity with our project, we provide labels to help you choose which issue you can work on or pull requests you can review and test.

Understand Issues and Pull Requests Labeling System

Whether you are a new developer or new to Mautic, our labeling system will help you find and decide which issue or pull request to test or work on. So, what labels are they?

T1

If you’re a beginner or someone new to Mautic, we recommend you search for an issue or a pull request with this label. It requires minimal coding experience and takes a relatively short time to test. This label usually concerns small changes such as typo fixing, small bug fixes, translation changes, minor UI improvements, or minor enhancements.

T2

The T2 label indicates issues and pull requests that are more complex than the T1. It requires more time, intermediate coding skills, and problem-solving abilities. Issues and pull requests with this label may require you to create an external services (e.g., Salesforce/HubSpot) account for testing.

T3

Issues and pull requests with this label are the most complex, demanding advanced coding knowledge and experience. They might touch multiple parts of Mautic, change large amounts of code, or completely change how some aspects of the code work.

Other Labels

There are other labels besides what is mentioned above to give you information on what type of issue or pull requests they are. To understand their meaning, hover over each label to see the information.

Search Issues and Pull Requests with Specific Labels on GitHub

You can use the filter options to locate specific labels. This will give you a list of issues or pull requests with the labels. You can filter and search one or multiple labels. Here is the way to do that:

1. Search One Label

To search one particular label, once you’re in the “Issues” or “Pull requests” tab, click the “Label” dropdown at the top. Scroll down or type the label you want to search in the input, then click the label name.

2. Search Multiple Labels

If you want to search more than one label, you can type them in the search input right on top of the issues or pull requests list. For example, `is:open is:issue label:bug label:T1`. This means you want to find open issues with “bug” and “T1” labels.

Start Contributing and Be a Mautician!

Now, you have the knowledge to start contributing to Mautic and join our community.

If you’re ready to contribute, you can find more detailed information in our Contributing to Mautic Guide for Developer and Code governance pages. Take your time to read them before contributing.

Lastly, we are excited to welcome you as a fellow Mautician!