Proposal Portal - Retroactive Grants proposal workflow

[idiom-bytes]

Problem:

• We need to build the retroactive grants proposal flow
• Proposals should not be accepted into the round right away and should perhaps go into a staging area

Towards Solutions:

Retroactive grants workflow

• Inside the schema, we could have 2 types/enums ('previous', and 'retroactive'), and force type #2
• Default proposal schema would default to 'retroactive'
• Proposals enter a staging environment (or not)
  • Do we need a staging environment or can we receive the proposal into "pending"
  • then it can go into "accepted" or "rejected"

[Accepting/Rejecting Proposals & Resubmitting ]

• Do they have to create a new proposal in R2 if it's rejected during R1?
• Can they update their existing proposal, and resubmit into the same round?

[Providing Feedback vs. Accepting/Rejecting]

• separate the Providing Feedback from Accepting/Rejecting
• this may lead to less requirements implementation wise, or workflow

[Staging Port Category]

• Can we do this? should we do this?
• Are there other ways of handling the Port/Discourse side of things.
• (Malte) Leave them available in the Admin portal until accepted. Problem: It should go away when the round starts, or some other method. Perhaps a separate page?

DoD:

• [ ] Inside the proposal portal the user can submit a retroactive proposal, and be taken through the full UX path.
• [ ] Proposal sits a pending state, which when accepted, is submitted into the voting period.

[malvonme]

Thank you!