We initially created dev stages to encourage engagement in the community. Later on, devs decided that dev stages should reflect a developer’s technical OpenMRS knowledge/skills independent of community engagement. Rather than simply removing the community engagement aspects of dev skills, I moved them into a draft “ones stages” that we could revisit if we wanted a metric of community engagement again. I don’t see them as a hierarchy; rather, I see them as complementary. dev stages reflect technical skills and omrs stages reflect engagement in the community (and, obviously, doesn’t depend on someone being a developer). A /dev/2 + /omrs/5 would be a leader in the community with modest technical skills; a /dev/5 + /omrs/null would be someone who could do anything with OpenMRS technically but not involved in the community.
Given that community engagement was the initial purpose of dev stages, I’d love to see omrs stages realized. Plus, it would give targets for non-devs to achieve.