...
- Become familiar with OpenMRS and the project(s) for which you're applying. If relevant, make sure you have OpenMRS installed and running. Read the Developer Guide, Getting Started as a Developer, and ask others in the community if you have questions. If you ask questions the smart way, you'll get better responses.
- Make sure your development environment is installed and running, and optimized for maximum efficiency. Review our Conventions page.
- Review project ideas listed here & ask questions about those or other projects in the GSoC category on OpenMRS Talk.
- Spend as much time as possible in our IRC channel or Telegram chat, as well as on OpenMRS Talk with other community members. Remember, GSoC-specific questions should be asked on Talk.
- Introduce yourself on the community introduction page on OpenMRS Talk.
- Achieve /dev/1 status. (earn the /dev/null badge and then earn the Smart Developer badge by passing the quiz).
- Work on JIRA tickets. Pick some tickets from JIRA (under your targeting project or anywhere) and work on those tickets. Send the pull request with your changes to respective repository
- Run, Test and identity some potential issues in OpenMRS Core or modules. Create new tickets in JIRA if those are not reported yet.
- Increase your visibility on OpenMRS Talk and IRC. Help others in the talk and participate in other's discussions as much as possible.
- Do some code reviews. Reviewing code from others is one of the great ways to learn the OpenMRS code base. This is a must. No student will be selected who has not done code reviews.
- If you're returning to do GSoC with OpenMRS for a repeat term, be just as thorough (or more so!) than first-time students. Don't skip steps and work extra hard to impress your mentor(s).
- Additional expectations :
- Write some blogs about OpenMRS or any related matters on OpenMRS which can help others.
- Properly document your work in JIRA and help others to continue from it.
- Work on some #community-priority tickets.
...