Ahoy!

I don't recall seeing a link to a demo of your back end configurability system - is there one available?

The comments made by both @starkerz and I about the scope clash between this project and Ecency / Breakaway Communities are based on both projects seeking to fill a gap between Hive and requirements for customised Hive installations. Both projects result in a customisable front (and back) end, plus open source editability. However, Ecency is already funded to expand on this and their feature set is pretty large in comparison. So I'm still not seeing why you don't see an issue with funding two projects that are aiming at the same target and where the one that is already funded is way, way ahead already.

As Matt already pointed out, it makes sense for people who want to achieve this goal for Hive to join forces with Ecency and to make that code the best it can be. My own view on what I've seen of deployment of the previous versions of their breakaway communities is that it can be extremely powerful but is really lacking great customisation of the back end - which is now what you are selling your poject as.. So, to me, the clash is made doubly relevant by viewing your project in this way.

I do understand that Ecency's funding is theirs and isn't automatically going to go to you - so I don't have a straightforward solution - other than that it would be good if @good-karma would comment on this (if he hasn't already and I have missed it) and if we can somehow rejig this situation so that everyone gets what they need and progress for Hive is expanded.