I did update https://wiki.openmrs.org/display/RES/How+To+Organize+An+OpenMRS+Hackathon with a Preparation section containing this information.
Can someone update https://wiki.openmrs.org/display/ISM/OpenMRS+ID since I dont have permission to edit the page. I think a section with ‘How Can I Get It?’ with link to https://id.openmrs.org/ + info on JIRA access through helpdesk would be good.
the ticket is already in progress 
you are so wise!!!
Loollll. It was too attractive not to be stolen by someone watching. 
I will update it tonight. PS…it’s being taken down tonight for an hour.
There are some tickets from the OMRS16-Hackathon here https://issues.openmrs.org/issues/?filter=17156 (some are still open)
@teleivo by the way congratulations on joining ThoughtWorks.
While you were away SDK became the most awesome tool equivalent of the GNU utilities for Linux, I suggest that you help the hackathon attendees set this up as it will speed up your environment setup for the modules especially openmrs-sdk:watch which allows changes to GSPs and Controllers to be autoloaded…
@raff and @SolDevelo team continue to work their magic …
Hey @teleivo,
Don’t know if that’s useful to you, but this is my post about a Ebola Hackathon we organised at ThoughtWorks Brasil. It might be useful to you.
Dear all!
I’ve come up with quite a list of issues (regarding refactoring and adding tests) which I think should be enough for the first time. Unless the GSoC applicants finish them before the hackathon which would be a nice side effect!!!
Am hoping that the people that come enjoy the hackathon and get a long and that we can repeat the event to get some more long term contributions. If you still have ideas for technical tasks that you would like to get done and that have been bugging you for a while, just tell me 
Something that bothers me is the high number of warnings Eclipse shows (+1000). Some of them are slightly hard to fix and test (I’m thinking about the generics ones) but others are easy (variables not used, deprecated methods etc.). I know it’s not a very interesting task to perform though.
good point! I did go through the most critical sonar issues, and after the critical ones are gone I would tackle the major ones. Unused vars for example where in there so Im sure some issues will be addressed. But I’ll keep that in mind. thanks @lluismf!!
Great work @teleivo 
I see the complexity of some tickets set to High. Was that intentional?
yes, since writing tests for methods that are not tested means you have to understand code that somebody else wrote. so I just wanted to signal to participants that if they are looking for a ticket to start, maybe a simple ‘remove unused …’ is best to do first. but we can also set it to medium. not sure if there is a wiki on this
At least Medium looks like a better compromise. 
