liquidvotingio / liquidvotingio/decidim-module-liquidvoting
Feature toggle
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Currently when our module is added liquidvoting overrides every instance of each voting method it's integrated with (at this point only participatory process proposal supports).
In order to allow for partial adoption (eg: smaller scale pilots within a larger instance), admins should be able to choose where to activate liquidvoting, piecemeal.
I'm thinking of a feature toggle on the overriden modules' admin interface, like Marc had suggested, rather than having an admin for liquidvoting itself - this way we bypass the overhead of componentizing the module.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the liquidvoting module overrides and the admin interfaces for the supported participatory process proposal. Trace how those overrides are activated, then determine how an administrator can enable liquidvoting for selected instances rather than all instances. Done means partial adoption is possible without a separate liquidvoting admin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100