I suggest you consider this approach (as an extension to @raff’s comment):
- build a completely new application from scratch (using a very-popular-today JS framework)
- this is a very thin layer on top of bintray
- no data storage at all for the OWAs, outsource this completely to bintray
- this indexes the OWAs on bintray, and presents a few valuable summaries in an openmrs.org-themed UI
- eventually this should support indexing OWAs across different organizations, e.g. OpenMRS, Bahmni, PIH, Sunbiz, etc.
- show things like most-downloaded, top-rated, most-recently-updated, etc
- could have a data store for features like “OWA of the month” or “included in Reference Application”
- all non-trivial functionality (e.g. giving a rating, downloading an old version) is just a link to bintray
- The scope of this GSoC project is just to build our “OWA App Store” but be aware that this should eventually replace Modulus for our OMOD files also.