show conv rate rate at time of posting

[owocki]

What

In github notifications Instead of

This issue now has a funding of 0.3 ETH (201.0 USD) attached to it.

we should say something like

This issue now has a funding of 0.3 ETH (201.0 USD @ $700/ETH) attached to it

Requirements

• support eth/usd
• support any other ratio that has a conversion rate in the backend

Places to update:

• tip / github marketing
• bounty / github marketing
• bounty / slack marketing
• bounty / twitter marketing
• bounty/email marketing
• bounty details page

[gitcoinbot]

This issue now has a funding of 0.04 ETH (44.47 USD) 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
• $12318.97 more Funded OSS Work Available at: https://gitcoin.co/explorer

[tansaku]

@owocki any pointers as to where in the codebase changes would be required to implement this? My guess is here: https://github.com/gitcoinco/web/blob/master/app/dashboard/notifications.py#L219

[owocki]

@tansaku you could use the convert_amount() function in economy/utils

[bhenze]

Seems straight forward. I can start digging into it now.

[gitcoinbot]

Work has been started on the 0.04 ETH (41.48 USD) funding by:

1. @bhenze

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.

• Learn more on the gitcoin issue page
• Questions? Get help on the Gitcoin Slack
• $11331.1 more Funded OSS Work Available at: https://gitcoin.co/explorer

[bhenze]

I have everything except for the email. I was thinking about exposing a member in the Bounty object to return the USDT value of ETH. Does this sound reasonable?

[bhenze]

@owocki I am having difficulties setting up the database and am unable to test my changes. Do you happen to have an easy way I can test my updates?

[owocki]

@owocki I am having difficulties setting up the database and am unable to test my changes. Do you happen to have an easy way I can test my updates?

docker is pretty easy way to go.. if you post in slack and tag myself or @mbeacom if you have any issues.. that could work.

if the changes are small enough, you could maybe test them via the command line.

I have everything except for the email. I was thinking about exposing a member in the Bounty object to return the USDT value of ETH. Does this sound reasonable?

this exists already. its called value_in_usdt

[bhenze]

@owocki I was able to get docker to work and am able to test the page itself but having problems getting data to stick. I tried setting up a local database but to no avail. The changes are fairly small and can test some through the command line.

Also,

value_in_usdt exists but eth_value_in_usdt for 1 ether does not exist. This is more or less what I was trying to test on the bounty details page and emails.

[mbeacom]

@bhenze The docker-compose stack provisions a postgresql instance for you. You can view the data in your database by browsing to: http://localhost:8081 which is running pgweb. Or you can access via psql cli with: psql -h localhost -U postgres - If you don't have psql, you can install it on mac via brew install postgresql

[bhenze]

@mbeacom thanks for your help! I am new to psql so I have been messing with it a bit. Ended up going down quite the rabbit hole but I am back on track now. My test environment is up and running.

[amites]

so what's going on with this one?

I see the MR has fresh comments

[bhenze]

Just responding to the comments now.

[bhenze]

Sorry, if you are asking for specifics. I am trying to figure out what the preferred format for the message should be:

"($201.0 @ 700 USD/ETH)"
... or ...
"($201.0 @ $700/ETH)"
depending on the answer to my question above

[scottydelta]

I agree to @tra38's point. People who don't deal in ETH have no idea how big or small a bounty is when only given in terms of ETH. Showing the $ value might be something which will attract more users to take up the tasks for the bounties.

[scottydelta]

I like @lazaridiscom's suggestion here at issue #460, we can finally just have:

This issue now has a funding of - More information at: Gitcoin

And there is definite need to limit the number of messages a bot can add to an issue(this thread is a good example), since we are going for a single line message, can we just have only one Gitcoin Bot message per issue and new messages gets appended to the old one like a log?

EDIT: replaced price URI from my personal domain to coinbase which only provides price and not the value of required ETH in USD and edited accordingly.

[gitcoinbot]

Work has been started on the 0.04 ETH (37.4 USD) funding by:

1. @scottydelta

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.

• Learn more on the gitcoin issue page
• Questions? Get help on the Gitcoin Slack
• $10276.08 more Funded OSS Work Available at: https://gitcoin.co/explorer

[bhenze]

So what is the plan for this issue then? Do we want to update the story to reflect the proper verboseness?

[bhenze]

Sounds good! thanks for the input.

[mbeacom]

@bhenze @lazaridiscom Glad to have you both here and actively engaged!
If you're ever uncertain about whether or not to proceed with working on something, feel free to reach out to us / request evaluation of your proposed idea. We'd be more than happy to work through it with you. When in doubt, feel free to reach out.
We encourage community feedback and contributions!

For this particular issue, I think it's safe to proceed with the scoped out change provided by @owocki.
As for the newly proposed changes, we think that’s a good idea to have a dynamic banner.
Right now, we aren’t sure how to implement the changes quite yet. Let’s discuss that issue separately on the Github thread and bounty once we agree on the approach. Sound good?

[bhenze]

@mbeacom happy to help where I can! And yeah, that sounds great.

[owocki]

looks like gitcoin bot is going haywire. sorry everyone. planning on triaging today / tomorrow

[owocki]

just put in a fix ( 12c8837 ) . deleting the erroneous comment right now

[vs77bb]

@bhenze @scottydelta Poking in here, who is working this one right now? It seems like this might be in need of feedback from @owocki but I can't tell for sure.

Apologies for Gitcoin Bot coming in and trying to take over 😛 (Which I can see is a topic of conversation itself).

@owocki @PixelantDesign Any thoughts to add on the approach suggestions?

[bhenze]

Yeah, this one kinda got a little confusing. I have changes #387 but there is a bit of drift now and I will need to do some manual merging. Just wanted to wait till I had the go-ahead before I did that.

[owocki]

id be happy to move over to a clean thread if that'd help make this neater :)

@bhenze let me know if you need anything from me! lets we left things i think we were on the same page

[scottydelta]

are we still adding live rates using shields.io API?

@bhenze if the answer is yes to the above question then I can work on adding that if you haven't worked on it already. thanks

[owocki]

id prefer to complete the original scope here and then consider adding that later..

[bhenze]

@owocki yup, we are on the same page. I was just waiting for a review on #387 but while I was waiting, some of those strings got updated a bit. So I just need to go back, rebase and fix those strings. I will go ahead and do that in a few and let you know when it is ready to look at.

[bhenze]

@owocki, okay. My branch is up to date with all my updates from previous reviews and all the latest code from master. Cheers!

[owocki]

commenting over at #387 now

[bhenze]

@owocki responded to your questions.

[owocki]

😍

@bhenze send me your ETH address and ill pay you out the bounty

[bhenze]

@owocki
0x0370feF36074ccd141fb3BfFee17824021dc0417

Thanks! Look forward to helping out in the future.

[owocki]

here ya go @bhenze -- thanks again! http://etherscan.io/tx/0x7c23844fb3eb7d58eb17411ece2364679e53310831c5ff135edd3eea68096e19