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

Bot / Github integration Revamp #34

Closed
owocki opened this issue Oct 19, 2017 · 3 comments
Closed

Bot / Github integration Revamp #34

owocki opened this issue Oct 19, 2017 · 3 comments

Comments

@owocki
Copy link
Contributor

owocki commented Oct 19, 2017

  1. Repo level permissions that allows repo owners to enable/disable functionality per user.
  2. a repo owner cofigure bot to have the bot comment on every single new issue, soliciting funded issues.
  3. every time an issue is funded from that repo, the comment is updated with current funding amounts.
  4. ability to fund an issue straight away through the bot, just to a github user
@owocki owocki changed the title Bot Revamp Bot / Github integration Revamp Oct 19, 2017
@frozeman
Copy link

frozeman commented Oct 20, 2017

Ok so here are my thoughts on how this should work:

Repo owners perspective:

  1. You add the gitcoin bot to your repo, like travis.
  2. Ideally he does a simple GitHub connect, and gitcoin just creates an ID for a GitHub username. He then should be able to set the donation gitcoin gets per issuer tip jar resolution (default 0.5%?)
  3. This will now automatically create - as first comment on every new issue - a message telling people to send money to address x to "fund" this issue.
  4. If an issue is funded and somebody resolves it, he has to add an address and the issuer number to the PR, e.g. "fixes Pytest version conflict with ethereum package #123 payout to 0x123456543212345678.." (address here should allow uppercase, checksum and normal, but not incorrect addresses)
  5. If the issue is resolved and no address or message was put in the description. Then either this money goes to the repo owner, or back to the funders. (Maybe its an option in the bitcoin settings)

Contributor perspective:

  1. He goes to gitcoin and looks for lucrative issue he is able to solve.
  2. fixes it and puts in the PR description "fixes Pytest version conflict with ethereum package #123 payout to 0x123456543212345678.." on the top. Then a gitcoin comment appears as first comment, saying he connects this PR to issue X and will payout to Y. Maybe the repo owner can click some button in this issuer to cancel or something.
  3. His PR gets merged, fixes Pytest version conflict with ethereum package #123 and the money goes to his address

Repo user perspective

  1. User has created an issue for a fix or a feature, and desperately needs it
  2. The gitcoin comment appears and shows him an address, which gitcoin is watching.
  3. He sends money to this address, gitcoin then uses this address to create a tip jar smart contract, which has some rights (maybe repo owner can refund people, and ideally only payout when oracle says the related PR is merged)
  4. The issue comment is now updated with the new address of the tip jar contract, plus shows the amount in realtime. (If people should still send money to the creation address, it will be forwarded to the tip jar contract)
  5. Other people will fund this issue useful, and contribute more funds until somebody is willing enough to fix it.

@gitcoinbot
Copy link
Member

This issue now has a funding of 1.15 ETH (354.25 USDT) attached to it. To view or claim this funding, click here.

@PixelantDesign
Copy link
Contributor

Closing since we've done this!

owocki pushed a commit that referenced this issue Oct 10, 2018
vporton pushed a commit to vporton/gitcoin-web that referenced this issue Jun 27, 2020
…kens

[WIP] Buy and Redeem pTokens on profile

Merging to get the workflow in place and will re-open a PR for the web3 stuff
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants