OpenEMR and github

OpenEMR Development
1

bradymiller wrote on Wednesday, August 24, 2016:

Hi,

OpenEMR’s codebase is on sourceforge and mirrored to github which allows developers to use the github tools such as pull requests which are heavily used now. The current OpenEMR account on github is a individual user account. Would it make sense to change it to a organization account. Then other developers besides myself would be able to close pull requests for example. And could also use other project tools there, such as issues.

thoughts?

-brady
OpenEMR

2

sunsetsystems wrote on Wednesday, August 24, 2016:

Sounds reasonable. Free for open source, right? Are there any gotchas or disadvantages?

Rod
http://www.sunsetsystems.com/

3

robertdown wrote on Wednesday, August 24, 2016:

Think it’d be a good idea. I’m not aware of any issues changing to an organization.

4

mdsupport wrote on Wednesday, August 24, 2016:

Seems to have no show-stoppers but everyone should review their disclaimers :

  1. What’s the difference between user and organization accounts?
  2. Converting a user into an organization
5

bradymiller wrote on Sunday, August 28, 2016:

Hi,

I just converted the github account into an organization, which worked out very well. I also transferred the website repo into the organization:

-brady
OpenEMR

6

wakie87 wrote on Tuesday, August 30, 2016:

Hi,

With the transition of github to an organisation, (Yes us Australians spell it with an ‘S’) should we look at moving over the bugs from SF to Github?

We already do most of the code reviews on there.

Maybe we should look at making Github our primary repository and SF our secondry?

Scott

7

bradymiller wrote on Wednesday, August 31, 2016:

Hi,

The official OpenEMR codebase repository is now on github. This will make it much easier for the Integration Developers (myself, Rod, and Scott), but won’t really impact anybody else; since almost everybody is using pull requests on github for code submissions anyways (note it is still not required to use the pull requests).

We can also start using the Issues feature on github (for tracking bugs etc.), which does seem to be much more intuitive than sourceforge’s tracker:

-brady
OpenEMR

8

sunsetsystems wrote on Wednesday, August 31, 2016:

Thanks Brady! I see you updated the Git for Dummies guide accordingly. I had a couple of questions/suggestions about that which I put in the Discussion tab there.

Rod
http://www.sunsetsystems.com/

9

bradymiller wrote on Saturday, September 10, 2016:

Hi,

We are going to start migrating tracker over to github on Issues · openemr/openemr · GitHub

To this end, I have begun inviting folks to be members on the github openemr organization (need to be a member to be assigned items etc.).

If I missed you, just let me know and I’ll send you an invitation.

thanks,
-brady
OpenEMR