-
-
Notifications
You must be signed in to change notification settings - Fork 775
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
As an admin, I want Trust Through Transparency best practices for *Reading Data* implemented at Gitcoin, so I can be sure that users can trust our site. #796
Comments
This issue now has a funding of 0.15 ETH (57.16 USD @ $381.06/ETH) attached to it.
|
Work has been started on the 0.15 ETH (72.9 USD @ $485.98/ETH) funding by: Please work together and coordinate delivery of the issue scope. Gitcoin doesn't know enough about everyones skillsets / free time to say who should work on what, but we trust that the community is smart and well-intentioned enough to work together. As a general rule; if you start work first, youll be at the top of the above list ^^, and should have 'dibs' as long as you follow through. On the above list? Please leave a comment to let the funder (@owocki) and the other parties involved what you're working, with respect to this issue and your plans to resolve it. If you don't leave a comment, the funder may expire your submission at their discretion.
|
This issue has been returned to an 'Open' Status due to inactivity. Feel free to 'Start Work' if interested! |
@vs77bb the deadline could be extended? i would like work on this in the weekend 😄 |
@zoek1 no problem. just click 'start work' again over at https://gitcoin.co/issue/gitcoinco/web/796 |
@zoek1 @owocki To be fair, looks like @john-brunelle has picked this up. John, can you please provide us with an approach? @zoek1, please click 'Start Work' on the ticket as well. If John doesn't follow through, we'd love to have you work here. |
@john-brunelle was just testing the iOS app. pls disregard his claim on the work (which i've removed) |
@vs77bb i'm started with this but gitcoin doesn't allow to start the work when i clicked the button 🤷♂️ |
It appears the bounty has expired. We can tip you out and fix the bounty to display as if you completed it following submission of the PR until we decide on a course of action for expired bounties. Thanks @zoek1 ! |
@rav8815 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
Issue Status: 1. Open 2. Expired The funding of 0.15 ETH (78.34 USD @ $522.28/ETH) attached to this issue has been cancelled by the bounty submitter
|
Refers
Web3 Design Principles
See Also
#796
#797
#798
#799
#800
#801
How to Implement here:
I think that the following best practices can / should be implemented at Gitcoin:
Suggested implementation:
Perhaps there is some UI element we could add to the bounty explorer and the bounty detail page. Maybe an info popover?
Perhaps in the footer, or on this part of the app - http://bits.owocki.com/1R1Y2w3h0m0Y/Screen%20Shot%202018-04-04%20at%202.40.56%20PM.png
We'll also want to follow the best practice around 'show a compact versions of the hashes but always show the initial and end parts' and 'always prepend the “0x” to indicate that it’s a hash' and 'allow users to expand the full address/hash ' here
Definition of Done
The above 2 best practices are implemented in a way that makes sense for Gitcoin. Pls allow for 1-2 rounds of feedback on designs before moving into implementation / coding.
The text was updated successfully, but these errors were encountered: