Propose new functionalities for Decidim software

Fingerprint

The piece of text below is a shortened, hashed representation of this content. It's useful to ensure the content hasn't been tampered with, as a single modification would result in a totally different value.

Value: 491be12c34adbf9918863059df054d722f908460c98065c53b97bbad83179fcb

Source: {"body":{"en":"<p><strong>Is your feature request related to a problem? Please describe.</strong></p><p>With the actual voting systems on participatory budgets, users can vote according to a percentage of the total budget, or with a min or max of projects to be voted on. The problem is that they <u>can't express any preference for a specific project by granting it several votes</u>. </p><p>As a user voting in participatory budget process, I want to express different levels of support to the projects I'm voting for.</p><p>As an admin I might want to implement rules to register that information and adapt my vote tally accordingly.</p><p><strong>Describe the solution you'd like</strong></p><p>As a user, I want to be able to give several votes of my total votes to the same project. To do this, I want to see next to on the budget card and pages a voting button method allowing me to assign multiple votes for each project.</p><p>As an admin, I want to have config flags to activate this voting method in the admin panel (in the \"voting rules\" section of the Budget component) and have a field to configure a maximum of votes a user can give to a single project.</p><p><strong>The doubts we have</strong></p><p><u>We're asking ourselves a lot of questions about this feature, so if you have any insights please share</u>! </p><ul><li>How can we make a scalable design ? </li><li>Do we keep a clear \"Voting\" button on the project, and then display the voting by points? Or vice versa? </li><li>Should this be a new independent voting rule or should it be compatible with others? Which ones? </li></ul><p><strong>Additional context</strong></p><p>For now, we have thought about the attached design, which we think is more scalable than the one with a <a href=\"https://user-images.githubusercontent.com/24740/69743328-88dc3980-113e-11ea-8f32-c48856b2f1c0.png\" target=\"_blank\">hovered scale</a>. This would allow the admin to enter any number he wants in the field \"maximum number of votes the user can allocate to a project\".</p><p><strong>Does this issue could impact on users private data?</strong></p><p>No</p><p><strong>Related links</strong></p><p><a href=\"https://meta.decidim.org/processes/roadmap/f/122/proposals/15058\" target=\"_blank\">Token voting rule on Budget component</a> (withdrawn)</p><p><a href=\"https://meta.decidim.org/processes/roadmap/f/122/proposals/14931\" target=\"_blank\">Provide new option to support a proposal: with a scale</a></p><p><a href=\"https://drive.google.com/file/d/1L4i-3u6I--jap7q9hNxkzDHZY5wUWjzk/view?usp=sharing\" target=\"_blank\">A study conducted by Toulouse about voting methods on participatory budgeting</a> (in french)</p><p><strong>Funded by</strong></p><p>Toulouse</p>"},"title":{"en":"Vote multiple times for a same project"}}

This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online and copy-paste the source data. ×