I am working on an article for developers interested in collecting the bounty. The article would discuss the areas of importance you would expect to see in a winning wallet open source project. I’ve put some of the links I thought would be useful in the #wallet-bounty Slack channel. However, I did receive feedback from one very enthusiastic developer, who I feel is already cashing the check, that has given me the reason to ask the following questions:
How developed do you expect submissions to reach? (i.e. alpha, beta, etc.) Should teams have a development timeline for adding mobile? I realize the size of the dev team and their marketing reach have an effect on this, correct?
If you have two similar wallets would you focus more on user adaptation numbers vs. “working” features? Are you looking for quantity or quality end-users?
Would you give high marks to a project with Mockups or other ways for your team to provide feedback? Not to say you would have the time, however, at some point when you have to judge, will you be leaving feedback in the form of issues on the Github?
Again, I know the team is really busy getting things ramped up for this next evolution of blockstack. However, with the scarcity of Senior blockchain developers in the space, the more useful information I can provide new developers - like the ones in Free Code Camp, the better it will be for the entire blockstack space. Free Code Camp portfolio piece is usually with a non-profit. However, why couldn’t it become open-source bounties or contributing to projects?
Free Code Campers could come together and create an employee-owned company. Stranger things have happened.
But mostly in this day and age of non-technical users looking to enter the space, I feel like the more user-friendly the discussion of this bounty is to new devs, to better traction your project will have over the competition. Not to mention, I want to see more teams than just the aforementioned one. Don’t you?
I look forward to your thoughts @xan