Where is most of the OpenMRS-related development activity over the past week? Should we be reaching out to a highly active volunteer who recently went silent? What is our average response time for a pull request on a community priority ticket? Are we improving? Did someone manage to simultaneously resolve the most voted tickets and get the most like posts on Talk last month? How many…
These and many more questions could be answered with existing data if we had the tools to explore them. Tools like GrimoireLab can be used to create a community dashboard through which insights can be gained and better (more informed) decisions can be made. For example, here is dashboard created for OPNFV by Bitergia.
Benefits to the OpenMRS Community
By pulling together activity in GitHub, JIRA, Talk, Wiki, CI, IRC, etc., the OpenMRS community could increase transparency, be better informed about community activities, and do a better job recognizing community contributions.
As a side effect, we could also have realtime stats to drive our website and provide data for annual reports.
The biggest risks would be:
- The dashboard setup is complicated/fragile (too difficult to maintain/upgrade/modify)
- We aren’t able to come up with actionable questions to drive metrics
- Available data don’t provide meaningful/actionable insights
High level project plan
We would hire a group like Bitergia with expertise to do the initial setup and initial iteration. The goal would be to have a community-hosted dashboard that could be sustained and adapted by the community.
- As a community, decide on our top ten metrics of value [1-2 weeks]
- Set up a GrimoireLab dashboard to answer those questions [2 months]
- Review dashboard and decide on key changes & improvements
- Second iteration [1 month]
- Document & hand off to infrastructure team and community developers [1 month]
USD $20-50k, depending on how fancy we get
Availability of other resources / matching funds
As on open source project, we may be able to get a reduced rate.