Transfer of DIT Module Github Repo to OpenMRS

Development Repo Management
1

I am about to release the Data Import Tool module to the OpenMRS community. Here are the details:

Github userName: Ch3ck

Github Repo: https://github.com/Ch3ck/openmrs-module-dataimporttool

Description: The Data Import Tool eases data migration for production settings by improving upon an existing data migration tool to make it more user friendly. The Data Import Tool integrates the eSaude Data Migration Tool (eSaudeDMT) it in order to migrate data from SQL-based data source into OpenMRS. This module provides a WUI to configure migration settings that are currently being performed using an XML file (config.xml), and a Start Migration(command) button to ignite the execution.

This project was developed as part of the Google Summer of Code program to enable data migration between OpenMRS and other Software.

2

Sounds good to me.

1 Like
3

The Repo respects the OpenMRS naming conventions and carries the OpenMRS License. I think it’s ready for transfer.

4

I don’t see a LICENSE.md file in the root of the repository, but it does look like at least some .java files have the header for the deprecated OpenMRS Public License. Is there any particular reason why that was chosen over the current Mozilla Public License 2.0 with Healthcare Disclaimer (MPL 2.0 HD)?

1 Like
5

@michael, I’ll update the Licence for the files and create a .Licence.md file. I’ll take a look at other examples and make the necessary changes.

1 Like
6

Hello, @michael

I have updated the Licence for the source files and successfully added the .LICENCE.md file. Is there anything else?

Cheers!

7

Hello @burke @darius @ryan ,

I have updated the Licence for the module and based on @michael 's recommendations. I’ll like to know how to transfer the Repo ownership to OpenMRS. My mentors are Ok with it.

Cheers! Nyah

8

It seems like everyone has forgotten this post? :burke:

9

@ch3ck, GitHub permission changes has broken our typical approach for migrating repos. @ryan has a workaround.

10

There is a workaround but there’s not yet an approval from the engineering team for the request of ownership transfer to OpenMRS Inc. :wink:

11

@michael

Are there any issues the repo might have I’m not aware of. I have respected the naming conventions and updated the licence as you requested. If there are any issues with the engineering team. I’ll be glad to fix them ASAP.

Cheers! Nyah

12

While we could continue to nitpick (e.g., using LICENSE in plain text like openmrs-core, adding .git-ignore & .git-attributes lke openmrs-core, etc.), it’s not really fair given that many of our modules (already under OpenMRS.org) have similar problems.

We can go ahead and move this under the OpenMRS org.

I would recommend getting rid of .LICENSE.md, copying LICENSE + .gitignore + .gitattributes from openmrs-core, and removing the target folders (derived folders/files shouldn’t be committed to github). But none of these need to prevent migrating the repo.

3 Likes
13

As our brand new dev tools manager, @maany will be responsible for the execution of these moves going forward (not the approval process, but making sure they happen). He is currently traveling today but once he’s on the ground, we’ll make sure that he gets up to speed on the current GitHub issues and gets the transfer completed.

2 Likes
14

Hello,

I have made the necessary changes you recommended and pushed the changes to GitHub.

Thanks,

2 Likes
15

@ryan @maany Can one of you help us transfer this repo?

Thanks!

1 Like
16

Hi @pascal and @ch3ck I was at a hackathon in the US. I’m back today and will transfer the repo now. :slight_smile:

2 Likes
17

Thanks @maany Is there anyway I can assist in this? :grinning:

Cheers!

1 Like
18

Thanks for the assistance @ryan and @ch3ck Here is the transferred repo : https://github.com/openmrs/openmrs-module-dataimporttool Good luck for the release guys :smiley:

3 Likes