I definitely agree that using hosted bintray instead of running our own modulus server application makes sense in the long run. But I don’t think a pure refactoring of modulus-ui to use a different back end is worth the effort of code rewrite + data migration.
Doing this in the context of adding new functionality would make more sense. E.g. it makes sense to do this in the GSoC OWA store project.
On the related thread I suggested we should in fact also rewrite the UI from scratch: OWA App Store GSoC project
How much functionality does modulus-ui have that we want to maintain versus how much would we get rid of with a bintray back end? (This is an honest question, not a rhetorical one.)
My initial thought is that what we’d want in our module/OWA store in a hosted-on-bintray world is quite different from the current functionality, which is why I suggest a rewrite of an essentially different application, that is mainly about indexing things hosted elsewhere.
-Darius (by phone)