liquidvotingio / liquidvotingio/api

Proposal collection reference field

Open
#245 3 comments 0 reactions 1 assignee View on GitHub

@oliverbarnes is already working on this.

Since Apr 29, 2021.

Dominant language
Elixir
Stars
17
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Decidim participatory budgets integration brings up the scenario of voting on a selection of projects:

> Open question: the delegation will be given within the scope of the budget - so neither globally, nor individually for each project/proposal. How do we solve that? We have the idea of delegations by category in the horizon, but I'm not sure that's a fitting abstraction for what is in the end a custom selection of projects. This scenario might come up again where there's multiple choices involved (the scope of a question, for instance, for multiple answers).
(https://github.com/liquidvotingio/decidim-module-liquidvoting/issues/45#issuecomment-819726486)

I'm thinking the API needs a proposal collection reference field for delegations that could account for different kinds of proposal buckets. This would still be external as the bucket will be platform-dependent. And the initial assumption, which we need to confirm, is that it'll have its own url.

Possible candidates:
- scope_url
- proposal_collection_url
- proposal_group_url
- proposal_collection_url

There's also the issue of whether `proposal` itself is still a valid abstraction (say people are voting on answers rather than proposals), that perhaps precedes this. I'll open a discussion for it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.