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
Intent: By giving a voice to community members in decisions that matter, we let them help shape the ecosystem based on their experiences, needs, and preferences, leading to better ecosystem-community fit.
Description: Let admin configure voting, incl category specific parameters, and let voters cast votes according to that configuration
Outcome: Get admin feedback on ease and flexibility of voting setup; get voter feedback on the experience and understandability of voting
Focus roles: admin + voter
Value Delivery
-Give community members a voice in decisions that matter, in a way that the community can trust
-Accelerated ecosystem innovation with crowdsourced decisions
-Improve ecosystem-community fit
-Enable us to get feedback on voting setup and participation
Design Principles
-Enrich data over time
-Reduce overwhelm
-People powered innovation
-Privacy by design
Expected experiment outcome: We want the admin teams to tell us that the voting configuration meets their needs and they have high confidence in its ability to replace the current processes. We want voters to tell us that voting is easy, understandable, and fun. We want voters to help us better understand the reasons they vote for proposals, how they make decisions, and what would make them cast more votes
Workflow:
-ADMIN input JSON to configure voting parameters for campaign and categories
-ADMIN edit JSON elements from UI
-VOTER browse campaigns, categories, proposals, reviews in voting space
-VOTER see tentative voting power prior to snapshot, final voting power after
-VOTER select proposals, review details, and add to voting list
-VOTER view vote list, change choice, remove from list
-VOTER review choices, sign with key, submit, and get confirmation
-VOTER see voting history and verify past votes
Action Labels
-Setup Voter Voting Power
-Setup Voter Snapshot
-Register as voter #discuss: guest view, turn into participant
-View my tentative voting power
-View my final voting power
-View published proposals
-View vote list / remove item
-Add / remove proposal to / from vote list
-Cast / sign batch of votes
-View voting history
**DISCUSS: volatile vs stable vs final voting power needs to be understood. Design decision on what to show users when. As a user, I want to see my tentative voting power be as close to real time as possible, but I should understand the potential for rollbacks and changes.
Summary
MVE7
JIRA Epic
https://input-output.atlassian.net/browse/NPG-7772
Description
Intent: By giving a voice to community members in decisions that matter, we let them help shape the ecosystem based on their experiences, needs, and preferences, leading to better ecosystem-community fit.
Description: Let admin configure voting, incl category specific parameters, and let voters cast votes according to that configuration
Outcome: Get admin feedback on ease and flexibility of voting setup; get voter feedback on the experience and understandability of voting
Focus roles: admin + voter
Value Delivery
-Give community members a voice in decisions that matter, in a way that the community can trust
-Accelerated ecosystem innovation with crowdsourced decisions
-Improve ecosystem-community fit
-Enable us to get feedback on voting setup and participation
Design Principles
-Enrich data over time
-Reduce overwhelm
-People powered innovation
-Privacy by design
Expected experiment outcome: We want the admin teams to tell us that the voting configuration meets their needs and they have high confidence in its ability to replace the current processes. We want voters to tell us that voting is easy, understandable, and fun. We want voters to help us better understand the reasons they vote for proposals, how they make decisions, and what would make them cast more votes
Workflow:
-ADMIN input JSON to configure voting parameters for campaign and categories
-ADMIN edit JSON elements from UI
-VOTER browse campaigns, categories, proposals, reviews in voting space
-VOTER see tentative voting power prior to snapshot, final voting power after
-VOTER select proposals, review details, and add to voting list
-VOTER view vote list, change choice, remove from list
-VOTER review choices, sign with key, submit, and get confirmation
-VOTER see voting history and verify past votes
Action Labels
-Setup Voter Voting Power
-Setup Voter Snapshot
-Register as voter #discuss: guest view, turn into participant
-View my tentative voting power
-View my final voting power
-View published proposals
-View vote list / remove item
-Add / remove proposal to / from vote list
-Cast / sign batch of votes
-View voting history
**DISCUSS: volatile vs stable vs final voting power needs to be understood. Design decision on what to show users when. As a user, I want to see my tentative voting power be as close to real time as possible, but I should understand the potential for rollbacks and changes.
Extract addtl requirements from #109
Design tasks
Backend tasks:
Todo
<list 1 name>
<list 2 name>
The text was updated successfully, but these errors were encountered: