Feat: decidim private fields

[froger]

Include a new feature in the Awesome module: Add private fields to custom proposals.

As a participation designer, I can define private fields for proposals to ask proposers for personal information. This personal information could be required to submit a proposal and should not involve an extra step in the proposal submission process.

Context
The city of Lausanne wanted to request private fields for their Participatory Budgeting (PB) in order to:

• Get consent for contacting proposers.
• Obtain a phone number.
• Collect additional information on the project (e.g., postal addresses to send materials).

Open Source Politics also contributes, financing adaptations for export and compatibility with version 0.27. <3

Solution

In the custom field administration, add another "custom field" zone, reserved for private fields.
In the form, add a section at the end for private fields.
Add an exporter, not exposed to open-data, to export personal data from the administration.
Change exporters of proposals to include custom fields.

Screenshots
Proposal form, user side

Confirm screen, without private data

Published proposal, without private data

Visualization of the fields, admin side

Export options for private data

Proposal administration

[froger]

So from the pipelines, I see I need to do at least:

• Fix tests to have pipelines passing
• Fix linting

[froger]

Putting this PR in draft the time I make the necessary updates.

[simonaszilinskas]

Hey @froger , just wanted to ask if you had any news concerning the requested changes

[paarals]

Hey @froger , just wanted to ask if you had any news concerning the requested changes

also, this feature will may be cover with Roadmap (view).

[froger]

Hello all,

• The administration looks now better, but still is without tabs. After discussing with Lucien, we will make a design proposal to refactor the administration of decidim awesome in a more sustainable way. (in another issue).
• The private fields are now encrypted
• The PR should looks a bit better, synced with develop branch
• private fields are now a jsonb , that can handle translation (still don't know why we would translate private data)

We still miss:

• pipelines that should pass
• tests should pass, it seems some tests on collaboratives drafts are not passing, didn't checked this out yet.

[froger]

Hey @froger , just wanted to ask if you had any news concerning the requested changes

also, this feature will may be cover with Roadmap (view).

Our customer needs where quiet specifics to having a "private section" of the form. I am unsure the feature you mention will attend their need, but we can discuss on this.

[microstudi]

@froger if you are ok with it, we are going to finish this PR as we have time and certain pressure to finish it this month.

I'd like very much to maintain you as the author of the PR to recognize your good work. To do so, you should create this PR from a branch in this repository (I've invited you now), then we will be able to add commits to it in order to finish it.

On the other hand, we will make a new PR for the develop branch to add this feature to the 0.28 too.

[froger]

closing in favor of #314
@microstudi as discussed, I've open a branch local to this repository. Feel free to update the code ;)
Thanks a lot for your help.

[microstudi]

Thanks to you @froger , we'll finish this!