Adding OpenMRS license to modules

Hi, I had a recent interview (for research purposes) with Akhil Ravindran and he was very open to keep the radiology-dcm4chee as open licensed as possible. We have a GCI issue - and here the students are writing the MPLv2+disclaimer to modules

Now, I wonder if the module authors donated the code to be included in OpenMRS github org. Does that mean the license can be changed with the author permission? Are all the modules listed under openmrs org in github mean, they are owned by OpenMRS as well?

We have yet to formalize this, but my bias is that should be focused on community-supported and community-owned repositories and not hosting all community repositories.[1] The assumption that any work that is OpenMRS-related should be under the OpenMRS org in GitHub is not scalable. For example, GSoC repos should move under the organization only when/if they become community-supported or community-owned. There’s nothing wrong with using a repository under a community member’s account as the “official” repository.

Community-supported & community-owned repositories should be under OpenMRS license (OPL 1 or MPL2+HD) in most cases, perhaps with a few using some other OSI-approved license when there’s a reason to do so. In all cases, they should be copyrighted to OpenMRS so that there are no issues/concerns about what the community can do with the code or its licensing/copyright going forward.


This should likely first be reconciled with the (Draft) Copyright & Contribution Policies.

1 Like