I’d like us to consider the best way to distribute OpenMRS Open Web Apps and bundle them easily with the Reference Application. I see it as a chance to reconsider how we currently distribute openmrs platform and modules.
Currently we use the OpenMRS maven repository to publish omods. This repo is used for fetching dependencies when building modules, but also for creating a bundle of modules for the Reference Application distribution. In addition to that we use modules.openmrs.org to distribute omods for end users. Furthermore we publish the bundle of modules (the Reference Application) to sourceforge. That’s a lot of different distribution channels already.
Now we need to distribute yet another package that is OpenMRS Open Web App, which is basically a zip.
In the current setup we rely mostly on our infrastructure to distribute releases. We have our own maven repository and modules repository. It feels too much for our community to maintain. I think we should be putting efforts in creating better platform and modules and not distribution tools.
To give an example that we are not doing good at maintaining distribution tools is that a simple bug of sorting versions of modules is broken on modules.openmrs.org since the beginning of the repo, which at times leads to not showing the latest version correctly. Since we are using our own solution we still haven’t been able to implement a REST interface to publish to modules.openmrs.org directly from maven or CI.
At the same time there are tools out there, which already have all we need and are free for open source projects. A good example is https://bintray.com/ Also there’s no reason to maintain our own maven repo when most projects simply publish to maven central (bintray integrates with that too). Even sourceforge is easier to publish than modules.openmrs.org.
Writing this I’ve realised we have a GSoC project to build a repo for OWA, but please let us reconsider using something already available in the market rather than investing more in our own solutions.