The idea is to migrate the hosted un-supported version into the cloud. There are some issues which must be considered when we upgrade (please complete the list):
The web page uses the old Jive SBS API (documentation no longer available) to fetch community information. It has to be ported to the Jive v3 REST API. This seems to be easy.
Where are the JSP pages?
The Tomcat version may be out-dated, it should be moved to Tomcat 7.
Community / Spam filter
We use currently a custom plugin, for Jive7 there is a Jive plugin with similar functionality. The spam features are available in Jive’s cloud release - we need to test it. See https://community.jivesoftware.com/groups/external-community-managers/blog/2013/ 04/18/spam-happens-learn-to-live-with-it
Maybe we use http://community.igniterealtime.org as a unique URL only for the community - so there is no reverse-proxy in front of it and we split up the design and UI of “www.” and “community.”. The look and feel should be kept, but it may not look like a 100% integration. From the marketing pov this would be a disaster, but I think one can live with it.
For me the most critical part - the 4.x version seems to be much faster than the 6.x or 7.x versions.
I hope there is a way to get it fast, without too much external files.