In this article we're going to be exploring assemblies, what they are, why they're important, why you might want to get involved with using them, and what you can do.
If you prefer to watch this in video form, you can do that here:
Assemblies can be found via the link on the main menu. When you access this page you will notice that there are some assemblies which are highlighted, followed by the full list of top level assemblies.
An assembly is a grouping of people who come together to make decisions about specific things or to run different parts of the community.
We have different reasons for having assemblies. So some of them are relating to decision making and governance - such as the Council and the General Assembly - but there are also assemblies for Teams, Meetup Groups and Working Groups as well.
An assembly can also have assemblies nested within it - for example the MautiCon Working Group is nested within the Community Team, because that is the team in which it belongs. This is denoted by the card having a stacked appearance, and listing the number of assemblies within it, as seen in the Community Team here.
When you click through onto an assembly you will be presented with the overview page.
An assembly has formal roles including:
When you click on the members item in the assembly menu it lists the formal members.
If you are interested in an assembly the best thing to do is to follow that assembly to get updates. When you start practically contributing to an assembly in some way, the team will make you a contributor or whatever the formal role that's relevant for the assembly is called.
In the Community Team, you'll notice we've got a blog. Anything across the whole of the community portal can have a blog and they all get output into the activity feed, so it's a great way of keeping people apprised of what your team is working on and what your project is doing.
In this case, you can see that there's an official post from the team asking for people who are interested in promoting Mautic in their local regions - to become ambassadors - to come and tell us that they're interested.
Another popular component that we use in the portal is meetings. Meetings can be online, hybrid or in person, and there is an option to filter using select boxes and a search box to show all meetings, upcoming meetings, past meetings, and also to filter by type.
There is an option to export the calendar, which is great if you want to ensure that the meetings for a particular assembly are in your personal calendar. This creates a URL which you can subscribe to in your calendar of choice, so it is updated automatically.
Click on the meeting to learn more about what is being discussed.
To subscribe to an Assembly's calendar, click on the Meetings link in the Assembly menu, then click Export Calendar. This provides a link for you to add the Assembly calendar in your tool of choice.
To subscribe to all events site-wide, follow the same process but use the Meetings & Events menu item on the main menu.
You'll notice in the new features process, we've got the component for debates. Any of the assemblies or processes can have the debates component available.
If you have a question, and you want the community to be able to give you feedback or discussions, this is a great way to do it within the community portal.
So, in this one, we were working on CKEditor and a question came up about when you're using the GrapesJS Builder, what should you be able to change in the WYSIWYG editor? Because you can change a lot of the stuff in the GrapesJS builder itself, so how much do you actually want to be able to change within the WYSIWYG editor? This is an opportunity for us to have a discussion about something and have a debate.
Debates could be time limited, or they could be closed when the discussion gets to a point where a decision has been made, and then if appropriate a related proposal could be made.
Found errors? Think you can improve this documentation? edit this page