A participatory process is a sequence of participatory activities (e.g. first filling out a survey, then making proposals, discussing them in face-to-face or virtual meetings, and finally prioritizing them) with the aim of defining and making a decision on a specific topic.
Examples of participatory processes are: a process of electing committee members (where candidatures are first presented, then debated and finally a candidacy is chosen), participatory budgets (where proposals are made, valued economically and voted on with the money available), a strategic planning process, the collaborative drafting of a regulation or norm, the design of an urban space or the production of a public policy plan.
🚀💡 Be a Part of Mautic's Evolution: We Need Your Ideas! 💡🚀
Welcome to Mautic’s vibrant melting pot of innovation and collaboration! Do you have a transformative idea for a new Mautic feature or improvement to an existing one? Fabulous, because this is the platform where your ideas matter.
Every proposal here fuels Mautic’s continuous journey of evolution, shaping its open source prowess and usability. Receive endorsements that reflect community interest, engage in collaborative discussions to refine your idea, and witness your proposal become a game-changing Mautic feature! Remember, your contribution doesn't stop at proposals - your comments on others' ideas are equally valuable, helping collectively drive an idea to a productive result. Together, let's write Mautic's future, test change, and make history in marketing automation!
P.S. If you ever dreamed of influencing the roadmap of a cutting-edge, open-source project, here's your chance. So, go ahead, dive in and make waves in the Mautic ecosystem - You can be our next change-maker! 🌐🔮📝
About this process
This process belongs to Participate
Who can propose improvements to Mautic?
Any member of the community can make a proposal for a new feature or the improvement of an existing one.
Proposals can receive endorsements, although these are not decisive for a proposal to be included on the roadmap. The endorsements serve as indicators of the interest of the proposal or the need it covers. The comments to the proposals are also enabled, to collectively elaborate the initial idea and bring it to a productive result.
We always encourage discussion of features and direction for current and future versions of Mautic, within the following guidelines:
- A little discussion is great. However, we try to avoid having too much discussion in favor of 'try it first'.
- In the event that there isn’t any kind of real consensus in the discussion, or significant disagreement among a minority in the discussion, the Product team reserves the right to make arbitrarily binding decisions and move forward.
- In the case where it’s kind of a UI or design thing where there’s no way to have a solution that can satisfy everyone, our philosophy is:
- Do the simple / clean thing whenever possible
- Gather basic feedback
- Try it for a while – live with it
- Adjust it over time based on feedback from living with it
- We reserve the right to be wrong about any of those binding decisions and revisit them at some later date.
- We don't want to overload Mautic with numerous complex settings; our preference is to supply sensible default configurations which are suitable for nearly all contexts, and that can be adjusted if needed. Regardless, in a few distinct cases the requirements are so varied that a new setting must be implemented. This approach should only be used as a final option.
- Mautic is free and open source software! Test the change you want to see, via your own instance first, and then share with the community how it went.
How do we decide the acceptance of new features?
The Product team reviews new proposals on a monthly basis that have been published the previous month. In order to decide whether a proposal is accepted we ask ourselves the following questions:
- Has it been discussed on the Mautic Forums and is there sufficient interest?
- Is this feature sufficiently well-defined?
- How many different Mautic instances are complaining / asking about this?
- What is the community composition of those Mautic instances that will benefit? Large, small, institutional, specialist, generalist, cranky (we dislike change), progressive (we love change)?
- How active is the proposer in the community?
- Is this going to benefit massive instance with huge send volumes, or a small instance?
- How strongly does the team feel this would help many (or all) other Mautic instances?
- How in tune with the Mautic mission and vision is this feature?
- Have any discussions (on the forums, or here in the Debates section) been satisfactorily resolved or come to a decision that is accepted by the majority?
- Does it have funding? This sponsor will be responsible for finding and providing the economic resources to carry out its development. In this sense, sponsors can be: public institutions, companies or members of the developer community, associations, collectives, etc.
Once the development of a new feature is finished and it meets the requirement for being merged, it is included in the next appropriate release (External link) and communicated to the community (External link).
< ADD IMAGE TO SHOW WORKFLOW>