Hi, thanks for the more detailed insight into your proposal here.
Frontend: Are you aware that Ecency has already put significant resources into the Breakaway community system - in association with SPK - that effectively enables anyone to run their own custom and open source version of Ecency?
Maybe you can explain why Frontend is needed in light of the funding for Ecency's breakaway project?
Invoicing: In the same vein, are you aware that there are already multiple systems that deliver invoicing on Hive? There's keychain Store for mobile (funded via keychain DHF) and also Hive Debit the upcoming debit card system. Plus also V4V.
So is there a need for another system that does similar?
I think one of the biggest annoyances I have with the development on Hive is that there is so much duplication. I can't think of any important feature that doesn't have at least 2 teams working on it in competition with each other - sometimes with both teams being funded. I appreciate that some people think that competition is good, but I think any benefit like that is lost when both are being funded regardless of success - since there is no commercial aspect.
I think you should probably rethink the problems you are aiming to solve.
It seems like the biggest problem from a development standpoint is the total lack of standardisation. This has led to a situation where almost all developers think that the code provided by other developers isn't worth using or high enough quality. If you could specify a coding standard system and modularisation/plugin system for Hive (not a simple task) then that would be the ultimate win from my POV. An example of what I'm talking about is the plugin system used in the Elgg open source social networking framework.
Cheers