This is an EPIC

Epic description

This EPIC defines a series of improvements to the Decidim Assemblies (decidim-assemblies) module, used for participatory spaces and councils.
This module consists of a high-level section (similar to Participatory Processes) where the existing assemblies are linked to their specific pages where their characteristics and functions can be consulted (documentation, meetings, etc.)

Main related issues

• Improvements to Assemblies - MVP Improvements to Assemblies MVP #2709

• Design for Assemblies homepage (General) Design for Assemblies homepage (General) #2594

• Improvements to Assemblies - Iteration 1 Improvements to Assemblies - Iteration 1 #2832

• Improvements to Assemblies - Iteration 2

Assemblies homepage (general) must:

• Include a general description of the Assemblies homepage.
• Show a full list of Assemblies, filterable by type of assembly (sectorial, city, district, neighbourhood, others) with the filter and browser available for other components such as Proposals or Meetings.
• Show an organisational chart of assemblies with their relationships (e.g. the working groups of an assembly).
• Show the map of meetings for all assemblies.

An Assembly (in terms of the database) must include the following additional fields:

• Area: territorial or sectoral, to be chosen from the general areas, or it should be possible to define the area manually. [MVP --> Improvements to Assemblies MVP #2709 ]
  • Territorial areas: City, District, Neighbourhood.
  • Sectorial areas: (e.g. Economy and Finance; Social Rights, Culture and Sports; Citizen Rights, Participation, Security and Prevention; Ecology, Urban planning and Mobility; etc.)
• Function of the Assembly (Purpose of action). [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
• Type of Assembly: government, executive, consultative/advisory, participatory, working group, commission, others. [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
  • In the case of a working group, it can be linked to the Assembly to which it belongs.
• Date created [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
• Created by initiative: [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
  • of the City Council;
  • the Public;
  • Others [open field]
• Duration [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
  • Indefinite
  • Fixed: end date
• Date of inclusion in Decidim [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
• Closing date and reason [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
• Internal organisation: how it is organised (functions, competencies, etc.) [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
• Composition: It must be possible to automatically generate a view of the composition of the assembly, based on the following data: the composition of the participating/integrating members as well as the groups and subgroups to which they belong/represent (for example: municipal group and group name), if it is possible to sign up to it and how to do so, and the method used to select members. [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
  • By draw or as representatives of other assemblies (indicating which ones).
  • By direct election within the assembly itself.
  • By voting for candidates through the platform.
• It must be possible to show links on the participant’s page on Decidim to the assemblies of which they are members and the groups or subgroups to which they belong. [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
• It must be possible to indicate the gender of the people belonging to the assembly, their age and origin. [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
• Types of members: [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
  • President: must include full name, group to which they belong, mode and date of designation
  • Vice president: must include full name, group to which they belong, mode and date of designation
  • Secretary
  • Others (it must be possible to specify one or more fields)
• Composition of internal working groups (e.g. oversight committee, advisory commission, etc.)
• Changes in the members of the assembly must be recorded in the assembly’s history.
• Characteristics of the assembly: [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
  • Is it Open (yes/no)?: Indicates whether the assembly is open to direct participation from the public. If the answer is “no”, the next question should be displayed.
  • Is it Public (yes/no)?: Shows whether attendance to the assembly is open to the public or not. If the answer is “no”, the next question should be displayed.
  • Is it Transparent (yes/no)?: This shows whether the acts and information on assembly meetings are accessible to the public.
  • If it is special, a field must be shown to explain the characteristics (e.g. restricted to members of an organisation, aimed at a specific audience, etc.)
  • These characteristics are inherited by all the face-to-face meetings created by the assembly.
• Social networks of the assembly, with the following fields: [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]
  • Name of the network (Twitter, Facebook, etc.)
  • Link to website.
• Show the upcoming meetings of the assembly. [Iteration 1 --> Improvements to Assemblies - Iteration 1 #2832]

In terms of functionalities, the following should be possible:

• Follow an assembly and be able to receive assembly updates (documents added, new face-to-face meetings, new proposals, etc.) by direct messaging. [MVP --> Improvements to Assemblies MVP #2709 ]

Relationship between assemblies

• It must be possible for an assembly to have children (e.g. working groups). [MVP --> Improvements to Assemblies MVP #2709 ]

Relationships with other Spaces and Components

Processes

• It must be possible to link participatory processes (e.g. elections for positions) to assemblies. [MVP --> Improvements to Assemblies MVP #2709 ]

Fridge

Assemblies homepage (general) must:

• Show the calendar of meetings for all assemblies.~~

An Assembly (in terms of the database) must include the following additional fields:

• Composition:
  • By direct request.

In terms of functionalities, the following should be possible:

• Link to the agenda of the meeting with YouTube videos or other video streaming platforms (marking the specific timing of interventions).

Relationship between assemblies

• Two assemblies can be merged into one.
• An assembly can be divided into two.

Relationships with other Spaces and Components

Processes

• It must be possible for an assembly to be the promoter of a process.
• It must be possible for an assembly to make proposals as part of a participatory process (even if it was not initiated by that assembly).
• It must be possible for an assembly to start a participatory process.

Proposals

• It must be possible to see all the proposals arising from an assembly’s meetings and sort them by dates.
• It must be possible to label proposals as generated by an assembly, even if they are not directly associated with a meeting.
• There may be various types of proposals:
  • Proposals for municipal action.
  • Proposals for modification or objection to given public action.
  • Reports and opinions on action plans or actions already carried out.
  • Request for a municipal position to make an appearance (Art. 44 NRP (Rules Regulating Citizen Participation).
  • Requests to other supramunicipal administrations or Manifests that people can sign.
• Like any proposal, these must be accepted or rejected. The rejection must be reasoned and acceptance can be monitored.
• The proposals must identify the way they will be decided: by consensus, or majority (total or partial) as well as the votes in favour, against and abstentions.
• Add a tag if the proposal is approved by consensus.

Meetings

• It must be possible to associate meetings with assemblies.
• Meetings will automatically inherit the characteristics of the assembly.
• Meetings associated with a child assembly will automatically be associated to the parent assembly.
• A meeting may be associated with more than one assembly (Art. 49.2 NRP).
• It must be possible to link the minutes of the meetings to assemblies, and they will be independently listed in the meetings.
• As for the proposed order of agenda and other Meetings features, they will be improved in accordance with their Module (Improvements to Meetings).
• It must be possible to link citizen initiatives of the "Add an item to the council agenda" type. This request is related to the assembly and not to the meeting. In the event it cannot be accepted for a planned meeting, it will be placed into the next meeting and cannot be eliminated.