.webp)
.webp)
[ONLINE] Product Team Meeting
March
12
2024
-
Online
-
15:00 PM
-16:00 PM UTC
⚡️🎯 Drive Mautic's Innovation: Connect at the Product Team's Monthly Meetings! 🎯⚡️
Intrigued by shaping Mautic's trajectory? Our monthly meetings are your stage to turn this intrigue into action. From release planning, enhancing security, to brainstorming new features, we explore the gamut of product development.
No matter your role - developer, coordinator, tester, or user - your unique insights can fuel our mission. A hub for both discussions and decisions, these gatherings are the engine behind Mautic's evolution.
Connect with us to truly impact Mautic's course and be part of our inventive symphony. Together, let's engage, innovate, and revolutionize Mautic's journey! 🚀🌍🔧
Product Team Meeting 03/12/2024
Mautic release strategy [ 15:00 - 15:00]
Quote Ruth
the release strategy has become very vague on both the timelines and the specification of release leaders.
It would be nice to get into the process of having a named lead and a shadow lead with the aim of supporting contributors to step up to leading a release in the longer term so there's a wider pool (and also a person to take on the reviewing/merging so it's not falling just to one/two people.
Let's discuss how we can make this more transparent, predictable and manageable and make the plan for a clear(er) roadmap.
new themes / plugins from the community [ 15:00 - 15:00]
Ricardo Freire made some new themes, see https://github.com/ricfreire?tab=repositories&q=mautic&type=&language=&sort=
There are other individuals / companies who made plugins and themes that exist as repo's, and we have the marketplace (as concept)
Do we want to improve / promote the visibility of those as part of the Product (so in scope for this team)?
If so:
- how do we want to make this a better part of our Product ecosystem?
- What needs to be done on a technical level
- What governance / structure changes are needed
Tiger team effort vs perception in the community [ 15:00 - 15:00]
Ensure we're all on the same page for the work happening related to https://community.mautic.org/processes/roadmap/f/4/proposals/6
The tiger team will / has created 2 blogpost on the UX part and the redesign part, but seen the discussions on Slack / Github this will not be enough to get aligned.
How do we make questions / decisions visible for those interested / involved, to ensure it's clear what the goal is, the needed effort, ...
How do we remove the perception it's 1 company defining, developing and approving changes?
Share