Ethereum-CommitETH Alpha — Development update April 2017
Since the initial alpha release we’ve had 139 people sign up and test out what we’ve built so far! Thank you to everyone for the wonderful feedback and suggestions we’ve received.
In this post we’ll outline a few of the updates that have been made since then — focusing mainly on the most commonly requested feature: progressive permissions.
At the time of launch, when a user signed in using their Github account, CommitETH asked for admin permissions to get access to the users repositories, this was required so the tool could create the bounties on the repositories, but even users who were only there for bounty hunting had this requirement imposed on them. Another issue was that the OAuth tokens were stored on the CommitETH server. Respecting user’s privacy is important to us, so we’ve since implemented a solution.
New Progressive Permissioning
- When a user signs up for CommitETH, they will only be asked to provide their email address access for identifying the user so they can claim bounties.
- If a user wants to set bounties on repositories they will be asked to enable permissions for CommitETH to access the repositories.
a user has enabled the permissions to the repositories, there is an
additional step where the user can choose which repositories to add to
the bounty system. Also forked repositories will be available to those
who want to add bounties to their forked repos instead of the originals.
All repositories can be identified and the forked ones differentiated
from the originals with the use of
username/repositoryscheme to prevent fraudulent use of bounties.
- All Github access tokens will now be stored on the user-side using the
localStorageof the user’s browser.
It’s still early days for this tool, but with these changes we’re making steady progress, and hope CommitETH will become more attractive to those who wish to enable a community driven development model for their repositories, and reward those who wish to get paid for their contributions to the open source projects.
Here’s a list of what has been happening in the CommitETH development, lead by Teemu:
Progressive Github permissioning & client-side oauth tokens by tpatja · Pull Request #46 · status…
require only user:email oauth scope when signing up if user wants to set bounties on repos, request additional oauth…github.com:https://github.com/status-im/c...
Use ropsten revival chain · Issue #48 · status-im/commiteth
User Story As a user, I expect Commit ETH to use the Ropsten revival chain. Description We indicate Testnet usage on…github.com:https://github.com/status-im/c...
- Filter for forks on Repositories view #47
- Update comment image for signed off bounty #36
- Update comment when pull request merged #44
- Show organization thumbnail and repository name for bounty-added and bounty-balance-updated activity feed items #41
- Cache invalidation for app.js #24
CommitETH + Status
In the context of Status, once CommitETH is further along we plan to begin allocating a portion of our development budget towards bounties on open issues.
Why? One observation we’ve had through our hiring process, is there exists a large pool of very talented developers who already have full-time positions, and are actively contributing to open source projects for a few hours each week during their free time. We believe by providing a strong monetary incentive for PR’s, we can then utilise this workforce while keeping our overhead low, while also providing developers with an avenue to explore open source, demonstrate their skills based purely on merit, and lead to full-time positions should they wish.
Try it Out
We want to invite everyone to join testing the alpha of CommitETH, contribute to the development, and come chat with us at the Status Slack, where we have a dedicated #commiteth channel. CommitETH also has its own Twitter: https://twitter.com/CommitEth
A Mobile OS, built for Ethereum.