All 3 of these projects are lacking things that we each have.
The server part of the libbitcoin stack is well developed, but we're still working towards client-side software for managing wallets. I was very impressed by Thomas' presentation about how he's turning Electrum into a framework. However the backend for Electrum is lacking, and also the servers are unreliable. We have built the client side libraries (Pablo's pure Python ZeroMQ
+ Pablo's obelisk-client
+ Vitalik's Pybtctools
+ Robert's BlockAlchemy
). This removes any need for dependencies (pure Python) and can easily be deployed on Android (through Kivy).
I'm imagine a core on the desktop with an API over sockets that can only be called on localhost (although maybe do something else). Exchange the Electrum interface and start using the new library (move Electrum code over to it too, and provide a nice API).
Hive is even further in front of the user. The Electrum user interfaces suck (despite the technology being very good). And they're really thinking on different things. If we have a separate Python core with a socket, then it's possible to integrate with their C#. They already have their server backend and Electrum has one too, and so no point us all duplicating the same work when I've been doing backend/impl stuff for ages.
libbitcoin - server / core API stuff
* libbitcoin/obelisk server - me, Robert Williamson
* Client side library: Pablo, Vitalik and Robert.
** ZMQ (networking library) Python port by Pablo.
** Daemons like broadcaster or mixer written in Python for rapid development. This is one of Pablo's specialities.
Electrum - features, key management
* ThomasV, Animazing
* wallet, interface API - ThomasV
Hive - interfaces
* Wendell, Taylor Gerring
We can search for some designers, and we can provide infrastructure like servers and stuff. And contribute towards paying for packaging, Q&A, testing, ...
For the network stuff, I have help from Hintjens. He wants to make Pablo's Python an official port of ZeroMQ. The origin for ZeroMQ is from when he was working on networked financial software.