-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Estimated matching (again) #2944
Comments
I don't know who wants to solve this. @aminlatifi do you have any opinion? |
We need to make serious changes in the back-end for this one Nobody has bandwidth for this one this sprint so we will need to visit it next sprint. |
@aminlatifi shared the snippet code. |
@laurenluz is it still in our plan? I have some similar issues like these improvements in Post Launh QF issues, let's prioritize it. |
I don't think it's needs to be a priority. no one is really noticing v. much about the estimated matching... and this fix will only somewhat improve the estimate... I think for QF other issues are more important. |
related to #2886
Post-MVP, we should improve our estimated matching so that the cap of 20% of the matching pool is applied in our backend.
For example, if we have a $10,000 matching pool... and only 5 projects had donations.
Projects 1-4 have $0.01 in donations each
Project 5 has $1000 in donations
... we should show on our UI that there is an estimated matching of $2000 per project.
This is just an example, but I hope you get the idea! @mohammadranjbarz @aminlatifi
cc @maryjaf @MohammadPCh
The text was updated successfully, but these errors were encountered: