This idea was developed in chat box some 30min ago. However it evolved in my mind in mean time and it is quite different in this moment while I write this. I polished it quite a lot. Stay with me!
This is analog to Marketing fund, but it takes care of development/technical side of this coin.
Goal is to map the all the steps needed to get us all the sweet technicalities and present them in clean and cool way.
With this, it could be very clear for one developer to see how he/she/it can help development of Peercoin and what are end goals.
This can also be used to draw new investors, or to milk out whales among us.
Since all goals will be clearly presented, including all the tiny steps to reach them, investor can “adopt” development of some tiny program/library which is dependency of something bigger. This can be done with integration with Peer4commit.
I think this is how we draw developers too, since this could become bottomless hole in which we (the community) can dump our wishes and ideas. Then they become part of the tree and with it new challenge and job opportunity.
This is getting confusing so I made this sketch to show you:
This is inspired by 4X strategy games like Civilization/Freeciv, where player has “tech tree” where he decides where to invest according to his goals (http://en.wikipedia.org/wiki/Technology_tree).
Here you can see, to reach “Awesome web wallet” we need to “research” libraries for programming languages used for web development.
It is not important which one of those libraries is developed since each and every one increases a chance of “Awesome webwallet” to be developed.
This is pure logic, more libraries (tools) you provide there is more chance that someone who knows that tool to came along and make us web wallet.
There is added benefit with each and every library we invest in total infrastructure of the coin. Thus, helping future development and providing more options for possibly interested developers.
Other benefits are that we can have centralized mind map for all project we plan to do. Like OT, right now we know we need websockets interface with ppcoind. Now, this can be mapped and seen by everyone.
Use cases:
(this is generalizing, for example)
[Standard PPC fanboy] - Reads about OpenTransactions, wants this to be implemented with Peercoin.
He now submits this feature request to this system, with as much info he can gather. Request is passed to more tech savvy Fazon admin who researches it into more detail then maps to Fazon.
[Developer] - Looking for work
He/she drinks coffee on rainy Sunday morning. Check’s out Fazon for latest challenges.
Sees there is this thing called OT, and since it is interesting she/he looks into it and notices that Fazon admin missed dependency on “websockets”. So, developer notifies admin to map it.
Since developer sees this and interesting project, he proposes price of 500 PPC to develop wrapper for websockets.
This automatically creates new Peer4commit project and notifies admin that someone took the job.
[Investor] - PPC is dropping like a rock and he/she knows that a little push into infrastructure could be move in right direction
Investor comes to Fazon site and sees that there is a quest to reach integration with OT. Reads about OT and sees that first step is to develop this thing called “websockets”. And that someone offered to do this job for 500 PPC.
Investor concludes this is good deal and pays for it.
Funds are transferred to dedicated Peer4commit repository but still locked to admin of Fazon, not available to developer unless he is trusted person with reputation in community. In essence, developer is now employed by PPC community.
In the end everyone is happy, fanboy got his feature, developer got some extra money and investor helped to create new hype around PPC increasing price of his stake on PPC network. What is best of all, community prospers since this is usable for all of us.
[center]##################################################[/center]
I expect comments and suggestions since this is good idea and something can be done with this.
Also, project can be name “PeerTree” but is not cool as “Fazon”.