claytantor / gitpatron

the gitpatron project

gitpatron

Visit gitpatron!

##gitpatron Monetizes GitHub with coinbase. Quick and easy donations for open source projects. Using gitpatron is like puting a donation box on your open source projects, except the donationas can be targeted to specific issues that patrons would like to see fixed. GitHub is the best place to share code with friends. Coinbase is an international digital wallet that allows you to securely buy, use, and accept bitcoin currency. When you put them together you get an easy and safe way to support your favorite open source projects.

##How does gitpatron work? By letting bitcoin move with the development process. The flow of bit coin comes starts from the patron. If a patron wants to donate to a specific issue they would like fixed it is sent to the repo owners wallet. Committers identify which issues they would like to fix, and how much the minimum they should be paid for the fix. Once the fix is made and proof is provided via a github commit id; the repo owner chooses to pay for the full amount that all the patrons have donated. Every contribution and payout is visible to all parties in the process.

##Is gitpatron safe? Sunshine is the best disinfectant. Our project is 100% open source that means its safe because we allow our community to critique and improve our security procedures. All commerce is managed via the coinbase API, and we use delegated authority to github using the Oauth2 API an accepted standard for safe user authorization.

##How much money does gitpatron make on a donation? We haven't figured that out yet... Money is oxygen for projects. Thats why gitpatron exists. One day we would like to make money, we just havent figured out how to do that in a way that everybody thinks is fair. We will probably spend some time as this gets more mature experimenting with ways to monetize that work for the community. For now just use it to help your project succeed, that's pretty rewarding to us. If we we ever make it too expensive tell us.

##For Patrons Be a patron. And help open source projects thrive. Github projects need your help. When you support project issues you have a voice in what gets fixed first, and developers are rewarded for their contributions. You only need a bitcoin wallet to contribute to any gitpatron project.

##For Repo Owners Repo Owners. Engage your loyal patrons and give them a voice. What if your project fans could ask you directly for what they wanted simply by donating? Having a conversation with your patrons about your development road map, and giving them an opportunity to engage directly is like having a compass on the way to your project's success.

##For Committers Committers. Get paid for contributing to the projects you love. You are a skilled developer with a love for helping open source succeed. You can name your own price for fixes that further the project.

gitpatron's Issues

Gitpatron "login with Github" is asking for a lot of info+access right now.

It wants rights to read/write all public and private repos... why is that necessary? I'd be interested to check out Gitpatron but would be pretty reluctant to OK that request.

Only monetize open issues.

When the sync implementation with github does the api call it gets both open and closed issue. The sync should bring the issues in but it should set them to fixed so they cant be monetized and workflow starts.

D3 Charting for Patronage and Fixes

Use d3 to create charting over time for both patronage and fixes at the repo level. Take all the order events and create a time series of donations over all time.

So a basic selection for the charting lib built on D3 has been chosen. The developer need to use the following library for the implementation:

http://c3js.org/

This library is built on top of D3, both of these are now included in the header.html include.

Auto merge a pull request on payment

When a repo owner pays for a fix and if the merge is automatic then the merge should be done automatically via API.

https://developer.github.com/v3/pulls/#merge-a-pull-request-merge-button

Committer allowed to monetize without wallet

A committer can attempt (and fail) to monetize a fix even though they have not activated their wallet yet.

make auto callback url for buttons

https://coinbase.com/docs/merchant_tools/payment_buttons

https://coinbase.com/api/doc/1.0/buttons/create.html

button[callback_url]
optional
A custom callback URL specific to this button. It will receive the same information that would otherwise be sent to your Instant Payment Notification URL. If you have an Instant Payment Notification URL set on your account, this will be called instead — they will not both be called.

Value: Must be String

Watch a Repo

Allow no owners to watch an issue. Put updates to the feed in the users home if new issues , fixes or whatever happens. Put a link to the watched repos in the "watched tab"

Monetize Issue Visible

The monetize issue button should not be available or shown if a repo owner has not activated their coinbased account

Use gitpatron_repo.md for Repo description.

When a repo owner publishes a repo, if a gitpatron_repo.md exists it should take the content of that file and use it for the repo markdown. This file should always be updated with "sync issues"

Create activity feed: Callbacks, Orders, Patronage, Fixes

Create an activity feed that takes all the Callbacks, Orders, Patronage, Fixes and makes a feed that can be used to take action. Each feed item should have one, simple action associated.

BTC USD Conversion

https://coinbase.com/api/doc/1.0/currencies/exchange_rates.html

Refresh tokens for coinbase

Tokens are expiring forcing the user to disable the entire coinbase application and start over to get the new token. What should happen is the refresh token should be used to update the auth token required for the button to be generated.

Limit scope to button creation

The Oauth2 API doens't really need to be authorized to do "everything" limit the scope to only creating buttons.

https://coinbase.com/docs/api/permissions

Enable committers

There needs to be a way for a potential committer to say they are claiming to work on a ticket. There should also be a simple way for them to notify that the work is done and is ready for review. When the pull request is accepted they should automatically get paid for the fix.

Auto close on payment

After an auto merge has occurred and payment has been made the associated issue to teh pull request should be closed automatically.

https://developer.github.com/v3/issues/#edit-an-issue

All important fields transformed to published repo.

Many of the important fields that could make the integration more helpful are missing. Examples:

avatar_url
gravatar id
etc.

Command To Process Callbacks

Create a command that will process callbacks. This is a first step to handling callbacks but will allow us to create fake callbacks in the DB and process those in dev. (Order callbacks dont work to localhost)

Beta Support

There needs to be a way to restrict the users allowed to have access to the sight. Create a list of users that is checked prior to login. This list would be from the mailing list.

Committer workflow

There needs to be a workflow where committers can:

• Claim issues
• Monetized Issues with a commit id

also the repo owner should be able to:

• Pay committers
• Set items to fixed closed.

publish github repos

the ability to publish github repos somehow got broken, add the ability to see the list of available github repos and publish them as available for funding.

Invalid data-code attribute for fix buttons

The fix buttons are not getting created correctly. An incorrect code is being set making the button not work.

Support for Auto Repo Hooks

What would be really cool is if a repo is created it could automatically make a hook to update so sync would not be required. Dont know if this will be required for ALPHA though.

https://developer.github.com/v3/repos/hooks/