Oh no, how is it possibly Friday again, where did that week go?!
Here in Ipswich, UK we finally got a small dusting of snow this morning, the winter is definitely here!
So, Friday must mean that it’s time for Open Source Friday!
For those who don’t know, it’s where we ask organisations and individuals to give whatever time you can to contribute to Mautic in whatever way you can. If you can give us an hour, a couple of hours, half a day or the whole day, it can be super helpful to advance Mautic forward in many areas.
If you haven’t got time, but you could maybe give us some cash, you can also donate to Mautic - Open Collective and/or become a member of Mautic!
Coding / advanced testing for developers
We have several bugs which need to be reproduced and fixed, we’d love help with that!
Check the to-do column on this board.
Please move the card to ‘In Progress’ and assign to yourself if you want to work on something. Let us know if you need adding to the team to allow you to do this.
Mautic 6.0 alpha
Iintroduces support for Symfony 6 and some important deprecations - it is held up by testing, reviewing and fixing the unit tests on these mandatory PRs:
- Replacing the authenticator system (PR here) - this needs ONE MORE TEST! with SAML login, API login, and SSO login. We can’t merge it until we have these tests confirmed as working. This is a critical blocker to the release, please prioritise this.
- Updating Mautic to Symfony 6 (PR here) - this PR needs some help with fixing unit tests, if you can help with this please base it on this branch and let @escopecz know so he can merge your changes into this PR. See this slack message.
Some other PRs are staged for 6.0-alpha which we would appreciate developers prioritising for testing. Check out the milestone here.
- We need a PR to remove the legacy builder entirely from Mautic which should ship in 6.0. If you’d like to work on this, please let us know.
- It’d be good to remove the in-app user interface update screens in 6.0 also, if you’d like to work on this, please let us know.
Low / No Code Contributions
Reviewing and testing bug fixes and new features
For PR testing and code review, please continue to use the Open Source Friday board, here: Open Source Fridays · GitHub - let us know if you need some help with figuring out how to begin, as we do appreciate it can be a bit of a challenge getting started, and we have lots of lovely folks here to help you with your first contributions! You’ll find some docs at https://mau.tc/tester which will take you through most of the steps.
All other low/no code contributions
Since last month’s huge success with Hacktoberfest, we’re going to keep using the low/no code task board here: Mautic's 2024 No/Low/Code Tasks · GitHub as as central place for you to find things to work on which aren’t code-based, or have minimal coding needed. The board has tabs which allow you to quickly find the kind of tasks you would like to focus on.
There are LOTS of ways you can contribute to Mautic that don’t involve code. Here’s a few examples from our board:
- Write or review/update documentation for Mautic plugins (e.g. Zapier, SugarCRM)
- Convert pages on the Community Handbook (https://contribute.mautic.org) from Markdown (.md) to RST format so we can turn off this old server and switch to Read the Docs
- Write a ‘community spotlight’ post on each of our new incoming leadership team members for the mautic.org blog
- Write, review and build content on the new website we’re building for mautic.org (over 100 pages to review, we need a lot of help here!) - see #wg-website-rebuild for the working group
- Create an illustration to explain how features go from an idea to a newly released feature in Mautic
- Define Mautic’s brand imagery and illustration style
- Improve the process for advancing Mautic users into volunteers and community contributors
- Update some pages on the Community handbook to show the new leadership team and council members
- Translate any of the articles on kb.mautic.org to your language
As a rough approximation these are the Slack team channels where you can find people to help you with getting started or working on tasks for each area of focus:
Testing, UX/UI, coding > #t-product - chat with @Joey Keller @Rahul @Norman Pracht
End user, developer docs, knowledgebase & translations > #t-education - chat with @Favour Chi and @Favour
Design, Marketing, Content writing/editing > #t-marketing - chat with @Sven Döring and @Mike Van Hemelrijck
Community building > #t-community - chat with @Ekke and @Avi
How will you be contributing today? Let us know in the replies!