For me to consider building a transport for a new protocol, I generally need the following things:

1. An API, written entirely in Java (no JNI!), that is free, ideally open source.  Please provide a URL.  If you are aware of multiple APIs, please let me know about all of them and I'll evaluate them.

2. A way of understanding what needs to happen (in other words, either English support, or someone to walk me through the steps of various procedures, like getting an account, downloading a 'real client', that sort of thing)

3. A server/service to test against (either an established service like AIM, or some free server I can download, install, and test against, or a server hosted by the requestor or interested company that's willing to give me a test account)

-or-

1. Someone else writes the code and submits it to the project.  Contributor agreement with Jive must be signed.

2. Ability to test it against some server or service.  See above.

There are some instances in which there's an API and it's not good.  The official Skype API, for example, requires that you have a copy of the desktop client installed locally and also, per my understanding, only allows one person to log in at any time.  I generally require platform independent functionality, so this violates the ability to run a Skype transport based off this API on anything that there isn't an official Skype binary for.