Skip to content
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

Closed
owocki opened this issue Apr 4, 2018 · 11 comments

Comments

@owocki
Copy link
Contributor

owocki commented Apr 4, 2018

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:

  • Clarify which data comes from the Blockchain and which doesn’t
  • Clarify the address of the contract(s)

Suggested implementation:

Clarify which data comes from the Blockchain and which doesn’t

Perhaps there is some UI element we could add to the bounty explorer and the bounty detail page. Maybe an info popover?

Clarify the address of the contract(s)

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.

@gitcoinbot
Copy link
Member

This issue now has a funding of 0.15 ETH (57.16 USD @ $381.06/ETH) attached to it.

  • If you would like to work on this issue you can claim it here.
  • If you've completed this issue and want to claim the bounty you can do so here
  • Questions? Get help on the Gitcoin Slack
  • $2388.91 more Funded OSS Work Available at: https://gitcoin.co/explorer

@gitcoinbot
Copy link
Member

Work has been started on the 0.15 ETH (72.9 USD @ $485.98/ETH) funding by:

  1. @john-brunelle

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.

@vs77bb
Copy link
Contributor

vs77bb commented Apr 27, 2018

This issue has been returned to an 'Open' Status due to inactivity. Feel free to 'Start Work' if interested!

@zoek1
Copy link
Contributor

zoek1 commented May 1, 2018

@vs77bb the deadline could be extended? i would like work on this in the weekend 😄

@owocki
Copy link
Contributor Author

owocki commented May 1, 2018

@zoek1 no problem. just click 'start work' again over at https://gitcoin.co/issue/gitcoinco/web/796

@vs77bb
Copy link
Contributor

vs77bb commented May 1, 2018

@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.

@owocki
Copy link
Contributor Author

owocki commented May 1, 2018

@john-brunelle was just testing the iOS app. pls disregard his claim on the work (which i've removed)

@zoek1
Copy link
Contributor

zoek1 commented May 5, 2018

@vs77bb i'm started with this but gitcoin doesn't allow to start the work when i clicked the button 🤷‍♂️

@mbeacom
Copy link
Contributor

mbeacom commented May 5, 2018

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 !

@gitcoinco gitcoinco deleted a comment May 26, 2018
@gitcoinbot
Copy link
Member

@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!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@gitcoinbot
Copy link
Member

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

@kuhnchris kuhnchris added this to the Backlog > 1 Year - Relevance Check milestone Aug 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants