TLDR; Let's do all Mobile.next()/5.x development as the Aerogear community
I would see the FeedHenry community being strongly linked to RHMAP (Red Hat Mobile App Platform). There are large parts of that community that are tied into having access to a an RHMAP cluster e.g. SDKs & templates (There are some exceptions, which I'll call out later). The RHMAP MBaaS is available on github, but it is not very useful without an RHMAP Core. The RHMAP Core is only available via a RH subscription.
I would NOT see the Aerogear community as being strongly tied to RHMAP. The 2 main Aerogear projects are Unified Push Server & Digger (Build Farm). Both of these are standalone services that have been developed in an open manner from their inception.
See Ger's points for more about what the Aerogear community is doing well.
Building the Aerogear community as the upstream for mobile in Red Hat would draw a line between what's RHMAP 3.x/4.x and the future (5.x).
Steps from here:
* move the fh-sync-server project into the Aerogear community as the 'Aerogear Data Sync Service'
* move mobile.next()/5.x collateral (that's still relevant after the POC) to the Aerogear community
* progress development of mobile.next()/5.x as the Aerogear community
** update UPS documentation (it reference OpenShift 2! There's been great work done on updating UPS for decoupling keycloak & running on OpenShift 3 via APB)
** add Aerogear Data Sync Service documentation
** add Aerogear Digger/Build Farm documentation
** add Aerogear mobile.next() (name TBD) documentation
I'm sure there's things I've missed, and would welcome other peoples thoughts on this idea.