Now that many of us are making plans to attend our first world wide summit, we are welcoming as many as will be there and those that can remotely join in to our hackathon to be hosted at the summit venue on Sunday - Monday, 13 - 14 December 2015 after the conference.
OMRS15 Hackathon
Mingle, Learn, Share and Build reality.
Goal: To help community members socialize and learn something new from each other (learn, discuss, and then apply).
During the two day health hacking marathon, we expect various wonderful people of unique talents coming together and working towards solving selected issues and coming up with real world solutions that fulfill our OpenMRS mission, in other-wards we are to save lives throughout the two days via writing, testing, and using code.
Projects we are to work on:
We have so-far two projects subject to your vote;
We are expecting more project suggestions and project votings either by replying here or to this post. Please NOTE: suggestions are welcome only during October after which we shall close and consider the most voted projects.
We are setting up a hackathon environment to cover most of what we plan for this great important event which you can access even now from: http://omrs15-hackathon.devpost.com/ You may as well register with your email address on that platform in addition to your registration at http://omrs15.eventbrite.com/ so that we can keep you updated with all feedback and to help us in planning for this wonderful time that will positively affect the future of our community.
OpenMRS Inc is fully in support & sponsorship of the hackathon and therefore we are looking forward to a colorful successful hacking time where we shall have prizes for winners from the various working teams among several incentives.
Daily program/agenda (open to suggestions)
Organizers arrive and setÂup hack rooms
Opening
Previous hack update (moz15 hackathon on Sunday/first day, and previous day/Sunday on Monday)
Team confirmation.
Hacking.
Short timed Breaks
Surprising schedulesÍľ sort of interesting hack experiences, logical jokes from previously registered members etc; kind of the hackathon power-point karaoke.
Scrumming/progress updates.
Health IT or Medical world updates from registered members during some small breaks,
Etc/More suggestions are welcome.
Accepted projects shall be distributed to teams whose daily work timeline is as well still subject to suggestions:
Planning.
Team programming.
Tasks documentation.
Coding.
Testing.
Updates.
Etc/More suggestions are welcome.
WE ARE WELCOMING MORE PEOPLE TO BE PART OF OUR HACKATHON PLANNING AS WELL AS ATTENDING, AND IF YOU WOULD LOVE TO BE PART OF THE HACKATHON ORGANIZING TEAM, PLEASE WRITE TO @k_joseph PRIVATELY ON HOW YOU WOULD HELP OUT
@darius suggested “Applications using REST”. Perhaps one team creating a use case for REST and another team providing features/fixes to REST to support them.
@burke suggested improving timezone handling in REST (server handling better and/or using a library on client).
Nice to see people are interested in the Metadata Mapping Module! Here is a quick status update regarding said module.
I started working on the planned new features a while ago. My goal is to implement everything included in Metadata Mapping (Design Page).
Now, I do not how far I can get before the hackathon. Therefore I guess the possible hackathon goals regarding Metadata Mapping would be to continue working on the planned features that I have not managed to implement yet or to start working on some completely new set of features. Does someone have any ideas how we should proceed?
Anyway, I can keep you (who?) updated on my progress. Also, I will try my best to help in planning/coordinating, if required.
@kosmik - Great to hear that this is already moving forward! Let’s
create a Talk topic on this project and those of us interested in
updates on progress can watch it.
One idea for the hackathon: Instead of working on the Metadata Mapping Module itself, perhaps a team could work on implementing something that acts as a client to said module? Unfortunately, I must leave it to others to come up with the requirements for such a client.
