podemos-info / participa2

participa2

Citizen Participation and Open Government application.

This is the open-source repository for participa2, a web application based on Decidim. Decidim is a framework for participatory democracy, you can find more about it at its documentation page.

Note that whereas decidim is a library, participa2 is a final application that uses Decidim. More specifically, participa2 is a Rails application, whereas decidim is a rubygem that provides a set of Rails Engines to the application using it.

On top of decidim's default functionality, participa2 adds some extra functionality implemented as decidim components. These custom components live inside the participa2 repo and are the following:

• Census Connector: Basic connection to a census of people that belong to the organization.

• Crowdfundings: Crowdfunding campaings for the democractic activity that takes places inside the organization.

• Gravity Forms: Form management interface to the Gravity Forms Wordpress Plugin.

• Votings: Votings interface to custom secure external voting systems.

Setting up the application

You will need to do some steps before having the app working properly once you've deployed it:

1. Open a Rails console in the server: bundle exec rails console

2. Create a System Admin user:

user = Decidim::System::Admin.new(email: <email>, password: <password>, password_confirmation: <password>)
user.save!

1. Visit <your app url>/system and login with your system admin credentials

2. Create a new organization. Check the locales you want to use for that organization, and select a default locale.

3. Set the correct default host for the organization, otherwise the app will not work properly. Note that you need to include any subdomain you might be using.

4. Fill the rest of the form and submit it.

You're good to go!

Deploy

bundle exec cap staging systemd:hutch:setup
bundle exec cap staging systemd:puma:setup
bundle exec cap staging deploy

participa2's Issues

Allow to delete forms

Forms can't be deleted now

Handle when census app is down

Send an email notification on email taken

Census conection integration test

Notify user deletion to census app

Use slug for forms urls

Now it uses the id

Authorizations result and expiration date

Microcredits module

Include decidim user id in forms urls

URLs must be signed to avoid id tampering

Improve revoting handling

Currently, when a vote is emited again, sets its vote state to pending. This could be confusing, since there is a confirmed vote in the ballot box. We have many options here:

• Leave it as is
• Don't set the vote as pending if it is already confirmed
• Add a confirmed-pending state
• Change the status field to a confirmed_at date field
• Store one vote for each voting emission

Email normalization

Votings module

• agora connection

Add "scope_id" column in table "decidim_votings_votes"

Add "scope_id" column in table "decidim_votings_votes" to allow a better and cleaner migration of voting votes data

Users extra attributes

• Storage
• Automated update from census app

Offer become a member to grown up young members

Handle document scope for passports

Ensure a message about invalid scope reaches the user if trying to vote on a wrong scope

For now, I'm removing the unused i18n key in ad98dfd.

However, I'm not sure about this one. We should definitely protect against this at the controller level but will there be an expected user flow that results in this? In the case of protecting at the controller level, I'm not sure we should give such a specific message to the user. 🤔

Scopes updating process

• Deprecated scopes handling

Add pending scope types (islands, JEZs)

• alternative paths support needed

Authorizations tests

Users timezone management

Related to address scope. Should be used for activities start and ending hours when different from main timezone (and show main timezone small below).

Data migration

• users
• - verifications
• - paper_trail (?)
• elections
• - votes
• collaborations
• - payments

User account deletion for admin users

To process requests received by email or other.

Ensure voting cannot happen on inactive votings

Related dead code will be removed in 306cb6e.

Again, this looks like it only needs protection at the controller level but it's not an expected code path to actually try to vote on inactive votings?

Ensure voting can be restricted to users registered before a certain timestamp

The backend is already implemented, I think. The half implemented feature on the frontend side will be removed in f30b164.

User data report form

Use citizenship scope for document input

Change of address or phone form

Allow to create assembly users

Fix UK scopes

Should we seed staging on every deploy?

Currently the seed process is very slow and makes consecutive deploys fail.

I was thinking that we could pg_dump a brand new seeded DB, and then pg_restore on deployment, but then I realized that seeds in decidim don't lead to a known fixed state, but instead seed random data so I'm not sure reseeding actually buys us much, since the final state will be "random" anyways. Should we instead leave staging data untouched?

Car & home sharing module

External system integration or replacement

• volunteers (campaign and proxies)
• forms
• newsletters

Upgrade ruby version to 2.5.1

This needs some coordination for deployment (right?). But it'd be nice to get this up to date for speed, security and all that stuff :)

Galego language

Translatable texts must be always required?

Collaborations module

• Recurrent
• Unique