gitcoinco / gitcoinco/easy-retro-pgf
Evaluate feedback from RetroPGF3: Learnings & Reflections
- Dominant language
- TypeScript
- Stars
- 66
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
https://optimism.mirror.xyz/Bbu5M1mTNV2Z637QxOiF7Qt7R9hy6nxghbZiFbtZOBA
> “Extremely unfortunate that there was no way to import CSV so it had to all be added back to the interface manually. :/” - Amy
> “I used [West’s voting platform 4](https://round3.optimism.io/), and overall I found it quite intuitive and easy to use. For the next round of RPGF it would be good to add a) functionality for editing, forking, removing lists, and b) ballot import/export functionality to support the people working offline with spreadsheets - this would also be useful at times when the servers are experiencing overload.” - Joanbp
- [x] Import / Export CSV
> “We should have the option to write notes on applications for ourselves (i.e. non public). And e.g. have buttons to indicate if we want to vote for them or not (“Yes”, “No”, “Maybe” or blank), and then use that to filter applications.” - CheekyGorilla
- [ ] Private comments for applications (low effort could be to store in device local storage)
> “it would be great if there was a "hide from view" for projects that i have looked at and evaluated as not a candidate / that i will not be allocating towards / voting to” - Jenny
> “I have a few pieces of feedback I shared with the agora team before voting started that I think could make it better-have the ability to mark a project as seen or “don’t put in ballot” option-have the ability to allocate percentages as well as dollar amount-get rid of the lists function” - Katie
- [ ] Hide projects (low effort could be to store in device local storage)
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the linked RetroPGF3 feedback and locate the application and ballot UI; the issue names no files or tests. Confirm the scope for private application comments and hiding projects, with device-local storage suggested as a low-effort option, then verify both behaviors in the relevant UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100