{"action":"created","issue":{"url":"https://api.github.com/repos/decred/politeiagui/issues/1491","repository_url":"https://api.github.com/repos/decred/politeiagui","labels_url":"https://api.github.com/repos/decred/politeiagui/issues/1491/labels{/name}","comments_url":"https://api.github.com/repos/decred/politeiagui/issues/1491/comments","events_url":"https://api.github.com/repos/decred/politeiagui/issues/1491/events","html_url":"https://github.com/decred/politeiagui/issues/1491","id":506732798,"node_id":"MDU6SXNzdWU1MDY3MzI3OTg=","number":1491,"title":"RFPs in the proposal list views","user":{"login":"lukebp","id":9039877,"node_id":"MDQ6VXNlcjkwMzk4Nzc=","avatar_url":"https://avatars3.githubusercontent.com/u/9039877?v=4","gravatar_id":"","url":"https://api.github.com/users/lukebp","html_url":"https://github.com/lukebp","followers_url":"https://api.github.com/users/lukebp/followers","following_url":"https://api.github.com/users/lukebp/following{/other_user}","gists_url":"https://api.github.com/users/lukebp/gists{/gist_id}","starred_url":"https://api.github.com/users/lukebp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lukebp/subscriptions","organizations_url":"https://api.github.com/users/lukebp/orgs","repos_url":"https://api.github.com/users/lukebp/repos","events_url":"https://api.github.com/users/lukebp/events{/privacy}","received_events_url":"https://api.github.com/users/lukebp/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2019-10-14T15:42:05Z","updated_at":"2019-10-14T19:01:17Z","closed_at":"2019-10-14T19:01:17Z","author_association":"MEMBER","body":"The request for proposal (RFP) backend work is nearing completion.  One item that still needs to be decided is how the RFP proposal and the proposals that are submitted to the RFP (RFP options) are going to be displayed in the proposal list views.  These design decisions will effect how RFP proposals and the RFP options are returned in the `TokenInventory` call.  The backend RFP work cannot be completed until we figure this out.\r\n\r\nA little background on how the RFP process will work.  An RFP is a special kind of proposal that allows other proposals to link to it.  I'll use the market maker proposals to illustrate how it works.\r\n \r\n- jz would have submitted an RFP proposal detailing what the Decred community was looking for in a market maker and opening up the process for potential market makers to submit proposals that link to the RFP.\r\n- Market makers submit individual proposals that are linked to the RFP proposal.  Each proposal submitted and linked to the RFP becomes an RFP option.\r\n- When an admin starts the voting process on the RFP, the vote commences on all of the RFP options simultaneously.  The Decred stakeholders vote yes/no on each of the RFP options individually like you would normal proposals.  The RFP proposal itself is never actually voted on.\r\n- The proposal with the most net yes votes wins (must also meet the normal quorum requirement).  The i2 proposal would be declared the winner.  There can only be one winner so even if one of the other market maker proposals met the 60% pass requirement, their proposal would still be considered rejected if it did not get more net yes votes than the i2 proposal.\r\n\r\nWe need to figure out how these RFP proposals and RFP options will be displayed in the proposal list views.\r\n\r\n**Considerations:**\r\n- The RFP options fit into the existing architecture where a proposal is either approved, rejected, or abandoned, but the RFP proposal itself does not since it is never actually voted on.  Once the voting period has ended on the RFP options, what tab (approved, rejected, abandoned, etc) should the RFP proposal be listed under?\r\n- Should the RFP options be listed as individual proposals in the list views or should the RFP and all of the RFP options be grouped together as a single item?\r\n- It will be possible for an RFP option to meet the normal quorum and pass requirements, but still be rejected if one of the other RFP options has more net yes votes.  This could lead to confusion if, for example, a proposal with a 70% pass rate that met the quorum requirement is listed in the \"Rejected\" column.\r\n\r\n**Potential Solutions**\r\n1. We could group the RFP and all the RFP options as a single list item.  After the vote is over, the list item would should the yes/no results for each RFP option.  The RFP list item would be listed under the \"Approved\" tab if one of the options was approved.  It would be listed under the \"Rejected\" tab if none of the options met the quorum and pass requirements.\r\n- Cons: the only way to access an individual RFP option would be through the RFP proposal.  The RFP options would not be listed individually under the Approved, Rejected, or Abandoned tabs.  This could be confusing since the RFP proposals are voted on individually so you may think that they should be listed in the Approved, Rejected, or Abandoned tabs based on their individual outcome.\r\n\r\n2. The RFP proposal would be listed under a new RFP tab.  The RFP options would be listed individually under the Approved, Rejected, and Abandoned tabs based on the outcome of their individual vote.\r\n- Cons: a proposal that would normally be considered approved because it met the normal quorum and pass requirements could still be listed under the rejected tab if another RFP option received more net yes votes.  This is confusing.\r\n\r\nI need the design team to put some thought into this and weigh in.\r\ncc: @linnutee @MariaPleshkova "},"comment":{"url":"https://api.github.com/repos/decred/politeiagui/issues/comments/541860040","html_url":"https://github.com/decred/politeiagui/issues/1491#issuecomment-541860040","issue_url":"https://api.github.com/repos/decred/politeiagui/issues/1491","id":541860040,"node_id":"MDEyOklzc3VlQ29tbWVudDU0MTg2MDA0MA==","user":{"login":"lukebp","id":9039877,"node_id":"MDQ6VXNlcjkwMzk4Nzc=","avatar_url":"https://avatars3.githubusercontent.com/u/9039877?v=4","gravatar_id":"","url":"https://api.github.com/users/lukebp","html_url":"https://github.com/lukebp","followers_url":"https://api.github.com/users/lukebp/followers","following_url":"https://api.github.com/users/lukebp/following{/other_user}","gists_url":"https://api.github.com/users/lukebp/gists{/gist_id}","starred_url":"https://api.github.com/users/lukebp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lukebp/subscriptions","organizations_url":"https://api.github.com/users/lukebp/orgs","repos_url":"https://api.github.com/users/lukebp/repos","events_url":"https://api.github.com/users/lukebp/events{/privacy}","received_events_url":"https://api.github.com/users/lukebp/received_events","type":"User","site_admin":false},"created_at":"2019-10-14T19:01:17Z","updated_at":"2019-10-14T19:01:17Z","author_association":"MEMBER","body":"I had this incorrect.  The RFP proposal will actually be voted on.  Only once the RFP proposal has been approved will there be a period that allows other proposals to link to the RFP, then there will be a separate vote on those proposals.  This makes displaying RFP proposals in the gui much easier since they will fit into the existing approved or rejected tabs.\r\n\r\nClothing this issue."}}
{"actor":{"display_login":"lukebp"}}