Skip to content

Improvements to Assemblies - Iteration 1 #2832

@carolromero

Description

@carolromero

Depends on EPIC: #2708

This is a Feature Proposal

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

  • editor Function of the Assembly (Purpose of action).
  • selector Type of Assembly: government, executive, consultative/advisory, participatory, working group, commission, others.
    • In the case of a working group, it can be linked to the Assembly to which it belongs.
  • date Date created
  • selector Created by initiative:
    • of the City Council;
    • the Public;
    • Others [open field]
  • date Duration
    • Indefinite
    • Fixed: end date
  • date Date of inclusion in Decidim
  • date Closing date and reason editor
  • editor Internal organisation: how it is organised (functions, competencies, etc.)
  • editor Composition: It must be possible to automatically generate a view It must be possible to explain 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.
    • 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.
    • By direct request.
  • It must be possible to show links on the participant’s public profile on Decidim to the assemblies of which they are members and the groups or subgroups to which they belong.
  • [WIP] relation Members:
    • 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)
    • [WIP] It must be possible to indicate the gender of the people belonging to the assembly, their age and origin.
    • [WIP] Changes in the members of the assembly must be recorded in the assembly’s history.
  • string Composition of internal working groups (e.g. oversight committee, advisory commission, etc.)
  • selectorCharacteristics of the assembly:
  • Private field (checkbox): remains the same as the other spaces. If it is not activated, the Assembly is public and open (anyone can participate in it).
  • Transparent field (checkbox): by default it is activated and disabled. If you activate the Private field, the Transparent field is enabled and you can deactivate it, that means that the Assembly is private and not transparent.
    Depending of the options selected we'll have 3 different Assemblies:
    • Open: anyone can see it and participate.
    • Private: only members can see it and participate.
    • Transparent: only members can participate but anyone can see it.
    • These characteristics are inherited by all the face-to-face meetings created by the assembly.
  • string Social networks of the assembly, with the following fields:
    • Name of the network (Twitter, Facebook, etc.)
    • Link to website.
  • Show the upcoming meetings of the assembly.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions