Difference between revisions of "New Developer Information"

From OpenEMR Project Wiki
 
(32 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Welcome and thank you for your interest in the OpenEMR system.  The OpenEMR community is very open and we welcome contributions of code and ideas. We ask that the code be released under the General Gnu Public License to keep the licensing consistent.
Welcome and thank you for your interest in the OpenEMR system.  The OpenEMR community is very open and we welcome contributions of code and ideas.  


Here is some basic information for new developers to get up and running quickly:
* Contributed code should be released under the General GNU Public Licence (GNU GPL 3)
* To get started, feel free to introduce yourself at the [https://community.open-emr.org developer forum] or email the administrators, Rod Roark (rod at sunsetsystems dot com), Brady Miller (brady.g.miller@gmail.com), Robert Down (robertdown@live.com), Jerry Padgett (sjpadgett@gmail.com), Stephen Waite (stephen.waite@cmsvt.com) or Stephen Nielson (snielson@discoverandchange.com).
* Here is an overview of the [[OpenEMR System Architecture|OpenEMR system architecture]].
* Here is an overview of the [[OpenEMR System Architecture|OpenEMR system architecture]].
* Here is an overview of the [[Development Policies|OpenEMR coding policies]] aka [[Development Policies|Coding Standards]].
* Here is an overview of the [[Development Policies|OpenEMR coding policies]] aka [[Development Policies|Coding Standards]].
* To get started, feel free to introduce yourself at our developer forum on sourceforge [http://sourceforge.net/projects/openemr/forums HERE] or email the administrators, Rod Roark (rod at sunsetsystems dot com) and Brady Miller (brady@sparmy.com).  Tony McCormick is the volunteer coordinator and can be reached at (tony@mi-squared.com).
* Here is an overview of [[How to Document Your Code Properly]]
* Code patches for review can be submitted in the sourceforge tracker [http://sourceforge.net/tracker/?group_id=60081&atid=1245239 HERE]. We usually can test and give feedback to your patches within 1-2 days. Please derive patches from the most current OpenEMR development version from either of below repositories:
* The easiest way to get started on development is to [https://github.com/openemr/openemr/blob/master/CONTRIBUTING.md#code-contributions-local-development documented here].
** The 'master' branch from the git repository on sourceforge: git://openemr.git.sourceforge.net/gitroot/openemr/openemr
** The 'master' branch from the git repository on github: http://github.com/openemr/openemr ([[Git for dummies|quick howto documentation here]])
** The 'master' branch from the git repository on gitorious: http://gitorious.org/openemr/openemr
** The 'master' branch from the git repository on repo.or.cz: git://repo.or.cz/openemr.git


Again, feel free to email the administrators (listed above) with any questions or concerns.


Again, feel free to email the administrators, Rod Roark (rod at sunsetsystems dot com) and Brady Miller (brady@sparmy.com) with any questions or concerns.
[[Category:Developer Guide]]

Latest revision as of 12:25, 13 September 2022

Welcome and thank you for your interest in the OpenEMR system. The OpenEMR community is very open and we welcome contributions of code and ideas.

Here is some basic information for new developers to get up and running quickly:

  • Contributed code should be released under the General GNU Public Licence (GNU GPL 3)
  • To get started, feel free to introduce yourself at the developer forum or email the administrators, Rod Roark (rod at sunsetsystems dot com), Brady Miller (brady.g.miller@gmail.com), Robert Down (robertdown@live.com), Jerry Padgett (sjpadgett@gmail.com), Stephen Waite (stephen.waite@cmsvt.com) or Stephen Nielson (snielson@discoverandchange.com).
  • Here is an overview of the OpenEMR system architecture.
  • Here is an overview of the OpenEMR coding policies aka Coding Standards.
  • Here is an overview of How to Document Your Code Properly
  • The easiest way to get started on development is to documented here.

Again, feel free to email the administrators (listed above) with any questions or concerns.