Read more about The Document Foundation
Proposed Phases (default)
In Decidim’s documentation, they propose a phase model for a participatory process; their model has seven phases (https://docs.decidim.org/en/admin/_images/process_steps_components.png)
- Configuration & Presentation
- Proposal Creation
- Proposal Selection
Each phase gets defined, configured and described by the admin(s). This includes assignment and configuration of one or more components to each phase. "Admin" is not meant technical, but a kind of moderator or "process owner".
Decidim is providing several components which can be used in each phase of the process. Besides these, there is also a Newsletter to send on every user of the platform who agreed to get it. The components are:
This is to add static pages to give some Information. No Interaction intended.
This is mere the configuration page for proposals each user can make. Here can be set the vote limit per user and per proposal, the max. length of the proposal text, the proposal wizard help texts (when creating, comparing or publishing proposals) etc. Proposals can be commented, answered, endorsed or voted on – all this can be switched on or off.
In a later project step, proposals can be accepted or rejected by an admin. Possible admin ACTIONS on a proposal are Private notes, Answer, and Preview. To answer, its status can be set to Accepted, Rejected, or Evaluating. Each status decision can be accompanied by an explaining text.
The meeting component serves as announcement and documentation of the meeting; besides an etherpad integration there is no direct meeting support like a common whiteboard. One can have a “Registration”, “Agenda”, Minutes” and “Close” part. Types of meetings are “In-Person” – real live or Online meetings - and “Official” (created by an administrator) vs. “User” meetings (created by some user).
This is a Forum-like component. Each user may leave a text on a topic.
To create surveys and visualise their result. Each question can be marked as mandatory. Type of question can be short answer, long answer, single option, multiple option. The results of the survey can also be exported in formats CSV, JSON or EXCEL.
This is used to display the results of a process or Phase in a compact form. That is to say, the proposals that have ended up being the result of the decision making in the Decidim, either directly (through the result of the application of a voting system) or mediated by meetings, assemblies, technical or political team, and its degree of execution.
This is used to vote on a (sub)budget of a project. A “budget project” is a single budget that can be voted on – e.g. one number in a budget plan. There can be many of them in one process stage. There are different options, e.g. “Vote in one”: allows participants to vote in any budget, but only in one. Voting can be restricted independently from other components, but the methods must be implemented by a programmer.
The Sortitions function allows you to randomly select a certain number of proposals from a series, for example, to determine at random which people will form part of a group (such as a committee) from a larger group, where each person would be a nomination.
No entry in documentation; try out later.
If there are scopes defined in the basic configuration, each project or even a component may be assigned one or more scopes. For instance, in the case of the city of Barcelona the scopes are its districts, and the children of a district are its neighborhoods. They can also have types, so it can be configured, for example, by thematic and also territorial scopes. For LibreOffice, this could be e.g. the national language projects.