Welcome to the OpenMRS Hackathon Germany!
Join us in supporting the OpenMRS mission in a one day hackathon with the main focus on paying back technical debt that has accumulated over time.
How To Join The Hackathon
Everyone is more than welcome to join us for the hackathon! You do not need to be a domain expert in healthcare. However since we want to solve code related OpenMRS issues you need to be familiar with the technologies OpenMRS is built on. We expect you to have experience with Java and tools/frameworks such as maven, JUnit, Spring, Hibernate, Mysql.
In order for the organizers to cope with the logistics please join the meetup group https://www.meetup.com/ThoughtWorks-Berlin/
and register for the OpenMRS hackathon event you want to attend.
Mandatory Pre-Hackathon TODOs
If you want to join us for the hackathon please follow the next sections with at least a few days, even better a few weeks in advance. We want to spend the hackathon with helping out the OpenMRS community and not with setting up laptops. If you are having any issue or questions please refer to the need help section.
Get An OpenMRS ID
In order for you to claim the issue you’ll be working on in the OpenMRS issue system https://issues.openmrs.org you need an OpenMRS ID. This login is also used to login in to the OpenMRS forum http://talk.openmrs.org/ which is what you’ll need to talk to the community.
To get your OpenMRS ID
- go to https://id.openmrs.org/ and follow the instructions
- once you have your OpenMRS ID go to https://help.openmrs.org/ and request JIRA access and mention your OpenMRS ID
Please do this as soon as you are sure you are going to participate as this can sometimes take a few days. The helpdesk is run by the community which are mostly volunteers so please keep that in mind!
Setup Your Development Environment
Make sure you have completed the following steps before the day of the hackathon
- Create an account on https://github.com/
- Fork the repository https://github.com/openmrs/openmrs-core on Github (for help refer to the https://help.github.com/articles/fork-a-repo/ )
- Install all prerequisites and build the OpenMRS application https://github.com/openmrs/openmrs-core#build
- Followso you'll write code and unit tests according to the OpenMRS convention
- (Optional) Read and play with the OpenMRS SDK which helps you to quickly setup multiple demo servers like the publicly available http://demo.openmrs.org/
If you want some more details go to Getting started with OpenMRS
Read About OpenMRS Coding Conventions
- Java Conventions
- Unit Tests
- Unit Testing Conventions
- Pull Request Tips - this one especially before making your first pull request on Github
Optional Pre-Hackathon TODOs
Create Or Find Issues
You can help us in creating issues for the hackathon by getting familiar with the OpenMRS code base and especially by looking for
- critical or major code smells on the code quality tools OpenMRS uses: Sonar Cube or Codacy
- untested code using the Coveralls Code Coverage Site
- existing issues at https://issues.openmrs.org that are not labeled with 'hackathon-germany' but you think you can complete in a one day hackathon or you commit to complete soon after the hackathon
IMPORTANT NOTE: please involve the community in the ticket creation process, we do not want to drain community resources, the community should decide what is of importance. So be considerate, ask first at http://talk.openmrs.org/ or on IRC Chat if you are uncertain.
|April 22, 2017||OpenMRS Hackathon||9am - 8pm UTC+01:00||ThoughtWorks Werkstatt: Mülhauser Str. 6, 10405 Berlin; https://goo.gl/maps/95KSFxVCLT12||https://www.meetup.com/ThoughtWorks-Berlin/events/237696997/|
On the Day of Hackathon
What To Bring
Your laptop & your friends with laptop :)
What To Work On
Our goal is to complete as many issues as we can; the goal is not to claim as many issues as we can but to successfully complete them. Therefore please
- pair with someone if its your first time or if the issue seems more complex
- claim only issues as described in the section find tickets. These are tickets that the community pre-selected for this hackathon; please stick to those as the community put in time and effort in selecting issues it can use our help!
- furthermore if you have some ideas on how to improve the code which are not covered by the tickets please share them with the community
Find a ticket to work on
Please claim the the top most issue in the TODO column of the kanban board created for this hackathon:
The issues for the hackathon are all labeled with 'hackathon-germany' and already prioritized.