@suthagar23 Thanks for the great suggestion!
The advantages of having such a tag are many as mentioned by you. Having said that, here is my qualm regarding the same:
-
Every module developer would like to get their module OpenMRS verified. To ensure the quality of the modules tested, we will have to test every aspect of the module from the quality of the code to its conformity with the OpenMRS standards. This, in my opinion, would be a slow process and we would probably need to have a few devs who will be looking into this.
-
Module verification is a continuous process i.e. suppose we have a module A whose v1.0 runs well with Ref App 2.6. The suppose, Ref App 2.8 is released and the development of Module A has stopped and no longer works with this new release. The right thing to do in such a case would be to remove the OpenMRS verified tag. However, we currently have about 300 modules on AddOns and this list is growing each day. Won’t it be extremely tedious to keep a track of what happens to each module individually?
Having said that, my solution to the abovementioned would be to either:
-
Only add such a tag or a (Ref app module) tag to the ones released as part of a particular ref app release.
or
-
We can possibly follow the approach taken by the popular app stores and review the modules with the highest number of downloads each quarter/month.
If you have any further solutions/points to the points mentioned above, do let me know 