VoteIT / VoteIT/voteit

Groups for meetings - advanced features

Open
#93 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

hold
Dominant language
Python
Stars
2
Forks
0
Avg merge
1d 2h
Merged PRs (30d)
1

Description

A lot of functionality in VoteIT3 depends on users belonging to one or more groups. This needs to be implemented here too. By using meeeting-bound groups we can fix the following functionality:

  • Vote as organisation with a different number of votes.
  • Handled in #96 : Handle groups like "board" or "presidium" etc, so users that belong to that group may add proposals as that group.
  • Have votes that belong to organisations rather than individuals.
  • Use roles within a group.
  • Meeting-wide policies for groups, like "users can only belong to one group", "only groups have votes" etc

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.

Research direction

No files or tests are named; start by locating the existing meeting, user, and group models and reading the related work in #96. Define acceptance criteria for voting, roles, organisation-owned votes, and meeting-wide policies before implementing and testing the agreed scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.