You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "yes/no/abstention" schema is not enough for certain use cases. For instance, voting for a type of tree to plant in given zone choices should be a list of tree types
The text was updated successfully, but these errors were encountered:
Right now there is only one type of proposals (yes/no/abstention).
I am going to add an extra table called Choices where i am going to store the values for the differente choices a proposal can have. (Proposal has many choices)
As most of the proposals will be of the (yes/no/abs) type I think we can left those values "hardcoded" with the buttons as they are right now.
For the new choices there will be two types of choices one and multiple.
For multiple choices there will be check buttons to allow the voter to select one or more of the available choices.
For single option choices the voter will be presented with radio buttons.
If the number of choices is very big maybe we should switch from radio buttons and check boxes to select (not sure about this)
This might be wrong place to ask, or may be covered elsewhere, but is there any discussion of including capability for IRV (instant runoff voting) as an option into the software? It's sort of related to lists like this, and seems generally in keeping with liquid democracy ideas, but I'm new :-)
The "yes/no/abstention" schema is not enough for certain use cases. For instance, voting for a type of tree to plant in given zone choices should be a list of tree types
The text was updated successfully, but these errors were encountered: