Adding OpenMRS license to modules

We have yet to formalize this, but my bias is that http://github.com/openmrs/ 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.

2 Likes